[Q] Unable to Flash Recovery -- Odin Fail -- please help - Sprint Galaxy S 5 Q&A, Help & Troubleshooting

Hello All,
First, I apologize for the fact that I am a long time (years) lurker and this is my first ever post. I have prior experience with rooting and installing custom roms on my samsung moment, moto droid (original), HTC droid incredible, moto droid X, samsung fascinate, samsung galaxy nexus, and samsung galaxy s4. All were successful with minimal issues. Here's my current issue...
I have had my S5 for several months and finally decided to root it. My first attempt was to leave it on the stock 4.4.4 OTA that I had and attempt to Odin CF-Auto Root. This resulted in a "FAIL" during the flash at the cache.img.ext4 phase. Subsequently I tried every version of Philz and TWRP I could find with the same failure.
Then I did an Odin of full ANK that I found on SamMobile's site. This was successful. So I tried ALL of those recoveries on top of that flash. All failed. I tried reflashing the whole tar ball in between and I tried several recoveries back to back without the tar ball in between. I tried it both ways.
Then I flashed the new NKD build that is out there. This was successful. Then I tried every single on of those recoveries (including CF-Autoroot) on top of that an all failed. In between EVERY one, I have tried flashing back the full NKD tar ball.
I even tried the packages that someone put out which include the firmware and either Philz or TWRP. I tried both. Both FAIL in the same way on Odin.
Now when I try to go back to the ANK tar ball, it hangs in a boot loop on first boot. I don't care, I don't want ANK, I am just sharing the facts. It's back on the NKD leak now.
Every flash is done on my macbook pro running windows 7 in WM ware fusion. It's always done by entering download mode from a battery pull.
I have also tried repartitioning during some of these flashes with a PIT file I downloaded. NONE of this helped. My phone runs with the NKD leak on it, but I want root and I want a custom recovery.
My goal is to have a custom recovery and full root so I can go back to flashing custom roms. Yes I have already tripped my knox counter, and no, I don't mind. Can anyone help me get this thing rooted with a custom recovery on it?
Thanks in advance!

Use heimdall for mac or find a real Windows pc if you want to use odin.

That's right, I forgot to mention, I tried Heimdall to flash just the recovery and that fails too!

Since we've had a couple new firmwares and lots of other stuff going on in the last several weeks, I've probably used Odin 30 or 40 times so I'm thinking a cable or try a different pc.

And by the way, when I run the command as follows:
heimdall flash --recovery recovery.img --cache cache.img
I get the following:
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
I HAVE tried another cable, but not another computer. No idea why it would flash full tar balls fine, but not work with just a recovery... EVER.
In terms of Odin, I should also mention that I have tried 3.07, 3.09 and 3.10. I tried to troubleshoot everything that I thought could be the culprit.

