Backstory - I have been rooting and flashing custom roms for the last 5 years starting with my 1st HTC Evo. So I have a lot of experience.
But this is wearing me out. So I picked up at Note 4 this past Friday. I only got around to rooting it tonight (Hawaii time). (Which is also weird because all of my phones were rooted as soon as I got home. Note 3 rooted only 20 minutes after I left Sprint last year.) Any ways, I have the NK2 build. I rooted using the Chain Fire method and I flashed TWRP 2.8.3. Did a full wipe and tried to flash Bonsai the deodex version. TWRP kept rebooting every time I tried to flash the rom.
Does anybody have any ideas on what to do? I haven't tried flashing TWRP 2.8.1 yet though.
I wasn't even aware TWRP updated to to 2.8.3.0 but do see it now. I'm using openrecovery-twrp-2.8.1.1-trltespr.img downloaded from flashify.
BTW, I don't see a Bonsai NK2 ROM. Try a NK2 ROM. I'm running rooted stock NK2 so don't have a suggestion in regards to custom NK2 ROM.
http://forum.xda-developers.com/not...-nie-stockish-knox-root-sprint-stock-t2919346
Its wasnt labeled Bonsai. It is a NK2 friendly rom. Meh. I guess i still have to look around.
OK that's basically stock NK2 deodexed; didn't mean to steer you away from that. Bad download? Try again.
The weird thing is, i downloaded thru chrome on my laptop and i got a message after it downloaded saying it was a file that is not normally downloaded and asked if i wanted to discard it. Sigh. I hope i can get this on my phone. Thanks for the help
Have Wi-Fi connection available to your phone? Download to phone.
smh. I just noticed that I was trying to flash it off of my sd card. ARGH!!! Thanks for the help samep.
Related
When I tried to switch from ACS EI22 4 to 5 my phone force close looped because of some issue with launcher pro. I went to reflash the rom from CWM and ever since my phone won't properly load roms from CWM. When the phone has a custom rom it boots right to CWM when I power them up only to freeze again when I try to boot the rom from recovery.
I have Odined to stock EC05, and one click flashed CWM. I have flashed pre-rooted EC05 roms. I Odined to EI22 & EC05 modem Tar and went on to install ACS recovery over CWM.
I have Odined multiple times on multiple stock roms and custom roms. The problem persists. Once I'm in recovery (I've tried 3 versions) and I click "reboot" the phone locks with a black screen with the home buttons on or an image of the clockwork logo (depending on which version I'm trying).
The strange thing is, all of the stock roms work just fine and I was able to install EI22 from OTA with no problems. But who wants that icky CIQ? or Sprint nascar/football/bloatware? Yuck!
I've had some limited success with simple pre-rooted deodex etc roms I flash from Odin, but sometimes recovery loads when I power up the phone. And sprint keeps wanting to force the update on me.
Does anyone have any suggestions? I've tried everything I can think of and have searched, to no avail, for a solution.
Does anyone think this is a hardware issue? One of the kernels I tried on ACS 5 was a beta.
If so, how should I go about getting it fixed since it is under warranty. I do have accidental damage coverage.
Most likely not hardware related. I say that because you said you can run stock just fine.
I would try the new CWM5 just released and see if the problem is still there.
Disregard post
Sent from my SPH-D700 using xda premium
Neckberg said:
Most likely not hardware related. I say that because you said you can run stock just fine.
I would try the new CWM5 just released and see if the problem is still there.
Click to expand...
Click to collapse
That's what I thought and why I continued to Odin and one-click root different types of CWM and ACS recovery.
I'm going to see if the repair store nearby can run a diagnostic. Otherwise I'm going to stay away from any modifications that require me to use CWM for anything since I was able to Odin a custom rom (but it was EC05).
Hopefully Samsung will release the EI22 modem tar and someone will release a pre-rooted version that I can Odin.
I tried odin flashing different recoveries yesterday. Odin gave them a pass but they wouldn't boot from the 3 finger salute (like they didn't install).
I've never tried to install CWM this way so I'm not sure if you need to be rooted before hand or you need a specific kernel.
osiris2600 said:
I tried odin flashing different recoveries yesterday. Odin gave them a pass but they wouldn't boot from the 3 finger salute (like they didn't install).
I've never tried to install CWM this way so I'm not sure if you need to be rooted before hand or you need a specific kernel.
Click to expand...
Click to collapse
So it goes back into stock recovery with 3 finger? Easiest fix is Odin in a prerooted EC05 ROM tar like EC05plus then flash a Gingerbread ROM then flash the modem delta.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
So it goes back into stock recovery with 3 finger? Easiest fix is Odin in a prerooted EC05 ROM tar like EC05plus then flash a Gingerbread ROM then flash the modem delta.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Yes it goes into stock recovery. Unfortunately flashing in CWM has been the problem that lead me to flashing CWM through Odin. For more detail see the original post. Whenever I try to flash something through CWM the recovery has problems and it fails to load the rom that is installed.
I'm trying as many alternatives to pinpoint the problem. I'm going to try switching SD cards and see if the problem resulted from some kind of data corruption there. Should have an update on that sometime tonight.
If I can't figure out and fix the problem I'll be at the mercy of sprint or if I want root I'll have to wait for a pre-rooted EI22 rom complete with modem tarball so I can odin that.
I saw the OP but didn't see where you Odin'd a prerooted EC05 ROM like EC05plus. Then flash a GB ROM right after. Just 2 steps. Then if you want the modem one more step to flash the delta. It's worth a shot?
Sent from my SPH-D700 using XDA App
kennyglass123 said:
I saw the OP but didn't see where you Odin'd a prerooted EC05 ROM like EC05plus. Then flash a GB ROM right after. Just 2 steps. Then if you want the modem one more step to flash the delta. It's worth a shot?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I can't flash from CWM no matter how CWM gets on my phone. I tried exactly what you said. My original post says I Odined multiple stock and custom roms. I didn't get around to CWM flashing on a different card tonight, finals got me busy busy.
Enjoy your turkey day!
osiris2600 said:
I can't flash from CWM no matter how CWM gets on my phone. I tried exactly what you said. My original post says I Odined multiple stock and custom roms. I didn't get around to CWM flashing on a different card tonight, finals got me busy busy.
Enjoy your turkey day!
Click to expand...
Click to collapse
Thanks, you too.
So if Odining the EC05Plus ROM didn't get you a working 3 finger salute CWM, then maybe you should try ROM Manager and downloading CWM 5.X.
http://forum.xda-developers.com/showthread.php?t=1357655
It must be a hardware problem. I can odin a rom with CWM and it will boot fine. However if I ever try to open CWM the rom will never load again as the phone boots to recovery and get's stuck there.
I confirmed this by Odin flashing and then going into clockwork and not even flashing anything and it got stuck. Flashing in CWM will actually install things as I can change CWM within CWM but I still get stuck when trying to load the rom.
So the only way for me to enjoy a rooted phone is to refrain from CWM recovery.
I went back to a EH17 odined pre-rooted rom. When EI22 gets a modem tar hopefully someone will make a pre-rooted, deodexed, zipaligned odin tar (and if I'm lucky, CiQ will be removed).
Otherwise I'd like to get a replacement but explaining the problem to sprint is kind of a catch 22 since the issue only appears when I load a custom recovery.
How about flashing CWM 5.027 and downloading ROM Manager and installing 5.027 through that as well. Rom Manager actually downloads the CWM 5 and keeps it packed on your sd card and installs it everytime you use it. It allows ROM Manager to be able to update the CWM whenever a new version comes out.
Ok here is the deal. I had a camera focus issue with my original S3. Took it to the warranty center and they replaced it. Works great. I rooted then rom'd and it breaks the camera. Doesn't matter if 4.2 or 4.3 camera can't connect.
Flashed back to stock checked the camera works just fine. So I rooted the phone and didn't flash a rom. Camera works fine. I tried to fix permissions for the camera no difference when I flashed a rom.
This is very annoying. I really like having a rom'd phone but I need my camera.
Any suggestions I can try?
Well it seems that no one had any idea about this issue. I talked with a friend last night and he said flash TWRP to the newest. I did flash the newest TWRP and it fixed this issue. Camera works as advertised when I flashed a ROM
Rooted my husband's phone today and encountered this same problem. I flashed with CWR. Do you recommend going back to stock and flashing with TWR or just flashing to TWR without going back to stock?
bonespanda said:
Rooted my husband's phone today and encountered this same problem. I flashed with CWR. Do you recommend going back to stock and flashing with TWR or just flashing to TWR without going back to stock?
Click to expand...
Click to collapse
Make sure you are on the newest clockwork or the newest TWRP
sparker366 said:
Make sure you are on the newest clockwork or the newest TWRP
Click to expand...
Click to collapse
Thanks I'll try that ASAP.
On another note, I'm wondering if flashing the incorrect or out of date CM had anything to do with this. Hes currently on 4.1.2 so I flashed CM v 10.0.0. Any thoughts?
**This is what happens when you learn something, leave it for a couple of years and come back to it on a device that's not even yours**
Hi all, hope you are doing well (I also hope that you can help me ).
I just recently got a replacement phone because my other one had a faulty speaker (crackling, etc.). The other one was rooted (via CF-AutoRoot) and had TWRP on it, and I made a complete nandroid backup of it onto my MicroSD card.
I rooted the new phone using CF-AutoRoot via Odin and installed TWRP on it as well (also via Odin). Then I swapped the SD card and SIM card and restored the complete backup to the new phone.
It took a while, but the phone booted up and I had two working clones, the only way to tell which was which was by changing the volume and hearing the crackling on the old one.
So the new phone worked all day (was able to make calls and everything, and the GUI that was customized with Wanam Xposed even looked good), however when I restarted it to put in my backup battery, I didn't have root for some reason. I tried and tried to get it back (reinstalled SuperSU, tried the TWRP method) to no avail.
I re-flashed CF-AutoRoot just to see, and the phone booted up but and for some reason SuperSU was gone (and I didn't have root). When I restarted, I got a boot loop and could not even get back into a recovery.
I got tired of this and wanted a fresh start, so I just flashed the stock ROM via ODIN and did a factory reset. However now if I try to boot, the Samsung logo will flash and just shut down, and I won't be able to get into the recovery no matter what. If I flash a recovery (CWM, TWRP or even stock), the recovery will work until I try to actually try to boot the phone. I've tried taking the battery out for a good 5 minutes and retrying (also tried swapping batteries), I've tried doing complete resets galore from all three recoveries mentioned with no success. Obviously Download mode still works so I know it's not completely bricked, but I am getting a little scared.
Any and all help is extremely appreciated as I would prefer not to have such an expensive paper-weight.
Thanks a bunch!
I would suggest going all the way back stock on stock firmware via Odin. Then re-root, TWRP, and re-download the rom of your choice. Dont restore the backup. Just start fresh.
I Think My S4 Is Insane
SICK MADE DEVELOPMENT
alloycowboy said:
I would suggest going all the way back stock on stock firmware via Odin
Click to expand...
Click to collapse
Thanks for the reply.
And okay, I tried that.
I flashed stock using the T-Mobile ROM I found here: galaxys4root_(dot)_com/galaxy-s4-stock-firmware/
This is the same ROM file I used to completely restore the phone I had to return, and that worked fine.
But it still won't boot up or go into recovery mode (just shows the Samsung logo for a split second before shutting down).
One thing I did do on the other phone was flash a kernel which had set-MUID to off so I could WiFi tether, but I thought flashing the stock ROM would revert that back as well. Do you think that's the reason it messed up so badly? I restored the backup from the other phone with a different kernel? Right after I restored the backup to the new phone and everything was working, I remember checking the kernel info in the About Phone section of the settings, and it was in fact the kernel I'd installed on the other phone.
TLDR: Tried flashing stock ROM to no avail. Download mode still works but can't enter recovery mode or boot.
Are you doing a factory reset after flashing stock firmware?
I Think My S4 Is Insane
SICK MADE DEVELOPMENT
I'd flash a stock rooted ROM. Get that root and recovery back. The konane tar file from the stickies, perhaps.
Sent from my SGH-M919 using xda app-developers app
alloycowboy said:
Are you doing a factory reset after flashing stock firmware?
Click to expand...
Click to collapse
Yeah, as soon as it finished installing I went into stock recovery and did a factory reset.
Karakoram2 said:
I'd flash a stock rooted ROM. Get that root and recovery back. The konane tar file from the stickies, perhaps.
Click to expand...
Click to collapse
Alright, I'll try that.
Is the konane tar an actual ROM? And what do you mean in the stickies?
Sorry, not very familiar with XDA forums.
Samsung GT-I9500 flashes n switches off!
BallisticallySimilar said:
Hi all, hope you are doing well (I also hope that you can help me ).
I just recently got a replacement phone because my other one had a faulty speaker (crackling, etc.). The other one was rooted (via CF-AutoRoot) and had TWRP on it, and I made a complete nandroid backup of it onto my MicroSD card.
I rooted the new phone using CF-AutoRoot via Odin and installed TWRP on it as well (also via Odin). Then I swapped the SD card and SIM card and restored the complete backup to the new phone.
It took a while, but the phone booted up and I had two working clones, the only way to tell which was which was by changing the volume and hearing the crackling on the old one.
So the new phone worked all day (was able to make calls and everything, and the GUI that was customized with Wanam Xposed even looked good), however when I restarted it to put in my backup battery, I didn't have root for some reason. I tried and tried to get it back (reinstalled SuperSU, tried the TWRP method) to no avail.
I re-flashed CF-AutoRoot just to see, and the phone booted up but and for some reason SuperSU was gone (and I didn't have root). When I restarted, I got a boot loop and could not even get back into a recovery.
I got tired of this and wanted a fresh start, so I just flashed the stock ROM via ODIN and did a factory reset. However now if I try to boot, the Samsung logo will flash and just shut down, and I won't be able to get into the recovery no matter what. If I flash a recovery (CWM, TWRP or even stock), the recovery will work until I try to actually try to boot the phone. I've tried taking the battery out for a good 5 minutes and retrying (also tried swapping batteries), I've tried doing complete resets galore from all three recoveries mentioned with no success. Obviously Download mode still works so I know it's not completely bricked, but I am getting a little scared.
Any and all help is extremely appreciated as I would prefer not to have such an expensive paper-weight.
Thanks a bunch!
Click to expand...
Click to collapse
The same thing has happened to me! Did you find any solustion for this?? Please help!! This was my first attempt and i have no idea wats going on!
Here are the stickies for our forum: http://forum.xda-developers.com/showthread.php?t=2419828
Sent from my SGH-M919 using XDA Premium 4 mobile app
What I did to unbrick my T-Mobile S4 (SGH-M919)
killerwolf2121 said:
The same thing has happened to me!
Did you find any solutions for this? Please help if you can; this was my first attempt and I have to idea what's going on.
Click to expand...
Click to collapse
Well, for the first problem, flashing the stock ROM did it for me. I followed this tutorial.
For the second issue of not booting up after displaying the Samsung logo; my battery just simply was too dead and didn't have enough juice to start. You have no idea how stupid I felt.
Let your phone charge from the wall cable for a good while before trying all this again; then see if that works. It did it for me. If it doesn't, I'm not sure what else to try.
After that (if it works), if you still want root, just flash CF-Auto-Root and then a custom recovery if you want (like ClockworkMod Recovery (click the little version link, not the "Download ROMs" button) or TWRP via GooManager) (I use TWRP)
All the best and let me know how it went!
Keep in mind that I did this on an SGH-M919 (T-Mobile S4) running Android 4.2.2, so if you don't have that, I have no idea if any of the above will work for you. Also I'm pretty sure if you do have 4.3, you will ruin your warranty forever due to the Knox restriction they added (if you haven't already).
Android_Monsters said:
Here are the stickies for our forum: http://forum.xda-developers.com/showthread.php?t=2419828
Click to expand...
Click to collapse
Thanks
BallisticallySimilar said:
Well, for the first problem, flashing the stock ROM did it for me. I followed this tutorial.
For the second issue of not booting up after displaying the Samsung logo; my battery just simply was too dead and didn't have enough juice to start. You have no idea how stupid I felt.
Let your phone charge from the wall cable for a good while before trying all this again; then see if that works. It did it for me. If it doesn't, I'm not sure what else to try.
After that (if it works), if you still want root, just flash CF-Auto-Root and then a custom recovery if you want (like ClockworkMod Recovery (click the little version link, not the "Download ROMs" button) or TWRP via GooManager) (I use TWRP)
All the best and let me know how it went!
Keep in mind that I did this on an SGH-M919 (T-Mobile S4) running Android 4.2.2, so if you don't have that, I have no idea if any of the above will work for you. Also I'm pretty sure if you do have 4.3, you will ruin your warranty forever due to the Knox restriction they added (if you haven't already).
Thanks
Click to expand...
Click to collapse
I am on 4.3 and yes, flashing the stock rom worked for me too! relief thanks a ton!
Having trouble unbricking M919 T-Mobile
Hi, I'm trying to unbrick my M919 through Odin. I have all the updated software, but I keep getting a fail message. Any help would be appreciated.
So my wifes i747 was running 4.0.4 so I decided to upgrade it for her a bit. Im not new to rooting and flashing roms so I figured why not just put a custom KK rom onto it in order to freshen it up a bit for her. I also have to add that it is a ATT S3 unlocked and being used on Tmobile network.
Came to the forums and downloaded SlimKat rom and installed CWM and flashed the new rom. Everything went fine, but in the end my wife didnt like the feel of it and just wanted a new phone. So I traded her my phone and got hers. Well i wasnt a huge fan of the SlimKat rom either, nothing particularly wrong I was just always a CyanogenMod fan. Im having issues right now because I cannot get it to flash any new ROMs without messing up. Ill either get an error in CWM saying it cant flash the new rom or it will Flash but then never leave the LOGO screen. Ive let it sit for 45mins before.
I was able to always restore to a backup and just keep using SlimKat, but just tonight Im no longer able to restore to the backup. CWM sits at "Restoring data... c7ac6bd9.0..." but never actually finishes the restore.
So am I bricked? or what should I try? and also can someone just tell me what Rom/Kernal/Modem I need to flash in order to get it working. Id really like to use the Cyanide L, with Shift kernal but im not sure which modem I need. Tmobile modem or Att modem and which number.
Any help would be great thanks.
Additional info: I wiped cache, dalvik, and system/data everytime I tried to flash new rom, I made a backup and saved to my external before the flash. It is carrier unlocked and rooted. model number is the i747. CWM is v6.0.1.2
Your CWM is outdated.
Flash the latest Philz tar.md5 file in Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
The latest KK ROMs will also need an updated bootloader and modem to function properly.
Hi, When I got my Note 4 it had stock lollipop. I was happy with it and it had great battery life but I wanted xposed so I found a tutorial for sprint note 4 lollipop. after i flashed xposed my phone got stuck in a boot loop and i didn't have a backup. i tried to Odin back to stock but that kept failing, i gave up and flashed noterized rom through TWRP. now i want to got back to stock or at least get a different rom (maybe Vision or hybrid i tried both) but i tried flashing a couple of different rom but they never work, my phone just keeps rebooting (goes to "Samsung galaxy note 4 powered by android" screen and then restarts i tried waiting 30 mins but no luck) however i am able to flash an AOSP rom but i don't like them i really like TW. what can i do to restore to stock, downgrade to 4.4.4, or flash vision rom?
for battery life i tried restarting, factory restore, clearing cache and dalvic cache, and formatting everything and re-flashing the rom but nothing seems to work.
if you have any question or need more information please ask. any help is appreciated
ismaeel96 said:
Hi, When I got my Note 4 it had stock lollipop. I was happy with it and it had great battery life but I wanted xposed so I found a tutorial for sprint note 4 lollipop. after i flashed xposed my phone got stuck in a boot loop and i didn't have a backup. i tried to Odin back to stock but that kept failing, i gave up and flashed noterized rom through TWRP. now i want to got back to stock or at least get a different rom (maybe Vision or hybrid i tried both) but i tried flashing a couple of different rom but they never work, my phone just keeps rebooting (goes to "Samsung galaxy note 4 powered by android" screen and then restarts i tried waiting 30 mins but no luck) however i am able to flash an AOSP rom but i don't like them i really like TW. what can i do to restore to stock, downgrade to 4.4.4, or flash vision rom?
for battery life i tried restarting, factory restore, clearing cache and dalvic cache, and formatting everything and re-flashing the rom but nothing seems to work.
if you have any question or need more information please ask. any help is appreciated
Click to expand...
Click to collapse
Youre stuck on Noterized. Enjoy.
No way out? What if somone gives me their back up?
I was stuck i tried different stock tar files from different sources. Finally found one that work the other tar files kept failing in odin. Your not stuck just go online and find the solution yourself . If it's not affecting anybody else they careless if you fix it man and that's with life too just sayin . Good help hard to come by nowadays
Might wanna go through the Q&As and rethink your post. As to avoid contradicting your post all together, could you at least provide a link to the file that got you unstuck to help in the first place.
I pm'ed the guy already
So what did you flash to get back to stock??....HmmmHmmm
EpicBarbecue said:
So what did you flash to get back to stock??....HmmmHmmm
Click to expand...
Click to collapse
so what I did was root using odin installed twrp from the playstore and flashed the twrp recovery from the app. once I had recovery I flashed a stock rom from the forum in twrp. that booted up fine then I hooked my phone into the pc and open kies to see if it reconized my phone and it did so I hit the tools tab at the top of the program and clicked on firmware upgrade and initialization and it stared updating my phone back before the oel update
credit: @bonebeatz1234
I have a update I flashed off of stock and went back then flashed cm12 and the method I used earlier didn't work I was stuck for 2 hours. I flashed a tw rom in twrp when it finished installing I pulled the battery and flashed the modem from bob firmware and bootloader before I restarted the phone I found a bootloader and modem from bob firmware on the forum flashed both and both failed but from what I cant tell it installed enough for the phone to reboot on back on tw and from there I used kies to get back on stock 2nd time bringing it back very long process just finding the right solution
xxSTARBUCKSxx said:
so what I did was root using odin installed twrp from the playstore and flashed the twrp recovery from the app. once I had recovery I flashed a stock rom from the forum in twrp. that booted up fine then I hooked my phone into the pc and open kies to see if it reconized my phone and it did so I hit the tools tab at the top of the program and clicked on firmware upgrade and initialization and it stared updating my phone back before the oel update
credit: @bonebeatz1234
Click to expand...
Click to collapse
So you were actually able to downgrade from OE1? What stock rom did you flash that actually booted up? Thanks.
Yeah i was on hybrid x. I saw someone needed help so i tried to mess my phone up to replicate what the guy did yes the method i used earlier works but only if your on a tw rom . So i flashed cm12 and was stuck before i got back on touchwiz yeah i see what people mean you can't flash ****. So i went to twrp flashed hybrid x didnt restart phone i pulled battery and went to odin and flashed the bob bootloader tar and modem tar i found on the forum i flashes both they both failed but one of them flashed about 75% on odin and i rebooted and tw was back then i went to kies upgraded to stock now back on stock. Unzip these and flash in odin https://www.dropbox.com/s/cvkynp4kmkw8f8c/bootloader lolipop and modem.zip?dl=0 hope this help but if you live in Rockford ,illinois i could just fix it for you
dteze88 said:
So you were actually able to downgrade from OE1? What stock rom did you flash that actually booted up? Thanks.
Click to expand...
Click to collapse
I personally havent been on OE1. A few people who havent been plagued by this horrible and unnecessary update have been trying to help those who have and are. The guy i mentioned at the bottom(of the post you quoted), those were his steps. But it seems some of the information has changed since that post. Look above this post and he explains the differences whether on TW or non TW rom.
One thing Samsung is telling us though through their actions, if theyre pushing out updates and its not over a GB, i wouldnt take it, or I'd at least wait until seeing the ramifications of the update through other users taking it, which there will always be.
ismaeel96 said:
Hi, When I got my Note 4 it had stock lollipop. I was happy with it and it had great battery life but I wanted xposed so I found a tutorial for sprint note 4 lollipop. after i flashed xposed my phone got stuck in a boot loop and i didn't have a backup. i tried to Odin back to stock but that kept failing, i gave up and flashed noterized rom through TWRP. now i want to got back to stock or at least get a different rom (maybe Vision or hybrid i tried both) but i tried flashing a couple of different rom but they never work, my phone just keeps rebooting (goes to "Samsung galaxy note 4 powered by android" screen and then restarts i tried waiting 30 mins but no luck) however i am able to flash an AOSP rom but i don't like them i really like TW. what can i do to restore to stock, downgrade to 4.4.4, or flash vision rom?
for battery life i tried restarting, factory restore, clearing cache and dalvic cache, and formatting everything and re-flashing the rom but nothing seems to work.
if you have any question or need more information please ask. any help is appreciated
Click to expand...
Click to collapse
Did you get it working?
---------- Post added at 01:55 PM ---------- Previous post was at 01:55 PM ----------
bonebeatz1234 said:
Yeah i was on hybrid x. I saw someone needed help so i tried to mess my phone up to replicate what the guy did yes the method i used earlier works but only if your on a tw rom . So i flashed cm12 and was stuck before i got back on touchwiz yeah i see what people mean you can't flash ****. So i went to twrp flashed hybrid x didnt restart phone i pulled battery and went to odin and flashed the bob bootloader tar and modem tar i found on the forum i flashes both they both failed but one of them flashed about 75% on odin and i rebooted and tw was back then i went to kies upgraded to stock now back on stock. Unzip these and flash in odin https://www.dropbox.com/s/cvkynp4kmkw8f8c/bootloader lolipop and modem.zip?dl=0 hope this help but if you live in Rockford ,illinois i could just fix it for you
Click to expand...
Click to collapse
So, were you on OE1 when you did this???
13druber said:
Did you get it working?
---------- Post added at 01:55 PM ---------- Previous post was at 01:55 PM ----------
So, were you on OE1 when you did this???
Click to expand...
Click to collapse
Fyi, the latest update tar just dropped today on Sammobile (OF5). Download, odin, and prosper again
Sent from my SM-N910P using Tapatalk
Androidious said:
Fyi, the latest update tar just dropped today on Sammobile (OF5). Download, odin, and prosper again
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you sir, i did that yesterday. I am rooted and bloat ware removed.
13druber said:
Thank you sir, i did that yesterday. I am rooted and bloat ware removed.
Click to expand...
Click to collapse
Glad you were able to get back finally
Was getting worried that us N4 users would be stuck forever, LOL!
Sent from my SM-N910P using Tapatalk
Androidious said:
Glad you were able to get back finally
Was getting worried that us N4 users would be stuck forever, LOL!
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Me too.
Using noterized over of 5 it works ok