Hey guys, android 5.0 has been causing many of my apps to crash. Before I installed it, I had to flash the stock rom 4.4.4 since it was rooted and had a twrp recovery. After successfully flashing the stock rom, I installed 5.0 through OTA. It's my third day with the new version and the problems are pretty bad; nearly all apps crash. I turned off my phone to see if restarting would help. After trying to turn it back on, the boot animation would be constantly running. I can get into fasboot mode but for recovery mode, there's a message saying "No command." The final problem is... I did not turn on USB debugging through the developer's options in the settings which means I can't flash/ downgrade to 4.4.4 or any other rom. Any help or suggestions would be greatly appreciated, my phone is basically a brick right now.
Thanks!
You don't need USB debugging to be on to flash through fastboot mode.
Just follow this http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 to flash again and it should work
I did not know that. Thanks a ton!!! :good:
I´m running Android 4.2.2 and now want to update straight to Android 5.0. Is that possible or do I have to update successively from 4.3 and higher?
I have already tried flash the google factory image and got stuck on the spinning circles for hours. Have tried the wipe cache and factory data reset, but nothing happens. So got back to 4.2.2.
Any idea on how i can taste Android 5.0 in my Nexus 4?
RodrigoBR said:
I´m running Android 4.2.2 and now want to update straight to Android 5.0. Is that possible or do I have to update successively from 4.3 and higher?
I have already tried flash the google factory image and got stuck on the spinning circles for hours. Have tried the wipe cache and factory data reset, but nothing happens. So got back to 4.2.2.
Any idea on how i can taste Android 5.0 in my Nexus 4?
Click to expand...
Click to collapse
Are you using the Nexus 4? This is the Nexus 5 thread. However all you need to do is unlock the bootloader then run the install for the factory 5.0 and wait like 15 mins for it to boot up the first time. If you want to keep data then that's a whole different story as flashing the factory image wipe contents of your sdcard. ALL OF IT!!
Jnewell05 said:
Are you using the Nexus 4? This is the Nexus 5 thread. However all you need to do is unlock the bootloader then run the install for the factory 5.0 and wait like 15 mins for it to boot up the first time. If you want to keep data then that's a whole different story as flashing the factory image wipe contents of your sdcard. ALL OF IT!!
Click to expand...
Click to collapse
Thanks for the answer! I was just wondering if there is any problem in updating it straight from 4.2.2 to 5.0. I'll try couple of times more and hope to get any luck!
Related
Hi guys! I am stuck with a dilemma if I should format my phone. I am quite aware of the dev tools as an IT student but this is the first time I've experienced this problem:
First I stupidly installed Nexus 5's Ambient Display mod without making a backup of the apk's affected resulting for I guess maybe a coincidence but I cannot install the 5.01 OTA as when I went back to the original recovery, I get the green Android logo and "Error" under.
So I flashed via the flash-all.bat the 5.01 stock firmware from Google but removed the userdata.img as I don't want to lose any of my files. It worked seamlessly. No lags, no crashes, bootloops, nothing.
Now, my problem is I want to get the Ambient Display 5.01 to run again, but this time when I tried installing CWM/TWRP via fastboot, it says okay then when I select recovery, it goes back to the Google logo then it boots normally.
What do you guys think is the problem? Should I re-flash the whole firmware? BTW I was able to root my phone the other day. So I don't know what's up. Any suggestions would be great. Thanks!
Remove the scripts in the ROM that flash stock recovery on boot. Then, fastboot flash the recovery of your choice.
http://forum.xda-developers.com/google-nexus-5/help/flash-recovery-stuck-dead-android-t2978052
Hi all,
I need the pros here. It's NOT the regular wipe/clean/factoryreset bla bla issue.
received OPO from china with colorOS. Having the strangest behavior ever! I just can't install cyanogenmod 44S.
First I'll describe what I did:
unlock bootloader + TWRP with root + installed 44S using that comes prerooted from here: http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-4-4-4-xnph44s-t2932551
device stuck on boot (powered by android msg)
wipe dalvik/cache didn't help.
wiped again ((format dalvik cache data system) and installed using fastboot official 44s from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
eventually after almost having a heart attack and trying all the permutation of wiping/installing official/unofficial cyanogem 44S - I thought installing an older version.
I can'ts emphasize how many times and effort I put into installing 44S.
I then wiped everything again (format dalvik cache data system), rebooted to recovery and installed 25s official.
It's working!
now I try to update but OTA doesn't find anything. tried reverting to cyanogenmod recovey also but that didn't help.
so I thought installing the zips one by one (the OTA ones) but that doesn't work because I get error executing updater binary in zip and something with apache.xml
In addition, I hate the fact I don't have native OTA...
Please help me upgrade to 44s and if possible - restore OTA functionality. I have this strange feeling that I destoryed something in the device internally or something. I don't see a reason why 44S won't work on my device after having full wipe....
I love you all please help!!! Thanks!!!!
p.s - One time I did succeed booting to 44S but when I reset the device (after factory reset) It was stuck again in boot screen.
Exactly what happens when you flash the 44S fastboot images? Can you please copy/paste the text from the command prompt here?
Transmitted via Bacon
I can flash using fastboot 44s without any issues. But after that I can't pass the "developed by android" boot screen...
Just tried again and this is the fastboot log: http://pastebin.com/TyaBn85F
Everything seems ok.
Does the fastboot zip that comes from cyanogenmod download page includes the stock kernel as well?
Did you wait enough time for it to boot? I find initial bit after a flash takes quite a long time. Sometimes up to 5 min
Sent From Lollipopified Bacon Goodness!
ron.r said:
I can flash using fastboot 44s without any issues. But after that I can't pass the "developed by android" boot screen...
Just tried again and this is the fastboot log: http://pastebin.com/TyaBn85F
Everything seems ok.
Does the fastboot zip that comes from cyanogenmod download page includes the stock kernel as well?
Click to expand...
Click to collapse
Yes it does, that's the boot partition.
Transmitted via Bacon
ek69 said:
Did you wait enough time for it to boot? I find initial bit after a flash takes quite a long time. Sometimes up to 5 min
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
i'm 20 minutes since installing. still boot screen.
I suspect it's something to do with either Color OS that came with my device handles file differently and left some buggy stuff that cyanogemnod can't handle OR cyanogenmod changed the ROM in 44s to raise somekind of a flag for china OPO (however with 25 I still can't use OTA or manual OTA zip)
It really sucks...I don't know what else to do.
Is there a special cleaning methodology I can use? (except format system/data/cache/dalvik from TWRP) to make the device as clean as possible before installing using fastboot?
Try reading the color os thread. There has to be someone who wanted to go from color os to another os and maybe there's a different way for that
Sent From Lollipopified Bacon Goodness!
ek69 said:
Try reading the color os thread. There has to be someone who wanted to go from color os to another os and maybe there's a different way for that
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
Actually Iv'e been stuck on google (xda especially) trying to find answers for the past two days...and nada...
ron.r said:
Actually Iv'e been stuck on google (xda especially) trying to find answers for the past two days...and nada...
Click to expand...
Click to collapse
Go back to Stock Color Os and try this. Might just work.
https://forums.oneplus.net/threads/oneplus-one-coloros-to-cm11s-the-right-way.77361/
and no I am not a pro
Thanks. Saw that link. Just thought it's usless to go back to Color OS and do the whole process again...
UPDATES:
was able to install 33R using fastboot and everything works amazing including OTA...
BUT - after updating to 38R I have the same issue again. The device doesn't pass the boot screen.
UPDATE 2: After going to sleep frustrated with the device Off I woke up and tried to turn it on - and - it's working. how weird is that?
UPDATE 3: with 38R working (I really don't know how) I got OTA to 44S. I gladly updated. after pressing 'Install Update' the device turned off and didn't show the regular update script running in TWRP. Now the device stuck on boot screen again...so i'm back to square one.
Could it be that cyanogen changed something to block china versions?
UPDATE 4: turned the device in recovery mode and the update script (from 38R to 44S) ran immediately and when it's done it restarted the device.
The device is now back on. seems to be working with 44s. I'll do some more tests and if everything is fine i'll mark as solved.
BTW - the magic was probably installing 33R and from there start updating using OTA. However I don't know how to explain that after 38 OTA and short night sleep the device decided to wake up and work...
Ok. I know what's happening but I can't explain that.
Unless the device is powered off and after 30 seconds turned on - there's no way to pass the boot screen.
Restarting normally from working state doesn't work, restarting from recovery, power off and power on immediately doesn't work as well.
The ONLY way for me to pass the boot screen is to power the device off completely, go drink a small beer, come back (30 seconds is enough) and turn the device on.
Any advice???
ron.r said:
UPDATE 4: turned the device in recovery mode and the update script (from 38R to 44S) ran immediately and when it's done it restarted the device.
The device is now back on. seems to be working with 44s. I'll do some more tests and if everything is fine i'll mark as solved.
BTW - the magic was probably installing 33R and from there start updating using OTA. However I don't know how to explain that after 38 OTA and short night sleep the device decided to wake up and work...
Click to expand...
Click to collapse
Hello RON,
I'm in the same situation; did you solve the problem?
Briefly follows my tests:
- after updating from OTA to 44S the opo stuck at logo.
- reflashed the stock 38r...
- Applied 44s update from recovery but after restart the system stuck.
- installed the calkulin 44S and radio file from twrp... the opo stuck at logo "1"
- FLASHED stock 44s and new kernel from https://cyngn.com/products/oneplusone/ : stuck at logo.
gioninardo said:
Hello RON,
I'm in the same situation; did you solve the problem?
Briefly follows my tests:
- after updating from OTA to 44S the opo stuck at logo.
- reflashed the stock 38r...
- Applied 44s update from recovery but after restart the system stuck.
- installed the calkulin 44S and radio file from twrp... the opo stuck at logo "1"
- FLASHED stock 44s and new kernel from https://cyngn.com/products/oneplusone/ : stuck at logo.
Click to expand...
Click to collapse
reboot to recovery
it should install the 44s update
then restart normally.
if stuck on boot - turn the device off. after 30 seconds turn it on.
that worked for me.
ron.r said:
reboot to recovery
it should install the 44s update
then restart normally.
if stuck on boot - turn the device off. after 30 seconds turn it on.
that worked for me.
Click to expand...
Click to collapse
thank you.
Already done... but without result!
Just flash the 44S ROM using fastboot. You can find them on the forum.
Why flash an old ROM and uwe OTA if the most updated ROM is available...
Help Please!!! I need help reloading my Moto G 2013. I had android 5.0.1 running on it but I was not able to perform a device wipe. I read somewhere that encrypting and decrypting could be a workaround, so I decided to do that. Encrypting took less than 10 mins and the hone got stuck in a restart loop. So I tried flashing it with ADB and now I get the android man laying fat with the red triangle. I am guessing no more operating system.
I have tried making use of adb to load the rom but I keep getting the error no device found. I have tried every single process online. It is the google play edition xt1032 I have.
Thank you.
Can u reach recovery mode? Or bootloader
tdjeans said:
Help Please!!! I need help reloading my Moto G 2013. I had android 5.0.1 running on it but I was not able to perform a device wipe. I read somewhere that encrypting and decrypting could be a workaround, so I decided to do that. Encrypting took less than 10 mins and the hone got stuck in a restart loop. So I tried flashing it with ADB and now I get the android man laying fat with the red triangle. I am guessing no more operating system.
I have tried making use of adb to load the rom but I keep getting the error no device found. I have tried every single process online. It is the google play edition xt1032 I have.
Thank you.
Click to expand...
Click to collapse
That red triangle android robot is stock recovery. There should be a hardware key combination to wipe cache try searching on google. If all else fails then reboot to bootloader by using hardware key combination and perform a factory reset using fastboot.
Thank you for the help. I was able to get it fixed by flashing TWRP and the sideloading 4.4.4 on the phone. But I noticed the screen flickers for the first few minutes the phone is on. I also tried to update to 5.0.1 via OTA but after download, the phone restarted and instead of installing the 5.0.1, it booted to TWRP recovery. I want to know if I follow the instructions on http://forum.xda-developers.com/showthread.php?t=2542219, will I be able to remove the TWRP and have my stock recovery back and then be able to update via OTA. Also, I noticed I still cannot do a factory reset, the phone just restarts and everything remains the same.
skyguy126 said:
That red triangle android robot is stock recovery. There should be a hardware key combination to wipe cache try searching on google. If all else fails then reboot to bootloader by using hardware key combination and perform a factory reset using fastboot.
Click to expand...
Click to collapse
tdjeans said:
Thank you for the help. I was able to get it fixed by flashing TWRP and the sideloading 4.4.4 on the phone. But I noticed the screen flickers for the first few minutes the phone is on. I also tried to update to 5.0.1 via OTA but after download, the phone restarted and instead of installing the 5.0.1, it booted to TWRP recovery. I want to know if I follow the instructions on http://forum.xda-developers.com/showthread.php?t=2542219, will I be able to remove the TWRP and have my stock recovery back and then be able to update via OTA. Also, I noticed I still cannot do a factory reset, the phone just restarts and everything remains the same.
Click to expand...
Click to collapse
In order to do any factory resets or ota you must have stock recovery installed or else android cannot communicate properly with recovery for commands and such.
Ok. Thank you. I have reloaded to stock firmware and done an OTA update to 5.0.1.
skyguy126 said:
In order to do any factory resets or ota you must have stock recovery installed or else android cannot communicate properly with recovery for commands and such.
Click to expand...
Click to collapse
I finally was able to with TWRP.
instinctblade said:
Can u reach recovery mode? Or bootloader
Click to expand...
Click to collapse
Hey guys,
I haven't touched my Nexus 5 for a while and today I picked it up for some development actions. Atleast that was my purpose. I booted it and I saw it was still running the Lollipop 5.0 beta from a year a go. I immediately downloaded the lmy47i 5.1 Nexus 5 Hammerhead factory image and flashed it (using the flash-all file).
However, it was stuck at the boot animation (spinning dots) for over an hour. So I erased user data and cache (fastboot erase -w) and then flashed it, with a new fresh clean download of 5.1 again. Let it go again, but after an hour still no go.
When I loaded it into fast boot mode, I did not had to unlock it again, since it was still unlocked. But I guess that shouldn't make a difference.
I am running on a Mac, so NexusToolkit isn't an option, sadly..
Any suggestions?
Blackvibes said:
Hey guys,
I haven't touched my Nexus 5 for a while and today I picked it up for some development actions. Atleast that was my purpose. I booted it and I saw it was still running the Lollipop 5.0 beta from a year a go. I immediately downloaded the lmy47i 5.1 Nexus 5 Hammerhead factory image and flashed it (using the flash-all file).
However, it was stuck at the boot animation (spinning dots) for over an hour. So I erased user data and cache (fastboot erase -w) and then flashed it, with a new fresh clean download of 5.1 again. Let it go again, but after an hour still no go.
When I loaded it into fast boot mode, I did not had to unlock it again, since it was still unlocked. But I guess that shouldn't make a difference.
I am running on a Mac, so NexusToolkit isn't an option, sadly..
Any suggestions?
Click to expand...
Click to collapse
What happens when you flash a kitkat rom?
Hi guys,
I was still running 4.4.4 (KTU84P) for a while on my Nexus 5 and decided to flash up to Marshmallow. I flashed to LRX21O (5.0) first, then to LRX22C (5.0.1) successfully. I can get it to boot up fine as well. However, no matter how many times I try flashing LMY47D (5.1.0), I get stuck in a bootloop. I'm pretty sure it's a bootloop, as I'm stuck at the 4 floating dots, and I've waited for over an hour. I've tried using the flash-all.bat as well as flashing each img manually via adb.
Anyone have any suggestions/ideas? Am I missing something?
Are you also flashing the userdata.img file and performing a factory wipe before booting the phone for the first time with the newly flashed rom?
I am also flashing user data. I've been trying to get into recovery to do a factory wipe but whenever I hold Vol up and power, I end up at the Android with the red triangle
Okay, this can be closed. I ended up flashing another version over it and it seemed to have cleared up.