Related
Rom Manager doesn't seem to know that I've got CWM installed. When I rooted and installed CWM I didn't do it through Rom Manager originally. Now CWM won't let me use it to manage my backups and keeps asking me if I want to install CWM? I've got Google Wallet installed so I'm a little nervous flashing things needlessly.
Any suggestions?
Thanks
edit: CWM v5.5.0.4
do you try "wipe cache" and "advanced->wipe dalvik cache?"
Thanks, I just tried, it took quite a while to clear the cache. When I booted up it went through a whole Optimizing Apps process, I'm not sure if that was due to wiping the dalvik cache? But it still didn't fix the Rom Manager issue.
Its probably not yet compatible if you have the touch version of cwm installed, so it wants to flash the standard one. Or you could always just let rom manager just reflash cwm overtop and then you may be good to go.
EvanVanVan said:
Rom Manager doesn't seem to know that I've got CWM installed. When I rooted and installed CWM I didn't do it through Rom Manager originally. Now CWM won't let me use it to manage my backups and keeps asking me if I want to install CWM? I've got Google Wallet installed so I'm a little nervous flashing things needlessly.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Maybe it can't detect it? I know we had to set which CWM version we had installed on the SGS.
Maybe try to run the install?
Sent from my Galaxy Nexus using Tapatalk
I don't have the touch version installed (doesn't seem to be the touch version anyway). I should have said this in the first post but it CWM v5.5.0.4.
Herman76 said:
Maybe it can't detect it? I know we had to set which CWM version we had installed on the SGS.
Maybe try to run the install?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Flashing CWM over CWM shouldn't wipe my phone right? It's only the stock bootloader that requires a full wipe?
I installed ROM manager and then CWM via ROM manager last night and its CWM v5.5.0.2 which ROM manager thinks is the latest: perhaps it can't deal with 5.5.0.4 yet...
Clancy_s said:
I installed ROM manager and then CWM via ROM manager last night and its CWM v5.5.0.2 which ROM manager thinks is the latest: perhaps it can't deal with 5.5.0.4 yet...
Click to expand...
Click to collapse
ah, that would probably do it...guess i'll just wait it out a little longer, thanks
I have the exact same issue as this Rom Manager refuses to see I have CWM installed so just keeps telling me I need to install it it also can't download and flash its own version and just freezes after download
So any updates on this or more users experiencing it ?
I think I've found the solution. In ROM Manager tap the menu button at the top and then tap Manual Flash Override. Next it'll ask you if you've flashed CWM manually so tap OK because that's what we've done. Next pick which GN you have and then choose CWM 3.x+. There you have it, it should work now.
Don't use ROM Manager - problem solved!!
Seriously, though, it's a TERRIBLE piece of software
I'm fairly new to using it but it seems decent, why is it so terrible? I had an eris before this and did everything manually through recovery, this seems like it's a lot better than that.
It's just more trouble than it's worth. Why not just manually flash CWM using fastboot and get your head around that as opposed to an app which can - frankly - break things?
Flashing it via fastboot is what causes the above issue. Since you flash it manually rom manager can't see it, that's why I posted the above steps to kind of "force" rom manager to see the manually installed version.
But if you're not using ROM Manager then what's the issue? Copy ROM to SD card, reboot to recovery, flash ROM...where is ROM Manager needed in that equation?
If you're not using it then there is no issue, but this thread isn't about using it or not, it's about getting it to work with the galaxy nexus when you manually flash CWM.
I like it for the backup and restore feature and being able to change the names used to backup
Okay, I'm new to Android and I heard this is the go-to spot for help. Anyway, this is what happened to my Wind SGH-T999V. Mind you i'm VERY new to this rooting thing
I rooted my S3 by using TWRP 2.6.3.0 and i used odin3 v1.85 and it worked. I downloaded a root checker and it said i'm rooted. Then i put CM 10.1.2 on my sd card and wanted to install it via TWRP recovery but it gave me an error that said "No MD5 filed found" or something along those line.
I then tried to use different versions of twrp ( twrp 2.6.1.0) and a different CM (10.1.1) but i still got the same "no Md5 found" error. So, a friend then told me to ditch twrp all-together and download CWM instead. So, I download recovery clockwork touch 6.0.3.7 and put it on my phone.
THEN, i tried to go back to the recovery boot place, but after that small blue font saying "recovery boot", my phone goes black. I dont see the old twrp recovery or the clockwork one.
I just really want to have Cyanogenmod on my phone, i've been having a hard time. Help please?
Just disable the md5 check, most or the ROM files are not going to include a hash file, but will flash fine. TWRP or CWM will error out if the flash fails.
Also, it sounds like your recovery install failed, just reinstall using ODIN and a file from @DocHoliday77 (I recommend TWRP over CWM, but it is just preference)
It's already unchecked.
Install TWRP and try again, should work without issue. Also, redownload the ROM file, preferably the latest version, 10.1.3RC2 (I think)
Sent from my T-Mobile T999L using TapaTalk 4 and delivered by Planet Express.
Can you link me the most STABLE CM that works with my Wind SGh-T999V?
qasde455 said:
Can you link me the most STABLE CM that works with my Wind SGh-T999V?
Click to expand...
Click to collapse
Don't use RC2. If you want stable, use 10.1.2. get.cm, filter it for your device. I think Doc also has them in his signature.
http://get.cm/?device=d2tmo&type=stable
"Stable" is relative, the RCs are just as good.
Aerowinder said:
Don't use RC2. If you want stable, use 10.1.2. get.cm, filter it for your device. I think Doc also has them in his signature.
Click to expand...
Click to collapse
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
qasde455 said:
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
Click to expand...
Click to collapse
You need to edit the install script because your device isn't supported. Or you can download Doc's version.
Actually I'm pretty sure cm includes the T999V, but I'm betting the firmware needs to be updated.
Look in Aerowinders Sig for the links to the firmware. In that OP you should find a link to the thread with the T999V firmware.
Or, you can go to my T999L thread and get the Rom there. But w/o updated firmware it may be buggy.
Sent from my SCH-I535 using Tapatalk 4
It's already unchecked.
qasde455 said:
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
Click to expand...
Click to collapse
CM10.1.3 is now Stable and will be the last 4.2.2 build. It should has the all of the Asserts, including the MB7 one. Also, update your TWRP, the current is 2.6.3.0.
I want to install CM so bad but after reading lot of threads n comments, I am scared. there are many terms used, i even dont know like flash kernel, OTI, radio etc... i just know about rooting, recovery and ROM... so i have decided to install PAC man instaed its a combination of couple roms and is most successful and stable..
malibu.barbie said:
I want to install CM so bad but after reading lot of threads n comments, I am scared. there are many terms used, i even dont know like flash kernel, OTI, radio etc... i just know about rooting, recovery and ROM... so i have decided to install PAC man instaed its a combination of couple roms and is most successful and stable..
Click to expand...
Click to collapse
You should read the sticky threads, and use xdas search for terms or definitions anytime you run into stuff you aren't familiar with.
Sent from my SGH-T999V using Tapatalk 4
hello
I am courious
how many of us are rooted already ?
what method did you use to root your phone ?
nowy57 said:
hello
I am courious
how many of us are rooted already ?
what method did you use to root your phone ?
Click to expand...
Click to collapse
Rooted since long ago... On every build... All the time. :good:
If you're still having trouble with rooting CM or Omni, try the following.
You should be able to flash the SuperSU zip in TWRP after clearing Dalvik and Cache. If that fails, try below.
If you have SuperSU installed already and are failing to get root, you may have to remove your current SuperSU version. Don't just uninstall SuperSU! Go into SuperSU and go to "Settings". Scroll way down to "Full Unroot". Let that run as it needs to, then reboot into TWRP and wipe Cache and Dalvik. Then flash the SuperSU zip. Reboot to system. Test root.
sorry mate
it doesnt work to me
I have tried two times
as you wrote
Harfainx said:
Rooted since long ago... On every build... All the time. :good:
If you're still having trouble with rooting CM or Omni, try the following.
You should be able to flash the SuperSU zip in TWRP after clearing Dalvik and Cache. If that fails, try below.
If you have SuperSU installed already and are failing to get root, you may have to remove your current SuperSU version. Don't just uninstall SuperSU! Go into SuperSU and go to "Settings". Scroll way down to "Full Unroot". Let that run as it needs to, then reboot into TWRP and wipe Cache and Dalvik. Then flash the SuperSU zip. Reboot to system. Test root.
Click to expand...
Click to collapse
I have the same issue too. SuperSU installed 3 times. Did the full unroot like you said and reran the install after wiping both the cache. Still no root access.
I think that magic which found us oppo+CM team is missunderstand couse when I first time heard about cooperation this two companies I was so much happy .
by now when I have it I know that maybe couple of hundred is sold this phones and nobody cares about support it .
1.ROM straight from CM/OPPO site doesnt install propely via TWRP( without ingeration for user-script)
2.no root acces yet
this is sad true .
I v got note3 and I see more future with this phone
AOSP/CM is on a way - a lot of android entusiasts is working for free of charge about better and better ROMs
I am dissapointed - no offens to anybody
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
ChodTheWacko said:
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
Click to expand...
Click to collapse
it is not installed under CM ROM
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
ChodTheWacko said:
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
Click to expand...
Click to collapse
The exploit method was apparently patched in the official CM release. That exploit doesn't work.
Harfainx said:
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
i am really confused couse I am pretty sure I am doing good as you said but no succes .
Harfainx said:
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
If TWRP doesn't work properly how did you root? With the stock recovery?
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
nowy57 said:
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
Click to expand...
Click to collapse
You can indeed install straight from stock recovery. I did it last night. You have to use the official rom for the n1. Works nicely. I also had root working on cm. I flashed cm from stock recovery then used fastboot to install twrp. After twrp i flashed supersu zip. After i did the fix root or remove or whatever it is in the ap, reinstalled and tested it in titanium. Said i did have access but then went back to coloros to try and fix my mediascanner issue.
Sent from my N1 using XDA Premium 4 mobile app
nowy57 said:
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
Click to expand...
Click to collapse
I mean straight flash CM on the stock recovery, not on TWRP. You would have to be on the stock recovery for it to work straight from the CM download. On the stock recovery though, you will not be able to flash SuperSU on it. I do not believe that Omni can be flashed from there either, but I could be wrong (I haven't tried it).
There's a thread in the dev section that has the stock recovery hosted there. You can always fastboot flash back to that at any time.
Okay, I decided to install Cyanogenmod for the heck of it.
I already had TWRP 2.6.3.1 installed,
I downloaded and modified cm-10.2-WPPH50O-n1-signed.zip as per this page's instructions:
http://forum.xda-developers.com/showthread.php?t=2553165
I also downloaded supersu (current version is 1.86).
I entered TWRP and installed it, following that page's instructions.
After the install, I selected 'reboot'.
When I selected 'reboot', It prompted me with:
install superSU now? this will root your device.
I said no, and then rebooted back into TWRP.
Now back in TWRP, I install SUPERSU.
Now reboot again.
Now in CM.
Now run SuperSU, select 'settings', and unclick 'Respect CM root settings".
Now root works for me.
Two notes:
1) Respect CM root settings implies that in 'developer settings', there is some sort of "allow root" checkbox. I can't find it.
2) If, after the CM install, you answer 'install SuperSU' with YES", then it installs SuperSU, and reboots.
When you go back in, and run SuperSU, it says "gee, you aren't rooted, install SuperSU?"
If you answer THAT with yes, then it downloads some version of SuperSU, reboots into twrp, and installs it.
So it's kinda pointless answering YES in the first place, imho.
Are you serious right now?! I was worried unchecking Respect CM root setting would mess things up. But now I have root access. OMG... I unchecked it and it works! ^_^
57 43235953
ChodTheWacko said:
...
Two notes:
1) Respect CM root settings implies that in 'developer settings', there is some sort of "allow root" checkbox. I can't find it.
...
Click to expand...
Click to collapse
There is actually a #Superuser control panel just below "{} Developer option" that has lots of useful settings for root user control.
I haven't rooted yet but it seems like handy stuff for supersu to respect? Once you go into #Superuser use the menu button and you can add a profile etc it seems.
It's all kind of oddly done since adding that control panel after activating developer mode doesn't actually add an "su" binary.
hammerandtongs said:
There is actually a #Superuser control panel just below "{} Developer option" that has lots of useful settings for root user control.
I haven't rooted yet but it seems like handy stuff for supersu to respect? Once you go into #Superuser use the menu button and you can add a profile etc it seems.
It's all kind of oddly done since adding that control panel after activating developer mode doesn't actually add an "su" binary.
Click to expand...
Click to collapse
On what version of CM? or did you mean OMNI?
Under 'System' I only have:
Date & time
Accessibility
Developer options
Performance
About phone
Unless you meant 'in {} Developer' but I don't see anything in there either.
- Frank
ChodTheWacko said:
On what version of CM? or did you mean OMNI?
Under 'System' I only have:
Date & time
Accessibility
Developer options
Performance
About phone
Unless you meant 'in {} Developer' but I don't see anything in there either.
- Frank
Click to expand...
Click to collapse
WOW...so it literally disappeared as I was composing this message.
Cyanogenmod "signed" installed with the oppo bootloader (not rooted as supersu doesn't install successfully through bootloader etc).
Some kind of UI refresh after I changed some home screen settings?
It was persistent through 5-10x reboots and now is gone.
Obviously a glitch since I don't have su and I'm not truly rooted but it WAS there :\
I'd say its a bug to be filed if you are rooted and it's not available.
Hello there,
I'm new to Android (got me note 2 three days ago) and I rooted the phone yesterday, I flashed cm ROM into the note, because It was as simple as an iPhone, and it was fast, but I lost some of the greatest features that note 2, offers which are the multiscreen and the S-Pen features, I have posted a help thread about that and they replied that I need a Touchwiz ROM, I went to my close friend Google and searched for Touchwiz rom(s) but there were way too many, can you recommend a good light one with nice interface and noob-friendly? I would really appreciate it.
With regards,
OverDub
Sent from my GT-N7100 using xda app-developers app
It's hard to say which is best. A twizz rom is a stock based rom. If you want a rom with lots of features I'd look at one of the note 3 based roms like ditto. If you want something light any rooted stock rom will do then you can use titanium backup to freeze or remove anything you don't use. If you want to increase battery life then check out apps like greenify and receiver stop. They help to stop rogue programs running in the background
Sent from my GT-P3110 using XDA Premium 4 mobile app
Thanks for your help, seems that dn3 is good but I have a question, I'm using a Cyanogenmod ROM, will upgrading from cm to dn3 cause me any problems?
Sent from my GT-N7100 using xda app-developers app
No there will be no problem at all. If you are already on a 4.3 bootloader you will be fine If you aren't you just need to flash either the wifi patch or devil kernel to get wifi. I am on the n7105 which is slightly different. If you follow any of Dr ketan's guides you will not go wrong. Airview pen window and quad screen multi window are all pretty cool features in dn3
Sent from my GT-N7105 using XDA Premium 4 mobile app
You can try Tiagra ROM, its supposed to be 4.3 Touchwiz ROM with the features of Note 3.
sawdoctor said:
No there will be no problem at all. If you are already on a 4.3 bootloader you will be fine If you aren't you just need to flash either the wifi patch or devil kernel to get wifi. I am on the n7105 which is slightly different. If you follow any of Dr ketan's guides you will not go wrong. Airview pen window and quad screen multi window are all pretty cool features in dn3
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you a bunch, I'm running a 4.3.1 jellybean CyanogenMod, im I going to need to flash a WiFi patch or a kernel ?
Sent from my GT-N7100 using xda app-developers app
Just do a full wipe (is a must and most advisable) when you jump from 1 rom to another.
If you are not sure which bootloader you are in now (noobproof in my opinion) :
1) try download all the files you need first, and put them all on the SD card (ROM, Wifi patch N7100 dr. ketan).
2) Full wipe (if you are on philz cwm, do a clean wipe to flash new rom), and flash new rom.
3) let it boot. Try the wifi, if it doesn't work, it means you are on the old bootloader, then you have to follow the wifi patch instructions (or flash devil kernel on my device N7105).
antique_sonic said:
Just do a full wipe (is a must and most advisable) when you jump from 1 rom to another.
If you are not sure which bootloader you are in now (noobproof in my opinion) :
1) try download all the files you need first, and put them all on the SD card (ROM, Wifi patch N7100 dr. ketan).
2) Full wipe (if you are on philz cwm, do a clean wipe to flash new rom), and flash new rom.
3) let it boot. Try the wifi, if it doesn't work, it means you are on the old bootloader, then you have to follow the wifi patch instructions (or flash devil kernel on my device N7105).
Click to expand...
Click to collapse
Thank you for the reply, I have the ROM manager app which is associated with CWM, it has the (install a ROM from SD card) option, and if u press it There are two checks which are (wipe data) and (wipe cache).
Is it safe to use the ROM manager way of installing a ROM ?
P.S: I used the ROM manager way yesterday to change ROMs from cm 10.2 to cm 10.2 nightly and it worked perfectly.
Sent from my GT-N7100 using xda app-developers app
OverDub said:
Thank you for the reply, I have the ROM manager app which is associated with CWM, it has the (install a ROM from SD card) option, and if u press it There are two checks which are (wipe data) and (wipe cache).
Is it safe to use the ROM manager way of installing a ROM ?
P.S: I used the ROM manager way yesterday to change ROMs from cm 10.2 to cm 10.2 nightly and it worked perfectly.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Better flash MJ5 bootloader than Wifi-patch. A lot of people reported problems without new bootloader. MJ5 is knox-free.
OverDub said:
Thank you for the reply, I have the ROM manager app which is associated with CWM, it has the (install a ROM from SD card) option, and if u press it There are two checks which are (wipe data) and (wipe cache).
Is it safe to use the ROM manager way of installing a ROM ?
P.S: I used the ROM manager way yesterday to change ROMs from cm 10.2 to cm 10.2 nightly and it worked perfectly.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
You can try what dalanik suggest for the bootloader.
as for the flashing of DN3, I would suggest u flash Philz CWM, or TWRP. I myself use Philz CWM (I always use his since Note1, and so far give me less headache in my personal opinion/experienced).
Anyway, CM10.2 to CM10.2 nightly are still the same base CM. When you want to jump into TW from CM, I would highy recommend to do a full wipe. And the full wipe is the best do from recovery.
I'm sorry, I have no idea on using ROM manager to flash ROM on Note device. I left it long time ago. Galaxy S1 is my last device to use ROM manager.
antique_sonic said:
You can try what dalanik suggest for the bootloader.
as for the flashing of DN3, I would suggest u flash Philz CWM, or TWRP. I myself use Philz CWM (I always use his since Note1, and so far give me less headache in my personal opinion/experienced).
Anyway, CM10.2 to CM10.2 nightly are still the same base CM. When you want to jump into TW from CM, I would highy recommend to do a full wipe. And the full wipe is the best do from recovery.
I'm sorry, I have no idea on using ROM manager to flash ROM on Note device. I left it long time ago. Galaxy S1 is my last device to use ROM manager.
Click to expand...
Click to collapse
Good advice. Most people seem to have more success with phils revovery on DN3. Aroma can be buggy at times and different recoveries can struggle with aroma
Sent from my GT-N7105 using XDA Premium 4 mobile app
antique_sonic said:
You can try what dalanik suggest for the bootloader.
as for the flashing of DN3, I would suggest u flash Philz CWM, or TWRP. I myself use Philz CWM (I always use his since Note1, and so far give me less headache in my personal opinion/experienced).
Anyway, CM10.2 to CM10.2 nightly are still the same base CM. When you want to jump into TW from CM, I would highy recommend to do a full wipe. And the full wipe is the best do from recovery.
I'm sorry, I have no idea on using ROM manager to flash ROM on Note device. I left it long time ago. Galaxy S1 is my last device to use ROM manager.
Click to expand...
Click to collapse
Well , I Wiped , cleared cache and dalvik cache, then flashed the DN3 rom , now im stuck in a bootloop after the DN3 finished installing, i cant access my recovery menu , i tried flashing philz and still cant access, the only thing i can access is the download mod[VolumeDown+Home+Power]
I would really appreciete some help because i might have bricked my phone, im a completely new to this, so please help in the "noob" language.
OverDub said:
Well , I Wiped , cleared cache and dalvik cache, then flashed the DN3 rom , now im stuck in a bootloop after the DN3 finished installing, i cant access my recovery menu , i tried flashing philz and still cant access, the only thing i can access is the download mod[VolumeDown+Home+Power]
I would really appreciete some help because i might have bricked my phone, im a completely new to this, so please help in the "noob" language.
Click to expand...
Click to collapse
So... you really did it from ROM manager ? I guess you are faster then I reply earlier.
ok.. Now you go to this website : http://www.mediafire.com/?v6cyi52g2ydbd
and then download : philz_touch_5.00.5-n7100.tar.md5
after that you can flash it from PC Odin (since you said u still can go into download mode).
Once you see pass and your phone reboot, press vol up + home + power to go into recovery. You shall see Philz CWM there.
here is how to flash PHilz from PC Odin :
http://forum.xda-developers.com/showthread.php?t=2028103
(go to post #2)
antique_sonic said:
So... you really did it from ROM manager ? I guess you are faster then I reply earlier.
ok.. Now you go to this website : http://www.mediafire.com/?v6cyi52g2ydbd
and then download : philz_touch_5.00.5-n7100.tar.md5
after that you can flash it from PC Odin (since you said u still can go into download mode).
Once you see pass and your phone reboot, press vol up + home + power to go into recovery. You shall see Philz CWM there.
here is how to flash PHilz from PC Odin :
http://forum.xda-developers.com/showthread.php?t=2028103
(go to post #2)
Click to expand...
Click to collapse
I followed your steps , by going into recovery and doing a full wipe , then flashing it, but i ended up in a bootloop, thanks for the quick reply
antique_sonic said:
So... you really did it from ROM manager ? I guess you are faster then I reply earlier.
ok.. Now you go to this website : http://www.mediafire.com/?v6cyi52g2ydbd
and then download : philz_touch_5.00.5-n7100.tar.md5
after that you can flash it from PC Odin (since you said u still can go into download mode).
Once you see pass and your phone reboot, press vol up + home + power to go into recovery. You shall see Philz CWM there.
here is how to flash PHilz from PC Odin :
http://forum.xda-developers.com/showthread.php?t=2028103
(go to post #2)
Click to expand...
Click to collapse
Thank you so much for solving this , i now have my old CM 10.2 Nightly , so now DN3 is a no for me because of what happened , any similar roms you can recommend ?
Thank you again
OverDub said:
Thank you so much for solving this , i now have my old CM 10.2 Nightly , so now DN3 is a no for me because of what happened , any similar roms you can recommend ?
Thank you again
Click to expand...
Click to collapse
btw.. which version of CWM Philz installed on your phone ?
if you want the Note3 features, I only know DN3. Sorry I rarely see the N7100 ROM, because I only own a N7105.
But if you don't care about Note3 feature, I believe N7100 got so many rom you can try....
antique_sonic said:
btw.. which version of CWM Philz installed on your phone ?
if you want the Note3 features, I only know DN3. Sorry I rarely see the N7100 ROM, because I only own a N7105.
But if you don't care about Note3 feature, I believe N7100 got so many rom you can try....
Click to expand...
Click to collapse
My CWM is 6.0.4.3 and the philz i downloaded before you told me to download 5.00.5 was 6.70.9 , i think its the latest.
OverDub said:
My CWM is 6.0.4.3 and the philz i downloaded before you told me to download 5.00.5 was 6.70.9 , i think its the latest.
Click to expand...
Click to collapse
yep correct.
If you ever consider to try again, inside Philz, when you choose wipe data/factory reset, there's option something like "Clean wipe to install new ROM". choose this one. It will do necessary wiping + formatting system/data and necessary formatting. Then you can wipe cache & dalvik. Then you can go on on flashing again.
Or... The best way that I always use, is to clean the internal storage (if I jump from TW to AOSP or the other way around), by using Zoots script. This script (custom wipe => mega wipe), will remove everything inside the internal storage. It will make a very clean place (until your backside ) to flash new ROM.
Link : http://forum.xda-developers.com/showthread.php?t=1983489
Use it with Philz 5.0.0.5
Just an opinion, if you would ever like to try again in the future.
All recoveries can be a bit buggy with aroma and bootloop is common. Sometimes turning the phone on and off works sometimes it can take 3 or 4 attempts to work so don't panic. I don't think one of us has never had a bootloop with aroma. As antique_sonic said I think earlier versions of phils play better with aroma. I think it's version 5.15 not 5.05 that's the one I used anyway
Sent from my GT-N7105 using XDA Premium 4 mobile app
sawdoctor said:
All recoveries can be a bit buggy with aroma and bootloop is common. Sometimes turning the phone on and off works sometimes it can take 3 or 4 attempts to work so don't panic. I don't think one of us has never had a bootloop with aroma. As antique_sonic said I think earlier versions of phils play better with aroma. I think it's version 5.15 not 5.05 that's the one I used anyway
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks
5.15 it is :highfive:
So my E980 will not turn wifi on with a custom ROM. I have tried probably 10 different roms and many different android version numbers with no change. The switch is greyed out and will not turn on at all. I have the following installed:
CM12-20150625-Snapshot-YNG4NAO09M
WildKernel
I believe Mack's modem
Gapps
Nothing will fix this. I have read where other people have installed stock Kernels to fix their issues but will doing that cause a problem because I am on android version 5.x+? Everything seems to work ok on the phone other than wifi and I really need that.
Have you tried to flash CM over full stock 4.1 without custom modem? All CM based roms recommended install is: flash stock 4.1 kdz through Lg Flash Tool 2014 cse flash, then root, then freegee + cwm, then CM. And only if something is wrong then patches.
Yeah that's how I have been doing it actually. I only started doing there kernels and stuff yesterday morning. I did find that blisspop v3.6 actually had working WiFi on my phone but it had other weird issues. It would randomly reboot and then go into reinstalling the ROM and it would also randomly shut my cellular data connection off by itself. Like I could watch it turn the switch off and on ine settings app. Those coupled with really bad battery life made me flash back to stock 4.1.2.
Then after flashing back to stock I went on and did the ota update to 4.4.2 but that caused issues with the screen not coming back on after making a phone call without doing a power cycle. I would love to run a custom ROM but none I have found are stable and only one has most all the stock features working in it.
Did you use recommended recovery version? Try upgrading from stock 4.1 directly to BlissPop using latest Philz Touch or TWRP 2.8.6.0 modified? Personally i prefer this recovery: https://www.androidfilehost.com/?fid=95916177934554356 for my E988. It can flash and backup modem and EFS.
xermit said:
Did you use recommended recovery version? Try upgrading from stock 4.1 directly to BlissPop using latest Philz Touch or TWRP 2.8.6.0 modified? Personally i prefer this recovery: https://www.androidfilehost.com/?fid=95916177934554356 for my E988. It can flash and backup modem and EFS.
Click to expand...
Click to collapse
The recovery part has always confused me. Thus far I have been downloading FreeGee Free off the playstore and using it to install CWM. I tried TWRP once but the interface wouldn't work right on my device. Some of the onscreen buttons would do different things than their label said (like Reboot would take me to a different screen, not Reboot) and the slider bar at the bottom wouldn't work.
How do you install the recovery using that Zip file? And could that be causing me problems?
Noggles10 said:
How do you install the recovery using that Zip file? And could that be causing me problems?
Click to expand...
Click to collapse
I'm installing it from recovery just like another zips (ROMs etc)
Problems? Theoretically, yes, if you flash recovery that isn't compatible with your device