Related
I bought a second hand xperia play a few days ago and now looking to whizz things up a bit with a new Rom.
It's already been rooted but looks to have a stock Rom running
Here's the details
2.3.4
Kernal version [email protected]#10
Build number 4.0.2.A.0.42
Basically I'd like a properly established Rom without the bloatwear, every time I open task manager theres about 15 things open when I'm not using them
Sent from my R800i using XDA
Check the dev section out for a rom find something you like
Sent from my R800a using XDA App
thatsupnow said:
Check the dev section out for a rom find something you like
Sent from my R800a using XDA App
Click to expand...
Click to collapse
From my details above what do I have installed? I'm not too familiar with with all this :$
Sent from my R800i using XDA
Jokawild 2.5. Trust me....after using it you won't switch again till final ice is released.
jaygrae said:
Jokawild 2.5. Trust me....after using it you won't switch again till final ice is released.
Click to expand...
Click to collapse
Sounds good, how do I install it in simple terms? Sorry if I sound like a orange :-S
Is it just a straight install or do I need to mess with kernels etc,
How's yours set up? Rom/Kernel etc
Help is much appreciated
Sent from my R800i using XDA
mozzy said:
Sounds good, how do I install it in simple terms? Sorry if I sound like a orange :-S
Is it just a straight install or do I need to mess with kernels etc,
How's yours set up? Rom/Kernel etc
Help is much appreciated
Sent from my R800i using XDA
Click to expand...
Click to collapse
Since it already has doomlord's kernel on it, it is rooted and the bootloader is unlocked, so you can probably use fastboot to install most roms. If you want compatibility for all the games, stick with GB. If you go to an ICS build, you'll likely have problems with certain games crashing, graphical errors, or gamepad not working.
I have no problems with the gamepad so far using DarkForest ICS.
I tried ICS++, I prefer Darkforest still. Probably sticking with it till the real ICS.
There are so graphical issues, but its pretty nice, no bloatware either.
If you already have a kernel with recovery, all you need to do is install the .zip file for the ROM through it.
Put the zip on your sd card, reboot the phone. While it boots and the light turns blue, press the back button.
I attempted to update the kernel earlier and bricked my phone, I the fastboot method and actually completed the flash, when I powered on the mobile it was just displaying a black screen,
After looking about I got the stock rom and flashed it, and its working again!
Now my mobile is on stock rom with stock kernel,
It displays a message saying theres a system update available but when I connect to pc I get some message saying the software cannot be installed because the device has unauthorized software on it, I also got this message before I flashed to the stock firmware so it seems that they know my mobile was rooted etc and cant update through their software...
Could someone kindly walk me through what I need to do to put doomkernel v13 and jokawild rom on,
Thanks
Sent from my R800i using XDA
How does jw with doomkernal 13 compare to team stock with stock kernal?
swebosdev said:
How does jw with doomkernal 13 compare to team stock with stock kernal?
Click to expand...
Click to collapse
I wish I knew
Sent from my R800i using XDA
SirRudolph said:
I have no problems with the gamepad so far using DarkForest ICS.
I tried ICS++, I prefer Darkforest still. Probably sticking with it till the real ICS.
There are so graphical issues, but its pretty nice, no bloatware either.
Click to expand...
Click to collapse
have you tried Age of Zombies? and hows your battery? last time I used darkforest I'd only get 5 hours of battery life with just texting and listening to music :S
Any suggestions,
Sent from my R800i using XDA
mozzy said:
I attempted to update the kernel earlier and bricked my phone, I the fastboot method and actually completed the flash, when I powered on the mobile it was just displaying a black screen,
After looking about I got the stock rom and flashed it, and its working again!
Now my mobile is on stock rom with stock kernel,
It displays a message saying theres a system update available but when I connect to pc I get some message saying the software cannot be installed because the device has unauthorized software on it, I also got this message before I flashed to the stock firmware so it seems that they know my mobile was rooted etc and cant update through their software...
Could someone kindly walk me through what I need to do to put doomkernel v13 and jokawild rom on,
Thanks
Sent from my R800i using XDA
Click to expand...
Click to collapse
Flash stock ROM with flashtool, load fastboot, flash kernel image for DooMKernel, boot into recovery, clear cache, apply the update.zip for jokawild, done.
If you need more detailed instructions I'll write out a full guide later when I can use my home PC.
Actually, I was thinking of doing a full guide with pictures anyway.
Sent from a Galaxy far, far away
captain67 said:
Flash stock ROM with flashtool, load fastboot, flash kernel image for DooMKernel, boot into recovery, clear cache, apply the update.zip for jokawild, done.
If you need more detailed instructions I'll write out a full guide later when I can use my home PC.
Actually, I was thinking of doing a full guide with pictures anyway.
Sent from a Galaxy far, far away
Click to expand...
Click to collapse
Oh I have got jokawild flashed and doomkernel but having battery issues with the latest update,
I wanted to know any other Rom suggestions
Sent from my R800i using XDA
mozzy said:
Oh I have got jokawild flashed and doomkernel but having battery issues with the latest update,
I wanted to know any other Rom suggestions
Sent from my R800i using XDA
Click to expand...
Click to collapse
if u want to play games, better stay with gb.. for ics, darkforest is the best for me
---------- Post added at 02:23 PM ---------- Previous post was at 02:20 PM ----------
mozzy said:
I attempted to update the kernel earlier and bricked my phone, I the fastboot method and actually completed the flash, when I powered on the mobile it was just displaying a black screen,
After looking about I got the stock rom and flashed it, and its working again!
Now my mobile is on stock rom with stock kernel,
It displays a message saying theres a system update available but when I connect to pc I get some message saying the software cannot be installed because the device has unauthorized software on it, I also got this message before I flashed to the stock firmware so it seems that they know my mobile was rooted etc and cant update through their software...
Could someone kindly walk me through what I need to do to put doomkernel v13 and jokawild rom on,
Thanks
Sent from my R800i using XDA
Click to expand...
Click to collapse
u have unlock bootloader.. it cant be update using pc companion.. u need to relock it back using .ftf file via flashtool
Hello Guys,
I think I have a problem with Flash Tool. Everytime I want to flash stock ICS .587 It says "Error 31".
Also my phone doesnt start up. It just vibrates and turns off again.
I used this Rom http://forum.xda-developers.com/showthread.php?t=1979829 and wanted to change to Slim Bean.
I hope somebody have a solution for me.
Another questin. I cant flash kernels anymore since u upgraded my PC to Win8... So does anyone have an idea how to fix this?
Thanks :good:
Try
seus
Sent from my LT15i using xda app-developers app
Hi there,
I definitely can't install any latest ROMs on my ARC (Ultimate HD 3.x, Zelly Cream,...) using CWM.
The latest ROM that doesn't hang during boot or just give black screen is Ultimate HD 2.0.3 (Ultimate HD MOD works either)!
- I've tried different kernels like Lupus, Fusion, RUSH as recommended in several threads but without any chance with latest ROMs...
- I've also tried re-download ROMs and kernels... No change.
- I've also tried rebooting without SD in case it sucks... No change.
For info I'm not noob, I use custom ROMS since HTC Legend...
I obviously erase /CACHE /DATA /SYSTEM /SD-EXT also dalvik and battery stats each time I install custom roms and always do clean install. No upgrade.
- My bootloader is unlocked,
- I've got one sd-ext partition,
Did I missed any new process that 100% require to use flashtool instead of CWM to flash latest ROMs? If so it suck
I don't really understand the issue this time except hardware failure but I don't have any issue of any kind with any previous ROM. No hang, no bootloop...
Any help would be very welcome
Thanks
Have you tried flashing original Stock. tft then flashing?
SevenD2 said:
Have you tried flashing original Stock. tft then flashing?
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
Nope. Never had to do so for any ROM since the day I unlocked my bootloader. And it's a so sudden behavior...
Do you think it could work ? I mean is there any specific reason that it could solve the problem? Does the latest ROMs use some brand new drivers or something else that may require that?
I'll give a try because I've checked my baseband and I'm 70 while you're 83... Am I wrong or some ROM do change the baseband while some other don't ?
I did use flashtool but only to update the baseband. not for flashing custom rom... That may be the problem
I start feeling ashamed LOL !!!
yeah, try flashing the latest firmware / baseband first.
neo2k12 said:
yeah, try flashing the latest firmware / baseband first.
Click to expand...
Click to collapse
Flashing the latest ftf should include the baseband anyway so you shouldn't need to flash separately unless flashing something different.
Yeah I'm sure it will do the trick... I'm definitely noooooob to forgot that baseband stuff... T_T LOL
I'll confirm tonight.
Thanks everyone !
nop
Hi guys,
I've flashed the latest baseband (83) and it didn't change anything!
I've flashed RUSH kernel and install Viper Xperia V4 + modules + baseband 83 libs and it still hang at the same moment. with this ROM it freeze during the boot animation (4th times xperia logo appears if this detail can be useful).
RUSH works fine. Once again if I install Ultimate HD 2.0.3 I've got no issue at all...
I definitely don't understand what's going on...
Odp: Can't install any latest ROM and no I'm not noob !)
Did you flash LT15i ftf or LT18i ftf?
All new ROMs are getting more features and they are getting bigger in size. Arc allocates less space to /system - maybe that's the reason.
When I was on CM10 on LT15i firmware I had about 1MB free space on /system after clean install.
Try flashing LT18i ftf before flashing any custom ROM.
Sent from my Ultimate LT15i using xda app-developers app
michel_666 said:
Did you flash LT15i ftf or LT18i ftf?
All new ROMs are getting more features and they are getting bigger in size. Arc allocates less space to /system - maybe that's the reason.
When I was on CM10 on LT15i firmware I had about 1MB free space on /system after clean install.
Try flashing LT18i ftf before flashing any custom ROM.
Sent from my Ultimate LT15i using xda app-developers app
Click to expand...
Click to collapse
I flashed LT18i one from papayayoghurt
http://goo.im/devs/papayayoghurt/anzu/Basebands
Re: Can't install any latest ROM and no I'm not noob !)
So how did it go?
You okay now?
Sent from my Xperia Arc using xda app-developers app
No I'm not
Flashing LT18i baseband 83 + libs didn't change anything...
Re: Can't install any latest ROM and no I'm not noob !)
Okay.Try doing it this way.
Flash stock 0.587 ftf.
Fast boot kernel that you want.
I presume the ROM that you need is already on your sdcard.
Go into recovery.Wipe data then go to mount/storage- format/system.Then choose the ROM zip and flash.
Tell me what happens.
For now do not choose any other baseband.Just use stock 77 which is included in the stock ROM.
Sent from my Xperia Arc using Tapatalk 2
sandroidnz01 said:
Okay.Try doing it this way.
Flash stock 0.587 ftf.
Fast boot kernel that you want.
I presume the ROM that you need is already on your sdcard.
Go into recovery.Wipe data then go to mount/storage- format/system.Then choose the ROM zip and flash.
Tell me what happens.
For now do not choose any other baseband.Just use stock 77 which is included in the stock ROM.
Sent from my Xperia Arc using Tapatalk 2
Click to expand...
Click to collapse
Ok I'll do so! But I won't be able to do it before EOD Paris time.
Thanks for helping.
No luck...
I've reflashed stock 587.ftf, boot ok on stock at this point.
Then flashed Rush kernel, wiped everything as I used to do and flashed Viper V4...
It's still hanging at the very same point during boot animation! :silly:
Re: Can't install any latest ROM and no I'm not noob !)
im_bol2riz said:
No luck...
I've reflashed stock 587.ftf, boot ok on stock at this point.
Then flashed Rush kernel, wiped everything as I used to do and flashed Viper V4...
It's still hanging at the very same point during boot animation! :silly:
Click to expand...
Click to collapse
Try AOKP m1r3 rom with ArcFusioN4.4 kernel.
Sent from my Xperia Arc using xda app-developers app
sandroidnz01 said:
Try AOKP m1r3 rom with ArcFusioN4.4 kernel.
Sent from my Xperia Arc using xda app-developers app
Click to expand...
Click to collapse
It boots! Does this ring the bell regarding what's happening ?
I'll don"t really mind to give a try to this ROM but I would love to understand what goes wrong
Anyway a big thanks for helping.
Re: Can't install any latest ROM and no I'm not noob !)
Always consider evry custom ROMs instruction. Like in Viper thread, did you note the procedure in flashing the stock firmware?
Sent from my Xperia Arc S using Tapatalk 2
Re: Can't install any latest ROM and no I'm not noob !)
I am pretty sure that there was nothing wrong in all your attempts earlier.
Sometimes flashing a new rom takes a bit too long to boot up.
I do change roms very often but when I first started I had the very same problems that you faced.
We are so eager to use the newest rom that we do not give a chance for it to read the entire stuff that we've got in our device.
Sometimes first boot takes such a very long time.This is where we make our mistake.
We presume its not working.Or there's something wrong with the rom and a host of other things runs thru our head.
I for one was a impatient guy.Not so now.I just leave the phone alone after flashing.Use my secondary,much cheaper phone, till I feel I've given my arc ample time to sync completely with latest rom.
Sent from my Xperia Arc using xda app-developers app
sandroidnz01 said:
I am pretty sure that there was nothing wrong in all your attempts earlier.
Sometimes flashing a new rom takes a bit too long to boot up.
I do change roms very often but when I first started I had the very same problems that you faced.
We are so eager to use the newest rom that we do not give a chance for it to read the entire stuff that we've got in our device.
Sometimes first boot takes such a very long time.This is where we make our mistake.
We presume its not working.Or there's something wrong with the rom and a host of other things runs thru our head.
I for one was a impatient guy.Not so now.I just leave the phone alone after flashing.Use my secondary,much cheaper phone, till I feel I've given my arc ample time to sync completely with latest rom.
Sent from my Xperia Arc using xda app-developers app
Click to expand...
Click to collapse
coldmoonbeam said:
Always consider evry custom ROMs instruction. Like in Viper thread, did you note the procedure in flashing the stock firmware?
Sent from my Xperia Arc S using Tapatalk 2
Click to expand...
Click to collapse
No guys, I'm 100% sure that it sucks. No offense to you but as I've said on my first post I'm not that noob on flashing ROMS, rooting devices... Even if I've left some stuffs due to the time I didn't changed my baseband... Indeed I read each ROM instruction I know the basic rules of the forum. Anyway I either don't take any offense and I understand why you write that...
I did precise at what time the boot process hang but it definitelty goes onto boot loop whatever the recomended kernel has been flashed.
I've left my phone rebooting several times knowing that it won't stop nut just in case, I've also cleaned all caches just before first boot...
Honestly I felt ashamed enough having forget that baseband stuff to not double checked if I did something wrong
I gave another try to Viper ROM some times after successfully boot onto AOKP M1R3 and obtain the same hang and bootloop.
Thanks all :highfive:
Last status...
I managed to install "Xperia T ICS Rom V7.1.0 For Arc / Arc-S" which looks interesting therefore I think I'll keep it.
coldmoonbeam may be right regarding that stock ftf... I did retrieve one from other source and maybe it wasn't the right one compared to the one I've got from Xperia T ICS Rom thread...
I'll try to flash VIPER again now and post the result. Then close the thread.
SOLVED!
That ftf stuff was the problem. It works with the one I used to flash Xperia T ICS Rom.
Thanks all for your help :highfive::good:
I am trying to upgrade my Virgin ROM to the 9.12 build but get a fail upon trying to flash it. The background.... I'm using TWRP recovery and have tried the chainfire root method. Here are the results:
As you can see you can see some conflicting information... all shots were taken in sequence. I'm thinking the fail in twrp is coming from the system not having root but the info is telling me otherwise....
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Do you have the latest SuperSU version?
I'm a little lost at what you are saying.
You flashed a rom, and it said fail, and you think it has to do with Root?
If you have TWRP installed it doesn't matter if you are rooted or not. It's going to over right the system partition regardless if you have root or not.
So it's either a bad download or bad transfer for it to fail.
Sent from my SGH-M919 using Tapatalk 4
I do have the latest SU version by chain fire. And maybe I'm doing something wrong the because I am running the virgin gpe ROM now and that flashed in twrp with no issues. Now when I go to install (after wiping) and select the 9.12 update that I downloaded it hangs on trying to open the zip and fails... I haven't changed any twrp settings but in the write options of twrp what boxes should be checked because system is not by default... Thanks for the replies!
Sent from my GT-I9505G using xda app-developers app
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
You can give CWM a try, I've been using it for a while without any issues. Out of curiosity what version if TWRP you are using? I think most people recommend TWRP 2.5.0.2. I'm using the latest version of CWM.
Sent from my GT-I9505G using xda app-developers app
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
norml said:
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
Click to expand...
Click to collapse
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
th3h0ff said:
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
Click to expand...
Click to collapse
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
mrvirginia said:
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
Click to expand...
Click to collapse
Im going to give the twrp 2.5.2 a try as it seems most of my troubles keep happening on the 2.6.3 build. Hopefully that works either way its back to CWM for me as well. Thanks again for taking the time to help out and again sorry about hijacking the thread for a page... Your ROM is absolutely perfect so I appreciate the efforts and time!,
Andrew
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
th3h0ff said:
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
Click to expand...
Click to collapse
Good to know you are out of trouble
Sent from my Nexus 10 using xda app-developers app
See you shoulda said you were running 2.6.3 lol
word of advice (and to all who run twrp)
DO NOT RUN ANYTHING GREATER THAN 2.5.2!!!!!!!!!!!!!!
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