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

[Q] Can't upgrade to 10.6.1.14.10 in TWRP

Hi,
I'm no expert in flashing tablets but I have done a few phones in the past, but I'm stuck with a problem trying to get the firmware file (10.6.1.1.10) upgraded to my Jellybean 4.2.1 install, so that I can eventually get CROMI-X on my tablet. I had '10' on my TF700 via OTA and downgraded to '8' to get root (as per the CROMI-X instructions but I can't get '10' to load via TWRP, I just get "refresh failed. Please try again" I've tried shortening the filename-loading from SD card and Internal storage-redownloading the file but nothing changes. I did notice that when I boot into TWRP, it will say 'Updating partition tables' even before I attempt to flash the update and it will appear to be stuck at this point after checking the .md5 file.
Can anyone offer any suggestions or anything I can try without bricking the thing?

Argenti12 said:
Hi,
I'm no expert in flashing tablets but I have done a few phones in the past, but I'm stuck with a problem trying to get the firmware file (10.6.1.1.10) upgraded to my Jellybean 4.2.1 install, so that I can eventually get CROMI-X on my tablet. I had '10' on my TF700 via OTA and downgraded to '8' to get root (as per the CROMI-X instructions but I can't get '10' to load via TWRP
Click to expand...
Click to collapse
Any 10.6.1.14.x bootloader is compatible with CROMI-X 5.x, so you don't need to upgrade to .10.

_that said:
Any 10.6.1.14.x bootloader is compatible with CROMI-X 5.x, so you don't need to upgrade to .10.
Click to expand...
Click to collapse
So you think I can just go ahead and install CROMI-X now? For future reference, is the 'Updating partition details' in TWRP normal? I don't remember seeing this when I first installed.
Thanks for the help.

Argenti12 said:
So you think I can just go ahead and install CROMI-X now?
Click to expand...
Click to collapse
To be 100% sure, check in the bootloader menu (before you select RCK) that your bootloader build version is 10.6.1.14.x, with x either 4, 8, or 10.
Argenti12 said:
For future reference, is the 'Updating partition details' in TWRP normal?
Click to expand...
Click to collapse
Yes.

_that said:
To be 100% sure, check in the bootloader menu (before you select RCK) that your bootloader build version is 10.6.1.14.x, with x either 4, 8, or 10.
Yes, its '8'.
Yes.
Click to expand...
Click to collapse
I was going to just try and install Cromi but now TWRP doesnt see the downloaded .zip!
This is becoming a headache.

Argenti12 said:
I was going to just try and install Cromi but now TWRP doesnt see the downloaded .zip!
This is becoming a headache.
Click to expand...
Click to collapse
Did you browse to the right folder that has the cromi zip file? In TWRP, you can select the internal sd or external sd. Make sure that you have selected the right sd card...

LetMeKnow said:
Did you browse to the right folder that has the cromi zip file? In TWRP, you can select the internal sd or external sd. Make sure that you have selected the right sd card...
Click to expand...
Click to collapse
Okay, I redownloaded the ROM file and copied it to the SD...plugged it back in the tablet and booted into TWRP, ....now I see both! oh well, I installed the ROM and now have CROMI-X running on this baby! Thanks for your help and advice guys.
One small thing that I noticed, again with TWRP is that when I invoke the power menu, I don't get any options to boot to recovery...or anything non-standard for that matter. I think my TWRP might be broken, is there a way to uninstall/reinstall?
Thanks again guys.

Argenti12 said:
Okay, I redownloaded the ROM file and copied it to the SD...plugged it back in the tablet and booted into TWRP, ....now I see both! oh well, I installed the ROM and now have CROMI-X running on this baby! Thanks for your help and advice guys.
One small thing that I noticed, again with TWRP is that when I invoke the power menu, I don't get any options to boot to recovery...or anything non-standard for that matter. I think my TWRP might be broken, is there a way to uninstall/reinstall?
Thanks again guys.
Click to expand...
Click to collapse
TWRP on tf700t, you have only two options on the boot menu. One is a reboot to your system. Second is power off your device.
About the uninstall/reinstall, all you need is to flash the TWRP blob on top of your existing one....
Edit: I think that your TWRP is working properly. If you don't have to flash your custom recovery again, you can minimize the risk of brick your device. Please don't mess with your bootloader and your recovery unless you must touch them for a good reason. Otherwise, just leave them alone. Just my two cents....

LetMeKnow said:
TWRP on tf700t, you have only two options on the boot menu. One is a reboot to your system. Second is power off your device.
About the uninstall/reinstall, all you need is to flash the TWRP blob on top of your existing one....
Edit: I think that your TWRP is working properly. If you don't have to flash your custom recovery again, you can minimize the risk of brick your device. Please don't mess with your bootloader and your recovery unless you must touch them for a good reason. Otherwise, just leave them alone. Just my two cents....
Click to expand...
Click to collapse
Great, thanks for clearing up that doubt...and also for the good advice! I'm already enjoying the CROMI-X experience!

[Q] Force OTA udpate?

Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!

Nikojiro said:
Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!
Click to expand...
Click to collapse
I'm having the same issue. No idea, we might just have to wait a while.

Delete Data from Google Framework Apk and then start the Update Checker.

UNCUT88RAW said:
Delete Data from Google Framework Apk and then start the Update Checker.
Click to expand...
Click to collapse
Aah didn't think of that trick, it works, <thank you> pressed :laugh:

Could someone please give me a link to the Stock Recovery and maybe a description what the best way is to flash it instead of the Custom Recovery? Thanks ...

I have had no problems flashing updates with ClockWorkMOD revocery.
However if you have the 1.0 version from http://forum.xda-developers.com/showthread.php?t=2390389 the update will fail with an error.
1.0 had a name wrong that makes it think the update are for a different device.
the command to flash the stock recovery (if every thing is in the correct place) is "fastboot flash recovery recovery.img"

chevyowner said:
1.0 had a name wrong that makes it think the update are for a different device.
Click to expand...
Click to collapse
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!

fquadrat said:
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!
Click to expand...
Click to collapse
When I was checking to see if I had 1.1 I found the naming error is still there.
This brings me to my next point. I had edited the ramdisk on 1.0 to correct the naming error, and not updated to 1.1
Here is a link to 1.1 with the edited ramdisk.
Update
I messed up the link in Google drive i think i fixed it now.

chevyowner said:
Here is a link to 1.1 with the edited ramdisk.
Click to expand...
Click to collapse
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.

fquadrat said:
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.
Click to expand...
Click to collapse
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"

chevyowner said:
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
Sorry, I just flashed stock recovery and my Shield is installing Android 4.3 right this second ...

chevyowner said:
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?

desertflame said:
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?
Click to expand...
Click to collapse
should be

Photon Failed to hab check for recovery: 0x56

So, I got my Photon Q today and I've already unlocked it and I was trying to install TWRP but I messed up somehow.. It still boots into the stock Android ROM and works fine but whenever I try to go into the recovery/Fastboot (Whatever it's called) I get this screen with some info text. At the bottom it says this:
Failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
Whenever I try to flash a recovery with an app it always succeeds but I still get this screen when I try to go into the recovery. Help me.

Have you tried doing 'fastboot flash recovery recovery.img' instead of using 'apps' to flash recovery?

arrrghhh said:
Have you tried doing 'fastboot flash recovery recovery.img' instead of using 'apps' to flash recovery?
Click to expand...
Click to collapse
I have. It says "Preflash validation failed" and nothing on the phone changes. This is really frustrating.

Cwazywazy said:
I have. It says "Preflash validation failed" and nothing on the phone changes. This is really frustrating.
Click to expand...
Click to collapse
Where do you get this error? I've never heard of fastboot spitting out such an error...
I assume you're in fastboot mode when you try this? What does 'fastboot devices' output?

arrrghhh said:
Where do you get this error? I've never heard of fastboot spitting out such an error...
I assume you're in fastboot mode when you try this? What does 'fastboot devices' output?
Click to expand...
Click to collapse
Nevermind, I figured out how to unlock the bootloader and TWRP finally installed successfully.
The only rooting/custom ROM stuff I've done is with my Nexus 7 and that wasn't as hard as this was.

Cwazywazy said:
Nevermind, I figured out how to unlock the bootloader and TWRP finally installed successfully.
The only rooting/custom ROM stuff I've done is with my Nexus 7 and that wasn't as hard as this was.
Click to expand...
Click to collapse
Oh, your bootloader was still locked...
That would do it! Glad you got it working. I hadn't seen that message before, but it makes sense now why I've never seen it before . My Q was unlocked immediately after unboxing!

arrrghhh said:
Oh, your bootloader was still locked...
That would do it! Glad you got it working. I hadn't seen that message before, but it makes sense now why I've never seen it before . My Q was unlocked immediately after unboxing!
Click to expand...
Click to collapse
I have a new problem.. I flashed the latest stable CyanogenMod and it wouldn't boot. (Boot animation just kept on going) So I went into TWRP and tried to do a wipe. For some reason it says "Unable to mount /data" or "internal storage". Even if I go into advanced wipe and choose everything but the external SD card it fails to mount any of it..

Cwazywazy said:
I have a new problem.. I flashed the latest stable CyanogenMod and it wouldn't boot. (Boot animation just kept on going) So I went into TWRP and tried to do a wipe. For some reason it says "Unable to mount /data" or "internal storage". Even if I go into advanced wipe and choose everything but the external SD card it fails to mount any of it..
Click to expand...
Click to collapse
I've heard of other people complaining about this on TWRP.
You should either a) use OpenRecovery or another recovery... or b) use an older version of TWRP. I'm on 2.6.3.1 and it works _flawlessly_.
I haven't had time to update to the latest versions of TWRP to investigate this issue.
As for your CM issue, make sure you wipe (using a recovery that works haha) and also make sure you give it plenty of time to do the first boot - there is sometimes a fsck process which runs at boot and takes a lot longer than usual for the device to actually boot up.

