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 .
Related
So I have a Sprint Galaxy Mega and it seems as though it may be semi-bricked. It will not boot past the GALAXY MEGA logo. It will just continuously power cycle to and from that logo. If I attempt to put it in recovery, it will say "RECOVERY BOOTING" in blue letters as usual, then power cycle right back to the GALAXY MEGA screen. It will boot into Odin mode and accept Odin files, but after attempting do do a typical "stock Odin" scenario, nothing has changed. I looked around for the Pit but cannot seem to find it. Does anyone has a reliable link to the latest Odin stock restore and the PIT file that matches it?
Maybe an error with your system data. So you can't reboot into recovery ? If you can try to wipe data and cache and reboot.
It may be an abnormal re-partition when flashing stock rock, and then I can't help you (have the i9205 international model). Some members of this section have the Sprint version, try to send them a PM if nobody can help you
Nope, no recovery. I was considering flashing a custom recovery to it to see what it does but I don't wanna kill the phone any more than it already is...
Yes I understand. But flashing custom recovery can solve your problem, only if you can boot on it. I think it can't make more damages to your phone, he just always stuck on boot phase like a brick, but if you don't want to try, wait for a developer making you a PIT file. More safe, the Galaxy Mega have a too poor development support for risk anything...
Well I went ahead and flashed TWRP to it. It will boot into TWRP just fine. Tried flashing the stock L900 ROM zip and it still won't boot.
Well I installed a custom ROM, SlimKat, and the phone boots. If I install the stock ROM located in the following link, OP's signature, the phone goes right back to bootlooping. ???
I need either the stock ROM or a ROM with dialer codes because this phone will be flashed to a regional carrier.
what recovry version you use bro. maybe recovery problem. try use your custom rom to flash another recovery from philz. the latest one. some time recovery dont work properly to downgrade from 4.4.2 to stock 4.2.2.
Great, so with Philz Touch Recovery, I never had problems for downgrade and I do this often for testing roms. Now it should not bootloop if you reflash stock.
I am using "CWM-based recovery 6.0.4.7"
I will try Philz recovery
After trying Philz recovery to flash the stock file I found, it once again bootlooped. Is there another stock ROM floating around somewhere or possibly a custom ROM that has dialer codes such as ##3282# enabled?
No idea... But actually the most complete stock based custom rom is MegaFire I think. Flash V5 (not V5x !) it should be enabled.
I don't see what is the problem while flashing stock rom... Oh ! Maybe you haven't enabled USB Debugging, I forgot to do that one time and I had some issues, in case you try to flash a firmware where Knox or others features are on with a modem without these, may cause bootloop. I've searched for 2 days before solve that little problem...
Have you tried another firmware ? If you can flash custom rom, something went wrong before flash... Odin folder is complete ?
Strange...once again a boot loop after flashing the MegaFire ROM
I'm almost certain I need the PIT file. I cannot find it anywhere.
Well I got the phone to boot from that rooted stock ROM FINALLY. I don't remember for sure but I think what I did was first flash TWRP, then flashed boot.img.tar that I found somewhere, it was listed for the Sprint Mega. I then booted into TWRP and flashed the stock rooted ROM(zip) I mentioned before. It now boots perfectly and everything works except one tiny little detail. No WiFi, no cellular signal at all. Baseband version: unknown in About phone.Already tried flashing the Sprint stock modem from the same download link as the ROM and it didn't work.
I'm having the same problem too dude, I
I download n flash all.the firmware I could find online, since I have no idea what the country of origin is. But most of them work, but no WiFi, Bluetoothand the sim card slot don't read
VirtueToVice said:
Well I got the phone to boot from that rooted stock ROM FINALLY. I don't remember for sure but I think what I did was first flash TWRP, then flashed boot.img.tar that I found somewhere, it was listed for the Sprint Mega. I then booted into TWRP and flashed the stock rooted ROM(zip) I mentioned before. It now boots perfectly and everything works except one tiny little detail. No WiFi, no cellular signal at all. Baseband version: unknown in About phone.Already tried flashing the Sprint stock modem from the same download link as the ROM and it didn't work.
Click to expand...
Click to collapse
hellow guys !
recently i flashed some roms on my GT-S6310....no problem whit them....everthing worked perfectly (just to compare them)
so.... i flashed a stock rom on my phone to apply a theme....everything went good....how i expected my custom recovery image was replaced whit the stock one ....... so far so good....but when i try to flash via Odin the same CWM it show me "pass" but when i boot into recovery it appear the stock one
in that way i tried a milion of methods to flash the custom one but they wasn't work
even the "root" didn't worked :crying:
now i'm stack into the stock rom , whitout any way to escape
please guys help me to understand why it happened , and how to resolve it
stefan254235435235411354 said:
hellow guys !
recently i flashed some roms on my GT-S6310....no problem whit them....everthing worked perfectly (just to compare them)
so.... i flashed a stock rom on my phone to apply a theme....everything went good....how i expected my custom recovery image was replaced whit the stock one ....... so far so good....but when i try to flash via Odin the same CWM it show me "pass" but when i boot into recovery it appear the stock one
in that way i tried a milion of methods to flash the custom one but they wasn't work
even the "root" didn't worked :crying:
now i'm stack into the stock rom , whitout any way to escape
please guys help me to understand why it happened , and how to resolve it
Click to expand...
Click to collapse
Don't let it auto reboot after the recovery flashes. Either uncheck auto reboot or just hit the combo for recovery when the phone reboots. Many newer Samsung phones have a script that reinstalls the original recovery if it realizes that you have changed it. You have to install another rom or root it and remove the script and reflash the recovery and it'll stick if you just want stock rooted.
es0tericcha0s said:
Don't let it auto reboot after the recovery flashes. Either uncheck auto reboot or just hit the combo for recovery when the phone reboots. Many newer Samsung phones have a script that reinstalls the original recovery if it realizes that you have changed it. You have to install another rom or root it and remove the script and reflash the recovery and it'll stick if you just want stock rooted.
Click to expand...
Click to collapse
didn't worked...... after i flash the recovery (i'm in download mode) i boot directly into recovery.... the same problem
try to instal the recovery via rom manager.....seems to work.....but when i want to boot from rom manager into recovery it show me an error ("an error occurred while attempting to run privileged commands !" )
what should i do now ?
http://galaxyyoungs6312.blogspot.com/2014/01/clockworkmod-recovery-for-galaxy-young.html
6310 + 6312 use the same recovery.
yeah....but i tried that rooting method and it didn't work....
maybe i can flash a new rom from ADB but i can't pass the signature verification
any ideas ?
Well I can tell from your pictures that you didn't follow the suggestion of trying SuperSU, but that might not help anyway. That Framaroot version is an older one. Get the updated version from here: http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276 and use SuperSU instead of Superuser. Sometimes you have to run it a couple times before it'll go through. Reboot in between tries. Here are better instructions for the rest of the process:
http://forum.xda-developers.com/showthread.php?t=2460029
man ...didn;t work... ... tried at least 5 times .....
or....i can flash a rom from ADB but i can't pass the signature verification....
a have an ideea ....maybe i can flash via odin a rom whit a custom recovery ...from there i can flash an old backup of mine .....it's good to proceed right that ?
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
William31 said:
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
Click to expand...
Click to collapse
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
mattnmag said:
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
Click to expand...
Click to collapse
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
William31 said:
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
Click to expand...
Click to collapse
Cool. Glad you got it fixed.
As you know, you can root with GhettoRoot from this thread: http://forum.xda-developers.com/showthread.php?p=57238246
Then can install Safestrap from this thread: http://forum.xda-developers.com/showthread.php?p=51616723
I've never used Safestrap because I can use regular custom recoveries like CWM and TWRP. I'm still on a 4.1.2 unlocked bootloader and currently running TrentsKKRom, Build #2...which is 4.4.2 based with stock kernel, so I think it would work with Safestrap.
I'd recommend reading through the Safestrap thread thoroughly and asking questions there to make sure you get everything installed correctly. I've read that with Safestrap, you need to make a backup of your Stock ROM first and save it somewhere safe, like to your computer and on your external sd card...so you can easily restore it if needed. (I'd also make a backup of the ESF in Safestrap if it lets you, then save it somewhere safe).
After you are rooted with Safestrap, you'll have to flash custom ROM's over the stock slot in Safestrap, as the other slots apparently don't work. Again, you're limited to only using Touchwiz ROM's with the stock kernel because of the bootloader still being locked.
Check out TrentsKKRom and Alliance build 30 . (I personally like Trent's build 2 best with the S5 clean theme). I've also found Trent's ROM to be really smooth without UI lagging, the Bluetooth works good with no stuttering, and it pairs well with my Sony Smartwatch 3. (Edit: If you do try Trent's ROM, you may need to install a couple apps.... Chainfire's Supersu app to control your root permissions (at least I needed to), and the FolderMount app to fix a KitKat internal storage mounting issue).
Have fun!!
So I wanted to install the new Android 6.0 for a few days ago. I accidentally installed the 6.0 bootloader first, and the phone i just stuck. I have installed the newest TWRP recovery and tried flashing stock rom ANDROID 5.1.1 , i also tried use smart manager to emeregency recover the phone... nothing semms to work, please help me. Every time im trying to flash a new rom in odin i just says NAND WRITE START!! FAIL!!
Well make sure that your is usb is ok, try on diffrent computer that your device has not been connect because the marshmallow diffrent set of drives , Try re download the copy of the firmware it might get damaged during downloading. Try to use the old tested kies it is more stable...
So I recently tried to unroot my device with flashing official ROM on it. Apparently I used the wrong file because my phone got bricked. I tried using XiaoMiTool by Francesco but it didn't help. I spent a lot of time trying to fix it so ill post what worked for me. I downloaded a lot of ROMS but none of them worked for me there was either flash error or device mismatching and I couldn't find right flash official software anywhere. I downloaded another ADB fixing program which worked, I downloaded Szaki/XiaomiADB fastboot tools which worked perfectly. I simply connected my phone searched for my phone code name (tucana) downloaded ROM from there, wiped all data off and finally flashed OS on my device. I also have a question, are there any android software fixing programs for phone repair companies or something similar?
Have good day and stay healthy,
MX8MC8
id suggest to unbrick with mi flash tool.
I did that always when i was stuck on something, it ofcourse removes your data but saves the device so its still the profit probably... After succesfull rom installation you can flash again.
Also you do this in fastboot mode
When I was stuck in the same way the solution I found was to flash whatever rom then when the phone bootloops, go into recovery, and format data. Afterwards it will boot to startup screen and take forever to load up. Anyway that is my solution, before that I would have to flash stock recovery to boot for the first time then flash a custom recovery back.