Related
I was trying to get my phone back to stock from Dman ICS stock rooted ROM, so I downloaded the stock rom from samsmobile, and tried to install it through CWM. It didnt work. Then I read in the forums that I had to do it trough Odin. Tried that, didnt work (Pit something was missing). So I searched a little more and found a post that said that I had to format data, system and cache and then flash it through Odin. After the whole formatting, tried the Odin thing and it starts writing, but then fails while writing factoryfs.img. So, I downloaded a CWM flashable version of stock ICS, and now when i go into CWM and try to flash anything it says that the signature can't be verified, if I say install anyway, the phone hangs and restarts to the "Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again". Kies doesnt recognize my phone in the recovery mode.
So, as of right now I can boot into recovery and into dowload mode (and Odin sees my phone). The problem is that I cant find a way to flash anything,
Thanks in advance to anyone who can get my out of this mess.
By installing Stock ICS kernel i removed the problem I had in CWM with the unverified signatures and the rebooting. Now Im trying to install the flashable stock rom, but so far it hangs on "installing update..." Will try to do it through Odin now...
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Thats my Oding failed log.
Will try dmans through cwm now...
Well, had to reinstall ICS stock kernel on CWM, restart, to get rid of the signature verifications problem.... Now, when I try to flash Dmans UCLJ3 I get stuck at Preparing Partitions...
Im running out of ideas here...
Anyone has a working link to the One Click Odin ICS leak file (http://forum.xda-developers.com/showthread.php?t=1831561) The one in there doesnt work...
Thanks... anyone?
Have you tried flashing via Odin with a stock firmware from SamFirmware ??
After your suggestion I went back to Odin, but this time I changed my USB port (read that somewhere), and it worked!
Awesome.
Thanks!
I Have tried everything....
I am at a loss here.
First of all, I got into a Bootloop/Soft Brick type thing.
Tried to reset using Kies and that just failed, now when I turn on my phone all I see is "Firmware Upgrade Encountered an Issue. Please select recovery mode in Kies & try again.
*hooks up phone to Kies*
*Starts Firmware Emergency Recovery*
*Sits at 0% for ever*
So then I try Odin,
I download the .tar of the stock firmware from Samsung-Updates (.) com when I flash I get a message in Odin that is "FAIL"
Here is the message in the box thing that I get:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1)
I HAVE TRIED EVERYTHING!!
Trying different USB Port
Multiple Versions of Odin
reinstalling drivers
Flashing Resurrection Rom
I EVEN TRIED RE-PARTITIONING AND NOTHING HAS WORKED!!
Please Please PLEASE Help me! I have looked everywhere and found nothing. I have been without a phone for a week now.
If you have any other suggestions, please let me know now. WHATEVER YOU HAVE TO SAY HELPS!
I will respond to every post you send
EDIT: About to try on another computer
:crying:
Do you have an i747m or i747?
If you have the i747, do you have a 4.3 bootloader on it? If you do, you cannot just flash a stock ROM via Odin. Repeated attempts to do so may brick your phone.
You can either download the necessary 4.3 Odin files from XDA or flash a custom recovery in order to flash a stock 4.3 ROM using your custom recovery.
Bootloader?
audit13 said:
Do you have an i747m or i747?
If you have the i747, do you have a 4.3 bootloader on it? If you do, you cannot just flash a stock ROM via Odin. Repeated attempts to do so may brick your phone.
You can either download the necessary 4.3 Odin files from XDA or flash a custom recovery in order to flash a stock 4.3 ROM using your custom recovery.
Click to expand...
Click to collapse
I have an I747 and I've already tried to flash a custom recovery (TWRP) But it just shows the TWRP title screen and then goes back into a bootloop.
Im kind of a noob at the Odin thing, I've only used it to root so i'm not sure what bootloader I have but I assume it's a 4.3.
Even if I do have a 4.3 Bootloader, where can I find such a ROM?
Did you try flashing Philz Touch via Odin? This is what I use on my i747m. You can flash the latest tar version from here via the PDA box in Odin: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
In Odin, do not check auto reboot, only F.Reset Time. Once you see the word Reset in the status window, remove the USB cable, pull the battery, insert the battery and boot into recovery, wipe cache, data, and Dalvik. You can copy a custom ROM (I use Validus 13) to an sd card and use Philz to flash it.
So do I download the tar.md5, if so I just tried and in Odin it says MD5 hash is invalid.
Thanks...Just one problem
Thank you so much, I made it into recovery! But just one problem, when I click Wipe data/Factory Reset the screen freezes and then it goes back into the bootloop. Could this be because I have no SIM or SD card inserted?
The freezing could be something else.
Did you try formatting the system?
I recommend doing a quick format before copying the ROM onto the SD card.
Yes, just tried formatting system (or at least what I think is formatting the system Mounts and storage>format /system) and It stiil freezes.
Do you think I could get away with not factory reset, because I was in the middle of a factory reset when the soft brick happened
BruceWayne_Batman said:
Yes, just tried formatting system (or at least what I think is formatting the system Mounts and storage>format /system) and It stiil freezes.
Do you think I could get away with not factory reset, because I was in the middle of a factory reset when the soft brick happened
Click to expand...
Click to collapse
Yes, try installing the rom without a reset. Theoretically, installing a new ROM should overwrite the existing ROM. If there are any files in the data or cache, this may prevent the ROM from fully booting.
Does Philz recognize the phone's SD card slot?
Yes it does. Flashing ROM Now:good:
I just hope it is able to flash a ROM and boot to the phone's desktop.
Perfect, It works, phone is now up and running, Thanks:good:
BruceWayne_Batman said:
Perfect, It works, phone is now up and running, Thanks:good:
Click to expand...
Click to collapse
Awesome:victory:
When you boot into download mode, what does it say on the screen? If you let me know what it says, I'll be able to tell if you have the stock 4.3 bootloader.
(This is my new account instead of BruceWayne_Batman) but yes, it does boot up to the phones desktop and is working in tip-top shape again thanks so much for the help
-#imanoob
---------- Post added at 06:09 PM ---------- Previous post was at 05:54 PM ----------
Okay here is the text in order:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: Yes (7 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECURE BOOT: ENABLE
Warranty bit: 1
BOOTLOADER AP SWREV: 2
3p1x said:
(This is my new account instead of BruceWayne_Batman) but yes, it does boot up to the phones desktop and is working in tip-top shape again thanks so much for the help
-#imanoob
---------- Post added at 06:09 PM ---------- Previous post was at 05:54 PM ----------
Okay here is the text in order:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: Yes (7 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECURE BOOT: ENABLE
Warranty bit: 1
BOOTLOADER AP SWREV: 2
Click to expand...
Click to collapse
Your phone has the 4.3 bootloader and I recommend against using Odin to flash any ROMs.
If you want to restore a 4.3 stock ROM, use a method from the ROM development section.
audit13 said:
Your phone has the 4.3 bootloader and I recommend against using Odin to flash any ROMs.
If you want to restore a 4.3 stock ROM, use a method from the ROM development section.
Click to expand...
Click to collapse
Yeah. I don't usually use Odin to flash Roms anyway. Thanks again
I am not new to rooting and flashing roms but this has really stumped me. I'm on a rooted sprint note 4. I'm running the Bonsai stock rom with TWRP recovery. I absolutely cannot factory reset or wipe or even format from recovery anymore. No matter what I do. It appears to wipe but the current rom loads back anyway. I am totally perplexed. Only thing I can think of is maybe a virus. Has gotten a hold. Any help would be most appreciated.
I'm not fully clear on what you're saying. Sound like you can get into recovery, but no of the wipe functions of TWRP are working.
Was TWRP working before? If so, than maybe something you flashed corrputed the custom recovery. I two suggestions. 1) reflash TRWP via Odin. That may fix the custom recovery, without wiping the phone. If that doesn't work, 2) Odin the stock tar file so that phone is just like when you got it, excpet knox counter tripped; this is already tripped so it's not causing anything new. Then just reflash via Odian CF-autoroot and TWRP. Something you just have to start to from step one. Hopefully, you either have a nandroid or backed up your apps via Titanium Backup.
Thanks you lovekeiiy for replying. Just to be clear I CAN get into TWRP. It appears to be working but it's not really doing anything. It runs through the scripts but it's not actually changing anything. Also when I'm am fully booted I can deleteprograms and cchange things around... Then reboot and everything comes right back like I never changed anything.
I agree. Flash recovery again, try wiping, let us know if that works.
I think I'm screwed. I downloaded the Original Stock Tar from Samsung. I first tried to reinitialize with Kies but that failed. So then I tried to ODIN the stock tar and that fails (see below). I can still use the phone...I can normal boot right back into the current rom as if nothing changed. But I cannot wipe this damn thing. Nor can I format or load a different rom! I have no idea what to do next.
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Also I can't re-flash the recovery cuz that fails too.
Might have to Odin to stock and start over. ?
No you don't understand. I can't Odin anything. When I try to flash the stock rom through Odin it fails. It's like this thing is write protected somehow. I am really at a loss here. I'm thinking of returning it to Sprint and take my chances gettig a rooted phone replaced or repaired unless someone can suggest something.
Just a thought, can you try Odin with the SD card and the Sim card removed?
Try a different PC, and good USB data cable! Can you un-root with super su? Then cf auto root Odin? Sometimes it is just the order of processes that can make it work or fail.
SS_DL.dll -->desktop
Romun yanındaki SS_DL.dll dosyasını desktop a atın
I tried to uproot with SU. It just doesn't matter what I do the rom loads right back up. It's as if nothing can be written to the system. Also I noticed when I enter recovery I am getting "recovery not seandroid enforcing".
Do you think if I take this to Sprint and ask them to factory reset they would do it? It's bizarre because something has got to be able to format this thing. Like a low level format or something.
Try going to this page, download the stock kernel zip and flash in twrp. Maybe then you can wipe is stock recovery. If that works, see if you can then flash twrp again.
http://shabbypenguin.com/?developer=Sprint_Note_4-trltespr&folder=Stock-NIE
---------- Post added at 03:04 PM ---------- Previous post was at 02:56 PM ----------
You can also go here, download twrp img file and flash with flashy in your rom. http://www.techerrata.com/browse/twrp2/trltespr
Thank you for the suggestion but Odin fails everytime. Here is the error I get on the phone: MMC: mmc_write fail It seems that the partition is write protected somehow. There must be a way to change this! I am really out of options here. Has anyone have any experience with write failures?
I didn't say to use odin in either of my suggestions. Within twrp you can flash the stock recovery and reboot recovery should bring you back to stock recovery so you can wipe and factory reset. If that doesn't work use flashy from the play store to flash twrp img within the rim.
dschachm said:
I didn't say to use odin in either of my suggestions. Within twrp you can flash the stock recovery and reboot recovery should bring you back to stock recovery so you can wipe and factory reset. If that doesn't work use flashy from the play store to flash twrp img within the rim.
Click to expand...
Click to collapse
I am sorry for misunderstanding you. It won't work from the recovery either. The reason is, that I cannot write to whatever partition needs to be written to, to delete or modify. I cannot wipe this device no matter what I have tried. When I flash an .img with Flashify or TWRP or ROM TOOLBOX or even ODIN it appears to flash but sends me right back to TWRP recovery with a message saying: recovery not seandroid enforcing. The area that I need to write to needs to be formatted or repaired but I don't know how or even what program to do this with. I cannot believe that there isn't a way to totally re-format and re-partition like a low level format. The weird thing is that I can still totally use the phone. It's just that if I re-boot it, it returns to the state it was in when the problem started. This means if I add a program or delete a program or change anything, it will all revert back to how it is now after a re-boot.
Does anybody know of a way to completely reformat?? I hope this brand new Note 4 is not toast
If you have xposed installed, go to wanam, security hacks and select disable SEandroid. After reboot try flashy to flash twrp and the see if wiping works.
dschachm said:
If you have xposed installed, go to wanam, security hacks and select disable SEandroid. After reboot try flashy to flash twrp and the see if wiping works.
Click to expand...
Click to collapse
Thanks but that doesn't work. All it does is reboot me back to my current state (without the Winam hacks). I need something to re-partition or format from outside of the OS. That's why I thought ODIN would be the answer but it too can't write. I get eMMC_write fail. How do I fix that?
You need the pit file to flash with the stock tar so it reparations the phone. Not sure there is one yet. Pm shabby and see if he can get you it.
dschachm said:
You need the pit file to flash with the stock tar so it reparations the phone. Not sure there is one yet. Pm shabby and see if he can get you it.
Click to expand...
Click to collapse
Yes. The PIT file. I bet that will re-partition it. I will try to PM him. I know there isn't PIT yet.
Um How do I find Shabby?? Is "Shabby" his username?
Hey,
I'll try to keep this short. I have an ATT GS3 i747, was running Slimkat 4.4.4, my Bootloader & baseband were "I747UCDLK3." I also had PHILZ recovery
I wanted to go back to a reliable stock image where everything didn't crash. It's late now but this is what I believe I did:
-Went to this thread and downloaded the ROM and the bootloader "Touchwiz KITKAT 4.4" (KT747-TW-KK-4.4-ATT-05-13-2014)
http://forum.xda-developers.com/showthread.php?t=2658486
-I'm not sure which I did now since it's late, but I believe I flashed the above ROM and bootloader. After this my phone could still get to Download mode but not boot. So I flashed the below STOCK Restore rom.
http://forum.xda-developers.com/showthread.php?t=2658486
-At this point it wouldn't turn on. I used Debrick image "SGH-I747U-CUEMJB3" and was able to boot into the stock recovery or download mode.
-Tried many many things, Finally found this thread:forum.xda-developers.com/showthread.php?t=2549068
-Downloaded all the files from that thread, started by flashing TWRP "openrecovery-twrp-2.6.3.0-d2att.tar"
-Now my phone boots into stock 4.3 and works fine but only boots with debrick SD card. I can still get to download mode but can't get into a recovery mode. It will say "booting to recovery" but just boots normal.
-Looks like in the process of all these mess ups I flipped the warranty counter to 1. Wasn't really planning on selling it right now anyways.
So any advice on what I should do next to get it to boot normally without the SD card in?
Current about phone shows
-Baseband: I747UCUEMJB
-Build: JSS15J.I747UCUEMJB
Maybe your version of TWRP is too outdated. Try flashing TWRP or CWM for the d2lte.
Thanks,
I have downloaded the latest one from http://teamw.in/project/twrp2/104
I'll give this a try and see what happens.
I prefer Philz on the i747m. If TWRP doesn't work, give Philz a try.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
audit13 said:
I prefer Philz on the i747m. If TWRP doesn't work, give Philz a try.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Click to expand...
Click to collapse
Yeah I had PHILZ before and really liked it but I think it kept failing to flash.. I'll redownload and try it again.
audit13 said:
I prefer Philz on the i747m. If TWRP doesn't work, give Philz a try.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Click to expand...
Click to collapse
okay I'm able to flash these without any problem but I cannot boot into recovery. It says booting to recovery... Then it goes black for a few seconds and will vibrate and boot normally. I believe it's because of the Debrick image its booting from? I still can't get it to boot without the debrick image.
Do I need to try flashing the MJB Kernel/bootloader?
Can you get phone into download mode without the SD card in the phone?
I've never had to restore a bricked phone so I'm just guessing here.
audit13 said:
Can you get phone into download mode without the SD card in the phone?
I've never had to restore a bricked phone so I'm just guessing here.
Click to expand...
Click to collapse
No :/ It doesn't even turn on without the SD card in.
With the SD card out, i can plug the phone into the computer and the red notification light will come on. If I then put the battery in and hold the power button down, the red light will eventually go off (like it's turned on) but the phone stays blank.
I can get to Download mode with the SD card in and remove the SD card though, Once the phone is on I can take the SD card out and it still works fine.
Thanks for the update. Are you flashing recovery without the SD card in the phone?
audit13 said:
Thanks for the update. Are you flashing recovery without the SD card in the phone?
Click to expand...
Click to collapse
Yeah.. The Kernel is "kernel 3.031-2024954" Is that correct? Not sure what to do lol
79TAKid said:
Yeah.. The Kernel is "kernel 3.031-2024954" Is that correct? Not sure what to do lol
Click to expand...
Click to collapse
Maybe the partitions are messed up? Since you can get into Odin, try flashing a stock recovery and see what happens.
http://forum.xda-developers.com/showthread.php?t=2789917
audit13 said:
Maybe the partitions are messed up? Since you can get into Odin, try flashing a stock recovery and see what happens.
http://forum.xda-developers.com/showthread.php?t=2789917
Click to expand...
Click to collapse
Okay so I tried flashing that w/re-partition enabled. It flashed but nothing changed... (I realized though that I still had the SD card in when I flashed)
I reflashed without the SD card (and re-partition on) but it failed .
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img.ext4
<ID:0/007> NON-HLOS.bin
<ID:0/007> recovery.img
<ID:0/007> rpm.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> system.img.ext4
<ID:0/007> __Xmit Write fail
<ID:0/007> XmitData Fail..
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Before I turned it off, I just flashed it one more time (only auto-reboot checked) and it completed, but won't boot on its own still
Where did you get the rom? I see that there was no aboot.mbn included.
audit13 said:
Where did you get the rom? I see that there was no aboot.mbn included.
Click to expand...
Click to collapse
It was from these instructions I believe.
http://forum.xda-developers.com/showpost.php?p=53574211&postcount=9
I clicked your link and saw these instructions on the same page.
In the thread you sent me, I didn't a stock recovery file I could flash with ODIN. Seemed like everything needed to be flashed with in the custom recovery that I cant get to.
Tried a different de-brick image, didn't work. Tried a 2nd one, worked but then my phone said unknown baseband and unknown IMEI (maybe wrong version?)... Trying to go back to the one I had been using and now that's not working! This phone is driving me crazy
not buttin in audit13 , but havent some people had to try different SDcards and maybe multiple times ?? (p.s. what the heck is "aboot.mbn" ?). excuse newbness please.
p.s. will google.
err on the side of kindness
mrrocketdog said:
not buttin in audit13 , but havent some people had to try different SDcards and maybe multiple times ?? (p.s. what the heck is "aboot.mbn" ?). excuse newbness please.
p.s. will google.
err on the side of kindness
Click to expand...
Click to collapse
Yeah I have 2 SD cards with me. The one that has always worked is a Sandisk 16gb class 4. I have a Samsung 16gb class 6 but it has never worked when I write a de-brick image to it.
I should probably just stop trying things because I seem to be making it worse. I will try loading the de-brick image that HAD been working great for me again but i've already tried multiple times. I had to go back to the de-brick image that messed up my IMEI again as it's the only one that works now.
I got into download mode (which looks slightly different now (doesnt show the flash counter anymore). I tried starting over and flashing the 4.3 rom through ODIN again. It failed, trying a 2nd time now. Might be failing because I took the SD card out? Was going to try flashing 4.3 and then going back to the 4.3 De-brick image before it loads. This may accomplish absolutely nothing lol, just trying to get back to where I was so my phone will have connectivity
Edit*
If any of this is making since, the 2nd reflash of stock 4.3 ROM worked fine. But I can't get it to start up with the MJB de-brick image yet.
Edit** Yeah what I did, didn't do anything.
I've borrowed another phone (An identical ATT Galaxy S3) so I have a phone for now but would still like to try fixing mine. I guess I'll do some more research unless someone has a suggestion. Unless I didn't see it, I couldn't find an ODIN flashable stock recovery the other day.
tried google ?
"all i can really do, is stay out of my own way and let the will of heaven be done"
audit13 said:
Maybe the partitions are messed up? Since you can get into Odin, try flashing a stock recovery and see what happens.
http://forum.xda-developers.com/showthread.php?t=2789917
Click to expand...
Click to collapse
I've had mroe time to mess with the phone. I've got it booting without the SD card now and can get to recovery I successfully flashed TWRP with Odin now and can get into it fine. :good:
Now I just need to figure out which rom/stock rom to load and hope I dont have to start over again
While attempting to root my galaxy note 4 I somehow managed to get caught it a boot loop when trying to revert to a rooted stock room please help
Double check the ROM you're trying to flash, if it is the correct one for your device.
Sent from my GT-I9505 using XDA Free mobile app
yilun said:
Double check the ROM you're trying to flash, if it is the correct one for your device.
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Before the boot loop odin failed on me while trying to flash N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5
LeoPRide said:
Before the boot loop odin failed on me while trying to flash N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5
Click to expand...
Click to collapse
Most likely can't flash that unlocked bootloader from a reactivation locked bootloader. What is your current bootloader? Most likely not OB7 because it's blocked to Odin.
Try to restore the last TWRP backup that ran after last update. No current backup, you need to Odin a tar. Maybe Noterized ROM will flash.
If you want to figure out which tar you can flash in Odin, Odin TWRP with no auto reboot and battery/USB pull for 30 seconds when done. Copy your TWRP log to sdcard and read it. Near the bottom it will tell your current bootloader. Flash that tar if you're stuck on boot loop.
I hope you didn't enable the reactivation lock in Settings/Security. That should be disabled prior to Odin flash. There's also an OEM unlock in Odin 3.10 series. You should use that but I'm not saying it bypasses the failure to disable reactivation lock. May have to call Sprint if that happened. It's anybody's guess if they can override that.
Sent from my SM-N910P using Tapatalk
Ive learned in the last 30 hours I have been fighting with rooting my friends 910p. I also have the note 4 910p and failed to realize he had updated to og5 (5.1.1 if I understand correctly.) Well I tried flashing the same way I did my phone using CF auto root and flashing Noterized Stable 3. Didn't even get through auto root and been looking for this boot loop fix since then. Tried flashing stock og5 and it didn't help. Also tried beastmode kernal with twrp. TWRP works fine and once out of about 35 flashes let me make it to android setup. Halfway though, it rebooted into boot loop. I've only tried Hybrid-X rom and a stock og5 .tar and it hasn't work. I'm about to try and figure out which boot loader I am working with (see previous posters statement saying "Most likely can't flash that unlocked boot loader from a reactivation locked boot loader. What is your current boot loader? Most likely not OB7 because it's blocked to Odin.") and try and match a stock file. After that ill be trying Sacs rom and what a previous poster in this page had said. Sounds like we are dealing with the same demon so I will update you if I make any progress with those ideas. Sorry for mispellings and if I dont make sense. I promised him Id have it figured out and im exhausted from up all night and then working. (side note I broke the laptop screen halfway diagnal across, because I somehow got the phone battery between the screen and keyboard hauling it home from work. If you fix your boot loop issue please post how :highfive: :fingers-crossed:
Also I left my friend the backing up process (he came to me wanting this because of mine.) and he only backed up photos, google, and contacts. I've been surfing this forum off and on for years (since my first smart phone Samsung Moment) for the knowledge you guys have that goes with my love of android. Hope to become a helpful active member.
Edit: I just seen a main difference where you failed odin and mine passes. Not sure if that matters.
store2426gm said:
Ive learned in the last 30 hours I have been fighting with rooting my friends 910p. I also have the note 4 910p and failed to realize he had updated to og5 (5.1.1 if I understand correctly.) Well I tried flashing the same way I did my phone using CF auto root and flashing Noterized Stable 3. Didn't even get through auto root and been looking for this boot loop fix since then. Tried flashing stock og5 and it didn't help. Also tried beastmode kernal with twrp. TWRP works fine and once out of about 35 flashes let me make it to android setup. Halfway though, it rebooted into boot loop. I've only tried Hybrid-X rom and a stock og5 .tar and it hasn't work. I'm about to try and figure out which boot loader I am working with (see previous posters statement saying "Most likely can't flash that unlocked boot loader from a reactivation locked boot loader. What is your current boot loader? Most likely not OB7 because it's blocked to Odin.") and try and match a stock file. After that ill be trying Sacs rom and what a previous poster in this page had said. Sounds like we are dealing with the same demon so I will update you if I make any progress with those ideas. Sorry for mispellings and if I dont make sense. I promised him Id have it figured out and im exhausted from up all night and then working. (side note I broke the laptop screen halfway diagnal across, because I somehow got the phone battery between the screen and keyboard hauling it home from work. If you fix your boot loop issue please post how :highfive: :fingers-crossed:
Also I left my friend the backing up process (he came to me wanting this because of mine.) and he only backed up photos, google, and contacts. I've been surfing this forum off and on for years (since my first smart phone Samsung Moment) for the knowledge you guys have that goes with my love of android. Hope to become a helpful active member.
Edit: I just seen a main difference where you failed odin and mine passes. Not sure if that matters.
Click to expand...
Click to collapse
First flash with CFAutoRoot will boot loop due to not using the kernel exploit and SuperSU zip (rooting stock? Just Odin of TWRP and pre-rooted Hybrid X would have been for OG5 stock).
2nd attempt with TWRP and Beastmode should have included the SuperSU zip prior to boot. But I don't think that should cause a boot loop.
If Odin isn't failing but you're getting boot loops, try installing CWM. It seems that if TWRP gets crashed on the reactivation bootloader, it no longer works to recover with a successful flash.
http://downloadandroidrom.com/file/GalaxyNote4/CWM/philz_touch_6.59.0-trlte.tar
I suspect that is the case with both phones in this thread.
Sent from my SM-N910P using Tapatalk
So flash a stock og5 file then reboot and wipe dalv and then use oden to flash cwm. After that flash a custom rom that's og5? This correct? Is there an easier way with having a non loading rom and TWRP on there now? Main thing I feel hurt this root was it was 5.1.1 and I didn't realize that.
Thank you for the fast replies!
store2426gm said:
So flash a stock og5 file then reboot and wipe dalv and then use oden to flash cwm. After that flash a custom rom that's og5? This correct? Is there an easier way with having a non loading rom and TWRP on there now? Main thing I feel hurt this root was it was 5.1.1 and I didn't realize that.
Thank you for the fast replies!
Click to expand...
Click to collapse
You can try just Odin CWM and flash the pre-rooted OG5 ROM. The ROM likely does most of the wiping for you if it's Hybrid X.
That should be enough. If not, format data partition and Odin OG5 tar and CWM then the pre-rooted ROM.
Sent from my SM-N910P using Tapatalk
It went all the way through the installer for the Hybrid 3.0 rom. After reboot it black screens with blue LED fading in and out. CWM worked amazingly!! Should I try and figure out the steps to find what boot loader its stuck on? Maybe it tried to take the 5.0.1 version and it stuck???
Progress baby, progress
store2426gm said:
It went all the way through the installer for the Hybrid 3.0 rom. After reboot it black screens with blue LED fading in and out. CWM worked amazingly!! Should I try and figure out the steps to find what boot loader its stuck on? Maybe it tried to take the 5.0.1 version and it stuck???
Progress baby, progress
Click to expand...
Click to collapse
I'm not familiar with Hybrid X 3.0 The Sprint yellow splash with blinking blue LED was common for many TW OB7 ROMs. IDK, that may been an indication it's installing the deodex ROM prior to optimizing and starting apps which would pop-up a notification screen.
Maybe let it sit 10 minutes or more and see if it updates the status? As long as the blue LED is blinking and phone doesn't vibrate and go off or loop, that may be acceptable if it actually completes the install.
Sent from my SM-N910P using Tapatalk
So while waiting on the black screen and blue led I fell asleep. still didnt work. Re downloading a good og5 tar to try and flash again. Also I am still struggling to figure out how to find which bootloader its on. Would it hurt to try flashing a 5.0.1 rom? Ill be giving him my sphone to use until I get this fixed. Hate to do that because I need my phone but it isnt his fault.
Also I have changed to odin 3.10.7 and it failed last try. It may have been my settings on odin though.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Erase...
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> carrier.img.ext4
<ID:0/004> RTN for Sprint
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
OP, is any of this helping? I dont mean to hijack your thread but figured we could work through it together. Otherwise if you like I can get my own thread going because this is a pain in the butt...... lol
store2426gm said:
So while waiting on the black screen and blue led I fell asleep. still didnt work. Re downloading a good og5 tar to try and flash again. Also I am still struggling to figure out how to find which bootloader its on. Would it hurt to try flashing a 5.0.1 rom? Ill be giving him my sphone to use until I get this fixed. Hate to do that because I need my phone but it isnt his fault.
Also I have changed to odin 3.10.7 and it failed last try. It may have been my settings on odin though.
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Erase...
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
persist.img.ext4
modem.bin
cache.img.ext4
carrier.img.ext4
RTN for Sprint
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
OP, is any of this helping? I dont mean to hijack your thread but figured we could work through it together. Otherwise if you like I can get my own thread going because this is a pain in the butt...... lol
Click to expand...
Click to collapse
Did you have the OEM unlock checked in Odin options? Was this OG5 tar?
Try to Odin the stock kernel first. Then try to recover with KIES. Odin or KIES might work after flashing the kernel, modem and recovery separately. It's risky doing it with OB7 individual Odin flashes but I believe it was done successfully on an OE1 update that crashed the reactivation locked bootloader. The gap may have been plugged on OG5.
IDK if CWM has a log like TWRP does. I can see the partitions by version in TWRP log written to sdcard.
You may also try just flashing an OG5 ROM or Noterized.
Edit: I no longer see OEM unlock in Odin 3.10.7; not sure which version had that or just bad recall; sorry for the bad info.
Sent from my SM-N910P using Tapatalk
So this is the stock file I been flashing.
ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB5691107_REV00_user_low_ship_MULTI_CERT.tar
Is that correct? I am not sure what modem or anything from before. I know it was the 5.1.1 and he updated earlier Aug. Is there a way to find out? Also I am still able to access and install twrp or cwm, use odin to flash tar files so I am not completely screwed yet. I am not used to using kies but wonder if I should get used to it quickly.
In 3.10.7 that failed (see post earlier), I had Nand erase, ??? for sprint, and f. reset time checked. The time it failed was the first time I seen a message on the phone saying to "use kies or recovery to fix a firmware issue."
Wasnt there some roms that requires it be pushed through odin?
I just tried the noterized stable 3 build (older version thats on my phone) and flashed stock tar and cwm, then tried stock tar and twrp. Never worked. Just starts spark screen then goes black with blue led slowly flashing. Also when trying to flash a rom through recovery it would start install then juat power off. Did this on 2 diff roms.
Ughhh so far away from getting this done i feel.
Somwtimes i see a message saying "skipping md5 check. No md5 file" or something along those lines.
Sent from my SM-N910P using XDA Free mobile app
store2426gm said:
Wasnt there some roms that requires it be pushed through odin?
I just tried the noterized stable 3 build (older version thats on my phone) and flashed stock tar and cwm, then tried stock tar and twrp. Never worked. Just starts spark screen then goes black with blue led slowly flashing. Also when trying to flash a rom through recovery it would start install then juat power off. Did this on 2 diff roms.
Ughhh so far away from getting this done i feel.
Somwtimes i see a message saying "skipping md5 check. No md5 file" or something along those lines.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
If developer doesn't include md5, the setting should be do not check md5 or something similar. Most do not include md5 from my experience on Note 4.
I thought you had established some success with CWM recovery. It usually works where TWRP fails.
I don't think it's necessary to flash a ROM prior to Odin of stock tar. I think I'd be wiping everything but sdcard plus data partition format or factory reset and powering down prior to Odin if it was boot looping. Did you try the stock recovery factory reset?
Sent from my SM-N910P using Tapatalk
I have done all that except the stock recovery factory reset. Trying that now. I have tried over and over variationd of using odin for stock tar then either superbeast, then a cwm or twrp, then try just that or then try to put a rom on. Twrp logs havnt helped other than seeing some "unable mount /data " just figured it was the rom due to trying to get root. Idk...
What could have possibly happened using auto root on a 5.1.1? It will sit ob spark screen for 5 min then just shut off. Other trys have gotten me to a boot loop 10 sec into booting...
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 02:00 AM ---------- Previous post was at 01:57 AM ----------
Also i have wiped everything including sd. Ive done this several ways too.
Its like it tries then half way during whatever its doing it just locks up then shuts off. Kinda like a random reboot but leads to boot loop..
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
Im re flashing stock tar now then when it goes dark during spark screen ill give it a few and batt drip. Then recovery and factory reset and let you know.
Sent from my SM-N910P using XDA Free mobile app
Anyone know how i flash these? I just need to get this phone working. Stock, rooted, doesnt matter..
Sent from my SM-N910P using XDA Free mobile app
So the latest is flashed stock tar, factory reset with recovery, then flashed stock tar again. Got all the way to optimizing apps 3 of xxx and shut off. Just powered off. Not sure why. Going to wipe dalv and reboot. May just load cwm and a rom to see what happens.
Sent from my SM-N910P using XDA Free mobile app
Here are a few pics to show what i am seeing. It made it to optimizing app 2 of 25 then just shuts off.
Sent from my SM-N910P using XDA Free mobile app
Got it! Had to format sd card twice. Then flash tar (no reboot), flash cwm and factory resets, then flash tar with reboot on this time. It is now a stock note 4 again and working. He wont let me try the 5.1.1 root method now that i know the new steps. Lol
Thanks for all the help! Hope to return the favor and pass along the info someday!
Sent from my SM-N910P using XDA Free mobile app