So I screwed up pretty bad....
I have done so many flash's / reboots over the years that I just went through it too quick and wiped EVERYTHING off the device. I am trying to install the factory rom in TWRP now but it is not working...when it trys to install it is saying no MD5 found..it completes the install and then when it asks for a reboot it is saying no OS found!
I don't know what to do...any advice or a thread anyone knows of that can help me get my phone back to a working order???? I have never made such a stupid mistake before.
Or is there a recovery somewhere I can get that will restore the phone to a usable manner so I can at least flash a fresh rom?
Never mind all! I stumbled on someone else's thread and after their experience I ended up rebooting anyway and it actually booted totally normal...Lesson learned about taking my time and double checking I still have a recovery!
Related
Well, please dont laugh...
As the title says I think I killed my GSM hero.... I need your help!
here is what happened
I'm new at this and I got a Hero with android 1.5 so I wanted to upgrade to a newer version
I followed instructions on this thread
http://forum.xda-developers.com/showthread.php?t=645253
I successfully rooted the phone then I tried to flash this ROM
http://forum.xda-developers.com/showthread.php?t=932377
After reboot the old rom was still there but wiped so I did everything from scratch a couple of times and didn't work.
I did notice the last time that there was an error that I'm sure I didn't see the first few times while wiping SD:ext so I looked for that on the forum and fund the following thread
http://forum.xda-developers.com/showthread.php?t=679991
I followed pseudoremora's instruccions and then tried to flash again, but got stuck on the boot screen...
Now somehow I lost my nandroid backup... I'm not sure what happened but is not with the rest of the things I backed up...
so here is the current status:
Can't boot
Can't flash the ROM
Can't restore the backup.
Is there anything else I can do to fix this? I found another thread that talks about using someone else's nandroid backup (but removing the pieces that contain personal data such as usernames and passwords) if that is possible, would anyone be willing to help?
Thanks!
Here is the last thread I mention
http://forum.xda-developers.com/showthread.php?t=545435
Can you boot into the recovery console by pressing power+home?
if recovery is not working for you , try going into fastboot i hope you knows how to use ADB over fastboot . Goood Luck
It's fixed!
Hi Guys,
IT's fixed!! I'm not exactly sure how I did it... I flashed the ROM several times until it worked...
Do you think it's a problem with the hardware itself? maybe the SDcard?
Anyway I'm reliefed! not i's working!
Cheers!
Hello,
If anyone could help me get my phone back into a functioning state, I would very much appreciate it! I have been playing around with the Cyanogenmod 10 nightlys. All was going well until I decided to try encryption. It encrypted the phone okay, but I decided to format the phone and get it back to an unencrypted state, except it wouldn't allow me to factory reset. The button to start the reset did nothing except reboot the phone a few minutes after pressing it.
No problem, I thought, I made a nandroid backup before I started playing with ROMs, I'll just restore that, except that didn't work because CWM couldn't mount the encrypted volumes. So, I copied the CWM backups to an SD card using root explorer, and tried to restore from there. It gave me an error advising it couldn't mount/format /system. So, I rebooted, only to get stuck on the Samsung boot logo.
I can still get into download mode though. so I tried flashing the stock firmware with Odin. Odin reported the software flashed succesfully, and the phone boots now with the stock animation so presumably it did work, but it still asks for the encryption key. I put in the key I used originally but it rejects it.
I don't know what else to do to restore my phone to a stock state.
This is my first Android phone and I was just playing around out of curiosity, so pleas excuse any noob errors I may have made along the way. I shall be sure to learn from them.
Please tell me I can get my phone back to the original state!
s0mmie said:
*snip*
Click to expand...
Click to collapse
It seems I have managed to get back to a working state by using the Android recovery menu. Phew. I shall not be messing with encryption again. All part of the learning curve though, I suppose!
I recently rooted my phone and everything was fine. This morning I installed a debloated rom http://forum.xda-developers.com/showthread.php?t=2296109 and It seemed to work but after I rebooted the phone just sits at a screen that says
Samsung
an unlocked icon
Custom
I can still get into Odin and TWRP but nothing I do seems to solve my problem. I have verified the MD5 of the image as well as trying to install a backup I made prior to flashing but the restore fails.
Does anyone know what I can do?
I should add that TWRP asks for a password when I load it but I never explicitly set one and also it seems to have trouble with the partition table.
Update: Solved maybe? I got this phone to boot but I am not sure what happened. I flashed a rom from TWRP several times and finally one took ... still would like info from someone who actually knows what is going on as I am not sure this wont happen again
Update: So it seems that every time I something happens and the drive or loader gets encrypted and it no longer boots. the "solution" is to do a full wipe then install a rom. This happens every time i reboot and I would really like a solution to this.
Hello, all. First, I'd like to say thank you for taking the time to read this and potentially try and help me out. Any assistance with this matter would be greatly appreciated!
I added the (Non-standard) to the title, as I've been flashing and modding this phone for over two years, and I've never experienced this issue. I'm not the type to ask for assistance, as my research skills are well above par, but after digging through literally countless forums and topics, I have yet to find anything quite like my situation...
ISSUE: Performed recent flash attempt to epinter's CM10.1. Now loads to Moto splash, sits there the usual few seconds, but when it comes time to load the rom, it reboots and starts the process again... (I swear I think I see it trying to load the rom splash for like a micro second, but then it could just be the delirium of long hours researching and fighting this problem.) Now, you might be thinking, "Eh, pretty common...", right? Yeah, me too, until I couldn't fix it like I've done a million times before... I can boot into recovery. I have performed ALL standard actions regarding flashing a new rom, yet the problem persists. The problem persists now no matter what rom I attempt to flash. Now you might be thinking, "Just flash your nandroid recovery...", but I wish, oh how I wish I could... I am currently using CWM-based Recovery 5.0.2.7, although I've tried more than a few different recoveries since this issue, all provide the same results... Which is nothing. I'm at the end of my rope here.
I've even tried flashing TWRP (two different versions) so I could at least get some charge to the battery so I could continue this debacle, but it hangs at the TeamWin splash screen...
Fastboot loads fine. Wipes performed to system, caches, partitions, etc, to no avail... Battery pull, already tried...
I've covered all the basic fixes, but my issue seems to be bigger than my knowledge base (at the moment).
Okay, here's the exact details of what led up to this...
My Atrix WAS unlocked, rooted, and using RR's CWM for recovery at the time. I had flashed everything coming and going as the scene grew, but eventually went back to CM7.2 and had been running it for ages. Well, I decided to try something new, and settled on trying BeanStalk. Flashed Aroma Prep, no problem. Flashed ROM and Gapps, no problem. Booted up fine. Decent start on the rom, but a little too buggy yet for me. So on this note I wiped and restored my CM7 nandroid backup, no problem. All was well, until I came across epinter's CM10.1 and thought, "Eh, why not?" (...and now look at the mess I'm in!) Performed a new nandroid backup of my CM7, and began the process that ended me... Everything went along just fine. Performed all my wipes, flashed my zips, rebooted, and BAM... boot loop! Little did I know what kind of headache I was in for, until I couldn't restore my backup. Now, I'm just praying I find a solution before my battery drains out completely...
SIDE NOTE: While attempting to restore fails and just resets recovery back to the main screen, there are no visible errors reported. Attempting to flash ANY of my other roms results in the same behavior. Flashes "appear" to go smoothly, but the end result is the same... I did notice upon attempting to flash BeanStalk again that there is an error reported in the aroma installer. It performs all wipes correctly, but when it comes time to actually install, it reports a broken symlink error, or something to that effect... (I would reproduce the install error message, but at the moment I'm trying to hang onto as much battery life as possible. My apologies for the inaccuracy of any statement.)
PLEASE, LADIES AND GENTLEMEN, I BEG OF YOU... If anybody has been unfortunate enough to have found themselves in my shoes, then hopefully you were lucky enough to get it figured out by now and would be willing to pass along the info. Although not my primary phone anymore, it still gets more than it's share of use. I'd hate to see it go out this way...
Any help to guide me in the right direction would be most appreciated! Thank you all in advance!
Hello,
I tried flashing a custom ROM on my samsung galaxy S7 (by the way I've already done this successfully, although I clearly don't know as much as I should).
Firstly I was getting the Error 7 and "your device is ." I did fix that by deleting lines in the updater-script of the ROM. It seems that this has worked, but I couldn't get out of twrp to test it. At first I thought it was an error with my ROM, so I just tried loading the backup I'd made before, but I still couldn't get out of twrp. And there I am, I can't go in download mode, or even power off, it just puts me back in twrp.
I tried updating twrp from a .img but it just didn't work and I'm still in 3.3.1-0. Very strange.
I don't know much of the science behind this, please explain me, I don't want to brick my phone...
Thanks to anyone who tries to help.
Nevermind ?, I just did an adb reboot, got out of recovery, and my backup was applied so... I guess I won't install that custom ROM. I don't know why I had this problem, but I solved it anyway.