Related
Whenever I was upgrading to a Kitkat custom Rom.
I faced Boot loop issues.
I upgraded my bootloader to DN3 V5 via ODIN but still the same bootloop issue.
I thought of restarting from scratch and while i connected my note2 via odin I used PIT_N7100_16GB_20121102.pit (pit file) and N7100XXDMG1_N7100ODDDMG1_INU_Prerooted in PDA file I am stuck in
"sboot.bin nand write start failed"...
Please help...
In download mode its showing
"Product Name: GT-N7100
"Current Binary: Samsung Official
System Status: Custom
Knox Warranty Void:1
AP SWREV: A2
SW REV. Check Fail. Device:2 Binary:1
Waiting for a wayout to start using my note2
Thanks a ton in advance...
net.susovan said:
....
I thought of restarting from scratch and while i connected my note2 via odin I used PIT_N7100_16GB_20121102.pit (pit file) and N7100XXDMG1_N7100ODDDMG1_INU_Prerooted in PDA file I am stuck in
"sboot.bin nand write start failed"...
Please help...
...
Click to expand...
Click to collapse
What you are trying above MUST fail, cause downgrading is NOT possible.
Flash newest firmware instead, this is a real start from the beginning, afterwards flash a new custom recovery and you will be able to successfully run any custom rom around here.
Thanks Androidwizzard
Androidwizzard said:
What you are trying above MUST fail, cause downgrading is NOT possible.
Flash newest firmware instead, this is a real start from the beginning, afterwards flash a new custom recovery and you will be able to successfully run any custom rom around here.
Click to expand...
Click to collapse
I am dowloading N7100XXUFND3_N7100ODDFND2_INU.zip from SAM mobile.Will flash it with ODIN.Keeping my finger crossed :angel:
Please let me know if NEED to flash the same Pit file as mentioned above?
Sorry for being a lot Noob
net.susovan said:
I am dowloading N7100XXUFND3_N7100ODDFND2_INU.zip from SAM mobile.Will flash it with ODIN.Keeping my finger crossed :angel:
Please let me know if NEED to flash the same Pit file as mentioned above?
Sorry for being a lot Noob
Click to expand...
Click to collapse
You will flash original firmware for your region, so no need for PIT, just flash firmware tab PDA/AP
And it worked like a charm
Bingo.....:good:
After updating my bootloader to NE2 using odin, by phone just keeps and booting up to the Samsung Galaxy logo and restarting. The logo appears for a second or so before restarting. I can access download mode, but receive the following:
ODIN MODE
PRODUCT NAME: GT-N7100
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
AP SWREV: A2
RPMB: INVALID RPMB DATA
( the last three lines have appeared, and were not there previously before updating the bootloader). The phone was working fine with stock 4.4.2, before installing the bootloader. I cannot access recovery mode, and have flashed TWRP with odin (reported success in odin), but cannot access the TWRP recovery menu on my phone. I have tried to flash stock 4.4.2 again with odin, I do not receive any errors and receive a success 1 in odin where a blue bar is visible (when flashing) on the screen of my phone. But after the phone restarts, i experience the same bootloop problem. Help would be greatly appreciated.
Open Odin, uncheck everything, flash latest stock ROM from sammobile (https://www.sammobile.com/firmwares/database/GT-N7100/), you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
audit13 said:
Open Odin, uncheck everything, flash latest stock ROM from sammobile, you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
Click to expand...
Click to collapse
Before proceeding, I'd like to ask:
1 - I have a motherboard that I've obtained from China. Would it be ok for me to flash as you've recommended with this motherboard, taking into account the "RPMB: INVALID RPMB DATA" message that appears in download mode ?
2 - Can I install any of the latest firmwares available on sammobile for my galaxy note 2 ?
3 - Would I be able to install TWRP and custom roms after ?
Thanks
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
audit13 said:
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
Click to expand...
Click to collapse
After flashing the N7100XXUFOC2 firmware with all boxes unchecked in odin, i still receive a bootloop, and the phone is not entering recovery :-/. The messages that appear in download mode have remained unchanged.
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
audit13 said:
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
Click to expand...
Click to collapse
Yes it flashes with no errors. When turning the phone on, the samsung galaxy note 2 logo appears for just under a second, and the phone restarts and repeats until i remove the battery. Nothing happens when I try to enter the recovery menu, the same behaviour is observed (phone restarting constantly after showing SGnote2 logo). I have been reading around, and i suspect (just a guess, not sure) that the "RPMB: INVALID RPMB DATA" message that I observe in download mode may have something to do with this.
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
audit13 said:
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
Click to expand...
Click to collapse
Is there anything else that i could try ? I used an app to check the bootloader version when it was working on stock 4.4.2, and it stated that it was at LJ7. After updating the bootloader to NE1, I've experienced this problem. Would it be possible to revert back to the previous bootloader ( and would this help ?). I've flashed custom roms with no problems, beforehand using TWRP.
How did you update the bootloader? Did you update the bootlaoder without updating anything else?
audit13 said:
How did you update the bootloader?
Click to expand...
Click to collapse
I downloaded the NE1 bootloader from a user here who has a list of bootloaders on his profile (user: Androidwizzard), and flashed it using Odin v3.09 with the default boxes checked. I did not update anything else ( just clicked the "BL" field and selected the bootloader, then flashed).
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
audit13 said:
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
Click to expand...
Click to collapse
Yeah. Would it be possible to revert the bootloader back to what it was previously ? Also, is there anything else that you may suggest that i could do ? I'm still not sure what is causing this issue exactly. It seems strange that I can flash all files with no errors using Odin. By flashing a later firmware, is the bootloader automatically updated ? ( if yes, then I'm not sure why the app stated that my bootloader version was at LJ7, given that I've flashed stock 4.4.2 with odin beforehand.)
Do you have a link for the bootloader?
Did the phone work properly before flashing the new NE1 bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
audit13 said:
Do you have a link for the bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
Click to expand...
Click to collapse
I have not tried flashing the latest rom ( I could try, if that may help). I can not provide the direct link to the bootloader, since i will have to produce 10 posts ( new user here lol ). You can find the bootloader by searching google: [bootloader/modem/rom][tw kitkat][4.4.2][pf1 + pc1 + oe1 + od4 + nl1 +], then going to Androidwizzard second post.
The phone was working great before flashing the NE1 bootloader. As mentioned previously, I've flashed the N7100XXUFOC2 firmware resulting in no change.
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
audit13 said:
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
Click to expand...
Click to collapse
I will give it a go right now. Would you be able to guide me to where I could obtain the appropriate pit file for the phone ? The firmwares with PF1 have (orange) carrier. Would this affect things ?
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
audit13 said:
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
Click to expand...
Click to collapse
16 GB model. Alright, I'll try to flash the latest rom.
OK I have officially screwed up...
So it was all going smoothly flashing a tweaked custom rom and twrp successfully and then I decided to back to stock...
I accidentally (ok maybe not so accidentally) flipped the OEM unlock switch and now I am locked out of my phone since I still had the custom binary on the phone.
I tried to flash the latest stock firmware for the s9 BTU found from samfirm but odin seemed to have not liked the firmware or something and it gave me an a red message on the odin mode screen.
When I try to flash everything at once I get "REV Failed Check (Bootloader)"
When I try to flash just AP I get "REV Failed Check (Kernel)"
At the moment when I boot up I get the message telling me to use emergency software recovery but Smart Switch does not seem to recognise the device either in the emergency recovery page however it does try to connect on the home page.
I'm not too sure what to do, any help would be nice?
Thank you
You cannot downgrade the bootloader, check which version your phone has in Download mode (BL: xx) and check which version the firmware you are flashing has G960FXXU1BRF8
*Detection* said:
You cannot downgrade the bootloader, check which version your phone has in Download mode (BL: xx) and check which version the firmware you are flashing has G960FXXU1BRF8
Click to expand...
Click to collapse
OK I think I have found the BL version from the line that says...
"RP SWREV B:2 K:2 S:2"
But what firmware has the BL Version 2? They all seem to have a BL version of 1 from what you've said?
If there are no firmware which match this, what do I do? Is my phone redundant?
Delks123 said:
OK I think I have found the BL version from the line that says...
"RP SWREV B:2 K:2 S:2"
But what firmware has the BL Version 2? They all seem to have a BL version of 1 from what you've said?
If there are no firmware which match this, what do I do? Is my phone redundant?
Click to expand...
Click to collapse
OK
I saw on another thread that was replied to about the Hong Kong version having been already upgraded to BL 2 so I am going to give flashing that a go and I will report back.
Delks123 said:
OK
I saw on another thread that was replied to about the Hong Kong version having been already upgraded to BL 2 so I am going to give flashing that a go and I will report back.
Click to expand...
Click to collapse
Yea you'll either have to do something like that, or wait for your region firmware to have it's BL updated
Tried it out with a BL2 BTU firmware from SamMobile and the flash went smoothly however now I'm stuck in a bootloop when I'm trying to boot up.
I know this could be anything but I can't get any form of logs as the only mode I have is Odin mode available to me...
The way I flashed it was by doing BL first followed by AP, CP then CSC separately with auto reboot and one other one checked that was instructed by SamMobile. I tried to do them together but I keep getting an error of not being able to read a line.
What should my next step be?
What could be the reason for this bootloop as according to Odin the flash went well?
Thanks in advance
Delks123 said:
Tried it out with a BL2 BTU firmware from SamMobile and the flash went smoothly however now I'm stuck in a bootloop when I'm trying to boot up.
I know this could be anything but I can't get any form of logs as the only mode I have is Odin mode available to me...
The way I flashed it was by doing BL first followed by AP, CP then CSC separately with auto reboot and one other one checked that was instructed by SamMobile. I tried to do them together but I keep getting an error of not being able to read a line.
What should my next step be?
What could be the reason for this bootloop as according to Odin the flash went well?
Thanks in advance
Click to expand...
Click to collapse
You might need to check "Repartition" in ODIN only, flash all 4 parts at the same time, use CSC and not HOME_CSC
Make sure you are using ODIN 3.13.1
Oh yea forgot the update...
I got it working, I think I unchecked repartition and auto reboot whilst flashing all of them together to get it working
So yea this is now solved
So i have a samsung s9 SM-G960F/DS version. i had have run TWRP on it and magisk + exposed and it worked fine. i had to uninstall exposed to log into some apps and then i would reinstall it agian. but when i ran the exposed unintaller the phone would not boot. i tryed diffrent things and it would not boot unless it had the exposed intalled on it. i did a complete wipe of the phone with TWRP and now i can´t install stock rom. i downloaded the latest stock ROM for my model and the latest odin that can handle the lz4 compression. bur when i but in BL AP CP CSC it just get stuck on system.img all the time. i there is simply nothing i have not tryed. and nothing works for me. The only think working is if i flash the TWRP then i can boot into recovery TWRP. thats it. i am at a point where i will pay anyone who can help me figure this out cause i almost lost all hope for this to work agian. So i really really hope someone here have an ide to what could work for me. every tip and trick i will test and if someone offer help via discord or somthing i would also be glad to hear from you.
Hi
Extract and flash bootload.img or hidden.img file from the main stock rom.
I'll check the actual file name for you when I get home later. Did experience that problem sometime back on my s6 edge.
Usually there is a small error message on the screen of the s9 if odin fails or stalls. It's small blue text, I have a feeling it's either 'magic string error' or 'SYSTEM not [Sec]' or close to it. I find this happens when flashing the wrong firmware for that model. Example, flashing G960N firmware for a G960F.
I just did a reflash and here are my exact steps for my G960F.
1. Download Odin 3.13.1
2. Make sure Samsung Drivers are installed
3. Grab the latest firmware for your device, my device is a G960F so I just picked the latest BRJ3 firmware with November patch from Updato. Just get the firmware for your exact model.
4. Extract the files from the ZIP file
5. Add all the correct BL, AP, CP and CSC files to odin.
6. Select nand erase
7. Boot S9 into download mode
8. Flash to phone.
Don't try to flash TWRP before installing the full firmwares and until the phone is setup.
If all fails, and because you seem to be able to install TWRP, then you can download TGP Kernel ROM and flash that. It is based on stock G960F firmware, has a nice aroma installer for selecting various things and tweaks. It also provides a clean install of Magisk if that's something you like.
Also be sure to flash no-DM Verify.
Make sure you're not trying to downgrade the bootloader, I'm sick of writing out the same guide each time and I just did it earlier today so shouldn't be hard to find
*Detection* said:
Make sure you're not trying to downgrade the bootloader, I'm sick of writing out the same guide each time and I just did it earlier today so shouldn't be hard to find
Click to expand...
Click to collapse
thanks for the replies. the issue is fixed and the problem was the i last my "magic string" but a friendly person on the forum sent me the things needed to restore it and then restore to prerelease rom so i could upgrade to latest rom agian.
zalik20 said:
thanks for the replies. the issue is fixed and the problem was the i last my "magic string" but a friendly person on the forum sent me the things needed to restore it and then restore to prerelease rom so i could upgrade to latest rom agian.
Click to expand...
Click to collapse
Why not ot share those items to help others in the forum.
nsnobel2 said:
Why not ot share those items to help others in the forum.
Click to expand...
Click to collapse
You should look for samfirm or frija tool . Those would help you get latest firmware for your phone. Download it , flash it with odin and everything should be fine. Just remember that its possible that as you would be on latest firmware, you might not be able to downgrade in future.
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Am i doomed?
cheen11 said:
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Click to expand...
Click to collapse
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
Shouldn’t be a big deal unless there’s something Carrier specific required by your phone. Just make sure you don’t lock your bootloader again while using custom binaries or you might soft brick your device again. To bypass the camera lock you can use a SafetyNet fix module for Magisk which will spoof the bootloader status to the camera HAL
cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
You can try also the NEE for Nordic Countries...
BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
cheen11 said:
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
Click to expand...
Click to collapse
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
Ah, once choosing all the files it worked, thanks a bunch
BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
cheen11 said:
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
Click to expand...
Click to collapse
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
BlackMesa123 said:
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
Click to expand...
Click to collapse
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
cheen11 said:
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
Click to expand...
Click to collapse
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
BlackMesa123 said:
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
Click to expand...
Click to collapse
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
cheen11 said:
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
Click to expand...
Click to collapse
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
BlackMesa123 said:
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
Click to expand...
Click to collapse
Oh yeah good catch, i renamed the folder and didnt consider that it might not be updated it odin. It finally worked, thanks again for the help very much appreciated
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
cheen11 said:
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
Click to expand...
Click to collapse
As mentioned in the TWRP thread guide, you must format your data partition in TWRP in order to be able to boot back in the OS.