here it is http://www.samsungdeck.com/2016/04/26/samsung-rolls-security-update-galaxy-a3-europe/
Hi there. I just flashed the BPC2 upgrade to my A300FU via Odin and it failed. Since then, it seems that every rom I flash fail (even those I previously flashed with no trouble at all). Something like a partition problem (wrong size of some...)
Anyway, I could solve this by flashing the BOL3 version which failed, but immediately after flash the autoroot by Chainfire then original recovery to have my phone working.
But I tried again to flash any stock rom and it fails the same every single time. Someone would have a solution?
Also I cannot use the BPC2 version, autoroot seems to not work on it. Maybe related to security updates?
Related
I've flashed a few phones in my time including 2 S2's and an S3 although I had a big problem with this S3 my friend had. It had 4.1.2 default samsung software on it and i tried to ODIN flash an autoroot cwm v5 file i usually use to root phones, it did not go as expected eg. it just turned the phone off but came out as a pass on ODIN, and ii flashed it again with another CWM recovery file i found from the net, this time its V6+ and it flashed like a charm you know the usual result right. Now that CWM works i tried to flash 4.4.2 on the phone and it gave me that "set metadata recursive some changes failed" error thing and the phone wont restart. I have wiped the data, dalvik and cache every single time i flash mind you using the CWM recovery. Now when i flash to some random rom lower than KITKAT it would flash well and would function quite well. I once again tried to flash kitkat by downloading rom manager and flashing to the latest version of CWM but here's the thing it CWM wont update and the current version installed just wont flash the KITKAT rom and just gives the same 'set metadata recursive some changes failed error' and again wont boot to system if i didn't flash back to 4.3 i tried twrp too to the same result "set metadata recursive some changes failed". The fix that the forums explained was updating to the latest CWM(CWM touch wont flash neither) but it didnt work forme even TWRP didnt work, someone help please.
First reset all you've done by flashing a full stock 4.3 rom, factory reset and make sure everything works.
Then flash philz recovery and use that to flash your custom rom.
Make sure you read the guides in general forum, sticky threads before you start.
Hello,
I've read random threads for the entire day but I'm a bit confused about how to proceed.
cm wiki requires the phone to have stock ICS
I remember something about the baseband, using russian Windows tools to update
I don't have Windows
I'm running osx 10.9.4.
What should I do? I'm also afraid of the superbrick bug.
What I've done:
got root with zergRush
tried to install CWM through ROM Manager, got custom recovery 2.5.1.2 (useless? very old?) but can't boot into recovery, first error was something about signature, when rebooting with volume up+home+power I get "can't access to system/csc/hui/system" instead
I tried then updating stock fw with kies for osx; i was stuck in "connecting" forever
tried installing kies in a windows vm; it couldn't even see the phone and failed to recognize it as a media device
What I know:
I can probably obtain a temporary cwm 6.* (supposed to be not affected by superbrick bug) by loading a zip through stock recovery mode
What I would like:
finally get KK
avoid windows
avoid heimdall; i have bad experience and could never compile it, months ago
avoid yellow triangle
BUT
If heimdall is now a working software and It solves everything (baseband included) by running a one line command, it is a welcomed solution.
Thank you!
p.s. hope I'm in the right forum section
You have really old recovery.
If you want to get newest recovery and avoid windows and have root as you said use Mobile Odin pro to flash the newest CWM (6.0.4.5 I think) and afhter that flash CM via new recovery
I don't know why ROM manager installed something so old.
I thought about Mobile Odin. Does it fix the baseband problem?
ROM managers etc. is balast which made a lot of problems. Don´t be lazy and flash manully
So I recently got my hands on an international Samsung Galaxy S3. The device is bricked. I've already had a lot of experience with unbricking this device and I've always done it succesfully. However this time everything fails.
The situation: Currently running Clockworkmod Recovery 6.0.4.6, which is (more or less) the latest for this device. I've got an 8 GB micro SD-card, so flashing custom roms should work just fine. Unfortunately though, this is not the case. I've tried several roms already: cyanogenmod 10, 11, 12, 13, Blisspop, Blekota, Revolutionary android HD, S5-rom, Archidroid, Archiport, ParanoidAndroid... and they all fail to be flashed correctly through CWM. Some of them come with the Aroma-installer. The wizard launches succesfully and I've managed to install Archiport and Blekota with it. At the end of the wizard I get the prompt that the rom installed correctly. But when I reboot the device afterwards... still bricked!
I've also tried to install roms via Odin (3.07, 3.09, 3.10 .... ) but none of them installed right. Odin says "NAND Write start...." and then "FAIL!" Everytime, or Odin just crashes.
The only clue I can think of is Clockworkmod that's causing all these conflicts... I've had more succes in the past by using TWRP or PhilzTouch. So I tried to flash these other recoveries via Odin, which fails every time with every version of the recovery. I also tried to flash it using CWM. Here I get the message that the zip installed correctly, but when I reboot into recovey again I'm still running CWM.
Like I said, I've tried EVERYTHING. It's very unusual that NOTHING works.
Am I missing something?
Thanks
Brick in what sense????
Below is URL for your device please do a search before making/creating new thread, Requested to search before making any thread
Samsung S3 - http://forum.xda-developers.com/galaxy-s3
and for Troubleshooting http://forum.xda-developers.com/galaxy-s3/help
Still having problem please leave a post
Ive noticed when I flashed the newer version of rom for Oreo 8.1 , I had to use twrp backup to restore it to earlier version . I liked earlier one cause could edit the apn settings . Well when I tried to flash earlier rom through odin it would say something like "fail aboot binary 6>5 "
Thats why I used twrp backup . I had my phone with the mods I wanted so had the idea if I turned off OEM unlocking in developer would it then make my phone safer since it was already rooted and I happen to lose it .
So I did then my phone wouldnt start up just flashed green screen with red letters saying unauthorized binary on phone.
I didnt have my computer at time and couldnt go into safe mode .
I did get computer and tried flashing bootloader , that didnt work . I then flashed newest version Oreo 8.1 through Odin , phone loaded back up . I then put back into download mode flashed twrp 3.3.1.1 and installed Magisk 19.2 . Phone then said it needed to reset because integrity authentication failed and needed factory reset . I did and it booted into recovery and I reset and it failed.
The benefit of doing this that may help others flash earlier versions of roms or diff roms is that Odin was able to flash that earlier version without a binary fail ! This may work on other models , it may not work but worth a try if you know how to flash stock firmware .
Hi all,
I sadly followed an outdated Flash Manual on my S3 running Android 9 (used a Manual for 8). I succesfully installed TWRP and still have a working ODIN connection. Installing a clean Original Rom does not work though. Always aborts with an error message. My TWRP Backup Image seems to be corrupt also. It installs it back then my Tablet even starts but says it has to be restarted with default settings and when i do so it gets stuck in the bootloop again.
So my big hope is someone here can help me out with an Android 9 stock or maybe any other backup from TWRP to maybe get it back to the old state. Thanks in advance.
I do have a stock 9 for T825 in several parts directly from sammobile.
Would you mind writing which device you've got?
Which TWRP do you use.
Which Odin Version did you try it with?
Which original ROM did you try it with (where from, version aso) and why do you think another one would do the trick?
A backup from another device would'nt help afaik.