Related
I'm currently running the stock EL29 with root and CWM but whenever I try to install a custom rom (AOPK, CM9, etc...) through CWM, it says "Instillation Aborted" as if they weren't made for this phone when I know they were. What's going on?
.HaVoC. said:
I'm currently running the stock EL29 with root and CWM but whenever I try to install a custom rom (AOPK, CM9, etc...) through CWM, it says "Instillation Aborted" as if they weren't made for this phone when I know they were. What's going on?
Click to expand...
Click to collapse
Silly question, and not assuming, did you use autoroot for cwm?
May want to Odin to el26 and autoroot cwm ans try it that way.
I personally Odin back to el29, autoroot, and (knock on wood) never had an issue.
Sent from my SPH-D710 using XDA
.HaVoC. said:
I'm currently running the stock EL29 with root and CWM but whenever I try to install a custom rom (AOPK, CM9, etc...) through CWM, it says "Instillation Aborted" as if they weren't made for this phone when I know they were. What's going on?
Click to expand...
Click to collapse
Usually that happens on a bad download. Did you download them on your phone or PC?
It turns out that is was just the version of CWM that I was using but now I have a new problem. I flashed CM9 and everything worked EXCEPT the data connection so then I flashed AOPK and had the same problem. The only way I can get online is via wifi. How do I fix this?
.HaVoC. said:
It turns out that is was just the version of CWM that I was using but now I have a new problem. I flashed CM9 and everything worked EXCEPT the data connection so then I flashed AOPK and had the same problem. The only way I can get online is via wifi. How do I fix this?
Click to expand...
Click to collapse
Check you baseband in settings>about phone. If it says unknown then just flash a modem of your choice. This has happen to me. On several occasions.
Sent from my SPH-D710 using xda premium
.HaVoC. said:
It turns out that is was just the version of CWM that I was using but now I have a new problem. I flashed CM9 and everything worked EXCEPT the data connection so then I flashed AOPK and had the same problem. The only way I can get online is via wifi. How do I fix this?
Click to expand...
Click to collapse
Cool that ya got to flash from though!
Sorry, I don't use CM9.
I can try on my other e4gt later and test though.
Sent from my SPH-D710 using XDA
krazy_smokezalot said:
Check you baseband in settings>about phone. If it says unknown then just flash a modem of your choice. This has happen to me. On several occasions.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
It says "S710.10 S.EL29"
Isn't EL29 for GB only or something?
.HaVoC. said:
It says "S710.10 S.EL29"
Isn't EL29 for GB only or something?
Click to expand...
Click to collapse
No its ok to have an older modem and be running ICS. They can be "mismatched."
slick_rick said:
No its ok to have an older modem and be running ICS. They can be "mismatched."
Click to expand...
Click to collapse
And I have found, in the boonies that I'm in, el29 modem works the best for me on any ics builds..
Sent from my SPH-D710 using XDA
.HaVoC. said:
It says "S710.10 S.EL29"
Isn't EL29 for GB only or something?
Click to expand...
Click to collapse
Did u get it to work yet?? Try to Odin stock gb el29 rom. And start from scratch...
Sent from my SPH-D710 using xda premium
krazy_smokezalot said:
Did u get it to work yet?? Try to Odin stock gb el29 rom. And start from scratch...
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I started from scratch and followed all the steps until I ended up in the same boat. AOKP Build 38 working perfectly EXCEPT data. I tried the EL29 and FE10 kernels but neither made a difference.
.HaVoC. said:
I started from scratch and followed all the steps until I ended up in the same boat. AOKP Build 38 working perfectly EXCEPT data. I tried the EL29 and FE10 kernels but neither made a difference.
Click to expand...
Click to collapse
Try going back to gingerbread and flashing the EL26 kernal. Then flash the ICS rom you want through that recovery.
AOKP and CM9 have problems with data. every time you or system turn off screen say goodbye to data until 1.enable disable airplane mode or 2.reboot that's the main reason I stay away from these awesome roms until source arrives.
These roms are the best. IMO
1.odin back to stock el29 full reset oc
2.boot update profile and prl
3.copy the rom files to sd
4.turnitoff it off
4.enter download mode and flash el26+cmw for AOKP or el29+cwm direct boot for CM9
5.clear cache, factory data reset, clear dalvik on advance menu
6.go back and select install zip from sd card and choose the rom and flash it
7.flash gapps if apply
8.go back and select reboot system
9.enjoy these awesome roms.
Sent from my SPH-L710 using Tapatalk 2
I think I FINALLY got it to work. I started stock with rooted EL29 Odin-OC, flashed the "StockCWM-EL26.tar.m5d" in Odin, flashed the AOKP build 37 rom, flashed gapps, then flashed the FE16 kernel AND modem. When I rebooted the data was working.
Not that I am advocating this, and I am far from an expert, but I odin flash a stock rooted rom (SPH-D710.FC22_CL287574_ROOTED-oc-sfx) without going back to el29 just to have a nice clean stock rom to flash over with something else (like FIFO2). I just try to make sure I do everything in the same session so I don't get stuck in a stock recovery.
My order when flashing (non-Odin):
calkulin's format all
Modem (sometimes...if newer is available)
Rom
Kernel (with a custom recovery; sometimes the roms come with a stock recovery so if you reboot before installing a custom one, you'll have to either use odin to flash a custom recovery or mobile Odin)
any additional items that the rom didn't include (like gapps, etc.)
reboot
---------- Post added at 02:09 AM ---------- Previous post was at 01:58 AM ----------
Another thing to keep in mind is that AOKP was ported to the E4GT. That could cause issues depending on what you're coming from. Make sure to read all the instructions from the dev before flashing. If the worst happens, buy insurance on your phone and smash it...That's what I did with my evo when I bricked it.
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
mr1080p said:
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
SysAdmNj said:
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
Click to expand...
Click to collapse
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
U have to make sure u are rooted first.
Sent from the TermiNOTEr!
mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
SysAdmNj said:
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
Click to expand...
Click to collapse
Yes. CWM and ported ROM. Everything works well I just want TWRP. But I guess I'll do with CWM. If it aint broke then why fix it. It works I guess. Thanks.
Sent from my SAMSUNG-SGH-I317 using xda premium
Check your build prop for device name. Maybe its not correct because of the Rom you're on. Whats the error you're getting?
Did you ever get TWRP on your phone?
I've had goofy issues with TWRP but much prefer it to CWM. Originally rooted using CWM and SuperSu and switched to TWRP when I flashed CleanRom several times via Romtoolbox pro I've flashed updated Twrp it said it was successful but when it rebooted was soft bricked! Had to use Odin and original CWM to get back in and re-install everything (nandroids were twrp backups) found file downloaded to sdcard that worked fine! Odd...
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
wargear said:
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
Click to expand...
Click to collapse
If by "installed" you are referring to the recovery program itself (and not your backups), you can only have one recovery 'installed' at one time as there is only 1 "Recovery" partition on the device (/dev/block/mmcblk0p9). So if you want to install CWM instead of your current TWRP (or visa-versa), either flash the appropriate new recovery zip via your current recovery... or Odin3 flash your desired new recovery tar. Either way, it will write to the same recovery partition. If you are referring to your backups... these are stored in the designated path you selected (either internal sd or external sd)... in the TWRP/BACKUPS folder. In that folder, you will have a device id #... in that folder are your backups.
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
wargear said:
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
Click to expand...
Click to collapse
Which version of Odin3 are you using? When I used Odin3 v1.85 I would get the "PASSED" but with Odin3 v3.07, I also only got "RESET" (on an WindowsXP box)... but both flashed it correctly (and auto rebooted after flash)
Galaxy Note2 TOOLKIT V3.0.0 ATT]
I tried the [Galaxy Note2 TOOLKIT V3.0.0 ATT] http://forum.xda-developers.com/showthread.php?t=2052779 out of curiosity sake. Worked for me installing TWRP 2.3.2.3 without a hitch. Great tool from what I can see, and that's just one of it's many features. Great for simplifying things for new Android users just entering the customizing scene and regulars alike. Big ups to mskip for making this available. I can foresee myself grabbing the donate version here real soon.
And to get yourself SIM unlocked, get yourself back to 4.1.1 and give this a whirl.http://forum.xda-developers.com/showthread.php?t=2014982 Bought my device used, was supposedly unlocked, wasn't. Even came with an unlock code that the previous owner purchased. Firstly it's a no go on 4.1.2, secondly still didn't work when I dropped back to 4.1.1. But this http://forum.xda-developers.com/showthread.php?t=2014982 will set you free. Big thanks owl74 for posting. Once again XDA forums saves my hair from being pulled out.
Hello,
So I've been rooted for a while now, i was going to install a custom rom but decided not to a few months ago. Tonight, i decided to install aokp, however my phone would not go into cwm, only stock recover. I could have sworn it was installed, but fine, so i installed it once again with auto reboot in odin checked, and it still wouldnt enter cwm. I then tried to install it again with auto reboot checked off so i could see if i could enter it without the reboot. I ended up getting into it, but then when i was taking a NANDROID, it just froze on one of the first steps. Fine, reboot, try to enter cwm again. Nope, just stock android recovery. I am sure im installing it correctly and pressing the right button combos. I am at a total loss for what is stopping me from being able to enter cwm. I hope you guys know/help me find whats going on.
Thanks!!!
Zay
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
pcshano said:
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
Click to expand...
Click to collapse
Yes my phones rooted.
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Zay48 said:
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Click to expand...
Click to collapse
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
pcshano said:
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
Click to expand...
Click to collapse
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
if you still want cwm then i guess you can try flash stock rom and root it again and see
since you're going to flash a custom rom which will delete all your data anyways
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Zay48 said:
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Click to expand...
Click to collapse
Bump
what version of CWM are you currently running?
you could always try to download GooManager or ROM Manager from the Play Store.
then from one of those, install the custom recovery, GooManager for TWRP or ROM Manager for CWM.
xBeerdroiDx said:
what version of CWM are you currently running?
Click to expand...
Click to collapse
3.0.7
Zay48 said:
3.0.7
Click to expand...
Click to collapse
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
zetsui said:
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
Click to expand...
Click to collapse
He's not having a problem restoring images, he's having a problem making his first nandroid.
Sent from my SGH-I747 using xda app-developers app
Zay48 said:
3.0.7
Click to expand...
Click to collapse
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
RPelham said:
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Download rom manager and update your cwm and then try making a nandroid again.
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
That said... If you insist in CWM, this is the guide I followed to get a successful CWM flash. (This was the CWM I was running successfully for the brief time TWRP disbanded.)
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
The above is for the ATT variant only. If you have a different variant and can't find the link, post back and I'll find it for you
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
apparently it's still around because new android users who want to root use those guides with outdated files
RPelham said:
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Preach brother!
Hello I tried to flash pure stock then recovery per instructions and now my t999l is stuck on android system recovery can someone plz tell me if I have bricked my phone crying hard right now
In recovery, factory reset. Then reboot and it should work fine.
Stock recovery will wipe your internal sdcard.
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
In recovery, factory reset. Then reboot and it should work fine.
Stock recovery will wipe your internal sdcard.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
Post is difficult to decipher, but I take it that the stock recovery is overwriting his custom recovery... but then the rest of the post doesn't make any sense. Needs clarification.
DocHoliday77 said:
In recovery, factory reset. Then reboot and it should work fine.
Stock recovery will wipe your internal sdcard.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
Mr. Doc I so appreciate you!!! First time posting to thread and Im grateful of your timely response. Let me just tell you exactly whats going on
my phone is in the android system recovery what I am seeing is green android man with a red warning over top of it. it will not let me do anything and I see a message saying "MANUAL MODE" successfully applied multi CSC. It won't connect to ODIN OR Kies Im so scared that I have ruined my phone crying very hard
Odin doesn't work unless you're in download mode.
What happens when you reboot? If it takes you to recovery, boot into download mode (power+vol down+home) and flash a stock image.
imblessed68 said:
Mr. Doc I so appreciate you!!! First time posting to thread and Im grateful of your timely response. Let me just tell you exactly whats going on
my phone is in the android system recovery what I am seeing is green android man with a red warning over top of it. it will not let me do anything and I see a message saying "MANUAL MODE" successfully applied multi CSC. It won't connect to ODIN OR Kies Im so scared that I have ruined my phone crying very hard
Click to expand...
Click to collapse
Also this happened after I flashed the pure stock then I flashed the recovery and the phone automatically went to what I have explained in prior post
When the phone is recovery it doesn't let me do anything factory/reset or anything and when i put in download mode it doesn't connect to ODIN
What rom were you previously using? And you do have a T999L right? You won't be able odin flash any stock firmware because there isn't any.
Try again to get into download mode. If you can boot recovery you should be able to get there too I'd imagine.
Hold volume down and home while powering up.
If you can do this, odin flash either cwm from aerowinders sig, or twrp from mine. Then reflash whichever rom you were running before trying the pure stock rom.
Sent from my SGH-T999L using xda premium
---------- Post added at 01:07 PM ---------- Previous post was at 01:05 PM ----------
Aerowinder said:
Post is difficult to decipher, but I take it that the stock recovery is overwriting his custom recovery... but then the rest of the post doesn't make any sense. Needs clarification.
Click to expand...
Click to collapse
Sorry bout that.
It sounds like he was on another rom and recovery and tried to flash back to stock.
Am I correct?
Sent from my SGH-T999L using xda premium
Hello I'm a she lol but what originally happened was I rooted phone through Odin. Then when I looked in Twrp and cwm it kept saying i had no recovery image. I went through thread on here and saw someone with same issue and follow Mr. Doc's instructions pertaining to the pure stock and recovery and this is where i landed. Im in download mode so yes i see my phone is not ruined lol I just need the file Mr. Doc is telling me about to reflash because im now connected to odin. I had to use another computer. I greatly appreciate all the time taken to help me get my phone back to working order. Since I am new I need to find the place where I can give a lot of Kudos to mr doc and his team now all i need is where to i go for mr doc file
In my signature, click Recoveries. Then in the twrp folder download version 2.5.0.0. Get the one that's a .tar.
Then once connected to odin, click the PDA button and select the tar file you just downloaded. Then click start.
Once done it should auto reboot. Now reboot into recovery and try doing a factory reset there.
If you still can't boot after that, flash the other, deodexed rom from my T999L thread.
I've got to go for a bit but will try to jump back on soon to see how you're doing.
Sorry bout the he/she thing!
Sent from my SGH-T999L using xda premium
Did you get it working?
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
Did you get it working?
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
Yesssss!!!! thank you so much now maybe i can redo what i tried to do
Right on! Glad to hear you're back up snd running!
Let me know if you have any other problems with the T999L stuff.
Sent from my SGH-T999L using xda premium
Thanks Doc and Team T999L!!!
DocHoliday77 said:
Right on! Glad to hear you're back up snd running!
Let me know if you have any other problems with the T999L stuff.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
I just want to thank Mr. Doc and all who are working very hard to create roms for t999L. I had att s3 on tmobile network and got my phone exactly the way i wanted it when my son comes in the house with a tmobile s3 and wanted to swtich with me because he didn't want the color he got (white lol i had red) however I didn't know this phone was very new and the only thing I could do is root lol. I'm waiting patiently because I really love the LIquidsmooth rom so on that note Mr. Doc and team again I thank you for all your hard work!
recovery
imblessed68 said:
I just want to thank Mr. Doc and all who are working very hard to create roms for t999L. I had att s3 on tmobile network and got my phone exactly the way i wanted it when my son comes in the house with a tmobile s3 and wanted to swtich with me because he didn't want the color he got (white lol i had red) however I didn't know this phone was very new and the only thing I could do is root lol. I'm waiting patiently because I really love the LIquidsmooth rom so on that note Mr. Doc and team again I thank you for all your hard work!
Click to expand...
Click to collapse
Mr. Doc what I was originally trying to accomplish was creating a recovery for the phone. I think my phone is only rooted and I have no recovery or so i think for the phone. Can you help me understand lol. I know cwm is not available yet at least it wasn't couple days ago.
goo.im
imblessed68 said:
Mr. Doc what I was originally trying to accomplish was creating a recovery for the phone. I think my phone is only rooted and I have no recovery or so i think for the phone. Can you help me understand lol. I know cwm is not available yet at least it wasn't couple days ago.
Click to expand...
Click to collapse
Mr. Doc when I go into goo.im it tells me in order to flash roms i need an open recovery scrip compatible recovery then it says it can find one for me thats where im lost and getting confused about whether i have a recovery on the phone. but if im right that means i can't right?
Neither CWM or TWRP have added support yet, though it should be as simple as asking. Ill try to contract them in a bit.
You can manually install any of the latest recoveries for the T999 though. They have been confirmed working by several people.
Are you familiar with Odin? I suggest going to the Recoveries link in my sig and get TWRP version 2.5.0.0. The one you want has the .tar extension.
Then flash that in Odin.
If you aren't comfortable with Odin I can tell you another way using terminal emulator.
Your phone does currently have a recovery, but unless you've installed a custom one its still stock.
Also, you can flash any of the Roms posted for the T999. If the rom doesn't include a kernel, and it touchwiz based, you can flash one of the kernels in my T999L thread in development section. I'd try the MD5 kernel first so its matched with the Touchwiz rom you choose. (If you flash CM or AOSP based roms, do not use the kernels I just mentioned).
Hope that helps!
Sent from my SGH-T999L using xda premium
I used the Toolkit to flash mine: http://forum.xda-developers.com/showthread.php?t=1746682
Choose Device option 62 and then Flash custom recovery. It will automate the ODIN install if you are not familiar.
DocHoliday77 said:
Neither CWM or TWRP have added support yet, though it should be as simple as asking. Ill try to contract them in a bit.
You can manually install any of the latest recoveries for the T999 though. They have been confirmed working by several people.
Are you familiar with Odin? I suggest going to the Recoveries link in my sig and get TWRP version 2.5.0.0. The one you want has the .tar extension.
Then flash that in Odin.
If you aren't comfortable with Odin I can tell you another way using terminal emulator.
Your phone does currently have a recovery, but unless you've installed a custom one its still stock.
Also, you can flash any of the Roms posted for the T999. If the rom doesn't include a kernel, and it touchwiz based, you can flash one of the kernels in my T999L thread in development section. I'd try the MD5 kernel first so its matched with the Touchwiz rom you choose. (If you flash CM or AOSP based roms, do not use the kernels I just mentioned).
Hope that helps!
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
I am familiar with Odin i used that to get me up and running again using the sig you just mentioned. If I'm understanding you correctly you're saying I can flash a t999 rom to my t999L but use a different kernel? Also am I flashing the rom using Odin and if so do I use the same method to flash kernel? I think Im getting a clear understanding because I thought I could only root thorugh odin but install roms through cwm and twrp lol and basically I can use Odin to do it all right? I want to make sure I don't have to bother you all the time lol I should have kept my darn att s3!! thanks again Mr. Doc you truly rock!!!!
DJ_SpaRky said:
I used the Toolkit to flash mine: http://forum.xda-developers.com/showthread.php?t=1746682
Choose Device option 62 and then Flash custom recovery. It will automate the ODIN install if you are not familiar.
Click to expand...
Click to collapse
Thank you DJ have you tried any rome yet and you have t999L also?
Hi XDA! I have a Samsung Galaxy Note 3 N900T T-Mobile. I've had custom roms such as CM11 Nightly in the past. Well after trying to do a fresh install a while back of another custom rom, my phone at first had no OS because I wiped it like a doofus. So I flashed it back to stock, 4.3 at the time. And then starting a couple weeks ago I flashed CWM using CWM Manager app. That's when the same issue that's recurring over and over, began. My phone works great as long as I never reboot into recovery. If I reboot into recovery it gets stuck in a bootloop. However I noticed tonight after trying to reboot into recovery using goo manager, I noticed the last line when it first boots, then bootloops, says Set warranty bit-recovery. If I remember correctly shouldn't it say kernel?? I know this is my fault because I'm not as knowledgable as all of you (I'm still learning on my own). SO my question is this. I want to fix this once and for all because I can't ever flash a custom rom like Darthstalker (that's the one I'd like to flash)...after several failed attempts of flashing CM for example, to no avail. What can I do to fix this once and for all and be able to flash a kernel, and Darthstalker? I can get into download mode, needless to say. ANd all the other times it's bootlooped I flashed KitKat 4.4.2 and everything works fine until i try to reboot into recovery. I am at my witts end because this i I really want a custom rom instead of flashing only the md5. Would anyone please be willing to give me a tutorial of some kind? I know it's a lot to ask but I can't find another reliable source that can explain how to do all of this. You're the only site I trust and if anyone is willing to give mea tutorial via email , PM, etc. I'd be eternally grateful beyond belief. Thank you in advance for any advice or info
I posted a few days ago about my bootlooping in the recovery. I finally fixed it by these 3 steps.
1) Odin flashed Stock 4.4.2 complete as this sets the correct boot loader.
2) I downloaded Twrp 2.7.0 the one that list KitKat (Must say this) 4.4 version.
http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.7.0.0-hltetmo-4.4.img.tar
3) Right from Odin when flashing this you set it not to reboot, Once finished you then unplug the usb cable and pull the battery. Let is sit for about 10 sec. Then with the upVlm,Home and Power it will boot to the recovery. It first will post what you said but wait about 10 sec more twrp will come up.
4) Now you should be able to flash any rom you want. I am using axmans N3 for now works great. I will be trying CM 11 later.
5) make a backup once in Twrp
Hope this helps.
helterkelter said:
Hi XDA! I have a Samsung Galaxy Note 3 N900T T-Mobile. I've had custom roms such as CM11 Nightly in the past. Well after trying to do a fresh install a while back of another custom rom, my phone at first had no OS because I wiped it like a doofus. So I flashed it back to stock, 4.3 at the time. And then starting a couple weeks ago I flashed CWM using CWM Manager app. That's when the same issue that's recurring over and over, began. My phone works great as long as I never reboot into recovery. If I reboot into recovery it gets stuck in a bootloop. However I noticed tonight after trying to reboot into recovery using goo manager, I noticed the last line when it first boots, then bootloops, says Set warranty bit-recovery. If I remember correctly shouldn't it say kernel?? I know this is my fault because I'm not as knowledgable as all of you (I'm still learning on my own). SO my question is this. I want to fix this once and for all because I can't ever flash a custom rom like Darthstalker (that's the one I'd like to flash)...after several failed attempts of flashing CM for example, to no avail. What can I do to fix this once and for all and be able to flash a kernel, and Darthstalker? I can get into download mode, needless to say. ANd all the other times it's bootlooped I flashed KitKat 4.4.2 and everything works fine until i try to reboot into recovery. I am at my witts end because this i I really want a custom rom instead of flashing only the md5. Would anyone please be willing to give me a tutorial of some kind? I know it's a lot to ask but I can't find another reliable source that can explain how to do all of this. You're the only site I trust and if anyone is willing to give mea tutorial via email , PM, etc. I'd be eternally grateful beyond belief. Thank you in advance for any advice or info
Click to expand...
Click to collapse
I'm honestly confused on what you are asking. What bootloader are you on . Jellybean or Kit Kat. That is the big part of the question. If you are on Kit Kat you can no longer run Darthstalker as it's a 4.3 rom. Just curious because you say that you flashed 4.4.2 rom and everything works. Also, the bootloop would either be your kernel or your recovery. I would suggest Philz or Twrp 2.7 as they are both updated and will work on either bootloader.
Once you have flashed a bootloader and custom recovery NEVER USE ODIN AGAIN UNLESS YOU HAVE BRICKED YOUR PHONE.
dragonstalker said:
I'm honestly confused on what you are asking. What bootloader are you on . Jellybean or Kit Kat. That is the big part of the question. If you are on Kit Kat you can no longer run Darthstalker as it's a 4.3 rom. Just curious because you say that you flashed 4.4.2 rom and everything works. Also, the bootloop would either be your kernel or your recovery. I would suggest Philz or Twrp 2.7 as they are both updated and will work on either bootloader.
Once you have flashed a bootloader and custom recovery NEVER USE ODIN AGAIN UNLESS YOU HAVE BRICKED YOUR PHONE.
Click to expand...
Click to collapse
I'm on 4.4.2.I figured it is my kernel. After sending this message last night I had my phone in download mode but didn't do anything to it. I decided to turn it off and then on again and it booted. So if this is a kernel issue where would I find one and how would I do this? Oh and when the bootloop occurred last night I was trying to boot into recovery via too manager. If I put Twrp on my phone when I have CWM will they interfere? I apologize for the likely stupid questions but I'm just wanting to get it done properly. One last thing is PacMan ROM compatible?
helterkelter said:
I'm on 4.4.2.I figured it is my kernel. After sending this message last night I had my phone in download mode but didn't do anything to it. I decided to turn it off and then on again and it booted. So if this is a kernel issue where would I find one and how would I do this? Oh and when the bootloop occurred last night I was trying to boot into recovery via too manager. If I put Twrp on my phone when I have CWM will they interfere? I apologize for the likely stupid questions but I'm just wanting to get it done properly. One last thing is PacMan ROM compatible?
Click to expand...
Click to collapse
The kernels you can use are listed in the general thread. A user posted a very good listing of what's what. TWRP 2.7 or Philz Touch are the 2 recoveries i would recommend using. Whichever one you decide will overwrite the other. you can never have 2 recoveries.
OK I'm sorry but I'm a little confused. One solution mentioned was to flash 4.4.2 stock using Odin. But you said not to use it unless I've bricked my phone. So now I'm lost. Lol. Do I flash the stock with the above mentioned method? Or do I flash a kernel and then a ROM? I apologize for my inexperienced questions. I'm including my device info below in hopes you can tell me the very first step I should take. Thank you for all your help!!!
Baseband N900TUVUCNB4
KERNEL- 3.4.0-660648 [email protected]#1
BUILD #- KOT49H.N900TUVUCNB4
SE FOR ANDROID STATUS- ENFORCING SEPF_SM-N900T_4.4.2-0005
SECURITY SOFTWARE VERSION- MOF v1. Release 2
Sent from my SM-N900T using xda app-developers app
helterkelter said:
OK I'm sorry but I'm a little confused. One solution mentioned was to flash 4.4.2 stock using Odin. But you said not to use it unless I've bricked my phone. So now I'm lost. Lol. Do I flash the stock with the above mentioned method? Or do I flash a kernel and then a ROM? I apologize for my inexperienced questions. I'm including my device info below in hopes you can tell me the very first step I should take. Thank you for all your help!!!
Baseband N900TUVUCNB4
KERNEL- 3.4.0-660648 [email protected]#1
BUILD #- KOT49H.N900TUVUCNB4
SE FOR ANDROID STATUS- ENFORCING SEPF_SM-N900T_4.4.2-0005
SECURITY SOFTWARE VERSION- MOF v1. Release 2
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
You are already on the 4.4 bootloader so you can no longer use the Darthstalker rom, you can only use Kit Kat 4.4.2 and above roms from here on out. Next question would be have your rooted your phone since the update and have a custom recovery. If you have not rooted, then you will need to use Odin to run the CF_Autoroot, but that will trip your Knox to 0x1. Thus voiding your warranty.
Yes I rooted. But every time I try flashing CWM or Twrp it bootloops. And to get out of bootloop I have to boot in download and then cancel download and it reboots normal again. Is this a kernel or boot loader issue?
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Yes I rooted. But every time I try flashing CWM or Twrp it bootloops. And to get out of bootloop I have to boot in download and then cancel download and it reboots normal again. Is this a kernel or boot loader issue?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Which cwm and twrp are you trying to flash. The only 2 that will work on Kit Kat are PHilz touch latest one, and TWRP 2.7
Twrp 5.7.3
Sent from my SM-N900T using xda app-developers app
So do I flash stock as mentioned from another member or do I flash a kernel? I'm not sure what to do next
Sent from my SM-N900T using xda app-developers app
helterkelter said:
So do I flash stock as mentioned from another member or do I flash a kernel? I'm not sure what to do next
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
oh sorry for the late response. Just got back from boy scouts. Anyway. No you don't need to flash back to stock, Your just flashing the wrong version of TWRP. You can go to the android originial development thread and download the TWRP 2.7 and flash via recovery and you will be all good to go. Also, download the latest Wootever kernel just to make sure you have both angles covered. Both downloads are found in the same section.
Ok thanks so much. Im a little scared to flash in TWRP as it always puts me in bootloops. I did download philz and I was considering flashing that via Odin as I can't boot into recovery. Would that be the next best thing to do? Oh and dont apologize!! I can't thank you enough!
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Ok thanks so much. Im a little scared to flash in TWRP as it always puts me in bootloops. I did download philz and I was considering flashing that via Odin as I can't boot into recovery. Would that be the next best thing to do? Oh and dont apologize!! I can't thank you enough!
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Yes, odin the custom recovery and you should have no more issues. As for the bootloops with TWRP, you only had issues with that, because the version you were trying to use was outdated and does not work on Kit Kat
Hmm found an interesting possible solution and would greatly appreciate your guidance. I found a ROM that supports KK and I think in this thread that it may indicate why I bootloop when trying to bootbin recovery. http://www.infamousdevelopment.com/...-recover-from-a-bad-flash-updated-for-kitkat/
I'm seriously considering following this whole tutorial of his to the letter. Would it be wise to do?
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Hmm found an interesting possible solution and would greatly appreciate your guidance. I found a ROM that supports KK and I think in this thread that it may indicate why I bootloop when trying to bootbin recovery. http://www.infamousdevelopment.com/...-recover-from-a-bad-flash-updated-for-kitkat/
I'm seriously considering following this whole tutorial of his to the letter. Would it be wise to do?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
You have already upgraded to Kit Kat, that part is done. and you ran CF_Autoroot correct in Odin correct? If you have done both steps all that is left is to Odin the Philz Touch Recovery that you downloaded.
Ok and yes I did both the first two steps you asked above. After I do flash philz can I flash a ROM it CM or PacMan as long ad they're 4.4.2?
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Ok and yes I did both the first two steps you asked above. After I do flash philz can I flash a ROM it CM or PacMan as long ad they're 4.4.2?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
As long as they are AOSP Roms that support both bootloaders yes, and as i've been told most if not all the AOSP Roms do support the Kit Kat bootloader that you are already on.
Ok thank you again. I will likely flash philz tonight (if hubby allows me to cuz I usually stay up all night til I got my phone the way I want it, ie no boot loops lol) I will report back to let you know if it works. This phone has been through hell and back with me but I've learned a lot!! Especially from contributors such as yourself. :thumbup:
Sent from my SM-N900T using xda app-developers app
Cool. I'm glad I read this thread. I too had same problems.
Sent from my NOTE 3 using Tapatalk