Develop Bugs

[Q] Encryption Unsuccessful Recovery - Help!

So here is the situation:
Samsung Galaxy S3 T999 with no external SD card (at the moment).
Locked to TMobile, but running on StraightTalk.
Rooted using ODIN and Root66.
Installed CWM (whatever the most recent version is) by way of ROM Manager.
Installed Cyanogenmod 10.0.0-d2tmo.
Dorked around for a while.
Attempted to encrypt phone.
Encryption failed, and I am now faced with the ubiquitous "Encryption unsuccessful" error.
I can still access CWM, and can still put the phone in Download Mode. I have attempted to delete/clear all partitions/caches through CWM, but, unsurprisingly, that did nothing. Internal SD card will not mount.
I have been doing some reading throughout the various forums here, and while I am fairly sure how to proceed, I want to make sure before diving in:
1. Is this recoverable through ODIN / Root66?
1. a. Will I need an external SD Card for ODIN?
2. Barring that, has anyone found a better work-around than using an external SD card to boot your phone, and apparently ignoring the onboard storage?
Thanks for whatever help you can provide... I know just enough to root and flash, but this went *way* over my head .

ODIN was the trick - plugged in the phone, flashed it back to a rooted stock, it rebooted, had the whole "Encryption Unsuccessful" screen when it came back up, I may have uttered a few choice words, pushed the "reset" button, the phone sat there for a good long while, and came back up in the rooted stock. Flashed CM on the phone, and we are back at work again.
Note to self - no more whole-phone encryption. Bummer.
Coming from an HTC Incredible, this whole "ODIN" thing is downright awesome.

Glad you figured it out.

The Encyption Bug is affecting the S3s now?!?! I though it was only prevalent on the first Galaxy S Devices. Is this a Cyanogenmod issue?

I cannot say if it is THE "encryption unsuccessful" bug, but I cannot think of any other reason this would have happened - the phone was chugging merrily along at encrypting itself (about 35% last I paid attention to it) until it was not, in a safe location, away from pets / small children / etc. It was plugged in, charged adequately, and had a PIN already set.
Annoying as hell, but at least it was recoverable!

I just experienced the same issue. Encrytion fail galaxy s3 while I was on custom rom. I tried everything. First you need to go to sammobile and download the firmware that matches your device. Download the newest version of odin. Download the newest samsung drivers. Go in to odin and attach the tar file in the pda section of odin. Flash it! Ta Da! Back to stock. Now all you have to do is root and install cwm.

Problems after restoring backup

I have recently acquired a Telus/Koodo GSM HTC One V and successfully installed Shpongle. I noticed there were problems when connecting the phone to my computer, it appears as two removable devices and a CD drive. I never did try connecting the phone to a computer in its stock condition, I assumed transferring files to the phone would not be an issue. Anyway, I decided to restore the backup I created of the stock ROM installation to see if there is a greater hardware issue with the phone. The result of the backup is a phone that hangs on the splash screen.
What I have done to the phone up to this point.
Unlock the bootloader
Root
Flash Recovery - TWRP v2.3.3.0
Backup Stock ROM with TWRP
Install custom ROM (shpongle_primou-20130521) and Kernel (boot-HELLBOY-20130514 )
Install GAPPS
Noticed problem with when trying to copy files to the phone.
Restore backup of stock ROM - failed
I can still get to the bootloader and the recovery.
If the connectivity issues can be resolved with a simple fix then I do not mind going back to the custom ROM. If there is no fix or it is too late to implement, I would very much like to get the phone back to the stock condition and test the connectivity issues. What are the appropriate next steps to remedy this situation?

You need a kernel change. Titanium kiss might work. There is also a stock kernel linked in one of these threads somewhere. Not sure, but I may have downloaded it

Thanks mrcorey for the insight on the kernel incompatibility.
I downloaded the RUU and found instructions to extract and flash the ROM and kernel to the phone. After upgrading it by running the RUU completely, I had a working phone again. Everything is back to stock as far as I can tell and USB connectivity is as it should be. Once connected to a PC and selecting the disk drive option on the stock HTC ROM both the internal memory and the microSD card are available in windows explorer. Why is the internal memory and card not accessible in windows when I had Sphongle installed on the phone? Is there a option that was not set right to get things to work properly?

[Q] Bricked Phone...Peculiar Situation

Hey guys,
First off, I've searched far and wide for any help with my problem but it is such a peculiar situation that I have yet to find someone with a similar situation. I expect if I want to ever use my M8 again, I'll need to send it to HTC and pay a few hundred bucks to fix it. But maybe someone here will have an idea that I've missed.
Shortly after getting my M8, I unlocked my device, rooted it and installed a few roms. Everything was fine save for one major thing: no matter which PC I used (and I used MANY - 3 different windows destops, a windows desktop at the office and my Macbook Pro) the device was never able to mount and make the storage accessible. I knew at that point something at some point had gone wrong. I've long preferred to use a wireless file transfer app to send stuff to and from my phone so I wouldn't have to break out all my cables so I figured it wouldn't be a big deal. I'd make it work.
A few days ago, I decided to try a different rom than what I'd been using for months (HD Revolution - great rom!) and downloaded everything required. I booted to TWRP, wiped the usual stuff and flashed my rom. When I rebooted, I was continually met with a crash as soon as the phone started and was never able to get into the OS. No big deal - this has happened before with other devices, so I didn't sweat it. I simply powered down the phone and tried to get back to recovery. Here's where the problem really kicked in : when attempting to boot to recovery, my phone will bring up the Hboot screen but instantly try to select the first option, thus not allowing me to scroll down to "Recovery". No matter what I do, it brings up the white Hboot screen, automatically selects the first option, gives me some error (I'm at work so I don't have the device in front of me) and tries to boot to the OS. That takes us back to the automatic crash.
Now, I know usually the solution would involve USB and ADB, but like I mentioned at the start of my sad tale, connecting my phone to PC's results either in nothing (Mac) or a "the device has failed" message in Windows. I've tried removing all the phone drivers, reinstalling and using a few toolkit methods - the phone is just never ever detected.
So, that's it. I'm pretty much resigned to sending my phone in and the HTC folks quoted me about $200. I do have a functional phone at the moment so it isn't the worst situation in the world, but if I could fix this I'd be able to using it as my main device again or sell it for a good chunk of change - I just bought it in June.
Sorry for the long read!

