Related
Hi All,
The short of a long story is that I just changed carriers and found out way late that I couldn't bring my Sprint phone to MetroPCS. So now I'm using the budget PCS On5 that came with the deal when we signed up.
I successfully loaded TRWP and then rooted however, I didn't know about FRP until it smacked me in the face. The root went fine but later SU prompted me to update the binary and when it did, it tripped factory reset protection and soft bricked my phone.
I want to reinstall stock OS on this phone but it appears that I have a software version that I haven't been able to find on the web yet. I found the stock rom for the MetroPCS On5 easily enough but it's Revision 0.0 and the box I have for the phone says REV0.4.
When I try to Odin Flash the REV0.0 version, I get SW REV CHECK FAIL DEVICE 2, BINARY 1 fail. So I guess I had the latest software on my phone and the phone thinks I'm trying to roll back using the 0.0 revsion.
My question is this, does anyone here have the stock rom for G550T1 REV0.4? Help!
If nobody does, maybe I can still fix this phone. I have a TRWP backup from the sister phone (same model same revision 0.4) that I'm using right now but I can't get back into TRWP on the soft bricked phone to recover that way to use the backup file.
Next I thought I might take the backup files and turn it into a rom and just flash that. However, with the tutorials I followed I kept running into problems. When I went to unpack the files per the tutorial, my rar software said that the file was corrupt. Maybe it is. but maybe not. It was my first time attempting to make a rom. If I can't find the software I need, could any of you Android geniuses help me get this backup into a flashable format?
I have to admit I'm daunted by the FRS in 5.0 and above. Is it defeatable? How do you root newer Android versions?
Thanks!
I did the same thing to my phone. did you get yours fixed?> if so could you provide me with the rom?
I haven't found the fix yet. Hopefully somebody will come through with a helping hand!
I finally got it figured out! So here is what i did and hopefully it will work for you.
1. I Odin flashed a good BL from the ROM REV0.0 floating around on the net. So at least I could now get into download mode.
2. Then I used Kies3 > Tools > Firmware Upgrade and Initialisation. It will ask you for your model number and then when you click ok it will ask you for a SN.
3. The trick is that Samsung doesn't put the SN that you need on the phone or the box. (personally, I couldn't find it on the phone either once I got it up and running) so go here: https://forum.xda-developers.com/android/general/root-samsung-galaxy-on5-t3435457/page46 and get a SN from post #454 and use that. (don't forget to say thanks)
4. Click Ok. Let it work, and max and relax.
Mine took about 10 minutes. Hopefully this will work for you too! Thanks XDA!
Help!
What is BL from the ROM REV0.0? I need your help, I have the MetroPCS On5 and I installed Reborn ON5 I want to go back to the MetroPCS ROM because the camera and the audio do not work and I tried to install the original ROM through Odin but it does not work I get an error. What I can do? I would like to use this method but I do not have very clear files needed.
You could help me bro, I'll thank you
Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera
I recently purchased a new S7 not realizing that it was equipped with a Nougat OS. I would like to restore my current phone to the new one, but my current phone runs on MarshMallow. After restoring the backup, my new phone has no haptic feedback, no fingerprint sensor with "an error has occurred with the fingerprint sensor. if this message appears repeatedly, restart your phone" message and the Camera doesn't work.
I'm sure it has something to do with bootloader N using MM. Even restoring Stock Marshmallow firmware (Including BL) on the new phone removes these functions. Does anyone have any ideas on how I can get these to operate?
My current phone has
Bootloader Version: G930W8OYA2APK3 (MM)
Baseband and PDA Version: G930W8OYA2API1 (MM)
When I restore my old phone to the new one, it ends up with
Bootloader Version: G930W8OYA2BQK4 (N)
Baseband and PDA Version: G930W8OYA2API1 (MM)
EDIT: Just tried the Nougat firmware with MM Bootloader. All of the functionality is present.
Bootloader Version: G930W8OYA2API1 (MM)
PDA Version: G930W8OYA2BQK4 (N)
Just restored old backup with MM bootloader (Boot, Data, System only).
No Fingerprint Sensor or Camera.
BTW, ignore the HAPTIC FEEDBACK portion of this post. I believe it is working.
Any help with this matter would be greatly appreciated.
Not possible to downgrade since the bootloader block you from flashing lower version of that. You may try to flash without BL, but your phone will be malfunction
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Sleaze0 said:
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Click to expand...
Click to collapse
do not flash AP from a firmware set made prior to the bootloader youre on, it will more than malfunction, itll probably brick
i went back and read all the tl : dr stuff and saw that you seem to have got it working, oddly enough. The camera issue is likely the kernel
Thanks for the info on the thanks button. I've just about given up trying to get Marshmallow to work properly on this phone. Looks like it'll take weeks to configure my new Nougat phone to be similar to the three years of tweaks I've made to my old MM one. Oh well, first world problems I guess.
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Droiderat said:
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Click to expand...
Click to collapse
i cant even begin to imagine how/why that would work. the bootloader doesnt really care what ROM you install, its the other way around. The ROM being installed has to be compatible with the bootloader. So, installing a ROM wouldnt really do anything to the bootloader and therefore wouldnt be able to bypass the lock in knox.
The procedure I outlined apparently works where the custom ROM includes a related bootloader. Thus, when it is installed via TWRP, it replaces both the existing ROM and the bootloader. I know that TWRP can be used to install a bootloader, as I have done it (on a SM-930F). And if the gatekeeper is Odin and not the bootloader itself, then this could work.
As I stated, I haven't tried this, nor have I extensively researched it. I've only read about it, and am passing it along as a possible solution.
This post can be closed since the phone was deemed Lost or Stolen by the carrier, therefore they couldn't unlock it for me to use my SIM card. I've since returned the phone. At least I learned a few lessons for my next one. Mainly, back up the phone when you first get it. Thanks again for all of the feedback.
So I have a Samsung j260AZ and it got stuck in firmware binary and will not accept any of the original firmware because of the Bit numbers below
B=5 K=5 S=5 <-- this was not the original numbers
So I Am trying to figure out how I can get the phone to accept the firmware.
I've tried 3 different odins (Comsy, 13.3, patched)
I have tried numerous ways to flash this phone and it just wont get back to normal.
HELL I even tried flashing the wrong firmware just to get firmware binary to leave and any kind of launcher to boot up but it wont accept any kind of firmware ...and I am not trying to go any higher in bit numbers. I tried to flash a unlocked version of bit security but that doesn't work either.
Anyways if anyone has any options I can do please let me know.
TheofficialJonerockit said:
So I have a Samsung j260AZ and it got stuck in firmware binary and will not accept any of the original firmware because of the Bit numbers below
B=5 K=5 S=5 <-- this was not the original numbers
So I Am trying to figure out how I can get the phone to accept the firmware.
I've tried 3 different odins (Comsy, 13.3, patched)
I have tried numerous ways to flash this phone and it just wont get back to normal.
HELL I even tried flashing the wrong firmware just to get firmware binary to leave and any kind of launcher to boot up but it wont accept any kind of firmware ...and I am not trying to go any higher in bit numbers. I tried to flash a unlocked version of bit security but that doesn't work either.
Anyways if anyone has any options I can do please let me know.
Click to expand...
Click to collapse
Let me guess, you updated your device and now you want to go back to what you had?
Or, your device needed to have the stock firmware reflashed to repair the device to normal function and now you are trying to flash the stock firmware to repair the device but the firmware you are flashing is older than the firmware that was already on the device?
If either of these is the case for you, it is failing because you can't downgrade from a higher binary down to a lower binary, you can only keep the binary you have or flash up to the next binary, but once you go up to that next binary, once again, you can't go back to the binary that you had before.
In other words, if the firmware that was already on your device was a binary 6 or higher firmware, you can't flash the binary 5 firmware, you could flash a binary 7 over the binary 6, but once you had binary 7 installed, you could never go back to binary 6 or binary 5.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Let me guess, you updated your device and now you want to go back to what you had?
Or, your device needed to have the stock firmware reflashed to repair the device to normal function and now you are trying to flash the stock firmware to repair the device but the firmware you are flashing is older than the firmware that was already on the device?
If either of these is the case for you, it is failing because you can't downgrade from a higher binary down to a lower binary, you can only keep the binary you have or flash up to the next binary, but once you go up to that next binary, once again, you can't go back to the binary that you had before.
In other words, if the firmware that was already on your device was a binary 6 or higher firmware, you can't flash the binary 5 firmware, you could flash a binary 7 over the binary 6, but once you had binary 7 installed, you could never go back to binary 6 or binary 5.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Yeah that's what I read also
but I was just hoping that it wasn't true or that their was some way to intercept or clone its coding but install the real thing.
Well I guess I am gonna make this phone my test phone and see how badly I can screw it up by installing stuff and test software on it. LoL until it wont work anymore.
Has anyone tried Linux/Heimdall vs Windows/ODIN? I am just curious to try it myself as I gave up on Windows years ago. It also seems to me that since Android is a Google-based form of Linux, that a Linux user may have more success.. I will be attempting it myself as I cannot get my phone to update to Android Pie, or anything after the June 2019 version of Oreo and the security updates. Contacting Cricket nor Samsung is of any use as they are both reluctant to help anyone with any issue that doesn't include buying something (i.e. new warranty, new phone, new service upgrade, ect.), even though my phones are always purchased, not leased. Anyway.... I will be either flashing this old and busted thing or destroying it completely. Wish me luck.
Tried to root using a method that involved 4 odin files which I guess is most methods nowadays. Im used to old root methods were there is only one file I need to flash so I only flashed one file and it failed I don't have snapdragon chip set I don't think I googled my IMEI number and it said I didn't. Now my phone is stuck in Bootloop I tried flashing stock firmware I got from Sammobile and other sites making sure it was the latest version and it didn't work. I went into Maintenance recovery and tried factory reset it gave me the erasing screen but would still not boot up. I can still enter download mode and recovery but nothing seems to work please help.
Tried flashing ENG boot although I have no clue what it is but it made no difference. Tried also flashing TWRP I got error: SECURE CHECK FAIL: recovery. I did some research and apparently I might have a locked bootloader.
I just want to boot into my phone whatever it takes please help
Last OS update I got was either may or june
IMEI: 358166076487955
If your phone is model SM-G935V, aka Verizon, you have a Snapdragon chip. Therefore, there is no TWRP. And, depending on the bootloader version you had prior to attempting root, you might be out of luck.
What was your firmware version BEFORE you attempted root? (For example, mine is: G935VVRS4CRI1). The 5th digit from the right is the important one.
SkylineDriver said:
If your phone is model SM-G935V, aka Verizon, you have a Snapdragon chip. Therefore, there is no TWRP. And, depending on the bootloader version you had prior to attempting root, you might be out of luck.
What was your firmware version BEFORE you attempted root? (For example, mine is: G935VVRS4CRI1). The 5th digit from the right is the important one.
Click to expand...
Click to collapse
Thank you for your help but i figured it out. Finally found my specific firmware and got it to boot. the thing is I googled my IMEI and it says I dont have a snapdragon I have an exynos chipset. Did some more digging and it confirmed I had an exynos chipset. Problem is fixed though thank you for the help.
If you have Exynos then it is not a Verizon branded phone. Your phone might be working on the Verizon network, but....
Either way, thanks for the update. Glad you got it sorted.
I bypassed the 360 hr period to unlock Bootloader. I made a new Mi a/c and used a older software to do bypass the period. Older softwares have a error asking them to update the unlock tool to the latest version, but this software didn't prompt for such updates, rather unlocked my bootloader the same day I got my device.
Also, Official TWRP didn't recognize my Internal storage, and would get replaced by stock recovery even after flashing lazyflasher. So, I extracted the recovery image form Orangefox zip and flashed via the fastboot mode, and then flashed custom ROM over it, and finally it worked. I am currently on Havoc os v3.8 without google services and Agni Kernel 9.7. I couldn't get any version of Gcam working, although mine is not Indian Whyred version, so am currently using TRcam v7 clone. Everything is working well. I am getting 8-10 hours of SOT, depending on use.
I am not a developer, and am just a newbie, and If this thread could help other newbies like me, I'd be glad. Thanks.
dl.mi-globe.com/dl/rdAy5/mi-globe.com_Xiaomi_Mi-UnlockTool_3.5.1108.44.zip ( I can't attach hyperlink because I have a new account)