Please help me. I can't find any solution and I can't boot into CMod.

Cwazywazy said:
Please help me. I can't find any solution and I can't boot into CMod.
Click to expand...
Click to collapse
I gave you a solution, please at least try it.

arrrghhh said:
I gave you a solution, please at least try it.
Click to expand...
Click to collapse
Oh. I didn't see that, sorry. Trying it now.

arrrghhh said:
I gave you a solution, please at least try it.
Click to expand...
Click to collapse
Nope. Didn't work. Gave CM about 30 minutes to boot with no luck.

Cwazywazy said:
Nope. Didn't work. Gave CM about 30 minutes to boot with no luck.
Click to expand...
Click to collapse
Without logs I don't know what the issue would possibly be...
I would suggest trying CM10.2 perhaps? Or pull logs (adb logcat) from the failed boot of CM11. Like I said, that fsck process can take a very long time. I haven't personally experienced it, but I recall hearing reports of it taking upwards of an hour - either way, without logs, we don't really know what is going on.

arrrghhh said:
Without logs I don't know what the issue would possibly be...
I would suggest trying CM10.2 perhaps? Or pull logs (adb logcat) from the failed boot of CM11. Like I said, that fsck process can take a very long time. I haven't personally experienced it, but I recall hearing reports of it taking upwards of an hour - either way, without logs, we don't really know what is going on.
Click to expand...
Click to collapse
Here you go. Thanks for trying to help me (I zipped the file so I could use the uploader.)