As far as the storage issue, never seen that happen before so I'm not sure. When you plug it in to the computer does the phone ask if you want to connect it as a storage device etc?
The bootloader is a very peculiar problem. It almost sounds like you have an img file that its trying to read as soon as you boot into boot loader.
Try to install HTC sync. And make sure the computer has an internet connection when you plug it in via usb.

Try to flash stock recovery fw buddy
Maybe thats problem RUU
Cek mike blg to find all stock recovery fw
After that install custom recovery again

This sounds a little familiar.
In my experience I've found some firmware versions and ROMs very choppy.
I once had a problem with storage too, couldn't send anything over to my phone.
Fortunately I could access recovery, so used ADB sideload and installed another ROM. And went to another firmware and never looked back.
The last 401.6 firmware gave me all sorts of issue.
If you can access fastboot I'd also recommend new firmware 401.7 is working flawlessly for me with ARHD 21.
Sent from my HTC One_M8 using XDA Free mobile app

I would try putting one of the bootable ruus on your SD card so when it goes to your hboot, it'll read the RUU and install it

Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.

Xavierc123 said:
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Click to expand...
Click to collapse
Download a rom that can use the 2.xx firmware. Look around and you should be able to find the roms. There's still plenty out there. Here's a little suggestion, reflash TWRP (or other recovery) through fastboot than grab a SD card and place the rom into the SD card and install the rom using through the use of a SD card. Just remember to do a full wipe before that

Soft bricked SPH-L710- Possible to recover data or repair without wiping?

I was using Chrome when the phone froze. I restarted it, and now the phone just hangs at the Samsung logo.
I have a completely stock unrooted Sprint SPH-L710. I'm moderately sure the phone is on MD4 since I didn't want Knox. It would be nice if there were a way to double check, though, since I don't remember why it stopped pestering me to upgrade. The phone doesn't boot far enough to get into safe mode, but it will enter recovery and download mode. Clearing the cache in recovery had no effect.
My PC and Kies don't see it when I connect it.
My contacts and photos are mostly backed up, so I'm more worried about salvaging other things, like Chrome bookmarks. My bookmarks aren't synchronized with Google. Apparently root is required to access them, so I never got around to it. It would be nice to recover text messages and gamesaves too. I haven't tried a factory reset yet since that would wipe everything.
What should I do from here? Is it possible to install a custom recovery at this point and use that to backup files?
Or should I try to flash a stock rom from the SD card or Odin? Or will that wipe everything or cause other problems?
I don't have USB debugging activated, so is there anything useful I'd be be able to do with ADB?
Or should I just shrug and go for the factory reset?
Thanks guys.

It's been an educational experience.
Without root or USB debugging enabled, it's apparently impossible to install custom firmware from soft bricked status.
ADB was never even able to see my phone. Not even in recovery or download modes.
Odin is a surprisingly temperamental program. It would see my phone, but not successfully flash until I uninstalled Kies. Rwilco's ROM's and one click flashes were all entirely unsuccessful. It's difficult to find older GS3 ROM's since link rot has claimed nearly all of them. There's about a million skeychy Samsung firmware/update sites, and most of them are worthless.
Heimdall is a little disappointing. You can't just point it at a ROM. You have to track down a Heimdall specific package. I couldn't find a suitable one.
Eventually, I found a sketchy Samsung firmware site that had the MD4 ROM, and it actually flashed in Odin. Then Odin stopped seeing my phone entirely.
So, I ordered a Tmobile Note 4 to use on Ting. It's cheaper, and I like the removable battery and microSD. Just for kicks, I factory reset the S3. To my surprise, the factory reset worked. I guess I should have tried that before I ordered a new phone
In the meantime, I guess I will still try to recover files, demote the S3 to media player/backup phone status, and use the incoming Note 4 as my daily driver.
From here on, I guess it means rooting and monthly backups.
Thanks guys.

When you boot into download mode you'll see your Knox flag if the phone has been upgraded to a Knoxed up firmware. I'm too lazy to check but it looks something like Knox: 0x0 or 0x1.

problems after rooting

I just rooted my brand new OP5T and ever since I've been experiencing problems. If I download anything through the browser I get errors saying that the download could not continue because it can't find my SD card even though this phone doesn't use cards.
Also, if I connect it to my PC under file transfer I can't transfer files, but if I connected it to my pc mounted in TWRP then it works just fine.
Anyone any idea on how to solve these problems? I already tried a factory reset...

It would also seem as though taking pictures, seeing pictures, music and video doesn't work either any more...

Nothing like this here. I would suggest repeating the whole process using:
[TOOL][OP5T] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

Nothing like this for me too. Rooted, kernel changed and TWRP and all fine.

OrtizFerrari said:
Nothing like this for me too. Rooted, kernel changed and TWRP and all fine.
Click to expand...
Click to collapse
I watched a video on how to do it, but I don't think I have flashed a different kernel... I simply rooted my phone. I'm still on stock, as I intended in the first place whilst awaiting the Oreo update.

Format data

This will work
https://www.youtube.com/watch?v=y6R6t2RdKWg