Related
Hello,
I've installed Hensemod a few times now, without any problems the first time I boot the phone.
Only after that, when restarting or turning the phone on again, it takes very long to start, like it's installing again and then the internal memory is suddenly full, even though I had about 100mb when turning the phone off. Also, all apps I installed are gone. In the applications list (in settings) they seem to still be there, but they're all 0kb and there's no shortcuts to them in the programs overview... Like I said, I've installed the Hensemod a few times now, and every time this happens.
Anyone knows how to solve this? I really like this rom, I can finally install and update all apps I want without the phone becoming unusable because of full internal memory! Thanks!
Carolien
I used HenseModv3 is a nice ROM, u must have to wipe all the data, cache and dalvick cache in the CWM recovery section, then install the HenseMod ROM.
If any other problem, plz share.
I followed all the steps stated in the development forum post, it works fine, just cant restart the phone because it will stop working...
My phone just continuesly restart...
Plug off ur battery, then go to CWM recovery, try to intall any other/different ROM.
I install each ROM by above method,i didn't use fastboot uncheck option.
Never mind I was just being stupid... I wiped the cache partition and not the dalvik cache. Sorry about that! Let's see if it will work now. Installing rom at the moment.
And again... first boot worked fine, after that I'm stuck in a bootloop now... Just like couldzxz. Too bad! I'll have to try yet another mod. Hope the next update of hensemod will solve this!
yes, u can try different custom ROM if any problems with a particular ROM
wait for next updates from Henry_01
I got stuck in bootloop too. I reqlly like the rom but well.. :/
Sent from my HTC Wildfire S A510e using xda premium
Okay, i've seen your problems.
I've tested latest build, but didnt rebooted it.
I suggest you all use a previous version (3).
Problem can be also kernel related.
I don't have time now (exams), I will make a proper working build after some weeks.
Don't hesitate to post here further, I want to know if it is ROM or phone related.
BIG EDIT: i will include link for version 3.
Thanks to djpc for a new hack which will solve reboot/kernel/overclock problems.
Expect a build and a proper test on friday or saterday.
I will change links now so that you will get a good version lol.
Somehow, the fifth time in installed the latest Hensemod rom, it worked like a charm. I can reboot, have installed and updated all apps I wanted and still got like 90mb remaining. Fantastic! Finally after 6 months I have the phone I wanted.
First and second install I couldn't reboot
Third install I got stuck in a bootloop
Fourth install gapps crashed every 2 seconds (due to calendar and contacts synchronization)
Fifth install = perfect!
I don't know how it happened, I just kept on installing this one so I could copy another rom on the sd card since I don't have an adapter or card reader for it.
Thanks!
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Did you do a full wipe ???
ryansinibaldi said:
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Click to expand...
Click to collapse
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
donhashem.dh said:
Did you do a full wipe ???
Click to expand...
Click to collapse
Full wipe as in? (sorry, still a bit new). I did do a factory reset in CWM before installing whichever ROM I was trying at the time. I wiped all caches too.
slack04 said:
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
Click to expand...
Click to collapse
I used the HTC One V AIO Toolkit to unlock the bootloader, get root, install CWM 6.0, create a backup and then install a kernel (I used the Super Sick JB one). From there I used CWM to gain access to my SD card and transferred over the CDMA Pacman ROM (after wiping everything clean) and then installed the ROM. It booted up successfully however as stated in a minute or so it would freeze up and restart itself. Even if I don't do anything after a reboot it'll still reboot itself anyways.
I did a bit of research and I'm thinking it could be due to the OTA Radio update from 2-3 weeks ago? I'm at my bootloader now and it says I have radio version 1.00.00.0928.
Any further help to resolve this issue would be greatly appreciated. It's worth noting that I've tried many different Kernels (repeating all the steps above with full wipes every time) and different ROMs that were supported by the kernels. I've even tried to restore my phone back to stock and it just starts skipping at the VM Boot screen.
Oh, and I'm running Windows 7.
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
donhashem.dh said:
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
Click to expand...
Click to collapse
Pardon my ignorance but that just doesn't make sense. I've tried several different ROMs with the correct kernel's (Pacman, CM9/10, AOKP JB) and it's all the same scenario. They all boot (or occasionally don't boot and restart themselves at the boot animation) and then reboot themselves once they're pass the lock screen.
Like I said even currently if I restore my stock rom file it just loops at the VM Boot animation (which doesn't play fluidly).
Figured out the issue . It was radio version 1.00.00.0928 messing up my kernel.
HI, I am a complete stranger to rooting but I wanted to improve my phone without buying a new phone.
I have read the "effen manual" and downgraded the ROM.
I then installed 'cfx_ace-4.2-SR5.zip' and after a long time and a couple of forced reboots the phone came to life. I then had no access to download apps (the gapps zip was not included or mentioned on the site, I think).
I wiped the phone clean and then installed 'cm-JellyTime_42_R2.zip' and still had the same issue. Basically, after the initial HTC screen nothing happens after the ROM has been installed and I have rebooted the phone. It takes a lot of re-installing, removing battery, re-installing before I finally get the phone to work. Finally everything works, I also install 'gapps-jb-20121212-signed.zip' to get access to Google playstore but a new problem arises. I am not able to access the internet.
I am in Australia and use Lycamobile (I have added the APN settings ‘manually' but still no luck, I have rebooted my machine many times, spoken with the customer support but still no luck. Strangely enough the same sim card works fine in an unrooted phone.
I have now wiped the phone clean again and am in the process of installing 'ViperSaga_OTA_1.1.0.zip' but am stuck on a blank screen for the past half hour in desperation. (http://forum.xda-developers.com/showthread.php?t=1983604).
The instructions say
1. Download the ROM – Done (but does not say which one so I have downloaded the Ota one)
2. Flash the ROM (AROMA Installer will pop up) – It did and once it was done, it said reboot
3. Choose Fullwipe (important)- from where??
4. Choose the mods you want – from where??
5. Reboot
6. The Rosie (HTC Sense launcher) needs about 5-10 minutes to get the best speed, so it needs some time of playing until you have the best speed
7. Battery life is the best after 3 charginig cycles so give the ROM a chance
My question(s) for which I am seeking your advice is
a) What am I doing wrong in installing the ROM's why does my phone take so long to come to life?
b) What do I need to do to fix my internet issue (Wifi works fine). My radio version is 26.10.04.03_M
Many thanks and apologies for the long post and showing my ignorance…
How long a time approximately? All ROMs take a bit of time on first boot. This is when they're populating the dalvik-cache with optimized data for each app on the phone. So it's normal to see a black screen or continuous bootanimation for some time on first boot. So once you flash a ROM, just let your phone be idle till it turns on fully. Don't pull battery or do anything in between. The next time you reboot your phone, you'll see that it boots much faster because the dalvik-cache is already built.
Coming to the topic of the ROM you're trying to flash, ViperSaga is a ROM for the HTC Desire S, not the Desire HD. You shouldn't be flashing it. Even if it was a ROM for the DHD, you need to flash the ROM zip first and *then* flash the OTA. OTA = Over The Air. OTA zip files are meant for small updates to an already existing ROM. They are not the full ROM, so you need to flash the full ROM first and then flash the OTA package to update it. These OTAs can also be downloaded in Settings->About->System software updates.
In the 4th post in the ViperSaga thread, a list of ROM downloads is provided. The actual ROM file is ViperSAGA v1.0.0 (dev-host) which is 427.47 MB. That is the one that should be flashed first. The OTA file is meant to bump the ROM from v1.0.0 to v.1.1.0, not to be flashed by itself. That's why it's of such a small size of 28.47 MB. ROMs are never that small a size.
Now, DON'T flash that ROM. It's not meant for this phone! If you want a similar ROM, there's ViperDHD by the same developer. And don't flash gapps for a ROM unless it's explicitly mentioned in the first post of the ROM thread. If you look throught the cfX and JellyTime threads, you'll see that it is. You will find the latest gapps (Android version-specific) at http://goo.im/gapps and you can read about gapps at http://wiki.rootzwiki.com/Google_Apps.
The reason you weren't able to see the options for full wipe and the modifications is because, apart from flashing a wrong device ROM firstly, you didn't flash the right ROM file, so the AROMA installer didn't show up. AROMA is an interactive installer that allows you to choose stuff rather than just directly flashing a ROM file. Try the same procedure with ViperDHD, following the instructions and downloading the right files, and you'll see everything properly. ViperDHD has an AROMA installer that provides options to wipe your phone automatically rather than doing it yourself, thus making it easier to flash the ROM. ROMs don't usually have this. Before flashing a new ROM (not an update to an already flashed ROM, but an entirely new one), you should ALWAYS wipe your phone fully. This can be done in recovery by going to 'wipe & format' and choosing 'wipe boot', 'wipe system', 'wipe data/factory reset' and 'wipe cache'. For example, if you want to switch from ViperDHD to cfX, then you need to full wipe. If you just want to flash an updated version of ViperDHD or cfX, then you don't need to unless you're testing for bugs to report to the developer.
Here are some guides to booting into recovery and the correct flashing procedure of a ROM -
http://forum.xda-developers.com/showthread.php?p=35937493
http://forum.xda-developers.com/showpost.php?p=30530565&postcount=179
I'm not sure about your internet issue, but first flash that ROM and try if it works.
Sent from my Desire HD using xda premium
sashank said:
I'm not sure about your other problems, but ViperSaga is a ROM for the HTC Desire S, not the Desire HD.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Thanks Sashank,
downloading ViperDHD_v1.2.3.zip as I write, hopefully, hopefully that will fix my issue....
Thanks once again.
I just updated my post with a lot more info after you replied. I was in a bit of a hurry and I didn't read your post fully at first. Once I did I knew what you were doing wrong. So refresh your page and read it fully again. Good luck.
sashank said:
I just updated my post with a lot more info after you replied. I was in a bit of a hurry and I didn't read your post fully at first. Once I did I knew what you were doing wrong. So refresh your page and read it fully again. Good luck.
Click to expand...
Click to collapse
Hi Sashank,
Apologies for the delayed reply, I have just loaded the new ROM and it works.. it works!!!!!!!!
Thanks heaps for hitting the nail on the head and the very detailed email explaining what I was doing wrong.
Just one more question.. do i need to upgrade my radio??
Kind Regards,
Not necessarily. You only need to flash a different radio version if you are having low signal issues, dropped calls, high standby battery usage, and overall bad connectivity with your current radio version. If you feel calls sound good, and you're getting a good signal, then you don't need to. Radios are region specific, so newer is not always better. You just need to find one which works well for your region and stick with it. If your current one does, then leave it like that.
You don't flash radios in recovery the same way as a ROM. They are flashed in different ways. Here's a guide to flashing radios the easy way - http://forum.xda-developers.com/showthread.php?p=30552152
Also, point to keep in mind, when you see anything about flashing RIL after flashing radio - Corresponding RIL for a radio version should only be flashed on HTC Sense Gingerbread ROMs. Not on HTC Sense ICS ROMs and AOSP ROMs like cfX, Jelly Time, CyanogenMod etc.
Sent from my Desire HD using xda premium
Hi
Guys i need your help. Pleas can someone tell me for now what mods is much better for I927R (Also withe very stability and with much less bugs) ?!
I found Liquid Smooth but it have some problem so i need your guide about other mods.
Thank you
ICS Roms are the best and most stable... Stock ICS from AT&T UCLJ3 or any roms based off of it ... Dman's daily driver, Ice Pop Rom by RawRaw, LiteRom by TheGreaterGood...
Unfortunately none of those are being maintained but I had been running Dman's for the last couple months, great battery life when paired w/ JuiceDefender (20+hours of heavy use when I'm not sleeping).
Now the newest CM10.1 by Spyke seems pretty solid ... Just a couple of issues.
ICS is the only one you'll get bug free, though. Stock is hard to compete with when we're pairing up roms without a true Devdeloper.
On this subject, I've just reverted back to using IcePop ROM after (unhappily) downgrading from Spyke's latest 10.1 ROM - just mainly because of the Bluetooth headset issue, which I really need working for work purposes.
I'm just wondering if there are any ICS builds that have GPS working correctly? I tried flashing the Rogers modem (since my phone was originally a Rogers import, flashed to AT&T ICS, then played with ICS from there) and first time I ran GPS status it took 771 seconds... I'm going to keep trying just in case that was the first time only, but 12 minutes is still a very long time for an initial fix .
Also - I've found that I'm getting more and more bootloop problems even with clean installs - so wiping cache, data, dalvic, etc. Is there some way to do a *thorough* wipe without bricking the phone? I can back all my data up no worries, but next time I move to JB (in the optimism that the BT issues will be fixed soon, judging by the positive progress being made by Spyke ) I would like to do a clean build from scratch and not have to gamble being able to start the phone up again
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
I, also, had reverted to using JB Because GPS wouldn't work ... There's a thread in here (search for it) that shows the solution to the GPS fix, its editing sirgps.conf and gps.conf ... I was getting a fix on GPS in under 30 seconds.... GPS was a huge let down in the stock ICS rom, Even when using TheGreaterGoods LiteRom w/ GPS fix I found after a couple of days my gps didn't hold....
Thanks for the reply.
I was considering formatting /system this morning when I was getting stuck in a boot loop from trying to get M3 running, but decided it was a risk I'd have to check up on first . Next time I do a build from scratch (I'm going to resist until the BT stuff is working - fingers crossed!) I'll do that.
I remember having a look at the gps.conf fix but don't recall anything about sirgps.conf - so I will look it up, thanks!
As an aside, I've been checking the GPS fix a couple of times since my last post and it is coming up in under 30 seconds each time... I'm wondering if my attempt to flash the Rogers modem did in fact fix the issue... I'd do a reboot but I'm too scared I won't get the phone up again XD
EDIT:
Found the fix, I did a few of the changes (rather than all of them), and it's now picking up 8 satellites instead of 3-5, and getting a stronger signal from each... and all I did was point it to the AU ntp server, and tell it I'm not on the ATT network . I'll save the suggested settings to a text file on my SD card so next time I'm out and about and if it plays up I'll have access to the details.
yohan4ws said:
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
Click to expand...
Click to collapse
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
davidpartay said:
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
That has to be very concerning to you, I've never had an issue booting any ROM. And very strange flashing the Kernel separately would resolve your booting issues...
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
If I were in your position I would try and do a full revert back to the earliest version of gingerbread I could find on samfirmware and then use Kies to udpate - THEN I would retry flashing to a newer JB or ICS Rom.
Pretty time consuming but that is the price we pay to mod
davidpartay said:
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
yohan4ws said:
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
Click to expand...
Click to collapse
Not yet. I'll have to check which ones I have - I'm certain I have the AT&T ICS rom from November but then I'd have to go digging through my email for the unlock code again, so I'm trying to avoid doing that at this point . If i can find the stock GB Rogers rom at some point I might flash that one back on before I do any more upgrades. The phone is up and running at this point though, so I'm not too fussed. I've also noticed that it's a little quicker than before so I think the version of LiteKernel I installed was a good idea anyway.
bubor said:
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
Click to expand...
Click to collapse
I've tried pulling the battery a few times, but probably no longer than 30 seconds. Next time I'll give it a couple of minutes. I tend to do this late at night when I'm not expecting any calls (except fire brigade but I have a pager for that too) so time without a phone is no issue to me
Yesssss
After much irritation at continually getting stuck in boot loops again, I've 'Oneclicked' the phone twice, got fed up with the AT&T ICS ROM within about 5 minutes, gave up on IcePop because of buggy GAPPS...
And thought, bugger it. Format /system. Factory reset. Clear cache + Dalvik. Installed in this order:
Jellybean 4.2 ROM from 0217
Spyke's M3 update
PAC rom
GAPPS dated 0427
"Kick-ass Kernel"
and it BOOTED FIRST GO
I am pleased
Does JB need already to be installed before putting the M3 revisions on? Maybe that's where I've been going wrong all along, because my attempts at running both the standard M3 and PAC ROM (even immediately after OneClicking) resulted in boot loops or eternal boot loading.
Uhh... what do you mean by "One Clicking" ??
I know there's a "superoneclick" that will flash and root the rom all at once, but I never personally found it to work for our glides.
Using CWM and installing the ROM through the CWM boot menu is severaly key presses so ... not too sure what you're referring to.
Also, I've always downloaded to a hardwired computer then copied over USB to my phone and flashed ... sometimes the download will have errors if I grab it from my phone.
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
davidpartay said:
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
Click to expand...
Click to collapse
Interesting... for future reference, www.samfirmware.com has the stock firmwares, then there's the superUser file floating around the forums that allows you to root by flashing it. Passed that, remove bloat.
Glad you got it working! Welcome to JB
[Q&A] [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Q&A for [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
kbfirebreather said:
Anyone having problems with torch on the beta build? Not turning on LED for me, and keeps force closing.
Click to expand...
Click to collapse
I'm having issues with it as well. Sometimes it sits there thinking it works, other times it waits a few seconds and then crashes. It worked for a day...not sure what I did past that to break it.
Is there anyway to overclock the latest update? I know I can't install a new kernel with this ROM.
Also, any option for Volume Rocker unlock? I'm new to this ROM, coming from CM. I kinda rely on that option, since my power button is kinda on the fritz.
Fml 4.4.4 beta
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?
vicious01 said:
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?
Click to expand...
Click to collapse
Which gapps package are you using? I'm using the modular mini. Try another clean flash (sorry) and use a different package than you are now.
aaa
nothing
I've tried a lot of KitKat ROMs, but each one with a lot of issues. So I came back to the 4.3, it surprised me for his stability (1 year with bugged ROM make you feel that your phone sucks more than it actually does [no, it doesn't, I love it!]) and I decided to don't try your FML. Now I can't wait for Lollipop, and even if I haven't tried your ROM, I trust in it and I think it will be the best choice. Good work and thanks!
Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!
Samsung Galaxy Nexus FML Lollipop
Hello. I hope this is the right place to post this. I have less than 10 posts so I have to post here...
I've tried to install your FML rom (the lollipop beta) on my Samsung Galaxy Nexus, but I seem to be having the same issue that coleburns is having. Namely, I flashed the rom from recovery, but when I reboot the phone, it shows the Google splash screen and then keep rebooting over and over again.
I understand that the first boot is supposed to take some time, but I've left it for over an hour and it still won't boot into the OS. Is there a step I'm missing?
I'm using the custom version of TWRP that you linked to in the first post. I also formatted all the partitions to ext4. Before flashing the rom, I performed the factory reset from recovery and also cleared the /system folder.
I've managed to load on the KitKat version of your ROM just fine...I can't work out what I'm doing wrong!
Anyway, if you need some logs or something to help debug the issue, let me know. Or, if I'm doing something wrong, could you please let me know? I'm very keen to try Lollipop!
Thanks.
Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!
lollipop build 2
Haven't seen anybody ask... In your changelog for lollipop you said the rom takes a VERY LENGTHY FLASH TIME. Are we looking at 5 minutes or more?
edit: VERY LONG... over 5 minutes for me
This is the best rom ever!
When you said, "These builds are very early! They aren't daily-driver-stable, but they are progressing extremely fast." I was expecting junk, then I tried it. I was a big fan of your kit kat rom as well but once I tried this android l rom I fell in love. I have used this all day and it is extremly stable. The only bug I have to report that isnt even a need is the app drawer is the app drawer animation is very laggy. I tried enableing 2d gpu acceleration just in case that had something to do with it but it still didnt help. Any suggestions would be great. Oh and yes I have tried closing other apps, multitasking is no issue with this rom, the memory management is great. I thank you so much for such a great rom, keep up the amazing work.
Installing TWRP Problem
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!
Mondos said:
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!
Click to expand...
Click to collapse
Download the file in the OP for FML (twrp 2.7.1). Flash with Flashify. Reboot to recovery.
Don't worry too much about it not working. It's fully working for me but it's pretty slow when you actually need to use it. If you get it going it will pick up the pace, but it's far from usable, being in an app for longer than a minute and touching the home screen button will freeze it up for 10 seconds before it takes you to an empty screen that takes another few seconds to load all the apps and widgets back in. I'd wait for a newer release.
Feedback
Hello i have tried the older version and it was great but i really need my camera so i went back to 4.4 but i appreciate you so much thanks !
Please fix the camera asap and i will definitely install this rom ! and i tried to install the new version but it said Error Binary something in TWRP recovery what can i do thanks!
Q
Is the camera fixed yet?
Notification Light
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.
TheIbanez97 said:
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.
Click to expand...
Click to collapse
I don't think so.
I found that the miscellaneous section of the battery stats was taking up most of the battery usage. I don't have any apps installed other than the stock standard.