Related
So working on my USCC desire.
I was trying to install a ROM on the phone, and while doing so I wiped the phone. When I say wiped I mean that there is nothing on the sd card, no OS, no backups, nothing. I still have access to ClockworkMod Recovery v2.5.0.9.
Is there anything I can do.
Depends on what you want. If you want a working phone boot in to recovery mount your sd, copy a rom and flash. If you want your data back try a data recovery program.
Not sure if its the same for cdma phones but it's better to use CWM 2.5.0.7(do check if this works for cdna phones)
Sent from my HTC Desire using XDA App
Thanks ill try that tonight.
Sent from my SGH-I897 using XDA App
So i just flashed another rom and my sd mount was working but on miui my sd won't show up on the computer it just says I don't have the drivers but it doesn't let me install them. So what could it be wrong with the rom?
Sent from my PC36100 using XDA App
jc8081 said:
So i just flashed another rom and my sd mount was working but on miui my sd won't show up on the computer it just says I don't have the drivers but it doesn't let me install them. So what could it be wrong with the rom?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
ok so lets try a few things. First lets try to fix permissions since miui is a asop rom. If that doesn't work make sure you wipe the dalvik cache, card partition, and data factory reset if your using rom manager. Also data factory reset when flashing a totally new rom not an update. If this doesn't work flash back to an older rom and see if this works. If not we will need to flash back to stock rooted to see if that fixes the problem.
I just flashed the stock rooted and it worked. I really like my miui setup and dot feel like wiping data since I don't connect it to the computer that much. But How do I check permission tho?
Sent from my PC36100 using XDA App
jc8081 said:
I just flashed the stock rooted and it worked. I really like my miui setup and dot feel like wiping data since I don't connect it to the computer that much. But How do I check permission tho?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
go into rom manager and tell it to fix permissions at the bottom.
Hi I recently flashed evo-decks 1.2 stable after I did that I had errors with any nandroids and I can't flash any sense or aosp ones either. I'm stuck and and stumped as to what my course of action should please any ideas would be fantastic thank you.
Well first, do you have a current working rom at the moment?
What he ^ said.
Sent from my PC36100 using XDA Premium App
yes I do its the evo decks 1.2z the one I found to be more of a stable version
[email protected] said:
yes I do its the evo decks 1.2z the one I found to be more of a stable version
Click to expand...
Click to collapse
Well backup the rom; make sure you have at least 500mb free space. Do a full wipe [factory/data, cache, dalvik cache], flash the new rom. Make sure you have more space, because the sense 2.1/3.0 can be big in backup size.
What happens when you try to flash another Rom?
Sent from my PC36100 using XDA Premium App
I get stuck at the HTC evo 4g screen just stays white and wont boot I have wiped it numerous times and I get the same result never happend until I flashed the 1.2 stable I also did flash the vipermod and Google apps as well as available memory mod I found I had used that multiple times before as well
Wipe everything 3x, use Virus's CR super wipe after you manually wipe everything. Factory wipe, cache and delvik cache. That should clear everything out. Then flash a Rom. It sounds like something isn't getting wiped.
Sent from my PC36100 using XDA Premium App
Well it says report to the recovery log to see what went wrong its preventing me from even Making a backup at all it says depot to recovery log to see what went wrong seems more serious no?
So because somethings not wiping properly that will give me an error telling me to view the recovery log and then prevent me from flashing different builds and making a nandroid backup I don't seem to see a link for the superwipe under virus I tried searching and i could not locate it is it on his website?
[email protected] said:
So because somethings not wiping properly that will give me an error telling me to view the recovery log and then prevent me from flashing different builds and making a nandroid backup I don't seem to see a link for the superwipe under virus I tried searching and i could not locate it is it on his website?
Click to expand...
Click to collapse
here you go.
http://bit.ly/jEjuoN
If I were you, I'd backup my SD Card, format it, repartition it, if you're using partitions, and then copy the essentials back over. Specifically, you're nandroid folder, then reflash your Recovery, which hopefully, is Amon Ra.
Then either try to reflash one of your nandroids, although if it was me, I'd just copy the ROM you want first, and then try to flash that, and it if goes well, try a nandroid you have saved.
I've had this happen twice and both times, reflashing recovery did the trick
Alright ill try thanks alot everyone I appreaciate your help ill get back to you guys hopefully with good news
Well so there's no way I could just wipe it with recovery and flash it over cause apparently I'm not the only one with this issue and somebody said it has to do with partitions of my SD card I'm trying to look into it deeper.
Sent from my PC36100 using XDA App
[email protected] said:
Well so there's no way I could just wipe it with recovery and flash it over cause apparently I'm not the only one with this issue and somebody said it has to do with partitions of my SD card I'm trying to look into it deeper.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You don't have to partition it; first reflash your recovery via PC36IMG image, then copy your sdcard to a pc, format it, then copy the files back over, try to restore a backup, or reflash the rom.
I really need some help. I have no idea what has happened to my phone. Anything I d/l from the market or from the computer fc on my phone. I can't use anything. I tried flashing other roms but any ROM I flash just keeps looping the boot image over n over. Even when I try to restore one of my back ups from recovery it does the same it says error while formating data. Then Wen I reboot it just loops the boot image as well. I've tried everything I can think of. If this has happened to anyone please let me know.
Sent from my ADR6300 using XDA App
do you have a droid incredible? your profile says you have t-mobile.
Yes I used to have a my touch on tmobile. But I have a Droid incredible with Verizon
Sent from my ADR6300 using XDA App
criveroh said:
Yes I used to have a my touch on tmobile. But I have a Droid incredible with Verizon
Click to expand...
Click to collapse
By boot image do you mean "splash screen" and "boot animation?" Can you get back to recovery? If so, which recovery and version? If clockworkmos, make sure it's at least 3.0.0.7 or later if your Inc has an amoled screen, 3.0.0.8 if it's SLCD.
If you can get to recovery, power off the phone. Pull the sd card and check that your computer can read it and it's formatted FAT32.
If so, put a clean copy of a ROM on the root of the SD card. Reinsert it in the phone. Boot to hboot (you are running hboot 0.92 right!?) and then to recovery.
In recovery, factory reset, wipe cache and wipe dalvik, then flash the ROM.
If you're running an older hboot and/or older recovery, see elsewhere on XDA how to update those first.
Sent into the interwebs from my Droid Incredible using XDA Premium
Just to add onto the info already posted, hboots and recoveries can be downloaded at: dougpiston.com
Thanx but I've tried all that. Nothing works
Sent from my ADR6300 using XDA App
criveroh said:
Thanx but I've tried all that. Nothing works
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Have you tried flashing stock froyo and then doing a factory reset from hboot? And by stock froyo i mean the official ruu with stock recovery.
Next time you try to do a wipe, also go into mounts and storage and format boot, data, system, and cache. This happened to me once and this seemed to fix my problem. Now I do it every time.
Tried a different sd card?
Sent from my ADR6300 using XDA Premium App
I have used MIUI since June with no problems at all, I then tried to install the 9.30 update. It didn't install right even though MD5 matched (stuck on the white HTC Incredible screen). I tried restoring to my backup and after rebooting nothing happened. It tries going to the boot animation but doesn't, just goes to a black screen. I've let it sit for an hour there and nothing happens. I tried resolving this on the MIUI.us forums, but no responses so far.
At that point I tried cm7, it worked but was really glitchy and bootlooping. cm6 was next, and it was working mostly but didn't seem stable to run. I then tried going back to MIUI all of them, 8.19, 9.2, and 9.9 as well as the 9.30, did not install.
I am now running the rooted stock rom and it seems to be running fine these past two weeks (aside from the fact it's sense). Over the weekend I tried, again, to install MIUI and restore a backup but it's still not working. And to make matters worse cm6 and 7 are no longer running.
I have also tried all of the above with CWM 3.0.0.8, CWM 5.0.0.2, and Amon_RA 3.02 (no restore to test) and have had the same issues across all recoveries.
It really seems like my phone has become allergic to any AOSP rom, I haven't tried other sense roms but I'm expecting them to work since the rooted stock rom has both installed and restored with no issues.
I have not tried going back to bone-stock and then re-rooting as that would be a pain. But if it is my only option to get back to MIUI then I will give it a shot.
Any help would be greatly appreciated.
Before you flash a ROM do you:
Clear data: Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik
Then flash the ROM?
Before a new rom (not btwn miui updates) I normally wipe data/factory reset and wipe dalvik. But I don't do anything in mounts and storage unless I need to mount usb storage.
Sent from my ADR6300 using XDA App
I would back up your current working ROM, try what I mentioned above, and then try flashing MIUI again.
In Mounts and Storage, you'll have the option to format emmc, and sd card too. Just make sure you ARE NOT selecting those items, as obviously you want those intact. If you follow the instruction above, you should be fine.
Got proper HBOOT version?
Sent from my ADR6300 using XDA Premium App
When I get home I will try doing everything suggested.
My hboot is 92 I believe.
Sent from my ADR6300 using XDA App
RMarkwald said:
Before you flash a ROM do you:
Clear data: Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik
Then flash the ROM?
Click to expand...
Click to collapse
Ok, I did all of the above and still have no luck in installing MIUI or restoring a backup.
Also, I didn't mention this in the first post. When I try and boot from a restored MIUI and it tries to load the boot animation I can still reset the phone with the 3-finger salute, so the phone is still doing something just not what it's supposed to. I did try flashing another boot screen incase there was something wrong with the backup, but that didn't work.
Any other ideas out there?
Tried a different sd? Copy and paste the contents of sd to pc, reformat sd fat32, copy contents back to sd, see if issue persists.
If reformatted native sd doesn't help, perhaps try another.
Sent from my ADR6300 using XDA Premium App
I just tried both a different sd card as well as reformatting my current one, in both cases I can't install MIUI nor CM6.
Stumped here... Only other thing I can think to try is a Sense ROM on either/both sd's to see what boots and runs without issue.
Sent from my ADR6300 using XDA Premium App
As I mentioned already I'm currently running the rooted stock gb rom, which is sense. I can try another sense rom just for fun.
Sent from my ADR6300 using XDA App
Yep, apologies. Speculation on my part:
Bad sd. AOSP interacts with sd on boot and during normal use, device acts up only with AOSP, hence bad sd.
Also, when flashing the AOSP ROM on newly formatted sd, wipe of mounts (data, cache, boot, and system) as well as factory reset, cache partition, and dalvik, all from recovery were successful?
Sent from my ADR6300 using XDA Premium App
So sense does not interact with sd the same way as aosp? What could be the problem with the sd card that allows it to do everything but allow it to boot aosp roms (especially since I have tried 2 different ones) ?
Sent from my ADR6300 using XDA App
AOSP calls on and even interacts the sd during boot, as well as during normal use. If your device is only wonky running AOSP, I'd suspect the sd, provided a complete wipe is done and the cwm, radio, and HBOOT are what's called for by the AOSP ROM.
Assume nothing restored to fresh aosp install, correct?
Sent from my ADR6300 using XDA Premium App
Yeah, a restore or a fresh install has problems. If I install and then remove the sd card would it possibly boot then?
I'm still confused as to how the sd card can do everything else that it's supposed to but not talk to an aosp rom.
Sent from my ADR6300 using XDA App
AOSP uses the sd to operate, Sense does not.
Sent from my ADR6300 using XDA Premium App
What I still don't understand then, if it is the SD card, why do I still have the problem with a different sd card?
Is it possible that it is hardware related, or something else, with the phone? I am able to read and write to the SD card when operating the phone, but the issue only appears to happen at boot.
This weekend I may try and unroot and then reroot, just incase some important files got corrupted. as the unroot would replace nearly everything it should fix the problem if it isn't hardware... I'm hoping.
Stumped... Hard to say.
Sent from my ADR6300 using XDA Premium App
Well, I got tired of sense so I flashed the RUU, reloaded CWM 5.0.0.2 and restored my old rom... it worked. So now I'm fixed, yay.
Thanks for helping me troubleshoot it.