I recently purchased a Nexus 6 running PureNexus 6.0.
I have tried to update to 6.0.1 without any success. I have downloaded the 6.0.1 update including the gapps file. I have booted into recovery mode using Teamwin. I have wiped delvik and cache and then selecting the zip files, I swipe install and reboot. The phone does not update. I am still on 6.0. Hoping that some can provide me some clear information on what i am do wrong and how to correctly update my phone.
Thank you in advance
Alex
If this pure nexus you mentioned is a custom rom, yes you can not update it with original rom update. You need custom rom update which generally rom developer prepares as a full stand alone rom, not update. But if you're talking about original factory rom, this time you need to flash all 6.0.1 rom because you have custom recovery so the update itself will not work.
But above all, which I get confused, what is this update zip you are speaking of ?
Related
here's what i did: i installed Microkat on a XT1068 with 48.86 bootloader, i formated my internal storage and my micro SD a day after. Today i was looking for a 5.1 ROM and i found a new SlimLP update, so i wanted to install it, and i did. The ROM booted up but there was something wrong, the wallpaper was the same i used on Microkat ( i did a clean install ), the launcher was Nova Launcher, the same launcher MicroKat uses, and some of my old apps where there, i don't know how it happened. So android.acore was FCing, so i went to TWRP and formated everyrhing and installed the ROM again. The rom doesn't booted up anymore, and i don't have a PC to save my phone, there is any way to save it without a PC? I know why it happened (its because i installed a Stock KK rom and then an AOSP 5.1 ROM, i already faced this issue, but now i don't have a backup or a Stock 5.0.2 zip file to install and free me out of this bug). Please if there's any way to do that without a PC tell me
Sent from my GT-i9506 using XDA Free mobile app
You'll have to restore stock 4.4.4, OTA update to 5.0.2, and then install custom 5.1.1 ROM.
You'll also need to make sure you update the bootloader, if you haven't done so already.
Just wipe system cache data and dalvik cache and then flash. No need of again flashing 5.0.2 and all that.
Sent from my Moto G 2014 using Tapatalk
Hello guys! How are you?
I'm having some bugs with CyanogenMod 12.1 in my MotoG and haven't found nothing that could help me with my problem.
Well, here's the story:
My device had Android KitKat 4.4 as the stock rom and I updated it to Lollipop 5.0 before rooting.
Well, I unlocked the bootloader and used TWRP as a custom recovery and installed SuperSU.
I've been using the phone about almost 8 months after rooting and then, Motorola released an update, I tried to update it via OTA and, of course, it didn't worked since TWRP can't OTA. Nothing changed in my phone, I simply rebooted it and it worked but since a few days some apps started to suddenly close and/or stop.
I decided to install CyanogenMod 12.1, downloaded the latest nightly and a stock package of GApps and flashed them via TWRP.
Wiped Dalvik Cache, Data, Cache and System
At the first attempt, TWRP rebooted after flashing CM12.1 and I wiped the caches via WIPE menu before flashing GApps wich couldn't be installed because there was "no space in storage". Well, I booted my phone normally (running cm12) and downloaded a Micro GApps package and flashed it sucessfully.
Problem is: Clock stops working (it has stopped for now), I can't install some apps from PlayStore such as Facebook, etc and my phone appears to be unrooted.
I think my TWRP is bugged or something cause it does not works as tutorials, etc tells...It shows some errors and sometimes reboots itself after flashing some file.
Do you guys think I should reset everything and then redo all the steps to use CyanogenMod properly? I really liked this custom rom but I'm afraid there will be more bugs in the future....
Anyone?
my solution..
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.
sagar846 said:
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.
Click to expand...
Click to collapse
This is exactly what you should do.
There are several things that don't work as they supposed to do, so follow the steps @sagar846 mentioned.
Sent from somewhere
Oniganon said:
Anyone?
Click to expand...
Click to collapse
cm 12 and 12.1 have some little bugs still but it is useable for daily use
Hi dear developers,
I just got my new Galaxy Tab S2, T813. Updated it to Nougat, firmware T813XXU2BQD1_T813OXA2BQD1_DBT. I rooted it via Chainfire's autoroot and worked perfectly fine. I installed the latest TWRP (twrp-3.1.1-1-gts210vewifi), advance wiped in twrp (like tens of times before with Galaxy S5, Galaxy S7, Redmi 4, ZUK Z2, Xiaomi Mi 5s, LG G2 etc.). I flashed Lineage 14.1 (Lineage-14.1-20170516-nightly-gts210vewifi) but when I rebooted the phone Lineage setup would not start. I went back and advance wiped again and installed an older Lineage version but again the same. I advance wiped again and installed Omni (Omni-7.1.2-20170521-gts210vewifi-weekly), but here again setup would not start. I reformatted the data in twrp and reinstalled Lineage 14.1 but again the same. So I went back and flashed via Odin3_v3.12.3 the stock firmware (for Germany) T813XXU2BQD1_T813OXA2BQD1_DBT. Odin command was pass and i though everything was fine. When the original firmware rebooted i have the same problem, the setup would not start and starting apps would crash. I entered recovery (of course stock recovery because twrp has been wiped by odin), but it says "no command".
Smart Switch would not support my device although it actually should.
I tried to flash via odin also on my second PC but again the same problem. Both PCs are running Windows 10.
I never faced something like this before. And after hours of search I found nothing. Please help me solve my problem so that i can install at least one firmware (no matter which one: Stock, Lineage, Omni etc.).
When you flashed lineageOS or omni rom, did you also flash gapps?
musashiken said:
When you flashed lineageOS or omni rom, did you also flash gapps?
Click to expand...
Click to collapse
First time flash:
+ clean advanced wipe
+ lineage
+ gapps (ARM64, Android 7.1, Pico)
+ addonSU
other times flash:
+ clean advanced wipe
+ lineage
or
+ clean advanced wipe
+ omni
I believe either flashing Chainfire Autoroot file or flashing TWRP might have caused the problem and might have deleted something or maybe i deleted something during first time wipe via twrp.
Is there a patch or aboot or something to flash via Odin prior to flashing the stock firmware to correct the problem with stock rom setup blockade?
Ok, I'm not sure what went wrong with how you did stuff but let's not use Chainfire's autoroot again. The best way to root is to do it manually.
Anyway, firstly you should be able to go back to stock samsung firmware by using Odin and flashing the full tar file. I'm not sure why that is not working for you as that's the only way to reset and fix your tablet.
Please check how to flash the full firmware via Odin again.
- ensure you downloaded the correct nougat firmware file. Latest LineageOS should require the EU version of the nougat firmware. I think it is T813XXU2BQD3. Not the firmware you used.
Once you are able to load a fresh samsung firmware, then come back again. I'll see if I can guide you through the TWRP and rooting process again.
musashiken said:
ensure you downloaded the correct nougat firmware file. Latest LineageOS should require the EU version of the nougat firmware. I think it is T813XXU2BQD3. Not the firmware you used.
Click to expand...
Click to collapse
Thanks fo the tip with the new version of firmware. I installed the firmware ...QD3 via Odin...
Closed per OP request
Hello all,
Firstly I would like to thank all the great people here, I've been struggling for hours with my dead Xperia Z and the amount of dedication and support I've found so far across all the members here is really impressing.
Let me first illustrate my case.
Firstly, I came here to root my phone and install a custom rom ships with Android N 7.1.2 (Resurrection Remix), I did went through all the newbies/how to threads and I did successfully ended up with Android N on my phone
Unfortunately, the device was not working probably in case of incoming or outgoing calls. No ringtone (already selected from Settings >Sound - played and heared), while in call it keeps ending the call unexpectedly, sometimes it feels very laggy that I couldn't even tap on anything. So I decided to give up until I found another rom that ships with Android N (XOSP), after successfully installing the rom, it starts out very smooth and I tested everything and it was ok, until yesterday the same issue still persists plus my device mic is not working no one can hear me while I'm talking neither from a headset mic nor the device mic. Finally I gave up and decided to rollback to the old lolipop stock rom.
Here's comes the current problem:-
1- I did flash 10.7.A.0.222 Customized MEA using flash tool and it's flashed successfully.
2- I'm now stuck with a dead black screen after sony logo.
I tried everything, changed the flashtool version, downloaded other ftf kernel file, used Xperia Companion and non of them worked for me. I did also tried what's listed in here https://forum.xda-developers.com/xperia-z/general/disaster-recovery-getting-z1-zu-z-zl-to-t2229250
I only can boot into fastboot or flashboot mode
I cannot copy files to my phone as it never appears as a storage media in my computer.
Any help will be much appreciated
Sorry for the long post
I never had this problem before, but have you try other ftf with lower android version like KK?
I see this problem on someone, everyone of them had this problem when they try to revert back to stock LP from N. Then someone suggest to flash KK ftf. You should try this if you haven't try this.
Sorry if my English is bad.
UPDATE:
when the first 7.0 nougat custom rom came, I'm on 5.1.1 rom with XZDual recovery. I made a backup for this rom and flash the 7.0 N rom only for trial then revert back to stock 5.1.1 that I backup before. Chippa's rom always came with latest built-in recovery so when I upgrade to nougat rom the XZDual recovery also lost (I don't have FOTA recovery, lol).
The step I made to revert back to stock is to do a FULL wipe of the phone (cache, davlik cache, data, system, AND internal storage), not a regular full wipe (without internal storage).
I put my backup stock rom file to my external sdcard (because the internal storage got wiped) and begin to flash, BUT NOT reboot into system, I reboot the phone to recovery instead (because I think the 5.1.1 rom works better with old TWRP so I reboot the phone to recovery first to get the old XZDual recovery).
After phone enter the old TWRP, I do a FULL wipe (cache, davlik, data, system, internal storage) once again to make sure everything OK, then flash the stock rom once again.
aand... it works. I did it 3-4 times to test new build of 7.0 n rom and never have any problem of reverting back.
But, I never test this method on newest 7.1.1 rom or 7.1.2 rom.
since you can't boot on LP rom, then try to flash KK rom.
Just install phone driver, flashtool, and download the KK ftf.
I'm sorry I can't provide you the full instruction because I never had this problem before, but you can search for this on N rom thread (the rom developed by Chippa). There is a guide made by someone on that thread.
Zerikwan said:
I never had this problem before, but have you try other ftf with lower android version like KK?
I see this problem on someone, everyone of them had this problem when they try to revert back to stock LP from N. Then someone suggest to flash KK ftf. You should try this if you haven't try this.
Sorry if my English is bad.
UPDATE:
when the first 7.0 nougat custom rom came, I'm on 5.1.1 rom with XZDual recovery. I made a backup for this rom and flash the 7.0 N rom only for trial then revert back to stock 5.1.1 that I backup before. Chippa's rom always came with latest built-in recovery so when I upgrade to nougat rom the XZDual recovery also lost (I don't have FOTA recovery, lol).
The step I made to revert back to stock is to do a FULL wipe of the phone (cache, davlik cache, data, system, AND internal storage), not a regular full wipe (without internal storage).
I put my backup stock rom file to my external sdcard (because the internal storage got wiped) and begin to flash, BUT NOT reboot into system, I reboot the phone to recovery instead (because I think the 5.1.1 rom works better with old TWRP so I reboot the phone to recovery first to get the old XZDual recovery).
After phone enter the old TWRP, I do a FULL wipe (cache, davlik, data, system, internal storage) once again to make sure everything OK, then flash the stock rom once again.
aand... it works. I did it 3-4 times to test new build of 7.0 n rom and never have any problem of reverting back.
But, I never test this method on newest 7.1.1 rom or 7.1.2 rom.
since you can't boot on LP rom, then try to flash KK rom.
Just install phone driver, flashtool, and download the KK ftf.
I'm sorry I can't provide you the full instruction because I never had this problem before, but you can search for this on N rom thread (the rom developed by Chippa). There is a guide made by someone on that thread.
Click to expand...
Click to collapse
Thank you so much for your reply. I will try it out. I really appreciate your contribution and I will keep you updated
I have a SM-G800F that's been running 4.2.2 forever. Last night I attempted to upgrade to 5.1.1 using Odin, afterwards I'm caught in a bootloop (just the Samsung logo). I tried recommended steps of wiping cache / factory reset from the recovery menu but no dice. I then attempted to flash 6.0.1 stock onto it, same problem.
Any help would be appreciated. When it was on 4.2.2 it was rooted with stock samsung fw and TWRP installed.
Just to add an update here, I flashed TWRP on it and then a LineageOS 14.1 Custom Rom with little hassle. Still not sure why the stock upgrade failed, possibly due to it being rooted already. Runs Android 7.1 beautifully so far.