I have a few questions:
1. Firmware and custom ROM difference. For example I have android LP but to upgrade to MM custom ROM I need to update my firmware which goes with bootloader and some other stuff for MM. Why is that and what's the difference?
2. When flashing a new ROM, if I wipe (TWRP) dalvik, system, cache, data and internal storage and ROM fails to install, everything is deleted including bootloader. Now it's obvious to me why but where is it stored exactly and what's the android OS storage hierarchy like?
3. Why can't I downgrade from let's say MM to LP directly by just deleting the MM and installing LP?
4. How can I avoid hard bricks because everytime I tried to flash a ROM on my zenfone 2 z00a I managed to hard brick it every time before finally installing it by following some step by step tutorial (I really want to know how to actually do it on my own), and it's a long process of unbricking
5. Are there any good sites that explain android system apart from reading the documentation on official site
Related
So, the situation is I have moto g xt1033 with :- unlocked bootloader, rooted, stock rom 4.4.4 kitkat (i mean no custom rom). and fastboot flash mode 41.13 2014-06-16 and philz touch 6 clockworkmod v6.0.4.7
I want to know how to update to lollipop with official OTA update (not manually or sideloaded)?
Why I am asking this?
I got the prompt of official OTA available on my phone and then i clicked yes and downloaded the update. But when i clicked on install, it went in bootloop. It boots on the philz recovery mode and then nothing happens just restart again whatever i select.
As of now, as I backed up, I recovered to the before state of the phone. Do I need to lock the bootloader again or what? The official OTA update is not for me? Then how to get lollipop? I read the soak test etc threads but why not official update ?
Locking the bootloader won't do anything,so don't lock it
Ota update requires:
1.Stock firmware(unmodified and unchanged or tampered)
2.unrooted
3.Stock recovery
That probably happend becuZ your KitKat firmware was modified and you have custom recovery,root..
So just reflash the stock firmware
Do that on your own risk as failing this might brick your phone
Thank me if I helped
Thanks mate for reply.
1. I have stock firmware KK 4.4.4 (though xposed framework & few modules are installed currently)
2. Rooted
3. What is stock recovery? (m noob here)
And i guess reflashing the stock firmware wipes out all user data & apps, right?
Any other alternative which does not wipes out my data?
instinctblade said:
Locking the bootloader won't do anything,so don't lock it
Ota update requires:
1.Stock firmware(unmodified and unchanged or tampered)
2.unrooted
3.Stock recovery
That probably happend becuZ your KitKat firmware was modified and you have custom recovery,root..
So just reflash the stock firmware
Do that on your own risk as failing this might brick your phone
Thank me if I helped
Click to expand...
Click to collapse
pr.itdude said:
Thanks mate for reply.
1. I have stock firmware KK 4.4.4 (though xposed framework & few modules are installed currently)
2. Rooted
3. What is stock recovery? (m noob here)
And i guess reflashing the stock firmware wipes out all user data & apps, right?
Any other alternative which does not wipes out my data?
Click to expand...
Click to collapse
Actually there is no other way you could do it
i tried everything i could to stop the wipe procedure but it obviously wiped everything
you just backup everything you have got on your internal and external sd card ..
1.Stock Recovery:: Android devices come with Google’s recovery environment, which is often referred to as the “stock recovery.” You can boot to the recovery system by pressing device-specific buttons as your phone or tablet boots or by issuing an adb command that boots your device to recovery mode. The recovery menu provides options to help recover your device — for example, you can reset your device to its factory default state from here. The recovery mode can also be used to flash OTA update files.
2.Custom Recovery::A custom recovery is a third-party recovery environment. Flashing this recovery environment onto your device replaces the default, stock recovery environment with a third-party, customized recovery environment. This is a bit like flashing a custom ROM like CyanogenMod — but, instead of replacing your device’s Android operating system, it replaces the recovery environment.
what you have to do is:
Find the Kitkat official update on the internet accrouding to your [Build number],[model number] [system version] you can get this information in about phone....
If you have asia retail then follow this method http://forum.xda-developers.com/showthread.php?t=2700502
ok Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
Hey,
I been trying different custom lollipop roms on my G3 but for some reason after I go into twrp and do a factor reset then install a different lollipop ROM it will start up with the screen saying android is updating like you if you would flash and update. I alos even tried doing format or delete everything option I twrp, and put a rom on my SD card and it did the same thing. Is there something I'm doing wrong or is that just normal?
Thanks
Multi part question here which, in my mind, are somewhat related.. I've read up on many posts but these questions I still am not totally clear on and would rather not risk bricking trying to experiment....
#1) When a nandroid is taken on a particular firmware (say 4.4.4) and then after upgrading firmware to a different firmware (say 5.0.2) and I encounter a problem where there is no OS left after wiping and failing to install a custom ROM (TWRP will report: no OS installed! are you sure you want to reboot?), can I flash restore the 4.4.4 nandroid and be ok or will I brick because of bootloader incompatibility [I come from motorola phones recently - this is my first HTC]?
#2) When adding additional ROMs to multiROM do the ROMs have to be of the same firmware version? Moreover, can multiROM have a sense ROM as it's primary ROM and a GPE ROM as a secondary ROM and vice versa?
( FYI - as of this posting I still have yet to successfully boot my secondary ROM using multiROM - I can successfully install mod'd TWRP, the manager, and the patched kernel but something is eluding me - anyone with a link to a very simplified and step by step procedure on installing mulitRoom would be appreciated. I thought I had enough understanding [of the procedures I could find anyways] but apparently not, as I obviously can not get secondary Rom to boot.) I'm able to add the ROM in TWRP but when I reboot, the ROM is not listed after pressing cancel and going to the multiROM boot screen, there is simply nothing there.
#3) Re: multirom - When I reboot into the mod'd TWRP recovery and flash gapps (or any zip file for that matter) how do I know which ROM the zip is being applied to (ie: primary or secondary)?
Feel free to answer as many or as few of the questions as I know it is a lot. Thanks in advance!
HTC one m8 verizon, rooted, s-off, BL unlocked,
Successfull flashes of Viper, Skydragon, FluentROM, Adrenaline2.4* (*current DD)
kerryh said:
Multi part question here which, in my mind, are somewhat related.. I've read up on many posts but these questions I still am not totally clear on and would rather not risk bricking trying to experiment....
#1) When a nandroid is taken on a particular firmware (say 4.4.4) and then after upgrading firmware to a different firmware (say 5.0.2) and I encounter a problem where there is no OS left after wiping and failing to install a custom ROM (TWRP will report: no OS installed! are you sure you want to reboot?), can I flash restore the 4.4.4 nandroid and be ok or will I brick because of bootloader incompatibility [I come from motorola phones recently - this is my first HTC]?
#2) When adding additional ROMs to multiROM do the ROMs have to be of the same firmware version? Moreover, can multiROM have a sense ROM as it's primary ROM and a GPE ROM as a secondary ROM and vice versa?
( FYI - as of this posting I still have yet to successfully boot my secondary ROM using multiROM - I can successfully install mod'd TWRP, the manager, and the patched kernel but something is eluding me - anyone with a link to a very simplified and step by step procedure on installing mulitRoom would be appreciated. I thought I had enough understanding [of the procedures I could find anyways] but apparently not, as I obviously can not get secondary Rom to boot.) I'm able to add the ROM in TWRP but when I reboot, the ROM is not listed after pressing cancel and going to the multiROM boot screen, there is simply nothing there.
#3) Re: multirom - When I reboot into the mod'd TWRP recovery and flash gapps (or any zip file for that matter) how do I know which ROM the zip is being applied to (ie: primary or secondary)?
Feel free to answer as many or as few of the questions as I know it is a lot. Thanks in advance!
HTC one m8 verizon, rooted, s-off, BL unlocked,
Successfull flashes of Viper, Skydragon, FluentROM, Adrenaline2.4* (*current DD)
Click to expand...
Click to collapse
You won't brick it.. softbrick/bootloop maybe.. but it's easy enough just to keep a copy of the different firmware zips to flash before restoring that version nandroid.
dottat said:
You won't brick it.. softbrick/bootloop maybe.. but it's easy enough just to keep a copy of the different firmware zips to flash before restoring that version nandroid.
Click to expand...
Click to collapse
Much oblige! I assume then what to do would be to NOT reboot to system but to BOOTLOADER and fastboot flash the zip? or would I flash the firmware from TWRP (I thought firmware had to be fastbootRUU flashed)?
thx again
Hey there.
So, my 6045 was on that awful MM update filled with ads, so I changed the firmware to the Panasonic one in order to be able to install TWRP and next flash either Lineage or RR.
I have no problem installing TWRP using the Idol 3 suite (Here), however, whenever I try to flash the Lineage zip, or the RR zip, it gets stuck on the Powered by Android screen.
I always wipe everything before flashing the zips.
I have tried wiping cache/dalvik after flashing them, and also not wiping. Either way, and with both roms, the phone gets stuck, and I need to use the Panasonic tool again to restore the phone to a functioning state.
Please help, I've been repeating this process about 10 times, and it's getting very frustrating.
Thanks.
EDIT: Is the version of TWRP somehow relevant for this? The latest version I can install is 3.0, from the link provided. If I try to install this one I get a bootloop. Please help.
Hi, u need to flash the MM partitons zip first then the rom . Look on AlekDev customs roms threads, he usualy has the MM partition file.
Hey there,
I found a J7 2015 (the Exynos variant) sitting in my dad's drawer. I decided to come here after a full day of trying to get Centaurus OS (from here) up and running but in vain. The reason why I am here and not on its official thread is that the official thread is closed.
After powering on the device and seeing the Samsung Logo, it is just a black screen from that point onwards. I am able to go into download mode or recovery and restore another OS, which is good, but Centaurus OS seemed fairly stable based on the feedback on the thread. I am able to get other ROMs running, including ones that are based on Android 7.1+.
Here is a summary of my attempts. I will try to not keep it long.
Method 1: Starting from Android 5.1.1 stock
Flashed TWRP 3.0.2
Factory Reset + Delete Data
Flash ROM and go through setup
Stuck on that black screen after restart
Method 2: Flashed Android 6.0.1 stock from SamFirmware.
Tried with either TWRP 3.0.2 or 3.3.1
Factory Reset
Flashed a ROM with Android 7.1
Factory Reset again
Flashed Centarius ROM
Stuck again on Boot
I have done variants of those methods multiple multiple times but nothing really worked out. I am certain I am using flashable files that are 100% designed for my phone model.
So here's what I am asking for:
Could anyone help me fix the issue? OR...
May I know of another fairly stable ROM for the J7 2015 that is based on Android 7 or higher?
Thanks a ton for passing by
Oops, this was too ridiculous on my side. It actually worked finally. Here's my setup and what I have done:
Setup:
TWRP 3.3.1 tar file Flashed via Odin
Boot into Recovery
Go to Wipe > Advanced Wipe
Check Data, Cache, SYSTEM, etc, but not External MicroSD Card and USB OTG
Back to TWRP main screen, Reboot > Recovery, ignore warning
Flash the Centarius ROM from the external MicroSD Card
Should work after reboot
After trying quite a bunch of ROMs, there's actually nothing that matches the stock ROM for our J7. Other ROMs, whether LineageOS based or based on some other ROM from another phone, are half done with minor, but annoying issues.
This is the stock ROM I used. He got a more recent version of Android Security Patches, but still quite old now. Use that one, or if you are security-paranoid, then consider switching to another phone.
https://forum.xda-developers.com/ga...-stock-custom-rom-debloated-deodexed-t3339816