Related
Hi folks and especially Chainfire if he is tracking nu-bees,
Nu-bee here. Just installed Resurrection Remix Pro ICS firmware following instructions at Galaxy2Root.com. They had me install 3 files with the Remix package, GoogleApps and GoogleAppsFix. All went well. Then the instructions told me to install 10_CWM.zip so that ClockWorkMod would work. But CWM had been overwritten, so I couldn´t install something from my internal sdcard. I thought I would be clever and install one of Chainfire´s custom CF-root packages. I selected one close to the kernel number I have installed (LPJ). I flashed it over with Odin.
No joy. The phone booted, showed the opening logo and then lay there with a black screen. But CWM recovery still was active, so I wiped the system and reinstalled the files this time including 10_CWM.zip (4 files). This time I have ICS but CWM is gone again. I´d like to back up the ROM.
I´d like suggestions as to how to get CWM installed. I would be most grateful! I read the entire 450 page set of posts on Chainfire´s CF-root upgrades (whew). I´d use one of those if I was confident that I wouldn´t go back to a black screen again.....
still trying
Well, I haven´t gotten much of a response with this. With this 10 post limit for noobies, I can´t get to the developers forum where I would find the folks who grapple with these kinds of issues.
Anyway, I flashed the latest of Chainfires kernels, the LP7 version, and ended up with a black screen again. So I went into restore (and had CWM restore at least) and restored my ROM, etc. But of course, I lost CWM in the process. And had to reconfigure my phone all over again. I had used My Backup Pro and it didn´t save the connections to the Google Market, so I had to reinstall my apps all over again. Is Titanium better in this regard? My Backup Pro claims to make better backups for rooted phones, but this was pretty feeble.
So that will be my question for this forum - should I change to Titanium? Will it get all my apps, settings, and data back into my preferred configuration?
Have a great day......
I am in same boat as you are. I buy i just installed rom with Rom manager and i have Gapps fixer and remix one left and CWM ofcourse. So my problem is i don't have Ex-sd as they suggest to Install "Cwm.zip from external sd card from recovery". How to do so ?
Please help
Thanks in advance
EDIT: Never mind I sort it out Yesterday. I installed from Rom manager & Flash recovery from it and then boot up into recovery from App and then Flash Touch Recovery.
[Q] Verizon GS3 I535, rooted w/ Saferoot, attempted flash w/ Safestrap & Alliancerom
I successfully rooted my Verizon GS3 I535VRUCML1 using Saferoot ( http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1 ). I successfully got Safestrap going to attempt to flash a custom rom ( http://forum.xda-developers.com/showthread.php?t=2605648 ). I tried flashing Alliancerom ( http://forum.xda-developers.com/showthread.php?t=1973982 ) over the stock rom. I read that this was possible & several people said they were able to load custom roms over stock, because of the limited space on the phone (16GB); however when I tried to do it, the rom started, & then as soon as it said it was going to format the rom, it rebooted the phone & soft-bricked it. I was able to get back to a stock rom using Odin & the bad partition fix ( http://forum.xda-developers.com/showthread.php?t=2586319 ), but I'm wondering how others were able to install custom roms over stock without an issue like this happening. I will say that, with all the options available in Alliancerom, I choose the following:
Email Selection(stock)
Launcher Selection (Apex)
Messaging Selection (AOSP)
File Manager Selection (Both Es file & Myfiles)
KeyBoard Selection (both stock & google)
Accuweather Widget Selection (s5 themed)
Music Selection (Touchwiz Music)
Bootanimation (Kitkat Anim)
System Sounds (Aosp Sounds)
Misc App Selection (all)
Kernel Selection(Safestrap)
Not sure if any of those may have affected the install. I know they say you can't install AOSP roms, but I figured AOSP options within this 4.3 TW rom didn't count & should be ok.
I really need help guys!! Get me off STOCK!!!!!
Update
So I redid Saferoot & Safestrap, & this time I installed Alliancerom on Romslot-1. When choosing a format option, I choose just to wipe cache & davlik (I think last time I choose to wipe /data too because I wanted a clean install). I seemed to get it installed, but then when going through setup, I couldn't even make it past adding my Google account before it would just reboot the phone on its own. I still would like to be able to install over the stock, & I still want a STABLE rom obviously, which it appears this is not.....why do I seem to be one of the only people having issues with this Alliancerom?? His board seems to show plenty of happy users, so why can't I seem to get it installed & setup successfully?
SadPanda284 said:
So I redid Saferoot & Safestrap, & this time I installed Alliancerom on Romslot-1. When choosing a format option, I choose just to wipe cache & davlik (I think last time I choose to wipe /data too because I wanted a clean install). I seemed to get it installed, but then when going through setup, I couldn't even make it past adding my Google account before it would just reboot the phone on its own. I still would like to be able to install over the stock, & I still want a STABLE rom obviously, which it appears this is not.....why do I seem to be one of the only people having issues with this Alliancerom?? His board seems to show plenty of happy users, so why can't I seem to get it installed & setup successfully?
Click to expand...
Click to collapse
I have had problems ever since he started to use xposed framework. Use to love his roms but alliance is not to my personal standards. If you want stability I would suggest finding a rom that doesn't use xposed.
This is a WW SKU ROM with custom Kernel based on the latest ASUS stock firmware. It has been pre-rooted, zipaligned and debloated. The ROM has busybox, some added applications and minor tweaks.
Some of the things removed
ASUS Browser
Asus Email
Asus Setup Wizard
Asus Story
File Manager
Kindle
Omlet
Press Reader
What's Next
Zinio
... and more
... and even more (r150131)
Things added
Latest SuperSu
Total Commander (replaces the ASUS file manager)
The good old ASUS Tree
Day Scene live wallpaper
The new Pixelmaster Camera (r150131)
RootDim (r150301)
Features
The ROM will not touch your custom recovery, plus it installs over any previous ROM
eMMc fstrimmed during setup
Mobile data is now disabled by default
Auto-wipe dalvik cache (r150131)
Default CPU governor is now Interactive (r150301)
Minimum brightness lowered to 1 in kernel (plays nicely with Rootdim) (r150301)
How to install
Make sure your phone is unlocked
Flash CWM recovery 6.0.2.9
Boot into recovery mode
Select "wipe data/factory reset"
Select "install zip from sideload" (my preferred), or "install from zip" (if you have copied the ROM previously to the root of your phone)
Wait until it says it's done, then reboot* (see next section below)
Wait some more until it configures itself for the first time
*Fairly relevant
When CWM asks "ROM may flash stock rocovery on boot. Fix?" Choose "No"
When CWM asks "ROM access possibly lost. Fix?" Choose "No"
Downloads
CWM 6.0.2.9
Tari's ASUS PadFone 2 ROM+KERNEL (KitKat 4.4.2 r150301)
tari01 said:
[*]The ROM will not touch your custom recovery, plus it installs over any previous ROM
Click to expand...
Click to collapse
so i can install this over the GuerillaROM (4.1.1) from SiSSiDroid??
BPM said:
so i can install this over the GuerillaROM (4.1.1) from SiSSiDroid??
Click to expand...
Click to collapse
I see no reason why you couldn't. I only advise you to flash the CWM recovery first, then do all the wiping as mentioned (note that this will be a clean install, so back up anything of importance to you).
If you are paranoid enough (this generally applies to any ROM installation), you can enter CWM, and mount + format ALL the partitions you see there one-by-one. After this (rather extreme preventive measure) boot into recovery again and do whatever you wish.
Please do tell me about you installation experience, so others could learn, and I could improve the instructions.
tari01 said:
I see no reason why you couldn't. I only advise you to flash the CWM recovery first, then do all the wiping as mentioned (note that this will be a clean install, so back up anything of importance to you).
If you are paranoid enough (this generally applies to any ROM installation), you can enter CWM, and mount + format ALL the partitions you see there one-by-one. After this (rather extreme preventive measure) boot into recovery again and do whatever you wish.
Please do tell me about you installation experience, so others could learn, and I could improve the instructions.
Click to expand...
Click to collapse
flashing works without problems. do not forget to wipe dalvik cache because device will hang on boot if you forgot this!!
its not my primary device any more so i have not really test it now.
will test a bit more and report back.
want to sell my device and have to be sure that everything works without problems
Finally a custom kitkat rom for our Padfone 2!
I am on the latest stock kitkat version of the device. I really want to test your rom, but i am a noob and have no experience on flashing the device. I tried to flash CWM using fastboot as a first step, but i am failing.
Do i need to unlock or root the device first ?
impact79 said:
Finally a custom kitkat rom for our Padfone 2!
I am on the latest stock kitkat version of the device. I really want to test your rom, but i am a noob and have no experience on flashing the device. I tried to flash CWM using fastboot as a first step, but i am failing.
Do i need to unlock or root the device first ?
Click to expand...
Click to collapse
Yes, custom recoveries/ROMs can only be flashed onto unlocked devices.
tari01 said:
Yes, custom recoveries/ROMs can only be flashed onto unlocked devices.
Click to expand...
Click to collapse
Whats the easiest way to unlock the device? Mine is under latest kit kat and rooted.
Thanks in advance!
rafael_mfr said:
Whats the easiest way to unlock the device? Mine is under latest kit kat and rooted.
Thanks in advance!
Click to expand...
Click to collapse
See this post.
tari01 said:
See this post.
Click to expand...
Click to collapse
I just managed to unlock my bootloader on kitkat WW11.8.4.23 using just the Asus UnLock.apk after I changed my GMail "less secure app settings" without any difficulties!
Then I easily flashed CWM using fastboot. I'm going to flash your rom as soon as I download it. Thanks.
ansarijavid said:
I just managed to unlock my bootloader on kitkat WW11.8.4.23 using just the Asus UnLock.apk after I changed my GMail "less secure app settings" without any difficulties!
Then I easily flashed CWM using fastboot. I'm going to flash your rom as soon as I download it. Thanks.
Click to expand...
Click to collapse
Wow. That is very good news. If you have the time, you could go to the other thread and post step-by-step instructions in case somebody is interested. Thanks for sharing this.
tari01 said:
Wow. That is very good news. If you have the time, you could go to the other thread and post step-by-step instructions in case somebody is interested. Thanks for sharing this.
Click to expand...
Click to collapse
I just downloaded the UnLock.apk here: http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone2/UnLock.zip
What I did was simply as follows:
1. Installed UnLock.apk and ran it.
2. Accepted warnings.
3. Inserted my gmail password (it automatically identified my account).
4. It failed with the "not valid password message.
5. In my gmail inbox, I got a message that gmail had blocked access from "less secure app", of course UnLock.apk!
6. I followed a link in the gmail message and changed the settings so that "less secure apps" could access my account.
7. I repeated steps 2 and 3 again, this time my phone restarted quickly, on the bootloader, I got a message that bootloader was "Unlocked".
8. then I downloaded the CWM you provided and flashed it (fastboot flash recovery cwm.img) in CMD.
@tari01,
I wondered if this thread is still monitored. I have a problem with my Padfone 2 and I wondered if you could help me...
gentle_giant said:
@tari01,
I wondered if this thread is still monitored. I have a problem with my Padfone 2 and I wondered if you could help me...
Click to expand...
Click to collapse
Well, I get E-mail notifications and I still own a PadFone 2 - so I guess the answer is yes. Whether I can help you remains to be seen
great, perhaps you can help me further.
It is only indirect related to this tread. My Padfone 2 was soft-bricked, I found this tread, followed the instructions, the ROM starts up well but if I restart it the same old thing. It stops at the boot logo and stays there.
using CWM I can see that every time after a restart, in recovery, /data, /sdcard, /system, /persist and /tombstone are not mounted.
Perhaps this is normal when in discovery, anyway, I can mount all the items except /sdcard.
In CWM I can also see warnings:
E: can't open /cache/recovery/log
what could be going wrong?
gentle_giant said:
great, perhaps you can help me further.
It is only indirect related to this tread. My Padfone 2 was soft-bricked, I found this tread, followed the instructions, the ROM starts up well but if I restart it the same old thing. It stops at the boot logo and stays there.
using CWM I can see that every time after a restart, in recovery, /data, /sdcard, /system, /persist and /tombstone are not mounted.
Perhaps this is normal when in discovery, anyway, I can mount all the items except /sdcard.
In CWM I can also see warnings:
E: can't open /cache/recovery/log
what could be going wrong?
Click to expand...
Click to collapse
I think this could be beyond me, but I can give you a few pointers. If you are planning to flash "my" Kernel and ROM:
- Make sure every file is from the links I provided
- Start the whole flashing thing all over again from the first step
- After CWM is installed, try to format EVERY partition you can find
- If your phone is not unlocked and the motherboard has been serviced, all sorts of things could go wrong
- Note that the ROM is based on the WW firmware, make sure your phone is the same
- Do not use Linux live sessions for flashing - use a full instalation
That's about it. I really can't think of anything clever to add - I hope it helps you somewhat.
thanks for the info Tari01.
the first 3 points were done as per instructions. I formatted all partitions twice on two separate occasions.
As far as I know the phone is unlocked but I didn't use the unlock app after I tried to flash your ROM, or any other ROM for that matter.
But once unlocked it stays unlocked isn't it? I mean, I can flash any recovery.
The second last point: I'm aware of this. I always choose WWE based roms.
your last point: I don't know anything about Linux command lines etc. As a matter of fact, when I use ADB or fastboot I just go through the motions as per instructions but I hardly know what I'm doing.
On the bright side; I'm most likely not the only one.
I will use this phone solely as a learning devices for better understanding of the Android platform and ADB etc.,...
@tari01 - greetings and thanks for a wonderful custom ROM - I have just flashed it and it seems very stable for now.
Two questions though - did you remove the Audio Wizard from the stock ASUS ROM? Don't know 'bout you, but I think the sound was more "vibrant" when docked into the tablet when using a Stock ROM (but the stock rom was more unstable, I have NO IDEA why - gapps/android.system/everything kept crashing after a few hours).
Second, is your custom ROM compatible with Stone Kernel? I would like to try it out (OC version, because, overclock, why not? )
Thanks in advance for a cool ROM, and I shall await your reply.
tassadaru said:
@tari01did you remove the Audio Wizard from the stock ASUS ROM? Don't know 'bout you, but I think the sound was more "vibrant" when docked into the tablet when using a Stock ROM
Click to expand...
Click to collapse
I removed the Audio Wizard because I saw it as unnecessary bloatware. I doubt it would make any difference, since it only changed audio profiles. I use Rocket Player for music and BS and MX Player for video: all these can be tuned to sound as you like.
tassadaru said:
@tari01is your custom ROM compatible with Stone Kernel? I would like to try it out (OC version, because, overclock, why not? )
Click to expand...
Click to collapse
I am not sure what would happen if you used an older kernel. In the one that I've built , the CPU governor is not set in stone: If you want to use another one, there are many apps in the Play Store that will allow you to change it, and you can also set the desired frequencies. Note, that of all the CPU governors the one that I set proved to be the most efficient - it runs on a single core when you don't need CPU power, then, as applications request more power, it activates the entire CPU and delivers as much as it can - all this saves a lot of battery power. Overclocking will definitely drain your battery much faster, and I'm not sure you'd get noticeable performance.
@tari01 - thank you for the quick reply and the info provided. I am replying because, as I said, I encountered problems when using stock 4.4.2 - it seems your ROM is not exempt from those problems.
To be more specific, everything on my home screen disappears completely, only the live wallpaper remains, then when I try to open any app from the apps menu, com.google.process.gapps and android.process.acore keep crashing (Unfortunately, xxx has stopped message).
This happens after the phone/tablet is in idle for a few hours (as far as I could test it). I tried wiping cache, etc, but to no avail.
Android 4.1.1 does not have this issue, but the phone/tablet moves like an earthworm compared to 4.4.2 and support is limited.
Any ideas/pointers? I flashed your ROM over a stock 4.4.2 using the images you provided, and using the instructions you provided.
Thank you in advance!
tassadaru said:
@tari01 - thank you for the quick reply and the info provided. I am replying because, as I said, I encountered problems when using stock 4.4.2 - it seems your ROM is not exempt from those problems.
To be more specific, everything on my home screen disappears completely, only the live wallpaper remains, then when I try to open any app from the apps menu, com.google.process.gapps and android.process.acore keep crashing (Unfortunately, xxx has stopped message).
This happens after the phone/tablet is in idle for a few hours (as far as I could test it). I tried wiping cache, etc, but to no avail.
Android 4.1.1 does not have this issue, but the phone/tablet moves like an earthworm compared to 4.4.2 and support is limited.
Any ideas/pointers? I flashed your ROM over a stock 4.4.2 using the images you provided, and using the instructions you provided.
Thank you in advance!
Click to expand...
Click to collapse
Well, I'm afraid this seems to be out of my league. I'm still using my PF2 (in fact, it's my only phone/tablet), but I have no issues with it. Perhaps the only thing worth mentioning is that I don't use live wallpapers, I let my apps regularly update via Wi-Fi, and that I have a hacked Play Store. The rest is pretty much the same as you'd find it after flashing the ROM. I really have no idea what could be causing the errors you get
I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Morthawt said:
I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Click to expand...
Click to collapse
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
LS.xD said:
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
Click to expand...
Click to collapse
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Morthawt said:
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Click to expand...
Click to collapse
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
LS.xD said:
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
Click to expand...
Click to collapse
Oh I will read everything before trying anything serious like this. I felt as if I was smashing my phone into the ground when I rooted it lol, so dangerous :S, even though I was following a guide. But now that I have all the tickboxes ticked and backed up and I have also copied that backup to 2 different hard drives... I should be safe with that.
So for my additional questions.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
Thanks so much for answering my questions, it is really making me feel more confident with the whole process. I don't like going into things blind, I'm a computer techie and like to know what I am doing and why I am doing it. This phone customization business is entirely new to me beyond changing settings and themes lol.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
--> You could flash a wrong zip containing a recovery (Probably you will not do)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
--> Yes
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
--> Every rom has an updater-script that (normally) checks the compatiblity before TWRP installs it
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
--> Stable means NO BUGS, Nightlies are updated nearly every day with the latest commits as they are in development status. May or may not contain bugs. Check out the specific rom thread on xda. Stability of the rom / bugs are discussed there by the users every day. So you can check out which version will work.
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
--> Restore the phone to fully stock firmware. Such official firmware can be found at SamMobile.com
And most important: Press "thanks" at the botom of my posts
(had to remove quotes due to outside links preventing my posting.)
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
Thanks button pressed on them, because truly your information is extremely helpful.
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
LS.xD said:
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
Click to expand...
Click to collapse
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
EDIT: Should I wipe Preload?
Morthawt said:
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
Click to expand...
Click to collapse
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
LS.xD said:
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
Click to expand...
Click to collapse
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Morthawt said:
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Click to expand...
Click to collapse
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
LS.xD said:
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
Click to expand...
Click to collapse
I am on the latest CM11 snapshot Amazing! Although I am confused by some of the options. Is there any documentation on the OS? I see for Network modes things like "2G | 3G", or "2G | 2G + 3G" and "2G | 3G | 2G + 3G" . I pretty much can assume I know that 2G | 3G means 2 or 3G but when it comes to ones with +'s that is just confusing. 2G and 3G at the same time? No idea lol.
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Morthawt said:
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Click to expand...
Click to collapse
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
SlimKAT is a fast, lightweight rom and should be working.
LS.xD said:
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
Click to expand...
Click to collapse
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Morthawt said:
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Click to expand...
Click to collapse
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
LS.xD said:
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
Click to expand...
Click to collapse
Those exist in the TWRP zip format? Where can I find those?
Morthawt said:
Those exist in the TWRP zip format? Where can I find those?
Click to expand...
Click to collapse
I should have read before I answered Seems not to exist for your phone. I don't know the reason.
Good day everyone, especially to every great and talented android developer out there. Please be nice and give some patience in me, im a newbie. I don't intend to annoy anyone . I am here asking for help to anybody.
Device: Samsung Galaxy Tab 3 Lite SM-T110
1. I rooted it and flashed custom recovery(TWRP) following this thread. https://forum.xda-developers.com/showthread.php?t=2674649. It works fine. Reasons? To enhance battery life and give smooth performance especially in games. I have backup everything and put in my laptop.
2. I installed app remover/uninstaller from google play to remove unwanted system applications.
3. I installed custom kernel/ROM and flashed it in recovery mode. It failed, I reboot the device, and it tells "NO OS".
I follow instructions in this link https://forum.xda-developers.com/galaxy-tab-3/development-7/rom-i8200-build-t110-t3139478
4. I try to restore the back-up in recovery, but it failed. So, i downloaded the stock/official firmware.
5. I flashed stock recovery, then flashed the stock/official firmware of my device. It works again (No Root this time)
6. I am really curious about custom kernel/rom, so i reapeat 1-5. (3x)
7. The second time, i wonder why it failed to install the rom, so i go to recovery->wipe->format Data
8. This time, i know my device breaks. It keeps on rebooting and sometimes it stuck at startup.
9. I unbreak/softbreak it following no. 1 but nothing change, my device didn't start. It's stuck.
I think my device is now dead.
Any comments/suggestions is highly appreciated.
Thanks in advance.