New to GN2 - Sprint Samsung Galaxy Note II

Hi folks,
Just decided to retire my old S3 and when looking for a new phone my main requirement was to get a good DAC built in without breaking the bank or renewing my contract, ended up with the Sprint Note 2. Naturally I was excited but quickly put off by the stock ROM so I decided to root/flash, etc. This is what happened so far;
-Rooted with newest TWRP and root verified on stock rom (followed NK2 instructions)
-Made the big mistake of flashing now without backup, after trying a couple of roms I kept having the same problem (phone gets stuck in load animation indefinitely regardless of rom flashed)
-Gave up on custom roms so I flashed a rooted stock NE2 rom and phone turned on wooohooooooo
-But wait, no network connection, no voice or data, tried to flash modem zip file from http://forum.xda-developers.com/showthread.php?t=2139889 but it keeps saying zip is corrupt, redownloaded & recopied to SD with the same result.
Now I have a working phone but not so working since I can't place calls. What went wrong? any help is very very appreciated.

Phone works after flashing Alliance ROM but somehow now TWRP recovery is gone and phone is UnRooted which is less than ideal but it works nevertheless...
Now before I go off wasting a whole day flashing & waiting for battery to recharge can anyone please point me in the right direction?
I need to figure out the following:
-Root method that works, I'm on Alliance NE2 now
-Which recovery is best recommended for current ROMs?
-Need a kernel that enables audio features like Direct DAC & upsampling
-ROM that actually works with said Kernel and functions at least 90% with wifi tethering etc.?
Surprised it's this difficult with this phone coming from the S3 which took me no more than an hour first time rooting/flashing.

hhmmm 63 views and nobody able to help?
Currently stuck on this ROM, which is horrible because maps doesn't work well, pandora crashes, UI fc's left & right and to top it off the phone is sluggish in every way possible.
Unified Toolkit not working, drivers installed properly, ADB visible in device manager, debugging enabled yet phone can not be seen by Toolkit.
I really don't want to switch back to my cracked S3 but I'm not left with many options considering my note 2 is barely usable now.
Is anyone out there... there.... ere... ere... ere.....
lol seriously feeling like I'm the only person left in these forums.

Use odin to flash recovery but make sure you uncheck reboot option. Once flashed remove battery and while doing the recovery hotkeys insert battery. Now wipe everything and flash another rom.
Sent from my GT-N7105 using XDA Premium 4 mobile app

here's what I've done now;
-Flashed newest TWRP via Odin
-Wiped & flashed Rwilco12's NE2
-Rebooted and phone booted yipeeee
-No cellular connection, crap phone i hate you
-Rebooted to recovery & flashed NE2 Modem
-Rebooted again and recovery is now gone
So either I get root but can't use the phone as a PHONE
or I loose Root and get basically the same POS I started with.
I've given up on eye candy, custom rom, custom settings and my expectations have dwindled down to just ANY ROM + Root + Tether yet that can't even be accomplished. I know I'm doing something wrong but at this point I'm over 10 hours into trying to figure this out and have no idea what to do next. Anything?

Finally:
CWM Recovery - OmniROM - Micro Gapps - Devil Kernel - Rooted
In case someone is in my shoes and hating life, I'll save you a lot of headache by telling you that TWRP recovery does not work for 90% of the ROMs that are still available for this phone so use Phil'z CWM

oceanisbleu said:
Finally:
CWM Recovery - OmniROM - Micro Gapps - Devil Kernel - Rooted
In case someone is in my shoes and hating life, I'll save you a lot of headache by telling you that TWRP recovery does not work for 90% of the ROMs that are still available for this phone so use Phil'z CWM
Click to expand...
Click to collapse
Twrp 2.8.6.x works for almost every rom but you will find most users recommend philz. I as a wantabe dev will suggest philz 6.0.7.9 expect in a few rare cases with aroma installer needing twrp. Personally I have philz 6.9.7.9, twrp 2.8.6.0, shift dual recovery and devil dual recovery zip on my external sdcard. This way I always have what I need depending on what I am doing.
All this info along with solutions to every problem is here on xda already. It may take some time to find everything but really the users should do his homework before doing anything to the phone anyways.
Also if you read the rom thread (Alliance) you would know why you lost root. Simply put you updated supersu app and binary. It is a known issue on every ne2 based custom rom for this device.
Sent from my GT-N7105 using XDA Premium 4 mobile app

Hey thanks for the feedback.
Almost everything I tried on twrp failed, when flashing anything I follow all instructions in the OP's first page. In Alliance's case the resolution to the issue does not come up till page 23, I'll just be honest & say I haven't and probably will never read every page of comments before flashing a ROM, 10 pages okay but beyond that it's more trouble than it's worth.
Can that same issue happen with all other ROMs? on Omni I just ran Root Checker & it said not properly installed!

oceanisbleu said:
Hey thanks for the feedback.
Almost everything I tried on twrp failed, when flashing anything I follow all instructions in the OP's first page. In Alliance's case the resolution to the issue does not come up till page 23, I'll just be honest & say I haven't and probably will never read every page of comments before flashing a ROM, 10 pages okay but beyond that it's more trouble than it's worth.
Can that same issue happen with all other ROMs? on Omni I just ran Root Checker & it said not properly installed!
Click to expand...
Click to collapse
I will read every page myself even if it takes a week. You say reading it is more trouble than it is worth which is why you had that issue with Alliance. Same goes for your omni issue.
If you don't want to read that is up to you. A google search will normally help with common issues. I dont mind helping but you have to help yourself first. Not to be rude but I wont answer your omni question because you have not looked. Ypir issue is the number 1 issue omni users have.
Sent from my GT-N7105 using XDA Premium 4 mobile app

won't argue with your opinion as I have my own

oceanisbleu said:
won't argue with your opinion as I have my own
Click to expand...
Click to collapse
I see you edited that a bunch. I dont mind helping. I have been helping so far. Now about the omni gps. I only know on possible fix bit it is a pain.
1. Flash stock/stock based rom
2. Get gps lock
3. While locked and in app reboot to recovery
4. Wipe and install aosp rom & gapps or restore aosp backup
Then you might get gps lock.
Sent from my GT-N7105 using XDA Premium 4 mobile app

reading back I realized some clarity on my part would have been helpful rather than make a general statement.
So the issue with reading 25, 50 or a 100 pages isn't by choice (may have sounded arrogant the way I said it at first) but I work 50 hrs a week, I do work on my home myself, I rent out rooms to students, I have other projects going, etc. so a very very busy lifestyle. Not to mention the daily crap that tends to come up all the time the moment I get home from work so in short, I really can't afford the time to read in that much detail whether I want to or not.
Regardless, by no means am I lazy when it comes to research, notice my post count? yet I've been here since 2009, and since 09 I've had at least 8 different phones (windows phones too) I really try to figure out everything I need on my own so in this case I spent 3 days working on my initial issues, after that I posted this thread which was 8 days ago and had it figured out and finished yesterday (a few bugs aside), that's easily 10 days I spent at least an hour or two a day working on one thing. Surely you understand how frustrating that must begin to feel.
Regarding my last reply, haha I had to delete most of it because I realized I was beginning to take my frustration out on you when in fact you're the only person who actually offered help (still very very thankful) and to top it off I screwed up the rest of the reply when I mentioned GPS, got that mixed up with the topic we were actually discussing (losing root) this happened because I was reading through the GPS issues before I got to your reply and yah mixed it all up, so again apologies for the lack of clarity and thanks for your last reply, it's more straight forward than all the comments I found on that issue.
You won't have to explain anything else I promise haha and I did all this just now but want to verify I did it correctly so I don't come back to it again. After flashing ROM/Gaps/Kernel & supersu, never update supersu after running rom correct?. Root verified as of 30 minutes ago.
GPS, this one is a big big deal because I use it for work but I had already found the answer pretty quickly as I had read something about it before I even flashed Omni.

I do know how frustrating it can be. I have been in worse spots and had to create my own fixes which I have shared here. As far as time goes I understand that being a parent of 7 children.
I am still active here and always willing to help others long as they help themselves also. We seem to have gotten off badly. While some of your post seemed you had done nothing to help yourself. So lets forget earlier stuff and move on.
Yes you seem to have all the steps correct.
FYI android 5.0-5.0.2 all have gps issues but there is a flashable fix. Most new 5.1.1 builds have gps fixed.
If you run into any issues feel free to ask but include steps you have taken to fix the issue. The more you tell the better help you can get. Plus others wont think you are wanting to be spoon fed.
Sent from my GT-N7105 using XDA Premium 4 mobile app

haha thanks for understanding, very much appreciated.
7 kids??? where do you find the time? my situation does not fare in comparison :laugh:
Now that I've resolved the "failed" issue when flashing ROMs I may be brave enough to test some 5.x.x out, I had stuck to 4.x.x because I was under the impression that they were more stable...
Would you be willing to recommend any specific ROMs based on our discussion?
By the way, I tend to ramble on and on most forums that's a bit faux pas so I've sorta been conditioned to keep it sweet & short, clearly that is a bad approach on here, we live & learn

oceanisbleu said:
haha thanks for understanding, very much appreciated.
7 kids??? where do you find the time? my situation does not fare in comparison :laugh:
Now that I've resolved the "failed" issue when flashing ROMs I may be brave enough to test some 5.x.x out, I had stuck to 4.x.x because I was under the impression that they were more stable...
Would you be willing to recommend any specific ROMs based on our discussion?
By the way, I tend to ramble on and on most forums that's a bit faux pas so I've sorta been conditioned to keep it sweet & short, clearly that is a bad approach on here, we live & learn
Click to expand...
Click to collapse
Well I personally have a Frankenstein device. It started out as a sprint l900 but I removed the sdcard/sim board and put a n7100 board so I can use a cricket sim. This causes issues with calls on aosp so I run modified t0lte (n7105 international) roms.
As far as 5.1.1 roms I personally build 2. First is CyanideL (highly modified cm base) and broken (a highly modified slimroms base). Those two are really the only two worth flashing. There is also cm and I think a liquid rom but they don't have the features of the two I compile.
If you want a stock based rom I did the Community Rom (s5/n3 based) which is stable with only two issues. Spen clipping does not work and updating suoersu causes loss of root.
Sent from my GT-N7105 using XDA Premium 4 mobile app

jlmancuso said:
As far as 5.1.1 roms I personally build 2. First is CyanideL (highly modified cm base) and broken (a highly modified slimroms base). Those two are really the only two worth flashing. There is also cm and I think a liquid rom but they don't have the features of the two I compile, I believe Phill'z CWM download link is down as well.
If you want a stock based rom I did the Community Rom (s5/n3 based) which is stable with only two issues. Spen clipping does not work and updating suoersu causes loss of root.
Click to expand...
Click to collapse
wow CyanideL is you, how did I miss that?? looking at too many ROMs is how I suppose...
Going to CyanideL asap. Seriously thank you for keeping the CyanideL thread up to date, it drove me crazy to read & read & read in ROM threads for a while until I decided "okey let's give this one a try" only to find out that the download links are broken or the files are no longer there, had that issue with Omni till I found comparable files on another website (gapps I think it was) and Phill'z CWM thread has a dead end download link as well.
I was really really wanting CyanideL to work for me last week (when I was having the flashing issue) and was so bummed out every time I failed to flash it. I plan to make a donation as soon as I get it working, I feel like I owe you simply for the time you've spent on my thread alone and of course I love supporting people who support families :highfive:

oceanisbleu said:
wow CyanideL is you, how did I miss that?? looking at too many ROMs is how I suppose...
Going to CyanideL asap. Seriously thank you for keeping the CyanideL thread up to date, it drove me crazy to read & read & read in ROM threads for a while until I decided "okey let's give this one a try" only to find out that the download links are broken or the files are no longer there, had that issue with Omni till I found comparable files on another website (gapps I think it was) and Phill'z CWM thread has a dead end download link as well.
I was really really wanting CyanideL to work for me last week (when I was having the flashing issue) and was so bummed out every time I failed to flash it. I plan to make a donation as soon as I get it working, I feel like I owe you simply for the time you've spent on my thread alone and of course I love supporting people who support families :highfive:
Click to expand...
Click to collapse
Well the donation would be nice but understand when you hit my donation button/link it will take ypu to the Red Cross donation site. That is not a mistake. I personally dont take donations and feel of someone wants to donate something it should go where it can be used by those who need it.
Sent from my GT-N7105 using XDA Premium 4 mobile app

Related

[DEVELOPERS] TWRP Touch Recovery for Epic Touch

