Database Info

I think I may have messed up putting a new ROM on my phone

So I'm still extremely new to rooting/ROMS/ODIN etc. Well I finally decided to throw caution to the wind and attempt to root and install Slim Bean on my phone. Honestly I think because most help sites can't keep up to date with all the current ROM updates and what not that I may have messed something up. Also, before anyone rips my head off, I tried to post this question in the developers thread but I'm still to new. Anyways here's what I did:
Downloaded ODIN v1.85, SkyrocketCWMrecovery.tar, Slim Gapps and Slim-i727-3.1.0-OFFICIAL
I first ran ODIN (left all the check boxes alone as they appear when you start up), chose PDA, and chose SkyrocketCWMrecovery.tar to install.
Preformed install and rebooted my phone, everything works fine
Put Slim Gapps and Slim I727-3.1.0 onto my Internal SDCard
Disconnected phone from USB and started CWM (the version CWM is v5.0.2.6)
I wiped data/factory reset and under mounts and storage format/system
Then I installed Slim I727-3.1.0 and Gapps
I rebooted my phone and it starts loading, gets to the slim bean screen and stops
I've also tried Cyanogenmod 9.1 and 10. 9.1 does the same thing Slim bean does and 10 gets an Status 7 error, Installation aborted. I've read so many posts about this but nothing has seemed to fix my issue, at this point I would happily go back to a stock phone (I wish I'd just backed it up when I had the chance, live and learn I guess)
If someone can please help me, I'd really appreciate it.

Why using a Old Reciovery?
Head to ClockworkMod v6.0.2.7 Touch v14.4.6
Download the Latest Touch Recovery File and put it on your Sd Card and flash it Via Recovery.
After that Boot into Recovery
Format system (usually in mounts and storage menu option) X3
Format data X3
wipe data and cache partition X3
After that Flash the Rom.
In case if the Issue still persists revert back to Stock and Try Again..

manu44 said:
Why using a Old Reciovery?
Head to ClockworkMod v6.0.2.7 Touch v14.4.6
Download the Latest Touch Recovery File and put it on your Sd Card and flash it Via Recovery.
After that Boot into Recovery
Format system (usually in mounts and storage menu option) X3
Format data X3
wipe data and cache partition X3
After that Flash the Rom.
In case if the Issue still persists revert back to Stock and Try Again..
Click to expand...
Click to collapse
Ok, I got it to flash to the new version (the website I was using had the download for the old version I was using). However, when I try to wipe data and cache partition it tries to preform the action but it just sits on the screen saying formatting data....
I tried just loading cyanogenmod 10 on there and see if I got lucky, with the new version I can get the zip file to install but when I tried to reboot I get to the cyanogenmod screen and it just sits there..... any ideas?

You have to start learning doing things in the "correct" and "safe" way ..
1.Leave all other websites and stick here for the flashing and roms and what not.
2.Never use ODIN for anything ever (except for flashing stock ROM)
3.An exception also for using ODIN is the bone stock phone , you'll need ODIN to just flash a custom recovery in .tar format (this is usually just done once , even if a new recovery comes out , you update it also from a custom recovery) , once your device has a custom recovery (and a recent one) do everything from there as the custom recovery enables you to do everything from inside the recovery ..
4.Learn from the stickies here on the skyrocket section .

drkreign said:
Ok, I got it to flash to the new version (the website I was using had the download for the old version I was using). However, when I try to wipe data and cache partition it tries to preform the action but it just sits on the screen saying formatting data....
I tried just loading cyanogenmod 10 on there and see if I got lucky, with the new version I can get the zip file to install but when I tried to reboot I get to the cyanogenmod screen and it just sits there..... any ideas?
Click to expand...
Click to collapse
Ill recommend you to Flash Back to Stock Rom and then Try again.. with the Latest Recovery file

manu44 said:
Ill recommend you to Flash Back to Stock Rom and then Try again.. with the Latest Recovery file
Click to expand...
Click to collapse
Awesome, my phones back. As for trying again, I'm thinking I may skip that lol. I came from a jailbroken Iphone to trying this on my android but the android is 10x more complicated (read: way more options/routes to go to do the same thing, which is way to confusing for the first timers). Thanks for all your help!

mahanddeem said:
You have to start learning doing things in the "correct" and "safe" way ..
1.Leave all other websites and stick here for the flashing and roms and what not.
2.Never use ODIN for anything ever (except for flashing stock ROM)
3.An exception also for using ODIN is the bone stock phone , you'll need ODIN to just flash a custom recovery in .tar format (this is usually just done once , even if a new recovery comes out , you update it also from a custom recovery) , once your device has a custom recovery (and a recent one) do everything from there as the custom recovery enables you to do everything from inside the recovery ..
4.Learn from the stickies here on the skyrocket section .
Click to expand...
Click to collapse
Again, still new, but I don't think I used ODIN for anything other than installing the CWM recovery and even doing that (notably was directed to an older version) the ROMs wouldn't take. Even after upgrading the CWM to most updated version it still failed to get any version of cyan 9-10 or slim bean to work, all of them get to their respective screens and load. I even got tired, went to bed and 7 hours later the phone still wouldn't boot.
As far as I can tell I did everything this website has said to do, unless you can point me to something otherwise? Not to be rude, just trying to figure out where I would have messed up, but I just can't see where I'd have messed up OTHER than running a old version of CWM. But even that was corrected with an update and still I received the same results.

drkreign said:
Again, still new, but I don't think I used ODIN for anything other than installing the CWM recovery and even doing that (notably was directed to an older version) the ROMs wouldn't take. Even after upgrading the CWM to most updated version it still failed to get any version of cyan 9-10 or slim bean to work, all of them get to their respective screens and load. I even got tired, went to bed and 7 hours later the phone still wouldn't boot.
As far as I can tell I did everything this website has said to do, unless you can point me to something otherwise? Not to be rude, just trying to figure out where I would have messed up, but I just can't see where I'd have messed up OTHER than running a old version of CWM. But even that was corrected with an update and still I received the same results.
Click to expand...
Click to collapse
Also, not sure if anyone else is having this issue but when I try to format cache, either using wipe data/cache partition or going under mounts and storage format cache it locks up. Does data just fine but cache is a no go. I'd mention this in the development section but not enough post counts.

mahanddeem said:
4.Learn from the stickies here on the skyrocket section .
Click to expand...
Click to collapse
+1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Always read the stickies. Always read the stickies. Always read the stickies.
This is a magical mantra, if typed three times it comes true))

