• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Media files not showing up

Are they in a sub folder of a folder whose name starts with a period? A folder whose name starts with a period doesn't show up in the Gallery. Or if the file name starts with a period. That's how Hide It Pro hides your stuff.

Nope, no periods.
 
Sorry for the late response, work got a hold of me today. :mad::p

Both of these can be wiped from the: Settings / Storage / "Phone Storage" and "Storage Card" menu's

Both cases it's "Erase Phone Storage / Storage Card"

Make sure you back up your info first!! ;)

After that, I'd boot to recovery, full wipe everything, then try one more reload of the rom. Then restore the files and see if it fixes it. :)

Followed all these steps and had no luck.
 
just curious if you have the same issue on aosp. i know you said you had the same issue with viper and mean as well. curious to see if cm10 would be any better.
 
just curious if you have the same issue on aosp. i know you said you had the same issue with viper and mean as well. curious to see if cm10 would be any better.

I haven't tried an AOSP ROM yet, if I was able to use all the Sense features I would strongly consider it. Or maybe I should just try CM10 to see if it does just fix my issues.
 
Man, something is not right here. I've never seen sometyhing like this before. A reformat should have fixed any errors, unless the card itself is borked.

Just for a little refresher, did you go full S-off for root?

Also I think we should pull these posts out and start a new thread for this issue. This is no longer just a Viper issue. Would you be opposed to this jl79?

I'll also check with the HTC guru and see if we can get to the bottom of this.
 
Man, something is not right here. I've never seen sometyhing like this before. A reformat should have fixed any errors, unless the card itself is borked.

Just for a little refresher, did you go full S-off for root?

Also I think we should pull these posts out and start a new thread for this issue. This is no longer just a Viper issue. Would you be opposed to this jl79?

I'll also check with the HTC guru and see if we can get to the bottom of this.

Let's do it, this is sounding like a phone issue.

The phone is s-on.
 
Man, something is not right here. I've never seen sometyhing like this before. A reformat should have fixed any errors, unless the card itself is borked.

The card worked fine in my old EVO, plus an exact copy of the files are on the internal storage (sdcard) card as well, so shouldn't they show up from that location even if the external (sdcard2) card was borked?

Just for a little refresher, did you go full S-off for root?

No, I was not able to get Ubuntu to work on my laptop so I just went with the manual HTC Dev unlock and then flashed Mean ROM to get rooted.

Also I think we should pull these posts out and start a new thread for this issue. This is no longer just a Viper issue. Would you be opposed to this jl79?

I don't have an issue with that at all...maybe I am an extremely odd case here and getting it out in the open could clear it up!

I'll also check with the HTC guru and see if we can get to the bottom of this.

Sounds good...thanks for all your help!
 
Ok, I'll do this after work.

Since the phone is S-on, could we try to relock the botloader and run an RUU?

I PM'd Scotty too maybe he can think of something we're missing. :o

I am willing to try anything...but I was told re-locking and then starting over fresh would not change anything.

Here is everything I could think of information wise about my device:

*** LOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.19.0000
RADIO-1.12.11.0809
OpenDSP-v29.1.0.45.0622
eMMC-boot
Aug 9 2012, 15:14:25


Hardware version: 0003

Android version: 4.0.4

HTC Sense version: 4.1

Software version: Viper4G 2.0.2

HTC SDK API level: 4.24

HTC Extension version: HTCExtension_403_1_GA_22

PRI version: 2.45_003

PRL version: 25009

Kernel version: 3.0.8-01680-gb6402b4
root@ABM030#1
SMP PREEMPT

Baseband version: 1.12.11.0809

Build number: 2.13.651.1 CL99866 release-keys

Browser version: WebKit/534.30
 
OK, got everything moved to a new thread. Scotty is due to check in this evening when he has time.

I'm thinking as of right now an RUU is probably in order. Stuff not showing up when it's in internal memory is way too strange.
 
Ok, I'll do this after work.

Since the phone is S-on, could we try to relock the botloader and run an RUU?

I PM'd Scotty too maybe he can think of something we're missing. :o

Wow this is a strange issue indeed... Considering everything that's been tried, I think I would relock and run an ruu.

After we know that it works 100% stock,we should be able to make it work with some custom roms. Its easy enuff to reunlock after. :)
 
Wow this is a strange issue indeed... Considering everything that's been tried, I think I would relock and run an ruu.