Cwazywazy said:
Here you go. Thanks for trying to help me (I zipped the file so I could use the uploader.)
Click to expand...
Click to collapse
Not what I was expecting, but this does show an issue with recovery... What is the issue, I am a bit baffled by. I was hoping for a logcat from the CM11 failed boot.
Can you try another recovery? TWRP seems to be failing all over the place for you, even the version that is working fine for me
TWRP is failing to mount a lot of partitions, which is obviously unacceptable. I'm still not sure why the older version wouldn't work for you...

arrrghhh said:
Not what I was expecting, but this does show an issue with recovery... What is the issue, I am a bit baffled by.
Can you try another recovery? TWRP seems to be failing all over the place for you, even the version that is working fine for me
Click to expand...
Click to collapse
I don't know, I tried Clockwork mod which had the same problems. Are there any others I can try?
I was an idiot and I forgot to back up the stock ROM before I flashed CMod..

Cwazywazy said:
I don't know, I tried Clockwork mod which had the same problems. Are there any others I can try?
I was an idiot and I forgot to back up the stock ROM before I flashed CMod..
Click to expand...
Click to collapse
OpenRecovery?

arrrghhh said:
OpenRecovery?
Click to expand...
Click to collapse
I downloaded TWRP from here: http://goo.im/devs/OpenRecovery/asanti which has OpenRecovery in the name so I dunno...

