im new to xperia Z2
and i want to understand some concepts i been reading around
Rom
Boot
Recovery
STOCK FIRMWARES
its all for rooting phone but i want to understand what are they about and what they are doing
thanks in advance
A custom ROM is basically a different operating system for your smartphone / tablet. I's still Android, but the developer has included his own options/themes/settings. In short: A modified firmware. ROMs for the Z2 can be found here: http://forum.xda-developers.com/xperia-z2/#romList
Boot is when you boot you device I think You might be thinking of a bootloader. The bootloader loads the actual Android operating system. You can "unlock" your bootloader, witch let's you run modified firmware (witch is not based on stock firmware) on your device.
Recovery can be started before the actual boot process of the Android operating system by pressing a certain key combination. It contains reset options for the smartphone and also the option to clear the cache, provide a backup, restore, among a bunch of other useful features. With a custom recovery, you can also create or install new version of custom ROMs, by flashing zip files.
Stock Firmwares is a unmodified firmware, like the one your device was sold with. You should always have a stock firmware(can also be called a stock ROM) for your device on your computer, in case you get in a bootloop(where your phone boots and then shuts down again, and then turns on and so on). You can then flash the stock firmware and maybe resolve the problem. Stock firmwares can be found here: http://forum.xda-developers.com/showthread.php?t=2759934
Hope this explains
so let me check if i get this right
i need to have unlocked boot-loader if i want to flash my phone with custom Rom
OR
i can have custom recovery to be able to install custom Rom but from the phone it self
either way i must have unlocked boot-loader to be able to install the custom Rom by flashing the phone or by using custom recovery
am i getting this right?
@pharaon said:
so let me check if i get this right
i need to have unlocked boot-loader if i want to flash my phone with custom Rom
OR
i can have custom recovery to be able to install custom Rom but from the phone it self
either way i must have unlocked boot-loader to be able to install the custom Rom by flashing the phone or by using custom recovery
am i getting this right?
Click to expand...
Click to collapse
You can flash a custom rom with locked bootloader, but then the rom has to be based on stock firmware. Roms like Cyanogenmod, witch is not based on a stock firmware, requires unlocked bootloader.
Here is a Screenshot of the Rom "Existenz Y"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can see it says "based on stock" that means you can flash it with locked bootloader
Sent from my D6503 using XDA Free mobile app
right i got it now thank you
well i have lollipop 5.0.2 build 23.1.A.1.28
and i read some where it drain battery when the mobile data is on because the application on lollipop keep the connection on all the time so that person had to downgrade to kitkat
is that true?
if it's true then what would be the best Rom which wont drain battery when mobile data is on
@pharaon said:
right i got it now thank you
well i have lollipop 5.0.2 build 23.1.A.1.28
and i read some where it drain battery when the mobile data is on because the application on lollipop keep the connection on all the time so that person had to downgrade to kitkat
is that true?
if it's true then what would be the best Rom which wont drain battery when mobile data is on
Click to expand...
Click to collapse
Well, I have not heard that story, and neither have I experienced it. I can use my phone with mobile data activated for 2 days without charging (stamina mode activated). However, I am now using the eXistenz ROM (lollipop ROM: http://forum.xda-developers.com/xperia-z2/development/rom-existenz-y-1-0-0-preparing-thread-t3113649 KitKat ROM: http://forum.xda-developers.com/xpe...m-existenz-ultimate-1-0-5-light-dark-t2835196), witch automaticly deactivates mobile data when my phone connects to a wifi network, and then activates it again when I disconnect from the wifi network. The battery holds for a very long time with this ROM aswell.
You have to experiment, and experience for yourself what is best for your daily use of you phone
so if i want to install this Rom i do these steps
From Stock Sony Lollipop:
Backup your datas.
Reboot in recovery.
Flash the rom.
If something went wrong, do a fresh install.
but how to reboot in recover dos stock Rom have recovery
also what about Fresh installation:
LOCKED & UNLOCKED Bootloaders
Flash latest rootable Sony's rom with flashtool (http://forum.xda-developers.com/show....php?t=2162907)
Root
Install NUT dual recovery (http://forum.xda-developers.com/show....php?t=2261606) or the recovery of your choice.
Reboot in recovery, Wipe Data, Cache and Dalvik/ART Cache.
Flash the rom.
1- what is rootable Sony's rom
2-what dos he mean with Root
3-what is NUT dual recovery
4- will this steps make my phone boot-loader unlocked?
@pharaon said:
so if i want to install this Rom i do these steps
From Stock Sony Lollipop:
Backup your datas.
Reboot in recovery.
Flash the rom.
If something went wrong, do a fresh install.
but how to reboot in recover dos stock Rom have recovery
also what about Fresh installation:
LOCKED & UNLOCKED Bootloaders
Flash latest rootable Sony's rom with flashtool (http://forum.xda-developers.com/show....php?t=2162907)
Root
Install NUT dual recovery (http://forum.xda-developers.com/show....php?t=2261606) or the recovery of your choice.
Reboot in recovery, Wipe Data, Cache and Dalvik/ART Cache.
Flash the rom.
1- what is rootable Sony's rom
2-what dos he mean with Root
3-what is NUT dual recovery
4- will this steps make my phone boot-loader unlocked?
Click to expand...
Click to collapse
First, let me say sory for the slow reply, I was working
1. The latest rootable rom(or rootable firmware) is the last firmware you can root. At this time, root for Lollipop can only be done by downgrading to KitKat, root, install recovery and then flash either a Custom ROM, or a Lollipop zip file. So the latest rootable ROM for sony xperia z2 is now KitKat, buildnumber 17.1.2.A.0.314.
2. Root itself is just a user with elevated permissions, who can do anything to any file or folder in the system.
3. NUTS dual recovery is a set of two recoveries, TWRP and ClockworkMod. These are just two different recoveries, and can do pretty much the same, however someone likes TWRP over ClockworkmMod, and opposite. Stock ROM(Or Stock firmware) does NOT have recovery installed. To get recovery on Lollipop, you have to downgrade to KitKat, root, and install recovery.
4. No, this steps will NOT unlock your bootloader. To unlock your bootloader, you have to go to Sony's website, type in your device' IMEI, your email and get a code. Flashing a Custom ROM will NOT unlock your bootloader. (If you want to unlock your bootloader, here is the link to Sony's webisite: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/).
A fresh insallation is when you wipe all data, and your whole phone. (Pretty much a factory reset) and then flash the rom. The ClockworkMod recovery even has an option who says "Clean to install a New ROM." witch is a fresh installation
Stock firmwares for Lollipop and KitKat can be forund here: http://forum.xda-developers.com/showthread.php?t=2759934
Don't be afraid to ask if there are anything else you are curious about!
so now to installthe eXistenz ROM i'll do this steps
1-Backup My datas.
2-downgrading to KitKat.
3- Root
4- install recovery
5- and then flash the eXistenz ROM
or i wont need this steps and can flash the eXistenz ROM right away
@pharaon said:
so now to installthe eXistenz ROM i'll do this steps
1-Backup My datas.
2-downgrading to KitKat.
3- Root
4- install recovery
5- and then flash the eXistenz ROM
or i wont need this steps and can flash the eXistenz ROM right away
Click to expand...
Click to collapse
If you have recovery now, you can flash it right away, but if you do not have recovery, that is your steps!
Sent from my D6503 using XDA Free mobile app
how can i tell if i have recovery or not
@pharaon said:
how can i tell if i have recovery or not
Click to expand...
Click to collapse
Turn of your phone, and then boot it again, If it vibrates and the led lights up, you have recovery.
Sent from my D6503 using XDA Free mobile app
it did not
@pharaon said:
it did not
Click to expand...
Click to collapse
Then you do not have recovery
Sent from my D6503 using XDA Free mobile app
well i can't writ to my SD card
i can't save office files to it
i can't you use file commander to move files from internal memory to sd card
my camera make unknown error when i try to record video and select SD card as storage
how can i be able to writ to my sd card and save files to it
Use a PC or something similar (card reader, spare phone etc). Be careful though, make sure you don't wipe he system if you can't read the memory card, it's ok to factory reset, but if you wipe the system partition and you can't access the ROM files on your memory card from recovery, you won't be able to use your phone until you can get one that reads (or phone repaired). a factory reset option is all you need from recovery for most things though, so only "wipe to install a new rom" if your card definitely works! Worst comes to worst and something did happen, flashtool should have your back anyway
how can i let office get Editing access to files on SD Card
@pharaon said:
well i can't writ to my SD card
i can't save office files to it
i can't you use file commander to move files from internal memory to sd card
my camera make unknown error when i try to record video and select SD card as storage
how can i be able to writ to my sd card and save files to it
Click to expand...
Click to collapse
You have to be rooted. Then you download sdfix for kitkat (works on lollipop too) from play store, run it and you're done.
Sent from Xperia Z2
Luckily not from an iPhone = Yesterdays technology at tomorrows prices
Related
I tried following this:
http://forum.xda-developers.com/showthread.php?t=1580070
"INSTRUCTIONS" part:
* RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
* RECOVERY: Install Rom: Download
* RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
* RECOVERY: Wipe Cache Partition
* RECOVERY: Wipe Dalvik Cache
* Reboot and enjoy
Click to expand...
Click to collapse
did all the above, never forgot any of the 3 wipes/resets that were necessary.
used this rom file:
http://goo.im/devs/paranoidandroid/roms/i9100g
(latest one)
for my Galaxy Samsung S II GT-i9100g.
I had CWM and also had a rooted android 2.3.
first boot it showed me the normal samsung boot screen, for 45 minutes....
so I restarted and the phone gave me the same behaviour..
so I removed the battery to turn off the phone, and attempted to reinstall the whole thing, going through this process again from scratch
not forgetting any of the wipes etc...
now every time I boot it, it leads me to CWM instead of the normal boot screen and the expected paranoid rom eventually...
I followed this path because CM 10 failed me because upgrading from 2.3 to 4.x requires going through something that is called "stock" or as I think it actually is - google's /manufacturer's original firmware/rom production line thingy
and after that it needs me to re-enable root on that stock rom all over again. And only then I may attempt to install CM10...
so I picked paranoid instead, because in it's instructions is showed me no such constraint. heck it can't give me that constraint because there is no "stock" of android 3.x for smartphones
but then this issue happened... so I need your help.
I found similar search results but couldn't figure out their solutions or how whatever triggered that same problem (which isn't mentioned in those threads) is related to what I did to my phone... (so that I will not repeat the same mistake)
your help is much appreciated as I need it so so much!
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
gastonw said:
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
Click to expand...
Click to collapse
by "flash"ing you mean the option "install from a zip file" in CWM in recovery mod?
if I have some rom, the only way for me to install another would always be by going through that middle step of also installing a 'stock' rom as well?
there is no way around it?
installing a 'stock' rom, wouldn't it make me loose my root I have on the phone and force me to root it all over again before I can continue install anything at all?
thats the reason I wanted to try out the paranoid way of doing this instead of the CM10, because I have no interest in rooting my already rooted phone and I hoped that paranoid does not need me to go to stock first....
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
some questions
ONE QUICK IMPORTANT QUESTION BEFORE THE REST:
If I use mobile odin, will I be able to use it to install stock rom and also root it at the same time?
SECOND IMPORTANT QUESTION:
you said I could flash whatever I want and still have root, but my problem was not 'not having root', it was not having the flash process complete successfully... how do I attack that?
THIRD IMPORTANT... info... :
My "BUILD" version is "GINGERBREAD.XXKL5", isn't that a 'stock' one?
If you don't have a lot of time,
then the rest of this post is not as important as the 2 questions above...
gastonw said:
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
Click to expand...
Click to collapse
the saddest part is that I couldn't figure out most of what you just said
what is 'nandroid'? 'flashing'? do you mean like dd in linux? copying to the entire flash storage device?
'IMEI'? huh..? O_O
at the moment I was able to 'get back on my feet', I restored everything back to normal with manual copying of important parts of the CWM corrupted backup from this week, and old stuff for a CWM backup made few months ago.
now that I am at a 'normal' state.. I want to install paranoid or CM10 on my GT-I9100g.
which one of those 2 does not force me going through installing stock?
I have this fear of installing stock that it will take away my root and that I will have to use adb from command line to re-enable root afterwards, which I have bad experience with.
I need to know a few things before I attempt to install stock via CWM,
will installing stock disable my root? will installing stock disable my ability to load recovery boot menu CWM?
is 'root' an attribute or state that belongs to the running rom itself after boot has been completed and to that only?
or does it also belong to the state the device is at while in the recovery boot menu CWM ?
I tried messing around with ADB in the past to see if I could root devices via that way but it wasn't very successful so thats why I'm afraid of having to attempt it again.
bumpitybump
even though a year later, I would still love some replies
resurrecting my motivation to do this once again.
copy paste from my other post;
before flashing, you will need these;
-stock rom (get it from Sammobile, sign in and select your country and phone model)
-blazing kernel for recovery (search in XDA)
-custom rom (CM, PA, Supernexus...your choice)
-backup your data
-GApps (get the latest one)
-you must know what are you doing and dont flame/blame other member if something wrong
how to flash;
-make sure you are on latest stock rom (mine is JellyBean 4.1.2), if not like the OP, flash the latest stock rom using Odin;
*reboot your phone in Download Mode
*open Odin and in PDA option select your stock rom and then Start
*if done it will display Done and disconnect your phone, it will boot up
*if bootloop, reboot into Recovery Mode, and then wipe data and cache, and then reboot normally
-after updating your phone to latest stock rom, copy your custom rom, GApps, and Blazing kernel into external SD card, then reboot into Recovery Mode
-choose "apply update from external storage" and choose Blazing kernel, wait for it to finish update
-reboot normally, and then reboot back to Recovery Mode. this time you will notice that your recovery is different from the previous one
-select install zip > choose from external storage/sdcard 1 > and then choose your custom rom. then wait for it to finish update
-repeat the above step to install GApps, and after that reboot normally
-if bootloop, reboot back to Recovery Mode and then wipe data, cache and dalvik and then reboot
-done, now you are running on custom rom
Click to expand...
Click to collapse
and about the root, i believe that almost all custom rom rooted
(Sorry if you guys don't like me using the term soft brick :S)
Phone version: Samsung Galaxy S II I9100
Problem: Rooted phone using [galaxys2root's method] (Odin + Jeboo Kernel + Clockworkmod) and then installed CyanogenMod using [WiredMash's method] (sorry can't post youtube links)
Followed the procedure and everything was working perfectly. Afterwards, I messed a few settings up so I thought it would be easy to simply do the process above again to start with a clean slate.
I don't particularly remember the order in which I messed things up, but I went back to Clockworkmod, cleared literally everything (including the internal SD, meaning I lost CyanogenMod) and then went back to Odin and tried to flash Jeboo Kernal on again.
Current Status of Phone:
Stuck at the Loading Screen with the Yellow Exclamation Mark.
Downloading mode states I've done Binary Flash 8 times (woops)
CyanogenMod no longer initiates.
Still able to access CWM, but can't flash any Zips on because there's nothing on the memory
What should I do? Would this simply be fixed by popping down to the store to grab a MicroSD and going on my computer, putting CyanogenMod on it and then flashing it using CWM?
If it works, would I have screwed up anything? Would I have to clear some stuff using CWM? Would it be like nothing happened? (I have a weird obsession that requires everything to be perfect)
Ok....it's not *really* a brick....it's not even a bootloop.....it's (as you said) a lack of os.
You have an accessible CWM, which basically puts you in the clear.
You suggested your solution.....buying a microSD card, copying a rom to it and using cwm to flash it.
I basically was in the same situation as you, and if I'd had a microSD card that my laptop recognised, that is the solution I'd have used. My issue was that my XP laptop doesn't like high capacity memory cards (mine is 32Gb)....if you are running XP, it might be a good idea to get a (maximum) 4Gb card.
The above method will also require you to flash GApps as well......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
No need to buy an external sd-card. Your phone has an internal storage which can be accessed / mounted via CWM. Just boot the phone in recovery mode (ClockworkMod) and head over to 'mounts and storage > mount USB storage'. Now use your cable to connect your device to your computer. It should only take a few seconds until your phone pops up in Windows Explorer. Then you're able to put your ROM .zip file onto the card. Choose to 'unmount USB storage' and install the ROM. Don't forget to wipe before Much luck,
experience7
Dude...you learn something new every day.....if I'd have known that when I had my issue (similar to the OP) I wouldn't have had to f**t around with odin installing a firmware in order to get at least *something* back on my phone to get it to boot again.....thanks for the share....gonna have to remember this tip
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
No, always go stock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from...this is not even my S2
Why should he go to stock if he desires his phone to run a custom ROM? Sounds like he accidentally formatted the system partition plus the internal storage. As soon as he flashes the CM zip file his phone has a working system directory and he should be able to. boot it up again
I was trolling keith.
Sent from...this is not even my S2
I guess the only reason for your inappropriate posts is to push your post count to its limit. Well done, sir.
That's so funny, why would anyone do that?
I want you to tell me, you got 2 min to make something up.
Be creative.
Sent from...this is not even my S2
Off-topic, 'nuff said. Now stop it please
Thought so
Be good now.
Sent from...this is not even my S2
experience7 said:
No need to buy an external sd-card. Your phone has an internal storage which can be accessed / mounted via CWM. Just boot the phone in recovery mode (ClockworkMod) and head over to 'mounts and storage > mount USB storage'. Now use your cable to connect your device to your computer. It should only take a few seconds until your phone pops up in Windows Explorer. Then you're able to put your ROM .zip file onto the card. Choose to 'unmount USB storage' and install the ROM. Don't forget to wipe before Much luck,
experience7
Click to expand...
Click to collapse
So I''ve done the USB storage method, shoving CyanogenMod, SuperSU and GApps onto the internal. I installed SuperSU and now I'm trying to install CyanogenMod and I'm getting the (Status 7, Installation Aborted) message. Am I missing anything required?
Re download the ROM, the files might be corrupted.
Sent from...this is not even my S2
No need to copy over SuperSU. There's a superuser app coming with CM Alternatives are in Google Play Store
Well, you're running Jeboo kernel. Stock based kernels sometimes cause errors when you try to install a custom ROM. Don't get me wrong, CM comes with its own kernel anyways, but there's still the chance that the installation fails like in your case. To solve your problem flash a custom kernel (I'd choose dorimanx - you can grab a copy here: dorimanx.shine.sk <- 8.x is for stock based ROMs, 9.x is for custom ROMs) So pick 9.35 and flash it. Then reboot the phone in recovery mode again. You've got a different Recovery system now. This time it will allow you to install CM followed by GApps
Edit: Don't forget that Dorimanx will be overwritten by CM kernel as soon as you flash CM. But if you're new to CM I recommend this kernel anyways
experience7 said:
No need to copy over SuperSU. There's a superuser app coming with CM Alternatives are in Google Play Store
Well, you're running Jeboo kernel. Stock based kernels sometimes cause errors when you try to install a custom ROM. Don't get me wrong, CM comes with its own kernel anyways, but there's still the chance that the installation fails like in your case. To solve your problem flash a custom kernel (I'd choose dorimanx - you can grab a copy here: dorimanx.shine.sk <- 8.x is for stock based ROMs, 9.x is for custom ROMs) So pick 9.35 and flash it. Then reboot the phone in recovery mode again. You've got a different Recovery system now. This time it will allow you to install CM followed by GApps
Edit: Don't forget that Dorimanx will be overwritten by CM kernel as soon as you flash CM. But if you're new to CM I recommend this kernel anyways
Click to expand...
Click to collapse
Hmm I seem to be getting the Status 7, Installation aborted problem with Dorimanx too :S I even tried 9.34 and redownloading 9.35
EDIT: Managed to get back to CyanogenMod. Thank you
Nice one mate. ...now if you want to go back to stock there's a handy little app called Mobile Odin. ...look for the thread here on XDA......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Hi so after updating from the stock zv6 to lollipop update my phone won't install a custom ROM. Every time I try to turn it on it goes straight to TWRP and went I install a ROM or try to load a backup as soon as I hit reboot it goes back to the TWRP page. Amy ideas?
You must flash back, using Flashtool, to zv4, then reroot, then flash newest TWRP. OTA software not included, because they flash every partition of the phone, including the boot loader. Stock roms like zv6 and zv8(lollipop)or AOSP, must be flashed from xda from here on out, because they've been modified to work correctly on zv4 boot loader. TWRP and root access only work correctly with zv4 boot loader.
sent from my LG G3
It sounds like there is no OS installed or it is stuck a reboot-loop. Try pulling the battery out for 10 seconds and if it still goes into twrp you know that it isn't a reboot-loop. When you go to restore a rom and it has the bar that shows the amount of storage does it say "0 MB"? If it does it means that twrp can't mount the storage on the phone thus causing it to not install/reboot. Have you tried side loading a rom via adb? Are you trying to install a rom off of a sdcard? I have seen many issues in the past sdcard related.
If you can please answer the following:
1) What is the message you are getting from twrp (if there is any)?
2) Have you installed a custom kernel and if so witch one?
3) What twrp are you running (the bumped one from xda or from the official twrp site) and what version is it?
4) Have you tried adb and pulling the battery?
If you answer these questions they should be able to tell us all that we need to know in order to help you out.
I have a moto e xt1021 (single sim) on kitkat 4.4.4 and I want to upgrade it to Lollipop AOSP 5.1.
So far, there have been no OTA updates to lollipop.
I've heard that lollipop has a different bootloader to kitkat, so i'm unsure if i can simply flash a lollipop rom.
Is there any way I can get lollipop on my phone?
If not, i'll just have to wait for the OTA update (if it ever happens).
Also, do rooted phones still get updates? Mine is rooted, but it's on stock rom with xposed framework.
Thanks.
bump
blazboi said:
I have a moto e xt1021 (single sim) on kitkat 4.4.4 and I want to upgrade it to Lollipop AOSP 5.1.
So far, there have been no OTA updates to lollipop.
I've heard that lollipop has a different bootloader to kitkat, so i'm unsure if i can simply flash a lollipop rom.
Is there any way I can get lollipop on my phone?
If not, i'll just have to wait for the OTA update (if it ever happens).
Also, do rooted phones still get updates? Mine is rooted, but it's on stock rom with xposed framework.
Thanks.
Click to expand...
Click to collapse
If you think you are quite comfortable with the fact that you are responsible for anything that happens to your phone, then I would suggest you to do the following things :
1) First of all unlock the bootloader (You'll find how-to's HERE)
2) Now install a custom recovery (TWRP 2.8.7 is preferred, Google it)
3) Make a full backup (System, Data, Cache, Boot) of your phone
4) Wipe everything (EXCLUDING YOUR SD CARD)
5) Go to the AOSP 5.1.1 thread, download the ROM
6) Download the GAPPS from HERE
7) Put these into the SD Card and boot your phone to TWRP
8) Install the ROM and GAPPS
OPTIONAL : You may want to install Super SU to have root access.
The first boot of the ROM takes a good 10 mins, so be patient.
Hope these hep u out... Cheers
Rohitagni said:
If you think you are quite comfortable with the fact that you are responsible for anything that happens to your phone, then I would suggest you to do the following things :
1) First of all unlock the bootloader (You'll find how-to's HERE)
2) Now install a custom recovery (TWRP 2.8.7 is preferred, Google it)
3) Make a full backup (System, Data, Cache, Boot) of your phone
4) Wipe everything (EXCLUDING YOUR SD CARD)
5) Go to the AOSP 5.1.1 thread, download the ROM
6) Download the GAPPS from HERE
7) Put these into the SD Card and boot your phone to TWRP
8) Install the ROM and GAPPS
OPTIONAL : You may want to install Super SU to have root access.
The first boot of the ROM takes a good 10 mins, so be patient.
Hope these hep u out... Cheers
Click to expand...
Click to collapse
Thanks.
Does lollipop use up a lot of the moto e's internal storage?
Also, how is battery life and performance?
Hello.
I am currently trying to bring my Samsung Galaxy SII (GT-I9100) to a current CM version. The phone is completely untouched and has never had any custom upload or anything similar.
The problem now is, while there are loads and loads of guides out there, all of them seem very old - and different. One says i need heimdall, other says odin, others seem way easier just adding the files to my SD card and installing through recovery - and basically all that does is confusing the hell out of me.
So, first things first - the most important thing seems to get root access - i've done that successfully using the "How To Root Samsung Galaxy SII GT-I9100"
The one thing that confuses me now is - where is CWM? I thought i installed it using that root method?
Another method i tried before updated my recovery while it was running from the stock one to CWM - but after rebooting into recovery it was the stock one again.
SO i am even more confused now as before.. At least i hope that my phone is and stays rooted, so that is a plus.
The question now is, what am i missing?
Were all of these CWM things i've "installed" just temporary? Where do i get the full version, and how do i install it?
Basically what i'm asking is, is there a current guide for all of the flashing? Can anyone maybe guide me through it? I mean, nowadays it seems the S2 should be flashed very easily, and i'm guessing it's just getting the correct CWM version and flashing it via recovery - but since i'm not sure, i'm asking for some guidance.
The easiest way to get a CWM custom recovery is to flash PhilZ recovery through your standard stock 3e recovery.
Look for your Android build number (under settings>>about device/phone) then go to the PhilZ thread......
http://forum.xda-developers.com/showthread.php?t=1877270
download the matching kernel/recovery zip (NOT .tar), copy to a micro SD card (or possibly even internal storage I can't be sure of that....It's been a while since I rooted my S2), boot into recovery and flash......
Simple as......
Edit....The thread states 'external sd card' so forget about using internal storage......
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks a lot, worked flawlessly!
I hope it is okay that i just ask about the next steps here.. Since i immediately ran into new problems.
So, i booted into the CWM and tried to push my cm package that i want to install via mfastboot-v2 and it failed stating the following errors:
Warning: No file_contextdetected filesystem ext4 for /dev/block/mmcblk0p9
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
It seems obvious ofcourse that i need to do a factory reset before, but the S2 is probably susceptible to a superbrick and i should not do that factory reset on my stock rom.
The question is - what now? Also i was not able to mound the external SD card in CWM.
ThePatchelist said:
Thanks a lot, worked flawlessly!
I hope it is okay that i just ask about the next steps here.. Since i immediately ran into new problems.
So, i booted into the CWM and tried to push my cm package that i want to install via mfastboot-v2 and it failed stating the following errors:
Warning: No file_contextdetected filesystem ext4 for /dev/block/mmcblk0p9
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
It seems obvious ofcourse that i need to do a factory reset before, but the S2 is probably susceptible to a superbrick and i should not do that factory reset on my stock rom.
The question is - what now? Also i was not able to mound the external SD card in CWM.
Click to expand...
Click to collapse
1) I can't comment on mfastboot v2 as I have no experience of using it.
2) which CM package are you trying to install?
3) the super brick bug only affects android 4.0.4 Icecream Sandwich....
And PhilZ kernels have removed/patched the EMMC_cap_erase command that activates the 'bug' anyway.
4) if your CM package came from XDA or the CM website, then it should install through PhilZ recovery.
5) what are you trying to achieve that requires external SD to be mounted?
The cm i'm trying to install is the latest stable one, being cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100
About the superbrick, i did not know that the philZ kernels fixed that, good to know.
And i tried to simply put the ROM image onto the external SD card to simply flash it from the CWM - but since that external SD card cannot be mounted, i tried using the adb push method.
Could i use the internal storage and simply apply update from zip file from there? Thought that might be an issue due to it being erased in the process?
CM 12 is lollipop base isn't it? The last CM I flashed to my S2 was 11.....but then my eldest son asked me for a phone so I returned it to stock and loaned it to him.
Obviously haven't been able to flash it since.
As for CM12, I've read that overall, it's not as stable as 11 (contains more bugs) and is heavier on the battery. I'm sure I've also read that the S2s memory partitions have to be re - mapped @gsstudios maybe you can help here as I'm not sure)
As far as I am aware, installing the rom from internal storage shouldn't be an issue......The only time data on that partition is compromised is if you perform a factory reset....and you would only have to do this (if at all) AFTER you have installed the rom. I'm also fairly sure that you have to have a specific version of CWM installed to be able to install newer CM roms, but again, I'd have to suggest waiting for @gsstudios to comment here......
ThePatchelist said:
The cm i'm trying to install is the latest stable one, being cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100
About the superbrick, i did not know that the philZ kernels fixed that, good to know.
And i tried to simply put the ROM image onto the external SD card to simply flash it from the CWM - but since that external SD card cannot be mounted, i tried using the adb push method.
Could i use the internal storage and simply apply update from zip file from there? Thought that might be an issue due to it being erased in the process?
Click to expand...
Click to collapse
Hi,
There are a few points I will give:
- cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100 is an old build of CM12.1. It doesn't have all of the latest features like Isorec (isolated recovery for TWRP 3 recovery support), hence it should be avoided. Instead, use CM12.1 Unofficial by CNBLACK or CM12.1 Unofficial by Markox89. Although they are unofficial builds, these are considered more stable than the CM12.1 snapshot build being offered.
- You can install CM12.1 via internal storage. It won't get erased during the flashing process, instead, this only happens when you re-partition your phone using a .pit file. You will need to increase you system partition size in order to flash gapps (google play store, etc) using Lanchon's repit tool. Documentation is already provided.
- Once you've installed CM12.1, it is recommended to change the recovery to TWRP (preferred) or CWM. This is because CM recovery is very limited and will become a problem later if you decide to flash CM13.
gsstudios
Hey there again.
First of all, thank you very much! I successfully flashed one of the cm's you posted @gsstudios and so far it works.
Now though i am struggling with the TWRP installation since i have to increase the partition size for gapps.. As i've read it TWRP must be flashed via heimdall (back to square one..) and there i am having problems with the connection (claiming interface error, was googling for 2 hours now, nothing helped)
Basically what i am now looking for is a way to get TWRP without having to flash via heimdall, but rather installing it through the cm recovery which seems not possible?
I am really sorry that i continue to post my issues here since i'm sure you guys helping out are really annoyed by this.. But currently i am again running my head into a brick wall not knowing how to proceed :/
Edit: jesus..
I have no idea how or why, but apparently i got it now.
I installed ROM manager externally and it showed me that i have CWM and TWRP already installed.. At first i was confused and set up TWRP as my recovery, but that only booted into the normal cm recovery. Then i tried the CWM one and when going into recovery i am now in TWRP.. Am reformatting my partitions, so far without any errors.
I am not less confused but close to being happy. As soon as i can flash gapps afterwards all of this is over and done.
Thanks still, for all the help guys! And sorry for being the usual annyoing user..
No problem fella....but in future, STAY AWAY from rom manager.....It sometimes doesn't play nice with the S2.
In the past I've read that it can 'fubar' recovery and can cause boot loops. (So up til now, you've been lucky).
For further info, Heimdall simply isn't needed.....The primary method of TWRP installation is via Odin. I'm a bit concerned that rom manager said you have both CWM and TWRP installed....Some investigation is in order....
Whichever recovery you boot into with the button combination is the recovery you have installed.....