After we know that it works 100% stock,we should be able to make it work with some custom roms. Its easy enuff to reunlock after. :)

This was my hunch as well. I wonder what the he-double hockey stick is causing this. :mad:

The command to relock the bootloader is: "fastboot oem lock" correct?
 
Okay, so is there a detailed guide as to what I need to do to return to stock? Should I run the RUU first then re-lock the bootloader?
 
Hold that thought jl, I'm looking for a specific thread, that I can't believe I've lost. :mad::p


Ok, you need to relock the bootloader first, then run the RUU.

http://shipped-roms.com/download.php?category=android&model=Jewel&file=RUU_JEWEL_CLICS_40_S_Sprint_WWE-2.13.651.1_Radio_1.12.11.0809_NV_SPCS-2.45_003_release_277028_signed.exe


Remember, this will wipe the phone clean, so save anything you might want from the internal memory. This won't mess with your external SD card.

This is the same exact software, radios, etc that are on the phone now, so you shouldn't have any issues. The RUU is an executable file that you run from your computer. Charge the phone up pretty good, then run the RUU on your PC. It'll tell you when to plug your phone / follow the prompts. Be patient, this process takes a little while. :)

Once we run the RUU, then we can look and see if the issue still persists. :)
 
Okay, so is there a detailed guide as to what I need to do to return to stock? Should I run the RUU first then re-lock the bootloader?


After whatever granite's got up his sleeve,all you need to do if its still needed,is:
-put phone in fastboot,plug in
-open cmd,change to folder that has adb/fastboot
cd c:\foldername
-make sure phone is connected:
fastboot devices. (should return serial number)
-relock bootloader
fastboot oem lock

This may give you a security warning and lock you into bootloader. Don't panic,its normal. You can always re-unlock with your original token if you need to.

-run ruu. :)
 
After whatever granite's got up his sleeve,all you need to do if its still needed,is:
-put phone in fastboot,plug in
-open cmd,change to folder that has adb/fastboot
cd c:\foldername
-make sure phone is connected:
fastboot devices. (should return serial number)
-relock bootloader
fastboot oem lock

This may give you a security warning and lock you into bootloader. Don't panic,its normal. You can always re-unlock with your original token if you need to.

-run ruu. :)

Okay sounds good!

Three quick questions...first, is there supposed to be underscores in between the spaces of those commands? Second, how exactly do I choose the correct RUU to run? And third, when I do go to re-unlock later on do I need that original token that I used to the first time to unlock? I did not keep that original token copied anywhere.
 
Hold that thought jl, I'm looking for a specific thread, that I can't believe I've lost. :mad::p


Ok, you need to relock the bootloader first, then run the RUU.

http://shipped-roms.com/download.php?category=android&model=Jewel&file=RUU_JEWEL_CLICS_40_S_Sprint_WWE-2.13.651.1_Radio_1.12.11.0809_NV_SPCS-2.45_003_release_277028_signed.exe


Remember, this will wipe the phone clean, so save anything you might want from the internal memory. This won't mess with your external SD card.

This is the same exact software, radios, etc that are on the phone now, so you shouldn't have any issues. The RUU is an executable file that you run from your computer. Charge the phone up pretty good, then run the RUU on your PC. It'll tell you when to plug your phone / follow the prompts. Be patient, this process takes a little while. :)

Once we run the RUU, then we can look and see if the issue still persists. :)

Okay sounds good!

Three quick questions...first, is there supposed to be underscores in between the spaces of those commands? Second, how exactly do I choose the correct RUU to run? And third, when I do go to re-unlock later on do I need that original token that I used to the first time to unlock? I did not keep that original token copied anywhere.

Ok, I edited my post above instead of just posting down here, lol. I've quoted what I posted above so you've get it in-line. ;)

First:
There should not be underscores, but spaces<spacebar>.

Second:
I linked the correct RUU for your hboot and radio version.

Third:
When you go to unlock again you'll need to get a new token.
 
Ok, I edited my post above instead of just posting down here, lol. I've quoted what I posted above so you've get it in-line. ;)

First:
There should not be underscores, but spaces<spacebar>.

Second:
I linked the correct RUU for your hboot and radio version.

Third:
When you go to unlock again you'll need to get a new token.

Perfect! Thanks so much! Going to make my back-ups and get on with the re-locking and RUU!
 
One more quick question...after re-locking, do I reboot and then run the RUU or do I stay in fastboot?
 
Back
Top Bottom