Related
Alright, after bricking my phone yesterday and spending hours finally unbricking it, I've decided that I'm just not quite ready to play around with ROMs on the Transformer Prime. At least, not until they get a little more stable.
However, I'm finding myself unable to get my Prime back to stock ICS...
What I'm currently running is a Cyanogenmod 9 nightly build from 3/4/12. Through Rom Manager I was able to install the latest CWM (5.8.2.0) BEFORE the whole bricking incident. Now I can't even get my WiFi turned on...so I suppose any further changes via Rom Manager are halted.
Anyway, I used Vipermod's tool and was able to unroot successfully. I then went into settings and attempted to perform a factory reset. However, my tablet booted up with the same, Cyanogenmod boot screen and brought me back without any changes.
So then I tried using ADB....plugging my Prime in and typing "adb reboot recovery". But I get the message "adb server is out of date. killing..." then on the next line * daemon started successfully *. My device resets...but same thing...cyanogenmod...no CWM...no changes.
I thought maybe ADB wasn't working because I had unrooted. So I re-rooted, again using Vipermod. I see superuser again now...but ADB reboot recovery is still not working.
So now I'm stuck... I seemingly can't perform a factory reset with my build of cyanogenmod, and I can't find any way of getting back to recovery (I've tried selecting recovery reboot after pushing the power button, tried selecting recovery from within Rom Manager and tried with ADB...all failed). Again, all I want to do is factory reset, and get my stock ICS back. Can anyone please help me out?
You won't get back a total stock ICS easily
You can't use Factory reset after unlocking the Prime and installing CWM
adb reboot recovery does not work
The only way to reboot to recovery is via holding down Vol_Down on boot and then pressing Vol_Up
non working wifi is because you have a wrong kernel
you can't boot to recovery because it's most likely wiped
Try installing CWM from Rom Manager again, if that does not work follow the guide in the dev section to flash another CWM version manually.
Then reboot to recovery and flash another ROM.
Make sure the ROM contains a new kernel, so your Wifi is working again.
Diamondback said:
You won't get back a total stock ICS easily
You can't use Factory reset after unlocking the Prime and installing CWM
adb reboot recovery does not work
The only way to reboot to recovery is via holding down Vol_Down on boot and then pressing Vol_Up
non working wifi is because you have a wrong kernel
you can't boot to recovery because it's most likely wiped
Try installing CWM from Rom Manager again, if that does not work follow the guide in the dev section to flash another CWM version manually.
Then reboot to recovery and flash another ROM.
Make sure the ROM contains a new kernel, so your Wifi is working again.
Click to expand...
Click to collapse
Thanks again Diamondback!
To clarify, I don't really need stock ICS. What I need is a working ROM with Android Market (Google Play, WTF?), WiFi, a web browser...all that. I've heard that Virtuous is good, so I'll probably go that direction.
But more importantly, I need a way to install it, and the only way I know how to do that is a) using Rom Manager (which apparently doesn't work with the Prime at the moment), or b) doing it through CWM (which isn't working for me at the moment either).
As far as your suggestions go, I can't use Rom Manager to install CWM again, because my WiFi isn't working. However, I have found instructions online for flashing CWM manually, but it involves installing fastboot, and doing something with a "blob". I don't know what a blob is, but in your unbricking post, you specifically state:
Do not, I repeat, do not try to flash a stock ASUS ROM/blob file.
Doing this you will most likely hard brick your Prime.
I'm not sure if that applies in this case, but the last thing I want to do is brick my device again.
This is the post I'm referring to:
http://www.theandroidsoul.com/install-cwm-5-8-2-0-on-transformer-prime/
Can you advise whether this method is safe, or point me in the direction of a safer method for flashing CWM manually?
Thanks!
scaryslocuda said:
Thanks again Diamondback!
To clarify, I don't really need stock ICS. What I need is a working ROM with Android Market (Google Play, WTF?), WiFi, a web browser...all that. I've heard that Virtuous is good, so I'll probably go that direction.
But more importantly, I need a way to install it, and the only way I know how to do that is a) using Rom Manager (which apparently doesn't work with the Prime at the moment), or b) doing it through CWM (which isn't working for me at the moment either).
As far as your suggestions go, I can't use Rom Manager to install CWM again, because my WiFi isn't working. However, I have found instructions online for flashing CWM manually, but it involves installing fastboot, and doing something with a "blob". I don't know what a blob is, but in your unbricking post, you specifically state:
Do not, I repeat, do not try to flash a stock ASUS ROM/blob file.
Doing this you will most likely hard brick your Prime.
I'm not sure if that applies in this case, but the last thing I want to do is brick my device again.
This is the post I'm referring to:
http://www.theandroidsoul.com/install-cwm-5-8-2-0-on-transformer-prime/
Can you advise whether this method is safe, or point me in the direction of a safer method for flashing CWM manually?
Thanks!
Click to expand...
Click to collapse
My warning only applies to STOCK blobs (like the ones in the official asus updates from their website).
The guide you posted seems to be fine.
Great! I'll give it a shot tonight.
One last thing... If I find that Virtuous isn't the best fit for me, would you advise AGAINST installing the stock firmware posted over at Android Soul? Is this what you would consider a "stock blob" or is this something different? Here is the link:
http://www.theandroidsoul.com/trans...h-cwm-recovery-on-unlocked-bootloader-primes/
That's a zip, not a blob, you can flash that
Diamondback said:
That's a zip, not a blob, you can flash that
Click to expand...
Click to collapse
Worked perfectly! Thanks so much for your help Diamondback...again!
My AT&T Samsung Captivate i897 has gone bad so I just purchased a used Note i717 (i tis on the way). I like the larger format, dual cameras +flash, LTE speed.
The phone is already in stock ICS 4.04 (build UCLF6). I would like to 1) root, 2) add CWM, 3) flash to final CM9 stable (like I have on my Captivate). I have read and read threads and posts to the point that I am a little dizzy. My questions are:
1) what is the best way for ICS 4.04 stock to be rooted and injected with CWM (the posts all seem to be targeted at the original GB)?
2) if I get in trouble and brick it (always seems to happen on my root attempts), is there a SuperOneclick or Heimdall or Odin approach that will push stock software (or any) so that I can retry 1 - in the past Heimdall was the savior)?
Thank you and I look forward to participating in this forum :good:
then by all means, visit the "note super everything thread" at the top of the general section.
Once there, scroll down to the big green arrow, and go from there..
And welcome to the I717 forums....g
gregsarg said:
then by all means, visit the "note super everything thread" at the top of the general section.
Once there, scroll down to the big green arrow, and go from there..
And welcome to the I717 forums....g
Click to expand...
Click to collapse
I do not see a big green arrow and am in graphics more. My apology. Am I blind or old or something?
I've seen the thread and slooked into the links seem to be stock GB specific in terms of rooting and adding CWM. Some talk of ICS 4.03 not 4.04 but still not rooting. Will one of the rooting tools (DA_G's) help me to get going?
At the bottom of the post I see the following but interestingly enough the CWM link assumes root. So, at a basic level I am looking to first root with ICS 4.04
Again, THANK YOU and sorry for feelign like an almost Noobie.
{ROOTING OFFICIAL ICS 4.0.4 I717UCLF6}
[Recovery] Clockwork-mod Based Touch Recovery - 04/14/12
or
[RECOVERY] TWRP2.2.2. TeamWin Recovery Project 7/17 Bugfixes
[ROOT] Superuser 3.0.7 for ICS 4.0.3 Leak
USB Driver for ATT I717Galaxy Note
tonyo123 said:
I do not see a big green arrow and am in graphics more. My apology. Am I blind or old or something?
I've seen the thread and slooked into the links seem to be stock GB specific in terms of rooting and adding CWM. Some talk of ICS 4.03 not 4.04 but still not rooting. Will one of the rooting tools (DA_G's) help me to get going?
At the bottom of the post I see the following but interestingly enough the CWM link assumes root. So, at a basic level I am looking to first root with ICS 4.04
Again, THANK YOU and sorry for feelign like an almost Noobie.
{ROOTING OFFICIAL ICS 4.0.4 I717UCLF6}
[Recovery] Clockwork-mod Based Touch Recovery - 04/14/12
or
[RECOVERY] TWRP2.2.2. TeamWin Recovery Project 7/17 Bugfixes
[ROOT] Superuser 3.0.7 for ICS 4.0.3 Leak
USB Driver for ATT I717Galaxy Note
Click to expand...
Click to collapse
Go to the last page in that thread. I posted an easy, fool-proof root method. It was simple enough that even I could do it.:laugh:
root for the ICS 4.0.4 is easy....
It consists of Odin pushing a CWM image, and flashing SU from your new found recovery.
But there are a few tips that will help you out...
follow teyshablue...and you'll be rooted in 10 minutes....g
THANKS
I thanked you both. My new Note is in tomorrow overnight via USPS overnight. Cannot wait!!! Teyshablue, the post with step-by-step pictures is excellent. It removes the risk of doing parts of this incorrectly, which I always do in geting to root and CWM (usually because somehting is always different than the directions say). I will do first thing upon receipt tomorrow and report in tomorrow. Obviously, I will spend the rest of my holiday weekend reloading my apps (how fun...really) OUTSIDE.
tonyo123 said:
I thanked you both. My new Note is in tomorrow overnight via USPS overnight. Cannot wait!!! Teyshablue, the post with step-by-step pictures is excellent. It removes the risk of doing parts of this incorrectly, which I always do in geting to root and CWM (usually because somehting is always different than the directions say). I will do first thing upon receipt tomorrow and report in tomorrow. Obviously, I will spend the rest of my holiday weekend reloading my apps (how fun...really) OUTSIDE.
Click to expand...
Click to collapse
Yeah, the video tutorial saved my bacon!:good:
Okay I'm planning on doing similar tonight with my newly arrived refurbed i717. It shipped with ICS.
I'm confused however...if I simply want to flash a custom ROM (versus running rooted stock ICS), I've seen threads stating that I don't need Root, but instead install TWRP2 via Odin from here:
http://forum.xda-developers.com/showthread.php?t=1584576
...then flash custom ROM via TWRP2 recovery.
Am I missing something? Searching on Q&A seems to indicate some worrying issues about attempting this method of root on these refurbed Note's running ICS:
http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
TIA
Root is your first step.....as you need the custom recovery to flash the roms...
ultimately.....pushing a recovery via Odin, is giving you root....g
You don't need to root to flash a ROM. You can flash cwm through Odin then flash the twrp zip if that's the recovery you desire. I'm not sure if all the bugs are worked out on the twrp Odin tar. Once you flash a recovery, you can make a backup of your stocker and then flash your ROM of choice. Again, you do not need to root. Flashing a custom recovery through Odin does not root your phone, and is the first step. If you wish to root , then you would flash the su binaries zip in a custom recovery. I just don't want there to be any confusion.
Gubment Cheeze
Oh boy...want to be sure here...
Froid, I think what you type is consistent with Teyshablue's process.
1) This process first adds CWM (the custom recovery) using ODIN with the file “odin_ni717_cwm_recovery_b4.tar" in PDS slot. I assumed it needed root first but here CWM is the first step.
See here:
http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
1A) Then, I think I should nandroid back up the Stock ICS ROM here with CWM? I think so but it's not in the guide.
2) The next step using CWM is to load "Superuser-3.0.7-efghi-signed.zip ". So this roots correct Froid?
3) After that, then I can nandroid back-up rooted ICS ROM again with CWM.
4) Then can clean cache, Dalvik, and flash CM9 with CWM (Do I need to do some factory reset full wipe before adding CM9 ROM)?
Am I missing anything?
You are flashing cwm recovery through Odin with that file. That process does not root your phone. You don't have to install the superuser zip file through cwm if you don't want to root(this is what gives you root). You can skip that step if you desire. Once you put the cwm tar file in the PDA slot and hit run, Odin will flash the custom recovery and reboot your phone. From there you can 3 button into recovery, make a backup, then flash your ROM of choice.
Gubment Cheeze
---------- Post added at 08:36 PM ---------- Previous post was at 08:25 PM ----------
On a side note, make sure you do your homework on the available recovery options before diving in head first. I personally use TWRP and would highly recommend.
Gubment Cheeze
Froid said:
You are flashing cwm recovery through Odin with that file. That process does not root your phone. You don't have to install the superuser zip file through cwm if you don't want to root(this is what gives you root). You can skip that step if you desire. Once you put the cwm tar file in the PDA slot and hit run, Odin will flash the custom recovery and reboot your phone. From there you can 3 button into recovery, make a backup, then flash your ROM of choice.
Gubment Cheeze
Click to expand...
Click to collapse
Froid, mind checking me one more time? I edited my prior post (with numbered steps) as you were typing the reply. I am not sure about skipping the rooting step but I know you are probably right. I think I will run through the process as stated adding the stock backup then the rooted backup. Sound okay?
MUCH THANKS !!!! :good:
On the recovery program, I have only used CWM while I had my Captivate. TWRP is new to me. More options better program?
That will absolutely work. Not a bad idea to have both stock and rooted backed up. Always full wipe when flashing a new ROM. follow the OP of the ROM you're flashing. I don't use cwm so do some research on whether or not you need the latest version to flash a cm9 ROM. There was an issue in the past with using an older version of cwm. Not sure if that still exists. Good luck
Gubment Cheeze
Rooting Upgrading Anxiety
thanks all for the help, knowing that I just purchsed a close to $500 (shipping and accesories) used phone and knowing how many times I messed up my Captivate did not allow me to sleep well last night. I really want to do this right and not be panicked with a messed up Note to start with. I will sleep better knowing that I have a thought out and tested approach for when it arrives tomorrow.
And yes, TWRP has a few more options. I was always a fan of cwm, and its a great recovery. I just prefer TWRP for its UI, backup speeds, and being able to name the backup beforehand.
Gubment Cheeze
Let me know of progress
Madtowndave, assuming there are no file problems (there should not be from what I see) I think the process by Teyshablue that I link to should work fine and appears low risk. As I mentioned, I would do a backup of the Sock ROM after the first ,ajor step of loading CWM.
For now, I will stick to CWM because I have used it and know it. Don't want too many variables or new learnings at the moment. The risk would be too high and I am unfamiliar with the Note (for example, I already see that recovery and download mode button combinations are different - little things like these have tripped me up in the past).
Madtowndave, let me know what process you used and how it went, and if any steps caused you problems.
tonyo123 said:
Madtowndave, assuming there are no file problems (there should not be from what I see) I think the process by Teyshablue that I link to should work fine and appears low risk. As I mentioned, I would do a backup of the Sock ROM after the first ,ajor step of loading CWM.
For now, I will stick to CWM because I have used it and know it. Don't want too many variables or new learnings at the moment. The risk would be too high and I am unfamiliar with the Note (for example, I already see that recovery and download mode button combinations are different - little things like these have tripped me up in the past).
Madtowndave, let me know what process you used and how it went, and if any steps caused you problems.
Click to expand...
Click to collapse
Yes, naming backups is good as I have had to go back and just had many dated files which became almost hunt and peck in finding the exact one I needed. As for CWM, I also used the Devil Kernel, not sure if it is available for the Note, that beyond speed, also gave a few added optionsto CWM including a file manager which came in handy in swapping out system files (like CM9's Trebuchet launcher being replaced by a lighter version). But, a step at a time. I only used the added kernel because the Captivate with single core was a bit speed challenged (but CM9 made it like new).
Success!!
I'll try to be as detailed as possible.
1. Use stock USB cable and plug in on a back USB port that is on the motherboard.
2. Let Windows install the i717 USB drivers. Annoyingly, whenever I was in a different mode (specifically, USB mass storage or d/l mode), Win7 would install/update more drivers. After 3 total device driver installs from the different modes, I rebooted my pc.
3. I d/l Odin 1.85 and the Odin .tar link under 4-14-2012 from here: http://forum.xda-developers.com/showthread.php?t=1584576
I decided to use the CWM touch version...very similar to Cappy CWM to go back in the menu you use the back capacitive button.
4. I decided on a custom ROM...For me, I loved Mosiac on the Cappy back in the day, so I chose from the fine folks at The Collective here: http://forum.xda-developers.com/showthread.php?t=1773229
5. Pushed the ROM and GApps zip files via USB
6. Run Odin as Admin, click on PDA and selected the .tar from step 3.
7. Put phone in d/l mode and plug in to USB, Odin Com port lights up...Click Start
8. After the phone rebooted, (wait for the haptic feedback) I pulled the battery
9. 3 fingered into Recovery and now in good ol' CWM. The one trick here is that the .zips are under Internal Storage menu option, not SD Card (unless of course you file transferred them to an external sd card)
10. Followed installation steps in ROM OP and flashed zips from Step 5.
11. Enjoy!
I did not need Root, but am now rooted by virtue of the custom ROM. I also did not Nandroid backup the Stock ROM since if I ever need to go back to Stock, I'll just use Odin.
Madtowndave said:
I'll try to be as detailed as possible.
1. Use stock USB cable and plug in on a back USB port that is on the motherboard.
2. Let Windows install the i717 USB drivers. Annoyingly, whenever I was in a different mode (specifically, USB mass storage or d/l mode), Win7 would install/update more drivers. After 3 total device driver installs from the different modes, I rebooted my pc.
3. I d/l Odin 1.85 and the Odin .tar link under 4-14-2012 from here: http://forum.xda-developers.com/showthread.php?t=1584576
I decided to use the CWM touch version...very similar to Cappy CWM to go back in the menu you use the back capacitive button.
4. I decided on a custom ROM...For me, I loved Mosiac on the Cappy back in the day, so I chose from the fine folks at The Collective here: http://forum.xda-developers.com/showthread.php?t=1773229
5. Pushed the ROM and GApps zip files via USB
6. Run Odin as Admin, click on PDA and selected the .tar from step 3.
7. Put phone in d/l mode and plug in to USB, Odin Com port lights up...Click Start
8. After the phone rebooted, (wait for the haptic feedback) I pulled the battery
9. 3 fingered into Recovery and now in good ol' CWM. The one trick here is that the .zips are under Internal Storage menu option, not SD Card (unless of course you file transferred them to an external sd card)
10. Followed installation steps in ROM OP and flashed zips from Step 5.
11. Enjoy!
I did not need Root, but am now rooted by virtue of the custom ROM. I also did not Nandroid backup the Stock ROM since if I ever need to go back to Stock, I'll just use Odin.
Click to expand...
Click to collapse
Awesome for you. I am awaiting dilivery from USPS. I hope they don't let me down after payong $40 for the overnight.
Two questions:
1) What did(do) your Win7 drivers in 'device manager' indicate? Was it something like “Samsung Mobile USB CDC Composite Device" or did it identify the phone by name. I have seen both types in my Win7 setup with my Captivate so want to make sure I get this right.
2) So, you did not specifically root (no need for the "Superuser-3.0.7-efghi-signed.zip" or something like it). So assuming adter I add CWMm I flash the CM9 (Cyanogenmod 9 stable) ROM will that root my phone? I guess the more general question is do these ROMS automatically come rooted?
I am at my wits end and hopefully one of you can help.
The phone in question is is the AT&T Galaxy S2 SGH i777. It was running a jellybean ROM and there were problems with the GPS and google maps not working at all about four months ago. Not sure what happened. I went through the usual process of putting a ROM on the SD card, wiping cache/davlik and installing, then installing the gapp.apk for that rom. Everything was fine. Except wireless. Wireless would not connect. Just wouldn't do it. Googled forever, found no real solution. Thinking it was the rom I reinstalled. Wash rinse repeat. Same issue. Thinking it was a bad rom I proceeded to go through about six more roms. Same issue. Four hours later I resolved to unroot, take it back to stock. Took it back to stop with no issues. Wireless worked just fine. Everything was great. Rooted it again with the stock gingerbread. Wireless worked fine. Made a backup of the rom and was feeling lucky so I installed the Carbon ROM from the Sept 29th post on galaxys2root.com (I don't know if you guys allow linking here) and the gapps from that post. I boot. Everything is looking fine....yet the wireless doesn't work. This has been consistent across every rom I installed. I am quitting for the night.
It is currently running android 4.3, kernel version 3.064-CM-gbc8f4c9 (if that helps). The phone service is fine and makes/receives calls/texts just fine. No other blaring issues. Worth pointing out: all roms in question came from galaxys2roms.com under the section for the AT&T i777 s2, so they should be compatible. Followed all directions/video ect.
I had this phone for years (girlfriend has it now) and Rom'd it many times with next to no issues, especially not with wireless. I don't understand why it was working fine on a JB rom and trying to change rom suddenly screwed the wireless.
I am literally at my wits end and it's probably the result of me being an idiot somehow and missing something. Can anyone suggest a fix?
God bless in advance.
fifthmanstanding said:
[...]all roms in question came from galaxys2roms.com under the section for the AT&T i777 s2, so they should be compatible. Followed all directions/video ect. [...]Can anyone suggest a fix?
God bless in advance.
Click to expand...
Click to collapse
My advice is to avoid downloading ROMS from galaxys2root.com
If you want the insider scoop, keep up at xda or at each group's G+ community.
if you want:
-Carbon; get it from: http://download.carbon-rom.com/?dir=./i777/nightly
-Cyanogenmod; get it from http://download.cyanogenmod.org/?device=i777
-Omni; get it from http://dl.omnirom.org/i777/
The installation is generally the same for all of them. Don't skip steps or take shortcuts.
flash:
-mr cooks rom wipe (good housekeeping is a must)
-chosen_ROM.zip
-Gapps (choose appropriately; only use 4.3 Gapps on 4.3 Firmware, etc)
-SuperSU (for Omni)
Happy Flashing
-Cyril
cyril279 said:
My advice is to avoid downloading ROMS from galaxys2root
If you want the insider scoop, keep up at xda or at each group's G+ community.
The installation is generally the same for all of them. Don't skip steps or take shortcuts.
flash:
-mr cooks rom wipe (good housekeeping is a must)
-chosen_ROM.zip
-Gapps (choose appropriately; only use 4.3 Gapps on 4.3 Firmware, etc)
-SuperSU (for Omni)
Happy Flashing
-Cyril
Click to expand...
Click to collapse
So would you suggest I revert back to the rooted gingerbread image and go from there?
I mean are we attributing the lack of wireless to this particular Carbon rom? I mean I had the same problem with like 6 different roms which leads me ot believe maybe it's missing something like a wireless apk or something (im not even going to pretend I know what the term is ). The reason I say it is that if it's consistently an issue with the roms, it must be the roms lacking something the hardware needs to function right?
fifthmanstanding said:
So would you suggest I revert back to the rooted gingerbread image and go from there?
I mean are we attributing the lack of wireless to this particular Carbon rom? I mean I had the same problem with like 6 different roms which leads me ot believe maybe it's missing something like a wireless apk or something (im not even going to pretend I know what the term is ). The reason I say it is that if it's consistently an issue with the roms, it must be the roms lacking something the hardware needs to function right?
Click to expand...
Click to collapse
You want to know if the problem is hardware related or firmware related. The test is to flash stock. You can flash any version of stock to find out, not just Gingerbread. UCMD8 will also give you a working wifi if the hardware is good.
creepyncrawly said:
You want to know if the problem is hardware related or firmware related. The test is to flash stock. You can flash any version of stock to find out, not just Gingerbread. UCMD8 will also give you a working wifi if the hardware is good.
Click to expand...
Click to collapse
Like I said I took it from what I think was a stock jellybean rom (where the wireless worked fine) and upgraded it to a kit kat rom and it stopped working, continued flashing roms with no success. Then flashed back to stock gingerbread and it was fine, then I rooted the stock gingerbread and it was fine. Then I took it to a non stock jellybean rom and the wireless didn't work. I mean I realize it's a lot of variables but if , consistently, I come from stock to a rom and wireless is not working, wouldn't that imply that the rom did not have something to support the wireless hardware? I had a similar problem years ago where I had to download a patch for the baseband to work after ATT changed the baseband. I was thinking maybe this was a similar problem where I could patch the wireless firmware with something to make it work. It just seems odd that like 6+ roms consistently left the wireless not working. And by not working I mean I can turn it on and off, see the available connections broadcast, see my network, put in my wireless pass word and it either suddenly shows as 'out of range' or will not connect to it at all.
Where would I find stock versions of rooted roms (jellybean or higher) for this phone. I didn't have much luck on google looking for stock.
fifthmanstanding said:
Like I said I took it from what I think was a stock jellybean rom (where the wireless worked fine) and upgraded it to a kit kat rom and it stopped working, continued flashing roms with no success. Then flashed back to stock gingerbread and it was fine, then I rooted the stock gingerbread and it was fine. Then I took it to a non stock jellybean rom and the wireless didn't work. I mean I realize it's a lot of variables but if , consistently, I come from stock to a rom and wireless is not working, wouldn't that imply that the rom did not have something to support the wireless hardware? I had a similar problem years ago where I had to download a patch for the baseband to work after ATT changed the baseband. I was thinking maybe this was a similar problem where I could patch the wireless firmware with something to make it work. It just seems odd that like 6+ roms consistently left the wireless not working. And by not working I mean I can turn it on and off, see the available connections broadcast, see my network, put in my wireless pass word and it either suddenly shows as 'out of range' or will not connect to it at all.
Where would I find stock versions of rooted roms (jellybean or higher) for this phone. I didn't have much luck on google looking for stock.
Click to expand...
Click to collapse
There is a working link to stock UCMD8, 4.1.2 in the Download Repository. It is said to be easy to root with Framaroot using the Aragorn exploit.
Cooked rom is based on UCMD8, deodexed, debloated, rooted with busybox.
And yes, it sounds like the roms are missing a compatible driver. Have you looked and asked about the issue in the rom threads. If there are not other people experiencing the same thing, then you need to look elsewhere for the reason and solution.
creepyncrawly said:
There is a working link to stock UCMD8, 4.1.2 in the Download Repository. It is said to be easy to root with Framaroot using the Aragorn exploit.
Cooked rom is based on UCMD8, deodexed, debloated, rooted with busybox.
And yes, it sounds like the roms are missing a compatible driver. Have you looked and asked about the issue in the rom threads. If there are not other people experiencing the same thing, then you need to look elsewhere for the reason and solution.
Click to expand...
Click to collapse
I apologize but where is the download repository, I'm not seeing it anywhere http://forum.xda-developers.com/galaxy-s2-att#subForums
fifthmanstanding said:
I apologize but where is the download repository, I'm not seeing it anywhere http://forum.xda-developers.com/galaxy-s2-att#subForums
Click to expand...
Click to collapse
hint: http://forum.xda-developers.com/member.php?u=2916435
cyril279 said:
hint: http://forum.xda-developers.com/member.php?u=2916435
Click to expand...
Click to collapse
Yeah I'm an idiot. I literally just saw that in the signature.
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
We understand that you're in a hurry to get the device fixed, but please take the time to read through one of creepy's links, or one of the many guides that explain the steps that you are about to take. Rushing it can make a worse mess of the device.
fifthmanstanding said:
Yeah I'm an idiot. I literally just saw that in the signature.
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
Click to expand...
Click to collapse
cyril279 said:
We understand that you're in a hurry to get the device fixed, but please take the time to read through one of creepy's links, or one of the many guides that explain the steps that you are about to take. Rushing it can make a worse mess of the device.
Click to expand...
Click to collapse
I agree.
Which links?
I read through the notes on the repository:
There is always some risk involved when flashing bootloaders and Param.lfs. Please don't flash this unless you absolutely need to.
"This is the complete stock UCMD8 Binaries downloaded from samfirmware at sammobile.com. Please note, this package contains boot.bin, sbl.bin and param.lfs, plus cache.img, factoryfs.img, hidden.img, modem.bin and zImage.I777UCMD8 Full Odin Flashable tar: I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5.7z 427.02 MB (Contains I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5)
(MD5: 307cc8fcbb8f220d3ae75d387569da40)"
And I'm downloading the file now. I've used odin before so I assume that goes by the standard process ( download mode, open, pda, select file, hit start, wait, finish) and then I went here http://forum.xda-developers.com/showthread.php?t=2130276 and he says "Version 1.3: Add Aragorn and Legolas exploits" so I assume based on Creepy's previous statement that's the one I need. I would download the apk and run it.
What am I missing?
Yeah I just installed the tar file using odin and before I even get to rooting process, wireless isn't working. This time it sees the network, password goes in as usual, it attempts to obtain IP address and says that forever. Never connects. Then goes back to scanning. Then attempts to connect again. No dice. No other device in the home has this issue. I'm out of ideas.
Edit:
Yeah I just tried again, using odin, took it back to stock, wireless works, using odin took it to stock with root, wireless works, using the tar file located here http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 took it to I777UCMD8 Stock Binary. Wireless is not working.
Does anyone have any insight? I've got a pissed off girlfriend an a perment dent in my desk from my head.
update: took it back to i777 UCMD8 with odin, just for kicks I tethered it to my nexus 4. Works fine. Turned off data, disconnected the wireless just to be sure. Turned it back on. Working fine. Still will not connect to my router. This would imply there is a router issue and I have less knowledge of how/why that would work. Thoughts?
fifthmanstanding said:
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
Click to expand...
Click to collapse
The file downloads as a 7z. Extract the .tar.md5 and put that in the PDA slot in Odin. Odin3 v1.85 is preferred for this phone, but the other versions usually work. There is a working link for the Odin download at the top of the page in the Download Repository. If you are unfamiliar with Odin, I can post more detailed instructions.
I am not personally familiar with Framaroot. It is an apk, so install on your phone and go.
Edit: Failed to click on the latest page of the thread before I posted this. Yes, it sounds like an issue with your router, perhaps. So find other routers and test the wifi. If that's the issue, then the other roms will probably also work on a different router.
creepyncrawly said:
The file downloads as a 7z. Extract the .tar.md5 and put that in the PDA slot in Odin. Odin3 v1.85 is preferred for this phone, but the other versions usually work. There is a working link for the Odin download at the top of the page in the Download Repository. If you are unfamiliar with Odin, I can post more detailed instructions.
I am not personally familiar with Framaroot. It is an apk, so install on your phone and go.
Click to expand...
Click to collapse
Yeah I've been using v 1.85. See above posts. UCMD 8 did not work. I have reflashed UCMD8 for the third time.
This third time followed the same as previously but for some reason wireless works all the way around. So that's progress.
The problem I'm having now is that I don't believe Framaroot is working. I followed the instructions and used the Aragorn exploit. It installed the SU app and it verifies that root is there. I downloaded rootchecker just to be sure. It verifies that root is there. I tried to boot into recovery to make a backup of the current state. It goes to stock android system recover. So I downloaded the clockwork mod recovery tar file. Ran odin with the CWM tar file, failed. For no apparent reason. I tried shutting it off, putting it back in odin mode, running the tar file again. Same issue. I took an alternative approach by downloading CWM Rom manager and tried installing CWM Recovery the the CWM Rom Manager app, it downloaded, requested SU permission, granted, installed and required reboot. Rebooted. Now if I try to boot into recovery (power off, power button +up/down buttons) it still boots into android system recovery stock mode. If I boot it, go to ROM Manager and tell it to boot into recovery mode it boots into CWM Recovery Mode with no issue. But CWM Recovery is not accessible through power+volume up/down buttons. Why is that?
At this point I want to get CWM Recovery to work, make a backup of current state and then push forward to getting this thing on a Jellybean rom because stock JP with touchwiz and the samsung nonsense and ATT Bloatware is horrd.
Any thoughts?
EDITosted before I saw your edit
fifthmanstanding said:
Yeah as stated, I'm familiar with odin. I've been using v 1.85. See above posts. UCMD 8 did not work. I have reflashed UCMD8 for the third time.
This third time followed the same as previously but for some reason wireless works all the way around. So that's progress.
The problem I'm having now is that I don't believe Framaroot is working. I followed the instructions and used the Aragorn exploit. It installed the SU app and it verifies that root is there. I downloaded rootchecker just to be sure. It verifies that root is there. I tried to boot into recovery to make a backup of the current state. It goes to stock android system recover. So I downloaded the clockwork mod recovery tar file. Ran odin with the CWM tar file, failed. For no apparent reason. I tried shutting it off, putting it back in odin mode, running the tar file again. Same issue. I took an alternative approach by downloading CWM Rom manager and tried installing CWM Recovery the the CWM Rom Manager app, it downloaded, requested SU permission, granted, installed and required reboot. Rebooted. Now if I try to boot into recovery (power off, power button +up/down buttons) it still boots into android system recovery stock mode. If I boot it, go to ROM Manager and tell it to boot into recovery mode it boots into CWM Recovery Mode with no issue. But CWM Recovery is not accessible through power+volume up/down buttons. Why is that?
At this point I want to get CWM Recovery to work, make a backup of current state and then push forward to getting this thing on a Jellybean rom because stock JP with touchwiz and the samsung nonsense and ATT Bloatware is horrd.
Any thoughts?
Click to expand...
Click to collapse
Apparently you are moving too fast, with too little information.
On this phone, recovery is compiled with the kernel, and they are installed as one unit. You will not successfully install a separate recovery. Also, rom manager has been know to cause issues on this phone, and should be avoided. There is a sticky about this at the top of the forum.
To get recovery you need to install a custom kernel. For UCMD8, that would be AJK v4.9 no swap. Someone said yesterday that the download didn't install for them. Don't know if they checked md5 on the download or not. I'd start with a download from the AJK thread and see if you can install it. You will use Mobile Odin lite or Mobile Odin pro on your phone to install the kernel. You will have to extract the boot.img from the CWM flashable zip and use that in Mobile Odin.
creepyncrawly said:
Apparently you are moving too fast, with too little information.
On this phone, recovery is compiled with the kernel, and they are installed as one unit. You will not successfully install a separate recovery. Also, rom manager has been know to cause issues on this phone, and should be avoided. There is a sticky about this at the top of the forum.
To get recovery you need to install a custom kernel. For UCMD8, that would be AJK v4.9 no swap. Someone said yesterday that the download didn't install for them. Don't know if they checked md5 on the download or not. I'd start with a download from the AJK thread and see if you can install it. You will use Mobile Odin lite or Mobile Odin pro on your phone to install the kernel. You will have to extract the boot.img from the CWM flashable zip and use that in Mobile Odin.
Click to expand...
Click to collapse
Fair enough.
I've downloaded the AJK no swap from here http://forum.xda-developers.com/showthread.php?t=2110542
I've downloaded Mobile Odin lite and am going to work on that.
Assuming it all works out and I get to make a backup. Where to next? This rom is terrible. What do you recommend for a jellybean experience as stock nexus 4 as possible.
Yeah the ajk no swap 4.9 is giving me a consistent java error that kills the download. I attempted to move it to the sd card and open in odin lite but am not seeing it on the card. Am I doing something wrong?
Edit. I tried connecting the phone to the computer and opening in explorer, following directions from here http://forum.xda-developers.com/showthread.php?t=2197157 , created a folder and attempted to drop the zip in there and it's not letting me drop files to the phone. nor to the sd card.
Edit 2: suddenly file xfer is working again. I dropped the .zip to the new folder on the internal and also created a new folder with the boot, METAINF folder and system folder that shows when you unzip. It's not detecting the zip file so I assume you're supposed to select the Boot file. I select it. Nothing happens.
Edit 3: looks like the actual download contains a boot disc image file. nothing md5. I'm assuming that's why when I click it it won't do anything. Any ideas?
fifthmanstanding said:
Edit 3: looks like the actual download contains a boot disc image file. nothing md5. I'm assuming that's why when I click it it won't do anything. Any ideas?
Click to expand...
Click to collapse
Open the AJK 4.9 ns zip file with an archiving program such as win zip, 7 zip, etc. You will see one file and two directories. The file is boot.img. Extract that and flash it in Mobile Odin. Ignore the directories.
If you were going to want to use AJK with UCMD8, you would then enter recovery and flash the full AJK 4.9 no swap zip file in CWM.
Otherwise, enter recovery and flash the firmware of your choice. For Samsung firmware based on touchwiz, I suggest SHOstock3 v4.0. It's still actively supported. I don't use AOSP based firmware so can't make any suggestions there. There's lots of info in the development forum.
creepyncrawly said:
Open the AJK 4.9 ns zip file with an archiving program such as win zip, 7 zip, etc. You will see one file and two directories. The file is boot.img. Extract that and flash it in Mobile Odin. Ignore the directories.
If you were going to want to use AJK with UCMD8, you would then enter recovery and flash the full AJK 4.9 no swap zip file in CWM.
Otherwise, enter recovery and flash the firmware of your choice. For Samsung firmware based on touchwiz, I suggest SHOstock3 v4.0. It's still actively supported. I don't use AOSP based firmware so can't make any suggestions there. There's lots of info in the development forum.
Click to expand...
Click to collapse
Ok by the looks of it that worked. Thanks for that.
In terms of roms I'm looking for something stable, jelly bean and non-touchwiz. As close to possible as nexus 4's jelly bean. Nothing comes to mind?
Edit: apparently the home key now no longer works properly, hitt it brings up a selection box and selects whatever is the left most side whether it's 'apps' tab or an icon on the home screen. Also the search magnifying glass soft key doesn't work, same function as the home key it seems.
Edit 2: And the wireless is no longer working. Was working fine before flashing the kernel. Put the phone directly on top of the router. It shows the network, allows for password input, says 'connecting' and never ever connects. Then it drops and goes to 'out of range'...sitting directly on the router. Just for kicks, like last time, I enabled the hotspot on my N4 and it connected fine. I attempted to connect to the router again and it does the same...connecting and drops to out of range. Sigh.
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
The ROM may not have Loki support...if you are using the older twrp version it may not auto lokify the ROM...try updating your recovery and give it another go
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
I would recommend trying out Philz ( cwm ) recovery possibly. There have been random issues like yours reported and usually updating the recovery or just trying a different ROM all together gets better results.
You shouldn't need to go back to stock mdk for anything since you're already rooted and have a custom recovery.
Sent from my SCH-I545 using Tapatalk
Thanks for the suggestions. I did update my recovery, but now that I think of it, I may not have tried to re-flash since upgrading. My preference is to not use CWM, but I will if I have to, I guess.
In either case, I'll try this all out when I get home from work and post back. Thanks for the suggestions.
FranklinPIerce said:
Thanks for the suggestions. I did update my recovery, but now that I think of it, I may not have tried to re-flash since upgrading. My preference is to not use CWM, but I will if I have to, I guess.
In either case, I'll try this all out when I get home from work and post back. Thanks for the suggestions.
Click to expand...
Click to collapse
Let me suggest trying liquid smooth 4.4
Awesome ROM to try.
Sent from my SCH-I545 using Tapatalk
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
I would try their suggestions. For future reference though, you can use heimdall instead of Odin on Linux. I love it I think its better than odin
Sent from my unknown using Tapatalk
Ok, so I updated TWRP to the latest and tried again. Got the same message as before about unauthorized software and in the upper left, it said something about "Fail: Kernal"
From there, I had a hard time getting back into recovery. It would either say it was booting into recovery and then shut off or it would freeze. I eventually got back in and am restoring now.
Thanks for the information on Heimdall - I wasn't aware of it. The reason I wanted to go with Carbon is that it has a built-in application to control/override application permissions. Does something like that exist for LiquidRom? Or is it compatible with PDroid or something similar? (I didn't see a mention of it in their features, but might have missed it)
One more thought: I am using the Carbon nightlies for KK. Maybe there's a problem with the source file (I've redownloaded 4 times)? Or maybe I'm just destined to be on stock forever. :crying:
Edit: I just tried putting Philz recovery on and now I can't get into recovery as that's now giving the same unauthorized software message.
Edit2: I was able to get TWRP on eventually by going into Odin mode and hitting "Cancel." Each normal reboot would then give the same unauthorized message, so I just went back to TWRP and it's booting normally again. Ah, yay to Verizon and their locked phones.
Ok, I've tried a few more times tonight with no luck, so I'll give it a break for now and look into it more tomorrow or over the weekend.
FranklinPIerce said:
Ok, so I updated TWRP to the latest and tried again. Got the same message as before about unauthorized software and in the upper left, it said something about "Fail: Kernal"
From there, I had a hard time getting back into recovery. It would either say it was booting into recovery and then shut off or it would freeze. I eventually got back in and am restoring now.
Thanks for the information on Heimdall - I wasn't aware of it. The reason I wanted to go with Carbon is that it has a built-in application to control/override application permissions. Does something like that exist for LiquidRom? Or is it compatible with PDroid or something similar? (I didn't see a mention of it in their features, but might have missed it)
One more thought: I am using the Carbon nightlies for KK. Maybe there's a problem with the source file (I've redownloaded 4 times)? Or maybe I'm just destined to be on stock forever. :crying:
Edit: I just tried putting Philz recovery on and now I can't get into recovery as that's now giving the same unauthorized software message.
Edit2: I was able to get TWRP on eventually by going into Odin mode and hitting "Cancel." Each normal reboot would then give the same unauthorized message, so I just went back to TWRP and it's booting normally again. Ah, yay to Verizon and their locked phones.
Ok, I've tried a few more times tonight with no luck, so I'll give it a break for now and look into it more tomorrow or over the weekend.
Click to expand...
Click to collapse
That's odd that flashing Philz didn't work for you. Its a pain I know but probably if you had wiped the phone with stock mdk then tried again it woukd have worked I bet. I had to do that with this phone when i got it. It came with twrp, but was acting real funny not always getting into recovery or just hanging up on reboot. But you have a working twrp so that's good too.
I don't believe liquid has the built in app permissions you're talking about but maybe I missed it. I don't really mess with permissions. Liquid has everything else though and then some!
I know some Roms were having problems with unified builds. I know liquid does not at this point. Maybe it'd be worth trying just so you're not on stock lol you may want to look into the Loki doki zip that you flash after flashing the ROM. I've seen some people on here using that when they were getting the same error you were. Just an idea.
Good luck man!
Sent from my SCH-I545 using Tapatalk
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