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

Root Help! Something really borked, tough time recovering

I re-downloaded 1.71 full since I was considering flashing that in its entirety. Something must really be off.

I've downloaded 1.71 several times. On the Venom site it says the md5 checksum is: 3D438D80EE5F65A7357B0E28D3E333CA

However, after downloading the file, copying it to my phone's SD card root (because one cannot download directly to the phone thanks to Google's latest restrictions), calculating the md5 checksum shows this:

b428a5d5d7062d4f856bf4e5280f371f

-----------------------------------------------

BTW, since I'm new to Verizon, I called their tech support this evening to ask where the nearest store is, in the event I'm able to return this phone for an exchange. Because I'm past 30 days by one week, they'd send a replacement via FedEx, which is fine. However, it's what the gal on the phone was explaining that intrigued me. She was elaborating how they wanted me to do a backup to Verizon Cloud to restore stuff (that's what nandroid and Titanium is for, honey), but she also said that before they would authorize an exchange, they would "be able to see the software and everything else that was ever downloaded to my phone" so that they'd be able to see if anything corrupted it and killed the ringer.

Interesting. So Verizon has the ability to see inside one's phone from the Internet or something like that?
 
I'm DLing from the mirrored Germany site as we speak. VERY slow, BTW.

Truthfully, I've never had a download issue before when I've DLd anything related to rooting. Weird that it's happening now.

Why the hell did Google stop our ability to DL directly to the phone or the SD card?
 
Lord Vader said:
I'm DLing from the mirrored Germany site as we speak. VERY slow, BTW.

Truthfully, I've never had a download issue before when I've DLd anything related to rooting. Weird that it's happening now.

Why the hell did Google stop our ability to DL directly to the phone or the SD card?
Click to expand...

They haven't, they just compartmentalized it.

Same thing is coming soon to internal storage.

Check out my edit for the fix.

There's also an Xposed module for it -

http://forum.xda-developers.com/xposed/modules/kitkat-sd-card-access-t2790992
 
EarlyMon said:
I find that very surprising.

And if you have some serious download corruption, that could explain any number of things.

Try one of the mirror sites?

By the way - I use Dolphin and download directly all of the time.

ViperOneM8 had the workaround built in but check out "SDFix: KitKat Writable MicroSD"

https://play.google.com/store/apps/details?id=nextapp.sdfix
Click to expand...

EarlyMon said:
They haven't, they just compartmentalized it.

Same thing is coming soon to internal storage.

Check out my edit for the fix.

There's also an Xposed module for it -

[MOD][KK][XPOSED] KitKat SD Card Full Access | Xposed General | XDA Forum
Click to expand...


Someone up there doesn't like me. LOL

I tried those .apks to get write access to my SD card, but I'm still unable to save to the card. The first app to which you allude tells me nothing was modified in my system because I already have enabled write access to the card. However, if that is true, how come I'm still unable to save to it? :p
 
Lord Vader said:
Someone up there doesn't like me. LOL

I tried those .apks to get write access to my SD card, but I'm still unable to save to the card. The first app to which you allude tells me nothing was modified in my system because I already have enabled write access to the card. However, if that is true, how come I'm still unable to save to it? :p
Click to expand...

I can only guess that it may be a corrupted rom or something.

One of the XDA guys asked, were you sure that you have the Verizon TWRP?

Not sure what else could cause so much trouble.
 
I'm 99% positive it's Verizon, because I went to their site. I remember when I installed GooManager and tried to install TWRP from there, per the TWRP site's recommended method, I got the message, "Unable to find a recovery for your device. Check back later."

I then had to do it via the fastboot method explained here.
 
That's the right site and fastboot flash is definitely the right way.

Flip a coin - if it comes up wrong, maybe re-download and flash TWRP again.

It won't hurt and you've definitely been forced to flash nearly everything else anyway.

You might also consider a full backup of your internal storage and sd card and just format both via the factory data reset or full wipe - but practice moving the rom over in TWRP Advanced first.

So - backup, download good rom (check md5 on your pc), wipe everything, load rom zip from pc via TWRP, then install.

If you used our Mini-SDK, there's an md5 checker included.
 
