Database Users

[Q] Stuck @ google logo

hi,
last day i flashed cyanogen 7.1 stable mod for defy.
it was working nicely
later on i wiped the system and and installed the backup of stock 2.2.2 using clockworkmod recovery, it also worked without any problems
again i wiped the system cache and installed cyanogen again ,but this time i got stuck at the cyanogen logo which comes in loop, so i flashed again but no positive
after that i entered into recovery mod and cleared the system cache and data
after this i got stuck at google logo,(still able to enter into default recovery mod, but i cannot enter into clockworkmod recovery)
plz help urgently
thanks

when this happened to me i had to flash a whole sbf to get things right.

exorz said:
when this happened to me i had to flash a whole sbf to get things right.
Click to expand...
Click to collapse
thanks
i will try it

i flashed stock froyo got from xda, back to normal
thanks thanks a lot
a million thanks

you're welcome. glad i could help out

Hi,
I am having the same problem.. I have followed the tutorial: http://wiki.cyanogenmod.com/wiki/Motorola_Defy:_Full_Update_Guide
With the only exception of this part:
On the computer, open terminal and run the following commands:
Code:
adb shell
su
cp -R /sdcard/bootmenu /data/bootmenu
For some reason the bootmenu directory was not present in the sdcard directory, so I created the directory myself and pushed the files for the bootloader 1 at a time (individually).
Everything goes well, until, after the installation, I reboot the phone. It stays on the Google logo. I have tried with and without the Google-Apps pack, but the result is still the same.
To get the phone back on track, I use the sbf file presented in this tutorial:
http://forum.xda-developers.com/showthread.php?t=1216982
Any idea on what is happening?
I have tried clearing the cache and factory settings, but to no avail as well.
I have also tried a nightly build, but this time it gets stuck on the Motorola logo... tired clearing cache and factory settings... no use.

flashed to stock rom from CM9; now endless errors/reboot7

I received my new Nexus 7 today (although I'll be sending it back for RMA replacement due to defective/blown speakers, but that's another discussion) and wanted to revert my Kindle Fire to stock to give to my parents. I had been previously running a vanilla build of CM9.
I downloaded Amazon's latest software update, renamed it update.zip, and copied it to my device. Using TWRP, I installed the update, wiped cache and dalvik. My Kindle rebooted (now without FireFireFire bootloader/recovery), however, once it starts I get multiple error messages as follows:
android.process.acore has stopped unexpectedly
com.android.providers.calendar has stopped unexpectedly
My only options are to force quit. Still, even if I don't touch the device and let it be, it will reboot itself withing a minute or so. There must be something amiss with how I went back to stock.
Any help with getting the device back into some working form? Or am I out of luck?
Nevermind; i managed to get FireFireFire and TWRP back on. Now to look for an edited Amazon ROM or perhaps a jellybean/CM10 rom...

when flashing the stock rom from cm9, you should do a full wipe ( system, factory reset, cache, dalvik) in TWRP
Sent from my Amazon Kindle Fire using xda premium

Josepho1997 said:
Try to root it again with KFU, and then redownload and reflash the update. Or turn your kindle completely off and then, in KFU, press install TWRP, and then turn your Kindle back on, and see if it can get into fastboot and install TWRP. Then turn it off, open off KFU, and press install FFF. Now turn it back on, and see if it installs FFF. If so, then just redownload and reflash the update.zip
Or install GR9 Modaco.
Click to expand...
Click to collapse
managed to install FireFireFire and TWRP during the brief window before the device rebooted. and thanks for the suggestion of GR9 Modaco

[Q] Please help! Stuck on boot screen!

I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?

danlk2 said:
I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
Click to expand...
Click to collapse
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.

irishrally said:
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
Click to expand...
Click to collapse
Wow, that didn't even cross my mind, I did this and I've got the rom up and running now. Thanks a lot.

HEL P...Nexus 10 Bricked...after rooting and installing custom rom

