Bootloop - Sprint Samsung Galaxy Note5

I've tried flashing the Unknown (XAS) version of the N920PVPS3DRD1 firmware coming from the N920PVPS3DRD1 Sprint (cdma) Through odin. It got stuck on finding pit file, so I closed odin and now my device is stuck in a bootloop. It stays on samsung galaxy note 5 screen then restarts and goes to TWRP. When I go into download mode it doesn't display any information in the top left. I have a backup of the sprint version which I have tried restoring to (I haven't wiped any data in fear of losing the backup) However I have the backup on my PC too which I should be able to send to the device using ADB. This didn't work. And it is still stuck in a bootloop. Does anyone know how to solve the issue? Thanks.

Download the correct 4 file package(I like Android File Host) and reflash using Odin. Edit the Odin .ini file to unlock all of the options, and then make sure you check the boxes that say nand wipe, phone efs clear, and bootloader update. Also extract the .pit file and insert that into the pit section. If it doesn't flash fully the first time, uncheck all of the boxes, reboot Odin mode, and flash again. This almost always solves my flashing issues.

Related

[Q] Unable to get phone to boot after Odin

Hope someone has some info.
I have recently tried to recover my phone via Odin flash. I'm flashing the GummyCharged 1.9 FE odin file. I've done this SEVERAL times w/ out any problems.
My problem now is that when the Odin flash is complete it shows "Pass" and when I reboot my phone it boots with an old version of CWM (4.0.0.1). Not only that but when I try to "reboot phone" it boot loops back to CWM and will not load ANY for of an OS. I've tried multiple Odin files with no luck. Same thing over and over.
Anyone have any suggestions? I'm used to having to recover my phone from a bricked state... but never had an issue where I push a file to the phone and it will not boot after. Tried wiping data/cache after Odin as well... Still nothing.
Wrong section but flash the newest cwm or try one of the full stock odin files. Make sure you are running as admin if using vista/7. Also once in download mode put the battery back in and start the flash.
Yeah, done that. I've Odin-ed plenty of times before with no issue. Still just loops. Its just not loading an Operating System for what ever reason. I just may need to get it back to verizon to swap it out.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General

[Completed] Note 4 recovery capped

I am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0
I figured it out
planb234 said:
I am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0
Click to expand...
Click to collapse
I fianlly figured out the deal with TWRP not flashing.
The change between file systems is what TWRP won't flash.
To flash into the new, the old, or back up property check the file type.
Ext 2, Ext 4, F2FS, etc ...
To get recovery to load install from odin with auto boot disabled, remove battery, than vol + - menu and power.
the steps below..
1. Power off (complete) boot to download.
2. Load Odin, uncheck auto reboot, PDA TWRP. after it installs pull battery to exit.
3. Boot to recovery - wipe- advanced wipe -Repairor Change File System - Check System (go thruough each)
4. Repair and change each to the file type you want to flash
5. repair and or change the files for the zip you are going to flash
6. you have done all the rest before ....
Issue resolved, thread closed, thanks.

Accidentally wiped int. sd card, no pc-usb connectivity + corupted initial bootscreen

Hey all,
A few days ago I did something very stupid and wiped the internal SD card which obviously bricked my phone down to download-mode, after which I initially flashed back a stock firm file which didn't help. After a lot of freaking out I remembered I had a TWRP-backup so I recovered this and my phone booted back up with IMEI in place and in/out calling+texting working.
Only things the backup couldn't fix are
1. PC - phone connectivity through USB doesn't work at all (besides when in download mode), it just charges and doesn't give me an option to choose or switch USB-mode. When connected while in TWRP there still is no connectivity, even after enabling MTP. Most importantly, Windows device manager doesn't seem to detect anything at all when I plug or unplug my phone but interestingly enough USB-OTG is working without a hitch so I have no clue as to why regular USB won't work on any pc :x
2. The initial boot screen (The one without animation saying Samsung Galaxy S6) somehow got corrupted and shows a somewhat glitched up download-mode screen before booting into system or recovery.
Anybody able to lend a hand?
if you can get to download mode and USB connectivity works, shouldn't you be able to flash stock firmware using OIDN?
Yeah I am able to flash, I already tried that and it did not help with either of the issues :/
Interestingly enough USB-OTG is working without a hitch so I have no clue as to why regular USB won't work on any pc :x
Have you tried flashing a 4-part firmware with PIT file and Re-Partition & Nand Erase All options checked in Odin ?
iDroid27210 said:
Have you tried flashing a 4-part firmware with PIT file and Re-Partition & Nand Erase All options checked in Odin ?
Click to expand...
Click to collapse
No I have not, I'd need to hunt this 4-part firmware down first + backup everything on there
Can I just restore a twrp-backup afterwards? or might that give me troubles?
screen said:
No I have not, I'd need to hunt this 4-part firmware down first + backup everything on there
Can I just restore a twrp-backup afterwards? or might that give me troubles?
Click to expand...
Click to collapse
Flash a 4-part firmware w/ PIT + Re-Partition and Nand Erase All to be back on a healthly base, then flash TWRP and restore your backup.
You can download a 4-part firmware using the SamFirm tool (Binary Nature checked in the software).
iDroid27210 said:
Flash a 4-part firmware w/ PIT + Re-Partition and Nand Erase All to be back on a healthly base, then flash TWRP and restore your backup.
You can download a 4-part firmware using the SamFirm tool (Binary Nature checked in the software).
Click to expand...
Click to collapse
This piece of advice fixed all my problems, thank you Only thing I ran in to was which PIT file to use since g920f has OPEN, OPEN_HIDDEN100M and OPEN_HIDDEN150M .PIT available and I do not know what the difference is between these (I ended up going with the non-HIDDEN one).

Help with bootloop issues after CLEAN flash odin SM-G9200

Hello, i have the SM-G9200ZH (Hong Kong version)
I disabled some system apps through pdp and got into a bootloop, after trying many things i did a factory reset and flashed through odin this firmware which is the latest
G9200ZHU2ERK2_G9200ZZH2ERK2_G9200ZHU2ERK2_HOME.tar the phone showed the bootanimation and then restarted to itself to bootlogo, over and over again.
So then i found a Pit file, and correct AP, BL, CSC, CP files for my device G9200ZHU2EQL1_G9200ZZH2EQL1_7.0, i flashed through odin selecting Nand Reset and Re-partition too.
At this point i still have the same issue, Phone goes into the bootanimation and then restarts itself over and over again.
The only way i have made the phone boot is by installing a custom ROM with TWRP, but i cant use any because it doesnt recognize the sim while using them.
Every time i flashed a firmware, When first booting i got a blue screen on the stock recovery that goes to 32% and then fails and says erasing.
Also im not using my Original Cable
So, can someone help me to make it work again? or to Tell me which custom rom actually works for my phone.
Did you try "wide /data" right after you've flashed the stock ROM?
forumber2 said:
Did you try "wide /data" right after you've flashed the stock ROM?
Click to expand...
Click to collapse
I did wipe data right after flashing through Odin, and also tried not wiping data after flashing through Odin. None of these worked, I don't know what to do
You can try flash twrp through odin then magisk/ supersu through twrp

S7 lost /efs and with it imei on bootloader v8 - chances of repair?

I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?
pr10dr said:
I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?
Click to expand...
Click to collapse
You just need to flash the latest G930F for Germany. The firmware code is DBT, it's unbranded so no netweork provider bloatware.
I've attached Samfirm tool. It gets the latest firmware straight from samsung servers version 8.
1. Unzip
2. Run application as admin
3. Check auto box
4. SM-G930F in Model box
4. DBT in Region box
5. Check Update
6. Wait to finish
7. Flash files with Odin
8. New Phone.
I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6
Alright i think i resolved part of the issue as follows:
* i flashed the complete stock firmware as described above
* After flash was done i rebooted again into download mode and installed TWRP as recovery via odin
* I then booted into TWRP and copied the "no-verity-opt-encrypt" in the latest version to the phone
* The zip of "no-verity-opt-encrypt" i then installed with TWRP.
The phone booted up. Factory Samsung Android works but the imei is still shown as empty / unknown.
Some guides suggest to flash a factory combination image but i can not find one for bootloader version 8 which is on my phone.
pr10dr said:
I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6
Click to expand...
Click to collapse
Yes sometimes this happens, try a different firmware like United Kingdom BTU.
Does Odin say Pass?
The updating and erasing screen is normal after flash just leave it.
Once the phone boots on BTU you can either change language to German or flash DBT again.
It's worth checking / reinstalling Samsung drivers. Use different USB port. Odin should be version 13.
As long as you can boot into download mode the problem is fixable.
Thanks for your advice.
I will try the BTU firmware later. Just to check we are on the right track: If i understand you correctly you are saying the lost imei will be "fixed" by installing either the BTU or DBT stock firmware via odin?
Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.
pr10dr said:
Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.
Click to expand...
Click to collapse
OK it sounds like the BL info on the EFS is missing or corrupt.
Just try one more thing before trying to repair the EFS.
Flash firmware again with Odin but uncheck "auto reboot"
When passed in Odin disconnect phone.
Hold volume down+home+power. As soon as the screen goes back move your finger to volume up while still pressing home +power. You want to boot into system recovery. It may take a few attempts.
Once in system recovery, wipe data/factory reset and reboot phone.
Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated
pr10dr said:
Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated
Click to expand...
Click to collapse
Anyone offering money to fix or connect to a server is a scammer, stay clear.
To repair the EFS you have to get the stock firmware back on there or flash someone esle's EFS back up file. You can buy a damaged S7, install TWRP, back up the EFS to the SD card, put that sd card in your phone then restore the efs. Your phone will then take on the identity of the phone the EFS file came from. Effectively you will have a new IMEI number and mac address. As long as the donor phone is not registered on the network your phone will work fine. You cannot have two phones with the same IMEI registered on the network, both will be blocked and black listed. Obviously the donor phone must be exactly the same model as yours.
However the method below should be tried first.
The error with the text "failed to open recovery" means the phone cannot find the partition where the stock recovery file is located.
Now to solve this we can install TWRP with ODIN and that will provide a way to install the stock firmware in .zip format direct from the sd card using TWRP as the recovery method instead of the inbuilt stock recovery which cannot be found.
You should then be left with a phone which has a restored EFS with your original IMEI and other data with TWRP as the recovery tool.
Which ever method you choose TWRP must be installed first.

Categories

Resources