To be continued, as it's late here and 5:00 a.m. comes early. I'll have to figure out SOMEthing, and soon, because all my md5 checks come up totally mismatched. :confused:

Another day with missed calls due to no phone ringer. :p
 
lotddragon said:
The manufacturer should replace it, not the company that sells it but this is becoming a back and forth thing. The CLNR phones are actually really good

Sent from my ViperOne M8
Click to expand...

So my CLNR phone arrives today. It's still in the box, sealed. Haven't removed it yet. I go get my current One M8, back everything up via Titanium, then do a factory reset. Just for the heck of it, I restored a previous backup, that being Viper ROM 1.70, the very first version I flashed when I successfully rooted my phone. Out of curiosity, I called my phone from my home #, and wouldn't you know it? The ringer worked! I messed around with it some more, then used Titanium to restore all missing apps and all system data, tested it again, and voila! Ringer's working, everything just like new.

So, now I have to call Verizon and let them know my original phone appears to be just fine. I'm guessing I should not send the original back and choose to keep the replacement. (To be safe, I'll hold on to both until Monday to make sure my original one doesn't go haywire again.)

For the record, I do NOT know why this particular factory reset followed by flashing Viper ROM in its first form for me ended up working, especially after a factory reset and stock, rooted ROM didn't help.

-----------------------------

On a related note...I picked up a 64GB microSD card and am going to transfer the contents of my current 32GB card. I remember a couple years ago using AmonRA to partition my cards. Questions:


  1. Is there a way to do that now?
  2. If so, is it even recommended anymore, especially when one has a 64GB card with 90 speed?
  3. Can I just simply just copy my current card to the new one, insert that, and be on my way?
 
Yeah, I think that you want to avoid old solutions, the new file system is a different ball game.

Format the new card on your phone, copy old to pc to new and you ought to be fine.
 
Well, if I format it on the phone, it formats only in FAT32, whereas if I do it on my PC, then copy the current card's contents to the new one's, my PC will format it in exFAT, which allows for larger files. Theoretically, this should work. It won't hurt to try.

(I've been sharing this with the XDA folks in the Verizon M8 thread.)
 
An update...

I formatted it exFAT in Windows 7, then I transferred the contents of my old card to the new one. Everything appeared to be OK, so I ran some apps that I know were on the card and not internal storage. They're so far running fine.

For now, it seems to have worked.
 
Lord Vader said:
Well, if I format it on the phone, it formats only in FAT32, whereas if I do it on my PC, then copy the current card's contents to the new one's, my PC will format it in exFAT, which allows for larger files. Theoretically, this should work. It won't hurt to try.

(I've been sharing this with the XDA folks in the Verizon M8 thread.)
Click to expand...

http://teamw.in/exFAT

In Terminal Emulator, check out how the sd card is being treated with the mount command.

If it says vfat you may want to rethink your strategy.

If you plan to use the sd card with TWRP, you may have issues.

But this is the reason that I recommended a phone format -

https://www.sdcard.org/downloads/formatter_4/

Best luck, glad you got it sorted, which fat is best for you is a lot smaller problem than you were having. :)


PS - I'm very surprised that your phone formatted the card FAT32 and not vFAT.

I haven't seen that before.
 
EarlyMon said:
PS - I'm very surprised that your phone formatted the card FAT32 and not vFAT.

I haven't seen that before.
Click to expand...

Actually, it wasn't my phone that formatted it; rather, it was formatted on my PC using Windows 7. It formatted exFAT, then I copied the contents of the other card to this new one, inserted it into the phone, and it's up and running. However, alluding to what you mentioned above--I have not yet rebooted into recovery or tried to use TWRP. It sounds like if I do, I'll experience problems.

Truthfully, I've never had files larger than 4GB, which is the limit of FAT32 formatting (exFAT formatting not having this limit, of course). If TWRP won't work for me because of this issue, I don't have a problem reformatting it using FAT32, then recopying the card contents. I got the new, larger card only because I was running out of space (hard to believe, I know).
 
Yep, understand as you said originally, it was the pc that formatted it exFAT.

What I'm curious about is the phone formatting fat32, also as you mentioned.

I know at one time that Windows would report vfat as fat32 - even when it wasn't so.
 
You must log in or register to reply here.
Back
Top Bottom