Hi:
I unlocked and successfully rooted my Nexus 10 (JB 4.3). Also have TWRP 2.6.1 installed. It worked fine with the stock rom rooted. Then I tried to install Custom Rom.. Paranoid Android..3.99. Everything went smooth until.I got stuck in BOOTLOOP. Reading the forums posts, I went back to recovery and wiped cache/dalvik cache.. and rebooted.. This time it proceeded with the ANDROID IS UPGRADING...but at the end of this once I got the lock screen..the dreaded UNFORTUNATELY SYSTEM UI has STOPPED window pops up and this is where I am stuck.
I have since then booted into recovery and cleaned cache and reinstalled custom roms.. PA, STOCK, CM 10.2 many times but of no use. The tablet is stuck at the SYSTEM UI HAS STOPPED.
Is there any way to fix this... ? ANY HELP WILL BE GREATLY APPRECIATED
I would be glad to get back to FACTORY SETTINGS if I can. Note that I can push files from my MAC using "ADB" and then use recovery.
THANK YOU IN ADVANCE FOR YOU ALL.
Edit: Well guess what... I did not see FACTORY RESET in TWRP all along (BEING DEFAULT ACTION) and was just wiping cache/dalvik cache before rebooting. FACTORY RESET is a life saver.... it works. Hope this helps others in similar situation. I am back on CM 10,2 and running.

Excellent. That was gonna be my suggestion, but glad you got it figured out.
Sent from my Nexus 10

vicky4112 said:
/snip
Click to expand...
Click to collapse
In the future, learn to use fastboot. ADB only helps you if you have a custom recovery that can run ADB onboard, which isn't always the case (for example, if you kill your internal storage). What could have saved you here would have been:
fastboot wipe userdata
fastboot wipe data
fastboot update -w /path/to/stock-image.zip
It's harder to kill fastboot on Nexus devices, so it's worth learning.

Rirere said:
In the future, learn to use fastboot. ADB only helps you if you have a custom recovery that can run ADB onboard, which isn't always the case (for example, if you kill your internal storage
Click to expand...
Click to collapse
Alternatively, TWRP can mount an otg-usb device. Totally saved my tush the other night.

[Q] Nexus 4 Bricked ?

I unlocked bootloader and rooted last night fine, this morning i was trying to flash cmod 10.2 through twrp and it said could not find md5 when flashing then it said it was flashed successfully. I did wipe the cache and dalvik and did a factory reset prior to attempting to flash. Yet when i hit reboot it only shows the google logo then the screen goes black and flickers between dark black and black. I know it takes time to boot the first time so i let it sit for 10 mins and nothing. Everything was working fine before this, the device still boots into fastboot mode and and i can get to twrp anything i can try through that ? Or is efants guide the only way to fix this. No Nandroid backup so ya i hate myself :crying:

BrownPride said:
I unlocked bootloader and rooted last night fine, this morning i was trying to flash cmod 10.2 through twrp and it said could not find md5 when flashing then it said it was flashed successfully. I did wipe the cache and dalvik and did a factory reset prior to attempting to flash. Yet when i hit reboot it only shows the google logo then the screen goes black and flickers between dark black and black. I know it takes time to boot the first time so i let it sit for 10 mins and nothing. Everything was working fine before this, the device still boots into fastboot mode and and i can get to twrp anything i can try through that ? Or is efants guide the only way to fix this. No Nandroid backup so ya i hate myself :crying:
Click to expand...
Click to collapse
Couple of things I would try first, re download CM 10.2 just to make sure you don't have a bad download and make sure you downloaded the correct file. Due your normal wipes then reflash. btw I never check the md5 box when flashing with TWRP. As long as you can get into recovery you should able to fix and always make a back up.

Ok i will give your suggestions a try and post back in a bit. Thanks for your help

If it's the CM10.2 nightly from 20130906, it's a known issue with it not booting. Flash an older nightly or another ROM.

I was unaware of the issues with this versioni thanks for that info. I can not push the zip file through adb i says device is offline, is there anyway to push the older cmod version through fastboot and install it with twrp on device ?
I miss having a device with a removable sdcard

BrownPride said:
I was unaware of the issues with this versioni thanks for that info. I can not push the zip file through adb i says device is offline, is there anyway to push the older cmod version through fastboot and install it with twrp on device ?
I miss having a device with a removable sdcard
Click to expand...
Click to collapse
Yup use adb sideload in TWRP : adb sideload path to rom/namerom.zip. Link http://teamw.in/ADBSideload.

Thank you for your response, going to follow the steps in the link hopefully i can solve this problem

Thank you all for your kind help and patience i was able to get cmod20130905 to flash through adb sideload and everything is working fine. First thing i did after it booted successfully was go back into twrp and make a backup Thanks again