Since a lot of people have asked me about TWRP 2 for Epic Touch and SGS2 devices, here's the deal:
1) I don't own an Epic Touch or a SGS2 device of any kind.
2) As some may be aware, many Samsung devices do not have and/or properly use a recovery partition. Instead the recovery is packed as a second ramdisk or as a separate recovery.rc in the same ramdisk in the boot image. This means that every time you install a new ROM or kernel, you will get stuck with whatever recovery is included with the boot image.
3) We do have a process that lets you inject TWRP into boot images that are still using the dual ramdisk setup typically found in CM7 boot images. I believe that somewhere along the development path of CM9, the boot image packing method changed to a single ramdisk with 2 init files (recovery.rc). This type of setup is much more difficult (if not impossible) to do "injection" and since I don't have a device in hand to work with I have no plans to attempt to create an injection method for this new type of boot image. The injection process still appears to work on CM7 boot images and some kernel devs for SGS2-type devices have not moved to the new method (yet).
4) We now have code that compiles in CM9. This new code base is much simpler to get started with - you just replace the bootable/recovery folder with the TWRP source code and grab a copy of our slightly modified 1.20 busybox code and you're ready to compile TWRP after adding a few build flags to your BoardConfig.
5) The TWRP source code is all public, including the GUI. It's pretty easy to compile and work with and we have a nice guide to help you out here: http://tinyw.in/nP7d
If you need help integrating TWRP into your builds or have questions about compiling TWRP, feel free to find us in #twrp on Freenode. TWRP works very well with thew GooManager app and if you host your ROM on http://goo.im, your users can receive notifications of ROM updates and easily download and flash the update almost like a regular OTA update. In addition, http://goo.im now supports automatic differential zip creation. You upload an update to your ROM and goo will create a zip with just the changes. Your users get smaller downloads, faster installs, and less wear and tear on the device since only the updated / deleted files get replaced, but this functionality is only easy to use with a supported recovery like TWRP. Please consider adding TWRP to your builds and using http://goo.im and GooManager! All of this functionality is free to you and your users!
If you're feeling really adventurous, you're welcome to install this for the Epic Touch after installing a copy of CM7. I was told by a tester that it was working fine but use at your own risk and be prepared to Odin / heimdall a working boot image if something goes wrong! Note that backups and restores done in TWRP / CWM are not easily interchangable!
http://goo.im/devs/OpenRecovery/epictouch/openrecovery-twrp-2.1.2-epic4gtouch-signed.zip
I can probably create the same kind of a zip for SGS2 International if someone is willing to stop by #twrp on Freenode to test it. I do know that someone has successfully tested a ramdisk on the SGS2 with Exynos so TWRP should work on this device with relative ease.
Also note that it appears for the time being that most Samsung devices released in the USA where all team win members live, are going to be using Qualcomm chipsets instead of Exynos. This means that the only Samsung device that's readily available in the USA that uses the new boot image methods is the Epic Touch. We have a release for the AT&T Galaxy Note and Skyrocket but both of these devices use the Qualcomm chipset which uses a "normal" and separate recovery partition.
No idea what this is about but I got the second post! Woot
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
abadasstanker69 said:
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
There is a working CM7 for the E4GT. It's posted over at Rootzwiki. TWRP worked fantastically on my Evo and Evo 3D. Glad to see we have another option besides CWM. Hopefully we can get past the bricking issue with ICS roms and I can throw this on my phone permanently.
Thanks Dees_Troy!
Agree worked awesome on my e3d looks to be great
Thanks for this
Sent from my SPH-D710 using xda premium
Team win ftw!!
Sent from my SPH-D710 using xda premium
I love using TWRP and goo.manager on my cm9 touchpad. So easy to use. Glad our amazing devs have more options.
Just wanted to say I used TWRP on my 3D and Nexus S and was my favorite recovery hands down. Would love to see it come to the Epic Touch.
Sent from my SPH-D710 using Xparent ICS Blue Tapatalk 2
I'm going to second everyone that likes twrp. I also enjoyed the recovery very much and it was the one thing I missed when moving to e4gt. I can't wait for source on ICS. If someone doesn't build it into a kernel, I'll be doing some kernel research and building it for myself.
Sent from my SPH-D710 using Tapatalk 2
This is great news I'm tired of not having a working recovery on ics
abadasstanker69 said:
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
first off the evo shift is an older lower end phone, so performance on any recovery besides cwm which is so basic is probably iffy. TWRP has been pretty amazing on the evo3d and also on my Gnex, and if it gets ported in any working for on the e4gt id be happy to use it for my wife's phone.
if i understood this correctly, twrp recognized the issue with a constant recovery on the e4gt, and they are basically giving us the source to build it into our roms instead of the the stock recovery, so its atleast there on install. it would be nice to see the developers working on cm9 on this phone integrate it into the rom.
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Kebetz said:
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Click to expand...
Click to collapse
i want a working one already because i dont have the means to get mobile odin, and im rarely home, i came from the og epic and most of my flashing was done on the go. Now im lucky to update my rom once a week. A working recovery that wont brick my phone is a huge plus for people on the go
Kebetz said:
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Click to expand...
Click to collapse
I don't mind flashing the EL26 Stock CWM kernel at all. With Mobile Odin it literally takes a minute tops. But I like having the best on my phone and IMO the best recovery out right now is TWRP. It's always worked REALLY well for me. Not one single issue ever. Add in the other features, like compressing backups to save space which may not be a big deal with this device but anyone who's used Sense 3.0 could testify how awesome that feature is. Along with being able to theme every aspect of the recovery and as a themer I just love that option. That's just to name a few. So again, in my case it's not about being lazy but more about wanting the best available for my phone. So if TWRP is a possibility I would love to see it.
I have to agree with tiffany. It is more about the recovery itself. I use mobile odin and take no issue with the current methods but I also would like to have TWRP running on my phone. Hopefully source is released soon and we can take advantage of this. Thank you for posting the links for it and hopefully one of our devs can help to make this happen.
Ok, I admit, odining back to el26 isn't something to complain about for normal flashing. But when trying to alter system files to get the result you are looking for can become somewhat frustrating when a boot loop occurs. Normally a battery pull and a quick flash gets you back in the game. In my experience though, as I'm sure other cracks flashers can agree, sometimes you just have to flash something new, right before you step out the door. Lo and behold you realize you have just set yourself up for failure, failure to boot that is. As I stated in another thread, a lot of folks have busy lives and don't spend every moment reading xda, all they want to do is grab what's hot and flash it with the same procedure as every other Android device that they have come to know and love. In my opinion, working recovery = happy forums. And soon enough we will, and when we do, I want to be sporting TWRP.
Sent from my SPH-D710 using Tapatalk 2
Why all the fuss over something that you use for 5-10 minutes when you flash a ROM, theme, etc.? How much time are you spending in Recovery?
The next thing you know people will want the "Download" mode to be themed and "prettied up" too.
Does anyone remember what it took to customize phones 4-5 years ago? Oh wait, this is XDA, I forgot it's the land of "gimme gimme gimme" and hardly ever about "thank you" or "how can I help you with that?". Users just want to be "alpha" testers so that they can have the newest, hardly do they ever upload logcats, dmesg logs, or help in troubleshooting.
-Daryel
daryelv said:
Why all the fuss over something that you use for 5-10 minutes when you flash a ROM, theme, etc.? How much time are you spending in Recovery?
The next thing you know people will want the "Download" mode to be themed and "prettied up" too.
Does anyone remember what it took to customize phones 4-5 years ago? Oh wait, this is XDA, I forgot it's the land of "gimme gimme gimme" and hardly ever about "thank you" or "how can I help you with that?". Users just want to be "alpha" testers so that they can have the newest, hardly do they ever upload logcats, dmesg logs, or help in troubleshooting.
-Daryel
Click to expand...
Click to collapse
Sure this is true of some but I get thanked all the time for the work I do. There will always be the gimmie gimmie gimmie people, no matter what your doing.
And yeah if I could theme download mode I probably would. Just the way I am.
graffix31 said:
I love using TWRP and goo.manager on my cm9 touchpad. So easy to use. Glad our amazing devs have more options.
Click to expand...
Click to collapse
For those who haven't seen this in action, its worth a look. It is nice to open up goomanager and see all of the latest ROMs and versions that are hosted in goo. You can select the ROM you want and the script flashes it for you and IT WORKS! It is very slick. I would love for a dev to take this on!
Would love to see a themed download mode
Sent from my SPH-D710 using Tapatalk

