I had 4.4.4 and flashed cf-auto-root trltrespr-smn910p. It said successful and auto rebooted into a bootloop. I tried downloading the twrp-2.8.7.0-trltespr.img.tar with odin3_v3.10.6 and no twrp. I unchecked autoboot, un plugged usb, battery for 10 seconds still nothing. Another problem is i lost the screenshot of the device info. Ive searched and triedwhat i could find but im at my whits end.
Try the NK2 stock tar. Backup internal sdcard (if you can) and wipe everything but extsdcard.
What you describe sounds like your bootloader is one of those that can't be downgraded. Have you ever been on Lollipop? {If so, you won't succeed getting it back to KitKat unless it never updated past OB7. In that case, you would have to Odin or KIES update to stock OG5. And root would only possible with kernel exploit on Beastmode kernel.}
Sent from my SM-N910P using Tapatalk
Ugh, Ok I downloaded the firmware file OG5 from sam mobile and it fails? Ive tried
N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5_HOME.tar.md5
N910PVPU1ANK2_N910PSPT1ANK2_N910PVPU1ANK2_HOME.tar.md5
twrp-2.8.7.0-trltespr.img.tar
I just moved and Im using a 3g connection in the evenings until we can find an internet company that works out in the country so this is really frustrating.
Im lost on what to try next? Any other suggestions???
A week has past; are you restoring a nandroid from TWRP recovery and booting that?
If so, what is your bootloader? Use galaxy tools or save your TWRP log to sdcard and read it; the bootloader is near the bottom.
Reasons for OG5 tar failing could be that the tar wasn't extracted or you don't have a stock kernel installed. Try that or describe your current setup regarding bootloader and kernel.
Have you tried to update through KIES?
What Odin or KIES failures are you getting?
Sent from my SM-N910P using Tapatalk
Sorry, I have 3 other company phones so Ive been using one of those. We just moved ourselves and my irrigation and landscape company, still no home internet. Life is tough right now between work and 3 kids with all their activites. I had responded but I see it didn't go through so if you will let me start again and maybe we can get this brick working.
I use odin3 v3.10.6. Ive tried to use the cfauto flash and it will not stick. Ive tried to download the stock tars above and they don't work. I cant get to a custom boot with everything Ive tried. I cant find more than the above tars to download to the phone. When I go into download mode the phone says
Odin mode (high speed)
product name:sm-n910p
current binary: Custom
System Status: official
Reactivation lock: off
knox warranty void: 0x1 (4)
qualcom secureboot: enable (csb)
rp swrev: s1, t3, r1, a4, p1
secure download : enable
udc start
so what should I try now? Im begging for mercy on this thing...
And I don't get fails, Odin says all threads succeeded 1 / 0 fail
Not sure I follow without a text of Odin and version you're flashing.
Had a guy in the forum last week that could get Odin to flash but phone kept boot looping and TWRP wouldn't flash a zip. Finally flashed CWM but still looped. I believe what he finally did was Odin flash stock tar with no auto reboot, factory reset in recovery (may have been Philz CWM), flashed Odin stock tar with auto reboot enabled. Pull battery for thirty seconds prior to stock tar flash.
Sent from my SM-N910P using Tapatalk
Related
hello, I bought this i747 in its current condition. I know nothing about its history.
when I power it on it goes to the phone, !, comp screen saying firmware upgrade encounter an issue, select recovery mode in kies.
in the top corner it says:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BITS: 0
BOOTLOADER RP SWREV: 2
Now when I connect to kies and run emergency firmware everything loads on kies, then gives an error, and
underneath BOOTLOADER RP SWREV: 2 it says: SW REV CHECK FAIL: Fused 2 > Binary 0 in red.
If this phone fixable? Any help would be appreciated.
mtsosie said:
hello, I bought this i747 in its current condition. I know nothing about its history.
when I power it on it goes to the phone, !, comp screen saying firmware upgrade encounter an issue, select recovery mode in kies.
in the top corner it says:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BITS: 0
BOOTLOADER RP SWREV: 2
Now when I connect to kies and run emergency firmware everything loads on kies, then gives an error, and
underneath BOOTLOADER RP SWREV: 2 it says: SW REV CHECK FAIL: Fused 2 > Binary 0 in red.
If this phone fixable? Any help would be appreciated.
Click to expand...
Click to collapse
Did you say it was recognized in Kies but firmware recovery failed? If so, and you were using Kies (not Kies 3), we may assume the last system update was not older than Android 4.1.1. I'll suggest you try these steps (in that order),i.e. if one doesn't work, try the next step ..
1. Try booting into recovery mode and doing a hard wipe/reset
2. Download the correct stock image from the thread below and flash via Odin. If you need help with flashing via Odin, please let me know
http://forum.xda-developers.com/showthread.php?t=1739426 or visit Sammobile.com to download the correct stock image.
3. Open Kies. Do not connect the phone yet. Go to Tools => Firmware Upgrade and Initialization. Enter your phone model name (SGH-I747)=>OK and serial number. Check device information inside the battery compartment. Wait for firmware download to complete and you are prompted to connect the phone and follow the rest of the on-screen instructions.
4. Contact the vendor to find out what they did wrong and see what refund options you have
Ok, so I also wasn't able to get into recovery.
I decided to flash cwm via odin. After it flashed the phone rebooted and turned on normally. I have turned it on and off like 5 times and everytime it boots normal.....But, there is still a problem... baseband version is Unknown and there is no IMEI Number.
Larry2999 said:
Did you say it was recognized in Kies but firmware recovery failed? If so, and you were using Kies (not Kies 3), we may assume the last system update was not older than Android 4.1.1. I'll suggest you try these steps (in that order),i.e. if one doesn't work, try the next step ..
1. Try booting into recovery mode and doing a hard wipe/reset
2. Download the correct stock image from the thread below and flash via Odin. If you need help with flashing via Odin, please let me know
http://forum.xda-developers.com/showthread.php?t=1739426 or visit Sammobile.com to download the correct stock image.
3. Open Kies. Do not connect the phone yet. Go to Tools => Firmware Upgrade and Initialization. Enter your phone model name (SGH-I747)=>OK and serial number. Check device information inside the battery compartment. Wait for firmware download to complete and you are prompted to connect the phone and follow the rest of the on-screen instructions.
4. Contact the vendor to find out what they did wrong and see what refund options you have
Click to expand...
Click to collapse
hi, yes those were the steps I tried and the result was fail. Now that I can boot it, it shows its 4.3 but no baseband and no imei.
mtsosie said:
hi, yes those were the steps I tried and the result was fail. Now that I can boot it, it shows its 4.3 but no baseband and no imei.
Click to expand...
Click to collapse
Oh, it's 4.3. Perhaps even better because you may be able to flash the 4.3 restore image. Your baseband/modem is corrupt or missing which is why it's showing the no baseband message.
Please see the thread below for the complete 4.3 stock restore image. Download the stock restore image and flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=2658486
Or you may just flash the 4.3 JB modem via custom recovery since you have custom recovery working. The modem zip can be found here ...
http://www.androidfilehost.com/?fid=23212708291681456
Larry2999 said:
Oh, it's 4.3. Perhaps even better because you may be able to flash the 4.3 restore image. Your baseband/modem is corrupt or missing which is why it's showing the no baseband message.
Please see the thread below for the complete 4.3 stock restore image. Download the stock restore image and flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=2658486
Or you may just flash the 4.3 JB modem via custom recovery since you have custom recovery working. The modem zip can be found here ...
http://www.androidfilehost.com/?fid=23212708291681456
Click to expand...
Click to collapse
:good: right on. you rock man. I flashed the modem and it works great now. thanks again.
mtsosie said:
:good: right on. you rock man. I flashed the modem and it works great now. thanks again.
Click to expand...
Click to collapse
You are most welcome. Glad to know it's now working.
hey guys am in trouble
Odin Refuse to flash
I747 warranty bit :1
bootloader rp swrev 2
SW rev check fail fused 2
Phone stuck on kies firmware upgrade encounterd
I Cant get 4.3 back again or downgrade to any older version
plz help me :'(
here is two screen shot in download mode while odin error
and in normal mode when i try 2 open
dark_darkness said:
hey guys am in trouble
Odin Refuse to flash
I747 warranty bit :1
bootloader rp swrev 2
SW rev check fail fused 2
Phone stuck on kies firmware upgrade encounterd
I Cant get 4.3 back again or downgrade to any older version
plz help me :'(
here is two screen shot in download mode while odin error
and in normal mode when i try 2 open
Click to expand...
Click to collapse
Can you try flashing custom recovery via Odin and then using custom recovery to do a stock restore to 4.3 following the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
can u share a link?
Larry2999 said:
Can you try flashing custom recovery via Odin and then using custom recovery to do a stock restore to 4.3 following the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
i've tried many custom roms
start flashing will and end with bug error at the end coz of warranty
can u share me a link for firmware tested ?
dark_darkness said:
i've tried many custom roms
start flashing will and end with bug error at the end coz of warranty
can u share me a link for firmware tested ?
Click to expand...
Click to collapse
I suggested custom recovery and not custom ROM. The idea is to get your phone back in working order first. Flashing a complete stock restore image should do it. Please refer to the thread I forwarded earlier. You should be able to flash custom recovery (like CWM or TWRP) to your phone via Odin and then use the custom recovery to flash the stock restore image.
I was flashing some Roms because i was trying to do the mod where the internal memory is switched with external, i was trying to find a rom that supported this. I flashed deadly venom, it runs on android 4.3 i believe, which required a modem and bootloader to be flashed for data and WiFi to work. After seeing it didn't work with the mod, I restored from a backup in TWRP. Everything seemed fine but now when I check my phone sometimes it says there's no connection. The signal bars have an x at times, it lasts like two minutes. I'm running CM 10.1.3. Before rooting I think my phone had android 4.1.1. Can I flash the original modem and bootloader, if so where can I find it? Also would it brick my phone if I tried?
Sent from my SM-P600 using XDA Free mobile app
Your phone is an AT&T s3 (i747) with a the 4.3 MJB bootloader? If it is, you cannot flash a stock 4.3 ROM via Odin unless the ROM as specifically compiled for flashing within Odin. Trying to flash any ROM older than 4.3 in Odin could brick your phone.
To confirm you bootloader, boot into download mode and let us know what it says on the download screen.
Is your phone showing the correct imei?
This is what it says in download mode:
ODIN MODE
PRODUCT NAME: SGH-i747
CUSTOM BINARY DOWNLOAD: YES (7 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Also I tried flashing Roms in TWRP and it says Failed
Sent from my SM-P600 using XDA Free mobile app
Okay, it looks like you do not have the 4.3 bootloader which is good.
If you have the AT&T s3 i747, yYou can use Odin to flash a stock AT&T ROM onto your phone while will restore it to the factory settings and software.
Download the stock 4.1.1 AT&T ROM from here: http://www.sammobile.com/firmwares/3/?download=9080
Download and install the latest s3 drivers. Download Odin 3.07.
Launch Odin, boot the phone into download mode, connect the phone to computer, click on PDA, select the AT&T firmware you downloaded, click Okay. It will take a few minutes for Odin to check the file. The only items that should be checked in Odin is F.Reset Time, nothing else. Flash the phone. When you see Reset in the status window, remove the USB cable, remove the battery, replace the battery, boot into recovery, wipe data and cache, reboot the phone.
This method has worked me for without any issues. As with an procedure involving a firmware flash, there is always a chance that phone may become hard or soft bricked. Make sure you are prepared for such emergencies.
OK, if it does get bricked are there solutions to bring it back? Also after this if it goes well can I just reroot and restore from backup? Thanks a bunch for the help
Sent from my SM-P600 using XDA Free mobile app
Since you don't have the 4.3 bootloader, the flashing process is very straightforward.
What backup do you want to restore?
If you restore to stock 4.1.1, I recommend using Odin to install the latest version of Philz Touch which will allow you to root in recovery mode, copy a custom Kit Kat ROM to your external SD card, and flash it.
I am trying to unroot and restore stock ROM so that I can sell my Note 2014 10.1.
I am using ODIN 3.09 and P600UEUCNK1_P600XARCNK1_HOME.tar.md5
ODIN keeps giving me a FAIL. Looks like "Cant Open Serial Port". I have attached a screen shot from ODIN.
Any ideas as to what I can do here?
Thanks
You need to extract the zip file, and edit .md5 off the end, leaving a .tar file to flash. Make sure you unroot via superuser, then factory reset, then download mode.....Will take 7-9 minutes. Wait for reboot, and removed to show in ODIN. Just did this myself, and device shows official, and recovery is stock, without even the Knox splash showing recovery bit! Easy breezy. I flashed on top of 4.4.4 bootloader the 4.4.2 .tar, and let it update OTA. T-Mobile P607-T Gluck!
Worked like a charm my friend...Thanks so much
Sent from my SM-N900P using Tapatalk
I followed these steps. Flashed same tar file, and successful install. Although i cant update software because says my version has been modified. Anyway to still get updates and be totally stock?
Flash updates from Kies instead OTA is never going to work again.
Sent from my SM-P600 using XDA Free mobile app
Please could anyone had the steps ... the same issue is faced with Note 10.1 Gt-8000
I' m using N8000XXUDNF2_N8000OJVDNF3_N8000XXUDNF1_HOME.tar with ODIN 3.07 which is detecting the com 3 or com 6 with it, and failing always and the device is stopped at either ODIN MODE if I used the volume down plus power or at Firmware upgrade encountered an issue. please select recovery mode in kies and try again... it would never enter to the recovery mode or Bootloader, please advise... thanks in advanced.
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
need someone to send the right firmware for my device
attached the error i get
thanks
And here we go again...... What version software was installed before trying to update? Were you rooted?
zjor2000 said:
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
thanks
Click to expand...
Click to collapse
Try Flashing CF Auto Root through Odin and reboot your phone and report back please.
w7excursion said:
And here we go again...... What version software was installed before trying to update? Were you rooted?
Click to expand...
Click to collapse
Lol, ikr....
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
zjor2000 said:
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
Click to expand...
Click to collapse
Were you on the OG5 OTA and tried to root your phone?
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Flash whatever firmware u was on in odin
zjor2000 said:
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Click to expand...
Click to collapse
In Odin, Flash the TWRP recovery
Download notarized,cm12 or sacs and put it on your SD card, and reboot to recovery and install your choice of Rom downloaded.
Reboot and relax.
tried to do thru sd card ,but i get :
dm-verity verification failed
can i just go back to 5.1 lollipop with an official stock rom via odin ?
zjor2000 said:
can i just go back to 5.1 lollipop with an official stock rom via odin ?
Click to expand...
Click to collapse
There is no official rom
any firmware can get me back to lollipop with odin !!!
zjor2000 said:
any firmware can get me back to lollipop with odin !!!
Click to expand...
Click to collapse
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OG5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing stock OB7 ROM, parts of stock tar with Odin with a flash result that won't boot but connecting KIES in recovery and using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
samep said:
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OF5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing parts of stock tar with Odin and connecting KIES using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
xxSTARBUCKSxx said:
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
Click to expand...
Click to collapse
I think your suggestion is consistent with what we're learning as you gave it. It seems to be evolving with trial and error. The CWM suggestion came from a single experience shared.
http://forum.xda-developers.com/showthread.php?p=62196189
The OP was asking for another solution and it wasn't clear where he started from to correctly recovery so tried to answer including all the options for each build. I added some things that may help depending on his situation.
Sent from my SM-N910P using Tapatalk
i managed to find the right fW ,,,if anyone has same problem u can do it your self
https://1fichier.com/dir/IOjXgJUa
and download this file : N910PVPU3BOF5_SPT3BOF5_SPR_Sprint_USA_5.0.1.zip
Ok I dont know the fancy terms so please bear with me as I explain what I did.
I wanted to root my note 4 I downloaded odin v 3.07 and followed the "easy" online steps.
so it did its thing odin said pass then the phone started resetting this just looped and looped. so I tried and tried again and no success . I factory wiped the phone and still nothing, I fear I bricked this thing can someone help me I feel like a complete idiot. Thanks
From the top, what update version were you rooting? What did you Odin?
If you're on a recent update OE1 and up, the bootloaders have a reactivation lock that keeps you from successfully downgrading. Even the OG5 bootloader will prevent going back a single update from what I've read. You should be using Odin 3.10.7 or latest using the OEM unlock in option tab. The ROM itself may be locked to reactivation in Settings/Security. You should also enable developer mode and make sure USB debugging is enabled.
Also, OG5 stock kernel blocks typical root methods. You need the exploited kernel for that plus SuperSU zip. Technically, you'd only need custom recovery flashed in Odin then flash either the zips or pre-rooted ROM with the kernel and SuperSU included in flash.
There's even a guide posted for that:
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Sent from my SM-N910P using Tapatalk
samep said:
From the top, what update version were you rooting? What did you Odin?
If you're on a recent update OE1 and up, the bootloaders have a reactivation lock that keeps you from successfully downgrading. Even the OG5 bootloader will prevent going back a single update from what I've read. You should be using Odin 3.10.7 or latest using the OEM unlock in option tab. The ROM itself may be locked to reactivation in Settings/Security. You should also enable developer mode and make sure USB debugging is enabled.
Also, OG5 stock kernel blocks typical root methods. You need the rooted kernel for that plus SuperSU zip. Technically, you'd only need custom recovery flashed in Odin then flash either the zips or pre-rooted ROM with the kernel and SuperSU included in flash.
There's even a guide posted for that:
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I believe i had the latest update 5.1.1 I got the phone working again. I found the latest Md5 and used odin 10.7. I am so new to this its stupid its taken me 2 hours to fix my first mistake I basically lost everything but im ok with that. Thanks let me give this another try i was scared id be at sprint in the morning buying a new phone.