If you're having trouble with cwm, try flashing twrp. I find that it is easier to use for the basics.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

If your recovery is up to date and its just bootlooping after flashing, reboot into recovery and wipe cache & dalvik cache.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

[Q] Big problem while restoring backup

l have a S4 One S flashed with CianogenMod10, stable version (10.0) and Clockworkmod 5.8.3.1 (l've read around here that TWRP is a better option but l don't know how to switch or if it's advisable/possible right now)
l did a full nandroid backup with CWM while still at the stable and then proceeded to update to the latest version (which is cm-10.1-20130222-NIGHTLY) through the update option in the rom settings menu. As l thought it could happen, the phone was stuck at the white screen with htc written in green. "No problem, l'll just restore the backup" l thought, but then here comes the problem:
l like to keep backups more than in one place, so l made a copy of the backup in my laptop, but instead of clicking copy i clicked cut, so the files are no longer in the phone's memory (which as you know is not removable). Opening CWM and selecting mount USB storage doesn't work, it says it's unable to open ums lunfile.
Can anyone provide help or point me to a link with the info l need? l've searched around without much sucess
lf l need to install TWRP, are CWM backups compatible?
Oh by the way, the hboot version is 1.14 if that's needed for anything

l know it's not a nice move to bump the thread asking for help but l have some dependency in the phone and some of the data l keep inside, and the problem doesn't seem too complex to solve: l just need to access the internal storage from my computer
There has to be a way. Maybe through the command line?

fastboot flash the boot.img
... Im getting kinda tired of writing that now... anyone else?

You tried to flash 10.1 onto 10, that was your first mistake. Those are two different versions of jellybean. Presumably you did not wipe the cache or factory reset before you did that either. Good new is you can fix your mistake, just wipe the cache, dalvic and the system and relash your CM10. After you flash CM10 it should boot because you should still be using the kernel from CM10, which is why 10.1 would not boot.

impostle said:
You tried to flash 10.1 onto 10, that was your first mistake. Those are two different versions of jellybean. Presumably you did not wipe the cache or factory reset before you did that either. Good new is you can fix your mistake, just wipe the cache, dalvic and the system and relash your CM10. After you flash CM10 it should boot because you should still be using the kernel from CM10, which is why 10.1 would not boot.
Click to expand...
Click to collapse
So that was the problem... thanks for the explanation. l simply touched the "check for updates" button and applied the last one through the menu, l supposed it would be compatible.
Goatshocker said:
fastboot flash the boot.img
... Im getting kinda tired of writing that now... anyone else?
Click to expand...
Click to collapse
Oh, l forgot about that. l knew the solution had to be something simple. That extra remark was not necessary though.
...
l have a different problem now, and it doesn't look good.
When l try to flash the 10.0 stable version again there's no way to access the phone's internal storage. CWM gives me an "Error mounting /sdcard!" message every time l try to open it and the mount USB storage still doesn't work. Even when doing a factory reset it skips the SD card step after the message "Error mounting /sdcard/.android_secure!".
l need to put the CM10 zip file into the card to flash it. How can this be fixed?

I had the same problems with CWM recovery, so I switched to TWRP recovery and never had that problem again. You are going to need to flash back to stock recovery and clear storage from Fastboot. Then you will need to flash TWRP, from there you just need to do everything like normal.

impostle said:
I had the same problems with CWM recovery, so I switched to TWRP recovery and never had that problem again. You are going to need to flash back to stock recovery and clear storage from Fastboot. Then you will need to flash TWRP, from there you just need to do everything like normal.
Click to expand...
Click to collapse
Do you have any instructions for that? If not here just a link will be fine.
l was really worried about not finding a solution. Does the CWM nandroid backup work with TWRP?

You need to read this entire post, watch the videos and really understand it before moving forward. The worst thing you can do while flashing ROMS is jump in headfirst, you'll break your neck. You don't want to brick your phone, so being informed completely will really benefit you when trying to troubleshoot your problems. When you know all the steps backwards and forwards then you can figure out where you went wrong.

impostle said:
You need to read this entire post, watch the videos and really understand it before moving forward. The worst thing you can do while flashing ROMS is jump in headfirst, you'll break your neck. You don't want to brick your phone, so being informed completely will really benefit you when trying to troubleshoot your problems. When you know all the steps backwards and forwards then you can figure out where you went wrong.
Click to expand...
Click to collapse
Yes that's the post l used the first (and last) time l rooted/flashed the phone. l mean instructions to install TWRP. Are they just the same but with other files instead of CWM's? And is the backup compatible? l really need that data.

As far as I know they are not compatible. Either way you will need to flash stock recovery and clear the storage from Fastboot, then reflash CWM recovery before you can mount the SD card.

Thank you SO much impostle, everything is fixed and back to normal again. l'm even using TWRP now, it's miles better than CWM.
What l did was:
-flash back stock recovery and clear storage
-flash TWRP
-mount storage to PC and copy the ROM and backup inside
-flash CWM
-flash CM10 and restore the backup from the SD
-flash TWRP again
And all is good now. Thanks again :victory:

Rodrows said:
That extra remark was not necessary though.
Click to expand...
Click to collapse
True, but when youve hanged around here a while and answered similar questions at least once a day, where the mistake/solution is to fastboot flash the boot.img - you eventually start getting a bit frustrated.
It wasnt really ment to you per sé, but more of a general complaint.

Goatshocker said:
True, but when youve hanged around here a while and answered similar questions at least once a day, where the mistake/solution is to fastboot flash the boot.img - you eventually start getting a bit frustrated.
It wasnt really ment to you per sé, but more of a general complaint.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

BMM wont start on next boot up?

Hey guys i have a problem with BMM but i didnt have it before. Last night i FXZ to AT&T stock 4.0.4 firmware, and i install bootstrap and booted to CWM to restore my nandroid backup to Telecom NZ firmware. Then after I flashed ParanoidAndroid to system_1 and from there BMM is installed, i activated System_2 then I installed DirtyUnicorn in System_3. Every time i flash e.g tweak in any system i reboot and it says BMM will not start on next boot up. Why? i did not have this problem before i FXZ.

Cant go from bootstrapper to BMM.
start over and install BMM instead of bootstrapper.
FYI, what I just stated is listed in every ROM thread.

I did it before tho.

MotoMudder77 said:
Cant go from bootstrapper to BMM.
start over and install BMM instead of bootstrapper.
FYI, what I just stated is listed in every ROM thread.
Click to expand...
Click to collapse
It said before i reboot is to go to system keeper and remove bmm from main system?

Darell3 said:
It said before i reboot is to go to system keeper and remove bmm from main system?
Click to expand...
Click to collapse
Not sure if question or statement.
But if you removed it then that could be the problem. Along with bootstrapper beforehand.
I did same thing a while ago. But eventually got issues.
Fxz to ICS
Root
Install BMM and do all steps
Flash ROM.
Sent from my MB865 using Tapatalk 2

What exactly do you flash that causes BMM to disappear??
Do you reboot through BMM or the tweak/zip you flash has an option to reboot??
The latter causes problems with BMM including but not limited to loss of BMM,bootlooping etc
---------------------------------------------------
May the -Mass times Acceleration-be with You...

deveshmanish said:
What exactly do you flash that causes BMM to disappear??
Do you reboot through BMM or the tweak/zip you flash has an option to reboot??
The latter causes problems with BMM including but not limited to loss of BMM,bootlooping etc
---------------------------------------------------
May the -Mass times Acceleration-be with You...
Click to expand...
Click to collapse
I FXZ then i bootstrapped to restore my nandroid backup. After that i flashed ParanoidAndroid 3.65 as my system_1 and from there i flashed Dirty Unicorn on System_3. System_2 partition is activated. BMM works in every boot but after installing a zip or clearing cache etc.. i try to reboot to any system i guess it reboots fine but without BMM coming up.

Why would you FXZ and then restore? kinda defeats the purpose of FXZin
Dont use bootstrapper if you want BMM.

MotoMudder77 said:
Why would you FXZ and then restore? kinda defeats the purpose of FXZin
Dont use bootstrapper if you want BMM.
Click to expand...
Click to collapse
Because i want to keep TNZ firmware as my stock but, i could not install BMM that way for some reason, so i flashed ParanoidAndroid over it to get BMM.

Darell3 said:
Because i want to keep TNZ firmware as my stock but, i could not install BMM that way for some reason, so i flashed ParanoidAndroid over it to get BMM.
Click to expand...
Click to collapse
As soon as u flashed PA over it your stock firmware is gone.
I'd look into why BMM is not liking stock. If it's rooted then it should work. Should just have to install BMM from play store and follow steps.
Sent from my MB865 using Tapatalk 2

MotoMudder77 said:
As soon as u flashed PA over it your stock firmware is gone.
I'd look into why BMM is not liking stock. If it's rooted then it should work. Should just have to install BMM from play store and follow steps.
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Heres an example of flashing a zip, i just finished updating JBX Kernal and at end of every single zip i flash it says removing bmm from non-main system. (picture below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Bump.
Just need to know why it it removes BMM from non-main system!

Darell3 said:
I FXZ then i bootstrapped to restore my nandroid backup. After that i flashed ParanoidAndroid 3.65 as my system_1 and from there i flashed Dirty Unicorn on System_3. System_2 partition is activated. BMM works in every boot but after installing a zip or clearing cache etc.. i try to reboot to any system i guess it reboots fine but without BMM coming up.
Click to expand...
Click to collapse
If I'm reading you right, this is what's supposed to happen. If you "reboot to any system" then it will...reboot to that system. Because that's what you just asked it to do. BMM will be skipped because you chose to boot to a specific system.
If you just do a simple reboot, then the BMM logo will popup, and you can choose your system from there. Either way works.
And regarding "removing BMM from non-main system", that is because you only want it installed on your Main system. Flashing a ROM with BMM built-in onto System 3-6 means that it has to remove itself during the flash to prevent conflicts. This is normal.

quasihellfish said:
If I'm reading you right, this is what's supposed to happen. If you "reboot to any system" then it will...reboot to that system. Because that's what you just asked it to do. BMM will be skipped because you chose to boot to a specific system.
If you just do a simple reboot, then the BMM logo will popup, and you can choose your system from there. Either way works.
And regarding "removing BMM from non-main system", that is because you only want it installed on your Main system. Flashing a ROM with BMM built-in onto System 3-6 means that it has to remove itself during the flash to prevent conflicts. This is normal.
Click to expand...
Click to collapse
+1 That's exactly what I was thinking.
Brought to you by time and relative dimensions in space.

i did this and now bmm wont start an failed to pass boot anim,,,
http://forum.xda-developers.com/showthread.php?t=2038070
the fix is?

hafizkris90 said:
i did this and now bmm wont start an failed to pass boot anim,,,
http://forum.xda-developers.com/showthread.php?t=2038070
the fix is?
Click to expand...
Click to collapse
If BMM won't start then your only option is probably to re-flash the FXZ.
Brought to you by time and relative dimensions in space.

1BadWolf said:
If BMM won't start then your only option is probably to re-flash the FXZ.
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
Just did.. xD
Sent from my Google Eyelids while sleeping..

my bmm got removed today as well.. idk whats wrong.. i flashed a zip that i successfully flash so many times but now it removed my bmm.. any idea?
im using leak 3 as main.. also when fxz back to jb leak 3.. it preserve my data except root.. is that how it works?
Sent from my Google Eyelids while sleeping..[/QUOTE]

[Q] Help: Nexus 5 bricked while clearing Cache Partition

I was on Android 4.2.2 STOCK recovery and Rooted with Chainfire's Auto Root. Had sideloaded the 4.2.2 update.
I was stupid and I booted into Bootloader mode (Power+volume up + volume down)
Then I cleared Cache Partition. (not factory reset). On doing that, nothing happened for 10 minutes. The message was "Formatting Cache" I then switched off my phone.
Since then nothing is working. I cannot connect to phone network. The SD card folder is not working.
I went into Bootloader, and get the following error:
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
______________________
I've tried sideloading OTA update files, but I get the same error above. On factory Reset/Data -- I get the same error. I cannot do anything at this point. As before I am on STOCK recovery.
Someone kindly help. Is my phone bricked. I am so nervous.
Everything was perfect until I cleared the Cache partition.
Thank you so much. I hope someone replies soon.

http://forum.xda-developers.com/showthread.php?p=48360203
You can fastboot flash cache.IMG from the stock image to fix the corrupted cache partition.
Sent from my Nexus 5 using xda app-developers app

xybur said:
http://forum.xda-developers.com/showthread.php?p=48360203
You can fastboot flash cache.IMG from the stock image to fix the corrupted cache partition.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thank you so much. The linked thread talks about the same problem I am having.
Could you please point me to instructions on where to get Cache.IMG from the stock Image? Is it ok to fastboot flash Cache.IMG from 4.4.0 or is there a Cache.IMG for 4.4.2 as well?
Thanks.

If you download the stock image from the Google Dev site, its in there.
https://developers.google.com/android/nexus/images
You will need 7zip or a similar program to read the contents of the file. Just keep unzipping until you find the directory with the cache.img file (there should also be a radio.img, bootloader.img, etc. Basically, all of the stock files. You're only interested in the cache.img file in this instance).
I flashed it after I did the 4.4.1. Ota update so you should be fine too fast boot flashing it as well.
Sent from my Nexus 5 using xda app-developers app

I had the exact same problem, so i did a factory reset and everythin went bak to normal.only thing had to reroot

This isn't 100% I've done this and full factory rest I ended up having to rma PS I had my Efs also it still didn't work my logs said that it couldn't create the SD partion because my system was read only so I'm without my phone for two weeks
Sent from my Desire HD using Xparent Green Tapatalk 2

xybur said:
You will need 7zip or a similar program to read the contents of the file. Just keep unzipping until you find the directory with the cache.img file (there should also be a radio.img, bootloader.img, etc. Basically, all of the stock files. You're only interested in the cache.img file in this instance).
I flashed it after I did the 4.4.1. Ota update so you should be fine too fast boot flashing it as well.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thank you. Just downloaded the Cache.IMG file. And then placed it into the directory where the Android Fastboot is installed.
What should be the exact command for using Fastboot flash on Cache.img?
"fastboot flash cache Cache.IMG"
Is there anything else to it? Thanks in advance.

iamjimmy said:
Thank you. Just downloaded the Cache.IMG file. And then placed it into the directory where the Android Fastboot is installed.
What should be the exact command for using Fastboot flash on Cache.img?
"fastboot flash cache Cache.IMG"
Is there anything else to it? Thanks in advance.
Click to expand...
Click to collapse
Should be it.
Code:
fastboot flash cache cache.img
while in bootloader mode. make sure "fastboot mode" is displayed in the bootloader. i.e.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

xybur said:
Should be it.
Code:
fastboot flash cache cache.img
while in bootloader mode. make sure "fastboot mode" is displayed in the bootloader. i.e.
Click to expand...
Click to collapse
Thank you so so much. I did this yesterday. It worked like a charm. I took the Cache.Img file (13 mb) from the stock Android 4.4 factory Image.
Then phone booted immediately and everything seems fine. I was still on 4.4.2 and did NOT even lose the root.
The only thing messed up was the notifications. I had to set the notification ringtone and also reintegrate Google voice voicemail. Everything else is perfect.
I really can't thank you enough. Much appreciated.

iamjimmy said:
Thank you so so much. I did this yesterday. It worked like a charm. I took the Cache.Img file (13 mb) from the stock Android 4.4 factory Image.
Then phone booted immediately and everything seems fine. I was still on 4.4.2 and did NOT even lose the root.
The only thing messed up was the notifications. I had to set the notification ringtone and also reintegrate Google voice voicemail. Everything else is perfect.
I really can't thank you enough. Much appreciated.
Click to expand...
Click to collapse
Another way to do this is to actually go back and clear the cache partition again. I had the exact same issue and thought that I was bricked until I went back and tried it again. Be patient, mine took between 10-15 minutes but eventually finished and everything was fine again.

iamjimmy said:
I really can't thank you enough. Much appreciated.
Click to expand...
Click to collapse
Not a problem, glad to be of service
---------- Post added at 07:33 PM ---------- Previous post was at 07:33 PM ----------
iboj007 said:
Another way to do this is to actually go back and clear the cache partition again. I had the exact same issue and thought that I was bricked until I went back and tried it again. Be patient, mine took between 10-15 minutes but eventually finished and everything was fine again.
Click to expand...
Click to collapse
If the cache is corrupt, it might not even be able to be mountable. YMMV, but when it happened to me, in my case, I had to use the fastboot flash method.

iboj007 said:
Another way to do this is to actually go back and clear the cache partition again. I had the exact same issue and thought that I was bricked until I went back and tried it again. Be patient, mine took between 10-15 minutes but eventually finished and everything was fine again.
Click to expand...
Click to collapse
I tried doing that. But like in the previous post, the Cache is not mountable or corrupt maybe. Nothing really happened when I did wipe cache partition. It kept giving that error about Cache not mounted.

iamjimmy said:
I tried doing that. But like in the previous post, the Cache is not mountable or corrupt maybe. Nothing really happened when I did wipe cache partition. It kept giving that error about Cache not mounted.
Click to expand...
Click to collapse
Have you tried to fastboot flash the cache.img?

jd1639 said:
Have you tried to fastboot flash the cache.img?
Click to expand...
Click to collapse
Yes. That's what Actually worked. Thanks to the guidance of user: xybur.
However I Flashed the Cache from the stock image on 4.4 Kitkat from Google servers on a phone which has been updated to Android 4.4.2.
I was not able to find the cache.img file in the OTA updates of 4.4.1 and 4.4.2 downloads.
So in other words, I have Android 4.4.2 but the Cache.img file flashed from Android 4.4 (base release). Not sure whether that would lead to problems down the road.
Also is clearing the cache partition ALWAYS recommended before sideloading an OTA update manually?

iamjimmy said:
Yes. That's what Actually worked. Thanks to the guidance of user: xybur.
However I Flashed the Cache from the stock image on 4.4 Kitkat from Google servers on a phone which has been updated to Android 4.4.2.
I was not able to find the cache.img file in the OTA updates of 4.4.1 and 4.4.2 downloads.
So in other words, I have Android 4.4.2 but the Cache.img file flashed from Android 4.4 (base release). Not sure whether that would lead to problems down the road.
Also is clearing the cache partition ALWAYS recommended before sideloading an OTA update manually?
Click to expand...
Click to collapse
You're fine. If you were really worried about it you could flash the 4.4 to 4.4.2 zip that's in the general forum ota sticky. That zip patches, it's not the full rom, 4.4. I don't remember if there are any cache patches in it though. As far as clearing the cache before the ota, I've never done that and haven't had any problems.

jd1639 said:
You're fine. If you were really worried about it you could flash the 4.4 to 4.4.2 zip that's in the general forum ota sticky. That zip patches, it's not the full rom, 4.4. I don't remember if there are any cache patches in it though. As far as clearing the cache before the ota, I've never done that and haven't had any problems.
Click to expand...
Click to collapse
Thanks. I did search the 4.4.2 big zip file which is supposed to patch from 4.4 to 4.4.2. I did not find a cache.img in that file. So it seems there is no new cache, so I guess Google patched the existing one.
In any case my phone is ok. Given that I'm on 4.2.2 already, will flashing the zip (which upgrades android from 4.4 to 4.4.2) even work? Doesn't that require the phone to be on 4.4?
Overall, I'm thinking of maybe not doing anything since the phone seems to work fine. I read that the cache is also not critically important to the OS and it only has logs, cache information and such.

Did you use twrp to wipe the cache?? Sometimes it takes a while. its a known bug
It happened to me... Just waited it out like 15 mins.. It went through
Sent from my Nexus 5

jdiddy_ub said:
Did you use twrp to wipe the cache?? Sometimes it takes a while. its a known bug
It happened to me... Just waited it out like 15 mins.. It went through
Sent from my Nexus 5
Click to expand...
Click to collapse
Nope. I did NOT have a Custom recovery. It was the Stock recovery. My phone was all stock except it was rooted and the bootloader was unlocked. I used CF-Auto Root for this.
I think what threw me off was how much time it took to clear Cache. Whatever device I've handled in the past, it takes 10 seconds to clear cache. With the Nexus 5, I boot into the bootloader (stock recovery), chose the recovery option and then Wipe Cache Partition. Nothing happens for 10 minutes except "Formatting Cache".
At this point, I grew impatient and thought something was wrong. Made the mistake of switching my phone off. And then all hell broke lose. I did not get a signal, no storage was recognized and nothing was accessible. Even factory Reset wasn't working from the bootloader. Every time I went to the bootloader it gave me errors on unable to mount cache, storage not accessible etc etc.
Flashing 4.4 stock image cache saved my life. I was thinking I bricked my phone for good. Won't be messing around with the Cache ever again.
Quick question: Can I do a nandroid backup with Stock recovery? I realize it's easy to do this with CWM or TWRP recoveries, but I have not installed them as yet. Thanks.

You can not do a nandroid with stock recovery

jd1639 said:
You can not do a nandroid with stock recovery
Click to expand...
Click to collapse
Wow. I didn't know that. That may be the single biggest reason to install a custom recovery.
The only reason I did NOT do CWM or TWRP was because I wanted to get OTA updates and be able to sideload them manually.
It seems with custom recoveries one has to flash to stock image every time an OTA comes. With Stock recovery I updated from 4.4 to 4.4.1 and 4.4.2 without any problems. I used adb to sideload the updates and then just used CF-AutoRoot to Reroot (my bootloader was unlocked). Very quick and painless.
Do you recommend installing a custom recovery to replace Stock?

[Q] Suggest a stable Rom which supports Xposed & GB. Further, I m using Lollipop 5.02

[Q] Suggest a stable Rom which supports Xposed & GB. Further, I m using Lollipop 5.02
Suggest a stable Rom for OnePlus One which supports Xposed & GB. Further, I m using Lollipop 5.02 Liquidsmooth and having bacon recovery. I want to know will I need to do a Factory reset and then wipe all the data or all just I need to use "Clear everything for New Rom?", the option available in Bacon recovery. This sounds a bit crazy, but my friend bricked its device so I want to be very careful because this seems a bit new to me, compared to the way Xiaomi Mi3 behaved.
Thanks a ton !

rizwan82 said:
Suggest a stable Rom for OnePlus One which supports Xposed & GB. Further, I m using Lollipop 5.02 Liquidsmooth and having bacon recovery. I want to know will I need to do a Factory reset and then wipe all the data or all just I need to use "Clear everything for New Rom?", the option available in Bacon recovery. This sounds a bit crazy, but my friend bricked its device so I want to be very careful because this seems a bit new to me, compared to the way Xiaomi Mi3 behaved.
Thanks a ton !
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rizwan82 said:
Suggest a stable Rom for OnePlus One which supports Xposed & GB. Further, I m using Lollipop 5.02 Liquidsmooth and having bacon recovery. I want to know will I need to do a Factory reset and then wipe all the data or all just I need to use "Clear everything for New Rom?", the option available in Bacon recovery. This sounds a bit crazy, but my friend bricked its device so I want to be very careful because this seems a bit new to me, compared to the way Xiaomi Mi3 behaved.
Thanks a ton !
Click to expand...
Click to collapse
Not really sure what you're saying in half of that post, but Xposed does not work with Lollipop so forget that idea.
What do u mean by GB?
Exactly which recovery are you using? Bacon is the codename for this device so all of the recoveries are for Bacon, but not named Bacon.
When flashing a new ROM you should wipe system, data, cache, and dalvik cache.
Transmitted via Bacon

GB = gravity box? If so you will need to stick with KitKat not any lollipop ROM. And since you're already on cm12 nightly the cm12 firmware is installed. That means you have to install cm11s firmware and modem first to get cm11s working again (probably how your friend messed up his phone).
There is a link in one of the cm12 custom ROM threads I can't remember which though. Search cm11s or cm11 firmware and you will probably find it.
Sent From Lollipopified Bacon Goodness!

ek69 said:
GB = gravity box? If so you will need to stick with KitKat not any lollipop ROM. And since you're already on cm12 nightly the cm12 firmware is installed. That means you have to install cm11s firmware and modem first to get cm11s working again (probably how your friend messed up his phone).
There is a link in one of the cm12 custom ROM threads I can't remember which though. Search cm11s or cm11 firmware and you will probably find it.
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
Thank u very much Timmaaa and ek69. Extremely sorry for not putting my question in a proper way. Let me do that now. Well, bacon was used by mistake, I m using Philz Touch 6.44.9 ClockworkMod v6.0.4.9 recovery in my phone.
In it, when we click on "Wipe Data/Factory Reset", there r 2 options namely"Wipe Data/Factory Reset" and "Clean to Install a New Rom". Now if I have a custom rom in my root directory, what M I supposed to click on ?? on "Wipe Data/Facory Reset" or "Clean to install a new rom".
Further, I also know that Xposed Installer & Gravity Box don't work on Lollipop. Even Viper4Android has also some issues on Lollipop. Therefore, I want to know a very stable rom which gives me the ultimate pleasure to use Xposed Installer & Gravity Box on my OnePlus One.
Thank you very much...

rizwan82 said:
Thank u very much Timmaaa and ek69. Extremely sorry for not putting my question in a proper way. Let me do that now. Well, bacon was used by mistake, I m using Philz Touch 6.44.9 ClockworkMod v6.0.4.9 recovery in my phone.
In it, when we click on "Wipe Data/Factory Reset", there r 2 options namely"Wipe Data/Factory Reset" and "Clean to Install a New Rom". Now if I have a custom rom in my root directory, what M I supposed to click on ?? on "Wipe Data/Facory Reset" or "Clean to install a new rom".
Further, I also know that Xposed Installer & Gravity Box don't work on Lollipop. Even Viper4Android has also some issues on Lollipop. Therefore, I want to know a very stable rom which gives me the ultimate pleasure to use Xposed Installer & Gravity Box on my OnePlus One.
Thank you very much...
Click to expand...
Click to collapse
I'm unfamiliar with Philz/CWM because I use TWRP because I believe it's a far superior recovery, so I don't quite know what each of those wipe options actually do. My guess is that the "clean to install new ROM" will wipe system, data, and your caches, so I'd use that option. But I'm only guessing.
It's too difficult to suggest one ROM over another, and I firmly believe it's disrespectful to the developers to do so. What I will suggest is for you to take a look at my index thread which lists all ROMs for this device (as well as all other important threads), that way you can have a look at what's on offer and decide for yourself.
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon

I can only recommend from my experience, liquid smooth has been..well smooth. So it gets my support, but if you're looking to mess around with things, lollipop might make that difficult as has been mentioned. I'm fairly sure exposed won't work at all. Your best option would be cm12 would it not?
Factory reset should also be fine.

Don't do factory reset in that recovery, I'm pretty sure I read somewhere that it will wipe the internal SD card as well. I guess do the other option to clean for a new ROM cuz that's the only one that is left lol. I also use TWRP so I can't guarantee anything. Or if you can manually wipe partitions then wipe the ones already written.
You have to stick with cm11s or some ROM based on cm11. I can't suggest any either since they all vary based on taste, features, etc. At this point they all are pretty much stable I would say. Also I agree with timmaaa you need to find one that works well for you. You have to read the first few posts of each ROM thread and see which one appeals to you
Sent From Lollipopified Bacon Goodness!