Hey, I have the recovery mode that I installed from here currently on my phone, but I would like to revert it to the stock recovery mode, because I'll be needing to take my phone to Verizon tomorrow. How can I go about doing that?
Chiggins said:
Hey, I have the recovery mode that I installed from here currently on my phone, but I would like to revert it to the stock recovery mode, because I'll be needing to take my phone to Verizon tomorrow. How can I go about doing that?
Click to expand...
Click to collapse
just flash theOTA (leak v3) it sets the recoveryand everything else back to stock
I downloaded the OTA for 2.1 and tried to install that, but when I did from the recovery mode I have, I got an error saying E:No signature (690 files)
Chiggins said:
I downloaded the OTA for 2.1 and tried to install that, but when I did from the recovery mode I have, I got an error saying E:No signature (690 files)
Click to expand...
Click to collapse
make sure the file is in the root of your sdcard
and instead of pressing up volume press down when powering your phone on
it will take you to the bootloader (h-boot)
use trackball as action button to finish installation =)
Yep, I've done that. Gone through h-boot into the recovery mode, and whenever I tried to install the OTA file that I renamed to update.zip, I get the E:No signature (690 files) error
Chiggins said:
Yep, I've done that. Gone through h-boot into the recovery mode, and whenever I tried to install the OTA file that I renamed to update.zip, I get the E:No signature (690 files) error
Click to expand...
Click to collapse
you have to name it as PB00IMG.zip
otherwise it will look right past it in h-boot
and give you the option to go into the recovery
I got the same error after renaming the file.
Chiggins said:
I got the same error after renaming the file.
Click to expand...
Click to collapse
your pressing volume down + power correct
not power up. power up not your friend in this case we want the bootloader not the recovery.
Well ****, now its doing something in HBOOT. There is a loading bar on the top right doing something.
Chiggins said:
Well ****, now its doing something in HBOOT. There is a loading bar on the top right doing something.
Click to expand...
Click to collapse
awesome now your cookin!
enjoy the OTA again haha
glad we could get you moving along.
and remember the action button is the trackball =)
Well, now when I booted back up, I was back in KaosFroyo.
And the recovery mode was the same.
Chiggins said:
Well, now when I booted back up, I was back in KaosFroyo.
And the recovery mode was the same.
Click to expand...
Click to collapse
did it say installation complete?
you let it run its course not pulling the battery correct? it took my phone about 5-7 minutes to complete
if so mabey the file was the wronge one.
http://www.mediafire.com/?qymwuzug5gl
I didn't see any text saying installation complete, and I didn't touch the battery. This file is a lot bigger than the one that I had. I'll download and give it a try.
Should I do a wipe to factory before I do this?
Chiggins said:
I didn't see any text saying installation complete, and I didn't touch the battery. This file is a lot bigger than the one that I had. I'll download and give it a try.
Should I do a wipe to factory before I do this?
Click to expand...
Click to collapse
no it will wipe everything but your sdcard
All of this will reset my phone to factory settings, right? So when I bring it to Verizon, I'll be under warranty?
Chiggins said:
All of this will reset my phone to factory settings, right? So when I bring it to Verizon, I'll be under warranty?
Click to expand...
Click to collapse
factory yes warranty ehhh thats arguable but with the firmware and rom stock they won't be able to tell at all so your fine to even seal the deal further after you reboot your phone it will promt you to install the new ota update just follow the on screen instructions for that and it will be fully updated and vzw approved
Is there anything else that I should do to ensure that they don't find that I've rooted?
Chiggins said:
Is there anything else that I should do to ensure that they don't find that I've rooted?
Click to expand...
Click to collapse
mabey clear your sdcard of nandroid and any other roms or patches just in case and any other root only folders like titanium or setcpu etc. etc.
The only thing I did was use nandroid, I already deleted my roms. Where is the setcpu folder?
Related
I rooted today, and I want to install damages rom. I've downloaded it, and I need some guidance. I have no idea where to go from here and don't see directions in the thread.
Anyone? eek! nervous
power off the phone
hold home and press the power button
let go of home when it vibrates
go to wipe..
wipe everything
go back to flash. flash the zip file.
reboot.
reboot takes forever.
what about a backup, should I run the nandroid backup and do a backup or a backup + ext I think it said or similar?
I want to make sure I can revert back to my 1.5 rom.
Do I also need to take all the damangecontrols zip file contents and put em on my sd card?
Kcarpenter said:
power off the phone
hold home and press the power button
let go of home when it vibrates
go to wipe..
wipe everything
go back to flash. flash the zip file.
reboot.
reboot takes forever.
Click to expand...
Click to collapse
Good quick guide. They should all be so simple. Although I don't go the home/power way (unless adb isn't connecting). I use adb shell reboot recovery. Just my 2cents.
chugger93 said:
what about a backup, should I run the nandroid backup and do a backup or a backup + ext I think it said or similar?
I want to make sure I can revert back to my 1.5 rom.
Do I also need to take all the damangecontrols zip file contents and put em on my sd card?
Click to expand...
Click to collapse
Yes, you need to nandroid. You only use nandroid+ext if you're using a2sd/apps2sd.
No, just put the zipfile on the SD card.
When you get into recovery (either the home+power on, or the adb shell reboot recovery method) AFTER doing your nandroid backup, then select 'flash zip from sd card' and select the ROM zipfile you put on the SD card.
KCarpenter's not kidding about the reboot. I've seen the first boot after installing DC's 2.0.8.1 take 15-30 minutes. So after flashing it, reboot and go take a shower or something.
smw6180 said:
Yes, you need to nandroid. You only use nandroid+ext if you're using a2sd/apps2sd.
No, just put the zipfile on the SD card.
When you get into recovery (either the home+power on, or the adb shell reboot recovery method) AFTER doing your nandroid backup, then select 'flash zip from sd card' and select the ROM zipfile you put on the SD card.
KCarpenter's not kidding about the reboot. I've seen the first boot after installing DC's 2.0.8.1 take 15-30 minutes. So after flashing it, reboot and go take a shower or something.
Click to expand...
Click to collapse
Nandroids are for pansy's.
Kcarpenter said:
Nandroids are for pansy's.
Click to expand...
Click to collapse
And for people like me who hate to have to start over from scratch every time he blows up a ROM install.
Ignore post -- looks like this has already been answered.
sweet...thanks guys. Wish me luck, gonna try this!
Oh one more question, are text messages migratable? Can I save those somehow before I upgrade?
chugger93 said:
sweet...thanks guys. Wish me luck, gonna try this!
Oh one more question, are text messages migratable? Can I save those somehow before I upgrade?
Click to expand...
Click to collapse
Going from 2.x to 2.x yes. I never had any luck migrating those from 1.5 to 2.1. All I ever accomplished was a lot of Force Closes and problems, so I just said screw it and stopped trying.
chugger93 said:
sweet...thanks guys. Wish me luck, gonna try this!
Oh one more question, are text messages migratable? Can I save those somehow before I upgrade?
Click to expand...
Click to collapse
Just blow em away...there are a couple options but none "good".
ok DM rom is installed!
I can't set it up tho and sign into google! says I dont have a network connection! Crap!
This could be a temporary problem or your phone may not be provisioned for data services
Thats what it says...
chugger93 said:
ok DM rom is installed!
I can't set it up tho and sign into google! says I dont have a network connection! Crap!
This could be a temporary problem or your phone may not be provisioned for data services
Thats what it says...
Click to expand...
Click to collapse
yeah prob temp but sometimes to get data working u have to turn wifi on for a min then the data starts to work. weird but it does. good luck
Ok so this morning my alarm wakes me up and I noticed I had to unlock my phone to make it snooze, something didnt seem right as my alarm app usually comes up to the front and I can snooze without unlocking my screen. So what do I decide to do half asleep? I decide to reinstall the rom. Here are my steps, and I suggest you dont follow them.
1. Format system
2. Format data
3. Format cache
4. Mount system
5. Reboot phone (Swear this was an accident, as I was trying to navigate to the "install zip from sd card" option)
So my question is ,whats the quickest way to unbrick my phone. It just stays on the "M" boot logo. I found a couple of threads on different sites but want to make sure I"m using the latest method and for the Droid X. Thanks in advance
SysAdmNj said:
Ok so this morning my alarm wakes me up and I noticed I had to unlock my phone to make it snooze, something didnt seem right as my alarm app usually comes up to the front and I can snooze without unlocking my screen. So what do I decide to do half asleep? I decide to reinstall the rom. Here are my steps, and I suggest you dont follow them.
1. Format system
2. Format data
3. Format cache
4. Mount system
5. Reboot phone (Swear this was an accident, as I was trying to navigate to the "install zip from sd card" option)
So my question is ,whats the quickest way to unbrick my phone. It just stays on the "M" boot logo. I found a couple of threads on different sites but want to make sure I"m using the latest method and for the Droid X. Thanks in advance
Click to expand...
Click to collapse
Looks like an SBF is in your very near future.
Go to the Development subforum and search there.
If you have not applied the OTA 2.2 update, you will need the instructions to SBF back to 2.1 and then apply the 2.2 leak, and load your ROM from there.
If you have already done OTA 2.2, there is also an SBF that will restore /system only. It Might save you.
BE ABSOLUTELY SURE YOU DO NOT FLASH the 2.1SBF if you were on OTA 2.2. If you do, it will be game over.
Let us know how you fair.
One of the first things I did was the 2.2 ota when I got my phone.
Thanks, I will search there and report back.
SysAdmNj said:
One of the first things I did was the 2.2 ota when I got my phone.
Thanks, I will search there and report back.
Click to expand...
Click to collapse
Can you not get back into Clockwork if you pull your battery?? And they do have a 2.2 sbf that restores your system files.
MrDanger said:
Can you not get back into Clockwork if you pull your battery?? And they do have a 2.2 sbf that restores your system files.
Click to expand...
Click to collapse
if you hose /system you won't be able to get back into recovery. Recovery depends on the logwrapper in /system/bin. If it's gone, no recovery boot.
I'm guessing Format System pretty much took care of that
MrDanger said:
Can you not get back into Clockwork if you pull your battery?? And they do have a 2.2 sbf that restores your system files.
Click to expand...
Click to collapse
Zaphod-Beeblebrox said:
if you hose /system you won't be able to get back into recovery. Recovery depends on the logwrapper in /system/bin. If it's gone, no recovery boot.
I'm guessing Format System pretty much took care of that
Click to expand...
Click to collapse
Correct, I cannot get back into clockwork recovery.
I can get into android recovery but I cant do much from there.
Guys, is the ota 2.2 sbf I need SHADO_X6_2.3.13_SYSTEM-ONLY.zip
found here?
http://rootzwiki.com/index.php/Main-Page/Team-Black-Hat-does-it-again.html
SysAdmNj said:
Guys, is the ota 2.2 sbf I need SHADO_X6_2.3.13_SYSTEM-ONLY.zip
found here?
http://rootzwiki.com/index.php/Main-Page/Team-Black-Hat-does-it-again.html
Click to expand...
Click to collapse
Yes. I think that is your only hope at this point. If it doesn't work, I think you are SOL.
I did something very similar to this, flashing the 2.2 System SBF fixed it
I'm back up and running. Thanks people.
good for you man. seriously. just read a couple threads like this. makes me real nervous about flashing roms.
Not nervous since I have insurance
Seriously I caused my issue with a silly mistake. Usually its smooth sailing.
Ok my battery was draining at a faster rate than normal so i figured I'd reboot my phone. Once I shut down my phone and hit the power button it boot into fastboot mode. I am literally the most basic Nexus 4 user meaning, I've never rooted, unlocked, flashed or done anything to my phone. I simply just don't know how to do any of this stuff so it's not like I was tinkering with anything.
I searched online and I went into recovery mode and tried to reset the phone and wipe the partition and it just reboots to the fastboot mode. I honestly have no clue what went wrong. Again, I know nothing about root and stuff but there must be a solution right or am I the first person to ever brick their completely stock phone by trying to restart it? I figure some of the awesome people on here what know what to do or to simplify some steps to fixing this. Thanks in advance.
Sounds like your volume down key might be stuck (as holding that when you power on is how you get to fastboot).
If it's not that then maybe you should try downloading the factory image from here: https://developers.google.com/android/nexus/images and letting that install.
I don't think the button is stuck.
Your device needs to be in fastboot mode, with the bootloader unlocked. The relevant key combinations and commands are documented on the page about building for devices.
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
After restoring a factory image, it is recommended that you lock the bootloader, for security reasons.
Click to expand...
Click to collapse
Rusty! said:
Sounds like your volume down key might be stuck (as holding that when you power on is how you get to fastboot).
If it's not that then maybe you should try downloading the factory image from here: https://developers.google.com/android/nexus/images and letting that install.
Click to expand...
Click to collapse
Definitely not the volume down key. I'm able to navigate with volume rocker in fastboot.
Alex_Dreyk said:
I don't think the button is stuck.
Click to expand...
Click to collapse
are u able to get to the bootloader and recovery
One3OneKing said:
Definitely not the volume down key. I'm able to navigate with volume rocker in fastboot.
Click to expand...
Click to collapse
I picked an instrucktion form the link below.
As you have already wiped it do as in instruction
faddyie said:
are u able to get to the bootloader and recovery
Click to expand...
Click to collapse
yes, I can get to recovery. can i get to the bootloader?how would i get there, no clue. lol
Bootloader = fastboot
Try the factory image flash.
Rusty! said:
Bootloader = fastboot
Try the factory image flash.
Click to expand...
Click to collapse
I kind of have an idea of how to do that but a link to a set of instructions would be great. I've looked but most people have rooted and installed computer programs so I didnt know what exactly I would need to do in my completely stock scenario.
One3OneKing said:
I kind of have an idea of how to do that but a link to a set of instructions would be great. I've looked but most people have rooted and installed computer programs so I didnt know what exactly I would need to do in my completely stock scenario.
Click to expand...
Click to collapse
Dear if you have not rooted it. your stock rom has not gone any where...
Goto recovery and then press volume up key and power button. keep holding for like 10 secs and u will be get into the system. However, check that your volume down key is not pressed
faddyie said:
Dear if you have not rooted it. your stock rom has not gone any where...
Goto recovery and then press volume up key and power button. keep holding for like 10 secs and u will be get into the system. However, check that your volume down key is not pressed
Click to expand...
Click to collapse
No luck. This is crazy, I literally don't know what happened...:crying:
Have u downloaded the sender image file as described in previous posts
Sent from my Nexus 4
One3OneKing said:
Ok my battery was draining at a faster rate than normal so i figured I'd reboot my phone. Once I shut down my phone and hit the power button it boot into fastboot mode. I am literally the most basic Nexus 4 user meaning, I've never rooted, unlocked, flashed or done anything to my phone. I simply just don't know how to do any of this stuff so it's not like I was tinkering with anything.
I searched online and I went into recovery mode and tried to reset the phone and wipe the partition and it just reboots to the fastboot mode. I honestly have no clue what went wrong. Again, I know nothing about root and stuff but there must be a solution right or am I the first person to ever brick their completely stock phone by trying to restart it? I figure some of the awesome people on here what know what to do or to simplify some steps to fixing this. Thanks in advance.
Click to expand...
Click to collapse
Being that you haven't unlocked or rooted the phone its most likely a hardware problem. If you bought it from Google RMA
From my BLACKED OUT N4
Before RMA'ing try the factory image. You don't need instructions, you just run a .bat file while in fastboot. What have you git to lose?
if you wiped your partitions, then you dont have a rom on your phone. flashing the factory img via fastboot would fix that.
simms22 said:
if you wiped your partitions, then you dont have a rom on your phone. flashing the factory img via fastboot would fix that.
Click to expand...
Click to collapse
You can't wipe /system from stock recovery, so he didn't do that.
EvoXOhio said:
You can't wipe /system from stock recovery, so he didn't do that.
Click to expand...
Click to collapse
i havent seen the stock recovery in a loooooooooong time, just going by what he wrote in his post :angel:
heres his quote, and thats what happens exactly when you dont have a rom stalled on the device..
I searched online and I went into recovery mode and tried to reset the phone and wipe the partition and it just reboots to the fastboot mode
Click to expand...
Click to collapse
simms22 said:
i havent seen the stock recovery in a loooooooooong time, just going by what he wrote in his post :angel:
heres his quote, and thats what happens exactly when you dont have a rom stalled on the device..
Click to expand...
Click to collapse
I'm guessing he wiped data and/or cache. If he truly is stock like he says then he didn't wipe his /system partition.
My phone got messed up once and I couldn't make or restore nandroids nor boot past the CM boot image, and it ended up being because my /data partition got corrupted. No idea how. I had to flash stock Google images to get it to boot. it happened during normal use of the phone.
EvoXOhio said:
I'm guessing he wiped data and/or cache. If he truly is stock like he says then he didn't wipe his /system partition.
My phone got messed up once and I couldn't make or restore nandroids nor boot past the CM boot image, and it ended up being because my /data partition got corrupted. No idea how. I had to flash stock Google images to get it to boot. it happened during normal use of the phone.
Click to expand...
Click to collapse
yea, if had my data partition get corrupted too, wouldnt finish booting. flashing the stock img fixed it quick. but it was my own fault.. bennchmarking at 1890mhz with fsync turned off
I ended up just taking advantage of my warranty and I'll get a new one. Thanks to everyone for the suggestions and tips. I'm still trying to figure out why simply turning off the phone to restart it caused this to happen. It makes no sense.
Last night Titanium got reset and so I had to refreeze to avoid losing MDL and cut bloatware/etc.
This morning I rebooted to try to get a stubborn app to work. Cue endless boot loop I've been at for over an hour. Somtimes it will flash my home screen with the icons then reboots. I effed up didn't I? When this happened with my iPhone 5 I was able to go in and delete out tweaks with iFile to fix, but from googling this seems a lot more complicated and really, really bad.
I know the #1 rule on here is to read and find the answer to solve the problem yourself, and I've got 7 other tabs open and am doing that, but I'm also in major panic mode. How do I fix this? I'm so pissed at myself for not opening the safe to freeze thread last night.
Worst case is to Odin the stock mdl firmware and start all over.
jd1639 said:
Worst case is to Odin the stock mdl firmware and start all over.
Click to expand...
Click to collapse
will I lose MDL and root? I'm getting the feeling scanning the various tabs that I'm gonna have to go back to square 1 somehow ugh, I want to cry.
Wittyusernametaken said:
will I lose MDL and root? I'm getting the feeling scanning the various tabs that I'm gonna have to go back to square 1 somehow ugh, I want to cry.
Click to expand...
Click to collapse
You won't lose mdl, you will lose root and will have to re-root and re-freeze the files to keep the ota from taking place. Do your homework on those first so you know which ones to freeze because it'll want to update.
Wittyusernametaken said:
Last night Titanium got reset and so I had to refreeze to avoid losing MDL and cut bloatware/etc.
This morning I rebooted to try to get a stubborn app to work. Cue endless boot loop I've been at for over an hour. Somtimes it will flash my home screen with the icons then reboots. I effed up didn't I? When this happened with my iPhone 5 I was able to go in and delete out tweaks with iFile to fix, but from googling this seems a lot more complicated and really, really bad.
I know the #1 rule on here is to read and find the answer to solve the problem yourself, and I've got 7 other tabs open and am doing that, but I'm also in major panic mode. How do I fix this? I'm so pissed at myself for not opening the safe to freeze thread last night.
Click to expand...
Click to collapse
You can factory reset from recovery. That will unfreeze all apps but keep root. Good luck.
jd1639 said:
You won't lose mdl, you will lose root and will have to re-root and re-freeze the files to keep the ota from taking place. Do your homework on those first so you know which ones to freeze because it'll want to update.
Click to expand...
Click to collapse
Well I'm in front of a computer now so there's no way I have any excuse not to check the safe to freeze list at least.
I found this http://downloadandroidfiles.org/download-i337ucuamdl_i337attamdl_att-zip/ I can't log in to my phone to tell specifically what I am, just that I'm ATT, MDL on 4.2.2. Is that the file I use in Odin?
jd1639 said:
You won't lose mdl, you will lose root and will have to re-root and re-freeze the files to keep the ota from taking place. Do your homework on those first so you know which ones to freeze because it'll want to update.
Click to expand...
Click to collapse
muniz_ri said:
You can factory reset from recovery. That will unfreeze all apps but keep root. Good luck.
Click to expand...
Click to collapse
EDITED: Okay, I flashed stock MDL with Odin after I could only get into Download mode, said it succeeded. And now we are back at the endless boot loop. Although it shows my regular home screen... wouldn't I have lost everything? So did it not take?
What do I try now that Odin failed?
Wittyusernametaken said:
I can't boot into recovery. I get the message that it tries to boot into it (volume up, power and home) but then turns off and starts the reboot process all over again.
How do I flash stock MDL with Odin if I can't get into recovery?
Click to expand...
Click to collapse
Make sure that you hold the three button combo long enough in order to get into recovery. there should be small, blue type at the top of the screen at that point release the buttons.
But if you really can't get into recovery hopefully you can get into download mode.....with the phone off press volume down, home, and power buttons. Connect phone to odin then hit volume up. At that point odin should recognize the phone and say "added" on the screen. Select the MDL (the above MDL file looks legit) tar file after pressing PDA in Odin then start.
Wittyusernametaken said:
I can't boot into recovery. I get the message that it tries to boot into it (volume up, power and home) but then turns off and starts the reboot process all over again.
How do I flash stock MDL with Odin if I can't get into recovery?
Click to expand...
Click to collapse
Can you get into Download Mode? opposed to Recovery
Volume Down + Power + Home...
If so you can reflash the stock MDL Odin files which will bring to phone back to factory settings (backup what you can), your need to reroot, and reinstall your custom recovery. Along with that block the update programs...
It flashes my home screen, I can hit the button to get into my apps, and can ALMOST get to Titanium before it reboots on me. Over and over and over.
NighthawkXL said:
Can you get into Download Mode? opposed to Recovery
Volume Down + Power + Home...
If so you can reflash the stock MDL Odin files which will bring to phone back to factory settings (backup what you can), your need to reroot, and reinstall your custom recovery. Along with that block the update programs...
Click to expand...
Click to collapse
I got it into download mode, and reflashed the MDL file. Odin said it was a succes but when it rebooted my apps are all there just like it was originally. Wouldn't it have brought it back to original? It's still stuck in endless boot loop, I can almost get to Titanium but reboots before I can get to it. Looks like ODIN failed but said it succeeded?
If you can get into recovery try a factory reset. That might help.
~wolverine~ said:
If you can get into recovery try a factory reset. That might help.
Click to expand...
Click to collapse
Can't get into recovery, can only get into Download mode.
Will it stay on long enough to get into settings and factory reset from there?
~wolverine~ said:
Will it stay on long enough to get into settings and factory reset from there?
Click to expand...
Click to collapse
I can't get in fast enough. I can get into Accounts > Backup and reset > but as soon as I touch Factory Restore, my 4 seconds are up and it reboots. I've tried to be faster.... not happening.
Wittyusernametaken said:
Can't get into recovery, can only get into Download mode.
Click to expand...
Click to collapse
Well, you could try flashing CWM through Odin, and then try to reboot into recovery. Also, when you're trying to get into recovery mode, make sure your phone is not plugged in to any power source. My phone kept rebooting when I did that.
Mine did pretty much the same after I used odin to go back to stock. The only thing that helped was a factory reset. Sorry I can't help anymore than that.
Wittyusernametaken said:
I can't get in fast enough. I can get into Accounts > Backup and reset > but as soon as I touch Factory Restore, my 4 seconds are up and it reboots. I've tried to be faster.... not happening.
Click to expand...
Click to collapse
A couple of options:
1) Here is the stock MDL recovery. Flash in the PDA slot in Odin then try to get into recovery and do a factory reset: https://mega.co.nz/#!A8UjUSwC!LBFQjs_Bp6bj1AqeawjaI_aEKej7DWV7NoXz4JEZ55M
2) Try re-flashing the MDL tar in Odin again but this time check the "Nand Erase All" box.
MrKhozam said:
Well, you could try flashing CWM through Odin, and then try to reboot into recovery. Also, when you're trying to get into recovery mode, make sure your phone is not plugged in to any power source. My phone kept rebooting when I did that.
Click to expand...
Click to collapse
Finally got into recovery and am wiped. Thank you all for the help. Now to spend the rest of the day rebuilding. Gah.
Hi All! I have an H918TN running the latest WETA (software version J). This morning I awoke to find an OTA update available for install (It must have happened overnight. Don't know why it appeared and don't know the size). I installed it and now I keep booting into recovery even after wipes and re-installs of backups and full installs. Nothing I've tried so far seems to work. Anyone know of a solution or link to one? I have access to ADB/Fastboot (still shows device) and the "J" KDZ file. For the record, I've tried "Restore v20 to 100% Stock (!!even for bricked devices!!" but LGUP (Version 1_14_3) says it doesn't recognize the model. TIA and later.
jt1954 said:
Hi All! Have an H918TN running the latest WETA (software version J). This morning I awoke to find an OTA update available for install (must have happened overnight. Don't know why it appeared). I installed it and now I keep booting into recovery even after wipes and reinstalls of backups and full installs. Nothing I've tried so far seems to work. Anyone know of a solution or link to one? I have access to ADB/Fastboot (still shows device) and the "J" KDZ file. TIA and later.
Click to expand...
Click to collapse
I got the same update but i turned off automatic updates in Dev section
bountyman334 said:
I got the same update but i turned off automatic updates in Dev section
Click to expand...
Click to collapse
No offense brother, but that's an after the fact solution. I was going to open a new thread to describe the update. Not likely, for now. What I need is a solution to my problem. Sorry if I sound pissy, but I didn't need this freakin' update to screw up my phone. Most importantly, I should have known not to update a custom with a stock update. Dumb mistake.
Regards, JT
jt1954 said:
Hi All! I have an H918TN running the latest WETA (software version J). This morning I awoke to find an OTA update available for install (It must have happened overnight. Don't know why it appeared and don't know the size). I installed it and now I keep booting into recovery even after wipes and reinstalls of backups and full installs. Nothing I've tried so far seems to work. Anyone know of a solution or link to one? I have access to ADB/Fastboot (still shows device) and the "J" KDZ file. TIA and later.
Click to expand...
Click to collapse
The same has happened to me. Did you figure this out?
ctalbot said:
The same has happened to me. Did you figure this out?
Click to expand...
Click to collapse
Not yet. Try LG Bridge->Software Update->update-error-recovery. I tried but my notebook only has 2gb memory and a 25gb SSD. Unfortunately, LG Bridge is looking for 10gb of storage (Internal. You can't use external for some friggin' reason) to download the file, etc. which I don't have available. Follow the instructions in the thread "Restore v20 to 100% Stock (!!even for bricked devices!!" in "LG V20 Guides, News, & Discussion". Good Luck!
The update probably didn't even install.
It should have just triggered a TWRP bootloop.
Easy fix.
Power off or pull battery for a sec.
Hold vol down and power button - as soon as you see LG logo - release and immediately re-press power button only while continuing to hold vol down.
Factory reset screen will come up if you did it right. Use vol down to select YES twice to factory reset. ( It won't really reset anything but the recovery boot trigger ).
You'll end up in twrp. Just select reboot system and profit.
midmadn said:
The update probably didn't even install.
It should have just triggered a TWRP bootloop.
Easy fix.
Power off or pull battery for a sec.
Hold vol down and power button - as soon as you see LG logo - release and immediately re-press power button only while continuing to hold vol down.
Factory reset screen will come up if you did it right. Use vol down to select YES twice to factory reset. ( It won't really reset anything but the recovery boot trigger ).
You'll end up in twrp. Just select reboot system and profit.
Click to expand...
Click to collapse
That did it! You are a lifesaver!
ctalbot said:
That did it! You are a lifesaver!
Click to expand...
Click to collapse
No offense taking...i should of been more helpful..i wasn't Tryna to cone off disk-ish...
What was the update? If i can ask
midmadn said:
The update probably didn't even install.
It should have just triggered a TWRP bootloop.
Easy fix.
Power off or pull battery for a sec.
Hold vol down and power button - as soon as you see LG logo - release and immediately re-press power button only while continuing to hold vol down.
Factory reset screen will come up if you did it right. Use vol down to select YES twice to factory reset. ( It won't really reset anything but the recovery boot trigger ).
You'll end up in twrp. Just select reboot system and profit.
Click to expand...
Click to collapse
You're the man! Worked like a charm. LG Bridge said the update was triggered but failed on a partial install. That's just an FYI, not trying to rain on your parade. In any case, thanks again and your thanks-o-meter just jumped up a notch!
Regards, JT
bountyman334 said:
No offense taking...i should of been more helpful..i wasn't Tryna to cone off disk-ish...
What was the update? If i can ask
Click to expand...
Click to collapse
Don't worry man, it was me just being pissy. My apologies. You were right. I should have disabled auto-installs. All's well now though.:good:
As for what it is, I have no idea. Since it had already downloaded I also don't know what the size was. Maybe a new security update or possibly 7.1.2. In any case, I'll wait until WETA gets updated. Not going back to stock.
Regards, JT
LG update requires stock recovery to install updates. You have twrp in place of stock so it can't do anything but throw you into a recovery loop.
If you had done the factory reset before restoring backups and stuff you should have seen no changes in your phone.
The update files need to be deleted from your fota folder or you can end up in the twrp bootloop again.
midmadn said:
LG update requires stock recovery to install updates. You have twrp in place of stock so it can't do anything but throw you into a recovery loop.
If you had done the factory reset before restoring backups and stuff you should have seen no changes in your phone.
The update files need to be deleted from your fota folder or you can end up in the twrp bootloop again.
Click to expand...
Click to collapse
I re-installed WETA and the update reappeared. The files were supposedly downloaded, but not installed. I canceled the install and blocked all notifications as well as stopping auto-updates. I checked the fota in cache, per your advice, but found not a thing. Not sure where it could be. If you have any suggestions as to where it might be, I would appreciate it. Thanks for the advice.
Regards, JT
jt1954 said:
I re-installed WETA and the update reappeared. The files were supposedly downloaded, but not installed. I canceled the install and blocked all notifications as well as stopping auto-updates. I checked the fota in cache, per your advice, but found not a thing. Not sure where it could be. If you have any suggestions as to where it might be, I would appreciate it. Thanks for the advice.
Regards, JT
Click to expand...
Click to collapse
Found it! Right in front of my freakin' eyes. Wasn't in the fota folder, as I thought, though it was in cache by its lonely self. Used ES File Explorer Pro and found the size to be 148mb. Looks to be a security update. If anyone wants it, and understand I have the T-Mobile variant H918TN, I'll try to upload it.
May all that is good and holy bless you. Google kept giving me results to do ADB stuff that was giving me "no such folder" or somesuch error after typing out long strings of stuff I wasn't confident I typed correctly (being dyslexic)... even tried plugging into the computer and copy-pasting what was supposed to be the fix so my dyslexia wouldn't be a part of the problem and nothing for over an hour of me getting more and more snappish at my kids interrupting me. This fixed the recovery loop in a couple seconds. I don't care if I have to redo everything on the phone (it's new anyway, stupidly accepted an OTA update of CM14.1 nightly just as I was about to be done setting the darn thing up). Now I can chill with my kiddos a bit until bedtime then mess with the darn phone again without worry that I'll screw something up by forgetting where I was in the process.
Bless. You. Muchly.
midmadn said:
The update probably didn't even install.
It should have just triggered a TWRP bootloop.
Easy fix.
Power off or pull battery for a sec.
Hold vol down and power button - as soon as you see LG logo - release and immediately re-press power button only while continuing to hold vol down.
Factory reset screen will come up if you did it right. Use vol down to select YES twice to factory reset. ( It won't really reset anything but the recovery boot trigger ).
You'll end up in twrp. Just select reboot system and profit.
Click to expand...
Click to collapse