[Q] Newbie Request For Assistance

Hello All,
aXcelio here…..
I'm new to the world of Android switched from the iPhone….(was and still am a loyal user of IOS devices for the better part of 5 years)…..but out of shear boredom, I made the decision to decided to make the switch and I for the most part could not be happier. In doing so I picked up a Galaxy Note II SGH-1317 (AT&T), I've updated the stock rom (I think that's what its called) to JellyBean 4.2.1……now I'm in a place where I want take advantage of some of the feature embedded in CM (it looks really cool)……
So a buddy of mine, who's been running with droid's for as long as I've been running IOS decided to give me a hand in getting my device rooted……we used an exploit called EXYNOS, and installed TWRP (again forgive me ignorance if I'm speaking out of term…I'm learning, or trying too), everything appears to be running without incident, (with the exception of my not being able to create any backup…as the system tells me that I don't have any free space)….get back to that in a lil bit.
Now….I scored the CM site as well as XDA, but haven't really been able to find what I'm looking for (some of which could be out of fear of destroying my device, and some of which is based on a lack of understanding….more I think though of destroying my device……..I should note that I completely understand that any of that any info I get here or there…..is as is, and without any guarantee.) So here I am reaching out to you folks for some guidance……..with that allow me to ask a couple of questions…..
In an effort to get a better understanding of what my buddy did…..I would like to go through the process of setting my device back to defaults (as if I just brought it home from the store) no root, no play apps that I've installed….(I can do that later, and I'm not overly concerned about losing anything) and re-root the device…..that being said, is there a way to that (set the device back to defaults)….I've seen one article using the stock firmware, (which I've downloaded) and another which states that I can do a factory reset which will unroot the device…(but not sure what approach to take or for that matter I should even worry about that)
The second thing I'm wondering about is this……most of what I've read regarding the install of CM is that I need clockwork recovery (or something along those lines) but I have TWRP…..if I opt to not reset the phone back to factory default and unroot (or find that I really don't need to move in that direction) can I install CM using TWRP?…..if I need clockwork, can I instal this over TWRP……or do I need to do something different?
a
The last thing I have (at least for right now) is this….assuming I can move forward with the install and configuration of CM, I wonder if any of you can provide a step by step guide on how I go about this on my particular device……I've seen this article well as this ones these however appear to be for version 10, of CM…but I see there is a 10.1……I read another article (but can't seem to find it now…which stated that it worked with my device and 10.1, with a link but all of the nighties….seemed to be specific to the Galaxy Note…..not the Note II…..and again I would much rather reach out to you guys for guidance prior to doing anything…..The last question I have is I see there is a version 7100 of my phone and then one that says something about LTE (but not specific version……) is the SGH-1317 an LTE device that is version agnostic (if you will)….in other words if I see a post for an LTE GNII is that speaking to my device or something else……
Thanks a lot……
aXcelio
If your all ready rooted why go back to stock?
You don't have to install CWM TWRP is fine as your main recovery.
don't install any ROM for the N7100, that is the non LTE version of the Note 2, it will brick your phone.
CM10 is Android 4.1.2 Jelly Bean. CM10.1 is 4.2 Jelly Bean.
Read the forums for the specific ROM it will give instructions on installing the ROM even if it mentions to use CWM, installing with TWRP is fine.
READ READ READ and have fun
I think i understand, you want to reset and do all this stuff on your phone yourself.
? You would would have to Odin your phone back. Either mobile Odin or one for pc. Pretty simple task once you get the files you need. Think that's right..
Edit: as the guy above me said either is fine. Just preference in what recovery to use. I would suggest to only use cmr based recovery as those seem to be more friendly with development programs and roms than the official by koush that you see in play store. I wouldn't even downloaded it.
Sent from my SGH-I317 using xda premium
nidnarb said:
I think i understand, you want to reset and do all this stuff on your phone yourself.
? You would would have to Odin your phone back. Either mobile Odin or one for pc. Pretty simple task once you get the files you need. Think that's right..
Edit: as the guy above me said either is fine. Just preference in what recovery to use. I would suggest to only use cmr based recovery as those seem to be more friendly with development programs and roms than the official by koush that you see in play store. I wouldn't even downloaded it.
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
PC Odin is more safe for the record
Here is a link to a post that breaks down the basics of starting from scratch, rooting and installing clockworkmod and then flashing a ROM. The instructions are in reply to a gentleman inquiring about the Jedi ROM but the instructions will be good for most other ROMs out there. Just check the installation instructions in the op of any rom to make sure there is not something else required for install.
http://forum.xda-developers.com/showthread.php?p=35726061
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

[Q] Reboots once at start up

The last few weeks I've noticed something odd which as far as I can tell is harmless but would like to understand. When I restart my Note 2 it goes through the entire start up process to the point of being on the lockscreen (perhaps a little further as I can get to home screen). It then spontaneously reboots itself! After that reboot everything appears to be running fine. Any explanation as to why this might happen and how to correct. My device is rooted. Use philz kernal 4.87. I also tried going down to 4.65 but no change.
Thanks!
What other mods do u have? can you link me to the kernel
deeznutz1977 said:
What other mods do u have? can you link me to the kernel
Click to expand...
Click to collapse
Hi. The kernel is from this thread.
http://forum.xda-developers.com/showthread.php?t=2028103
It has many nice features. I'm struggling to recall when this all started. It was before I upgraded to 4.12 via kies. I actually have not done a lot of mods as I reserve my tinkering for my Note 1 and use the Note 2 for my daily drive. But on the Note 2 I first used chainfire scheme to root. Shortly after that I used the Xposed framework to have unlimited apps in multiview. Then a bit later flashed the Philz kernal (Used mobile odin to do that the first time).The other thing I use that depends on root is linux on android and titanium backup. I look at this as rather modest mods.
I'm considering starting again from scratch but if you have some suggestions I might give it a go. I'm still learning about android (here is another opportunity!) coming from a N900. It seems there is a possibility it is a bit sensitive as it is booting up such that if an app is attempting something before the boot up is completed it triggers it to reboot. (Sorry if that is vague sounding). Is there a system log I can check to possibly track this down? Let me know if you need any specific information and I'll try to provide it. Thanks!
mscion said:
Hi. The kernel is from this thread.
http://forum.xda-developers.com/showthread.php?t=2028103
It has many nice features. I'm struggling to recall when this all started. It was before I upgraded to 4.12 via kies. I actually have not done a lot of mods as I reserve my tinkering for my Note 1 and use the Note 2 for my daily drive. But on the Note 2 I first used chainfire scheme to root. Shortly after that I used the Xposed framework to have unlimited apps in multiview. Then a bit later flashed the Philz kernal (Used mobile odin to do that the first time).The other thing I use that depends on root is linux on android and titanium backup. I look at this as rather modest mods.
I'm considering starting again from scratch but if you have some suggestions I might give it a go. I'm still learning about android (here is another opportunity!) coming from a N900. It seems there is a possibility it is a bit sensitive as it is booting up such that if an app is attempting something before the boot up is completed it triggers it to reboot. (Sorry if that is vague sounding). Is there a system log I can check to possibly track this down? Let me know if you need any specific information and I'll try to provide it. Thanks!
Click to expand...
Click to collapse
That's recovery not a kernel.. 1, Backup all your apps&data with titanium . 2,download this: http://forum.xda-developers.com/showthread.php?t=1975560.. 3, Factory reset& wipe caches 4, flash the downloaded file in odin.. Dont flash anything else reboot, setup your phone. now one by one try out your mods you want rebooting to check if all is well.... Let me know how it goes
deeznutz1977 said:
That's recovery not a kernel.. 1, Backup all your apps&data with titanium . 2,download this: http://forum.xda-developers.com/showthread.php?t=1975560.. 3, Factory reset& wipe caches 4, flash the downloaded file in odin.. Dont flash anything else reboot, setup your phone. now one by one try out your mods you want rebooting to check if all is well.... Let me know how it goes
Click to expand...
Click to collapse
Thanks again. You're right. That work by Philz is recovery not kernal. I've gotten into a bad habit of calling it a kernel. I think the title in the thread used say kernal but I see it has changed. I've since removed 4 or 5 apps and since then I haven't seen the extra reboot take place. So far I've rebooted 7 times today. Doesn't mean the problem is solved but it is certainly happening less frequently! If I spot it happening again I will give mrRobinson's rom a go.
mscion said:
Thanks again. You're right. That work by Philz is recovery not kernal. I've gotten into a bad habit of calling it a kernel. I think the title in the thread used say kernal but I see it has changed. I've since removed 4 or 5 apps and since then I haven't seen the extra reboot take place. So far I've rebooted 7 times today. Doesn't mean the problem is solved but it is certainly happening less frequently! If I spot it happening again I will give mrRobinson's rom a go.
Click to expand...
Click to collapse
Hey, if you need help dont hesitate to pm me

Samsung Galaxy S4 Problem

Hello everyone,
I really need your help with my wife's Metro PCS Samsung GS4 M919N.
The thing is, we are now living outside the US so I had to unlock her phone. After ordering the unlock codes, I decided to root the phone and use a custom ROM while waiting for the codes.
That is why I found this guide here: androidforums.com/metropcs-galaxy-s4-all-things-root/790899-metropcs-galaxy-s4-all-things-root-guide.html
So while reading the guide, I aimed to have the following accomplished at the end:
Recovery: TWRP
Custom ROM: CyanogenMod 10.2.1
I then started doing the guide for the TWRP recovery by using Odin. I got the message saying that the flashing passed and went ahead to restart to recovery to install CM 10.2.1 as a custom ROM. The thing is that I keep on restarting to the stock recovery not TWRP. So I went to YouTube and found a video showing how to flash TWRP using GooManager. After following that guide, I went to restart to recovery and I successfully got into TWRP.
Now, to achieve my goal, all that's left to do is to flash CyanogenMod 10.2.1 (jfltetmo).
Before doing that, I decided to make a backup. After using TWRP to do a backup, I proceeded to installing the custom ROM + gapps (wiped with the default settings). Everything was working I think (I handed the phone to my wife so she was he one testing it). After some time, she decided she wants the stock ROM instead so I decided to download the androidforums.com/metropcs-galaxy-s4-all-things-root/783769-rom-recovery-flash-able-stock-m919nuvuamf2-rooted-deodexed-rom.html ROM.
I flashed the newly downloaded ROM + gapps (same file). This time, I couldn't get the gapps to work probably because it was meant for another version. So I decided to just restore from the backup I created earlier.
So, the usual stuff. Wipe. Restore. Restart.
Seems to be going smoothly because my wife was happy to see the old ROM she was used to.
Until the phone started to restart on it's own. (It's pretty much downhill from here on out).
At first I thought it was just a random thing that probably would never happen again. I was wrong as it became more frequent as days went by.
Recently I can't just restart the phone, I would have to remove the battery and then restart it. Now, it's getting really hard to restart the phone. Please help me fix this. I prefer to leave the phone rooted, but if the fix unroots the phone then so be it, anyway my wife prefers the stock ROM so only the unlocking was necessary.
Metro PCS Samsung Galaxy S4 M919N
Recovery:
TWRP 2.6.3.1
ROMs:
Stock Metro PCS
CyanogenMod 10.2.1
Let me know if you need more information from me. Hopefully I can restart the phone so I can give you some version numbers.
Thanks everyone!
I didn't read everything but just wanted to say
VERY GOOD THREAD!
this is how threads should be done. Very descriptive, organized, told us everything you did and asked for help! Good job man! Only negative is it prolly should have gone in Q&A section but irregardless very good thread!
About your issue, I recommend flashing stock Odin tar file to everything back to stock and reroot and start over. Flashing stock will not lock it again it will remain unlocked. But should get you back up and fresh. Just be aware it will erase all your data and all of the internal SD card.
Sent from my SGH-M919 using Tapatalk
dokgu said:
Hello everyone,
I really need your help with my wife's Metro PCS Samsung GS4 M919N.
The thing is, we are now living outside the US so I had to unlock her phone. After ordering the unlock codes, I decided to root the phone and use a custom ROM while waiting for the codes.
That is why I found this guide here: androidforums.com/metropcs-galaxy-s4-all-things-root/790899-metropcs-galaxy-s4-all-things-root-guide.html
So while reading the guide, I aimed to have the following accomplished at the end:
Recovery: TWRP
Custom ROM: CyanogenMod 10.2.1
I then started doing the guide for the TWRP recovery by using Odin. I got the message saying that the flashing passed and went ahead to restart to recovery to install CM 10.2.1 as a custom ROM. The thing is that I keep on restarting to the stock recovery not TWRP. So I went to YouTube and found a video showing how to flash TWRP using GooManager. After following that guide, I went to restart to recovery and I successfully got into TWRP.
Now, to achieve my goal, all that's left to do is to flash CyanogenMod 10.2.1 (jfltetmo).
Before doing that, I decided to make a backup. After using TWRP to do a backup, I proceeded to installing the custom ROM + gapps (wiped with the default settings). Everything was working I think (I handed the phone to my wife so she was he one testing it). After some time, she decided she wants the stock ROM instead so I decided to download the androidforums.com/metropcs-galaxy-s4-all-things-root/783769-rom-recovery-flash-able-stock-m919nuvuamf2-rooted-deodexed-rom.html ROM.
I flashed the newly downloaded ROM + gapps (same file). This time, I couldn't get the gapps to work probably because it was meant for another version. So I decided to just restore from the backup I created earlier.
So, the usual stuff. Wipe. Restore. Restart.
Seems to be going smoothly because my wife was happy to see the old ROM she was used to.
Until the phone started to restart on it's own. (It's pretty much downhill from here on out).
At first I thought it was just a random thing that probably would never happen again. I was wrong as it became more frequent as days went by.
Recently I can't just restart the phone, I would have to remove the battery and then restart it. Now, it's getting really hard to restart the phone. Please help me fix this. I prefer to leave the phone rooted, but if the fix unroots the phone then so be it, anyway my wife prefers the stock ROM so only the unlocking was necessary.
Metro PCS Samsung Galaxy S4 M919N
Recovery:
TWRP 2.6.3.1
ROMs:
Stock Metro PCS
CyanogenMod 10.2.1
Let me know if you need more information from me. Hopefully I can restart the phone so I can give you some version numbers.
Thanks everyone!
Click to expand...
Click to collapse
I agree with Elesbb. If the goal is jus tto get back to stock, just do an odin flash of the stock ROM. Be advised if you flash the latest Kit Kay update you will nto be able to go back to Jelly Bean. From your post it seems like you are partial to Jelly Bean. So if that's what you want, but sure you use the stock 4.3 ROM. You can find it around here on XDA somewhere with a quick search to make sure you have the right one.
As Elesbb said, you won't loose the 'sim unlock'. But you will lose root. However you can root the stock ROM just fine.
You might also consider one of the myriad of TouchWiz based custom ROMs. They are look just like TouchWiz that your wife wants, but have a lot of optimizations and options in them. Those should flash just like any ROM. If you still get the reboot issue then do the Odin back to stock, reroot, then flash the custom TW roms.
---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------
Thread cleaned.
Rather than bashing a ROM or user let's keep on topic and help the OP resolved the problems he's having. Arguing over the virtues of a ROM doesn't help anyone.
Thank you,
Rwilco12
Before posting this thread I sent the aforementioned guide's poster (arocker). He sent me a reply saying not to use gapps as the stock ROM for Metro PCS already comes with Google apps. I'll try his suggestion first and see if the phone still reboots a lot.
If the problem persists, I will try the solutions mentioned here. Thanks a lot!
elesbb said:
I didn't read everything but just wanted to say
VERY GOOD THREAD!
this is how threads should be done. Very descriptive, organized, told us everything you did and asked for help! Good job man! Only negative is it prolly should have gone in Q&A section but irregardless very good thread!
About your issue, I recommend flashing stock Odin tar file to everything back to stock and reroot and start over. Flashing stock will not lock it again it will remain unlocked. But should get you back up and fresh. Just be aware it will erase all your data and all of the internal SD card.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
After trying arocker's suggestion to not flash gapps, the phone still reboots. So now, I am going to try your solution guys.
But before I do, I want to make sure that I am on the correct paths/links.
Here's what I found for the following:
ODIN
forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539
I've had a couple of chances to use ODIN but only using specific functions like flashing a recovery file while the phone is in download mode. I don't however have any experience using ODIN to put the phone back to stock where the phone gets unrooted. Having the phone unrooted is fine by me as I only needed to have the phone unlocked.
Any step-by-step guides for using ODIN for this specific purpose guys? I don't want to mess this up again.
Thanks and sorry for the trouble.
dokgu said:
After trying arocker's suggestion to not flash gapps, the phone still reboots. So now, I am going to try your solution guys.
But before I do, I want to make sure that I am on the correct paths/links.
Here's what I found for the following:
ODIN
forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539
I've had a couple of chances to use ODIN but only using specific functions like flashing a recovery file while the phone is in download mode. I don't however have any experience using ODIN to put the phone back to stock where the phone gets unrooted. Having the phone unrooted is fine by me as I only needed to have the phone unlocked.
Any step-by-step guides for using ODIN for this specific purpose guys? I don't want to mess this up again.
Thanks and sorry for the trouble.
Click to expand...
Click to collapse
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
PanchoPlanet said:
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
Click to expand...
Click to collapse
Hello PanchoPlanet,
Thanks for the link. I went ahead and tried to unroot without Windows (Mobile Odin) as per the instructions on the link. I downloaded everything and went ahead to install the Mobile Odin APK. When I ran it to install the Flash Kernel, the app told me that the device is not supported.
To my understanding the guide is for M919 devices but should work for my wife's device as well (M919N - Metro PCS). I would like to try the guide for using Windows but I'm not really expecting for it to work or I might mess it up more. I'll try to search some more and provide the links where this forum will lead me to. But if you have any ideas, please let me know asap. Thanks!
PanchoPlanet said:
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
Click to expand...
Click to collapse
Ok, here's what I found:
forum.xda-developers.com/showthread.php?t=2446497
It seems like the perfect thread for what I am trying to achieve. Will let you guys know if it is successful. But it will have to wait for tomorrow. Gonna catch some sleep.
Okay, I'm running out of options. I was able to flash the stock ROM using Odin 3.07. The recovery looks like it came back to the stock recovery as I no longer have TWRP installed. When I install Root Checker, I see that I am no longer rooted. That's good.
But my original problem is still here. The phone reboots a lot. The phone is so unstable that it is barely usable.
I am now going to try one more thing.
I have a Galaxy S4 (I337M) from Rogers Canada (my wife has Metro PCS M919N). Mine got rooted and has CyanogenMod 10.2.1 as a custom ROM. My phone is working perfectly while hers reboots a lot. I was thinking it was because of a faulty battery. So I am doing an experiment by swapping the batteries. So far no reboots have occurred, but I will continue to monitor this.
Any ideas why the battery is kinda messed up?
This thread talks about battery stuff and reboots:
http://au.ibtimes.com/articles/530338/20131216/samsung-galaxy-s4-problems.htm
Batteries can go bad a lot of ways. Extreme temperature, factory defect, phone drops, moisture, etc.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
This thread talks about battery stuff and reboots:
http://au.ibtimes.com/articles/530338/20131216/samsung-galaxy-s4-problems.htm
Batteries can go bad a lot of ways. Extreme temperature, factory defect, phone drops, moisture, etc.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And 100% of the time, they eventually just get old.
dokgu said:
Okay, I'm running out of options. I was able to flash the stock ROM using Odin 3.07. The recovery looks like it came back to the stock recovery as I no longer have TWRP installed. When I install Root Checker, I see that I am no longer rooted. That's good.
But my original problem is still here. The phone reboots a lot. The phone is so unstable that it is barely usable.
I am now going to try one more thing.
I have a Galaxy S4 (I337M) from Rogers Canada (my wife has Metro PCS M919N). Mine got rooted and has CyanogenMod 10.2.1 as a custom ROM. My phone is working perfectly while hers reboots a lot. I was thinking it was because of a faulty battery. So I am doing an experiment by swapping the batteries. So far no reboots have occurred, but I will continue to monitor this.
Any ideas why the battery is kinda messed up?
Click to expand...
Click to collapse
That's a wierd situation, by swapping batteries you basically performed a battery pull, which acts as a reset, that in it self may have cleared your issue.
Now if battery is bad that could be an unusual problem. Maybe just replacing the battery will be the end of your mystery.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
The battery should be brand new as the phone was just recently purchased this April.
Anyways, so far no reboots have happened and any instability has not been shown at all. Everything looks ok, yet.
Anyone know if it is safe to swap batteries? Our phones have different S4 models. I'm not sure what the implications would be. Also what is this battery pull which acts as a reset? We've been pulling the battery a lot of times but the reboot still happens but not when we swapped batteries.
The batteries are all the same. Don't worry about that.
Even if its a new battery if could have just been bad. A manufacturing defect perhaps.
Sent from your phone. You should be more careful where you leave that thing.
dokgu said:
The battery should be brand new as the phone was just recently purchased this April.
Anyways, so far no reboots have happened and any instability has not been shown at all. Everything looks ok, yet.
Anyone know if it is safe to swap batteries? Our phones have different S4 models. I'm not sure what the implications would be. Also what is this battery pull which acts as a reset? We've been pulling the battery a lot of times but the reboot still happens but not when we swapped batteries.
Click to expand...
Click to collapse
This battery thing is wacky, anyway swapping batteries should not be a problem, it's just an energy storage container. Pulling the battery isn't like powering down the phone or resetting/rebooting ,sometimes devs request a battery pull to get the proper wipe effect that reboots can't provide.
You inadvertently solved your problem by accident. That's a good thing.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
PanchoPlanet said:
You inadvertently solved your problem by accident. That's a good thing.
Click to expand...
Click to collapse
I have quite literally solved the vast majority of my problems this way.
Its a preferred method.
Sent from your phone. You should be more careful where you leave that thing.
Sometimes it's that "total disconnect "of power that kind of gets all the ducks lined up in a row and everything flows in the dynaflow.
Good.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
its very important topics and it might seen for every galaxy s4 users.just wonderful topics.
This exact same thing happened on my mother's 6-month old S3. If you're still wondering, you could try putting the old battery and running a CPU stress test app. It should increase the current draw and trigger a shutdown.
EDIT: whoops, sorry to kind of zombie. Didn't check the date.
Sent from my Galaxy S4

