Hello,
I have an optimus v phone that I rooted using fastbootroot. That worked great, while I had it. A couple of days ago I decided to sell the phone and tried to get back to stock. I do not remember correctly, but I had a nandroid of the original rom, that I tried to restore. For some reason it did not work. I then Tried using fastbootroom using option number 3, to restore factory room, and now I am stock in the Android System Recovery, build: RA-THUNDERC-1.1.0-GNM.
I tried installing the factory room (zip) that I downloaded from here, xda, and it installs fine, however, when it boots, it goes back to Android System Recovery build: RA-THUNDERC-1.1.0-GNM. I also tried The nandroid option but it does not work with the backups that I have.
I have tried other things during the past two days, but the last one was the KDZ FW Update, as noted here: http://forum.xda-developers.com/showthread.php?t=875881
I found the Firmware from LG for the Optimus V, but it is in a .cab instead of .kdz format, so that has not worked either. Also, I could not get the KDZ FW Update to recognize the phone, so even if I had a .kdz not sure if I could Flash.
I someone could direct me to a from to restore to factory of at least to boot again into a room, I would appreciate it.
Thanks!
FYI- I have also tried abd shell thing and it has not worked for me either.
Fixed
It took me a while to find a working fix, but this phone is finally working. With a thread over at android central, member Whyzor recommended using Xionia CWMA to flash a rom. I did that, and was able to reboot into a rom that I had saved on the SD Card. On Xionia I could not use the nandroids that I had created with Clockwork Recovery.
I then flashed Clockwork Recovery and rebooted to flash the Stock nandroid that I had. That worked perfectly, however, the phone would again be on a loophole with Clockwork Recovery (wonder why?). I just flashed Xionia once more, and the phone is back to stock Rom but with Xionia Recovery and Rooted.
The Xionia recovery can be found here: http://www.mediafire.com/?fbaoutnaw717pnb
And the original thread: http://androidforums.com/optimus-v-...android-system-recovery-after-data-reset.html
Hope this helps someone in the future!
Related
I rooted my samsung fascinate and falshed a CM7 stable, i loved it except for the fact that my GPS wasn't working. So after some reading and research, i learned that i would have to CWM recovery, flash back to stock, get a gps lock, and then restore back to CM7 and i would have a lock.
Few things went wrong, in my original rooting, i somehow managed to wipe data/cache, thus wiping the stock rom from the phone before i could make a recovery of the rooted stock rom. So when i went back to stock with Odin, i had to completely go back to stock (recovery, stock froyo, stock kernel, etc.) Even at completely stock i still couldn't get GPS lock, even though i could get gps lock before initial root, does anyone know why? I thought it was just Cyanogenmod but i flashed MIUI and still couldn't get lock, yet i was able to get a lock with out root.
after not being able to get a lock, i still needed to get back to my recovery that i made of CM7, problem is i'm not sure which version of CWM recovery i used in order to make the recovery, i'm almost certain that it was the recovery that came with the older rom manager version in the CM7 build i used, but i've tried multiple CWM recoveries and none of which is able to read the recovery files correctly and the recovery can't be fully restored. is there anyway to see exactly which version of CWM was used in order to create the dated backup files on my SD card? Or do i just have to keep trying different versions until one works? I've tried the latest CWM from ROM Manager for the fascinate, but unfortunately the latest version is still unable to read the recovery files
any help is appreciated. cheers.
...You dont have to root to flash a custom rom. That being said there is a guide in the general section that explains how to do things properly.
I installed TWRP on my phone, and went into Bootloader an hit RECOVERY so I can get to the program (the first time I did this it brought me to the TMRWP program). THIS time, it completely wiped my friggin' phone... after I sat there like 4 hours re-setting up everything PERFECTLY how I wanted it.
What's weird is it kept ALL my apps that I converted to SYSTEM APPS, but all my user stuff is gone.
Lesson learned... Don't click recovery from Bootloader.
That has yet to happen to me with any recovery and 3 devices currently with twrp. Might be a step missed with the install or maybe you left a bootloader update zip and ran it when you rebooted? Or it can be a bug as going to recovery from bootloader via a cold start is how to get there traditionally. I would email teamwin and try to sort it out or redo the recovery install, making sure to check the md5 of the file after you download it.
Sent from my Transformer TF101 using Tapatalk 2
Your supposed to click recovery at bootloader. Thats where you do backup, restore and flash new roms.
HTC Sensation z710e
ICS 4.0.3
Sense version 4.0
Software Sense-o-maniac v1.3
Kernel. 3.0.30 Bricked
Radio 11.68.3504
That's what I thought too. If I'm not mistaking, I flashed the new firmware after I did the TWRP, so maybe that screwed it up somehow. I take it TWRP must be the LAST image you flash? Only flashes I remember doing were:
Customize bootloader screen
TWRP.
firmware update
Do I need to re-flash the new firmware before re-flashing TWRP, or is the firmware going to remain no matter what I do from this point on?
Just adb flash recovery. Put the recovery image in your platform tools folder. Adb reboot bootloader. when you are rebooted adb flash recovery recovery.img.
Or use one of the many tools made to do that on our forums
Sent from my ADR6425LVW using xda premium
Well I went ahead and used the GOO Manager to flash TWRP again, and this time it worked fine. I'm going to re-setup my phone again then before I customize it back like I had it, going to try to get to recovery and see if it works.
With it now being installed, does that mean I can't flash anything directly from SD Card or modify the bootloader anymore without it causing problems?
What I mean, moreso, is... if I ever put factory reset. will it reload the factory rom + keep the newest firmware I installed (etc.) or do I nee to back up the phone with TWRP and recover from that when I want to load it back?
Factory reset just puts things back to the way they were without the stuff in the data partition or any user apps or settings. This means that say you flash a custom rom, it will reset to as if that custom rom was freshly installed since the custom rom has replaced the factory rom in the /system/ parition and anything else related to it.
With that said it is usually a good practice after rooting a fresh device to do the nandroid and then transfer it to a computer before you do anything else. Note that while you probably won't be switching recoveries a lot, that nandroid backups generally work only with the recovery that generated them so don't get them mixed up.
While I did find a similar posts, they were for different devices. I also tryed to search o different sites for similar problems to no avial.
What Happened: After backing up system data and app data then removing Foxhound ROM with factory reset, and installing UltimaROM i came to find that the modem did not install correctly result in no connection to my cell network. I booted into TWRP recovery to try and do a re-install of the ROM only to find that TWRP was restarting itself every 3 seconds or so. I attempted to restart the device which i found to result in a TWRP bootloop that i cannot get out of, it constantly is booting into recovery mode and i cannot get it restart the OS.
What I've tried: Since i can get into download mode i decided to attempt to re-install TWRP using Samsung Galaxy S3 Toolkit but since i do not have USB debugging on i cannot do that. I'm mainly looking for a fix before i go and claim it on the warranty saying update went bad or something. If people need more information I will try to provide it as best i can.
Summery if i confused people is that TWRP is in a bootloop, i am unable to get to the OS, but i still have download mode available.
I fixed it but not how I would have liked to. I ended up losing all data due to flashing stock ROM using ODIN. I would still much appreciate a alternative method that does not involve loss of data though just for future reference, that is if anyone knows a alternative method.
Sent from my GT-I9300 using xda app-developers app
could've tried reflashing TWRP or any other recovery through odin
I have an LG Optimus Q (LGL55c) with twrp loop. I was trying to go back to stock rom, instead I deleted all the system files in twrp when it was working...Then I rebooted back into recovery and get the loop. Does this mean I completely bricked my phone? I tried using adb, adb shell doesn't work. It does find the device. Even tried the LG update with no sucess Any ideas or suggestions?
I just read the forum title, I thought this was for the Optimus Q not the Samsung S3. Sorry mods
Temasek unofficial cm12 5.02
I was running this rom when my power button shorted and I got it replaced but then I tried to do a complete wipe and clean flash but since then it has been twrp bootlooping, tried to flash the latest recovery through Odin but still doesn't work also tried stock firmware flash but says binary not available.
This is my secondary device and I've not been in touch with Odin for a while. Any help will be appreciated.
Thanks
Download latest firnware from sammobile.com and flash it with Odin, as described on sammobile: does Odin finish with '1 succeeded'?
I'm in a very similar situation, but with my Samsung Galaxy Note 2 (N7105). It's rooted, and I am, or was using TWRP 2.7.0.2. ROM is CyanogenMod 12, 5.0.2 Lollipop.
I did a factory reset from INSIDE Android, and chose to wipe internal memory. Phone did the reset and wipe, rebooted into TWRP instead of Android, and now I have TWRP boot loop.
I posted more about it here: http://forum.xda-developers.com/showpost.php?p=60247503&postcount=3671
I have the Problem toooo!
What must i do Now!
with my S3 is the same!!!
For posterity:
With an old (2014?) version of TWRP and a custom ROM, I tried reverting to factory settings. That caused the phone to reboot TWRP, and the screen would flash every couple of seconds. I flashed a stock recovery image I found on Google, and when it restarted again, the wipe was completed successfully. My intention was to wipe all user data anyways so I can't say if this method might save it.
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.
Folks,
Phone - AT&T E970 Jellybean
I rooted and BL-Unlocked my phone and installed CWMOD recovery. I backed up my stock AT&T Rom using CWMOD. I played around with a few ROMS but I found that Stock was the most stable so I restored my backup using CWMOD so everything works like normal now. However, I still do have CWMOD recovery iinstalled. Is there a way to flash just the stock recovery back?
I did search for the LGNPST guide but that seems to over-write everything. Is there a lower risk way to restore the stock recovery using a TOT file or something like that?
Any help would be appreciated..