Post Chainfire Root Issues 5.1.1 - Sprint Samsung Galaxy S6

I attempted to root my phone using the Chainfire Auto-root method today and somehow managed to use the 925p edge MD5 file instead of 920p. This caused a few issues, the X-axis was inverted, no service, and a continual automatic reboot after about 30-60 seconds of the phone being on. In an attempt to fix it, I have tried a few things. in many combinations. I have reflashed the stock tar file, cleared cache, factory reset, and flashed the PIT file found in post 12 of this thread http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325/page3. Unfortunately all attempts have been for fruitless. Obviously the first issue to be tackled is the constant rebooting. Any help would be appreciated.

Maybe flashing unikernel will help, it can be found here: https://www.androidfilehost.com/?fid=24269982087012055
Just flash it in Odin, if that does not work you may want to try bringing it to where you bought it for warranty.

No luck, unfortunately.

offthatwall said:
No luck, unfortunately.
Click to expand...
Click to collapse
Idk, @koop1955 any suggestions?

1619415 said:
Idk, @koop1955 any suggestions?
Click to expand...
Click to collapse
Posted this in the other thread: http://forum.xda-developers.com/showpost.php?p=64735692&postcount=19
That is all that I have for you.

offthatwall said:
I attempted to root my phone using the Chainfire Auto-root method today and somehow managed to use the 925p edge MD5 file instead of 920p. This caused a few issues, the X-axis was inverted, no service, and a continual automatic reboot after about 30-60 seconds of the phone being on. In an attempt to fix it, I have tried a few things. in many combinations. I have reflashed the stock tar file, cleared cache, factory reset, and flashed the PIT file found in post 12 of this thread http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325/page3. Unfortunately all attempts have been for fruitless. Obviously the first issue to be tackled is the constant rebooting. Any help would be appreciated.
Click to expand...
Click to collapse
Koop's stock firmware didn't fix mine for some reason either...heres the stock version that fixed mine
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Hope it helps!

x1xmadex1x said:
Koop's stock firmware didn't fix mine for some reason either...heres the stock version that fixed mine
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Hope it helps!
Click to expand...
Click to collapse
The firmware posted above is OJ7, which seems to be an earlier version than the OL1 firmware. I have no idea why OJ7 would work for you when OL1 wouldn't. (Unless you got a bad download of OL1, which is why I recommend checking MD5.)
If you are still on OJ7, can you try system update and see if that takes you to OL1?

koop1955 said:
The firmware posted above is OJ7, which seems to be an earlier version than the OL1 firmware. I have no idea why OJ7 would work for you when OL1 wouldn't. (Unless you got a bad download of OL1, which is why I recommend checking MD5.)
If you are still on OJ7, can you try system update and see if that takes you to OL1?
Click to expand...
Click to collapse
I have already re-rooted my device and installed twrp...it wont let me install a system update due to custom and not official...Also I downloaded the OL1 three occasions..and MD5 passed

