On my Galaxy S4 19505 I installed many roms and made backups through TWRP without any problems. But now when I tried to create a backup I keep getting 'unable to locate storage device'. Do any of you know how to fix this problem? At the moment i'm using a Rom called Graviton, and it didn't let me backup using this rom and cm 10.2. I'm also using TWRP 2.6.3.0 if that helps.
PS This all started when I was on CM 11, and tried to update to the newest nightly version, but when I tried to flash the update it just said failed. After this I tried to go on restore and found all of my previous backup files were gone?
This is the att thread not i9505--
That said--you probably lost the card. Not uncommon for 4.4 roms and non-sammy sdcards.
Can you try another card and see if it works
Can you copy a rom to internal and flash it after wiping all including system. Flash a TW rom like Golden Eye from the i9505 forum, not another aosp/cm rom
I prefer twrp 2.5.0.2
You may have to take card out and format it. Not sure what card you got.
Assume you have important data/etc copied to your pc for situations like this.
Hope you get it sorted. I lost mine on an early kk rom and had to reformat and load it--
Related
I rooted my phone today. And everything was great.
I installed Clockwork. And applied CM 7.
I of course backed up my previous rom and everything was going smoothly until everything was completed.
My phone boot up as normal and then it got stuck in the CM logo.(now when I see a blue android skating I might puke)
So I tried to restore my previous rom but clockwork is defective. I selected 'backup and restore' and then nothing shows up in the screen..
Is there anything I can do to fix my phone?
I love this phone so much I really wanna fix it.
Any ideas?
since you are rooted, download the CM7 rom again (zip file) and put it on your SD card, then flash it from the recovery
Do all your flashing and backups from recovery, not from rom manager. You can confirm your backup exists by going to sdcard/clockworkmod/backups. If you did your original backup through rom manager, there's a good chance it's corrupted. Reflash cm7 from recovery if you can't restore your backup.
Sent from my HTC Glacier
I'm having basically the same problem. I just downloaded the cyanogenmod rom and put it on my sd card but I'm not sure how to flash it. Do i keep it as a zip and install it using the install update.zip thing? cause that gave me an error. Or do i extract it and put it in my backup folder and try to flash it using the restore option? Or is there some other option Im missing?
Thanks in advance
Ah ok I figured it out, I was trying to use the .zip for the a different model phone. I got it all working, thanks for the help guys!
Right basically if you've followed my last thread, http://forum.xda-developers.com/showthread.php?p=27975788#post27975788 it turns out I haven't got anywhere really. Today I managed to flash both froyo and GB but after trying to root both and install a custom ROM it would fail and I'd end up in a bootloop. Normally I'd just reinstall the dload files from the SD card and start again. Now however, when I go to boot the dload files, I get pink a screen (with usb plugged in I have the image folder with various files). When I try and boot recovery, nothing happens, I've tried replacing the recovery image, but no success. So now I'm left with a phone that does pretty much nothing other than bootloop or turn pink on command. Any suggestions on what I can do to install froyo or GB?
Sorry and thanks again.
Before root the rom(s) run ok?
And how you root the device? Also are you sure that the root have success? How you check it?
The root was fine, followed the instructions from the thread in dev section, ran the one click root everything was fine, swapped the recovery to get v5 used remount and astro explorer. went to CWM, made sure i had a rom that ran with the kernel, installed it everything said it was fine reboot into a loop. my options now are boot loop or pink screen, it wont even pick up the dload from the sd card.
So the bootloop happen with the custom rom you flashed from recovery mode?
Which rom you flashed? Did you wipe data/cache/dalvic_cache before the reboot?
Indeed I did. Something corrupted in the image folder. So I found a custom Image folder by the guy who's developed the v5.5 of CWM. In his signature theres a load of zip files one of them had a custom Image folder which Ive swapped in to which the phone has read the dload files now finally. Im hoping this will work.
If the device boots fine with the official roms, and bootloops with the custom, there is nothing wrong with the image file. The problem is with the rom that you try to flash and maybe with the recovery version.
For whatever reason ive tried multiple roms today none of which have booted, the closest i came was the oxygen rom but that failed at the oxygen splash screen. As for my problem, something had happened after i flash a rom, no idea what but a file in the image folder had gone bad. after swapping that out for one i found, dload from the SD card booted and installed. I now have a stock GB running which i think i'll leave it at that. i'm clearly missing something when i flash a custom rom whether it be bootloader related or a incompatible rom to kernel. either way now it works, i'll leave it as is. Thanks for the help though much appreciated. I'm hoping other will find the help they need here.
Dave759 said:
For whatever reason ive tried multiple roms today none of which have booted, the closest i came was the oxygen rom but that failed at the oxygen splash screen. As for my problem, something had happened after i flash a rom, no idea what but a file in the image folder had gone bad. after swapping that out for one i found, dload from the SD card booted and installed. I now have a stock GB running which i think i'll leave it at that. i'm clearly missing something when i flash a custom rom whether it be bootloader related or a incompatible rom to kernel. either way now it works, i'll leave it as is. Thanks for the help though much appreciated. I'm hoping other will find the help they need here.
Click to expand...
Click to collapse
The only cases I can think a custom ROM won't work are
- installing a .32 ROM over a ROM based on .35 and vice versa
- installing a custom ROM without wiping data and caches of the previous ROM, especially if they are not related, like not different builds of the same ROM
- installing a .32 ROM using cwm other than 5.0.2.6 and below
- installing a .35 or ics ROM using a cwm other than 5.5.0.4 or 5.0.2.7
Are you sure you did none of that?
Sent from my U8800
Hi everyone
This is my first post so please go easy on me
After long reading on internet I was trying to install custom rom on my phone but keep failing, my galaxy s3 is rooted already with CWM, after reading instruction how to root the phone it just keep saying installation failed from SD card, also try using twrp which did more harm then good for me but anyway managed to go back to CWM and still the same what I'm doing wrong? I download the CM11 nightly but it keeps failing to install.
Anyone have any suggestions?
u need to install the latest twrp or cwm
then put the rom zip file in your sd card
wipe data and cache
and select the zip from your recovery and flash it
done this but it keeps failing when installing also saying installation aborted it looks like that CWM and twrp having problem reading my sd card
try to change your sd card or borrow from any of your friend for flashing purpose
sorted now, downloaded rom manager which updated my CWM and now running on 4.3 happy days, will try kitkat 4.4 later
Hello, I am a novice at best when it comes to this. That being said I have successfully Unlocked my boot-loader, rooted and installed roms to my phone. Recently when using TWRP 2.7 I noticed that it would not mount data when restoring my backup. I then noticed it would not mount data when creating a new backup while using TWRP 2.7. I then installed CWM latest recovery. It does the same thing. In the process I got stuck in CWM and had to AP Fastboot to stock 4.4.2. Now with CWM it will not mount data when doing a backup. I cant load a rom without having a secure backup. What can I do? Need help! Calling all devs!
I'm pretty sure that the only recovery available is CWM for the RAZR HD. However, that recovery can't mount data. I don't think there is a custom recovery right now that had full functionality for the RAZR M.
With that said, the kernel sources have been released, so I would say its only a matter of time before an updated recovery is available that can support mounting data.
Sent from my XT907 using Tapatalk
queue72 said:
I'm pretty sure that the only recovery available is CWM for the RAZR HD. However, that recovery can't mount data. I don't think there is a custom recovery right now that had full functionality for the RAZR M.
With that said, the kernel sources have been released, so I would say its only a matter of time before an updated recovery is available that can support mounting data.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
I have had TWRP work just fine in the past. Others are having no problem with them as I can tell. This is an original Razr M.
ehunter74 said:
I have had TWRP work just fine in the past. Others are having no problem with them as I can tell. This is an original Razr M.
Click to expand...
Click to collapse
There is no TWRP designed for the KK update, yet. CWM is only working aftermarket recovery right now. TWRP should be out any day.
OK let me give more details. I was running Beanstock Rom with Android 4.3 on my ORIGINAL XT907. I was running TWRP 2.6 flawlessly. I tried to load a new ROM (KitStock 4.4.2). When I tried to backup my current configuration with TWRP it would not mount data during the backup procedure. I panicked and backed out. I seen that CWM was a better choice and installed CWM v6.0.4.8 It also would not load data during backup. I then tried to back out of that and it got stuck on boot. would not go past no matter what. tried to load KitStock ROM anyway. Same effect. I could still get back into CWM recovery and also bootloader. I then installed the latest STOCK ROM I could find and it is version 183.46.10XT907.Verizon.en.US. Kernal is [email protected]#1. Build number KDA20.62-10.1 Android version 4.4.2
I think what I have discovered is that I must have a "working" corrupted file script whit this stock ROM. I discovered that if I formatted my SD card I could mount the data and backup my nandroid. So my SD card was corrupted??? Also after I knew I had a good backup when I tried to install CM10.1 it gave me a status 7 error. Ok did the status 7 fix by editing the script on two different ROMs. It still aborts installation. Now I consider myself a noob but I'm no stranger to the ROM installation process. I've done all the right steps. Backup. Wipe 3x, mount system, install. This seems like a deeper problem. Please HELP!
Hi all technical gurus and experts
I have the standard u8800 X5 and have managed to recover it after two weeks after bricking it quite properly. The question I have is that I am unable to get the official GB update to install correctly over the stock Froyo Rom.
I had the phone running on the official GB for a number of years unmodified without problems until I rooted the phone for the first time.
In an attempt to fix it I managed to remove the OS completely (I know I know). I have finally managed to recover the phone by flashing the stock 2.2.2 B138 rom. Next I attempted to upgrade to to the official 2.3.5 B526 I downloaded from the huawei site. Every time after it installed it boot looped. Pull the battery out and put back then I do a factory reset from the recovery and the phone would work. At next restart it would have multiple error messages about processes unable to start and would reboot back into the boot loop.
Back to square one and re flash the froyo.
Eventually I flashed oxygen 2.3.7 over the froyo, which is stable.
I have root access and CWM 5.0.2.6 installed.
Please help as I would like to install a newer Rom like Aurora ICS or CM10, what do I need to do to get it right?
Thanks in advance.
Bump for @Blefish
Its difficult to understand why this is happening. However, if you installed 2.3, your baseband is updated and theoretically you should be able to switch the ROM, even though the stock ROM is crashing. Huawei ROM is loading some of the items from the "cust" partition, it might happen this does not have the necessary items but I doubt it.
Thanks for answering. You are the foremost expert on the u8800 that I know of.
Blefish said:
Its difficult to understand why this is happening. However, if you installed 2.3, your baseband is updated and theoretically you should be able to switch the ROM, even though the stock ROM is crashing. Huawei ROM is loading some of the items from the "cust" partition, it might happen this does not have the necessary items but I doubt it.
Click to expand...
Click to collapse
If you mean amms.mbn it is not the thing which controls switching between roms.
OP should check partitions, I think all the problems are from them (and from appsboot.mbn too ).
Last time I bricked my phone, it refuses to install any roms (I was on B919 and was not able to install B919 :silly: ) except B939.
I have checked logs, located in /sdcard/dload, and found some "partition error", or "installing new partitions", etc.)
PS: Solved.
Cust partition is not a problem, I remember I cleaned it from my U8860 and everything was ok.
OP, try to install different mods and if nothing helps, ask someone to send you a dump.
What you said about the updated baseband gives me an idea. If I can install CWM 6 with es file manager, after updating to the GB. I can use your partioning tool and then install Aurora or CM10. Do you think that could work?
missioner said:
What you said about the updated baseband gives me an idea. If I can install CWM 6 with es file manager, after updating to the GB. I can use your partioning tool and then install Aurora or CM10. Do you think that could work?
Click to expand...
Click to collapse
I am quite sure it could work. But I would suggest installing B518 or at least install pink screen unlock before you do repartitioning.
Thanks I will keep that in mind.
I will install ES explorer tomorrow and see about an updating the recovery
I checked the size of the internal sd card as Jeka suggested and total size is 1.4Gb. I remember that the internal SD card should be 2Gb if the partition is stock. I did run the Blefish recovery repartitioning zip before I so wonderfully bricked the phone, it is most likely the partition size that is causing the error.
I have the 3 partition zips downloaded including the stock partition one, so I will give it a go this weekend if my son agrees. It is his phone and he appears to be enjoying the oxygen rom currently installed. Ultimately I want an ICS rom installed though.
After much time I have solved the problem.
The phone has been running for some time on oxygen 2.3.7 GB, but sadly started having problems again. This time due to the dodgy games my son had installed on to the phone.
I flashed the official GB to update the baseband and then realised I had made a small mistake as I had also unrooted the phone and replaced the cwm recovery with a stock one.
Some hasty searching later and installing ES FILE MANAGER I managed to find and install a rooted recovery. I did this as my other root methods were unsuccessful.
This allowed for me to install the Team Win U8800 recovery. As per the previous post the phones partitions had not been restored to stock, so I installed the Aurora ICS Lite Rom.
Very happy with the results and I have to say that the TWRP recovery is top notch.