There's a patch to allow people who've run the ICS leaks to see their SD cards after returning to GB. Why is this necessary, and what does the patch do?
I ask because since S-off I've completely reverted to GB, and I'm still having problems seeing my SD, perhaps because it either had its format changed due to ICS, or because I previously applied the patch to the ROM I'm currently running.
cpurick said:
There's a patch to allow people who've run the ICS leaks to see their SD cards after returning to GB. Why is this necessary, and what does the patch do?
I ask because since S-off I've completely reverted to GB, and I'm still having problems seeing my SD, perhaps because it either had its format changed due to ICS, or because I previously applied the patch to the ROM I'm currently running.
Click to expand...
Click to collapse
It's probably more due to the s off process I've seen a lot of users with this issue who weren't on gingerbread also.
Take the data from your SD card and copy it to a folder on your computer. Wipe the card completely and format it in windows. Then put it in the phone and format it in Settings/Storage. then once you've done that put some stuff on it and see if it's being recognized. Finally you can copy all of your data over to the sd card again from the backup you made at the first step.
Yeah, I've got s-off, and I've reverted to GB OTA. But I've restored the ROM I was running on top of the ICS firmware, which must have the SD patch on it. So I'm trying to understand what's changed in order to navigate out of it.
In fact, I am already copying the files off so I can format the SD on another device. Something about great minds, I suppose...
Just wondering what's causing it, because I really don't know if the format's gonna help. Right now the phone doesn't even recognize the card from the ROM. Sees it fine in recovery though.
The mount points changed, if you had installed the patch to allow you to run a GB rom on the ICS firmware your mount points would be broken now. You should be able to flash the patch to allow you to run ICS on the old firmware and you should be good.
The patch just updates /system/etc/vold.fstab
So it looks like a device number associated with a drive is incremented. Apparently the ICS firmware reports this device at a higher number than the GB firmware, and so the GB won't see it unless fstab points to the correct index.
Since I'm on GB firmware now (thanks, s-off!) I can set the number back to the value in the GB RUU.
Having done that, my phone still does not recognize the card -- except in Amon Ra. Furthermore, the card was not recognized in an unmodified Droid X belonging to a co-worker. So something's wrong with the card, but it's not a clear failure.
I'm now running a FAT32 format from Windows, through Amon Ra, and I'm doing the full format rather than the quick version. Taking forever. We'll see. If this doesn't work, maybe I need to look for a card reader to format it.
Why might Amon Ra recognize the card, but not Android?
cpurick said:
So it looks like a device number associated with a drive is incremented. Apparently the ICS firmware reports this device at a higher number than the GB firmware, and so the GB won't see it unless fstab points to the correct index.
Since I'm on GB firmware now (thanks, s-off!) I can set the number back to the value in the GB RUU.
Having done that, my phone still does not recognize the card -- except in Amon Ra. Furthermore, the card was not recognized in an unmodified Droid X belonging to a co-worker. So something's wrong with the card, but it's not a clear failure.
I'm now running a FAT32 format from Windows, through Amon Ra, and I'm doing the full format rather than the quick version. Taking forever. We'll see. If this doesn't work, maybe I need to look for a card reader to format it.
Click to expand...
Click to collapse
HBOOT 2.21 simply mounts the "/sdcard" partition to a different EMMC block than previous 2.10/2.11 HBOOTs did. That is it. Its that simple. WHY did they make the change? I have no idea.
So, if you're on GB and you can't access your internal storage (/sdcard), all you need to do is simply flash an earlier HBOOT (2.10, or the 2.11 ENG HBOOT from the dev section) and make sure you're also using the corresponding GB radios. Then you have no more issues.
I have the 2.11 HBOOT and GB radios.
The problem is the External SD. I can share it between Amon Ra and Windows, but I can't mount it from Android. Android shows it unavailable. When I go to mount it, it briefly says, "Preparing SD Card," followed by a message telling me I can remove the SD card. The same thing is seen on multiple phones.
I did a long format, Fat32, from Windows 7 while the card was mounted in Amon Ra. I put a zip on the card and Amon Ra seems willing to flash it. I can definitely read and write it via recovery. But Android doesn't see it, and I think it's the card rather than my phone. Ideas? Anything I can do with partitions? Maybe there's something that can be "reset."
Each time I explore the card I find "lost.dir". I don't recall seeing that before.
cpurick said:
Each time I explore the card I find "lost.dir". I don't recall seeing that before.
Click to expand...
Click to collapse
Yup. Leave it alone. Been there all along, and not anything new. I've seen that directory going back to my Incredible two years ago, and I'm sure it goes back before that.
Try flashing the patch for gb firmware
Sent from my ADR6425LVW using Tapatalk 2
cpurick said:
I have the 2.11 HBOOT and GB radios.
The problem is the External SD. I can share it between Amon Ra and Windows, but I can't mount it from Android. Android shows it unavailable. When I go to mount it, it briefly says, "Preparing SD Card," followed by a message telling me I can remove the SD card. The same thing is seen on multiple phones.
I did a long format, Fat32, from Windows 7 while the card was mounted in Amon Ra. I put a zip on the card and Amon Ra seems willing to flash it. I can definitely read and write it via recovery. But Android doesn't see it, and I think it's the card rather than my phone. Ideas? Anything I can do with partitions? Maybe there's something that can be "reset."
Each time I explore the card I find "lost.dir". I don't recall seeing that before.
Click to expand...
Click to collapse
It was probably the formatting that did it. I would take it out, remove all partitions on it, and let the phone reformat it on its own.
cpurick said:
So it looks like a device number associated with a drive is incremented. Apparently the ICS firmware reports this device at a higher number than the GB firmware, and so the GB won't see it unless fstab points to the correct index.
Since I'm on GB firmware now (thanks, s-off!) I can set the number back to the value in the GB RUU.
Having done that, my phone still does not recognize the card -- except in Amon Ra. Furthermore, the card was not recognized in an unmodified Droid X belonging to a co-worker. So something's wrong with the card, but it's not a clear failure.
I'm now running a FAT32 format from Windows, through Amon Ra, and I'm doing the full format rather than the quick version. Taking forever. We'll see. If this doesn't work, maybe I need to look for a card reader to format it.
Why might Amon Ra recognize the card, but not Android?
Click to expand...
Click to collapse
I will tell you I tried hand editing mine and it would not take the changes no matter how many times I rebooted it. Flashed one of the patches and it worked like a charm. Don't ask me why, that was just my experience.
Related
The SD card slot on my phone seems to be broken. I've tried multiple SD cards and none of them seem to get read, so I've concluded that it must be the phone.
Im trying to unroot it so I can send it to verizon for a replacement. I was kind of depending on this method to do it:
http://forum.xda-developers.com/showthread.php?t=792026
but obviously I need the use of the SD card. So I'm kind of in a pickle.
Is there any other way to do it? Something that doesnt need an SD card?
The "Official" 2.1 RUU Utility (= Leak-V3) requires no SD Card
MultiUpload.com - RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
It runs on your Windows PC.
Charge your phone well (say, > 80%)
Turn it off
Plug it in to your PC (still off)
Start the Eris up in fastboot mode (Send+End)
Run the above (HTC) utility - follow the instructions on the screen.
Thanks, man. Just ran it. Worked perfectly.
Just got to install a few apps before I take it in so that it doesn't look too barebones >_>
This is really strange. I just put in the SD card, to see if it was still broken and it magically worked again @[email protected]
I tried with the same SD cards that I used when I was rooted and they all worked as well.
I guess this means I dont have to turn it in, but this is still very strange.
McFluffnStuff said:
This is really strange. I just put in the SD card, to see if it was still broken and it magically worked again @[email protected]
I tried with the same SD cards that I used when I was rooted and they all worked as well.
I guess this means I dont have to turn it in, but this is still very strange.
Click to expand...
Click to collapse
Bummer or Not Bummer? I'm not sure. Nothing like an intermittent problem to give you plenty of confidence.
Well, if you don't take it in, at least you will get more practice at rooting.
If you want to be one of cool kids on the block, you can update the unrooted RUU (= Leak-V3) software to the July 2010 OTA using the honest-to-goodness factory codes. You might want to do this anyway, because it will install the July 2010 HTC radio, if not for the "fun" involved.
Go visit this thread:
Consolidated HTC RUU, Leak, and OTA Downloads
and grab the "4th OTA" which converts 2.36.605.1 -> 2.37.605.4; the file name is
OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
You rename it to "update.zip", and put it on your SD card in the root folder, then:
- verify the file length and MD5 checksum (of the copy of the file on the SD card)
- charge your phone fully
- power your phone off and boot into recovery mode
(either Vol-Up+End, or HBOOT(Vol-Down+End) -> recovery)
- you will get that screen with the triangle and exclamation point; when that is showing, press Vol-Up+End again, and you will see the stock recovery menu.
- Choose the one that says something about SD:update.zip (or similar)
- Let it run through until it reboots (I can't recall, it may reboot twice).
Then, when you root this, you can take a Nandroid backup - then you will have a Nandroid backup of the July 2010 "Factory" configuration. The "cool kid on the block" part is that almost nobody has ever done this - most Eris rooters were already rooted when July 15-17 rolled around, or if they were stuck not rooted on Leak-V3, they got the OTA automatically. Very few people have actually ever used the factory recovery menu on the Eris. (I have done it just to look at it.)
Cheers
bftb0
McFluffnStuff said:
This is really strange. I just put in the SD card, to see if it was still broken and it magically worked again @[email protected]
I tried with the same SD cards that I used when I was rooted and they all worked as well.
Click to expand...
Click to collapse
Did you happen to partition your SD cards for apps2sd on a rooted 2.1 ROM and then try installing a Froyo ROM? If so, that is an explanation - (most) of the Froyo ROMs will not mount an SD card with more than one partition on it.
If this is the case, and you still want a Froyo ROM, you can backup the contents of your SD card, use Amon's Recovery to partition it again (setting the size of the ext2 and swap partitions to 0 bytes), and you should be ok. If the fact that your SD cards were partitioned was the issue...
Good catch doogald - I just assumed that this wasn't the case because the OP mentioned more than one SD card.
No, I was using a Froyo rom.
Also, I forgot to point out that it wasn't the first time it's happened. The Last time, however, I was able to get it to work again after a reboot. When I did get it to work, half the stuff on the card was missing. Luckily I had it all backed up, so it wasn't too much of a hassle.
This time, I couldn't get it to recognize the card at all, even after several reboots and trying several different cards.
But like I said, it works now. Ill probably re-root it again this weekend when I have the time. Hopefully, things work out differently this time.
I unlocked my bootloader, rooted, installed amon ra recovery, have flashed a couple different roms. This morning i flashed scott's cleanrom 4.0 booted up everything seemed to be looking fine. However i went to look in my gallery for photos and it just pops up the screen sd card unmounted. So i went to setting storage and clicked mount sd card and it says preparing sd card, but doesnt do anything. So then i looked in the file system. under /sdcard it says sd card empty mounted or unpresent. sdcard2 isnt even a file system (not positive its supposed to be) so basically i only have access to the RAM i think? ive rebooted, factory reset, id try flashing a new rom, but i cant mount the darn cards on the computer to flash a new rom (maybe i could do this from cmd with fastboot or something?) ive thought about trying to format the sd cards but im not sure how to do this especially since the internal one is also having troubles.
I would really appreciate help on this as i cant hardly do anything on this besides texts and phone calls right now!
Thanks for any help
noo_too_droid said:
I unlocked my bootloader, rooted, installed amon ra recovery, have flashed a couple different roms. This morning i flashed scott's cleanrom 4.0 booted up everything seemed to be looking fine. However i went to look in my gallery for photos and it just pops up the screen sd card unmounted. So i went to setting storage and clicked mount sd card and it says preparing sd card, but doesnt do anything. So then i looked in the file system. under /sdcard it says sd card empty mounted or unpresent. sdcard2 isnt even a file system (not positive its supposed to be) so basically i only have access to the RAM i think? ive rebooted, factory reset, id try flashing a new rom, but i cant mount the darn cards on the computer to flash a new rom (maybe i could do this from cmd with fastboot or something?) ive thought about trying to format the sd cards but im not sure how to do this especially since the internal one is also having troubles.
I would really appreciate help on this as i cant hardly do anything on this besides texts and phone calls right now!
Thanks for any help
Click to expand...
Click to collapse
Well, when you say you flashed a couple of roms.. the only rom at the time that would work with the new base was the stock rom that came with the RUU. Scott , then had the first rom with the new base. Using the old roms on the new base caused SD card issues that your describing , but I figured flashing Scott's rom would have fixed it . Easiest fix is if you backed up the stock rom that came with the RUU, if not only thing I can think of is to RUU again and start over. I know Dres is looking into this issue for Amon Ra in case the dev blocks changed , but until he does I would think reflashing RUU is the easiest suggestion.
Problem Solved
Thanks so much! I flashed the latest (that I could find) RUU 3.11.605.1 i got the boot.img and the stock rom out of the RUU and flashed them using fastboot and Amon Ra respectively. When I booted back up the sd cards were properly mounted and everything seems fixed. Thanks again for the quick helpful response!
Now, I still don't exactly understand what I did wrong. So let me try to get some things strait. So the latest RUU is the latest version of the leaked ROM (from HTC?) in question, ICS in our case. So whenever a new RUU is leaked all the developers build new roms on this RUU? and if i say, had been flashing roms from an old RUU, and then flashed a rom from a new RUU (maybe i also forgot to wipe things?) caused problems?
I'd just like to get a better idea of what the problem actually was, and why what i did fixed it. Hopefully someday i won't be so dependent on the great minds here on xda.
Thanks again for everything!
I'm in a similar boat.
I'm in a similar boat. I went straight from stock rooted gingerbread to CleanRom ICS and now I can't get the sd card to mount. CleanROM just kept rebooting over and over. I'm going to try the suggestion by the OP. Hopefully that fixes the problem.
I guess the dev block changed from the old base to the new. Amon ra is already updated. So when you Ruu again and ran the new stock it matched so fixed it. Just don't rum old roms or backups.
Sent from my ADR6425LVW using xda premium
Go into my ICS thread or any of the ICS threads and download the patch to run the new build on the old firmware to fix the mounts
I have kind of similar issue. My phone storage and sdcard are swapped. I only rooter and installed AmonRa recovery. I put 9gb of music on my card, but in setting my card looks empty and my phone storage only has 80m left.
Any ideas?
Thanks
what firmware are u on... u probably need to flash the other amonr ra version if you are on 3.14 flash 3.15 or vice versa
Seams to have started just after I S-Off'd my rezound. Took me forever to initially get it working and get cleanrom back onto it, where it immediatly started to reboot randomly after a minute or two, usually under quick/hard loads, it does it every time consistently when I try to Dial or Text someone. I also tried to upgrade to the leaked RUU and rom to fix this, nothing. The stock rom I could dial, but it did reboot once on lock screen. Custom roms reboot consistently. Help?
Did you flash the leak twice?
No, I followed instructions off of theandroidsoul,com rezound ics upgrade page to the 'T' since they supplied download links.
I'd post the page directly but I haven't reached my required post count.
It's a kernel upgrade via hboot, and a shell/rom flash via recovery, so I'm not sure if your expecting a different upgrade meathod.
Which am I expected to flash twice? And what is expected to change?
Check android community site with march 16 story to download rooted version for the leak. It should just be a ph98img.zip. before you do though, have you tried wiping everything in recovery, possibly 2 or 3 consecutive wipes, and then a completely clean install of Scott's stuff again? Also, are you on amon ra?
Edit- it would be the kernel to do twice. When it prompts at bootloader to update, you pick yes and if it doesn't hit all the entries, you have to run it again.b
I flashed the rom and the kernel twice earlier, stock seams to run flawlessly, I can dial, and the phone doesn't reboot Speed Ex 3D like it did earlier, though it plays double screened, weird. Anyway, I'll try flashing some various roms to see what happens.
Good to hear.
Ran into an issue, Stock ICS isn't mounting my SD card, simply says unavailable under storage. HBoot still finds the kernel upgrade, rather annoying when I'm trying to remove it to access recovery.
The format check earlier said Ext4, I assume RUU should be able to handle that. Would be unthinkable that I'd have to flash the GB fix.
have you checked under settings--about phone--software and made sure that it says android 4.0.3? I ran into a similar (maybe same) problem when I first tried flashing the leak firmware. It didn't fully flash correctly, so the first time it said I was still on GB and it could not mount my SD, the second time I flashed the ph98img.zip it said I was on 4.0.3 but still would not mount my SD. So I flashed it once more and everything was fine after that.
What the hell... I just noticed by radio is 1.22, I flashed the leaked radio awhile after the S-Off. Kinda screwy. I removed the external SD card, got into recovery, but when I mount the internal sd to the computer, I can't edit anything. Says full up to 1200kb if i read that right.
Btw, says 4.0.3 under software
SD Card reads normally under CleanRom DE, but still crashes
BAMF Senseless v2 crashes when I try to dial too.
Wait, is it the same sd you had in it when you did the S-off procedure? If so, have you reformatted it? If this is the problem, see sindroidx's how-to in the rezound general forum. If not, it still sounds like your sd card has either been corrupted/misformatted somehow. That's for external. If it is internal SD, see graymonkey44's "S-off is Official!!!" thread. It contains the fix for both, by the way.
swilbert80 said:
Wait, is it the same sd you had in it when you did the S-off procedure? If so, have you reformatted it? If this is the problem, see sindroidx's how-to in the rezound general forum. If not, it still sounds like your sd card has either been corrupted/misformatted somehow. That's for external. If it is internal SD, see graymonkey44's "S-off is Official!!!" thread. It contains the fix for both, by the way.
Click to expand...
Click to collapse
Definately, sounds like your SD card needs to be reformatted. Numerous posts on it , but some have had success just formatting in Windows ( might have to do it more than once to finally get it to show your full capacity) . I used Gparted Live CD to repartition and reformat to fat 32 and it worked great. Whatever your comfortable doing will work, but needs to be reformatted regardless. Also sounds like you should just RUU from scratch after your SD card is fixed , then start over once you know the phone is operating properly.
I RUU'd back to the OTA 2.011 and it fixed some odd issues I was having , now running the Sense 4 roms using the old firmware patch and everything is fine.
I formatted through recovery and RUU after I used a spare SD to install/update. Well this is what I don't get, under other Roms, my SD card mounts fine, but not under Leaked RUU, how ever if I'm on, say cleanrom and mount it to to the computer, windows acts like the external SD needs to be scanned/fixed, how ever I can still open and explore it just fine.
Ig I'll try reformatting my SD once more, then flash some GB kernels/fix
Will it matter if I'm on the GB or ICS bootloader?
sounds like the symptoms of not having the firmware patched.
What patch are you referring to?
In the meantime I'm going to try this kernel and run the GB > ICS fix
http://forum.xda-developers.com/showthread.php?t=1467793
swilbert80 said:
Wait, is it the same sd you had in it when you did the S-off procedure? If so, have you reformatted it? If this is the problem, see sindroidx's how-to in the rezound general forum. If not, it still sounds like your sd card has either been corrupted/misformatted somehow. That's for external. If it is internal SD, see graymonkey44's "S-off is Official!!!" thread. It contains the fix for both, by the way.
Click to expand...
Click to collapse
As I stated, Leaked RUU wont recognize either SD, CleanRom and others recognize both but reboot alot. I tried the internal fix by flashing the ICS Hboot for S-Off last night which changed nothing. I just now flashed a GB Kernel and ran the SD card fix to test with CleanRom and it still freezes/reboots.
-Edit-
Just checked, and it still says 4.0.3 under software. This is such a pain...
Also I can't access the internal SD card from the computer when I USB mount in recovery. It simply opens up blank.
http://forum.xda-developers.com/showthread.php?t=1560363 Sounds just like my problem.
The first guide I followed to upgrade was trash,
this guide has fixed everything:
http://www.teambamf.net/topic/3528-guide-to-install-ics-ruu-and-firmware-windows/
I did a nandroid restore (from this same external SD card). Android (ICS 4.0.3 , Sense 3.6) doesn't recognize the card. A root explorer shows the internal SD card as a folder, but the external SD card as a file of unknown type. The same card is read correctly by AmonRa Recovery, and through a card reader on the 'puter. Has this happened to anyone before?
I tried backing it up, reformatting (FAT32), and recopying, no difference.
Trying to mount it in AmonRa yields :
E: Can't mount /dev/block/mmcblk1p2
(File exists)
Talking to yourself again?
You're not s-off are you? I've seen a thread about an issue with the cards when s-off. It might also have to do with old firmware mixed with a newer ROM. Have you updated to the latest RUU, the global one?
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Might not have anything to do with it but can't hurt to get updated. Remember, I'm not an expert, I just play one in your threads. And you seemed so lonely in here I had to say something.
Hello? Hello? I thought I heard someone. Anyway, yeah, s-off, and not the latest RUU, but I thought it was the RUU the original ROM was based off. Could be mistaken. Next step IS to take that global RUU and try again, worst case, just start over from scratch.
Here, found this thread since you're s-off:
http://forum.xda-developers.com/showthread.php?t=1615418
feralicious said:
Here, found this thread since you're s-off:
http://forum.xda-developers.com/showthread.php?t=1615418
Click to expand...
Click to collapse
Hmmm... that looks..... risky. I'll try it when I get home tonight. Then if it fails I'll have time to go the new RUU route.
Thanks
So, of course, right after I posted that, I gave it a try anyway.... no go. Card reads/writes fine from recovery, but the Android OS refuses to see it. Back to original plan, re-RUU it tonight.
DIncLover said:
So, of course, right after I posted that, I gave it a try anyway.... no go. Card reads/writes fine from recovery, but the Android OS refuses to see it. Back to original plan, re-RUU it tonight.
Click to expand...
Click to collapse
Before you RUU again, try backing up the card, then reformatting it on your pc then pop it back in. I just remembered that I've read where that's fixed it for a few people.
You need to update to ICS firmware or use the old firmware patch if you're still on GB firmware, otherwise that shouldn't be the problem. What version of hboot are you on? Also what version of AmonRa?
feralicious said:
Before you RUU again, try backing up the card, then reformatting it on your pc then pop it back in. I just remembered that I've read where that's fixed it for a few people.
Click to expand...
Click to collapse
Tried that before.... no go.
mjones73 said:
You need to update to ICS firmware or use the old firmware patch if you're still on GB firmware, otherwise that shouldn't be the problem. What version of hboot are you on? Also what version of AmonRa?
Click to expand...
Click to collapse
HBoot = 2.25 , AmonRa=3.15 .... If I'm s-off, isn't the (ICS) firmware loaded with nandroid restore ?
DIncLover said:
HBoot = 2.25 , AmonRa=3.15 .... If I'm s-off, isn't the (ICS) firmware loaded with nandroid restore ?
Click to expand...
Click to collapse
Nandroid doesn't touch the firmware, you are running ICS firmware though.
mjones73 said:
Nandroid doesn't touch the firmware, you are running ICS firmware though.
Click to expand...
Click to collapse
You can tell that .... how? Through my HBOOT version?
Strangest thing happened last night. During the day I attempted the External SD-card fix linked to by feralicious, to no apparent avail. Last night, though I, out of the blue, saw an android notification that I had a blank SD card ... Do you want to format? I said OK. Afterwards, I went to Settings -> storage, and saw the SD was still unavailable .... rebooted, no change. I shut down the phone and put the SD card in a card reader and saw from my PC there was a sole LOST.DIR folder on the card. I restored my SD backup from PC, thinking maybe my problem is miraculously solved. Upon phone reboot, though, no change. SD card is still unavailable, though it can be seen from recovery. Tonight is (global) RUU night unless any more suggestions?
DIncLover said:
You can tell that .... how? Through my HBOOT version?
Strangest thing happened last night. During the day I attempted the External SD-card fix linked to by feralicious, to no apparent avail. Last night, though I, out of the blue, saw an android notification that I had a blank SD card ... Do you want to format? I said OK. Afterwards, I went to Settings -> storage, and saw the SD was still unavailable .... rebooted, no change. I shut down the phone and put the SD card in a card reader and saw from my PC there was a sole LOST.DIR folder on the card. I restored my SD backup from PC, thinking maybe my problem is miraculously solved. Upon phone reboot, though, no change. SD card is still unavailable, though it can be seen from recovery. Tonight is (global) RUU night unless any more suggestions?
Click to expand...
Click to collapse
Yes. Firmware refers to hboot and radios. Your hboot is the official ICS OTA.
shrike1978 said:
Yes. Firmware refers to hboot and radios. Your hboot is the official ICS OTA.
Click to expand...
Click to collapse
AmonRa nandroid gives the opportunity to backup and restore boot --- doesn't this mean I can effectively change firmware by restoring a different nandroid backup?
DIncLover said:
AmonRa nandroid gives the opportunity to backup and restore boot --- doesn't this mean I can effectively change firmware by restoring a different nandroid backup?
Click to expand...
Click to collapse
No, boot is just the kernel. There's no way to back up and change the firmware on the phone with nandroid.
OK, all good now. Had to re-RUU to the global, then reinstall latest version of ROM, then restore my apps and home screens, etc. Titanium backup was useful.
I still don't really understand how my card became unreadable, but c'est la vie (loose translation : $hit happens)
Hi folks. I had an unrooted Rezound. I used the HTC Dev site to get it to an unlocked bootloader. I installed the Amon-Ra recovery and used it to flash the Infection JB ROM. Now it boots into the white HTC screen, goes slightly darker white and doesn't move. I can get back into recovery but after some wipes to clear up problems, now I'm stuck. It won't mount the internal or external SD cards. I *can* boot into fastboot but when I try to push a different ROM, I get the message that it doesn't an android info file.
I think I might be okay if I can use flashboot to flash maybe an ICS based ROM but I'm not sure. It seemed the phone originally didn't like the 32 gig SD card in there (one boot prior to the flashing it said damaged SD card). I popped it out, put it in a USB card reader and formatted it to fat32. Recovery threw an error when trying to access the SD card to do the flashing of the Infection ROM so I just flashed it from the copy I had placed on the internal SD. I'm guessing I might have to flash a standard boot.img from flashboot and try things again?.
NapalmDawn said:
Hi folks. I had an unrooted Rezound. I used the HTC Dev site to get it to an unlocked bootloader. I installed the Amon-Ra recovery and used it to flash the Infection JB ROM. Now it boots into the white HTC screen, goes slightly darker white and doesn't move. I can get back into recovery but after some wipes to clear up problems, now I'm stuck. It won't mount the internal or external SD cards. I *can* boot into fastboot but when I try to push a different ROM, I get the message that it doesn't an android info file.
I think I might be okay if I can use flashboot to flash maybe an ICS based ROM but I'm not sure. It seemed the phone originally didn't like the 32 gig SD card in there (one boot prior to the flashing it said damaged SD card). I popped it out, put it in a USB card reader and formatted it to fat32. Recovery threw an error when trying to access the SD card to do the flashing of the Infection ROM so I just flashed it from the copy I had placed on the internal SD. I'm guessing I might have to flash a standard boot.img from flashboot and try things again?.
Click to expand...
Click to collapse
Try using the usb mount to access sdcard. you may have to reformat one if you have an extra one. Or format it prior to putting it in your Rezound. As long as you can access recovery you are not bricked.
dragonstalker said:
Try using the usb mount to access sdcard. you may have to reformat one if you have an extra one. Or format it prior to putting it in your Rezound. As long as you can access recovery you are not bricked.
Click to expand...
Click to collapse
Provided I can gain access to the SD card, what would be my next step? Flash an ICS rom?
When trying to access the internal SD from recovery, I get this error-can't mount /dev/block/mmcblk0p37 or mmcblk0p38. Invalid argument. If I try to flash anything from the SD card, it says that it is opening the package, gives another line and then kicks me right back to the recovery menu. From there, trying to pull up the external card leads to a blank directory unless I yank the battery and reseat the card (or potentially just reseating the battery). Does anybody have any ideas?
fixit if you are s-0n
Look around xda, or google and find/download RUU 3.14.605.12, which should be an *.exe executable file.
Use a md5 checksum utility to confirm validity, boot into fastboot, and run this RUU.
It should make everything OK again.
@Napalm
Format the sd card using your recovery.
If you still have it in its current state open the rom's zip file, copy out boot.img, and fastboot flash it. Then attempt booting like normal.
Thanks Michael and hi Snuzz! After doing more searching, I did notice an extra step in one of the roms I used. It mentioned about flashing the boot.img in hboot if S-On was true. For my rezound, yeah it's still S-on for me. When I get back to my main PC, I'll see what I can do. I really hope I can come back from it as I'm really looking fwd to upgrading from my Tbolt. The Rezound has such a nice camera and processor, I'd prefer not to have to go another route.
Oh my god. This is so horribly screwy. The problem all along.....it ws the stupid 32 gig SD card I was using. I put Rage 2.3 on a 16 gig card, tried to flash from that one and it worked perfectly. No need for the RUU. I'm happy I didn't need it because of this warning.
This will not work if you used the HTC Bootloader unlock tool. Your device must be fully stock with a locked bootloader or you must have S-Off
Click to expand...
Click to collapse
On the 32 gig card, the zip flash would go by very fast and then basically reboot the recovery. From there, well the thread covers that. As of right now, Rage 2.3 has booted and asking for initial setup info. Since Rage is going to be my first ROM on this device, anybody have any thoughts on it or comments on another they like more?