x1xmadex1x said:
I have already re-rooted my device and installed twrp...it wont let me install a system update due to custom and not official...Also I downloaded the OL1 three occasions..and MD5 passed[/Q
Im have the constant reboot now. Im gonna try another pb6 6.0.1 tar file only one ive tried was the sprint worker one said revo in in it. That didnt not fix my constant rebooting issue. So far any rom even after odin stock still rebooting every 2 minutes.
Click to expand...
Click to collapse

will get that logcat
Saafir said:
Note the time and grab a logcat.
Ok i left the phone at home but i did look at the log cat about the first ten lines all had emmc in them im not quite sure. Well I cant read it lol. when i get home il flash twrp and restore a back up let reboot a few times get a log cat and post it will twrps log cat work? If im lucky i might get a app installed to do it. I no longer got adb and fastboot on my computer but will download if needed.
im waiting for a replacement to get to the sprint store. i flashed stock and took it in rebooting sprint guy tried factory resetting it and clearing cache which got it stuck in the pre load starting or optimizing apps before itd finish it it would reboot and if i kept going id beable get to start up settings thats it. now i can flash twrp still it does restores my back ups and after that itl boot the system i can uninstall or install something or what not maybe 1 min after im able to get into it it reboot. only wifi connects though.
Again i had about all roms we got on sprint forum on that phone worked awesome loved it til the time i restored the efs on 6.0.1 with a twrp thats a unofficial build modded to work on 920p.
Click to expand...
Click to collapse

Sounds good thanks man.

Seems as maybe a somewhat common issue unfortunately thats happening for s6 as well as sprint note 5 as there are a few threads regarding the same issue. Theres a thread for s6 on this issue and on 2nd page appears as if someone found a fix having something to do with letting it die completely etc.. http://forum.xda-developers.com/sprint-galaxy-s6/help/constant-rebooting-t3287213

I figured my rebooting issue was corrupted data becausr i was transferring from phone to pc to phone and no md5 check. Though now i will use it. Good luck

Related

[Q] primoc cdma kernel crash (all kernels)

RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
Original post:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
wendall911 said:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
Try stock kernel if that crashes then custom rom
Sent from my One V using xda app-developers app
cybervibin said:
Try stock kernel if that crashes then custom rom
Click to expand...
Click to collapse
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.
wendall911 said:
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.
Click to expand...
Click to collapse
Does it happen like this?
http://www.youtube.com/watch?v=IIqT-xd0AqU&feature=youtu.be
I have the same issue man. It's bizarre.
patbushnell said:
Does it happen like this?
I have the same issue man. It's bizarre.
Click to expand...
Click to collapse
Yes, this is the same behaviour. I'm not sure if you're able to dump the dmsg stuff from adb, but certainly same crash. Typically the phone network status shows a little x, right before the reboot. But the lagginess starts happening when the 5 second kernel reboot is issued.
I've tried to change to airplane mode, disable sdcard and everything else I can think of, still crashing and I'm not able to make much of the logging info
When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain
aaronrw said:
When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain
Click to expand...
Click to collapse
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
You will surely get the RUU to make your phone working perfectly. That's what I did.
patbushnell said:
You will surely get the RUU to make your phone working perfectly. That's what I did.
Click to expand...
Click to collapse
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!
I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
wendall911 said:
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!
Click to expand...
Click to collapse
So are you able to run any other roms without reboots? Or are you only on stock?
MasterTec said:
I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
So are you able to run any other roms without reboots? Or are you only on stock?
Click to expand...
Click to collapse
I applied the OTA update. Only the stock kernel (after update) will boot now. Any non-stock kernel crashes - always seems the last line is rmt_storage, which the IPC to shared memory of the boot loader I believe.
Noob question
wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
Can you link me to a working RUU?
i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...
jetfactor said:
i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...
Click to expand...
Click to collapse
Yes it's possible that you got one with the update already on it however the problem you are having is completely different than the problem we're describing in this thread and could be caused by many other things - not necessarily the OTA update.
Seems a bit off topic for this thread...
More of the rebooting problem
I have 2 phones one with this problem, the other without it. My friend got one of these phones after i installed jelly bean on mine. He had it long enough to have updated the firmware using the stock image. I made a backup of the stock image, but it seems to have been corrupted (zero byte .zip file). I need to get the phone working (stock or updated, at this point there is no preference so long as it works)
In the bootloader, the radio version of the crashing one is:
1.00.00.0928
The working one is:
1.00.00.0521_2
As far I can tell, this is the only difference. I Used the same SD card and the same procedure for wipe/installing the OS with the same files.
Have you found a solution to this? If so, can you point me to the downloads/instructions for how to fix it?
Looking for help
wendall911 said:
RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!
madhephaestus said:
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!
Click to expand...
Click to collapse
hey can i please know how to fix the radio on my phone i have the same problem, my phone will boot and turn on but after 10 seconds in turns off again and boots again? can i please get help ?

[Q] I think I may have jacked my phone up

I had previously tried to root my phone and decided to flash it back to factory. I downloaded last nights OTA 4.3 update and after it installed, now my ATT S3 SGHi1747 gets stuck at the ATT logo AFTER the Samsung logo appears then disappears. My pc is no longer recognizing the device nor do I know how to get in there to at least get it up and running to try and flash it back to factory THEN download 4.3.
Any suggestions on how to get this fixed would be appreciated!
'Sider said:
I had previously tried to root my phone and decided to flash it back to factory. I downloaded last nights OTA 4.3 update and after it installed, now my ATT S3 SGHi1747 gets stuck at the ATT logo AFTER the Samsung logo appears then disappears. My pc is no longer recognizing the device nor do I know how to get in there to at least get it up and running to try and flash it back to factory THEN download 4.3.
Any suggestions on how to get this fixed would be appreciated!
Click to expand...
Click to collapse
ODIN back to stock.
Question
Did you try using ODIN or did you find a factory ROM to flash?
'Sider said:
I had previously tried to root my phone and decided to flash it back to factory. I downloaded last nights OTA 4.3 update and after it installed, now my ATT S3 SGHi1747 gets stuck at the ATT logo AFTER the Samsung logo appears then disappears. My pc is no longer recognizing the device nor do I know how to get in there to at least get it up and running to try and flash it back to factory THEN download 4.3.
Any suggestions on how to get this fixed would be appreciated!
Click to expand...
Click to collapse
Try booting into recovery and factory resetting, this usually fixes this problem.
polobunny said:
ODIN back to stock.
Click to expand...
Click to collapse
Downloaded ODIN, still a little fuzzy on how to operate it
Cadle said:
Did you try using ODIN or did you find a factory ROM to flash?
Click to expand...
Click to collapse
Im not too tech savvy obviously lol, can you point me in the direction of a factory ROM
dntesinfrno said:
Try booting into recovery and factory resetting, this usually fixes this problem.
Click to expand...
Click to collapse
Tried this twice, no luck.
Im assuming once I get this thing flashed back, I can download that app that will reset the counter?
'Sider said:
Downloaded ODIN, still a little fuzzy on how to operate it
Click to expand...
Click to collapse
If you google for "odin flash rom" there's lot of good tutorials out there, many on this forum alone. As for stock, i'm not sure where to find it since I flashed custom the day after I got my phone and never looked back...can't stand stock touchwiz. You could also try flashing any custom ROM you happen to have layin around...worth a shot until you find a custom one. I use BeanStalk ROM, which has 4.3 and 4.4 versions out now.
Best of luck to ya!
goombah88 said:
If you google for "odin flash rom" there's lot of good tutorials out there, many on this forum alone. As for stock, i'm not sure where to find it since I flashed custom the day after I got my phone and never looked back...can't stand stock touchwiz. You could also try flashing any custom ROM you happen to have layin around...worth a shot until you find a custom one. I use BeanStalk ROM, which has 4.3 and 4.4 versions out now.
Best of luck to ya!
Click to expand...
Click to collapse
I suggest here that everyone here read some of the other threads here on XDA, and see all the problems people are having flashing and rooting after taking this latest 4.3 OTA before advising the next person on how to make ANOTHER paper weight.
As for Sider,
You might be out of luck here, as there is no official 4.3 firmware yet available to flash back to stock, and also AT&T has done something with the new software update, where trying to downgrade it back to a previous version is going to either fail or brick phones.
Also, I haven't read yet where anyone has been successful flashing a custom recovery to fix any issues, but the posts are going up so fast right now that I might have easily missed it.
Edit: OK, someone was able to get TWRP installed, but is also having issues with root.
polobunny said:
ODIN back to stock.
Click to expand...
Click to collapse
DO NOT ODIN after last update (OTA 4.3) installed on phone. You will brick your phone.
norbarb said:
DO NOT ODIN after last update (OTA 4.3) installed on phone. You will brick your phone.
Click to expand...
Click to collapse
You're right. I completely forgot about that.

note 3 running 4.4.4 issues

ok guys, i have a question for you. keep in mind that im new to the phone world lol. ok so a bout a month ago i wanted to unroot my phone but for some reason the tar files on sammobile wasnt working right. so i came on here and downloaded what i believed to be the file that i needed to go back to stock. after i used odin and the phone rebooted it automatically notified me that i had a update. after i accepted the update and it rebooted, it again notified me that i have yet another update. so after this happened i noticed that my phone was updated to 4.4.4 kitkat which would be great exept for the fact that it keeps freezing and when i am on wifi i have a problem getting phone calls aswell as text messages. also when i disconnect from wifi i have to restart the phone to get any data back. is there anything that i can do? is it possible to go back to 4.3 or even 4.2.2? any help would be very much appreciated.
hellrazr209 said:
ok guys, i have a question for you. keep in mind that im new to the phone world lol. ok so a bout a month ago i wanted to unroot my phone but for some reason the tar files on sammobile wasnt working right. so i came on here and downloaded what i believed to be the file that i needed to go back to stock. after i used odin and the phone rebooted it automatically notified me that i had a update. after i accepted the update and it rebooted, it again notified me that i have yet another update. so after this happened i noticed that my phone was updated to 4.4.4 kitkat which would be great exept for the fact that it keeps freezing and when i am on wifi i have a problem getting phone calls aswell as text messages. also when i disconnect from wifi i have to restart the phone to get any data back. is there anything that i can do? is it possible to go back to 4.3 or even 4.2.2? any help would be very much appreciated.
Click to expand...
Click to collapse
Hello! Did you make a back up of your phone before you started the update? That would be the easiest way to go back to how it was. If you used Odin and didn't install a recovery like TWRP or Clockwork you may not have done so. I believe you can reload from Odin with an older ROM it will just erase everything you did. There are stock ROMS here at XDA and galaxynote3root.com as well. Let me know it this helps, sorry for your troubles.
5225
Jedidanno said:
Hello! Did you make a back up of your phone before you started the update? That would be the easiest way to go back to how it was. If you used Odin and didn't install a recovery like TWRP or Clockwork you may not have done so. I believe you can reload from Odin with an older ROM it will just erase everything you did. There are stock ROMS here at XDA and galaxynote3root.com as well. Let me know it this helps, sorry for your troubles.
Click to expand...
Click to collapse
Thanks for the reply, so i wont have any problem downgradeing? I think i read somewhere that i could brick my phone. And if it is possible what version am i able to go back to?
Oh and to answer your question, i have never has a custom recovery on this phone and i didnt make a back up.
Can you post a screenshot of your about phone page?
Techniques said:
Can you post a screenshot of your about phone page?
Click to expand...
Click to collapse
is this good
I'm actually surprised that you did get an update to 4.4.4... You could try going back to NF9. The safest route I see that you can take is to install a custom recovery and make a backup before doing this. If you odin NF9 and it doesn't boot then you're kinda screwed because we technically don't have the 4.4.4 update yet, so if anything goes wrong, you can install a recovery again and restore the 4.4.4 backup.
Techniques said:
I'm actually surprised that you did get an update to 4.4.4... You could try going back to NF9. The safest route I see that you can take is to install a custom recovery and make a backup before doing this. If you odin NF9 and it doesn't boot then you're kinda screwed because we technically don't have the 4.4.4 update yet, so if anything goes wrong, you can install a recovery again and restore the 4.4.4 backup.
Click to expand...
Click to collapse
haha i was surprised to, i cant find anyone else that has it with this phone either, i was kinda wondering if i maybe downloaded the wrong file maybe for a different country or carrier. im not sure how to do the hole backup and custom recovery thing.
hellrazr209 said:
haha i was surprised to, i cant find anyone else that has it with this phone either, i was kinda wondering if i maybe downloaded the wrong file maybe for a different country or carrier. im not sure how to do the hole backup and custom recovery thing.
Click to expand...
Click to collapse
You can get the latest TWRP recovery here : http://www.techerrata.com/file/twrp2/hltetmo/openrecovery-twrp-2.8.1.0-hltetmo-4.4.img.tar
Just odin that and after it's done, go into recovery by doing Vol down + Home and do a backup either in your internal or external storage. After that finishes, you can go back in download mode and odin NF9.
ok thanks for all you help man,
hellrazr209 said:
is this good
Click to expand...
Click to collapse
iam surprised as well how did you get the latest tar on tmobile note 3?
chipis said:
iam surprised as well how did you get the latest tar on tmobile note 3?
Click to expand...
Click to collapse
I got it on here, it was a tar for 4.4.2 i believe and after i downloaded it, it said i had a update. After that i had another update lol which brought me to the hell im in now lol 4.4.4
hellrazr209 said:
I got it on here, it was a tar for 4.4.2 i believe and after i downloaded it, it said i had a update. After that i had another update lol which brought me to the hell im in now lol 4.4.4
Click to expand...
Click to collapse
Well i believe if iam right samobile had not release it for tmo yet
chipis said:
Well i believe if iam right samobile had not release it for tmo yet
Click to expand...
Click to collapse
Yeah its not on their website. I have know idea what i got then lol anyway to fine out if i have something i shouldnt?

[Q] Factory reset in CM12 now stuck in recovery boot loop

So I'm just getting into the whole ROM thing and I'm pretty sure I've messed up here. I encountered a problem after installing CyanogenMod 12 Unofficial (trltespr NIGHTLY) where I could receive text messages but not send them. I could still load pages and apps over lte and call people but I couldnt send messages. I gave up with the idea of finding a solution after browsing forums and decided to preform a factory reset through settings. The phone was rooted but not after I installed the rom. after rebooting it went into recovery mode and began to loop showing the Team Win screen then going black only to do it again. I removed the battery and booted the phone into download mode and it is now sitting here connected to my computer with Odin up ready for whatever it is that I need to do to fix it. I have absolutely no idea what to do. Help is very much appreciated.
diehlkj said:
I removed the battery and booted the phone into download mode and it is now sitting here connected to my computer with Odin up ready for whatever it is that I need to do to fix it. I have absolutely no idea what to do. Help is very much appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-sprint/general/stock-n910pvpu1anie-stock-tar-t2944867
Go there and download the BOB7.tar and flash that.
xxSTARBUCKSxx said:
http://forum.xda-developers.com/note-4-sprint/general/stock-n910pvpu1anie-stock-tar-t2944867
Go there and download the BOB7.tar and flash that.
Click to expand...
Click to collapse
I went and followed the instructions and odin said it failed due to auth. Any other ideas?
diehlkj said:
I went and followed the instructions and odin said it failed due to auth. Any other ideas?
Click to expand...
Click to collapse
A couple but i dont think i can throw my laptop that far.
Youre an OE1 victim and Good Luck in your endeavors until a .tar comes out.
Search The Q&A threads pertaining to OE1 and see if you can manage to come out with a successful gathering of info and get back your phone.
xxSTARBUCKSxx said:
A couple but i dont think i can throw my laptop that far.
Youre an OE1 victim and Good Luck in your endeavors until a .tar comes out.
Search The Q&A threads pertaining to OE1 and see if you can manage to come out with a successful gathering of info and get back your phone.
Click to expand...
Click to collapse
Is there any way I can remove or reinstall/repair TWRP so i can properly wipe the system or just get another rom working?
Solved
Ok so I did some searching and didn't find any definitive answer as to how to fix this. Finally, figuring I couldn't mess this up any further I went into odin and re-ran the CF Auto Root. It rooted successfully and the moment it rebooted it loaded me back into Cyanogen. None of my settings were changed and everything was how I left it. As for my message problem they still wont send but at least I got my phone back. Thanks for the help as I'm now going to restore to factory settings so long as my recovery is working.
The reason rooting it fixed the problem is because it restored the factory recovery and I can now reinstall TWRP
diehlkj said:
Ok so I did some searching and didn't find any definitive answer as to how to fix this. Finally, figuring I couldn't mess this up any further I went into odin and re-ran the CF Auto Root. It rooted successfully and the moment it rebooted it loaded me back into Cyanogen. None of my settings were changed and everything was how I left it. As for my message problem they still wont send but at least I got my phone back. Thanks for the help as I'm now going to restore to factory settings so long as my recovery is working.
The reason rooting it fixed the problem is because it restored the factory recovery and I can now reinstall TWRP
Click to expand...
Click to collapse
Then you can flash notarize rom per that threads first post... Until an updated tar that will work in Odin.
http://forum.xda-developers.com/showthread.php?p=60506568
diehlkj said:
Ok so I did some searching and didn't find any definitive answer as to how to fix this. Finally, figuring I couldn't mess this up any further I went into odin and re-ran the CF Auto Root. It rooted successfully and the moment it rebooted it loaded me back into Cyanogen. None of my settings were changed and everything was how I left it. As for my message problem they still wont send but at least I got my phone back. Thanks for the help as I'm now going to restore to factory settings so long as my recovery is working.
The reason rooting it fixed the problem is because it restored the factory recovery and I can now reinstall TWRP
Click to expand...
Click to collapse
Yep, the trend seems to be pointing to CF Auto Root after trying to flash stock tar over OE1 build. Although I'm thinking the stock recovery is from way back unless CF updates his build.
About the text sending issue, did you apply the fix found in link below? Check under the spoiler.
http://forum.xda-developers.com/showthread.php?p=57613217
If you want to get back to TW, Noterized is a good OP option. (As mentioned above)
Sent from my SM-N910P using Tapatalk

I love my Note - Trying to get back to 5.1.1

I love my Note 4 so much that I tried for about 2 weeks to fix it's constant rebooting issue. Went to ATT & Samsung repair center and they couldn't get it to flash. However, it stills turns on, I just generally need to pull the battery for a few minutes to get it to boot.
With that said, I'm not incredibly knowledgeable in this area. I've downloaded ODIN and found lots of resources for the exact steps to follow, however, I'm not sure where I can locate a version of 5.1.1 for ATT. To me, this seems like my only fix for my phone. I've tried clearing cache and factory resets etc. My phone is unlocked. Am I missing anything that you can think of? Can someone link me to a reputable source for the appropriate files?
You seriously cannot imagine how happy I'd be if I can get this thing working again. Thank you!
PS, if you think there is a more stable version than 5.1.1, I'm open to that too.
Bump. Any help is greatly appreciated. Thanks!
Google is your friend...
http://rapidgator.net/file/2ab3e0dc...om/att-galaxy-note-4-sm-n910a-stock-firmware/
Punker1234 said:
I love my Note 4 so much that I tried for about 2 weeks to fix it's constant rebooting issue. Went to ATT & Samsung repair center and they couldn't get it to flash. However, it stills turns on, I just generally need to pull the battery for a few minutes to get it to boot.
With that said, I'm not incredibly knowledgeable in this area. I've downloaded ODIN and found lots of resources for the exact steps to follow, however, I'm not sure where I can locate a version of 5.1.1 for ATT. To me, this seems like my only fix for my phone. I've tried clearing cache and factory resets etc. My phone is unlocked. Am I missing anything that you can think of? Can someone link me to a reputable source for the appropriate files?
You seriously cannot imagine how happy I'd be if I can get this thing working again. Thank you!
PS, if you think there is a more stable version than 5.1.1, I'm open to that too.
Click to expand...
Click to collapse
What is your Baseband? Maybe you can't go back.
Heya guys.
Thank you for the link! I seriously googled and browsed forums for days looking for it. I even went to the Android website with a slew of different version but they did not have the ATT versions. Anyway, I'm going to give this a go but still pretty green to it. I was going to follow the instructions from this post - should work right? https://forum.xda-developers.com/note-4-att/general/expert-phone-trashed-t3573110
And Norbarb, I have no idea what my Baseband version is. I did a quick google to see if I can locate it somewhere but couldn't figure it out. How can I check?
I do appreciate your help.
Punker1234 said:
Heya guys.
Thank you for the link! I seriously googled and browsed forums for days looking for it. I even went to the Android website with a slew of different version but they did not have the ATT versions. Anyway, I'm going to give this a go but still pretty green to it. I was going to follow the instructions from this post - should work right? https://forum.xda-developers.com/note-4-att/general/expert-phone-trashed-t3573110
And Norbarb, I have no idea what my Baseband version is. I did a quick google to see if I can locate it somewhere but couldn't figure it out. How can I check?
I do appreciate your help.
Click to expand...
Click to collapse
Can you reboot to recovery?? There's some info there regarding your current setup
Ironically, now I can't even get the phone to turn on. I bought a battery charger for the Note battery to see if that is the issue. I can't get the battery to charge even when it's plugged in. That arrives Monday so I'll update shortly.
Quick update:
Baseband is N910AUCS2EPK3. I'm not sure if that means I can or can't roll back to Lollipop.
Popped in the charged battery from my new charger and it came right on. Had it on for a little bit just messing around with things. After rebooting it myself a few times, it now is reverting back to it not even turning on, even with a charged battery. I pull the battery 10-20 times, hold the power button without the battery to clearly out any remaining electricity and still no go. I have 2 batteries and neither work. So I'm going to let it sit and if I can get it to come on, install Wake Lock.
Does anyone know if I can revert back to 5.1? I'm not sure how my Baseband effects that. Thank you for all of your help! If I can't get this, I think I may go back to my S3 vs a Pixel.
Punker1234 said:
Quick update:
Baseband is N910AUCS2EPK3. I'm not sure if that means I can or can't roll back to Lollipop.
Click to expand...
Click to collapse
If you have this, you can easily go to Odin and flash 5.1.1. I don't have the link to the LP Odin files, but heres the Odin link for the MM files in OP:
ODIN FILES to get back to EPH5 and latest ODIN
ODIN
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Make sure you can be able to stay in Bootloader for a while before you attempt this, because if your phone dies before the Odin flash completes, you probably likely just created a brick.
Here's my How-To in that same thread. I've also used the newest Odin available with same good results.
https://forum.xda-developers.com/showpost.php?p=68620446&postcount=1180
In fact, I'm about to reflash back to 5.1.1 again from latest updates. MM is pissing me off on that battery issue again. I just wish I can keep it there and keep ATT from pushing OTA without me agreeing to it.
ljjehl said:
If you have this, you can easily go to Odin and flash 5.1.1. I don't have the link to the LP Odin files, but heres the Odin link for the MM files in OP:
ODIN FILES to get back to EPH5 and latest ODIN
ODIN
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Make sure you can be able to stay in Bootloader for a while before you attempt this, because if your phone dies before the Odin flash completes, you probably likely just created a brick.
Here's my How-To in that same thread. I've also used the newest Odin available with same good results.
https://forum.xda-developers.com/showpost.php?p=68620446&postcount=1180
In fact, I'm about to reflash back to 5.1.1 again from latest updates. MM is pissing me off on that battery issue again. I just wish I can keep it there and keep ATT from pushing OTA without me agreeing to it.
Click to expand...
Click to collapse
Holy crap, awesome man. Thank you. At this point, I can't even get the phone to turn on with 2 different batteries. Tried holding the power button down for awhile and letting it sit for hours and still nothing. Not sure what the deal is with this thing. I'll keep attempting.
Punker1234 said:
Holy crap, awesome man. Thank you. At this point, I can't even get the phone to turn on with 2 different batteries. Tried holding the power button down for awhile and letting it sit for hours and still nothing. Not sure what the deal is with this thing. I'll keep attempting.
Click to expand...
Click to collapse
Try holding power button, home button and volume up all at the same time while its powered off. If you can get to Recovery screen here, then you just may be getting somewhere. I would then wipe data/factory reset, then reboot again. If this doesn't work, you can then try holding power botton, home button and Volume down at the same time. This gets you in bootloader mode. Once you get there, only way out at this point is pulling battery (to start over) or get started on Odin flashing.
At least I have kept OTA from working, with this debloater from this link: https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
ljjehl said:
Try holding power button, home button and volume up all at the same time while its powered off. If you can get to Recovery screen here, then you just may be getting somewhere. I would then wipe data/factory reset, then reboot again. If this doesn't work, you can then try holding power botton, home button and Volume down at the same time. This gets you in bootloader mode. Once you get there, only way out at this point is pulling battery (to start over) or get started on Odin flashing.
At least I have kept OTA from working, with this debloater from this link: https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Click to expand...
Click to collapse
Thanks. Yea i can't get into recovery or the download mode. I bought a battery charger just thinking my phone wasn't charging them. The first time it started up perfect. Now I can't get it to come up at all. As mentioned, I'll keep trying. Wondering if something else has gone wrong, or if it's software related still.
ljjehl said:
If you have this, you can easily go to Odin and flash 5.1.1. I don't have the link to the LP Odin files, but heres the Odin link for the MM files in OP:
ODIN FILES to get back to EPH5 and latest ODIN
ODIN
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Make sure you can be able to stay in Bootloader for a while before you attempt this, because if your phone dies before the Odin flash completes, you probably likely just created a brick.
Here's my How-To in that same thread. I've also used the newest Odin available with same good results.
https://forum.xda-developers.com/showpost.php?p=68620446&postcount=1180
In fact, I'm about to reflash back to 5.1.1 again from latest updates. MM is pissing me off on that battery issue again. I just wish I can keep it there and keep ATT from pushing OTA without me agreeing to it.
Click to expand...
Click to collapse
Got the phone to turn back on. Quick question. In your post, you mention 4 ODIN files. I only have an MD5 file and a PT file. Is there something I'm missing? I downloaded the stock rom from the top of my post. Thank you!
Punker1234 said:
Got the phone to turn back on. Quick question. In your post, you mention 4 ODIN files. I only have an MD5 file and a PT file. Is there something I'm missing? I downloaded the stock rom from the top of my post. Thank you!
Click to expand...
Click to collapse
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
There should be a zip in here that you have to extract four files to a folder. You will use the Odin exe program to look for those files. Just follow my howto notes I wrote in the link I posted. This is to the Marshmallow stuff. Forget the MD5 and pit file unless you know what you are doing. Since I don't know where that came from, I won't even suggest those 2.
ljjehl said:
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
There should be a zip in here that you have to extract four files to a folder. You will use the Odin exe program to look for those files. Just follow my howto notes I wrote in the link I posted. This is to the Marshmallow stuff. Forget the MD5 and pit file unless you know what you are doing. Since I don't know where that came from, I won't even suggest those 2.
Click to expand...
Click to collapse
Ironically I'm looking to get rid of Marshmallow because I think 6.0.1 screwed up my phone. It was working great prior to that. So the LP files I have are the MD5 and pit, supplied in the 3rd post. Is there somewhere I should look for LP files? And to be clear, are there "regular" rom files for general use, and then ODIN specific files? ie, you could have a "regular" 5.1.1 file, and then ODIN specific 5.1.1?
Punker1234 said:
Ironically I'm looking to get rid of Marshmallow because I think 6.0.1 screwed up my phone. It was working great prior to that. So the LP files I have are the MD5 and pit, supplied in the 3rd post. Is there somewhere I should look for LP files? And to be clear, are there "regular" rom files for general use, and then ODIN specific files? ie, you could have a "regular" 5.1.1 file, and then ODIN specific 5.1.1?
Click to expand...
Click to collapse
Well, I have the 5.1.1 Odin files also, but will have to zip it and upload, unless someone else has a link faster
ljjehl said:
Well, I have the 5.1.1 Odin files also, but will have to zip it and upload, unless someone else has a link faster
Click to expand...
Click to collapse
Is there a way to use the files that I have? Not using ODIN? Or is that not recommended?
Punker1234 said:
Is there a way to use the files that I have? Not using ODIN? Or is that not recommended?
Click to expand...
Click to collapse
With the mess you have, I would think you want to Odin flash a whole new setup. You don't know what's wrong and a partition could be corrupted. If it's hardware, nothing you really could do about it anyways
ljjehl said:
With the mess you have, I would think you want to Odin flash a whole new setup. You don't know what's wrong and a partition could be corrupted. If it's hardware, nothing you really could do about it anyways
Click to expand...
Click to collapse
Got it. I looked around and cannot find the files for ATT. I see them for others I think, but ATT is a ghost. Would you mind uploading if you can? If not I understand. I appreciate all of your help! Crossing my fingers that my Note 4 is still alive and well.

Categories

Resources