Database Info

Quick Question, Google

I flashed a rom and I'm stuck on the GOOGLE screen. Roms flash completely but after I reboot the screen stays in GOOGLE?
Any ideas what I can do? I hard reset and no go!

Do a full wipe. Factory data then wipe the cache and dalvik then reflash the rom.

jerrycycle said:
Do a full wipe. Factory data then wipe the cache and dalvik then reflash the rom.
Click to expand...
Click to collapse
Thanks, I did that and than I go into recovry and flash a rom and it either freezes half way whil installing or it goes all the way through. BUT, once I reboot it stays on the GOOGLE logo forever!
Any other ideas?

Check the md5 and make sure your download was not corrupt. What rom are you trying to flash? It is for the nexus s correct.

jerrycycle said:
Check the md5 and make sure your download was not corrupt. What rom are you trying to flash? It is for the nexus s correct.
Click to expand...
Click to collapse
I'm sorry but what is the MD5? And I have tried a few roms for nexus s. Latest one is BOFTAIN-NS-V1.
Btw, when I install a rom i get E:ERROR IN /SDCARD/MIUIDEV.....ZIP (STATUS 7)."INSTALLATION ABORTED" What does STATUS 7 MEAN?

MD5 has (or checksum) functions as a compact digital fingerprint of a file. The download file and on both ends should have the same number. As for the status 7 not sure. I have never had that issue. I do recall others in the past did. What recovery version do you have?

I tried another thread that said to download the stock 2.3 gingerbread.... and the file is a backup for the nandroid something something. I did just as the instructiond stated.
But when it tries to restore it says CAN'T MOUNT SYSTEM. and it stops right there.
FASTBOOT VERSION SAYS REV 11
RECOVERY - CLOCKWORKMOD V2.5.1.8

JasjarMan said:
I tried another thread that said to download the stock 2.3 gingerbread.... and the file is a backup for the nandroid something something. I did just as the instructiond stated.
But when it tries to restore it says CAN'T MOUNT SYSTEM. and it stops right there.
FASTBOOT VERSION SAYS REV 11
RECOVERY - CLOCKWORKMOD V2.5.1.8
Click to expand...
Click to collapse
um... you need to update your clockwork, i dont know why you have a v2.x.x.x recovery version at all.. its not compatible with the NS

zephik said:
um... You need to update your clockwork, i dont know why you have a v2.x.x.x recovery version at all.. Its not compatible with the ns
Click to expand...
Click to collapse
GOT IT! I downloaded and flash 3.0 version and its working!
THANK YOU SO MUCH!

I have the latest one.
It's v 3.0.2.4 CWM
Topic: http://forum.xda-developers.com/showthread.php?t=988686
Don't forget to download the right one.
If you have nexus s super clear lcd (i9023) download the second one.
If you have the other one w/ SAMOLED (i9020) it's the first.
And flash it via fastboot
" fastboot flash recovery 3024v3-i9020.img "
Hope it helps

liquelt said:
I have the latest one.
It's v 3.0.2.4 CWM
Topic: http://forum.xda-developers.com/showthread.php?t=988686
Don't forget to download the right one.
If you have nexus s super clear lcd (i9023) download the second one.
If you have the other one w/ SAMOLED (i9020) it's the first.
And flash it via fastboot
" fastboot flash recovery 3024v3-i9020.img "
Hope it helps
Click to expand...
Click to collapse
The 3.0.2.4 CWM is a unofficial release. The official release is 3.0.0.5.
But regardless, both should work the same.
@Jasjer: Glad to hear its working

Sorry. I just put this because I think is better because I really don't like the lots of no's on 3.0.0.5 .
Thanks in advance.
Sent from my Nexus S using XDA Premium App

liquelt said:
Sorry. I just put this because I think is better because I really don't like the lots of no's on 3.0.0.5 .
Thanks in advance.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
yeah thats the only obvious change.. unofficial doesn't necessarily mean bad, just saying if you encounter bugs with the unofficial one try the official one.
i personally use 3.0.0.5 because im used to the No's

