Related
EDIT: I flashed again, without the MicroSD card (I don't know if that had to do with it), but after several tries, I was able to get to TWRP and root
Hey everyone!
I followed this post:
http://forum.xda-developers.com/tab-4/general/root-galaxy-tab-4-7-t230-t2835264
I tried twice, first with the auto reboot option checked in Odin, then, unchecked.
Both times I can't enter download mode.
When I try, I see the Team Win logo for a fraction of a second and then it resets.
Team Win logo
Any ideas?
Thanks!
Anyone? I'm afraid of trying other downloader and messing things up, since TWRP seems to be corrupted. I've checked the MD5 hash of the file before flashing, BTW.
Could be a device compality issue? What device do you have? Did you make sure of flashing the right one? It looks like it flashed correctly but doesnt work on your device.
Hey, thanks for the reply.
Well, I have SM-T230NU (compatible) with build KOT49H.T230NUUEU0ANE2, for which I haven't found any mention regarding whether or not it should work. I guess it should, it's not the latest.
Any ideas on how to proceed? TWRP is the only way to root, right? I haven't found any.
Hello there!
I've successfully rooted my (Rogers) S5 Active / G870WVLU1ANH3 / kltevlactive using CF Auto Root, blowing my knox and all that, works great.
However, I'm now trying to flash either TWRP or CWM Philz for klte (which may have not been to smart come to think about that, but I recall reading it should work just fine) using Odin, and I can't get into recovery. Whenever I attempt to boot into recovery, I end up with "cannot do normal boot".
I recall reading a SafeStrap for G900 works for the G870, but I can't find the thread again, and don't want to just try and see what happens.
I've also tried flashing a recovery using either TWRP app and RomManager, I have yet to try Rashr, but since all the recoveries I've found are for klte, instead of kltevlactive, I'm slightly worried.
I'm not all that new to rooting, but I'm quite new (and upset ) at the Samsung realm, any chance you guys would know what could get me going with a custom recovery?
I also have a Xposed Framework installed, I read it could cause issues with SafeStrap, but I don't suppose it would affect flashing a rom from Odin/whatever else?
My SELinux on the phone claims to be "Enforcing", if that matters, perhaps.
Thanks!
Im having The same issue please help
Sent from my SM-G870W using XDA Free mobile app
Any luck on this? I've scoured the forums with no luck, although I see people mentioning they have it.
I am experiencing something similar. I have a rooted SM-G870W (Bell). I tried both TWRP and CWM recovery.
Every time I tried to go to recovery mode either via pressing button combo or from adb (adb reboot recovery),
my phone goes into download mode instead, I get "Downloading... Do not turn off target" screen.
Have you also experienced some weirdness with your rooted phone? On mine if I go into boot into recovery
(this is without custom recovery), do nothing but select reboot, I will get "System UI stopped working".
Or "unfortunately mtp application stopped" . I re-flashed the phone with the stock OEM ROM and I don't
get the issues I sated above.
BTW, how did you get xposed framework installed. Mine said "not yet compatible with Android SDK 21 "
Thanks
kachnitel said:
Hello there!
I've successfully rooted my (Rogers) S5 Active / G870WVLU1ANH3 / kltevlactive using CF Auto Root, blowing my knox and all that, works great.
However, I'm now trying to flash either TWRP or CWM Philz for klte (which may have not been to smart come to think about that, but I recall reading it should work just fine) using Odin, and I can't get into recovery. Whenever I attempt to boot into recovery, I end up with "cannot do normal boot".
I recall reading a SafeStrap for G900 works for the G870, but I can't find the thread again, and don't want to just try and see what happens.
I've also tried flashing a recovery using either TWRP app and RomManager, I have yet to try Rashr, but since all the recoveries I've found are for klte, instead of kltevlactive, I'm slightly worried.
I'm not all that new to rooting, but I'm quite new (and upset ) at the Samsung realm, any chance you guys would know what could get me going with a custom recovery?
I also have a Xposed Framework installed, I read it could cause issues with SafeStrap, but I don't suppose it would affect flashing a rom from Odin/whatever else?
My SELinux on the phone claims to be "Enforcing", if that matters, perhaps.
Thanks!
Click to expand...
Click to collapse
kachnitel said:
Hello there!
I've successfully rooted my (Rogers) S5 Active / G870WVLU1ANH3 / kltevlactive using CF Auto Root, blowing my knox and all that, works great.
However, I'm now trying to flash either TWRP or CWM Philz for klte (which may have not been to smart come to think about that, but I recall reading it should work just fine) using Odin, and I can't get into recovery. Whenever I attempt to boot into recovery, I end up with "cannot do normal boot".
I recall reading a SafeStrap for G900 works for the G870, but I can't find the thread again, and don't want to just try and see what happens.
I've also tried flashing a recovery using either TWRP app and RomManager, I have yet to try Rashr, but since all the recoveries I've found are for klte, instead of kltevlactive, I'm slightly worried.
I'm not all that new to rooting, but I'm quite new (and upset ) at the Samsung realm, any chance you guys would know what could get me going with a custom recovery?
I also have a Xposed Framework installed, I read it could cause issues with SafeStrap, but I don't suppose it would affect flashing a rom from Odin/whatever else?
My SELinux on the phone claims to be "Enforcing", if that matters, perhaps.
Thanks!
Click to expand...
Click to collapse
I am having the same issue. Any solution?
I had the "cannot do normal boot" issue as well after doing something dumb which stopped me being able to get into recovery. Was about to flash the original firmware but flashed twrp with odin instead after doing some research. Fixed my problem easily, hope this helps.
Same story with mine
Hi There
I'm having the same issue but all they talk about here are 900 and we have G870W
If someone find any information and how to flash the 870 I would be greatfull
to them because all I could find on the internet pertains to the 900 this is infurating
and by the way any of you have that OEM button in developer?
I bet not again all I've been reading on S5 Active also mention about the OEM button
and this is total BS because we don't have a OEM button. If we can find
a site that could help use with our particular phone and not just the 900
Hello, I have successfully unlocked the bootloader and rooted my S5 Active SM-G870W using this guide and carefully following the appropriate links for my device:
https://r2.community.samsung.com/t5...ooting-Your-Phone-and-Flashing-A/td-p/2496038
Now I would like to flash a custom recovery such as TWRP, but cannot find a recommended version for the G870W. Does anyone have any suggestions on where to find one, or know if any of the ones for the 900 would work on the 870? It's a Canadian version of the S5. Thanks for any help anyone is able to provide!
Does anyone know if the instructions for installing Lineage for SM-G870A/F (found here: https://lineageosroms.com/klteactivexx/) would work on my SM-G870W, kltevlactive? How much of a chance would there be it would brick it? Help much appreciated!
Hey there, is there a kind soul out there who can help me out with the whole process of rooting and installing a custom rom?
I've been searching and trying out things for a lot of hours now, and I've reached a dead end. I have no clue what I'm doing.
I have skype/teamspeak/teamviewer
- Flash TWRP recovery with Odin.
- Wipe in the recovery.
- Flash the rom you want.
Lennyz1988 said:
- Flash TWRP recovery with Odin.
- Wipe in the recovery.
- Flash the rom you want.
Click to expand...
Click to collapse
I've been trying to flash TWRP for some time now, just keeps failing and then rebooting. I will try a bit more and report back. Thanks for your help.
Any idea how I install a kernel?
Even though I've done this stuff before on my SGS1, I'm totally blank.
Update: Found the .tar file after some digging, let's see if it works
Update1: Nothing happened. I am lost tbh. I've got 20+ things downloaded and NONE are working the intended way.
Update2: I think I've succesfully rooted the phone now (even though it should've been already) It says that I have no binaries installed?
Update3: Sorry for venting, but I'm really annoyed at this point. Nothing is working, even though I'm following every thread I see step by step.
Update4: Tried flashing with odinv3.09 instead of v3.04, and now I can't access my recovery anymore. -.-
Update5: I'm giving up, I'm not touching ANYTHING until I can get some help. If I do more and fail, I think I'm going to throw the phone at the wall out of frustration. /vent
PhilGizzle said:
I've been trying to flash TWRP for some time now, just keeps failing and then rebooting. I will try a bit more and report back. Thanks for your help.
Any idea how I install a kernel?
Even though I've done this stuff before on my SGS1, I'm totally blank.
Update: Found the .tar file after some digging, let's see if it works
Update1: Nothing happened. I am lost tbh. I've got 20+ things downloaded and NONE are working the intended way.
Update2: I think I've succesfully rooted the phone now (even though it should've been already) It says that I have no binaries installed?
Update3: Sorry for venting, but I'm really annoyed at this point. Nothing is working, even though I'm following every thread I see step by step.
Update4: Tried flashing with odinv3.09 instead of v3.04, and now I can't access my recovery anymore. -.-
Update5: I'm giving up, I'm not touching ANYTHING until I can get some help. If I do more and fail, I think I'm going to throw the phone at the wall out of frustration. /vent
Click to expand...
Click to collapse
What's your phone model? It is described in the download mode.
Uncheck auto-reboot before flashing the recovery in Odin.
Almost all Odin errors can be resolved by a different usb port and/or different usb cable.
Lennyz1988 said:
What's your phone model? It is described in the download mode.
Uncheck auto-reboot before flashing the recovery in Odin.
Almost all Odin errors can be resolved by a different usb port and/or different usb cable.
Click to expand...
Click to collapse
It's a GTI9505
I tried doing that, I did get Philz recovery installed, now I accidentally deleted the stock rom on my phone.
I did find a good usb port, and should be working (I've got drivers installed)
Philz recovery wants me to root my phone, but I guess I can't do that when I have no ROM installed.
Update: I have succesfully installed a 4.4 kitkat rom. Now, my intention is to upgrade to lollipop, and I'm afraid to break my phone at this point, so if I can get some help it would be much appreciated.
PhilGizzle said:
It's a GTI9505
I tried doing that, I did get Philz recovery installed, now I accidentally deleted the stock rom on my phone.
I did find a good usb port, and should be working (I've got drivers installed)
Philz recovery wants me to root my phone, but I guess I can't do that when I have no ROM installed.
Update: I have succesfully installed a 4.4 kitkat rom. Now, my intention is to upgrade to lollipop, and I'm afraid to break my phone at this point, so if I can get some help it would be much appreciated.
Click to expand...
Click to collapse
You won't break it, just keep doing what you are doing.
First want to say hi and that this site is full of knowledge so any help with my subject will be great.
Got a att s4 sgh-i337 phone. I rooted it before the lollipop ota update was out and everything went fine. Then the lollipop update came out and I followed one of the methods on keeping root and updating to 5.0.1 lollipop on the phone. Everything went fine with that. Still showed root status and never did the phone brick or have any issues in the updating.
At some point though, I did run triangle away because I would have the custom logo and opened padlock when the phone would boot up. I knew it wasn't a huge deal but the counter showed correct and never could just figure out how to get it to go away. Either way, I did run it and I think rebooting twice, the factory loading image came back to it. Now it shows my current status as 0 for the counter and the binary is Official.
I have not tried to load any roms or nothing like this to the phone, just followed the instructions to give it root access so I could run a few different apps and adaway for when I listen to Spotify.
One day, I was trying to install a new version of Words with Friends and it failed because I think wwf was open, but I did go back and install it. For some reason now, my phone never notifies my with a wwf notification when somebody plays me. Every now and then, it might pop up when I restart the phone but that is it. I don't think facebook notifies me everytime also but was more worried about words with friends.
Searching google, it says to go into recovery mode and flash the cache of the phone there. I have done the cache memory in the phone but that has not fixed my problem. When trying to go to recovery, it never works, it would always show, recovery booting and then load the phone up as normal.
I have download quick boot and rom manager since they all have an option to boot into recovery rather than pressing the buttons but it always does the same thing. Reading the web though, it seemed like I needed to install a different recovery than the factory I guess, so using rom manager, I tried twrp and that didn't work so I installed ClockworldMod 6.0.4.7. Rom manager shows that as the current recovery method.
When I try to boot into recovery, it still shows that recovery is booting and then goes straight to loading the phone as it should normally.
Now though, every time I restart my phone, it says recovery is trying to boot but never does.
How do I fix my phone to be able to boot into recovery and it not try to boot every time it powers on. I have tried searching google but I just just can find an answer to my direct problem. I know how to hold the buttons and go to recovery but does not work, and I also know how to get to it from the different app programs(rom manager and quick boot) but they do not work either. It would be nice to get the wwf notifications to work properly again also.
If you need any information from my phone, please ask. Thanks for any help on my matter,
Charlie
Odin stock and start over.
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
creepyncrawly said:
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
Click to expand...
Click to collapse
Thanks for the replies guys, I really don't know a whole lot about rooting other than following instructions about it. I was unaware you could not use the twrp or cwr as a recovery. My recovery did not work before so that is why I was trying to install those. I knew you could not install custom roms but I did not know that you could not use rom manager to install custom recoveries.
I appreciate the help so far and I will look into that thread you mentioned. I haven't read it but will this take me back to stock lollipop 5.0.1 and I just reinstall apps or will I have to re-root the phone.
Charlie
please delete, sorry
Charlie
You have to go back to 4.4.4, to the nb1 base, root with towelroot, and then use the keeproot method to get back to 5.0.1 rooted. The instructions are in the guide, and also a link to the keeproot thread is there.
By the way, for future reference, questions, help and troubleshooting issues should go in the Q&A forum, not the general forum.
not having any luck
Ok guys,
I am trying to follow the guide but not having much luck.
I downloaded the I337UCUFNB1_4.4_Stock_Odin_tar and put it in the AP Odin file. I'm not sure if I should be using it or the other file named I337UCUFNB1_4.4_Rootable_Stock_Odin_tar to begin with. The instructions said to use the first one so that is the one I was trying to use.
After putting the first file in the AP slot of Odin and hitting start, it begins to try to do it's thing and then says it fails!
What do I do now? Am I doing something wrong or what because I'm trying to follow instructions but not having much luck.
Please help. Sorry for posting in the wrong area also in the beginning.
Charlie
I'm screwed
Now when I turn my phone on, it says Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again?
doing better now
Pretty sure I got it going finally. I changed cords and then changed ports on my computer and it finally did go back to stock without an error. I'm currently back on Lollipop and rooted so now is the fun of reinstalling contact info and anything else. So far I have not rebooted but it was not showing the recovery booting option when it did reboot. Hoping my notifications work properly now also!
Thanks!!!
Charlie
Hello there,
I am having a little bit of an issue with a new Galaxy Note 4 that i got for my wife. We both bought our devices yesterday, mine from Three, and hers from EE (we are in the UK), both SM-N910F, so i proceeded to root my device and it worked all great. So earlier today i started the exact same procedure, unfortunately, my wifes Note 4 got stuck in a Recovery Boot Loop, and i genuinely don't understand what is happening.
As for the rooting method, i went with the [SM-N910*] CF-Auto-Root and choose the right .tar file, or else it wouldn't of had worked on the first device.
I have read quite a few posts, saw a few videos on youtube, but it far beyond me. I have seen a few people mention that i need to download the German (?) version of the Stock firmware, and then flash it. I seem to have found a link for it on SamMobile but it's gonna take 5 hours to finish, and i don't understand why i would download the German Stock firmware, is that the correct one for her device ?
At this point, is there any way around it ? Why did my device which is the same work perfectly, but not hers ?
I would appreciate any and all help, if you could make it quite detailed for me i would appreciate it even more.
Thank you!
Hi @Vaskie!
Can you enter in download mode?
Hello there @_mone, the following has happened since i posted:
Went ahead and flashed the following: N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_HOME.tar and it made the device reach the home screen, from there i attempted to root using the same method which worked, but it ended installing a few extra applications, which i don't understand how. I also don't understand how flashing a new stock rom didn't make me start the device from the beginning, it already had all my information and went straight to the home screen ready to use. I feel quite confused if im honest.
On the other hand, most things seem to be working perfect, but i am having some issues with the front camera. I have two Note 4s, both bought yesterday from the same place, but one was flashed with the Stock rom (N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_HOME.ta r) due to being stuck in a boot loop. The front camera seems to be massively over exposed compared to the other Note 4, not just a little bit either, making it almost unusable.
Would anyone be able to help ?
Vaskie said:
I also don't understand how flashing a new stock rom didn't make me start the device from the beginning, it already had all my information and went straight to the home screen ready to use. I feel quite confused if im honest.
Click to expand...
Click to collapse
That's because you "dirty" flashed a new ROM on top of the old one.. it was like an "update".
What I suggest you (because you already rooted your phone and your knox is 0x1) is to flash TeamWin Recovery Project from ODIN and then flash a TW ROM from the Galaxy Note 4 Android Development (Snapdragon) page
To do so download "twrp-2.8.7.0-trltexx.img.tar" from here, put your phone in download mode, connect it to the pc via usb, from the pc launch odin, let it recognize your phone, add the downloaded .img.tar file on the pda button, click on the "start" button and let it flash the recovery.
Now download a TW ROM like _alexndr's DevBase from here and this modem and this bootloader.
Then put the downloaded ROM (N910FXXU1POF2_DevBase_alexndr.zip) in your external SDcard. Reboot your phone in recovery mode. From TWRP go Wipe/AdwancedWipe/ and tick DalickCache, System, Data, Internal Storage, Cache and "Swipe to Wipe". After go back to the first page, hit "Install" search "N910FXXU1POF2_DevBase_alexndr.zip" in "/external_sd" and install it. Wipe Dalvick and Cache again and reboot into download mode. Again connect your phone to the PC and launch ODIN now put the downloaded modem "CP_N910FXXU1POF1.tar.md5" in the CP button and the bootloader "BL_N910FXXU1POF2.tar.md5" in the BL button and click on the "start".
Once it is done switch off and on your phone and start again with the latest samsung rom for N910F already with root, busy box and all the fixes by _alexndr
And let us know if you still have problems.
Thank you very, very much for the very well detailed reply @_mone
I will attempt to go ahead with your explanation tomorrow. Would that somehow fix the camera, and i guess the other question is.. is the front camera issue that i explained myself above to do with me "dirty flashing" ?
Is there anything inherently wrong with "dirty flashing" ?
Thank you yet again!
Nothing wrong with dirty flashing.. but sometimes doing so you can create conflicts between old and new rom or leaving "bugs" from the old to the new generating problems in your new os that may wont be there if you performed a clean install. :good: