Hello,
I may have bricked my phone but I'm open to suggestions of possible solutions.
I upgraded to lollipop and everything was working great, I decided to try out the encryption functionality and now it doesn't boot...
It gives me an error screen saying that encryption failed, perform a factory reset. I have done so and it still won't turn on...
Since I have done a ADB push rom.zip to it and that didn't work.
Tried both TWRP and CWM to factory reset...
Do you guys have any other ideas?
Thanks
Anthony
Solved
I did end up finding a solution, thought it would be nice to share just in case someone else has the same problem.
Flashing to CM12 actually worked and got me through but I wasn't happy being limited to CM12 because when I flashed back to the rom it had the same issue.
I flashed to a standard rom from Samsung and used it's factory recovery menu to do the reset and that worked
Related
Hello,
I've got a problem with my gt-i9505.
I've managed to root the phone and install TWRP.
So i decided to install CM10.2 (21-08) and the right gapps for it.
Everything worked very good and I couldn't be happier.
All my apps were back and it was ready to use it!
I turned off the phone and went to sleep.
The next day i turned it on and it got stuck on the bootscreen (not the CM bootscreen, but the SAMSUNG GALAXY S4 bootscreen).
So I tried to do factory reset and install rom again, gapps again, afterwards again wipe dalvik and cache.
But i keep having the same problem. Right now after flashing the rom it doesn't even boot up the first time.
I also tried going back to 10.1, but same problem.
I don't know what to do, i just got my s4. Really hope i can fix it.
Luckily i can enter the recovery. But i didn't do a backup or anything.
Does anyone have any tips on how to get it working again?
ricomana said:
Hello,
I've got a problem with my gt-i9505.
I've managed to root the phone and install TWRP.
So i decided to install CM10.2 (21-08) and the right gapps for it.
Everything worked very good and I couldn't be happier.
All my apps were back and it was ready to use it!
I turned off the phone and went to sleep.
The next day i turned it on and it got stuck on the bootscreen (not the CM bootscreen, but the SAMSUNG GALAXY S4 bootscreen).
So I tried to do factory reset and install rom again, gapps again, afterwards again wipe dalvik and cache.
But i keep having the same problem. Right now after flashing the rom it doesn't even boot up the first time.
I also tried going back to 10.1, but same problem.
I don't know what to do, i just got my s4. Really hope i can fix it.
Luckily i can enter the recovery. But i didn't do a backup or anything.
Does anyone have any tips on how to get it working again?
Click to expand...
Click to collapse
Hi,
Look HERE
Put everything back to stock then, try again.
I found some 10.2 ROMS do not like rebooting,and just hang.
Remove the battery and try again normally worked.
malybru said:
Hi,
Look HERE
Put everything back to stock then, try again.
I found some 10.2 ROMS do not like rebooting,and just hang.
Remove the battery and try again normally worked.
Click to expand...
Click to collapse
Thanks for replying
I followed the instructions and succesfully installed the official stock rom for my device and region.
But it's still stuck at the samsung boot screen.
And now i can't boot into TWRP anymore either, is that correct?
After that I flashed with the .pit file. But still stuck on bootscreen.
Is there any other way to solve this problem?
idgaf about custom roms or CM10.2 anymore, i just want my phone to work.
Wether it's with custom or with stock firmware.
Really hope I didn't break my phone. :crying:
EDIT:
I wiped cache after flashing, but no data wipe/factory reset. That did the trick.
God i can't be happier my phone finally works again. Now i'm scared to flash a custom rom again. I think i need to install TWRP or CWM again too I'll just wait for now.
So I have a LG G2 D802 that I rooted, then installed CWM and Mahdi ROM on. I had been having a lot of trouble with SuperSU not installing correctly after I installed the rom (had no issues with SU or CWM prior to installing custom firmware) so I decided to try a factory reset to see if that would help. Because I couldn't figure out how to get into recovery mode without going through ROM Manager, which didn't work any more since SuperSU wasn't working correctly, I tried doing a factory reset through the settings menu. After waiting about half an our to complete, I figured an error had a occurred and forced the handset to restart (in hindsight probably a terrible idea, but I couldn't think of anything else to do).
Now when I boot the phone, it gets past the LG logo to the boot animation and stays there. I worked out how I should be able to get to recovery but that only gives me the ability to factory reset the LG way (and pressing any other button besides power causes the menu to freeze) and when I try to factory reset again it just sits there, not progressing like it did before.
Now I have absolutely no idea what I can do, since recovery mode is inaccessible I have no idea what I could possibly do to fix it. Any help or advice at all would be GREATLY appreciated.
U should flash stock rom via pc, follow this thread http://forum.xda-developers.com/showthread.php?t=2432476
Sent from my LG-D802 using XDA Premium 4 mobile app
Deleted
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
not_su said:
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
Click to expand...
Click to collapse
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Rhymey said:
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Thanks - that's exactly what I've been trying to do. I haven't tried reflashing back to stock with Odin though. Hmmm...
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Click to expand...
Click to collapse
Bell, up here in the Great White North. I don't think locked bootloader is an issue - I was on the previous version of Danvdh's ROM, and everything was hunkydory. I just made the unfortunate decision to encrypt. Big mistake.
May try flashing back to stock. Nothing to lose, at this stage...
Thanks!
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
not_su said:
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
Click to expand...
Click to collapse
Good to hear. Should be able to flash to the rom once again no problem now that it's unencrypted!
Hello all,
I installed this ROM on my phone: http://forum.xda-developers.com/galaxy-s3-neo/orig-development/rom-cyanogenmod-12-1-s3-neo-t3099384
Notably I used the 20151111 version. Everything worked fine. I did however decide to try to encrypt the phone. Everything looked ok, but now the phone is stuck at booting. Notably, at the "Starting apps" stage of the boot process. Unfortunately this is too early to get a logcat. I already tried wiping the cache partition, doing a factory reset and reinstalling the image.
Any ideas on how to unbrick the phone?
x2b said:
Hello all,
I installed this ROM on my phone: http://forum.xda-developers.com/galaxy-s3-neo/orig-development/rom-cyanogenmod-12-1-s3-neo-t3099384
Notably I used the 20151111 version. Everything worked fine. I did however decide to try to encrypt the phone. Everything looked ok, but now the phone is stuck at booting. Notably, at the "Starting apps" stage of the boot process. Unfortunately this is too early to get a logcat. I already tried wiping the cache partition, doing a factory reset and reinstalling the image.
Any ideas on how to unbrick the phone?
Click to expand...
Click to collapse
Reinstall stock rom via Odin btw encryption screws up the phone in every aspect I recommend not doing so
Yeah. I was trying to unlock my bootloader using Controllerboy's guide, and I managed to install TWRP. I also managed to unlock my bootloader. When I tried to restore my phone using the backup I put on my computer and back to my A7, it won't boot - it's stuck on the "ZTE powered by android" boot screen.
I think that the problem is that when I was copying the backup from my phone to my computer it said "unspecified error" but still let me copy the files (the files and the sizes remained the same) so I just ignored it. Whoops!
So I tried to install CM13 in hope that it will somehow fix things, and unsurprisingly everything is still the same.
So. What do I do? I think that the problem was that I backed-up system and tried to restore system (probably).
Anyone got a solution? Or even a system restore that will cure my phone?
Any help will be greatly appreciated! Thanks in advance!
I managed to solve the problem myself by re-wiping dalvik and installing CM 13! Odd that it worked this time and not the other time I tried it, but at least it works