Stuck at "Google Logo" on boot (after Carbon Rom update)

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.

Alright, i ****ed up. need help

My phone suddenly started showing zero reception, so i tried wiping it to just get a clean start. Im using TWRP (which i havent really used in the past) and did the "Wipe Data" option rather than the normal wipe because i'm a ****ing idiot. now it says there is no OS installed, so yeah.
I can still boot into recovery but not much else obvously. I'm hoping there's a way for me to mount the phone to my mac and load on a rom and fix it. I understand how stupid i sound but i really need someone to walk me though this. I used to mess around with my GS3 and all my old phones all the time and never had a problem but i haven't with my nexus really since i first got it. I swear i'm not actually retarded.
What are my options here?

FixedTheFernBack said:
My phone suddenly started showing zero reception, so i tried wiping it to just get a clean start. Im using TWRP (which i havent really used in the past) and did the "Wipe Data" option rather than the normal wipe because i'm a ****ing idiot. now it says there is no OS installed, so yeah.
I can still boot into recovery but not much else obvously. I'm hoping there's a way for me to mount the phone to my mac and load on a rom and fix it. I understand how stupid i sound but i really need someone to walk me though this. I used to mess around with my GS3 and all my old phones all the time and never had a problem but i haven't with my nexus really since i first got it. I swear i'm not actually retarded.
What are my options here?
Click to expand...
Click to collapse
You could probably just flash the stock Nexus 5 image from here developers.google.com android section. You'll see a bit saying nexus factory images.
If you can't actually manage to transfer the file on to your phone and flash it from recovery, then just use the tutorial on that page using adb and fastboot.

Yep. The options are fastboot flash stock system and boot.img or adb push a flashable zip to your sdcard and flash via recovery
Click link in signature for sticky then read my adb and fastboot thread
Sent from my Nexus 5 using Tapatalk

rootSU said:
Yep. The options are fastboot flash stock system and boot.img or adb push a flashable zip to your sdcard and flash via recovery
Click link in signature for sticky then read my adb and fastboot thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot. Solved it with adb sideload cm11. i hadn't really ever used adb before so i was in a bit of a panic.

FixedTheFernBack said:
Thanks a lot. Solved it with adb sideload cm11. i hadn't really ever used adb before so i was in a bit of a panic.
Click to expand...
Click to collapse
Excellent
Sent from my Nexus 5 using Tapatalk

[Q&A] [RECOVERY][hammerhead] TWRP 2.8.1.0 touch recovery [2014-10-29]

Q&A for [RECOVERY][hammerhead] TWRP 2.8.1.0 touch recovery [2014-10-29]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][hammerhead] TWRP 2.8.1.0 touch recovery [2014-10-29]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Touchscreen Issues
I have tried to use TWRP as my recovery option but whenever i go into recovery mode the touchscreen ceases to work. and i have to do a hard reboot. On everyday use the screen works flawlessly and the issue only presents itself when using TWRP. My question is if there is anyway to use TWRP with the physical buttons instead of the touch interface.
Any help will be appreciated.

glm0025 said:
I have tried to use TWRP as my recovery option but whenever i go into recovery mode the touchscreen ceases to work. and i have to do a hard reboot. On everyday use the screen works flawlessly and the issue only presents itself when using TWRP. My question is if there is anyway to use TWRP with the physical buttons instead of the touch interface.
Any help will be appreciated.
Click to expand...
Click to collapse
No only touchscreen. You should check the way you install TWRP on your Nexus 5.

I upgrade twrp with this zip http://forum.xda-developers.com/google-nexus-5/general/recovery-zip-collection-t2636279
it's normally that after flash zip into twrp , reboot system and then stuck on teamwin logo for 2 seconds after twrp starts?
tnx

ironia. said:
I upgrade twrp with this zip http://forum.xda-developers.com/google-nexus-5/general/recovery-zip-collection-t2636279
it's normally that after flash zip into twrp , reboot system and then stuck on teamwin logo for 2 seconds after twrp starts?
tnx
Click to expand...
Click to collapse
Fastboot flash back to stock recovery, boot into recovery. Fastboot flash latest TWRP recovery. Test