Updating to Lollipop advice please

I am very new to this ( I have never done anything like this to my phone) i have just finally unlocked my phone so i can update to Lollipop. now i would like some advice please as i have no idea as to what i am looking at in the way of different versions which is the way to go please
1, some thing like the Resurrection Remix 5.3.3 SPECIAL EDiTiON.. unoficial
2. or [endeavoru] [5.0.2] [official] [CM12-based] **crDroid** OPfirebird11
as i have idea about the pro's and cons so any help would be appreciated..
Or even updating with a standard Lollipop rom if this is possible?
Thanks guy's
radicaldoc said:
I am very new to this ( I have never done anything like this to my phone) i have just finally unlocked my phone so i can update to Lollipop. now i would like some advice please as i have no idea as to what i am looking at in the way of different versions which is the way to go please
1, some thing like the Resurrection Remix 5.3.3 SPECIAL EDiTiON.. unoficial
2. or [endeavoru] [5.0.2] [official] [CM12-based] **crDroid** OPfirebird11
as i have idea about the pro's and cons so any help would be appreciated..
Or even updating with a standard Lollipop rom if this is possible?
Thanks guy's
Click to expand...
Click to collapse
I have upgraded to crDroid over a week ago, having a few issues - network gets lots upon turning mobile data on forcing me to reboot, ringtone doesn't change to any song on SD card, bluetooth A2DP keeps loosing audio ( no sound from time to time ). It is stable overall, but these few things really annoy me and now I'm going to try AICP - 8.0 - LP 5.0.2_r1 which is stable and apparently free of those errors. Other than that, just flash it normally. The overall experience is very good.
Ghostli said:
I have upgraded to crDroid over a week ago, having a few issues - network gets lots upon turning mobile data on forcing me to reboot, ringtone doesn't change to any song on SD card, bluetooth A2DP keeps loosing audio ( no sound from time to time ). It is stable overall, but these few things really annoy me and now I'm going to try AICP - 8.0 - LP 5.0.2_r1 which is stable and apparently free of those errors. Other than that, just flash it normally. The overall experience is very good.
Click to expand...
Click to collapse
it may be a good experience for you LOL for me it's a nightmare as i am worried about screwing my phone up.. when i unlocked my bootloader it wiped my phone and i didn't know it would as i hadn't read it all (my bad ) now it's messing and won't do a lot of stuff including re install stuff i had backed up so i am a little worried.. i have decided to try Resurrection Remix 5.3.3 SPECIAL EDiTiON i think....
radicaldoc said:
it may be a good experience for you LOL for me it's a nightmare as i am worried about screwing my phone up.. when i unlocked my bootloader it wiped my phone and i didn't know it would as i hadn't read it all (my bad ) now it's messing and won't do a lot of stuff including re install stuff i had backed up so i am a little worried.. i have decided to try Resurrection Remix 5.3.3 SPECIAL EDiTiON i think....
Click to expand...
Click to collapse
You didn't know it will wipe all your data? I assume this was your first custom ROM then. You really should start with reading some FAQ and general information on this site. However for future flashes, you can keep all of your settings and apps if you have an app like Titanium Backup. If you do everything as you're instructed in flashing tutorials, there is very small chance that you're going to brick your phone. Even thou I managed to mess my recovery up and brick it, local phone repair guy fixed it for me for less than 5$.
The ramblings of a retired moron............
Ghostli said:
You didn't know it will wipe all your data? I assume this was your first custom ROM then. You really should start with reading some FAQ and general information on this site. However for future flashes, you can keep all of your settings and apps if you have an app like Titanium Backup. If you do everything as you're instructed in flashing tutorials, there is very small chance that you're going to brick your phone. Even thou I managed to mess my recovery up and brick it, local phone repair guy fixed it for me for less than 5$.
Click to expand...
Click to collapse
Well after getting things slowly sorted i am trying to root my phone easy you would think but no even this appears to be difficult for me LOL.. After going through every thing the tut's say and downloading the all in one kit checking that the debugging is on and USB drivers are on etc. when i run Hassoons program and go to install either of the TWRP or Clockwork mod to root it all i get is the cmd screen and it does nothing just sit's there anyone have any ideas as i am out of them now......
Well sorted that now it appears it has to be in a folder called HTC on C: i didn't see any mention of that anywhere........ Oh one other thing anyone using the Hasoons program who want to install Clockwork mod you have to rename it in the recoveries folder to cwm.img or it won't load in the program as it is named incorrectly... so it can't find it..
Everything all good at the moment rooted and sorted CWM on and working now it's just having the cojones to try the new rom to take me to Lollipop.. This very scary for me as i don't have any money to buy another phone new or second hand money very tight.... I don't know if anyone has been reading my ramblings but if you have wish me luck i have done a back up in CWM and titanium so .....................................
well i found the cojones and it failed with an error in the Resurrection Remix 5.3.3 SPECIAL EDiTiON..... what a bummer.......
radicaldoc said:
Well after getting things slowly sorted i am trying to root my phone easy you would think but no even this appears to be difficult for me LOL.. After going through every thing the tut's say and downloading the all in one kit checking that the debugging is on and USB drivers are on etc. when i run Hassoons program and go to install either of the TWRP or Clockwork mod to root it all i get is the cmd screen and it does nothing just sit's there anyone have any ideas as i am out of them now......
Well sorted that now it appears it has to be in a folder called HTC on C: i didn't see any mention of that anywhere........ Oh one other thing anyone using the Hasoons program who want to install Clockwork mod you have to rename it in the recoveries folder to cwm.img or it won't load in the program as it is named incorrectly... so it can't find it..
Everything all good at the moment rooted and sorted CWM on and working now it's just having the cojones to try the new rom to take me to Lollipop.. This very scary for me as i don't have any money to buy another phone new or second hand money very tight.... I don't know if anyone has been reading my ramblings but if you have wish me luck i have done a back up in CWM and titanium so .....................................
well i found the cojones and it failed with an error in the Resurrection Remix 5.3.3 SPECIAL EDiTiON..... what a bummer.......
Click to expand...
Click to collapse
Try flashing the ROM manually (with no toolkit). Flash the zip from the recovery, but flash the boot.img manually.
You'll need the ADB bundle of course.
Avoid AICP when possible. While it's a great rom with lots of features, it's always extremely buggy/unreliable/currently overheats and reboots. I've been using AICP on a few devices since 4.3.1 - 5.0, while it's okay for some people on some devices.. there's a pretty consistent trend. If it's not good enough for my girlfriend, it's not good enough for a daily rom IMO.
Resurrection remix is a solid rom with many features and well laid out. While it tends to have less features and modifications than AICP, it is pretty solid and reliable while still being a major improvement over stock AOSP.
crDroid has never really hit the spot in performance or any other area which hasn't already been surpassed by other roms.
But please know nothing has higher battery life or produces less heat than HTC based roms & kernels. As this device can have poor battery life and runs quite hot. Another thing is the better control of the GPU with the HTC based kernels.

Categories

Resources