Related
Guys,
I have tried several roms and decided to odin back to 2.1, updated to 2.2 and just clean it up a bit and leave it as is for a while.
Everything went just fine, but yet again this damn clockwork recovery issue which I knew I would get but thought maybe it would be solved by now on rom managers side.
So, in rom manager, it shows that current recovery is 2.5.1.2 which matches the latest, however, when I reboot into recovery, I am still getting the standard 2.2 recovery console.
I tried searching but not sure what the issue is, of course I get the signature issue when I try to update package.
It's wierd that it's showing it's installed but it's not actually booting into the correct recovery console.
Thanks.
kero4 said:
Guys,
I have tried several roms and decided to odin back to 2.1, updated to 2.2 and just clean it up a bit and leave it as is for a while.
Everything went just fine, but yet again this damn clockwork recovery issue which I knew I would get but thought maybe it would be solved by now on rom managers side.
So, in rom manager, it shows that current recovery is 2.5.1.2 which matches the latest, however, when I reboot into recovery, I am still getting the standard 2.2 recovery console.
I tried searching but not sure what the issue is, of course I get the signature issue when I try to update package.
It's wierd that it's showing it's installed but it's not actually booting into the correct recovery console.
Thanks.
Click to expand...
Click to collapse
delete whatever update.zip you
http://forum.xda-developers.com/showthread.php?t=849028
get the 1 from there, reinstall packages twice and it should go to clockwork recovery
Okay, obviously option b would be better, however, will I have to reroot after if I use option B?
Nadda, same results, it's okay though, I'll live with it for now since I'll keep 2.2 with all the crud removed for now.
Please read that guide. You've missed some key points. I'd explain more, but I'm hanging with my kid.. Read the guide.
had the same problem i used this method and it worked for me
http://forum.xda-developers.com/showthread.php?t=833423&highlight=recovery
First of all, I want to thank everyone working on the CM7, CM9, CM10, SGT7, TWRP, CWM projects for the Nook Tablet. I've really been enjoying trying different ROMs on my Nook Tablet.
I started with CM7, and it ran pretty well. I also tried the CM9 (NX-Fire?) port, and I liked it as well.
I have been using the SGT7+CM10+Cherry Picks and it has been fine up to the 27/9 release. I cannot run anything higher than this on my NT.
I have tried CWM (up to 6.0.1.2) and TWRP (up to 2.2.2.0) to flash the newer ROMS, but the ROMS will not boot. The screen blanks, and after a time, it goes back to the boot screen.
I also can't seem to use the CWM 6.0.1.5 or TWRP 2.3.1.1 from the SGT7+CM10 thread.
I know I have the 16GB Nook Tablet. I have repartitioned the userspace, as mentioned in other threads. I can't help but feel like I'm missing a step somewhere.
Presently, my NT is running TWRP 2.2.20 and SGT7+CM10+Cherry Picks 27/9. Any one have any hints? A thread on the boards I have missed? Any help would be appreciated.
Again, thanks for all the hard work!!
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Moved. Questions belong in the Q&A section.
Thanks
AvRS
demetris_I said:
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Click to expand...
Click to collapse
Thanks! I'll try that this weekend. I knew I was missing something.
demetris_I said:
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Click to expand...
Click to collapse
Sorry, but how does one manually update a recovery? I've tried flashing the newer TWRP from CWM as well (from an older version of CWM), and while the flash doesn't fail, it won't let me boot into TWRP, and the new CWM crashes before I can do anything. I've also tried flashing the recovery from fastboot, but I get a "bad boot magic" error when I try to boot.
Just flashed couple of days ago: pretty nice ROM
Besides annoying "SD card unmounting" problem I found that B&N Nook app does not work, it just keeps restarting, some error message shows up but goes away so quickly I can't read it. I wiped before I installed the ROM and reinstalling the app didn't help.
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
jnorrisman said:
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
There is a search function on here...
Sent from my NOOK Tablet running CM10
jnorrisman said:
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
The OP in the developers section has links to both CWM and TWRP for your use. Remember, SEARCH is your FRIEND!
play store/goomanager closing
First let me say this rom is awesome! I had no idea my nook could run this smoothly. The only problem I seem to have is that on the newest build(10/25) both playstore and goo manager will open then close. I have tried clearing the app cache, re flashing rom and gapps, full wipes then reflash. I also tried reflashing the newest gapps without success. The 10/12 build works with both play store and goo manager. I am using the 10/12 build now so no worries if it can't be fixed. Again thanks for the time and effort on an awesome rom:good:
edit: I am using the latest twrp for my recovery (also awesome). the tablet is the 16gb version
Same problem as OP, latest SGT7 not loading
I am having the exact same problem as Byron and Spurious. I've really enjoyed this series of ROMs up until the last couple, which give the same symptoms as described in the OP - the ROMs will appear to load up to a certain point, then the device reboots. For me, the the device will load up to a seemingly random point -- sometimes it will reboot itself during the boot animation, and once it got all the way to the point where it starts updating the applications. But it never actually finishes booting up before it reboots itself.
In addition, the latest CWM and TWRP do not work for me. TWRP does not come up at all, and sometimes CWM will come up and I can move around the menus for a few seconds, then it hangs. It happens whether they were flashed via fastboot or SD, I've tried every combination. I can fastboot back to TWRP 2221 or CWM 6013 and they work fine.
I've been keeping my NT (16G) updated with the latest builds since early ICS and everything has worked as described up until now. I follow all instructions to the letter as regards to wiping, etc. so I don't think I'm doing anything wrong.
Is anybody else having the same issue with these latest ROMs? Byron, Spurious - did you get yours sorted? Could it be a hardware issue?
jarvz said:
I am having the exact same problem as Byron and Spurious. I've really enjoyed this series of ROMs up until the last couple, which give the same symptoms as described in the OP - the ROMs will appear to load up to a certain point, then the device reboots. For me, the the device will load up to a seemingly random point -- sometimes it will reboot itself during the boot animation, and once it got all the way to the point where it starts updating the applications. But it never actually finishes booting up before it reboots itself.
In addition, the latest CWM and TWRP do not work for me. TWRP does not come up at all, and sometimes CWM will come up and I can move around the menus for a few seconds, then it hangs. It happens whether they were flashed via fastboot or SD, I've tried every combination. I can fastboot back to TWRP 2221 or CWM 6013 and they work fine.
I've been keeping my NT (16G) updated with the latest builds since early ICS and everything has worked as described up until now. I follow all instructions to the letter as regards to wiping, etc. so I don't think I'm doing anything wrong.
Is anybody else having the same issue with these latest ROMs? Byron, Spurious - did you get yours sorted? Could it be a hardware issue?
Click to expand...
Click to collapse
Sort of. I figured out what I was doing wrong flashing the recovery from fastboot (you apparently have to extract the .img file from the zip) but was still having the exact same issues with CWM and TWRP as you. I've managed to get a newer version of CWM installed without it hanging by using the 5 touch enabled one from here. Using this I still have the same issues with the meghd00t rom going into a bootloop though.
I noticed OP said he has repartitioned his Nook, and I have as well. I wonder if this could be causing problems, have you done this as well, jarvz? Does anyone else have any input about if repartitioning could effect this?
spurious_access said:
Sort of. I figured out what I was doing wrong flashing the recovery from fastboot (you apparently have to extract the .img file from the zip) but was still having the exact same issues with CWM and TWRP as you. I've managed to get a newer version of CWM installed without it hanging by using the 5 touch enabled one from here. Using this I still have the same issues with the meghd00t rom going into a bootloop though.
I noticed OP said he has repartitioned his Nook, and I have as well. I wonder if this could be causing problems, have you done this as well, jarvz? Does anyone else have any input about if repartitioning could effect this?
Click to expand...
Click to collapse
Yes I have repartitioned mine as well, so that must be it. I was hesitant to go to the 5-touch because it was indicated in the thread that there was no way back after you do the firmware update, and so far there is only one rom that worked with the new firmware, so I didn't want to take a chance.
At least I'm pretty sure I'm not doing anything wrong, lol.
jarvz said:
I was hesitant to go to the 5-touch because it was indicated in the thread that there was no way back after you do the firmware update, and so far there is only one rom that worked with the new firmware, so I didn't want to take a chance.
At least I'm pretty sure I'm not doing anything wrong, lol.
Click to expand...
Click to collapse
Yeah, I don't have the new touch firmware installed either. CWM worked fine, though TWRP didn't seem to work properly (maybe it needs the new touch firmware?).
Do you know if there is any mention of re-partitioning causing an issue? I looked in the rom dev thread but didn't notice anything. I guess one of us who are seeing this issue could post there to see if anyone knows what could be causing this.
I finally got it to work. My PC is running Ubuntu, so YMMV.
Here is what I did:
1. Used "gparted" to create 2GB FAT32 partition that is bootable.
2. Used the instructions in the this thread thread to create a bootable SD disk that boots into CWM 6.0.1.2.
3. CWM 6.0.1.5 just doesn't seem to work on my Nook Tablet. So, I downloaded CWM 6.0.1.3 from here
4. I downloaded the latest ROM here
5. Downloaded the latest gapps: here
6. Copied the CWM, ROM, and gapps to the SD disk.
7. Inserted the SD and booted the Nook Tablet.
8. On first boot, it boots to CWM 6.0.1.2, so I flashed the CWM 6.0.1.3, and rebooted.
9. This time it boots to Cyanoboot, so I entered the boot menu and selected EMMC Recovery.
10. From CWM 6.0.1.3, I formatted /storage, and did a factory wipe. (I didn't format /storage the first time, and the wireless would not come up.)
11. Installed ROM from SD card.
12. Installed gapps from SD card.
13. Rebooted, this time letting cyanoboot boot from EMMC.
14. Profit!
I haven't tried 6.0.1.4 to see if that would work.
Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
You can install a kernel to see if that will solve the issue, but as far as I can see, the Carbon devs do not provide a stand alone kernel for their rom. You could use AJK or one of the other kernels though. Or you could just reinstall the rom to see if it would clear up the problem.
Or, you could extract the zImage from the full rom and use Mobile Odin.
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
jjack0310 said:
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
Click to expand...
Click to collapse
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
creepyncrawly said:
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
Click to expand...
Click to collapse
I followed Step 3a on this post: http://forum.xda-developers.com/showthread.php?p=18576627#post18576627
Unfortunately, for some reason, ODIN Lite was not recognizing DD_03042012.zip file. So I went with Siyah and downloaded the TAR file used ODIN to get the clockwork mod. It worked.
Now the problem is I cant restore my backup. I know the same backup has worked before, not it is giving me an error "Error while restoring /system". wth!
I dont remember what version of Clockwork Mod I had. I know it was an older version, becuase it didnt have touch.
How do I get a previous version of CWM?
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Actually,
Creepyncrawly, thanks for your help.
I downloaded ShoStock 3 and flashed it to get the previous version of CWM, and then was able to do a restore.
Sigh.. no harm done.
You can have your thread back... good luck!!
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
Yes, as stated by creepyncrawly, u can use mobile odin or regular odin to flash a kernel.
But i would suggest doing a MD5 check on the Rom u downloaded, because the Rom u flashed may be that of a corrupted download. If MD5 doesn't match then redownload, check MD5 and if good, reflash the Rom.
.....or maybe the nightly is messed up.
Sent from my SAMSUNG-SGH-I747 using xda premium
Mighty_Rearranger said:
Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
Click to expand...
Click to collapse
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
I can see why you could be upset that someone hijacked your thread.
I only see one question in your original post, which I believe I answered. You also requested assistance which I thought I provided.
Let me be a little more specific for you. Yes, you can flash just a kernel without re-flashing the system. However, you will need either an Odin flashable tar of the kernel, or you will need to install Mobile Odin and then you can flash a kernel directly from a zImage file.
However, I think 4-2ndtwin has the right of it. It was probably a bad flash, even though the phone booted normally. You should consider re-flashing the entire rom.
If you are not clear about anything, please ask questions.
Never mind.
I concluded it wasn't worth it just because I was lazy backing up stuff.
I used this: http://forum.xda-developers.com/showthread.php?t=1525821, then flashed a clean ROM.
Thanks for the help, you guys are awesome.
New to this - I really apologize if this has been covered before but I've been searching all evening and not coming up with a definitive answer.
What's the easiest way to remove a custom recovery (like twrp) and go back to stock? Still on the stock rom, just have custom recovery. I manually deleted a nandroid backup using a file manager from my sd card yesterday, and now when booting into recovery it sits on the twrp screen for easily 10-15 minutes. I can't fathom why that would have an effect on the start up time but that's all I can think of that changed. I've tried re-installing twrp via goomanager - no change.
Is there a way to do so without using usb? I'm curious because the first S4 I had, the usb port went bad after only a month and I was in a panic that I wouldn't be able to get it back to stock (until I finally got it to work long enough to flash it with odin). Really don't want to risk that happening again.
Looking to run some roms once I think I understand at least half of what I'm doing, but trying to be cautious. I'd like to keep twrp but I want to make sure it's working right by loading a clean install of it.
Thanks in advance.
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
gadget! said:
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
Click to expand...
Click to collapse
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
You flash it via recovery. Put in your sdcard/internal boot to recovery amd use the install zip option. Navigate to where it is and flash away.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
Yes, it is a flashable zip, just flash it in the recovery you have now.
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
margentieri said:
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
Click to expand...
Click to collapse
Answer would be device specific
Sent from my cm_tenderloin using xda app-developers app
Thanks Gadget, Hex. TWRP 2.5.0.2 works great. But just for future reference, is the only way to revert to the stock recovery by flashing a stock device image via odin over usb? So if the USB port were to fail entirely, I would be SoL - correct?
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
OK, from your post it looks like you have done this before. To be sure lets go through the motions one more time.
Your device is updated to 4.4.4 NK4 the latest KitKat version. It's rooted you have supersu icon and run a root checker. First download again ( in case you got a bad download ) a copy of Philz CWM version 6.48.4 here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ use "phil'z_touch_6.48.6-hlte.tar.md5" . I like to use odin version v1.85 it's little older but very stable, here is a link https://mega.co.nz/#!oA5xzTAL!LXoVWB...ZlOMSWdRGVX6Uo now flash the .tar file with odin. Make sure you let device boot up on it's own back to the OS, do not pull the cable and boot the device yourself. Then try and boot into recovery.
If it bootloops again, I would backup all your data to the PC desktop, and then do a factory reset get back to bone stock ( that means when your in download mode it says Samsung Official status not custom ) so many times I have seen folks with an unrooted device where the bootloader still says custom and you end up with a dirty flash or worse. It may take a couple factory resets to get back to stock, it doesn't always take the first time. When I flash a custom rom and then decide to go back to stock, I flash the rom two or three times to make sure I'm bone stock.
If the factory reset doesn't work you may have to flash a new stock NK4 OS. Then root again and install the recovery. Here is my thread with all the info you need http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 , Enjoy !!!
Thanks for taking the time to give me a detailed response. Sounds like I'm gonna have to wait till Wednesday or Thursday when im off work and have some time to do this, but yeah, I was thinking maybe just a factory reset, but I'll use your links and try it one more time first. I'll let ya know. Thanks again
Do you have another link to the older Odin (1.85).the link says the file isn't there... Thanks again
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Psychotic-Cerebellum said:
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Click to expand...
Click to collapse
Awesome, Ya idone is the man when it comes to enabling the mobile hotspot be careful what you click with app. I will correct that link. Thanks
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
That's the problem Knox security is getting harder flash engineering boot loader again then try rashr in app store to flash philz