I started the night by downloading a rooted kernel for the phone and installed that using ODIN. All good.
Next I installed a TWRP recovery image using the flashify application from the app store. That works and were still good.
Then I had to flash a "modem" and "bootloader" for marshmallow (note I do not really understand what these were for, i was trying to follow a guide).
This is where it went screwy, after flashing these 2 files for my specific device through ODIN, it would not boot.
Im not sure but likely to make things worse, I attempted flashing a new TWRP recovery version because i belived it would work with the modem and bootloader.
Ive now tried flashing the stock firmware using ODIN but i get a FAIL message. Please please help, i only just got the phone and i feel hopeless.
semb37 said:
I started the night by downloading a rooted kernel for the phone and installed that using ODIN. All good.
Next I installed a TWRP recovery image using the flashify application from the app store. That works and were still good.
Then I had to flash a "modem" and "bootloader" for marshmallow (note I do not really understand what these were for, i was trying to follow a guide).
This is where it went screwy, after flashing these 2 files for my specific device through ODIN, it would not boot.
Im not sure but likely to make things worse, I attempted flashing a new TWRP recovery version because i belived it would work with the modem and bootloader.
Ive now tried flashing the stock firmware using ODIN but i get a FAIL message. Please please help, i only just got the phone and i feel hopeless.
Click to expand...
Click to collapse
Can you tell me at which point in odin do you get the error? When 9n the log in odin do you get error?
Eg: hidden.img FAIL
semb37 said:
I started the night by downloading a rooted kernel for the phone and installed that using ODIN. All good.
Next I installed a TWRP recovery image using the flashify application from the app store. That works and were still good.
Then I had to flash a "modem" and "bootloader" for marshmallow (note I do not really understand what these were for, i was trying to follow a guide).
This is where it went screwy, after flashing these 2 files for my specific device through ODIN, it would not boot.
Im not sure but likely to make things worse, I attempted flashing a new TWRP recovery version because i belived it would work with the modem and bootloader.
Ive now tried flashing the stock firmware using ODIN but i get a FAIL message. Please please help, i only just got the phone and i feel hopeless.
Click to expand...
Click to collapse
use samsung smart switch to restore ur device to factory settings
it will fix ur phone back to normal
If smart switch doesnt work download your stock firmware from sammobile (make sure its the correct variant. Also were your updating from 5.0 to 6.0?
Related
I tried to do AdamOutler's unlock bootloader stuff, and when i flashed the unlocked bootloader file in his thread i got a boot loop, so i tried to flash the stock bootloader file also in his thread. now i get the yellow triangle saying i need to take it back to the store. i can still flash with odin and i just tried to flash the unlocked bootloader again and now i get a fail message in odin.
please help!
even if i can get back to the bootloop i'm willing to take it back to verizon at this point. i just dont want to do that with the yellow triangle, i could just make up some something for the bootloop.
Have you tried flashing back with the stock odin image?
fhould oriushe
SirVilhelm said:
Have you tried flashing back with the stock odin image?
Click to expand...
Click to collapse
i am currently downloading that (internet sucks.... 1 hour download -_-), i hope it fixes is, otherwise i think its the bootloader thats throwing the error and ive tried flashing the stock bootloader file Adam gives in his guide with no luck
ODIN will flash the stock bootlooder
znilsson said:
I tried to do AdamOutler's unlock bootloader stuff, and when i flashed the unlocked bootloader file in his thread i got a boot loop, so i tried to flash the stock bootloader file also in his thread. now i get the yellow triangle saying i need to take it back to the store. i can still flash with odin and i just tried to flash the unlocked bootloader again and now i get a fail message in odin.
please help!
even if i can get back to the bootloop i'm willing to take it back to verizon at this point. i just dont want to do that with the yellow triangle, i could just make up some something for the bootloop.
Click to expand...
Click to collapse
the first thing you ever do before flashing anything on your device is have a stock rom to odin back on. second your not following directions. third your device is not bricked...flashing back to stock will bring it back.
I'm having a similar issue. I had followed adam's protocol for rooting and unlocking using CASUAL; once the process was completed I received a notification claiming that my device was now 'rooted and unlocked.' I then proceeded to download ROM manager and flash clockwork recovery and upon reboot receive the 'system software not authorized' message. At this point I attempted to use the official ODIN provided in droidstyle's guide on root/unlock/etc thread. I see a successful flash of the image but still cannot get out of the unauthorized system software error. Any ideas? Thanks in advance.
tehlol said:
I'm having a similar issue. I had followed adam's protocol for rooting and unlocking using CASUAL; once the process was completed I received a notification claiming that my device was now 'rooted and unlocked.' I then proceeded to download ROM manager and flash clockwork recovery and upon reboot receive the 'system software not authorized' message. At this point I attempted to use the official ODIN provided in droidstyle's guide on root/unlock/etc thread. I see a successful flash of the image but still cannot get out of the unauthorized system software error. Any ideas? Thanks in advance.
Click to expand...
Click to collapse
you need to use the pitfile with the stock odin image...check out section1 again!
droidstyle said:
you need to use the pitfile with the stock odin image...check out section1 again!
Click to expand...
Click to collapse
i did! that's why i was a bit surprised that it didn't work. i downloaded both the VRALJB 4.1.1 stock image and pit file, placed them into their corresponding locations in ODIN and flashed away. should i be allowing ODIN to repartition the disk? (thanks for the help droidstyle!)
tehlol said:
i did! that's why i was a bit surprised that it didn't work. i downloaded both the VRALJB 4.1.1 stock image and pit file, placed them into their corresponding locations in ODIN and flashed away. should i be allowing ODIN to repartition the disk? (thanks for the help droidstyle!)
Click to expand...
Click to collapse
Edited:Sorry read your earlier post. Not sure how to help sorry
I'm posting this here hoping it will help someone out. A lot of people would rather not ship their phone off to a 3rd party for the unbrick, and also don't want to disassemble their device to do the resistor fix.
This is for people who flashed the wrong bootloader to their device, and now have a non-working "bricked" phone. It can be the N7100, N7105 or any other bootloader. This is the method I used to get my phone working, on AT&T with 4G service and everything working as it should.
Anyways, let's get down to business and fix that device!
You will need:
Odin Software
Stock ND3 Odin compatible stock ROM (I used N7100XXUFND3_N7100OXAFND3_XEF)
N7100 TWRP Recovery (Latest Version, Odin Flashable)
An i605 ROM (I used DN3)
1. Use odin to write the N7100 pit file
2. Then, using Odin, load "N7100XXUFND3_N7100OXAFND3_XEF" into the "PDA" section, after that was finished, I booted into the stock recovery and did a factory reset. That allowed the phone to boot up, but baseband was "Unknown" and it had no service.
3. Then, use Odin to flash the latest version of TWRP for the N7100(it MUST be n7100 or it will bootloop/stick on the Samsung/Rom Booting screen)
4. Then you must flash "N7100_ND3_DrKetan_Custom_ROM_V82.zip" using TWRP recovery, it will boot that up just fine, still says "Unknown" for baseband(i'll explain later why I flashed this, and am directing you to also flash this, despite bootloader still not working).
5. After that, flash "DN3_v5.2_VZW.zip", again, using TWRP Recovery. After that my phone booted up it had service and all of my apps worked.
When I skipped Step 4, a few apps wouldn't work correctly. Instagram wouldn't refresh the feed or load anything, Snapchat wouldn't open anything or send anything either. I'm not sure why that happens, but it ONLY happened if I didn't flash the N7100_ND3_DRKetan ROM before flashing the DN3 ROM.
These are the exact steps I followed, after accidentally flashing the N7100 bootloader onto my i605 Note 2. You MIGHT also have to flash the i605 EFS file to restore your baseband. On ocassion, I had to or I would get Unknown Bootloader. It would also help to flash the "I605VRAMC3 Modem.zip" file, to ensure you're on the i605 Modem.
Broken note 2 verizon
Hello beautiful people who work our confort
I have a big problm with a phone of a friend. i wanted to write firmware of an gt-n7105 on sch-i605 without know that will broke my phone.
I tryed to write with Odin every programs on it but nothing work. i got message "NAND write fail". I tryed to write pit files but nothing work. and erase and everything.
Any ideea of something else?
Thank you and sry for bad writing
iiNFAMOUS CHRiS said:
I'm posting this here hoping it will help someone out. A lot of people would rather not ship their phone off to a 3rd party for the unbrick, and also don't want to disassemble their device to do the resistor fix.
This is for people who flashed the wrong bootloader to their device, and now have a non-working "bricked" phone. It can be the N7100, N7105 or any other bootloader. This is the method I used to get my phone working, on AT&T with 4G service and everything working as it should.
Anyways, let's get down to business and fix that device!
You will need:
Odin Software
Stock ND3 Odin compatible stock ROM (I used N7100XXUFND3_N7100OXAFND3_XEF)
N7100 TWRP Recovery (Latest Version, Odin Flashable)
An i605 ROM (I used DN3)
1. Use odin to write the N7100 pit file
2. Then, using Odin, load "N7100XXUFND3_N7100OXAFND3_XEF" into the "PDA" section, after that was finished, I booted into the stock recovery and did a factory reset. That allowed the phone to boot up, but baseband was "Unknown" and it had no service.
3. Then, use Odin to flash the latest version of TWRP for the N7100(it MUST be n7100 or it will bootloop/stick on the Samsung/Rom Booting screen)
4. Then you must flash "N7100_ND3_DrKetan_Custom_ROM_V82.zip" using TWRP recovery, it will boot that up just fine, still says "Unknown" for baseband(i'll explain later why I flashed this, and am directing you to also flash this, despite bootloader still not working).
5. After that, flash "DN3_v5.2_VZW.zip", again, using TWRP Recovery. After that my phone booted up it had service and all of my apps worked.
When I skipped Step 4, a few apps wouldn't work correctly. Instagram wouldn't refresh the feed or load anything, Snapchat wouldn't open anything or send anything either. I'm not sure why that happens, but it ONLY happened if I didn't flash the N7100_ND3_DRKetan ROM before flashing the DN3 ROM.
These are the exact steps I followed, after accidentally flashing the N7100 bootloader onto my i605 Note 2. You MIGHT also have to flash the i605 EFS file to restore your baseband. On ocassion, I had to or I would get Unknown Bootloader. It would also help to flash the "I605VRAMC3 Modem.zip" file, to ensure you're on the i605 Modem.
Click to expand...
Click to collapse
go here, it's a more detailed tutorial to fix it:
How-To: Recover Your Samsung Note 2 [i605] From A Hard Brick [From Flashing The Wrong Bootloader(ex. N7100)] WITHOUT Using A Resistor
i rooted my devce using cwm(n9005-cwm-recovery-6.0.4.7-kk(0125)) and gained super su access.
tried to put new rom on went through the process of backing up which i dont thinhk worked, and wiping the sustem
tried to put on new rom using cwm and got an error on startup
so i tried to go back and start the whole process over again
using odin i tried to flash the phone and FAIL
i am stuck in a loop everytime i start normal or start in cwm i get a message saying firmware upgrade encountered an issue. please select recovery mode in kies and try again
but i can still use ODIN
What can i do
Thanks
I'd use TWRP if I were you and save yourself some headaches. From my understanding, CWM is hit or miss on our beloved Note 3.
https://dl.twrp.me/hltespr/twrp-2.8.6.1-hltespr-4.4.img.tar.html
Sent from my SM-N900P using XDA Free mobile app
Shotty2015 said:
i rooted my devce using cwm(n9005-cwm-recovery-6.0.4.7-kk(0125)) and gained super su access.
tried to put new rom on went through the process of backing up which i dont thinhk worked, and wiping the sustem
tried to put on new rom using cwm and got an error on startup
so i tried to go back and start the whole process over again
using odin i tried to flash the phone and FAIL
i am stuck in a loop everytime i start normal or start in cwm i get a message saying firmware upgrade encountered an issue. please select recovery mode in kies and try again
but i can still use ODIN
What can i do
Thanks
Click to expand...
Click to collapse
First what version of KK where you on when you rooted your device ? Anyway pull battery then reinstall battery. Boot into download mode, then odin flash the version of KK you had before you rooted your phone.
Chances are the device won't boot. DON'T PANIC !!! Happenes all the time, just pull the battery again. Boot into download mode again, and odin flash the stock KK again it should boot the second time.
Once you get it to boot up, check and see what version of KK you are running and make the kernel , modem, and bootloader are the same.
At this point l would odin flash it again to make sure you have a clean install. Now you can root and install a custom recovery. I use TWRP.
IF you have any questions just click rom flashing basics in my signature.
Pull battery boot cold to download mode. From there attempt odin flash of factory tar image. Report back please.
Sent from my 0x1 Note 3...... I love tep
i was originally using the stock 5.0 lollipop i rooted using the method on galaxynote3root. tried re flashing but got a fail again i dont know if im using the right kernel
odin OC5 tar.
odin cfautoroot.
odin twrp.
done. easy peasy.
WOOOP WOOOOOOOP.
It worked. it took 10 tries, but it finally worked
now to root is this the right cfautoroot
CF-Root: 48 514 333
CF-Auto-Root: 29 510 246
This file: 106 225
i just dont want to mess it up again
thanks so much guys
every things good rooted and twrp installed.
Thanks again guys
Hey guys,
So I tried to root my S6 Edge and it got stuck on startup, I tried flashing back to the stock ROM, for the SMG-925F, which is the phone I have. Odin fails when flashing the rom. On my phone it says SW REV. CHECK FAIL. DEVICE: , BINARY: 2.
I would really appreciate help as I just got this phone and it is quite frustrating.
Thanks for all the great work you guys do.
Do you have a custom recovery installed?
If so, upload zipped ROM via USB (MTP or USB host) boot to recovery, flash a 5.0.1 ROM from there, flash supersu afterwards and reboot system.
If no custom recovery , you can still try Samsung KIES software and use emergency recovery,
Hey. I have fixed my issue. I extracted my stock rom to a folder, deleted hidden.img/cm.bin/modem.bin and it let me use it. Can anyone explain why this worked? Thanks
nuclearbigdaddy said:
Hey. I have fixed my issue. I extracted my stock rom to a folder, deleted hidden.img/cm.bin/modem.bin and it let me use it. Can anyone explain why this worked? Thanks
Click to expand...
Click to collapse
The reason you probalby got stuck in starting screen is because you did not unlock the bootloader from developer setting which will cause it not to boot. But for the second part I don't know why odin does this; it seems like extracting the package let's you install the things that are actually needed.
Sent from my SM-G925T using Tapatalk
I tried to root my Samsung Galaxy S6 Edge, installed TWRP & tried to install SuperSU 2.79 and it got stuck on creating image, so I rebooted my phone and it didn't boot.
At this point i could only access TWRP and Donwload mode, I got worried and decided to flash stock recovery via ODIN but I think i forgot to uncheck auto-reboot box (Don't know if this step could cause the problem but I think they are related), and I know it's trying to open recovery mode because when I flash TWRP again, some red letters appear on the top-left corner of the screen, same as when I opened TWRP custom recovery, so at the moment I can only open Download mode.
The things I've tried:
ADB reboot recovery: It won't recognise the device anymore
Flash Stock Firmware/Recovery: After sboot.bin it fails (I have the Firmware for my specific model and region)
Also, I'm new to the forums stuff so forgive me if I do something wrong
I hope someone could help me,as I've searched all over the internet and found close to nothing about this thread
Afganito said:
I tried to root my Samsung Galaxy S6 Edge, installed TWRP & tried to install SuperSU 2.79 and it got stuck on creating image, so I rebooted my phone and it didn't boot.
At this point i could only access TWRP and Donwload mode, I got worried and decided to flash stock recovery via ODIN but I think i forgot to uncheck auto-reboot box (Don't know if this step could cause the problem but I think they are related), and I know it's trying to open recovery mode because when I flash TWRP again, some red letters appear on the top-left corner of the screen, same as when I opened TWRP custom recovery, so at the moment I can only open Download mode.
The things I've tried:
ADB reboot recovery: It won't recognise the device anymore
Flash Stock Firmware/Recovery: After sboot.bin it fails (I have the Firmware for my specific model and region)
Also, I'm new to the forums stuff so forgive me if I do something wrong
I hope someone could help me,as I've searched all over the internet and found close to nothing about this thread
Click to expand...
Click to collapse
Flash stock firmware it will work.
The reason it fails at sboot.bin is because your flashing a firmware with an older bootloader than you currently have.
Flash a newer/newest firmware and it will work.
callumbr1 said:
Flash stock firmware it will work.
The reason it fails at sboot.bin is because your flashing a firmware with an older bootloader than you currently have.
Flash a newer/newest firmware and it will work.
Click to expand...
Click to collapse
I tried with Nougat 7.0, still have the same problem, it keeps failing at sboot.bin
Afganito said:
I tried with Nougat 7.0, still have the same problem, it keeps failing at sboot.bin
Click to expand...
Click to collapse
Needs to be a newer firmware with a newer BL. Your still trying to downgrade BL.
callumbr1 said:
Needs to be a newer firmware with a newer BL. Your still trying to downgrade BL.
Click to expand...
Click to collapse
When I last checked my Android versión was 7.0 and I think that was the last update the galaxy s6 had, but if you can tell me where can I get a newer firmware that would be great, also thanks for the help you have given me until now.
Afganito said:
When I last checked my Android versión was 7.0 and I think that was the last update the galaxy s6 had, but if you can tell me where can I get a newer firmware that would be great, also thanks for the help you have given me until now.
Click to expand...
Click to collapse
So the BL is like G925FXXU-S4.... G925FXXU-S5.... flash one which is higher.
https://updato.com/firmware-archive-select-model?record=FE9175C4876911E89F15FA163EE8F90B
Try this one.
Sorry for late reply