I have:
Lenovo P1ma40 with last stock ROM (S040_170106_16G_ROW)
Root access
microSD card
stock recovery (but I cat flash TWRP 2.8.7.3)
So, is it possible to install some custom ROMs to sd card, without replacing stock firmware?
0x000000E2 said:
I have:
Lenovo P1ma40 with last stock ROM (S040_170106_16G_ROW)
Root access
microSD card
stock recovery (but I cat flash TWRP 2.8.7.3)
So, is it possible to install some custom ROMs to sd card, without replacing stock firmware?
Click to expand...
Click to collapse
Yes, it's possible, but the stuff to do it isn't available for all devices.
Some options are:
1) Safestrap recovery- this tool lets you keep the stock ROM and install custom ROMs inside Safestrap, then when you boot your device, you choose whether you want to boot stock or one of the custom ROMs. This is a dead project though, if you want it to support your device, you'll probably have to build a version of Safestrap for yourself so that it supports your device, then, if there are no custom ROMs available for your device, you'd have to build the custom ROMs for yourself also.
2) if you can flash TWRP and if there is a version of the Multi-ROM custom ROM for your model number, you can use it. Multi-ROM is a ROM that is built to boot different ROMs.
Sent from my LGL84VL using Tapatalk
Related
Hi there,
i'm a bit confused now. My Xoom (German Wi-Fi only, MZ604) should arrive this week and i wanna root it and flash the eos ics-nightly, but from what i've read, there are different root-methods for us and non-us devices and CWM-versions with and without sd-card support.
So, what mehtod is best for rooting? universar xoom root or xoot? and if xoot, what are the benefits of converting to an GDE-device? when rooted, i can flash every rom anayway, or am i wrong?
Second Question: When i root via universal xoom root, i'll have the taiamt recovery, right? so this will be the eos/tiamat recovery, which supports sd-cards? and can i use this CWM together with a regular installation of rom manager?
What about the rouge CWM? this one should also have sd-card support, right? can this also be used together with a regular rom manager or not?
The only thing i should avoid is flashing CWM via rom manager, correct?
Sorry for all the noobish questions, but this is quite different from the DHD handling
root via universal root(I prefer it)
http://forum.xda-developers.com/showthread.php?t=1242241
yup you will have the tiamat recovery
there are currently tow recoveries supported
1.) Rogue recovery
2.) solarnz recovery
I use the rogue recovery as it gives more options(ex flashing from internal sd card along with external)
but both are awesome
No you cannot use the recovery which comes with Rom Manager...
it does not detect the external sd , yup avoid flashing CWM with Rom manager
Advantages of GED device..
all i can say is that it receives update directly from google and the updates come alot faster
and you will have stock android ie no custom ui's like motoblur or so
thank you for the answer
so the work order will be root via universal root, flash the rouge recovery and flash the custom rom (and if needed flash google apps), correct?
GED isnt needed because aosp roms dont get updates from vendors or google.
Last question: should i install rom manager for nandroid management (if rom manager works with rouge cwm) or should i avoid rom manager at all and do backups directly through recovery?
thanks for the help
hello,
after reading almost everything i could read on the forums about the procedure of flashing roms, i'm left with a few questions that i couldn't find answers to, or i found more then one answer.I read all the following, and more:
1. [GUIDE] All-in-One Defy Beginner's guide by Zephyrot here: http://forum.xda-developers.com/showthread.php?t=1216982
2. [JB] CM10 Android 4.1.2 for the Defy(+) by Quarx here: http://forum.xda-developers.com/showthread.php?t=1768702
3. [GUIDE][KitKat][CM11] Updating to 4.4 by coolshahabaz here: http://forum.xda-developers.com/showthread.php?t=2568325
4. [Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+) by Quarx here: http://forum.xda-developers.com/showthread.php?t=2515036
5. http://forum.xda-developers.com/showthread.php?t=2597719
6. http://forum.xda-developers.com/showthread.php?t=2644812
7. http://forum.xda-developers.com/showpost.php?p=49558697&postcount=3
8. http://forum.xda-developers.com/showpost.php?p=49558744&postcount=4
My devicee is a Defy+ with Gingerbread 2.3.6. I found here: http://sbf.droid-developers.org/phone.php?device=28 "Android 2.3.6 Blur_Version.45.0.1610.MB526.Partner.en.IL" rom which is supposed to be my stock rom.
1. My main concern is always to keep the option to go back to stock rom. As i read here, this might be a problem with Defy+, but only if i flash SBF files, which i dont plan to. Is it correct that i will be able to flash the stock rom with RDS_lite, motorola drivers and bootloader (power up with VOL up) at any time?
questions about recovery:
2. I understand that i need TWRP 2.3.6 in order to flash new roms, and since recovery is protected in Defy, i must use 2nd_init to bypass stock recovery. Is 2nd_init include the custom recovery in it? if so, which one? and what version?
3. can i install CWM or TWRP without using 2nd_init?
4. What is rom_manager (for CWM) or goo.im (for TWRP) and do i really need them?
5. what is update_recovery.zip mentioned as part of the procedure here http://forum.xda-developers.com/showthread.php?t=2515036 does it update the custom recovery or the stock recovery? is it really needed since some of the procedures described above skip this step?
choosing a custom rom:
6. I'm looking for adnroid 4.4. what is the difference between this: http://forum.xda-developers.com/showthread.php?t=2597719 (AOSP Android 4.4 for the Defy(+)) and this http://forum.xda-developers.com/showthread.php?t=2515036 (CM11 Android 4.4 for the Defy(+))
7. If i want a as-close-as-possible to google original kitkat 4.4, which one should i use?
Thanks,
Roy.
I have some of the same questions you have... will follow this topic, hoping for some info! thx!
1. You can always go back to stock ROM using RSDLite. There is no such problem with the Defy+.
2. After rooting, install the 2ndinit app to install ClockworkMod recovery (which is now outdated). Then reboot, and flash this - http://forum.xda-developers.com/showpost.php?p=48501247&postcount=1250 in the recovery. This way you will get TWRP recovery required to flash newer ROMs such as 4.4.x ROMs.
3. The 2ndinit app installs custom recovery. This info is clearly given in Zephyrot's guide -
Here is where 2nd Init comes to play, this little awesome app kicks in right after the Bootloader and allows the Defy to load a different, non-Stock Android.
With this, you can also install a Custom Recovery, which runs from the Internal Memory, and is not ran from the Recovery Partition (remember: locked, not accessible) what does this means? That even screwing up your phone, deleting all your stuff, or screwing /system partition the phone can still get into Recovery, be recognized by RSD Lite in Bootloader Mode and be flashed with a Stock or modified Rom (more on this later) and it will come back to live normally.
Click to expand...
Click to collapse
4. You don't need them.
5. None of the recovery updates touch the stock recovery. The stock recovery is built-in, and due to the locked bootloader, it cannot be removed or modified. For 4.4.x ROMs, it is sufficient to follow step 2. This guide explains the steps for installing KitKat - http://forum.xda-developers.com/showthread.php?t=2568325.
6. The AOSP ROM is severely outdated, I recommend you to try SlimKat or CM. AOSP is pure android (stock android you find in Nexus devices).
7. Using CM or Slimkat is sufficient. Also there is no 'Best ROM'. It depends on the user's opinion and requirement.
hotdog125 said:
1. You can always go back to stock ROM using RSDLite. There is no such problem with the Defy+.
2. After rooting, install the 2ndinit app to install ClockworkMod recovery (which is now outdated). Then reboot, and flash this - http://forum.xda-developers.com/showpost.php?p=48501247&postcount=1250 in the recovery. This way you will get TWRP recovery required to flash newer ROMs such as 4.4.x ROMs.
3. The 2ndinit app installs custom recovery. This info is clearly given in Zephyrot's guide -
4. You don't need them.
5. None of the recovery updates touch the stock recovery. The stock recovery is built-in, and due to the locked bootloader, it cannot be removed or modified. For 4.4.x ROMs, it is sufficient to follow step 2. This guide explains the steps for installing KitKat - http://forum.xda-developers.com/showthread.php?t=2568325.
6. The AOSP ROM is severely outdated, I recommend you to try SlimKat or CM. AOSP is pure android (stock android you find in Nexus devices).
7. Using CM or Slimkat is sufficient. Also there is no 'Best ROM'. It depends on the user's opinion and requirement.
Click to expand...
Click to collapse
Many many thks!
Im trying to up to CM 11 from 2 months.Now Im on 10.0(4.1.2).Every try to update recovery with "update-recovery.zip" or TWRP 2.6.3.0 finished with bootloop or without custom recovery and balck screen.And them flash stock .sbf and start all from the begining.And try and try....In your guide it have link to update recovery.It have something about 30+ seconds waiting after TWRP update.So I try.
Hi it is the first time I am flashing Android ROM. I have done some reading already. Before I start, I still have a few questions and also want to make sure I am doing it right.
I own the Galaxy S4 Verizon I545. It is running Samsung ROM Android 4.4.2, Baseband I545VRUFNC5. My goal is to flash a new ROM with recent Android versions, hopefully 7.1.1 (but I would settle with Marshmallow if that is more stable), it can be close to AOSP, I don't need ROMs with extra features.
In my understanding, the bootloader is locked, it will only load signed kernels and recovery. And then the kernel would load the system. In order to flash the system, it is best to flash the recovery first with TWRP. TWRP is modded with loki hack so it would load with the locked bootloader.
So here are my questions:
1. Does it matter which firmware/baseband I am currently on? For some phones (LG G2) I heard newer firmware fixed the loki hack. Should I update to the latest Samsung rom or leave it at NC5?
2. I don't see many ROM posted for the i545, which one is the most recent and reasonable stable? The Cyanogen website is down, should I try LineageOS?
3. I see different instructions for flashing TWRP. Can I flash it with just Odin? Some instruction mentioned rooting the phone first with KingRoot or other root, and then use dd. Does the phone have to be rooted? (I prefer not to if it is not necessary)
4. If after I flashed recovery, it fails to boot into TWRP, what can I do to restore everything to default?
5. The kernel will be untouched in the process right? I am only flashing recovery and system ROM, and the kernel will work fine with the new system ROM?
Here are the step and software I plan to use:
0. reset the phone to factory
1. use Odin to flash TWRP 2.8.7
2. download a ROM compatible with I545 and place it on the phone
3. flash the system using TWRP
Any feedback would be appreciated.
PS: Also I have a LG G2 D801. I would flash that phone instead if it is easier. I just want to get started and learn some things along the way.
https://forum.xda-developers.com/galaxy-s4-verizon
Oh Sorry. Didn't notice there is another forum. Should I repost there?
Yes.
1. Yes, it does matter. As you said, newer firmwares have fixed the exploits which make the phone harder to hack.
2. Any ROM should support your phone. They are generally unified.
3. In the name of anything holy, do not root with KingRoot. If you want to root, then the only way to go is CF-Auto-Root.
Rooting is sometimes necessary because recovery won't always install with Odin.
4. Flash stock ROM.
5. Kernels are specific to ROMs. So no, the kernel won't be untouched.
I want to flash a custom ROM such as some CM 12 or any other stable on this Micromax Canvas Fire 2(A104)but I cant access the custom recovery some way.
I need a method to install the custom rom via some tool or maybe adb or something i.e basically from PC.is it possible to install custom rom by pc anyway?
I know stock rom can be flashed with SP Flash Tool but same is not possible for Custom Rom's, I guess.
Any help appreciated.
Hi Guys,
I have a N910F Device , so I have yesterday worked on Rooting the Rom and Install Custom Rom.
I have using a Tutorial from Saarliner Rom Devloper and his Rom N4Rom but after I have flashing TWRP over Odin and get in Odin and erase all and install Rom there were Bootloop.
After I have flashed Remix Rom Project or other Rom ever and ever the Same ever Bootloop
My Question what I have make wrong?
- Download Mode
-TWRP Recover flashing
- Erease all up to Point Micro SD
- Flashing New Rom
Isn´t Correct that?
I knowing from S2/S3/S4/S5
First Root stock Rom then TWRP then Custom Rom or was it right?
1. 910F is known to have an eMMC problem - read about it
2. when you flash an 910F it is advised to do it in a cool environment - no joke, get a fan to blow on it or something - because heat produce the damage from point 1
3. it looks ok what you did, but did you updated to the ROM required BL and Modem ? did you respected all the instructions? why don't you try to talk with the saarliner rom creator/developer?
To 1. isn´t present , because Stock Rom are working fine and without any Reboots or Errors.
To 2. yes it was very hot.
To 3. Yes i did and yes i have read it 2 times, so my Question is when I would like to install a Custom Rom, i must have a rooted Stock then Recovery TWRP flash then Custom Rom isn´t it?
Because the Way from Saarliner look like not complete, i can´t imagen that it work so in the Tutorials. The Developer self has a Broken N4.
bluedesire said:
Question is when I would like to install a Custom Rom, i must have a rooted Stock then Recovery TWRP flash then Custom Rom isn´t it?
Click to expand...
Click to collapse
Not obligatory to have a rooted stock. After flashing TWRP, you can root it also - my advice is to use Magisk for root.
Also as advice - if saarliner rom is not working, try some other rom. The snapdragon forum has some roms, both touchwiz based and AOSP.
I will try it out.