[Q] Help: Nexus 5 bricked while clearing Cache Partition - Nexus 5 Q&A, Help & Troubleshooting

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?

Related

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"
}

[Q] Every ROM hangs at startup screen

Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?
famac! said:
Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?
Click to expand...
Click to collapse
answered here http://forum.xda-developers.com/showthread.php?t=2465695
bweN diorD said:
answered here http://forum.xda-developers.com/showthread.php?t=2465695
Click to expand...
Click to collapse
Not really. The majority of ROMS in question have been 4.2.2 based....
famac! said:
Not really. The majority of ROMS in question have been 4.2.2 based....
Click to expand...
Click to collapse
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"
bweN diorD said:
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"
Click to expand...
Click to collapse
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.
famac! said:
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.
Click to expand...
Click to collapse
i could be wrong, but in my opinion having the exact same issue even though its a different version, one of the 2 fixes in that thread should work.
the first fix likely doesn't directly apply although i suggest you ensure you have the latest version of your recovery of choice found here http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
second fix (backup ALL data you don't want to loose first as noted above), then do a full wipe as listed above, not just a fdr that doesn't wipe everything on the internal card.
the problem at this point is, you are assuming it wont work because of version differences, i am assuming it will. until you try it, i don't see any point in exploring other options, if there are any.
Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.
RikRong said:
Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.
Click to expand...
Click to collapse
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.
famac! said:
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.
Click to expand...
Click to collapse
Nice! Glad to see you got it working.

Nexus 5 CWM problem?

So I'm trying to install custom ROM on my friend Nexus 5, should be a 2 minute job turns into 2 hours..
CWM is giving me a list of can't mount anything basically.
I tried fe-flashing the entire phone back to stock via fastboot, that went fine, flashed recovery again to CWM.. and can't mount anything again..
I need to be able to mount in order to install zip...
anybody can help??
now i got it to boot with purity ROM, telling me on startup with no google sign in... "
System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
THE_KINGDOM said:
now i got it to boot with purity ROM, telling me on startup with no google sign in... "
System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Click to expand...
Click to collapse
yup, you will need to wipe and reflash.
still can't mount sdcard in recovery..
so i can't do anything.. I had to sideload the ROM..
so i've done a bat flash all, restore to stock..
I don't get why everytime i flash CWM custom recovery I can't load anything.. how the hell do I install purity from stock if I can't install CWM ?!
THE_KINGDOM said:
so i've done a bat flash all, restore to stock..
I don't get why everytime i flash CWM custom recovery I can't load anything.. how the hell do I install purity from stock if I can't install CWM ?!
Click to expand...
Click to collapse
try twrp recovery
but i've been using CWM forever on every nexus device without problems..
I though process is simple.
1. Unlock bootloader
2. Fastboot flash recovery recovery.img (cwm)
3. wipe & install custom ROM (Purity)
4. gapps
5. start phone..
what am I missing???
so I tried installing the previous version of CWM 6.0.4.4 and CWM problems seems to be resolved.. clearly they must have issued with the latest version.
Now im able to read /sdcard and hopfully install purity ROM, gapps etc.
but I'm still getting the system UID's inconsistent issue...
what a colossal waste of time...
ok phone back to stock at again with a batch restore all file.. factory files...
how the ****ing hell do I install a custom ROM?!?!?!? Like iv'e done this a million times before.. what am I missing??????
anybody?????
THE_KINGDOM said:
ok phone back to stock at again with a batch restore all file.. factory files...
how the ****ing hell do I install a custom ROM?!?!?!? Like iv'e done this a million times before.. what am I missing??????
Click to expand...
Click to collapse
Put a custom ROM.zip and gapps package on storage, flash in recovery, flash SuperSU if necessary?
THE_KINGDOM said:
anybody?????
Click to expand...
Click to collapse
No bumping within 24 hours is the forum rule. I also believe they should set a punctuation limit. Chill out
Sent from my Nexus 5 using Tapatalk
Lethargy said:
Put a custom ROM.zip and gapps package on storage, flash in recovery, flash SuperSU if necessary?
Click to expand...
Click to collapse
this is what ive been doing.. when phone boots it doesn't ask for google login credentials and goes straight to android is upgrading as if I did a dirty flash and then tell me i have a UID mismatch, and to wipe data partition..
i've now reinstalled this phone close to 6 times.. I cannot figure this out
THE_KINGDOM said:
what am I missing??????
Click to expand...
Click to collapse
cwm recovery SUCKS. but if you are unwilling to try other recoveries, oh well..
THE_KINGDOM said:
this is what ive been doing.. when phone boots it doesn't ask for google login credentials and goes straight to android is upgrading as if I did a dirty flash and then tell me i have a UID mismatch, and to wipe data partition..
i've now reinstalled this phone close to 6 times.. I cannot figure this out
Click to expand...
Click to collapse
Well somewhere you're not wiping properly. Flash the factory images again using the flash-all.bat included in the compressed file as it'll wipe everything, then go from there.
Stock CWM always has issues. It's based on an outdated version of Android so it doesn't always play well with KitKat. I would recommend either TWRP or Philz Touch CWM.
Lethargy said:
Well somewhere you're not wiping properly. Flash the factory images again using the flash-all.bat included in the compressed file as it'll wipe everything, then go from there.
Click to expand...
Click to collapse
flashed factory img aroudn 6 times now.. every single time i got back to put on CWM and then flash the rom i get a UID mismatch, bunch of force closes etc..
BirchBarlow said:
Stock CWM always has issues. It's based on an outdated version of Android so it doesn't always play well with KitKat. I would recommend either TWRP or Philz Touch CWM.
Click to expand...
Click to collapse
CWM is built from CM11 4.4.3 source code.. But yeah it has issues., lacks functionality and also is antiquated
Sent from my Nexus 5 using Tapatalk
THE_KINGDOM said:
flashed factory img aroudn 6 times now.. every single time i got back to put on CWM and then flash the rom i get a UID mismatch, bunch of force closes etc..
Click to expand...
Click to collapse
Don't know what to tell you, just try TWRP. I've had issues with CWM on every single device I've put a custom ROM onto (Xperia Arc S, HTC One M7, Galaxy S4, HTC One M8, Galaxy Note 3, Xperia Z, Nexus 5), and never had a single issue with TWRP on any.
gonna try Philz Touch CWM and if that doesn't work then TWRP

TF 300T Partitions

Hey there!
I'm hoping that someone can help me out. My nephew who's a wanna-be geek was going to update my ROM (which didn't to be done really, but he wanted to show me what he was able to do). He went and downloaded the latest CM 11, rebooted and went into TWRP 2.7.0.1, did a factory reset, an advanced wipe, and did the Format Data. When he did that, it got stuck in a loop. Nothing happened. He tried to install the ROM he downloaded, and NOTHING! Long story short, by him doing the Format Data, he wiped out my partitions. TWRP, no matter what I try to do tells me it's unable to mount 'data' or 'media' etc. etc. Which is leading me to believe I have no partitions left. I've tried installing the latest update from Asus, and no dice. I've tried restoring backups that I have on my micro SD, and that's not working.
Can someone please help me and tell me how to fix this? Can I get my partitions back? I'm really hoping that I don't have to send this tablet off to Asus in Dallas, TX to have it repaired.
I'm using a loaner tablet from a rental store, hoping I can get my TF 300 fixed.
Any help is deeply and sincerely appreciated.
Omega
Sent from my SM-P600 using Tapatalk
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Duchman said:
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Click to expand...
Click to collapse
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Omega Recon said:
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
You could try flashing a newer recovery first, I think 2.7.1.0 is available for your device. Also try doing a hard reset by cold booting - here's a how-to: https://www.youtube.com/watch?v=oTU38Ewh8qo (wipe the cache afterwards)
If that doesn't help, reverting to stock is probably your best option. Try this: http://forum.xda-developers.com/showthread.php?t=1757077 (be sure to grab the correct firmware and back up your files)
Have you tried installing any other custom ROM? Does it give you the same error when you try to restore your backup?
Here's what I've come across so far. I did the reset, and that did nothing.
Tried to flash the stock version, after a few seconds, TWRP popped up with FAILED.
I've tried flashing Omni ROM. It will flash, load up, and gets stuck at the boot screen or boot animation. This happens with just about every ROM I try to flash.
Been looking for TWRP 2.7.1.0. I'm not seeing it listed on TWRPs site. Where can I get a copy? Thanks!
Sent from my SM-P600 using Tapatalk
Here you go: http://forum.xda-developers.com/showthread.php?t=2772093
Also do try flashing another recovery, PhilZ for instance: http://forum.xda-developers.com/showthread.php?t=2597860
Did you try wiping all of the partitions again?

Categories

Resources