Cwazywazy said:
I downloaded TWRP from here: http://goo.im/devs/OpenRecovery/asanti which has OpenRecovery in the name so I dunno...
Click to expand...
Click to collapse
No, not TWRP... OpenRecovery.
[25-11-2013] Photon Q Open Recovery 2.09
The links may not work in the OP, see here.
It's similar to CWM, but made specifically for the Q. Doesn't seem to have issues like TWRP, as it hasn't been updated in a while and it "just works". I'm still trying to sort out the issues with TWRP, why they affect some devices but not all.

arrrghhh said:
No, not TWRP... OpenRecovery.
[25-11-2013] Photon Q Open Recovery 2.09
The links may not work in the OP, see here.
It's similar to CWM, but made specifically for the Q. Doesn't seem to have issues like TWRP, as it hasn't been updated in a while and it "just works". I'm still trying to sort out the issues with TWRP, why they affect some devices but not all.
Click to expand...
Click to collapse
Ugh. Not working.
It says failed to mount /whatever (Invalid argument)

update to latest OTA and recovery issue

HI all, I have CM12 installed on my rooted phone and this morning when I switched it on, I got a message saying:
"WARNING: Update Cyanogen recovery is disabled. This may cause issues with updating your device. Please enable Update Cyanogen recovery in developer options"
Now, that option is off because I have my custom recovery TWRP installed on the phone, I'd like to keep that and I don't want to reinstall it after the update, so I believe I should ignore the message, but what I wanted to check with you guys is whether ignoring it will in fact cause any issues as this is the first time ever I've seen this message (this update by the way I think is the first one after installing CM12).
Any idea?
thanks

Disregard the message.

Thanks Heisenberg,
I did that but when the phone restarts trying to install the update, it goes straight into recovery mode (TWRP) and from there I don't think I can install the update, as none of the options seem to allow me to do so, see screenshot http://s23.postimg.org/6d6s7wyq3/IMG_20150625_135453.jpg

All right, I downloaded the zip from here http://cyanogen-ota-bacon.somee.com/ and tried to flash it from TWRP, but I get an error, screenshot here http://s28.postimg.org/zb06wtcpp/OTA_error.jpg, any idea why?

Same here, got an error in TWRP logs that prevented the update to install.
I'd like to avoid reflashing stock recovery only to install the update...
Heres the log: http://s29.postimg.org/njqqqlfc7/Screenshot_2015_06_25_08_49_42.png
Seems something related to outdated "build fingerprint" my device has currently 12.0-YNG1TAS17L

I guess the alternative would be to do it thru Cyanogen Recovery, but let's see what more knowledgeable members have to say as, like you, I don't want to have to reinstall TWRP and SU just for the sake of the update

Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official

Thanks for clarifying that davebugyi, then so be it, I'll do it thru cyanogen recovery and then reflash TWRP and probably SU as well
thanks
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse

Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse

duratto said:
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
Click to expand...
Click to collapse
For example here: http://forum.xda-developers.com/showthread.php?t=2810365

thanks! Ah OK I see so that's the whole ROM there as opposed to just an update

davebugyi said:
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
Click to expand...
Click to collapse
Do you mean flashing only this update found at the end of the first post?
YNG1TAS2I3 Radio, etc - Mirror - Same as YNG1TAS0YL
md5 - 6d5db5af6c92b814b9a0ebd18341dd8e
Click to expand...
Click to collapse
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?

Yes, but if I'm not mistaken, judging from the file size, that's the whole ROM
tsnake said:
Do you mean flashing only this update found at the end of the first post?
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Click to expand...
Click to collapse

The file I quoted is not a whole ROM, it's 31 MB.

AH OK, sorry I thught you referred to the 500mb file

Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.

I'm having the same issue. Anyone?

Got the same problem. Any idea?

duratto said:
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
Click to expand...
Click to collapse
Bump for a fix?

Juergen1337 said:
Got the same problem. Any idea?
Click to expand...
Click to collapse
The solution seems to be installing the new ROM provided. Related problem here http://forum.xda-developers.com/oneplus-one/help/twrp-cm-android-version-mismatch-t3147658