So the latest TWRP works with the official release LRX21O?

Hi, I have this problem.. I flashed the official lollipop image yesterday and after that, TWRP,all using fastboot commands. The fact is that TWRP works the first time after I Install it.. But then it stops working, and instead of booting into recovery, it display the Android symbol with a red exclamation mark over it. Anyone has the same problem?

BabboDemonio said:
Hi, I have this problem.. I flashed the official lollipop image yesterday and after that, TWRP,all using fastboot commands. The fact is that TWRP works the first time after I Install it.. But then it stops working, and instead of booting into recovery, it display the Android symbol with a red exclamation mark over it. Anyone has the same problem?
Click to expand...
Click to collapse
Yeah, same here

siddlv said:
So the latest TWRP works with the official release LRX21O?
Click to expand...
Click to collapse
Yep
BabboDemonio said:
Hi, I have this problem.. I flashed the official lollipop image yesterday and after that, TWRP,all using fastboot commands. The fact is that TWRP works the first time after I Install it.. But then it stops working, and instead of booting into recovery, it display the Android symbol with a red exclamation mark over it. Anyone has the same problem?
Click to expand...
Click to collapse
Did you use chainfire root method?
Sent from my Android 5.0 Nexus 5

Ben36 said:
Yep
Did you use chainfire root method?
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
I flashed lollipop image using flash-all script and then I flashed the recovery manually using fastboot with the phone in bootloader mode

BabboDemonio said:
I flashed lollipop image using flash-all script and then I flashed the recovery manually using fastboot with the phone in bootloader mode
Click to expand...
Click to collapse
Weird... Mine works but I fastboot'd just boot and system img and then booted into recovery and wiped caches before booting up
Sent from my Android 5.0 Nexus 5

Ben36 said:
Weird... Mine works but I fastboot'd just boot and system img and then booted into recovery and wiped caches before booting up
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
A friend of mine has the same problem

On that first time it works, did you flash supersu 2.19?
Sent from my Android 5.0 Nexus 5

Ben36 said:
On that first time it works, did you flash supersu 2.19?
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
Yes.. But then it stopped working again

BabboDemonio said:
Hi, I have this problem.. I flashed the official lollipop image yesterday and after that, TWRP,all using fastboot commands. The fact is that TWRP works the first time after I Install it.. But then it stops working, and instead of booting into recovery, it display the Android symbol with a red exclamation mark over it. Anyone has the same problem?
Click to expand...
Click to collapse
Same problem, I don t know why

Could it be linked to AOSP branch? http://forum.xda-developers.com/google-nexus-5/general/warning-lollipop-aosp-roms-broken-t2930512

Primokorn said:
Could it be linked to AOSP branch? http://forum.xda-developers.com/google-nexus-5/general/warning-lollipop-aosp-roms-broken-t2930512
Click to expand...
Click to collapse
The fact is that it didn't happen while I had dev preview.. But my recovery at the time was Phil'z

BabboDemonio said:
The fact is that it didn't happen while I had dev preview.. But my recovery at the time was Phil'z
Click to expand...
Click to collapse
There are obviously differences between the previews and the final factory imgs but I don't think it depends on the recovery you had/have.

Primokorn said:
There are obviously differences between the previews and the final factory imgs but I don't think it depends on the recovery you had/have.
Click to expand...
Click to collapse
Unfortunately the problem seems to be random, a user said that he flashed the recovery a second time and it didn't happen again (I tried that without success) another one didn't experience the problem... Don't know

BabboDemonio said:
Unfortunately the problem seems to be random, a user said that he flashed the recovery a second time and it didn't happen again (I tried that without success) another one didn't experience the problem... Don't know
Click to expand...
Click to collapse
Found a solution. Install with adb CF auto root by chainfire (on his thread) and then put recovery.IMG always with adb. All work now

YOG4PAS2QL bricks my OPO

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