Can't boot up an encrypted device - G3 Q&A, Help & Troubleshooting

Hello,
I've been using my device normally, when all of a sudden it froze and shut itself down. I've tried booting it up multiple times, but it wouldn't do. I thought that it might be up to the battery, so I've gotten a new one, but it's not up to it.
However, I've been able to enter TWRP Recovery. I thought that wiping data, cache and dalvik would help me get rid of my problems, but it didn't. Obviously, I can't mount anything, because everything seems to be encrypted. I wanted to flash another ROM, but I can't do so without connecting the storage with my PC. Now I'm cluelessly stuck in the Recovery.
Can anyone help me? I'd be very grateful if so. I might have made a foolish mistake somewhere, so please don't get harsh on me. The custom rom I've been using is CandySix

Related

Stuck on boot screen :(

I flashed to pays rom, successfully yesterday.
today, i wanted to wipe my phone (entered wrong gmail account so didnt have access to paid apps)
after doing so, ive been stuck in an endless boot screen.
anyone shed some light on the situation?
Oops. I think this happened to some G1 roms too.
Reflash?
the rom was absolutely flawless before this.
ive tried.
with 2 different roms.
wiped everything i possibly can in recovers & fastboot
insult to injury; recovery-windows wont load, so i cant even get past recovery screen.
My mistake. recovery-windows is loading. now flashing. again.
so then, managed to flash some sense based roms alright, until i get past bootloader.
com.android.acore error messages all the time.
loaded nexdesire rom fine with no errors.
ideas anyone?
Out of interest, did you re-partition your SD Card for A2SD at all??
If so... Try re-partitioning it again in recovery mode, but use it all as storage (no ext partition), wipe and re-flash.
I did.
I'll try that now and pray it works
Get in!
Working absolutely fine now

[Q] Stuck on boot logo, no matter what??

Ok, so I flashed a MIUI port for the AT&T Note 2, and it was disgusting...it crashed everything, and needless to say I ended up stuck at the boot logo for a long time. FINALLY managed to get it to flash via Odin...so I flashed Stock Rom...and now it's stuck on Samsung logo...Ok..so I go flash CWM...do a wipe and everything, and install CM10.1 via that...stuck at CM logo. I've left each ROM plugged in, stuck on boot screen for over 20-30 minutes each. I'm at a loss of what to do. Could I need to flash a kernel? or am I missing something obvious? The good news, I guess, is with a few steps, I can get into DL mode and use Odin, and I can flash CWM and get into that..but I can't inject anything into my phone so CWM can use it, I only have what's there now, which is CM10.1. I'm so mad...I've never had too many issues with ROMs but this one jacked things up badly...guess that's what I get for using a port even though it noted that everything was working now. Anyway...does anyone have any advice?
Edit: I flashed CWM, and tried to clear cache/dalvik then factory reset...the first two worked...as soon as I hit factory reset, that's where the screen goes black and it resets...it's like it just refuses to do it. I'm seriously at a loss here. Is it toast?
Edit again: sorry but I'm trying more to give more info. I went into CWM and went to advanced and started formatting one by one...it's when you hit format /data that it immediately dies and restarts. So..something weird is going on there. Can I use a PIT file for this phone, if it exists, to reformat and just get it going? I'm desperate...
Us this http://forum.xda-developers.com/showthread.php?t=2052779 on a PC.
Follow directions and Odin back to stock.
Sent from my SAMSUNG-SGH-I317 using xda premium

[Q] CM10 m2 Encryption Issue

Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
fza99 said:
Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
Click to expand...
Click to collapse
I have some very bad news for you.... Encryption is a one way street. Once encrypted the only way back is to flash stock via fastboot.
I can't even start to explain how to use fastboot as I have never been in a situation where I have needed it.
recoveries lose all access on encrypted devices so this is the only way.
Here is some links to get you started... Please do research before you begin the process and make sure you've obtained the appropriate files. I will take no responsibility for bricking your device.
Flashing via Fastboot:
http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
Installing Fastboot on Windows:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Sent from my SGH-I747 using xda app-developers app

[Q] Friend did a bad file flash, Hard bricked phone

Okay my friends wife had an unlucky bad file flash and ended up hard bricking somehow.
And keep this in mind that she never flashed a Int. version.
She flashed the SlimRom 3.1.0-D2SPR then she flashed the custom kernel unlocker file
to use the K747 kernel for slimrom, but the thing was ( She has TWRP ) when she slid the bar to flash
the file, the screen went back to the TWRP home page she waited 5-10 minutes then she tried reflashing the file again
and it said failed. Rebooted and the phone's hard bricked after installing the kernel. ( No LED when USB plugged in for recharge,
No power or haptic feedback. )
Her husband used the same method to install slim rom and his phone is fine
but the screen never went to the TWRP home page, it went straight into installing it.
The thing that boggles my mind is that she flashed everything in order and it hard bricked.
Rom first, rebooted recovery, kernel unlock, cache and dalvik cleared. rebooted recovery
When she tried flashing the K747 AOSP Kernel, she said it never went to the page screen that would show
it install, it just went straight to the home page, retry flashing but failed. ( here's the weird part I've never experienced. )
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.
Spark91 said:
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.
Click to expand...
Click to collapse
So, I'm just going to rattle through my thought process on this, just to get things clear in my mind:
Her phone cannot turn on at all. Do a battery pull/replace and make sure that there's no going into recovery or download mode. If that's the case, then JTAG might be your only solution.
This happened when trying to flash a kernel. It seems unlikely that a kernel would screw up the bootloader. I was under the impression that only recovery zips touch the bootloader/recovery partition.
If the kernel or Rom zip was for an international GS3, then it would try to write to the bootloader partition. But since you said your buddy's phone flashed the same files just fine, it seems unlikely that they flashed the international zips.
I've had TWRP fail to flash a zip. Each time I tried to flash a zip, it would say it failed. All I had to do was reboot into recovery (even if I hadn't flashed a ROM, so I had no system file), and then I could flash the file. Sometimes TWRP had those issues for me. Her story reminded me exactly of when that happened to me, but if hers won't load into recovery (or download mode), that's a major difference.
After all that, I honestly have no clue how this happened. It sounds to me like the JTAG is the best bet. You can find them online for around $60. Sorry this happened, and I hope you find a good fix for your friend's wife.
Its possible that you can still fix this....
Couple questions. When you try to turn it on, what exactly happens? does it vibrate? what occurs?
There is a possiblity that you can bypass the idea of holding the power button and vol button, try to adb reboot recovery command. ive had this save me about 5 times now when flashing goes bad.
http://droidlessons.com/how-to-install-adb-on-a-windows-7-pc/
make sure adb is installed...
while the phone is trying to boot, keep typing or copy/pasting or in cmd pressing up and enter after you enter the command.
adb devices
if it gives you the UID of your phone you at least know that you might have the ability to fix it.
From here just type
adb reboot recovery and it will reboot into the recovery to allow you to flash a "good" kernel again.
Bit of advice.. I am always paranoid after going through this so many times of a bad flash. As a result i never stack flashes.. for instance.
if i want to flash a rom, kernel, modem, radio..
i wipe dalvik, flash rom, wipe dalvik, wipe system, wipe cache.
Reboot let android do its thing...
reboot into recovery.
wipe dalvik, flash kernel, wipe dalvik, wipe system, wipe cache.
reboot, let android fully boot up.
reboot into recovery
wipe dalvik, flash radio, wipe dalvik, wipe system, wipe cache.
reboot...you get the point.
Just precations i started doing because of issues ive had in the past. If you have a mac, the commands are a bit different so let me know...
This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!
topherk said:
This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!
Click to expand...
Click to collapse
When i had my evo things flashed slightly different.
There were many issues in kernel flashing where if the kernel didnt download properly or you had a bad dl. it will what we called soft-brick. This would allow the phone to "act" like it was booting up but only display a black screen and never boot. Screen would flicker, phone was active but nothing would display and it will not boot loop. kind of just freeze.
We noticed that if we connect the phone to the computer we could actually use adb to access the phone. from there we noticed that we could push recoveries, and even push kernels and radios to the phone even though it wasnt displaying anything.
I figured the easiest way to get through this issue is to see if you can Reboot Recovery through adb if it allows you, and hopefully then you can restore functionality.
Help possibly?
Can you get it into download mode and just use Odin to flash it?

[help] soft brick? Bootloop? Corrupted nand? Help!

Hi,
Recently my brother gave up on his G-Nexus due to some complications that I soon discover. After he gave up reviving his phone, I took the liberty to try to ''revive'' his phone and found the same frustration that plague my brother.
Here's the thing:
1. I reflashed STOCK ROM + UNROOT. (tried 4.0.4/ 4.2.2/ 4.3. No success)
2. the phone is unable to BOOT, just BOOT LOOPs.
3. CAN boot into FASTBOOT.
4. unable to enter STOCK RECOVERY. (or in any rare case I could, cleared data, but bootloop persists).
5. fastboot flashed recovery TWRP and CWM , cleared data, reboot, and bootloop persist.
I'm out of option. I've googled for hours and nothing seems to help. Hoping the members here could provide assistance.
I've sent the phone for a troubleshoot, and the man told me it was the motherboard that was the case.
The thing with this is that I've flashed different stock ROMS and wasn't able to boot, not one successful boot.
My theory is that I've had a corrupted NAND?
Could anyone help me?
Thanks in advance.
blooddoom said:
Hi,
Recently my brother gave up on his G-Nexus due to some complications that I soon discover. After he gave up reviving his phone, I took the liberty to try to ''revive'' his phone and found the same frustration that plague my brother.
Here's the thing:
1. I reflashed STOCK ROM + UNROOT. (tried 4.0.4/ 4.2.2/ 4.3. No success)
2. the phone is unable to BOOT, just BOOT LOOPs.
3. CAN boot into FASTBOOT.
4. unable to enter STOCK RECOVERY. (or in any rare case I could, cleared data, but bootloop persists).
5. fastboot flashed recovery TWRP and CWM , cleared data, reboot, and bootloop persist.
I'm out of option. I've googled for hours and nothing seems to help. Hoping the members here could provide assistance.
I've sent the phone for a troubleshoot, and the man told me it was the motherboard that was the case.
The thing with this is that I've flashed different stock ROMS and wasn't able to boot, not one successful boot.
My theory is that I've had a corrupted NAND?
Could anyone help me?
Thanks in advance.
Click to expand...
Click to collapse
If you've flashed the phone back to stock and it still won't boot then there's probably nothing you can do. Time for a new phone.

Categories

Resources