Okay. Saw that CM12.1 came out, downloaded it. Flashed it. Forgot Gapps. So I kept getting the error message the Gapps crashed. Decided to flash back to 12, but still didn't have any Gapps .zip on the phone so it gave me the same error. Loaded my recovery, phone worked even if it was stock android bloated bs. But whatever.
Then I got a notification of an OTA update, figured I'd do that, then make a new backup before trying to reflash CM12.1 with the new Gapps package. Phone reboots, gets stuck booting to TWRP. Got home and downloaded Gapps 5.1, won't load past TWRP. Reflashed it with GL_G3_Flash2FixStuckRecovery.zip from here on XDA. Still no dice. So I queued up that, CM12 and Gapps 5. Still boots to TWRP. Then queued up that fix .zip, CM12.1 and Gapps 5.1, same ****. TWRP.
I'm going on a trip tomorrow, I'd quite like my phone to be operational so I don't have to use my ****ty burner. Any suggestions?
edit:
I can still transfer files to TWRP from my PC and access all of my TWRP functions, but it won't boot past that.
If you have a backup I would just restore to the previously working backup until the trip is over. Then when you come back worry about it. That being said, you said you took the OTA to Lollipop. Did it update successfully because typically it won't go through successfully if your d850 has been rooted. Are you on 20f? I would try flashing a rooted version of stock lollipop there is a few of them on here some are even debloated for you. If it works and you get a succeful boot then redownload the cm12 and Gapps and do a fresh clean install.
adosin said:
If you have a backup I would just restore to the previously working backup until the trip is over. Then when you come back worry about it. That being said, you said you took the OTA to Lollipop. Did it update successfully because typically it won't go through successfully if your d850 has been rooted. Are you on 20f? I would try flashing a rooted version of stock lollipop there is a few of them on here some are even debloated for you. If it works and you get a succeful boot then redownload the cm12 and Gapps and do a fresh clean install.
Click to expand...
Click to collapse
The issue was before booting and my recovery didn't work either. But I found a solution and was on CM12.1 the whole trip, so we're good.
Related
Hi mates.
So, I was running CM12 nightlies on my phone but it began to get slow and buggy.
I decided to go back to stock 4.4.4, ans then flash CM11 on dit
I did full wipe (data, system, cache, dalvik), installed stock 4.4.4 (latest official build)
Then i downloaded CM installer but couldn't get it to work.
So I used Nexus foot toolkit on PC, but the flashing process went wrong somehow, just when it reboots the phone to recovery, nothing happened, no flashing process whatsoever.
From this moment, my problem had appeared
So I rebooted normally, downloaded CM11 and I was unable to flash it. Signature check failed.
I've tried OTA 5.0.1, not working either, same error.
So I am currently running latest 4.4.4 without any problem, but even after an other full wipe I'm not able to flash anything, custom or stock. My recovery is the latest TWRP from the Google play app.
Could you please help me ? I don't mind wiping my phone, and I'd prefer a "no PC" solution but I still can use a PC if needed.
Thanks
visclo49 said:
Hi mates.
So, I was running CM12 nightlies on my phone but it began to get slow and buggy.
I decided to go back to stock 4.4.4, ans then flash CM11 on dit
I did full wipe (data, system, cache, dalvik), installed stock 4.4.4 (latest official build)
Then i downloaded CM installer but couldn't get it to work.
So I used Nexus foot toolkit on PC, but the flashing process went wrong somehow, just when it reboots the phone to recovery, nothing happened, no flashing process whatsoever.
From this moment, my problem had appeared
So I rebooted normally, downloaded CM11 and I was unable to flash it. Signature check failed.
I've tried OTA 5.0.1, not working either, same error.
So I am currently running latest 4.4.4 without any problem, but even after an other full wipe I'm not able to flash anything, custom or stock. My recovery is the latest TWRP from the Google play app.
Could you please help me ? I don't mind wiping my phone, and I'd prefer a "no PC" solution but I still can use a PC if needed.
Thanks
Click to expand...
Click to collapse
stop using toolkits, learn something for a change
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I was on stock rooted 5.1.1 and got the update notification, so i flashed the stock rom again to unroot, partition gpt.bin wouldnt flash, so i skipped it and it still worked, booted into 5.1..1 no trouble, hit the ota install, no trouble, booted up MM, no trouble, flashed twrp, booted into twrp, rooted using when twrp asked, and rebooted system- or tried to. it shows the bootloader is unlocked screen, and stays there indefinitely.
so i booted back into twrp and wiped cache, dalvivk, data, but it still didnt boot into system. i factory reset via twrp, no help, i flashed the supersu zip, thinking it was twrps root that was problematic, but still same problem.
Im going to try flashing cm13 via recovery to see if that works, but whats going on? is it that failed partition flash from earlier?
how can i get back to stock, mm or lp?
EDIT: CM13 works fine, no problems.
I'm having the same problem can u tell me how you solved this problem? Plzz ASAP
Sounds like dm-verity... Reflash your ROM and use systemless root from now on, don't ever touch /system!
Its been posted over and over, DON'T flash SuperSU when asked by TWRP, as Aquous said, use systemless root.
Sent from my SM-T530NU using Tapatalk
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
wahlmat said:
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
Click to expand...
Click to collapse
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(https://dl.twrp.me/bacon/).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware: https://drive.google.com/file/d/0BxysuRdzsJeWeW9JbTNwaUJKb1E/view?usp=drivesdk
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(opengapps.org)(optional).
Reboot.It should boot fine now.
Good luck!
Mr.Ak said:
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(Can't post links withing 10 posts apparently...).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware:
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(Can't post links withing 10 posts apparently...)(optional).
Reboot.It should boot fine now.
Good luck!
Click to expand...
Click to collapse
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
wahlmat said:
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
Click to expand...
Click to collapse
I'm glad you got it up and running.
Here are some FAQs:
What is a Firmware? What is Modem?
- Firmware is the whole package of proprietary partitions of your device, modem itself is a NON-HLOS file responsible for your device's communications over Wi-Fi, Mobile Networks and other such stuff.
So what is the difference between firmware and ROM then?
- Firmware is the responsible partition for IMEIs, the modemst partitions hold your IMEI, persist holds your Mac addresses etc.
ROM is only a combination​ of system.img and boot.img (kernel)
What to restore if I loose my IMEI?
- Both the modemst partitions (IMP: considering you took a backup of them before)
What is the default firmware? (default= firmware which comes with the latest CM/ LineageOS 14.1 weeklies)
- c6-00241
Thanks a lot, once again
Help!
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
HisMuse said:
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
Click to expand...
Click to collapse
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
wahlmat said:
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
Click to expand...
Click to collapse
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
HisMuse said:
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
Click to expand...
Click to collapse
Yes you do. You need that + some software. Check out some "install custom recovery oneplus one" guides, you should be able to find something. Are you on Mac or Windows?
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
HisMuse said:
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
Click to expand...
Click to collapse
Download the Samsung ADB driver or whatever it was called, then flash a new recovery for it. There are multiple guides for doing that. After that you should be able to transfer your files to your pc while being in recovery mode
Hi,
Its been a while since I been attentive to my Pixel. I was a lucky one who managed to get a Verizon 7.1.2 with an unlocked bootloader. I unlocked the bootloader, flashed a ROM, and rooted and haven't had a single major problem since.
I was running Resurrection Remix from about March and I yesterday I wanted to try to use Android Pay, so I followed a tutorial I found in another thread here to install Magisk, and when it was all said and done I ended up in a boot loop where the phone would reset as soon as it reaches the Google logo, ramdump, and eventually boot back into TWRP.
In the attempts to delete out all kinds of caches and dalviks and factory resets and whatever else, nothing worked.
So in the end I decided to just flash a new ROM. Flashed the latest Pure Nexus, reflashed TWRP, flashed the vendor image... went to go reboot and it gives me the WARNING! NO OS INSTALLED! error. I thought that was odd and decided to just update to the latest Resurrection Remix - same problem.
At this point I am unsure what to do next. I don't care about any user data on the phone, I just want to get it back up and running with a new ROM.
I have a few questions and thank you in advance for all help you may be able to offer:
1) Why am I getting the NO OS INSTALLED issue directly after flashing a ROM? Logs indicate no errors whatsoever. /system/ is mounted. Every time I boot into TWRP it asks me if I want to Keep System partition read only. I always tell it to allow modifications and never ask me this question again - it asks every time. Is it possible that /system/ can actually remain empty even after a fresh ROM install that gives no errors in the log?
2) I believe that I am supposed to reflash to stock image that this phone shipped with to start all over. If I reflash back to stock, will my bootloader have any chance of locking again? I don't even know what version the stock image was, and I'm further confused/concerned about the fact that it was a 7.1.2 image I shipped with - from my understanding there were security updates which make unlocking/rooting impossible. I don't understand why you have to start that far back - is it even needed? The latest Resurrection Remix ROM install instructions assumes that I am on latest "Firmware" NOF26W. This is another issue I don't understand - what is a firmware? The full factory image? In any case, NOF26W is specifically for Rogers Google Pixel devices. Since I need to be on this "firmware" before I install latest, can I just flash the NOF26W Stock image despite the fact that I am using a rooted Verizon Pixel? The NOF26W image is 1.8GB: What exactly in this ZIP am I supposed to flash?
3) There were various weird things about this phone/flashing ROMs that I seem to recall such as having to boot an older TWRP before flashing ROM and then flashing the newer TWRP - is any of this stuff still relevant?
4) I also remember that many people were fastbooting TWRP rather than flashing TWRP for some reason - are there specific builds/non-standard stuff required for any of this to work on the Pixel?
I really appreciate all and any help that anybody can provide. If there's files that you're referring to, PLEASE send links. I need to get this phone back up and running ASAP.
Thanks again!!
when you wipe system, twrp wipes current active slot but when install a rom, it gets installed in the inactive slot (which will become active upon reboot). but twrp still thinks the currently active slots system is erased and complains that no os is installed.
rohitece06 said:
when you wipe system, twrp wipes current active slot but when install a rom, it gets installed in the inactive slot (which will become active upon reboot). but twrp still thinks the currently active slots system is erased and complains that no os is installed.
Click to expand...
Click to collapse
This. I just reboot anyway after seeing that message and I've never had any issues.
So I was on tmobiles firmware rooted and something happened last night. It shut off and wouldn't boot up into system or recovery so after being frantic about it for about an hour and after some googling. I decided I was going to try a dirty flash (I think that's what I did)
I downloaded the latest ota zip from OnePlus 9.5.11 and used the all in 1 tool to boot to twrp and installed the ota zip there and installed twrp. Now the phone booted up to 9.5.11 on the international version and asked me to update to 9.5.13 which I let it. Then I rebooted back to twrp and installed magisk and reboot again. Bootloop happened so I went back to twrp and deleted my modules and rebooted again and it was fine and then reinstalled my modules....
Now for the actual question, should I be worried about corrupt data by doing what I did?
I really didn't want to lose my data, I have titanium backup but I can't get twrp to make any backups because I use OOS parallel apps
Bump
Anyone have an answer or any info to add?
If you didn't lose anything, then you didn't lose anything.