I understand that you're pc won't work with all tars & that a different pc may not be an option. If you are somehow able to flash ne5, you can follow the steps below without using computer the rest of the process to get root & custom recovery. I've done this method on 3 S5s so it's a sure thing & takes less than 5 mins after your on the ne5 bootloader.
1. flash ne5 full tar with odin
2. download towel root, install and run to gain root (Make it rain)
3. Install supersu from play store
4. Install flashify from play store, grant root access
5. Download recovery IMG (Make sure it's IMG and not tar or zip) twrp here >> http://techerrata.com/browse/twrp2/klte
6. Open flashify for root users and select recovery image, navigate to twrp or philz custom recovery you downloaded and flash within the app
7. Open supersu and follow steps to update binaries, phone will boot to recovery and complete the update then reboot automatically
8. Enjoy your rooted device and flash away!

This is awesome and worked perfectly. I had thought about trying to do something of this nature, but could not have pieced it together so flawlessly. How do I send a donation your way?
The last issue is now I am on NE5 baseband. Is there any way to get to ANK or later?

syntheticreality said:
This is awesome and worked perfectly. I had thought about trying to do something of this nature, but could not have pieced it together so flawlessly. How do I send a donation your way?
The last issue is now I am on NE5 baseband. Is there any way to get to ANK or later?
Click to expand...
Click to collapse
I'm no dev so I don't have a donation link set up. I do have a PayPal account I'll pm to you. I'm glad I was able to help get you up and running, I know what it's like. I have a Mac myself and no pc but was always afraid to try running a vm. Good to know that it's an option now

Sounds good. I figure I ought to buy to you a beer for the help!

I like beer ?

Glad you solved you problem. Its shows like you was downloading from rwilco12 site. All are bad.
Also if you want to try Philz, these is the real link.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/klte/
Sent from my SM-G900P

Related

[Q] GT2 7.0 Wont Take CWM

Seems like there are more and more people coming out having trouble geting into cwm on their device - I'm one of them...but there's a thread in the general QA that I think would get more attention and feedback here.
http://forum.xda-developers.com/showthread.php?p=27585693#post27585693
No idea how to move it...but in a nutshell I and others are odining the cwm package but still only get the factory recovery when we try to boot into cwm.
Any ideas?
Take a look here.
http://rootzwiki.com/topic/24762-stopping-recovery-overwrite/
I'm familiar with Heimdall - but I thought the bootloader had to be a bin file?
If someone had or could write a quick step-by-step on that, what version Heimdall, etc...I'd give it a go. I've been in Heimdall (newest version) connected to the unit and wasn't exactly sure which options to use...I hate to guess when messing with bootloaders.
Thanks Stranxk - it was the locked bootloader.
Steps I took that worked:
1. Download and launched Heimdall 1.85
2. Downloaded the appropriate unlocked bootloader from the links in the above post
3. Using Heimdall I exported my PIT directly from my device and used that in the flash tab
4. Select "add" and "Kernel" - and flashed the unlocked bootloader
5. Re-flashed CWM using ODIN
Went right into clockworkmod - running Tab2Lite beta3 right now...
Works great - Thanks!

Twrp boot loop

This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
lonoguge said:
This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
Click to expand...
Click to collapse
Where did you get twrp?
lonoguge said:
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
Click to expand...
Click to collapse
What is "another rom"?
lonoguge said:
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
Click to expand...
Click to collapse
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
bhundven said:
Where did you get twrp?
What is "another rom"?
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
Click to expand...
Click to collapse
I got it from what I thought was the official XDA TWRP thread but I'm not sure if it was official or not
at first I tried reinstalling codename but now I'm trying Beam (Tuk edition) and it seems to be working
TWRP Major Boot Loop
hey guys, im new here and i desperately need help with my phone!
the other day i was flashing a rom on my samsung galaxy s 4g. Things were turning out fine, until i had some complications on my phone.. so, i removed the rom. when i rebooted my phone, it went directly into the team win recovery project boot loop and every time i try to reboot my phone, it goes into the twrp. I also can't wipe anything and i can't delete anything! Does anybody know how I can solve this or is my phone basically bricked
more details would be helpful..
As in what rom, or what kernel.... etc... and make sure you have the corret phone.
Same problem with t959p
Looks like I'm not alone.......here's my story
the other day I wanted to switch from a stock rom to a custom, so I flashed redux 1.3 which was actually a froyo rom, and it started draining my batt like crazy so I flashed another rom on top of the froyo rom not realizing what I was doing and somehow messed it up cuz now it will only boot into recovery.
Now just to be clear I know this was my fault, I know I should have odin'd back to stock first, but I wasn't thinking at the time.....Ohh and just so you know I've flashed this sucker hundreds of times and was always able to get out of any mess I got in.
So here is the situation as it stands now, 3 button combo to enter download does not work. I can only get it into download with the jig I made. the problem is even in download mode none of my pc's will detect the device as a Samsung composite device, so odin will not see it. I've installed every possible 32 n 64 bit driver I could find including reinstalling kies. Kies wont even see it. I've tried flashing a few roms that I know worked and still it just boots into recovery. Now one thing I'll tell you is that depending on which rom I flash I can get recovery to switch from cwm to twrp. right now I left it with cwm 6.x.
what I need is a cwm flashable stock telus t959p rom complete with bootloaders or at the very least a cwm flashable zip file containing the bootloaders to see if I can recover the phone.
ohh and if your thinking about telling me to google search for the answer then don't bother.......I've spent the last 4 days reading posts and going to different websites and repositories trying to find something that would help me and so far nothing has.
the only thing that might work as a last resort is pushing the bootloaders as per one of raver's or whitehawks posts but it's a little more complicated for me as I would have to set up a laptop with Linux as I don't think i'll be able to pull it off with any of my windows pc's, win7 and win 8 only.
so if anyone has the files I need or can make them please let me know....or if you think you have another solution I could try i'm all ears err eyes.
thanks
Jedi
Have you tried heimdall one-clicks? Maybe it's showing up as gadget or something like that. I've had luck using zadig and heimdall to bring it back from the brink of death.
http://forum.xda-developers.com/showthread.php?t=1358498
EDIT
Woops replied to the wrong thread .
Nothing to see here, move along
Would like to revive a slightly dead thread.
I upgraded to a Galaxy S3 and no longer use my SGS4G for daily use. I had AOKP and disliked it, FC's and didn't like the feel. I have been trying to install a new rom ( old rom, VH Black Ed. ). Every time It loads into TWRP I have the ability to select the zip, install, it says complete, but reboots right back to TWRP menu. I've tried flashing CWM and it will install, flash the rom, reboot, and right back to this TWRP B.S... what am I doing wrong? I want to continue to use this SGS4g for music and internet duties.
How can I install CWM and have it stay even after a reboot? This TWRP is starting to me off
Did you happen to one click to stock before you went ham at the recovery?
Sent from my SGH-T959V using Tapatalk 4

[Q] Odin3: checkboxes are disabled

Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
HoPi` said:
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
Click to expand...
Click to collapse
Download a clean copy of Odin and install .
Auto Reboot is normal .
Root and Recovery TWRP
http://forum.xda-developers.com/showthread.php?t=1851548
Root and Recovery CWM
http://forum.xda-developers.com/showthread.php?t=1831173
jje
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet. But since this is getting off topic, I might be better off asking in other threads.
Thanks anyway!
HoPi` said:
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet.
Click to expand...
Click to collapse
Then you are not understanding instructions .
What is your intention .
Root or flash a stock rom .
Root via either method i posted .
Stock rom direct flash tar file via Odin.
ODIN flash is a tar not a zip.
Custom rom via a rooted phone with recovery zip file from ext sd card or sd card .
jje
Come on, the instructions are pretty clear boot in Odin Mode, click a button in Odin, let it restart, finished. The SuperSU zip file is from another guide, where the tar-file didn't include it. So I tried to manually install it via CWM (I think it was 6.0.2.7 or 8), but that didn't work either. Whenever the device reboots, Root Checker Basic runs for a few minutes and says "Sorry, the device does not have proper root access". If it helps, I used this guide:
http://www.android-hilfe.de/root-cu...ly-root-fuer-anfaenger-n8000-n8010-n8020.html
Even though it's in german, the screenshots are pretty obvious.
Sorry never ever seen any method with those sort of instructions.Personally not a clue what they mean .
I have used two methods as posted to root note 4 or 5 times. Rooted standard Samsung phones with cwm and root hundreds of times without any of those instructions.
Even run one standard cwm root via Odin to allow a specific rom install followed by a reroot using TWRP this afternoon .
jje
Sent from my GT-N8010 using xda premium
Thanks to Darkman, I finally got it. The problem was the current firmware update from Samsung. I reflashed with the version from January, followed his tutorial (like I did before - wow, after doing this 3-4 times, it certainly becomes second nature), and BAM, the device is rooted. Thanks anyway JJegan

[Q] Unrooting problem

So i did something stupid right after rooting my Relay. I deleted basic stock files that are necessary for the phone to function properly. I was able to copy them from my current phone (rooted T-Mobile G2/Desire Z) onto an SD card and in turn push them back onto my Relay. My problem is that I still get error messages constantly after boot up and the simplest tasks can take hours (not to mention I can't use phone, contacts, messaging). I have seen all over the web (and XDA) about unrooting the phone and retuning it to stock. I was thinking that I could unroot, then reroot my Relay and that will solve my problem.
I was all set to unroot when I encountered yet another issue. Samsung-updates.com and sammobile both direct you to download the firmware files from hotfile. Hotfile has been shut down due to copyright infringement. Where I can find the stock firmware files now that hotfile has been shut down?
Please help me as I anxiously await using my new phone without the extra bloatware!
Thank you,
RockinRita
RockinRita said:
I was all set to unroot when I encountered yet another issue. Samsung-updates.com and sammobile both direct you to download the firmware files from hotfile. Hotfile has been shut down due to copyright infringement. Where I can find the stock firmware files now that hotfile has been shut down?
Click to expand...
Click to collapse
Would Samsung's Kies software be able to restore it to stock, or is it too far gone for Kies to work?
Bobby Tables said:
Would Samsung's Kies software be able to restore it to stock, or is it too far gone for Kies to work?
Click to expand...
Click to collapse
Without the stock files wouldn't Kies be pointless?
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Pushing on a Relay
RockinRita said:
So i did something stupid right after rooting my Relay. I deleted basic stock files that are necessary for the phone to function properly. I was able to copy them from my current phone (rooted T-Mobile G2/Desire Z) onto an SD card and in turn push them back onto my Relay.
Click to expand...
Click to collapse
I did a very similar thing to my Relay and I can only get it boot off of the SD card. I am curious how you performed the push. I assumed that you
used adb push, but how?
Thanks,
Lou
scopedial said:
I did a very similar thing to my Relay and I can only get it boot off of the SD card. I am curious how you performed the push. I assumed that you used adb push, but how?
Thanks,
Lou
Click to expand...
Click to collapse
I copied the files from my rooted HTC Desire Z/ T-Mobile G2 to a spare SD card I have and then I inserted that card into my Relay and started it up. It took me a few hours to get passed all the error messages that constantly pop up. And then I went into my files, external SD and moved the files over to the system folder on the Relay. After several reboots, the error messages still are coming up which I why I need to unroot it and reroot it.
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
You may have just saved me, Magamo! Thank you for saving them to Drive! Once I get on my old slow Dell laptop (i'm on my Chromebook now- which unfortunately doesn't support most things) I'll try to flash your files and update you here since I cannot comment on your post as I have not posted enough myself.
Stock ROM Restore Method I Used
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
furboom1240 said:
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
Click to expand...
Click to collapse
I'll be honest, you've got me on this one. I've never used ODIN, and am not well versed in its use. But yes, this is sounds like a more technical way of doing it without the CWM flashables I've mentioned. -- Impossible in some situations. For example, my fiancee's phone's USB port has died for all purposes other than charging, So if I'm to send it in for a warranty repair, I'll have to use the method I posted.
Confused here
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
Magamo,
I'm sorry, but I'm still totally confused here. Not sure how to flash the files in. I downloaded Kies and both of the zip files from your post. Successfully updated the firmware and my error messages are gone, but I don't have CWM on it. I extracted your files, but now what? I'm not very technologically inclined so this is all Greek to me.
furboom1240 said:
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
Click to expand...
Click to collapse
furboom,
What is T699UVBMC5_HOME? How do I get the md5 sum of it? How do I use CWM to format /system? How do I get to stock restore? Again, I'm sorry for asking so many questions, i just have no clue what I'm doing here.
Thanks,
Rockin Rita
RockinRita said:
Magamo,
I'm sorry, but I'm still totally confused here. Not sure how to flash the files in. I downloaded Kies and both of the zip files from your post. Successfully updated the firmware and my error messages are gone, but I don't have CWM on it. I extracted your files, but now what? I'm not very technologically inclined so this is all Greek to me.
furboom,
What is T699UVBMC5_HOME? How do I get the md5 sum of it? How do I use CWM to format /system? How do I get to stock restore? Again, I'm sorry for asking so many questions, i just have no clue what I'm doing here.
Thanks,
Rockin Rita
Click to expand...
Click to collapse
If you don't have CWM, or some other custom recovery running on this, how did you get root in the first place? The easiest way to get root is to use heimdall or ODIN to flash CWM or another custom recovery, then flash Superuser or SuperSU using your new custom recovery.
The .zip files I linked are only meant to be flashed through recovery. Not Kies, not ODIN, not any other method.
Got it!!
With the help of this site (http://www.celldekho.com/how-to-unroot-samsung-galaxy-s-relay-4g/) and the file it linked to on rapidshare, along with your tip Magamo, I was able to unroot my Relay successfully. I'll reroot it later when I have the time and make sure not to delete important files LOL Thanks so much for the help!

Soft Bricked Note 5 SM-N920W8 - Please Help Recover

Hey everyone, so I have from what I researched here is a "soft" bricked phone as my recovery mode (TWRP) and download mode works fine but no boot.
First let me say this is the Canadian version of the Note 5 SM-N920W8. I posted here because there is no forum for that version everything seems to be the same and posted under 920T version.
HISTORY OF THE PHONE:
It was a while ago that I rooted but let me describe to the best of my memory how my note 5 ended up in the state that it is in. So stock was lollipop 5.1.1. I flashed the skyhigh kernel which gave root access but had random reeboot issues which led me to flashing TWRP recovery so I could flash boot.img as an image file which did take away the random reeboot problem and removed that red error on startup "kernel is not SEANDROID enforcing". Life was good at this point! Everything worked great woth no issues. I greenified everything and underclocked the cpu with system tuner and used system app removed to manually all the bloatware as I didnt want to start using custom roms I stuck with the stock firmware. Part of the reason that I didnt want to use custom roms is because I started reading up on xposed framework, so I decided to flash it and give it a try. I read the xposed framework thread followed the download link to my version downloaded it and flashed with TWRP. Immediately after this was a bootloop.
TROUBLESHOOTING:
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Im not sure what to do here I have a completely blank phone but twrp and download mode works so it recoverable right?
I read up on adb sideloader but didn't get too far.. is that worth trying for recovery in this case?
I also read a few threads on here for other samsung versions where they say to flash a PIT file with odin but they all say that it only works specifically for that phone and I couldn't find one for this version of the note 5.
I know the #1 rule here is to research before posting and Ive really made my best attempt to research on here and Google over the last few days but I really need my phone back. Any help is greatly appreciated.
re: phone won't boot
bloewen4 said:
Hey everyone, so I have from what I researched here is a "soft" bricked phone as my recovery mode (TWRP) and download mode works fine but no boot.
First let me say this is the Canadian version of the Note 5 SM-N920W8. I posted here because there is no forum for that version everything seems to be the same and posted under 920T version.
HISTORY OF THE PHONE:
It was a while ago that I rooted but let me describe to the best of my memory how my note 5 ended up in the state that it is in. So stock was lollipop 5.1.1. I flashed the skyhigh kernel which gave root access but had random reeboot issues which led me to flashing TWRP recovery so I could flash boot.img as an image file which did take away the random reeboot problem and removed that red error on startup "kernel is not SEANDROID enforcing". Life was good at this point! Everything worked great woth no issues. I greenified everything and underclocked the cpu with system tuner and used system app removed to manually all the bloatware as I didnt want to start using custom roms I stuck with the stock firmware. Part of the reason that I didnt want to use custom roms is because I started reading up on xposed framework, so I decided to flash it and give it a try. I read the xposed framework thread followed the download link to my version downloaded it and flashed with TWRP. Immediately after this was a bootloop.
TROUBLESHOOTING:
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Im not sure what to do here I have a completely blank phone but twrp and download mode works so it recoverable right?
I read up on adb sideloader but didn't get too far.. is that worth trying for recovery in this case?
I also read a few threads on here for other samsung versions where they say to flash a PIT file with odin but they all say that it only works specifically for that phone and I couldn't find one for this version of the note 5.
I know the #1 rule here is to research before posting and Ive really made my best attempt to research on here and Google over the last few days but I really need my phone back. Any help is greatly appreciated.
Click to expand...
Click to collapse
If you have either a custom or stock rom installed or the official Samsung firmware installed
then it should be an easy fix, you must have flashed a incompatible kernel or perhaps you
deleted the kerned. (the phone will not boot without a kernel)
You need to find a compatible kernel and flash it using twrp recovery.
Here is a link you may want to try, it's for kernels for the Note 5 only:
http://forum.xda-developers.com/tmobile-galaxy-note5/orig-development
It might even be better if you were to Odin flash a fresh copy of your Note 5 specific
firmware using download mode, that's the surest way to get your phone working again.
Give it a try...
Good luck,
Have a great day!
Good luck!
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Click to expand...
Click to collapse
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again
Click to expand...
Click to collapse
re: not sure what you mean
bloewen4 said:
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
Click to expand...
Click to collapse
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
or flashing firmware is the same process in odin. Use the AP slot.
And now I know what messed up your phone... it was as I posted before either
flashing the wrong kernel or the kernel got deleted who knows how.
That's all I can tell you except if you want the link to the official Samsung
N920T firmware here it is:
http://forum.xda-developers.com/tmo...t/rom-android-6-0-marshmallow-note-5-t3250812
The link also guides you thru the odin flashing process and other important things.
Good luck!
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
Click to expand...
Click to collapse
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Click to expand...
Click to collapse
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
bloewen4 said:
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
Click to expand...
Click to collapse
Wait. You have a W8 variant. Odin won't flash a T variant on your W8 device, I don't believe. You need to download your carrier specific, hopefully 6.0.1 version, of the firmware for your specific carrier version, and flash that in the latest 3.10.7 version of odin.
---------- Post added at 09:21 PM ---------- Previous post was at 09:08 PM ----------
bloewen4 said:
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
Click to expand...
Click to collapse
What carrier are you on? Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom, there's a fix in the note 5 gen section for making t/w8 devices work with call audio on intl roms and there's some stock Deodexed stuff at this point and certainly tekhd's mm rom...so from there the choices are yours...but your device is fine you just NEED to flash the correct stock firmware for your variant and use the latest version of odin with a factory usb cable and latest usb drivers from Samsung on your pc when you do it...you'll find links to all this stuff in most of the guides that are abundantly available...
Wait. You have a W8 variant. Odin won't flash a T variant on your W8 device, I don't believe. You need to download your carrier specific, hopefully 6.0.1 version, of the firmware for your specific carrier version, and flash that in the latest 3.10.7 version of odin.
Click to expand...
Click to collapse
I realize I have a W8 and hes providing the firmware for a T. I rooted with a kernel that was for a T version and everything worked fine. I researched rooting note 5 SM-N920W8 and they said do everything the same for the T version because theyre basically identical and isnt much info on the w8 version. So far Ive had no issues flashing everything designed for the T version on my W8. Actually Ive only tried flashing stock w8 firmware from.sammobile.com and got a fail in odin so now Ill try the version MisterJunkie provided me with for the T version unless considering all this you think I should still try a different firmware all together for the W8?
Misterjunky said:
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
or flashing firmware is the same process in odin. Use the AP slot.
And now I know what messed up your phone... it was as I posted before either
flashing the wrong kernel or the kernel got deleted who knows how.
That's all I can tell you except if you want the link to the official Samsung
N920T firmware here it is:
http://forum.xda-developers.com/tmo...t/rom-android-6-0-marshmallow-note-5-t3250812
The link also guides you thru the odin flashing process and other important things.
Good luck!
Click to expand...
Click to collapse
Bud, that's not the official tmo pd1 firmware, and I'm not sure if the leaked (alright it would likely run) would be the best here...plus he scares me when he says he cleared EVERYTHING cuz I'm thinking back to exactly how much twrp will wipe, but it's a lot so I fear he's going to need some partitions restored that are only going to come from a full pit file mapping...I don't believe official pd1 would flash in odin, nor would I recommend doing so- I would locate the most recently official firmware to ensure all partitions are restored, then if he doesn't have official mm support he can look into the leak, but if he had official for his variant and carrier that's his best bet to ensure 100% fix and give him a solid foundation to start from if he wants to root, rom, mod, etc
Not to discount your advice, I'd just hate to see him in a worse place than he is...which he's not even bricked YET...but he's starts screwing with wiping efs or messaging with csc stuff from different variants and he could back himself into a corner...
What carrier are you on? Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom, there's a fix in the note 5 gen section for making t/w8 devices work with call audio on intl roms and there's some stock Deodexed stuff at this point and certainly tekhd's mm rom...so from there the choices are yours...but your device is fine you just NEED to flash the correct stock firmware for your variant and use the latest version of odin with a factory usb cable and latest usb drivers from Samsung on your pc when you do it...you'll find links to all this stuff in most of the guides that are abundantly available...
Click to expand...
Click to collapse
My carrier is Rogers. I did goto sammobile.com already and downloaded and flashed what I thought was the current stock firmware for my 920w8, but I flashed without wiping all data as previously stated. Maybe doing this will allow my firmware to flash? Will try when Im home from work. Will also post the link from sammobile.com for the exact firmware I download just to verify ots the right one.
Yeah I literally wiped everything I checked all the boxes and I remember having to manually type y e s to proceed so yeah pretty serious wipe lol.
I have the latest version of odin 3.10.7 and tried installing drivers on my pc said theyre already installed.
When I connect my phone to usb in download mode it says com:4
I thought also that just flashing the stock firmware would be the solution since I get download mode and twrp I just have a blank phone but as I said I did get the stock firmware from sammobile.com and try but it failed. Maybe I grabbed the wrong one but it looked pretty straightforward. Maybe with MM coming out Wednesday for rogers note 5 Im downloading the wrong version.
Im worried like you wrote earlier that I deleted too much with twrp if I needing mapping partitions and PIT files I will need some serious help that stuff is beyond me.
Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom
Click to expand...
Click to collapse
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Do you think I need to remap partitions as you said earlier? Getting PIT files? Im lost here... appreciate any help
Still with a blank phone, any ideas?
Or if anyone could direct me to another thread that might be useful for re mapping partitions?
Have you tried flashing twrp again in Odin?
I hit too many buttons before when wiping. It even erased my recovery.
Once I had recovery again I could Odin flash the official firmware.
Could try Philz recovery as well.
Sent from my SM-N920T using XDA-Developers mobile app
Yeah I did try that heres the link where I got the firmware and yeah twrp is on there.
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Click to expand...
Click to collapse
bloewen4 said:
Yeah I did try that heres the link where I got the firmware and yeah twrp is on there.
Click to expand...
Click to collapse
Since you have twrp on the phone.. Tap to create a backup even if there's no system on it so that you can at least make it create the folder.. Try using adb to push a ROM and kernel to the phone so you can use twrp to flash it. If you can get into the phones storage using Windows then just drop a ROM and kernel for your device in the folder and then use twrp to flash.
By the way.. Use the SkyHigh kernel.
Follow the directions to a T!!
http://forum.xda-developers.com/note5/orig-development/kernel-skyhigh-tw-6-0-1-kernel-t3321646
If you can get into the phones storage using Windows then just drop a ROM and kernel for your device in the folder and then use twrp to flash.
Click to expand...
Click to collapse
I did try immediately to connect with Windows to my phone so I could try flashing stock firmware with twrp but its currently not allowing me access to view storage on Windows though it does connect with odin saying com:6.
Since you have twrp on the phone.. Tap to create a backup even if there's no system on it so that you can at least make it create the folder..
Click to expand...
Click to collapse
I will do this as soon as I am home from work. Will this perhaps allow access with Windows and/or adb sideloader?
Try using adb to push a ROM and kernel to the phone so you can use twrp to flash it.
Click to expand...
Click to collapse
I will be researching how to do this. Have you any threads to learn adb? So basically this will allow me to put ROMS or other files into the internal memory?
By the way.. Use the SkyHigh kernel.
Follow the directions to a T!!
http://forum.xda-developers.com/note...ernel-t3321646
Click to expand...
Click to collapse
Is this the right kernel for SM-N920W8?
* SAME kernel for ALL supported variant !!
** If other party cannot hear voice when on speaker phone ** Then read Post #636
SM-N920 C / CD / G / i [ v3.2 ]
SM-N9200_HK [ v3.2 ]
Click to expand...
Click to collapse
Also Marshmellow isnt out officially for SM-N920W8 so Ill need a kernel for lollipop 5.1.1 unless you suggest to wait for marshmellow then try a mm kernel?
Thanks for helping!
How about this adb sideloader does anyone think that will work to load the firmware? If so any good threads to guode me?
What did you end up doing? I have a similar problem except no recovery mode, just download mode for Odin.
bloewen4 said:
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Do you think I need to remap partitions as you said earlier? Getting PIT files? Im lost here... appreciate any help
Click to expand...
Click to collapse
Where did you get your firmware from?
Why oh why did I bother reading through this entire thread, with intentions to help OP. Lol I didnt realize the date till the last post.

Categories

Resources