It's been a while since I've tinkered with my Note 3, usually because I fancied seeing what the Note 7 OS looked like etc.
The last time was to unroot my phone and put the official KitKat back.
Now after sometime I've had issues with services like Bluetooth so I reinstalled the stock ROM although it's BTU Lollipop this time because for some reason Odin wasn't accepting my H3G 4.4.2 stock ROM.
Nevertheless, it has installed but to my surprise, all my apps, settings and messages are still there. The Bluetooth service is now back in business too. I guess I should be pleased but I'm wondering if this should happen?
As mentioned, it's been a while since I played about with ROMs but that was when I rooted and used apps like CWM but how do I completely wipe my phone first without rooting, before installing the stock ROM?
To install a stock ROM I press Vol. down, Home & power buttons and use Odin but before this, do I use the Vol. Up option first to wipe everyting?
One little extra question please, because my KtKat ROM seems corrupted now, where can I go to get another one? I can see samMobile.com has them but you have to pay. If that's the norm now then so be it.
Thanks very much and hope you can help.
Actually, nevermind, I bit the pillow and tried the Vol. Up option first to wipe the data & partition cache.
Just didn't know if I was going to find myself unable to install a new ROM with the Vol. Down option afterwards.
Needless to say, it worked a treat!
Very happy bunny.
Related
Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.
Hi all. Tried my first root + custom rom installation and i messed up the device..
i had the newest KIES firmware update (phone XXBMA5) and (XXBMA6) and i rooted the device with odin (3.07). That went OK.
Then i installed the CWM recovery with odin and that was OK too.
Then i downloaded the latest Omega Rom (i missread that it supports N8020) and followed the installation instructions to the point where it started installing Omega V2.0 from SDCARD and then it asked me to select device from a list that included only (N8000,N8010,N8013)..
So the situation now is that i have working odin, working CWM and backup of the EFS (img+tar) but no working recovery. i live in Finland and the device is Sonera locked i think, so the stock roms (international) do not work i guess.
KIES has a backup of my Note but i can't even get to a point where KIES discovers the device.
So basically i think i need a working ROM for my model (Note 10.1 4G N8020), or can i recover the original samsung software somehow ?
Any advices ?
Removed
Just a thought, but can't you reflash CWM or the stock recovery?
If you didn't install the rom why do you need to re-install anything. Just powering down and powering up should have left you as was....
Alajarvi84 said:
working CWM .......... but no working recovery.
Click to expand...
Click to collapse
Maybe i'm missing something but isn't CWM your custom recovery?
It doesn't sound like you've actually installed any rom yet.The Omega installer doesn't actually install anything until a few steps after the one you mentioned about the model type.
I'm with ultramag69 on this one. You should still be on a stock rom unless you already wiped your original rom.
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
What is truly amazing is that i did not brick the device tough..
switch from cwm to stock
Alajarvi84 said:
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
Click to expand...
Click to collapse
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
jjndimp said:
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
Click to expand...
Click to collapse
I was not easy, i just tried the download mode over and over again with KIES open in windows and somehow it finally did find my device and offered a emergency restore. That is it, and the device was restored to default "original state".
OMG.... one would think after nearly having bricked your device you would either A) stop messing around with it or, B) read and learn more about what you're wanting to achieve and THEN maybe trying something with the ABSOLUTE certainty that a backup to restore is available to you in case of any mishap!
Moral of story :
Don't do anything until you are absolutely sure you have read EVERYTHING about what you are going to do.
For others wanting to mess with their devices, take heed! You may not be as lucky as OP (or troller) whichever is applicable.
There comes a certain point, that when crossed one does not care what happens to the device at hand. After fighting with my n8020 for several days in a row i couldn't care less, and like said before i dont have the level of enhusiasm like i had when i was younger. Of course i know now what went wrong.. But seriously, these are just overpriced toys, so it's not a matter of life and death.
Sent from my GT-N8020 using XDA Premium HD app
First of all, I'm a complete noob. I just joined the xda forum today after a year of following developments especially for custom roms and apps.
I have a pre-owned rooted Samsung Galaxy Note 2 (Android v4.1.1) which the "About Device" indicates is model n7105. I really wanted to "upgrade" its capabilities and features to a level close to Note 3 and/or KitKat goodness. So after reading a lot about how to flash custom ROMS, I tried Ditto Note 3 v5 (http://forum.xda-developers.com/show....php?t=2589715). Everything went well during the installation but after reboot it got stuck in the logo screen. After waiting for 10 minutes I flashed it AGAIN but with the same result. Finally after waiting for 20 minutes, I restored my phone to its backup. Now my phone can no longer detect my SIM card and my IMEI is null/unknown, even after factory reset. I made a big mistake! Then I remembered that that the original owner mentioned it's a converted E250 KOREAN version but I'm no longer able to contact her. This phone has been rooted and tweaked many times for over a year now, and having it serviced is no longer an option.
I definitely still want to flash DN3 (or any custom ROM compatible with E250) but I also need how to revert E250 to N7105 and fix my "Insert SIM card" problem. So where do I go from here? Any help/comments/suggestions on my specific case would be greatly appreciated! I am willing to learn whatever it takes to get this done and experiment.
Note: I didn't find clear answers to these in related forums and I'm also not yet able to post anything there. Hoping someone knowledgeable and helpful reads this.
103
I would begin with calming yourself down :]
There's always chance to flash proper rom so don't worry.
Pick up proper DN distribution suitable for Your device and flash again.
Remember to clean system for new rom, wipe data/factory reset and also wipe cache and dalvik cache, format system, and flash the thing again.
Remember that not always rom will boot from the first kick.. it often happens to me (freeze on first screen - not Samsung but the one with Note2 screen), it's as easy as taking the battery off the device and reconnecting it again for awhile and then power on again (sometimes it works in thrid attepmt so be patient, once it runs there should be no more further problems)
I hope You will solve Your problem.
Good luck!
Yep I totally agree with roozxx on that
Sent from my GT-N7100 using XDA Premium 4 mobile app
Hello XDA!
I have some questions about my n8010. It is a tablet that I bought in Greece, in case that is necessary to know, and has an interesting background. It started late May. The tablet was unrooted and without any mods whatsoever. I was running the latest Jelly Bean update and had A TON of lag. I had replaced TouchWiz Launcher with Nova and a different gallery and music app with still a lot of lag. So I decided to flash CM11 since it would be lighter for the tablet. After some research I followed the root guide from Zedomax and everything was fine. I had root and so I proceeded doing a backup. This where everything got weird. The backup started but was stuck for long periods of time. After some time being stuck in a screen I decided I should force restart. After the Galaxy Note 10.1 logo appeared it just hanged there without booting into Jelly Bean. I checked recovery and download mode and they where all working fine so I flashed TWRP. It worked and so I took a backup and proceeded installing CM11. I had it already in my SD. I had followed the instructions in the XDA thread that said about removing a line to make it work on the n8010. The flash went great and after factory resetting I rebooted the tablet and everything was OK. At the first boot WiFi wouldn't work but after a reboot it was. The only thing that wasn't working was the video recording. It is a deal-breaker as I use it a lot. I had to switch ROMs. I tried CM10.2 and it still wouldn't. Same goes for Revolt. At lat I switched to a TouchWiz based ROM. Specifically Hyperdrive RLS8. Video was working so I stayed there. I was noticing that since I flashed CM11 my tablet showed up as an n8013 which was very weird but since these ROMs where designed for the n8013 I thought it was normal.
One ROM also had the front facing camera able to record. Upon further inspection I found that Download Mode had my tablet as an n8010 but with the flash count 0 and the status official! Now, I'm either super lucky or the completely opposite! It also says official under About Device! Fast forward a few months and I am now in a situation where the tablet lags once again like crazy. I uninstalled a couple of apps and also installed lighter alternatives and it's somewhat bearable. I was reading the Official OmniROM thread and saw that others also had issues, most of which had the new KitKat bootloader that I don't have, with YouTube and the Video Recording. The latest nightlies are said to have a fix. So I am thinking of installing OmniROM since I am lagging a lot and I would like Screen Mirroring to the Chromecast. My only concern is that I will either brick the tablet or the camcorder won't work. Many people have bricked their Notes and can't go back without the Samsung Service. Most have the new KitKat bootloader which I don't and I'm happy about. My tablet is in a weird situation, what should I do? Anybody else experiencing these issues? Any advice is appreciated!
Thanks in advance,
Chris
Edit: Forgot to say that I flashed Carbon ROM in September and I got a status 7 while flashing with PhilzCWM that I had installed in order to flash Hyperdrive. I had to flash back to Hyperdrive as it wouldn't boot after the status 7. It probably happened because it didn't have SE Linux support. If I do anything I'll flash the latest TWRP.
chrismin13 said:
Hello XDA!
I have some questions about my n8010. It is a tablet that I bought in Greece, in case that is necessary to know, and has an interesting background. It started late May. The tablet was unrooted and without any mods whatsoever. I was running the latest Jelly Bean update and had A TON of lag. I had replaced TouchWiz Launcher with Nova and a different gallery and music app with still a lot of lag. So I decided to flash CM11 since it would be lighter for the tablet. After some research I followed the root guide from Zedomax and everything was fine. I had root and so I proceeded doing a backup. This where everything got weird. The backup started but was stuck for long periods of time. After some time being stuck in a screen I decided I should force restart. After the Galaxy Note 10.1 logo appeared it just hanged there without booting into Jelly Bean. I checked recovery and download mode and they where all working fine so I flashed TWRP. It worked and so I took a backup and proceeded installing CM11. I had it already in my SD. I had followed the instructions in the XDA thread that said about removing a line to make it work on the n8010. The flash went great and after factory resetting I rebooted the tablet and everything was OK. At the first boot WiFi wouldn't work but after a reboot it was. The only thing that wasn't working was the video recording. It is a deal-breaker as I use it a lot. I had to switch ROMs. I tried CM10.2 and it still wouldn't. Same goes for Revolt. At lat I switched to a TouchWiz based ROM. Specifically Hyperdrive RLS8. Video was working so I stayed there. I was noticing that since I flashed CM11 my tablet showed up as an n8013 which was very weird but since these ROMs where designed for the n8013 I thought it was normal.
One ROM also had the front facing camera able to record. Upon further inspection I found that Download Mode had my tablet as an n8010 but with the flash count 0 and the status official! Now, I'm either super lucky or the completely opposite! It also says official under About Device! Fast forward a few months and I am now in a situation where the tablet lags once again like crazy. I uninstalled a couple of apps and also installed lighter alternatives and it's somewhat bearable. I was reading the Official OmniROM thread and saw that others also had issues, most of which had the new KitKat bootloader that I don't have, with YouTube and the Video Recording. The latest nightlies are said to have a fix. So I am thinking of installing OmniROM since I am lagging a lot and I would like Screen Mirroring to the Chromecast. My only concern is that I will either brick the tablet or the camcorder won't work. Many people have bricked their Notes and can't go back without the Samsung Service. Most have the new KitKat bootloader which I don't and I'm happy about. My tablet is in a weird situation, what should I do? Anybody else experiencing these issues? Any advice is appreciated!
Thanks in advance,
Chris
Edit: Forgot to say that I flashed Carbon ROM in September and I got a status 7 while flashing with PhilzCWM that I had installed in order to flash Hyperdrive. I had to flash back to Hyperdrive as it wouldn't boot after the status 7. It probably happened because it didn't have SE Linux support. If I do anything I'll flash the latest TWRP.
Click to expand...
Click to collapse
I would have fixed the original lag issues first. I would get it back to factory stock 100 percent, once back to factory I would do A factory reset and start all over. Get the system running stock as it should then reinstall apps one at a time. if it can't run stock for whatever reason other roms not going to fix the problem.
at least with factory stock you know what should be working. Instead of guessing if the problem is part of the new ROM
shaun298 said:
I would have fixed the original lag issues first. I would get it back to factory stock 100 percent, once back to factory I would do A factory reset and start all over. Get the system running stock as it should then reinstall apps one at a time. if it can't run stock for whatever reason other roms not going to fix the problem.
at least with factory stock you know what should be working. Instead of guessing if the problem is part of the new ROM
Click to expand...
Click to collapse
Thanks for the response!
Good idea! I was thinking of going back to stock and repeating everything. It should fix all my issues. It's too bad that I don't have a working stock backup and I will have to flash through Odin. The reason that I am not doing this is because I am afraid of making it even worse from the official status state that I have in Download Mode and my device is an n8013 under About Device. A flash back to stock through Odin would probably flash most of the system parts which would be kinda dangerous. But on the other hand that would mean that I could give it a brand new try with better luck possibly! It's not that TouchWiz ROMs don't work, it's AOSP that doesn't. I played a lot with Hyperdrive and seems like it's doing better from the lag prospective. But that's only gonna last 15 days. I am sure! So, I'll have your response in mind! Might try it out when I have some free time. Unfortunately, that will probably be Christmas.
Thanks,
Chris
Going back to stock is good advice.Should certainly fix the video problem which you said was important.
Phil789 said:
Going back to stock is good advice.Should certainly fix the video problem which you said was important.
Click to expand...
Click to collapse
I don't have any video playback issues. It's just the camcorder that doesn't work in AOSP ROMs.
Yes.My use of the word "video" should have been "video recording".
The time has come!
Hello everyone, happy holidays!
The time has come that I follow your instructions. I've done my research and here's how I'll do it. Do you agree? Do you have any other suggestions?
Take full backups with my current configuration (Hyperdrive RLS8, PhilzCWM)
Factory reset the device and clean it up so that there is a lot of space
Install Samsung Drivers
Flash Stock Greek 4.1.2 Frimware (N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5) through ODIN v3 1.85
Let it boot up and do a factory reset from stock recovery
Flash TWRP 2.8.1.0 for the GT-N8010 (openrecovery-twrp-2.8.1.0-gt-n8010) (I chose this version since it has the most downloads)
Make a full backup once again
Flash Omni ROM 4.4.4 (omni-4.4.4-20141222-n801x-NIGHTLY)
Flash SuperSU (UPDATE-SuperSU-v2.40)
Flash PA GApps (pa_gapps-modular-mini-4.4.4-20141214-signed.zip)
Factory reset
REBOOT!
Check everything (Video, model, download mode, bugs, etc.)
REPORT!
If everything goes correctly I believe I should be OK! Hope my issues will be over since the tablet is slow once again. Kinda scared, so that's why I'm asking you. Will I be (mostly) brick safe? Hope so!
Thank you very much for your support,
Chris
P.S.: Should I root before leaving stock? I mean through TWRP.
chrismin13 said:
Hello everyone, happy holidays!
The time has come that I follow your instructions. I've done my research and here's how I'll do it. Do you agree? Do you have any other suggestions?
Take full backups with my current configuration (Hyperdrive RLS8, PhilzCWM)
Factory reset the device and clean it up so that there is a lot of space
Install Samsung Drivers
Flash Stock Greek 4.1.2 Frimware (N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5) through ODIN v3 1.85
Let it boot up and do a factory reset from stock recovery
Flash TWRP 2.8.1.0 for the GT-N8010 (openrecovery-twrp-2.8.1.0-gt-n8010) (I chose this version since it has the most downloads)
Make a full backup once again
Flash Omni ROM 4.4.4 (omni-4.4.4-20141222-n801x-NIGHTLY)
Flash SuperSU (UPDATE-SuperSU-v2.40)
Flash PA GApps (pa_gapps-modular-mini-4.4.4-20141214-signed.zip)
Factory reset
REBOOT!
Check everything (Video, model, download mode, bugs, etc.)
REPORT!
If everything goes correctly I believe I should be OK! Hope my issues will be over since the tablet is slow once again. Kinda scared, so that's why I'm asking you. Will I be (mostly) brick safe? Hope so!
Thank you very much for your support,
Chris
P.S.: Should I root before leaving stock? I mean through TWRP.
Click to expand...
Click to collapse
I did it! It worked. Everything went OK but:
- Flash count is 0 and status official
- Back camera records in slow-mo
- Chromecast mirroring does not work
However:
-My device is an N8010
-I use the front camera instead
-Mirroring was not really needed
-LAG IS HISTORY!!! [emoji50] [emoji2] [emoji2] [emoji2]
I am so impressed by the performance, still doesn't best my nexus 4 with KK 4.4.4 but it's a GIGANTIC IMPROVEMENT! Veeery happy! Thank you for your support, I wouldn't be here without you!
Merry Christmas and happy holidays!
Chris.[emoji2]
Hello all! Long time lurker and user of LOS 14.1 on my osprey. COM13 before that. I'm not a tech wizard like most of you, but I'd say I'm fairly good at navigating this stuff. Hope someone out there can help me out with MMS issues.
I'm on 14.1-20190220-Nightly with squid's kernel and my service provider is T-mobile. I can't pinpoint exactly when but at some point in the last month, I stopped receiving MMS messages. I can send them, but when I try to receive, I get the "check your APN settings" message. APN settings have not changed and I have confirmed they are correct. I've wiped the cache partition and that did nothing. I don't know what else to try.
A possible related issue: sometimes SMS doesn't come through either until I turn off WiFi, or reboot. This is a difficult thing to reproduce, it seems intermittent.
Any direction or advice would be greatly appreciated! Thanks!
In the settings find the option to reset the Network settings.This section can get munged.I'm not on the Stock rom on my 2015 X1541(Osprey) I've recently installed Lineage's 16.1,"Pie" .Absolute dream rom.I didn't think anyone would bother making PIE for such and old phone but Lineage have done it proud
R1ffR4ff said:
In the settings find the option to reset the Network settings.This section can get munged.I'm not on the Stock rom on my 2015 X1541(Osprey) I've recently installed Lineage's 16.1,"Pie" .Absolute dream rom.I didn't think anyone would bother making PIE for such and old phone but Lineage have done it proud
Click to expand...
Click to collapse
How long ago did you install 16.1? Any issues at all with it? I might just go that route
I recently did the Network Settings Refresh to try and solve an issue with constant dropped Bluetooth connections. But I will give it another try! Thanks!
I installed PIE a few days ago.Not had one single problem with it.
I got it from here,
http://www.droidthunder.com/android-9-0-pie-on-moto-g3/
and I think it's compatible with your phone if.....
This Android 9.0 Pie based Lineage OS 16 ROM is compatible only with Motorola Moto G3 (Moto G 2015) with model numbers XT1540, XT1541, XT1542, XT1543, XT1544, XT1548 and XT1550. So do not try to flash this unofficial custom ROM on any other phone as it may cause permanent damage or even brick your phone. So its always better to confirm your device before moving ahead.
I made and kept a Nandroid backup of the Stock rom on my Laptop just in case.I now keep a Nandroid backup the PIE install with all my apps installed and the phone setup on my Laptop as well.
So many great features in PIE.I've even been able to swap my Return and Recent apps buttons from Left-to-Right as I'm right handed and hated having the Return button on the left
Tip:
If you do install any Custom rom wait for it's first boot to normal screen(Usually takes quite a while) then reboot to Recovery and do a Factory reset before you set up the phone.I've done this with every Custom rom I've installed on Android phones and it seems to prevent many problems.
I think some people also do a Factory reset before installing Custom roms as well.I can't remember if I did but most likely did .
R1ffR4ff said:
I installed PIE a few days ago.Not had one single problem with it.
I got it from here,
and I think it's compatible with your phone if.....
This Android 9.0 Pie based Lineage OS 16 ROM is compatible only with Motorola Moto G3 (Moto G 2015) with model numbers XT1540, XT1541, XT1542, XT1543, XT1544, XT1548 and XT1550. So do not try to flash this unofficial custom ROM on any other phone as it may cause permanent damage or even brick your phone. So its always better to confirm your device before moving ahead.
I made and kept a Nandroid backup of the Stock rom on my Laptop just in case.I now keep a Nandroid backup the PIE install with all my apps installed and the phone setup on my Laptop as well.
So many great features in PIE.I've even been able to swap my Return and Recent apps buttons from Left-to-Right as I'm right handed and hated having the Return button on the left
Tip:
If you do install any Custom rom wait for it's first boot to normal screen(Usually takes quite a while) then reboot to Recovery and do a Factory reset before you set up the phone.I've done this with every Custom rom I've installed on Android phones and it seems to prevent many problems.
I think some people also do a Factory reset before installing Custom roms as well.I can't remember if I did but most likely did .
Click to expand...
Click to collapse
Interesting. Have you tested MMS and Bluetooth? If those are working, I might just do this.
Thanks for the tips, I keep full nandroid backups too, just in case. I hadn't heard about performing the factory resets during the process but I will do that this time. Is the sequence: factory reset, then boot the ROM, then reboot back into TWRP, then wipe and flash as normal, then boot into new ROM, then reboot into TWRP, factory reset, then finally boot the ROM and setup as normal?
It seems strange that droidthunder instructs you to copy the zip file to internal memory, then wipe the internal memory and then try to flash the zip. Doesn't seem like that would work. Why not just copy the zip to the SD card and flash from there?
Cheers!
I think I just copied mine to the SD card.
I don't use MMS much as WhatsApp etc is way better and normal phone calls/Networks are getting old now but I've just tested MMS and working fine.
I don't use Bluetooth much but it works between my Moto G3 and my DooGee Chinaphone running Android Mokee custom rom.
PIE rocks!!!!!!!
Better battery management.Super slick and as said great features.I don't use the new Gesture system as I've always used,"Holo Launcher" instead of stock launchers and use it's Gesture options but PIE has loads of features but they have been moved around a bit just a bit of a new learning curve but nothing too hard.
R1ffR4ff said:
I think I just copied mine to the SD card.
I don't use MMS much as WhatsApp etc is way better and normal phone calls/Networks are getting old now but I've just tested MMS and working fine.
I don't use Bluetooth much but it works between my Moto G3 and my DooGee Chinaphone running Android Mokee custom rom.
PIE rocks!!!!!!!
Better battery management.Super slick and as said great features.I don't use the new Gesture system as I've always used,"Holo Launcher" instead of stock launchers and use it's Gesture options but PIE has loads of features but they have been moved around a bit just a bit of a new learning curve but nothing too hard.
Click to expand...
Click to collapse
Cool! Thanks for the feedback! I'll assume I have the factory reset sequence correct. I dig Holo Launcher too. Been using it for many years now
emanresutseb said:
Cool! Thanks for the feedback! I'll assume I have the factory reset sequence correct. I dig Holo Launcher too. Been using it for many years now
Click to expand...
Click to collapse
One word of warning.If you do a Factory reset after installing the Custom Rom it unroots the phone but I wanted that as one of my Banking apps won't run on a Rooted phone.I could just leave it rooted and use the Banking web page but the apps are more convenient
R1ffR4ff said:
One word of warning.If you do a Factory reset after installing the Custom Rom it unroots the phone but I wanted that as one of my Banking apps won't run on a Rooted phone.I could just leave it rooted and use the Banking web page but the apps are more convenient
Click to expand...
Click to collapse
Ah yes, good point. I do like some rooted apps like Titanium and Greenify. :good:
emanresutseb said:
Ah yes, good point. I do like some rooted apps like Titanium and Greenify. :good:
Click to expand...
Click to collapse
You don't need Titanium as TWRP Nandroid backup saves everything on the internal memory and everything else I want to keep is on the cloud or copied via USB to my PC/Latop.
As for Greenify those kind of apps are useless.You don't need battery savers in Android and even less since Marshamallow.PIE has awesome Battery management and even learns your usage.
FYI. I tried so many different things and nothing worked. Factory reset, no. Clean wipe and reflashed 14.1, no. Called service provider and they refreshed my connection, no. Then I installed squid2's 15.1 beta and it is working very well. Solved a lot of different annoying issues I was having. Hope it keeps working!!
emanresutseb said:
FYI. I tried so many different things and nothing worked. Factory reset, no. Clean wipe and reflashed 14.1, no. Called service provider and they refreshed my connection, no. Then I installed squid2's 15.1 beta and it is working very well. Solved a lot of different annoying issues I was having. Hope it keeps working!!
Click to expand...
Click to collapse
Glad you found something that works
So far, so good. Loving this ROM. It is as close to perfectly functional as any I have ever tried.
emanresutseb said:
So far, so good. Loving this ROM. It is as close to perfectly functional as any I have ever tried.
Click to expand...
Click to collapse
I feel the same about the PIE rom on my G3.It makes the old phone feel like a Brand new one :laugh: