I was on Carbon Rom 20140701 and updated OTA to 20140706. Now my Nexus 5 is stuck on boot at the Google Logo.
I only can access the Recovery (TWRP) but don't know anything to do with that.
Can you please help?
Towelie90 said:
I was on Carbon Rom 20140701 and updated OTA to 20140706. Now my Nexus 5 is stuck on boot at the Google Logo.
I only can access the Recovery (TWRP) but don't know anything to do with that.
Can you please help?
Click to expand...
Click to collapse
Have you tried reflash the rom or restore an eariel backup?
Read this how to send a rom to your phone if you are in recovery http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
bitdomo said:
Have you tried reflash the rom or restore an eariel backup?
Read this how to send a rom to your phone if you are in recovery http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
Click to expand...
Click to collapse
Thank you. It turned out, the nightly had a Problem. I flashed the previous Rom instead
Towelie90 said:
Thank you. It turned out, the nightly had a Problem. I flashed the previous Rom instead
Click to expand...
Click to collapse
Same issue with the same version of Carbon ROM. I tried to OTA update to 20140706 and was stuck at google logo. After reflashing 20140706 downloaded directly from carbon website with verified MD5 match, still no go.
Only reverting back to 20140705 did the trick. With 20140705 it booted first time with no problems, and, did not require a factory reset. All userdata still in tact.
Using TWRP 2.7.1.1
Thanks!
Towelie90 said:
I was on Carbon Rom 20140701 and updated OTA to 20140706. Now my Nexus 5 is stuck on boot at the Google Logo.
I only can access the Recovery (TWRP) but don't know anything to do with that.
Can you please help?
Click to expand...
Click to collapse
Vihsadas said:
Same issue with the same version of Carbon ROM. I tried to OTA update to 20140706 and was stuck at google logo. After reflashing 20140706 downloaded directly from carbon website with verified MD5 match, still no go.
Only reverting back to 20140705 did the trick. With 20140705 it booted first time with no problems.
Using TWRP 2.7.1.1
Thanks!
Click to expand...
Click to collapse
If you check the file size of that nightly it was smaller than the previous one. I would recommend making a backup before updating nightlies since sometimes these things happen.
Lethargy said:
If you check the file size of that nightly it was smaller than the previous one. I would recommend making a backup before updating nightlies since sometimes these things happen.
Click to expand...
Click to collapse
Yup. Always a good idea. Sometimes we get lazy though.
Vihsadas said:
Yup. Always a good idea. Sometimes we get lazy though.
Click to expand...
Click to collapse
And then come here and ask stupid questions
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
And then come here and ask stupid questions
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Whoa easy there on the full out attack. It's unnecessary.
And, I did not actually ask any questions. Just offered my experience for others that might have had the same problem.
Relax.
Hey,
Sorry if I'm a bit late here, but they actually left out some of the firmware from the release. If you download the 07/06 zip, then merge the 07/07 with it (of course, replacing anything that exists) and zip the combination up and flash it, you'll be all set with the newest nightly.
I have the same problem. Unfortunately, I updated about 10 minutes before I was leaving for work so now I'm without a phone until I can get back and flash yesterday's nightly. I usually only update in the evening in case this happens but I haven't had any issues with Carbon up until now so I figured, what the hell... Guess that'll teach me to do that again.
Related
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
dudekiller said:
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
Click to expand...
Click to collapse
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
quendil said:
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
Click to expand...
Click to collapse
im still getting invalid bootloader img
dudekiller said:
im still getting invalid bootloader img
Click to expand...
Click to collapse
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
quendil said:
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
Click to expand...
Click to collapse
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
dudekiller said:
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
Click to expand...
Click to collapse
Oh damn...
On bootloader when you give the command fastboot devices does it show you anything?
i wonder if the TWRP bug is why i was getting bootloop when flashing Bootanimations the other day?
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
alright guys i figured it out i did a oem lock and unlock and then the factory image worked so im stock right now... it might stay that way for a bit.. lol
comicbookguy72 said:
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
Click to expand...
Click to collapse
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Zepius said:
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Click to expand...
Click to collapse
his first priority is fixing it. his second priority is possibly finding out why he borked it and not making the same mistake again. i've borked stuff learning and fixed it with toolkits.
not everyone wants to learn ADB or fastboot commands, or install the SDK, and NOT EVERYONE HAS TO. not everyone is a would-be developer
dudekiller said:
they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
Click to expand...
Click to collapse
So why did you flash via TWRP then?
Han Solo 1 said:
So why did you flash via TWRP then?
Click to expand...
Click to collapse
i didnt go through the faqs before installing, i looked at the rom and what it offered. it said stable so i wasnt to worried about bugs since i was coming from cm11
OK guys let me tell you about my issue's
I'm using TWRP 2.7.1.0 (Tried 2.7.0.2 no difference) S-off, Unlocked, latest firmware from Santods files. The phone works fine with Sense ROMS but for the life of me I can't flash a GPE ROM. They fail every time. Santod tried to help me out the best he could by having me replace the Boot.img from the ROM I was flashing thinking that I was on a secure Boot image (And I may be but I replaced it and they still won't flash). Mr. Jaydee82 also modified a ROM for me to try out (although I'm not sure exactly what he did to it) and it wouldn't Flash properly either. When I try to flash these ROMs it will appear to flash properly and then they will go to the bootscreen and just sit there and churn. Depending on the ROM some will time out and power down the device and some will just sit there forever until I do a virtual battery pull. I'm freaking desperate to find out what is going on with this device and I don't feel right bugging Santod so I decided to post this in hope of more ideas about what could possibly be going on with my device. Any and all help greatly appreciated!!!
Thanks!
Duckman_UF said:
OK guys let me tell you about my issue's
I'm using TWRP 2.7.1.0 (Tried 2.7.0.2 no difference) S-off, Unlocked, latest firmware from Santods files. The phone works fine with Sense ROMS but for the life of me I can't flash a GPE ROM. They fail every time. Santod tried to help me out the best he could by having me replace the Boot.img from the ROM I was flashing thinking that I was on a secure Boot image (And I may be but I replaced it and they still won't flash). Mr. Jaydee82 also modified a ROM for me to try out (although I'm not sure exactly what he did to it) and it wouldn't Flash properly either. When I try to flash these ROMs it will appear to flash properly and then they will go to the bootscreen and just sit there and churn. Depending on the ROM some will time out and power down the device and some will just sit there forever until I do a virtual battery pull. I'm freaking desperate to find out what is going on with this device and I don't feel right bugging Santod so I decided to post this in hope of more ideas about what could possibly be going on with my device. Any and all help greatly appreciated!!!
Thanks!
Click to expand...
Click to collapse
What did you use to s-off; firewater or sunshine? Are you able to flash/boot AOSP roms? Did you take the 1.55.605.2 OTA before?
krazie1 said:
What did you use to s-off; firewater or sunshine? Are you able to flash/boot AOSP roms? Did you take the 1.55.605.2 OTA before?
Click to expand...
Click to collapse
I used Firewater I'm able to Flash all of the Sense ROM's not sure if they are considered AOSP. Give me an example of one and I'll try it. I'm not 100% sure if I took the OTA update before I Rooted and S-offed/unlocked the device but I think I did. I Flashed Santods Nobootimg firmware via ADB to be sure I was on the latest firmware. I know my radios were up to date before doing this but I wasn't sure about the FW so I flashed it. Flashed fine, didn't need to flush again, flashed fine first time.
Duckman_UF said:
I used Firewater I'm able to Flash all of the Sense ROM's not sure if they are considered AOSP. Give me an example of one and I'll try it. I'm not 100% sure if I took the OTA update before I Rooted and S-offed/unlocked the device but I think I did. I Flashed Santods Nobootimg firmware via ADB to be sure I was on the latest firmware. I know my radios were up to date before doing this but I wasn't sure about the FW so I flashed it. Flashed fine, didn't need to flush again, flashed fine first time.
Click to expand...
Click to collapse
I'll post a link to a aosp ROM but first can you link me to the firmware file you flashed?
krazie1 said:
I'll post a link to a aosp ROM but first can you link me to the firmware file you flashed?
Click to expand...
Click to collapse
4th one down and this was per Santod's instuction so I'm sure it's good.
http://www.androidfilehost.com/?w=files&flid=13966
Duckman_UF said:
4th one down and this was per Santod's instuction so I'm sure it's good.
http://www.androidfilehost.com/?w=files&flid=13966
Click to expand...
Click to collapse
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
krazie1 said:
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
Click to expand...
Click to collapse
Yes, ADB Fastboot Hboot...exactly as video instructed. No problems at all.
I'll give it a shot!
krazie1 said:
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
Click to expand...
Click to collapse
Is a Gapps package needed for this ROM. Ive used Cyanogen ROM's before just not on this Phone.
Duckman_UF said:
Yes, ADB Fastboot Hboot...exactly as video instructed. No problems at all.
I'll give it a shot!
Click to expand...
Click to collapse
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
krazie1 said:
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
Click to expand...
Click to collapse
Thats what I thought..Thanks! About to dl Gapps and give it a shot.
krazie1 said:
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
Click to expand...
Click to collapse
Yep flashed fine...no problems.
Duckman_UF said:
Yep flashed fine...no problems.
Click to expand...
Click to collapse
OK then, did you try both GPE ROMs for the vzw variant? Download the newest version of sinlessrom and wipe advanced (cache, dalvik cache, data & system) in TWRP.
http://www.androidfilehost.com/?fid=23578570567721616
krazie1 said:
OK then, did you try both GPE ROMs for the vzw variant? Download the newest version of sinlessrom and wipe advanced (cache, dalvik cache, data & system) in TWRP.
http://www.androidfilehost.com/?fid=23578570567721616
Click to expand...
Click to collapse
Already tried...Various Roms, various versions, 2 versions of TWRP (As stated) Aroma, non Aroma...They all just sit there and churn away on the boot screen or power down the device. I always wipe in that fashion
Man I'm out of ideas, I really want to help but can't think of anything. I'll still look and see if I can find anything.
krazie1 said:
Man I'm out of ideas, I really want to help bit can't think of anything. I'll still look and see if I can find anything.
Click to expand...
Click to collapse
I really appreciate your help. Santod and me went back and forth via PM a few times and JayDee modified his Rom for me and now you. IDK....I'm dumbfounded. If you think of anything let me know. I'll just stay on AOSP for now. Always liked Cyanogen's stuff anyway, just never even thought about them since their ROMS are not in the forums. They used to be for my various other phones. Never really though about them not being on XDA until we did this just now. Thanks again for you time and help!!!
Duckman_UF said:
I really appreciate your help. Santod and me went back and forth via PM a few times and JayDee modified his Rom for me and now you. IDK....I'm dumbfounded. If you think of anything let me know. I'll just stay on AOSP for now. Always liked Cyanogen's stuff anyway, just never even thought about them since their ROMS are not in the forums. They used to be for my various other phones. Never really though about them not being on XDA until we did this just now. Thanks again for you time and help!!!
Click to expand...
Click to collapse
Yeah cm11 is what I'm currently using, it recently had a speakerphone issue but its been fixed since 7/30. The only AOSP ROMs that have incorporated the fix are cm11, liquidsmooth & aokp. Here is the section for all the aosp ROMs they are universal so means 1 zip for all HTC One M8 variants.
http://forum.xda-developers.com/htc-one-m8/orig-development
Have you tried a RUU?
young0ne said:
Have you tried a RUU?
Click to expand...
Click to collapse
What do you mean? I put the phone in RUU when when flashing the firmware with ADB??
Duckman_UF said:
What do you mean? I put the phone in RUU when when flashing the firmware with ADB??
Click to expand...
Click to collapse
it put stock back on the phone just like it was new out of box. it re installs everything from factory.
Thanks!
GNU con Linux
I've done some searching around, and can't really find anyone else that is having quite the same problem as me. So, I'm running CM12 Nightlies on my One. After I upgraded from stock, everything worked flawlessly. But now, whenever I try to update it to a new nightly, it gets stuck in a bootloop. The only way I've found to get it to update without the bootloop is to wipe the whole system. Which is getting a little annoying having to reinstall my apps and stuff every day. I've found a few work arounds, like making a backup through TWRP, updating, then restoring just the data of the backup. But I'd like to be able to just update it without having to go through all that trouble. I don't know if I'm the only one having this specific issue, or if it's a CM12 issue. Any help would be great.
Have you tried using CyanDelta?
https://play.google.com/store/apps/details?id=com.cyandelta
Transmitted via Bacon
Its also possible there are firmware differences. I have read about some new firmware pushes in the nighties. I am currently on Bliss and we have to flash updated files to keep up with the cm commits. It could be that because your dirty flashing its causing an issue. Perhaps do a backup of data, install latest. And restore data is your best bet.
Sent from my A0001 using Tapatalk
timmaaa said:
Have you tried using CyanDelta?
Transmitted via Bacon
Click to expand...
Click to collapse
Tried that earlier today, didn't help anything.
gmac1990 said:
Its also possible there are firmware differences. I have read about some new firmware pushes in the nighties. I am currently on Bliss and we have to flash updated files to keep up with the cm commits. It could be that because your dirty flashing its causing an issue. Perhaps do a backup of data, install latest. And restore data is your best bet.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yeah, I think that might be my best bet. I guess it's better than nothing, haha. Thanks for you answers guys.
It probably is due to not having updated firmware. Which nightly? Wipe everything and flash the most recent nightly or go to blisspop thread and find the updated firmware zip it's around 30mb and flash that. It should fix your boot loop issues
Sent From Lollipopified Bacon Goodness!
The firmware can be found here:
http://www.vanir-exodus.net/exodus/bacon/
Transmitted via Bacon
Thanks for the help guys. That most likely would have been the issue. But, alas, I ended up soft bricking (still not sure how), and now I'm back to stock. I'll probably stick here until a more stable Lollipop ROM is out.
Skizwack said:
Thanks for the help guys. That most likely would have been the issue. But, alas, I ended up soft bricking (still not sure how), and now I'm back to stock. I'll probably stick here until a more stable Lollipop ROM is out.
Click to expand...
Click to collapse
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
timmaaa said:
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
Click to expand...
Click to collapse
I suppose that may have been my problem all along. The main problems I was having were just little bugs (system UI very rarely crashing, and a couple other minor annoyances), but I guess those could have been caused by having the wrong firmware. Maybe I'll give it another go soon. Now that I'm all settled in to CM11S, haha. Thanks again!
Has anyone else had any issues with the automated download and install feature in the CM12 settings? Mine will download the night lies and even automatically boot into TWRP but it doesn't flash?
timmaaa said:
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
Click to expand...
Click to collapse
So, I'm still having this issue. I flashed the new firmware yesterday, and I went back and installed CM12 (the 1-28-15 nightly). Just now I tried updating it to the 1-29-15 nightly with CyanDelta, and it's doing the exact same thing again. Any other suggestions? Did I flash the firmware in the wrong order?
Skizwack said:
So, I'm still having this issue. I flashed the new firmware yesterday, and I went back and installed CM12 (the 1-28-15 nightly). Just now I tried updating it to the 1-29-15 nightly with CyanDelta, and it's doing the exact same thing again. Any other suggestions? Did I flash the firmware in the wrong order?
Click to expand...
Click to collapse
which recovery and version are you using?
playya said:
which recovery and version are you using?
Click to expand...
Click to collapse
TWRP 2.8.4.1
Skizwack said:
TWRP 2.8.4.1
Click to expand...
Click to collapse
What's the name of the firmware file you flashed?
Transmitted via Bacon
timmaaa said:
What's the name of the firmware file you flashed?
Transmitted via Bacon
Click to expand...
Click to collapse
bacon_firmware_update_2015_01_16.zip, from that link you gave me before.
Skizwack said:
I've done some searching around, and can't really find anyone else that is having quite the same problem as me. So, I'm running CM12 Nightlies on my One. After I upgraded from stock, everything worked flawlessly. But now, whenever I try to update it to a new nightly, it gets stuck in a bootloop. The only way I've found to get it to update without the bootloop is to wipe the whole system. Which is getting a little annoying having to reinstall my apps and stuff every day. I've found a few work arounds, like making a backup through TWRP, updating, then restoring just the data of the backup. But I'd like to be able to just update it without having to go through all that trouble. I don't know if I'm the only one having this specific issue, or if it's a CM12 issue. Any help would be great.
Click to expand...
Click to collapse
have tried different version TWRP?
Skizwack said:
bacon_firmware_update_2015_01_16.zip, from that link you gave me before.
Click to expand...
Click to collapse
What about when you download the whole ROM zip from the CM site?
geowolf1000 said:
have tried different version TWRP?
Click to expand...
Click to collapse
The version he's on is fine.
timmaaa said:
What about when you download the whole ROM zip from the CM site?
Click to expand...
Click to collapse
I think I tried that before. Even if I downloaded that and flashed it from recovery (without wiping anything first), it would do the same thing.
I know it's best to not dirty flash, but my main reason I want to figure this out is because I use Google Music All Access. And every time I wipe my system I have to re-download all my music.
Skizwack said:
I think I tried that before. Even if I downloaded that and flashed it from recovery (without wiping anything first), it would do the same thing.
I know it's best to not dirty flash, but my main reason I want to figure this out is because I use Google Music All Access. And every time I wipe my system I have to re-download all my music.
Click to expand...
Click to collapse
Dirty flashing should be fine if you're just updating the same ROM. Do you check the md5 when you download the file? They might be getting corrupt during the download.
timmaaa said:
Dirty flashing should be fine if you're just updating the same ROM. Do you check the md5 when you download the file? They might be getting corrupt during the download.
Click to expand...
Click to collapse
If I remember right, I do. I'm on the latest version now though, so I can't really test it. When a new one comes out tomorrow I'll give it a go and see what happens.
Hi
Since updating my OPO to YOG4PAS1N0 I couldn't reboot my OPO. Since the last update it won't even boot any more. I've reflashed to stock 4.4.4, installed every update and had the same issue. I even tried to flash the zip true recovery, but i got an error while doing it. So, after three times of updating, I'm back to square one.
After going back to stock I have to factory reset in recovery, otherwise the OPO won't boot.
But of course I'd like to install Lollipop (and later Marshmallow). What can I do? I have a Mac with OSX 10.11 and a laptop with Windows 7, so I'm able to use both.
I did the flashing on my Macbook with the Toolkit found here. But I don't think there's an issue with this, as it uses the terminal. It's just easier then to type it all myself
Thanks in advance.
erdeebee said:
Hi
Since updating my OPO to YOG4PAS1N0 I couldn't reboot my OPO. Since the last update it won't even boot any more. I've reflashed to stock 4.4.4, installed every update and had the same issue. I even tried to flash the zip true recovery, but i got an error while doing it. So, after three times of updating, I'm back to square one.
After going back to stock I have to factory reset in recovery, otherwise the OPO won't boot.
But of course I'd like to install Lollipop (and later Marshmallow). What can I do? I have a Mac with OSX 10.11 and a laptop with Windows 7, so I'm able to use both.
I did the flashing on my Macbook with the Toolkit found here. But I don't think there's an issue with this, as it uses the terminal. It's just easier then to type it all myself
Thanks in advance.
Click to expand...
Click to collapse
It'd help if you actually posted what errors you're getting, without information like that it's virtually impossible to troubleshoot. Anyway, your best bet is probably just to flash the stock images with fastboot. Back up anything important first as this will wipe your device. See section 8 of my guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
The only error I got, was that it's impossible to boot. I'll try your guide asap
Heisenberg said:
It'd help if you actually posted what errors you're getting, without information like that it's virtually impossible to troubleshoot. Anyway, your best bet is probably just to flash the stock images with fastboot. Back up anything important first as this will wipe your device. See section 8 of my guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
I unlocked the bootloader.
I installed the latest fastboot image.
Now my OPO is stuck again at the 1+ / Powered by Android-screen. I can't boot into recovery, but fastboot mode is still possible.
Everything up to cm-12.0-YNG1TAS2XK-bacon-signed-fastboot seems to work fine.
erdeebee said:
I unlocked the bootloader.
I installed the latest fastboot image.
Now my OPO is stuck again at the 1+ / Powered by Android-screen. I can't boot into recovery, but fastboot mode is still possible.
Click to expand...
Click to collapse
erdeebee said:
Everything up to cm-12.0-YNG1TAS2XK-bacon-signed-fastboot seems to work fine.
Click to expand...
Click to collapse
Is there a reason you're using that particular build instead of the latest? How are you installing it?
Heisenberg said:
Is there a reason you're using that particular build instead of the latest? How are you installing it?
Click to expand...
Click to collapse
I'm sorry, I thought my message was clear. The latest build gives the same problem. With this build, I'm able to boot. I installed this in terminal as a fastboot-images.
This guy has the exact same problem.
erdeebee said:
This guy has the exact same problem.
Click to expand...
Click to collapse
Assuming that you want to upgrade your OPO to latest available version of Cyanogen
- Flash latest *fastboot* image from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- If you have already tried above step, flash cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip and then upgrade via OTA incremental update zip
Mr hOaX said:
Assuming that you want to upgrade your OPO to latest available version of Cyanogen
- Flash latest *fastboot* image from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- If you have already tried above step, flash cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip and then upgrade via OTA incremental update zip
Click to expand...
Click to collapse
I've tried the first, didn't work. I've tried flashing 11S and started upgrading. I didn't have issues until 12.0. When I got to 12.1 I couldn't reboot (but I could shut down and boot). With the latest update I couldn't even boot normally.
Anyone has some idea?
Verstuurd vanaf mijn A0001 met Tapatalk
erdeebee said:
Anyone has some idea?
Verstuurd vanaf mijn A0001 met Tapatalk
Click to expand...
Click to collapse
Not sure if its a language barrier but first of you are going to have to supply more information than that. Secondly what have you tried to fix it and especially since there are tutorial out the waaaaahzooo in here on how to repair your "bricked" phone.
Please research make some attempts and if any issue please document in full what your issue is. I guarantee you though whatever it is someone here has gone through it already so search thorough
playya said:
Not sure if its a language barrier but first of you are going to have to supply more information than that. Secondly what have you tried to fix it and especially since there are tutorial out the waaaaahzooo in here on how to repair your "bricked" phone.
Please research make some attempts and if any issue please document in full what your issue is. I guarantee you though whatever it is someone here has gone through it already so search thorough
Click to expand...
Click to collapse
What I have tried is on page 1 of this thread.
I tried to install 4.4.4 with a flashable zip and then installed all updates. I installed the 5.1.1 zip. I installed the fastboot 5.1.1 and 4.4.4 and installed all updates.
Now I'm on 5.0.
On the last update I couldn't update reboot or boot anymore. The update before that I couldn't reboot, bu I could boot.
erdeebee said:
What I have tried is on page 1 of this thread.
I tried to install 4.4.4 with a flashable zip and then installed all updates. I installed the 5.1.1 zip. I installed the fastboot 5.1.1 and 4.4.4 and installed all updates.
Now I'm on 5.0.
On the last update I couldn't update reboot or boot anymore. The update before that I couldn't reboot, bu I could boot.
Click to expand...
Click to collapse
My bad on that did not even realize there was another page.. dont know how that happened... Wow I say just start from scratch and go to cm page and download the latest stock software. I am sorry I see others have tried to help you and to be honest your breakdown is a lil confusing. NO worries though hopefully someone will come along to help
Hi,
I have a VZW Quark that's been unlocked with Sunshine and rooted and running fine on custom ROM's for a year. Today I did a factory reset and complete wipe and reinstalled RR Rom and GApps etc. However, on reboot, it only goes back to recovery (TWRP 3.1.1-0). I faced this the last time as well and managed to find the fix by googling it but can't seem to get to it now. It was a quick fix and then it booted to system fine and I cannot remember it. Can anyone help! Thanks.
Rikhit said:
Hi,
I have a VZW Quark that's been unlocked with Sunshine and rooted and running fine on custom ROM's for a year. Today I did a factory reset and complete wipe and reinstalled RR Rom and GApps etc. However, on reboot, it only goes back to recovery (TWRP 3.1.1-0). I faced this the last time as well and managed to find the fix by googling it but can't seem to get to it now. It was a quick fix and then it booted to system fine and I cannot remember it. Can anyone help! Thanks.
Click to expand...
Click to collapse
Someone else had this issue and they solved it by flashing the latest @bhb27 modded TWRP. You say you have TWRP 3.1.1, but is it from the TWRP website or from @bhb27? Flash this one below to make sure.
twrp-3.1.1-mod_2-quark.img
https://androidfilehost.com/?w=files&flid=39562
Once they flashed it, they were able to boot to system, then they booted back to TWRP (on purpose) -- and then upon subsequent reboots everything was fine.
See here:
mpro420 said:
@bhb27 Im face a problem, since I do a clean install build 08/23, when my phone restart, it always boot into TWRP, and I need to boot to bootloader and press START to start system normally.
Maybe Im doing something worng due the install process, (full wipe include internal storage, flash Crdroid, flash Gapps, reboot), I try to flash boot.img and new TWRP 3.1.1 recovery.img, but got a same results.
Please help, thanks a lot.
我從使用 Tapatalk 的 DROID Turbo 發送
Click to expand...
Click to collapse
bhb27 said:
You may not be using the TWRP made by me, check TWRP thread and use the twrp-3.1.1-mod_2-quark.img version that is in the afh mirror folder if you are not using that... also try to update the ROM as 8/23 is one month old on updates...
Click to expand...
Click to collapse
mpro420 said:
Thank you!!
After flash the TWRP 3.1.1-mod 2, my phone booting is back to normal. :good
ps: I want to donate to your hard work, but I dont had a Paypal account, its there other way I can buy you a beer?
我從使用 Tapatalk 的 DROID Turbo 發送
Click to expand...
Click to collapse
bhb27 said:
Mod TWRP can cleanup the "android to recovery commands" the process was changed in nougat and official or old version don't have the new support...
From outside of Brazil that is the only option that I can received and use what I have received...
:good:
Click to expand...
Click to collapse