Database Users

After the AlphaRevX Beta

Yesterday i had the fun to test out the beta and it was a succes.
But now i dont get it!
I tried the pc49img.zip story, but i cant get cwm recovery installed. Sd card is fat32 and its parsing the file, but it wont install cwm rec.
Whats steps should i do to install a custom rom?

wesleyvdbrink said:
Yesterday i had the fun to test out the beta and it was a succes.
But now i dont get it!
I tried the pc49img.zip story, but i cant get cwm recovery installed. Sd card is fat32 and its parsing the file, but it wont install cwm rec.
Whats steps should i do to install a custom rom?
Click to expand...
Click to collapse
Got it!!
Found this youtube movie: http://www.youtube.com/watch?v=oMmCatsXMSY

wesleyvdbrink said:
Yesterday i had the fun to test out the beta and it was a succes.
But now i dont get it!
I tried the pc49img.zip story, but i cant get cwm recovery installed. Sd card is fat32 and its parsing the file, but it wont install cwm rec.
Whats steps should i do to install a custom rom?
Click to expand...
Click to collapse
After S-OFF.....you've to Install ECLAIR FROM RUU...to downgrade the HBOOT and install UNREVOKED

emiliano7 said:
After S-OFF.....you've to Install ECLAIR FROM RUU...to downgrade the HBOOT and install UNREVOKED
Click to expand...
Click to collapse
Followed the youtube movie from my sec post.
Hboot stayed at v6.x but Unrevoked did his job, cwm is installed.

emiliano7 said:
After S-OFF.....you've to Install ECLAIR FROM RUU...to downgrade the HBOOT and install UNREVOKED
Click to expand...
Click to collapse
That is completely unnecessary.
Follow attn1's excellent guide here:-
http://forum.xda-developers.com/showthread.php?p=14693680

can u please sent me the files for the s-off.i know i need the key in order to work but please sent it
Thanks

emiliano7 said:
After S-OFF.....you've to Install ECLAIR FROM RUU...to downgrade the HBOOT and install UNREVOKED
Click to expand...
Click to collapse
Although it is not possible to downgrade hboot without the hboot downgrader they will release. But as the S-OFF is due to engineered hboot, this kind of thought is like, sacrificing the S-OFF just to root (which can also be done easily without downgrading).
Remember if u manage to downgrade the hboot, u will loose the awesome S-OFF. The process with xtc clip will not apply here.

im really newbie, let me get this straight
if i have a unrooted s-on hboot 1.01... and i will put the magic of alpha rev on my phone, it will root it and s-off?
or
it will s-off my unrooted phone, then i downgrade the hboot to necessary and install unrevoked?

tinkerer-svk said:
im really newbie, let me get this straight
if i have a unrooted s-on hboot 1.01... and i will put the magic of alpha rev on my phone, it will root it and s-off?
or
it will s-off my unrooted phone, then i downgrade the hboot to necessary and install unrevoked?
Click to expand...
Click to collapse
It will S-OFF your Wildfire. After that, do not downgrade the HBoot. Just follow the link given in Post #5 of this thread by kmdm. It's explained there what to do to to get Custom Recovery and Root.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

3xeno said:
It will S-OFF your Wildfire. After that, do not downgrade the HBoot. Just follow the link given in Post #5 of this thread by kmdm. It's explained there what to do to to get Custom Recovery and Root.
Click to expand...
Click to collapse
Why i shouldn't downgrading HBOOT by installing RUU?
If i use AlpharevX i can back s-on?

Marurban said:
Why i shouldn't downgrading HBOOT by installing RUU?
If i use AlpharevX i can back s-on?
Click to expand...
Click to collapse
Because there is absolutely no need for taking risks like that - each time you try to change your hboot, there is a chance that it won't work, and that you are stuck with a dead device.
And besides that, there is really no need to do so!
Unrevoked: used a exploit in the hboot 0.80 to get TEMPORARY S-off, so that they can install a custom recovery. Afther that you the security will be s-on again, but you will have a custom recovery. That makes is possible for you make changes in the protected folders, and makes it possible for you to flash new partitions, and thus install new ROMs.
S-off by AlphaRevX or XTC-clip: PERMANENT S-off. you can use fastboot (an utility of the hboot, as far as I understand) to flash any recovery you like, to flash any partition you like,...
So as you can see: really, really really no need to try to downgrade the hboot, as every S-off hboot is much better than an Hboot "cracked" by UnrEVOked (altough those guys did a very great thing for us - we will never forget them ).
Erwin

Hi everybody,
After the S-OFF of my wildfire can I use unrevoked to root it?
Thank you very much

Read my guide that's under the dev section to get root after S-OFF

nejc121 said:
Read my guide that's under the dev section to get root after S-OFF
Click to expand...
Click to collapse
Thank you very much.

[GUIDE] Unlocked bootloader, and new howto on rooting the HTC Evo Shift (2.3.4)

THIS THREAD IS OUTDATED.
PLEASE REFER TO
http://forum.xda-developers.com/showthread.php?t=1357157
WARNING: THIS VOIDS YOUR WARRANTY AND YOU WILL LOSE ALL DATA IN UNLOCKING THE BOOTLOADER
0) Be running stock 2.3.4 latest OTA update from HTC
1) Register at htcdev.com
2) Unlock the bootloader by choosing HTC Evo 3D for Sprint and follow instructions
3) Once you have unlocked bootloader flash clockwork recovery by downloading the following file:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-speedy.img
From the adb folder run "fastboot flash recovery recovery-clockwork-5.0.2.0-speedy.img"
4) adb reboot recovery
5) You will see the beautiful clockwork recovery screen.
6) Goto mounts/storage, mount usb storage
7) Download su from the following location:
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
8) Go back, install zip from sdcard, choose the superuser zip.
9) Reboot, open market, search for super user and install it.
10) Open superuser app go to preferences and choose update su binary.
11) Download terminal emulator and run "su" to test if you have root. $ should turn to #.
You have now rooted the Shift permanently!
Please note.. this is S-ON UNLOCKED BOOTLOADER, NOT ENGINEERING S-OFF BOOTLOADER.
Binary100100 said:
I don't know where to start with all of your questions but I will do my best.
The difference between S-OFF and Unlocked bootloader is that with S-OFF you can flash anything including a radio and supposedly it would give us the ability to update the kernel by recovery. With an unlocked bootloader we cannot update the radio or kernel but can pretty much change everything else. An unlocked bootloader is required to root your device and remove all the bloat that you don't like. You can temp root the device to remove that bloatware however they will re-appear after a reboot. It has been under some debate if in fact using the unlock_code.bin file provided by htcdev is going to void your warranty if your device would require servicing. If it's vital to know that information then call HTC to inquire before unlocking.
Regarding CM9, it is possible but slightly inconvenient since CM9 would almost certainly require a different kernel and since we cannot flash kernels by recovery it would have to be done in a very certain order. Is it currently in the works? To my understanding, yes! Any idea when you can see it as a download here in the forums? Not at this time. Check back daily because things change frequently!
Click to expand...
Click to collapse
Work arounds for unlocked s-on bootloader:
Flashing kernel/custom ROMs:
Pull boot.img from kernel or ROM zip file and run:
adb reboot bootloader
fastboot flash boot boot.img
power off
adb reboot recovery
wipe cache, wipe dalvik, (if flashing a rom format /system and do a wipe data/factory reset)
install kernel/ROM zip from sdcard in CWM
Work around for radio:
unroot, relock, take ota
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thanks:
koush
nurrwick
jmztaylor
sparksco
otaking71

Have you tried flashing a kernel?
Sent from my PG06100 using Tapatalk

drob311 said:
Have you tried flashing a kernel?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Bout to try dodge kernel now and adding note about s-on now.

I can never trust that HTCdev because of I can't have s-off but that's just me not wanting to deal with workarounds. But anyhow thanks for the information VICODAN greatly appreciated
Sent from my EVO 4G

notsointeresting said:
I can never trust that HTCdev because of I can't have s-off but that's just me not wanting to deal with workarounds. But anyhow thanks for the information VICODAN greatly appreciated
Sent from my EVO 4G
Click to expand...
Click to collapse
Work arounds for s-off:
Flashing kernel:
Pull boot.img from kernel zip file and run:
fastboot flash boot boot.img
power off
adb reboot recovery
wipe cache, wipe dalvik,
install kernel zip from sdcard in CWM
Work around for radio:
unroot, relock, take ota

Stock HTC Sense GB 2.3.4, rooted, radio 1.08.01.0111 running dodge kernel 1.6:

Very nice. I noticed we don't have a ruu for this update yet. Any way to get the system out with adb so some awsome sense devs could get working on a rom for us?

Antutu benchmark:
Dodge kernel 1.6, 1.92 ghz, bfq I/O scheduler, performance governor, patriot class 10 SD card
Quadrant:
Quadrant on CFQ:
Antutu on CFQ:

just got a evo 4g shift yesterday is there anyway to downgrade from 2.3.4 to 2.3.3? i updated by mistake i was originally on 2.3.3. can i follow this guide and unlock my phone then downgrade to 2.2.3?

onsomeg**** said:
just got a evo 4g shift yesterday is there anyway to downgrade from 2.3.4 to 2.3.3? i updated by mistake i was originally on 2.3.3. can i follow this guide and unlock my phone then downgrade to 2.2.3?
Click to expand...
Click to collapse
Well apparently temproot doesn't work but I'm wondering if you used my root process and relocked the bootloader and then flashed PG06IMG.zip 2.2 would it work? Can you please try this?

VICODAN said:
Well apparently temproot doesn't work but I'm wondering if you used my root process and relocked the bootloader and then flashed PG06IMG.zip 2.2 would it work? Can you please try this?
Click to expand...
Click to collapse
would i brick trying and how would i relock the bootloader?

onsomeg**** said:
would i brick trying and how would i relock the bootloader?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1277793
try that. its much easier.

jesuscash said:
http://forum.xda-developers.com/showthread.php?t=1277793
try that. its much easier.
Click to expand...
Click to collapse
thanks, so i don't have to unlock and then run the script or i do have to unlock and run the script?
and once i run it what do i do or pick?
sorry for all the questions my old phone was easier to root and i learned about it, seems like i'm starting over on this phone.

onsomeg**** said:
thanks, so i don't have to unlock and then run the script or i do have to unlock and run the script?
and once i run it what do i do or pick?
sorry for all the questions my old phone was easier to root and i learned about it, seems like i'm starting over on this phone.
Click to expand...
Click to collapse
you run the "fre3atlast" file and follow the cmd instructions.
This temproots you (hopefully, it worked on 2.3.3) and allows you to downgrade to 2.2 which has a permroot.

jesuscash said:
you run the "fre3atlast" file and follow the cmd instructions.
This temproots you (hopefully, it worked on 2.3.3) and allows you to downgrade to 2.2 which has a permroot.
Click to expand...
Click to collapse
I talked to Indirect and fre3atleast isn't any different than fre3vo.

onsomeg**** said:
would i brick trying and how would i relock the bootloader?
Click to expand...
Click to collapse
No you wont brick. Follow the instructions on HTCDEV.com

VICODAN said:
No you wont brick. Follow the instructions on HTCDEV.com
Click to expand...
Click to collapse
i got you and the other user confused as the same person lol okay so i'm bout to unlock using htcdev.com and what other steps do i need to take after that?

onsomeg**** said:
i got you and the other user confused as the same person lol okay so i'm bout to unlock using htcdev.com and what other steps do i need to take after that?
Click to expand...
Click to collapse
Read the OP for all the instructions.
My question is can you relock and flash Scaryghouls PG06IMG.zip and downgrade to 2.2?
You might need to run 2.3 RUU, either way instructions here:
http://forum.xda-developers.com/showthread.php?t=1357157

Ah, now I hope my phone doesn't die or nothing now so I don't get a replacement, and be stuck with 2.3.4, and the htcdev bootloader unlock, reminds me of the Evo3d rooting and flashing kernel, and roms complicated, lol.. But anyways great job finding this.
Sent from my PG06100 using Tapatalk

madplaya1 said:
Ah, now I hope my phone doesn't die or nothing now so I don't get a replacement, and be stuck with 2.3.4, and the htcdev bootloader unlock, reminds me of the Evo3d rooting and flashing kernel, and roms complicated, lol.. But anyways great job finding this.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You can always relock the bootloader.

Firmware-update JLS36I (Android 4.3.1) Nexus 7 2013 LTE available

This morning I was suprised to find a new update for my Nexus 7 2013 LTE; it brings the Android-version to 4.3.1
No changelog found yet...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Any news if this breaks root etc.? WIll flashing this from recovery and flashing supersu.zip afterwards work like last time?

Jacktheskipper said:
Any news if this breaks root etc.? WIll flashing this from recovery and flashing supersu.zip afterwards work like last time?
Click to expand...
Click to collapse
It's broken my root, though that's probably because I used the OTA update rather than flashing in recovery.

I got it too.
in the update file a some changes at:
keymaster / keystore
camera firmware
framework
services and telephony-common
what exactly has changed I do not know.
root + recovery need to be flashed again. but no problems.

if root and recovery need to be flashed again, did you just do the ota update from the sytem or did you sideload the zip and flash it from recovery?

I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan

jmone said:
I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan
Click to expand...
Click to collapse
You won't be able to until someone puts out a custom ROM for Flo/Deb.

jmone said:
I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan
Click to expand...
Click to collapse
First go back to stock kernel, then remove any custom modified files from stock, then try to do the OTA update.

jak3z said:
First go back to stock kernel, then remove any custom modified files from stock, then try to do the OTA update.
Click to expand...
Click to collapse
FYI - used the SkipSoft Android ToolKit to reflash the stock JLS36C then did the OTA update to JLS36I. Bit of a PITA as I now need to reinstall it all but it works!

jmone said:
FYI - used the SkipSoft Android ToolKit to reflash the stock JLS36C then did the OTA update to JLS36I. Bit of a PITA as I now need to reinstall it all but it works!
Click to expand...
Click to collapse
That was totally unnecessary,

I've updated European nexus in Russia without any problem
Have a trwp recovery and supersu binary. Check ota survivalable mode in supersu and just apply update. Trwp updates all stuff. Root works, recovery didn't check for now

jak3z said:
That was totally unnecessary,
Click to expand...
Click to collapse
Thanks.... Next time!

Update :lost trwp recovery and need to flash it again.
Отправлено с моего...

oh man! i just rooted my N7 last night. i just installed a LOT of apps .
i used wugs toolkit so right now i have twrp + root and nothing more. so im stock rooted.
i have never done this before but should i use wugs tool kit again to unroot and relock bootlader THEN ota?
or can i just update while rooted?
thanks!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

keplenk said:
oh man! i just rooted my N7 last night. i just installed a LOT of apps .
i used wugs toolkit so right now i have twrp + root and nothing more. so im stock rooted.
i have never done this before but should i use wugs tool kit again to unroot and relock bootlader THEN ota?
or can i just update while rooted?
thanks!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
You can run the OTA perfectly fine, you will lose Root and Recovery after you OTA, but you can get back those 2 anytime you want. Grab the CF-Auto-Root of chainfire (its on the Android Original Dev forum) and you will get root back.

keplenk said:
or can i just update while rooted?
p
Click to expand...
Click to collapse
you totally can, put the zip-file on your device, got to twrp-recovery and flash the zip file. if you wanna make sure you aren`t running into any trouble download the supersu.zip from here: http://download.chainfire.eu/346/SuperSU/ and flash it after flashing the update.

Jacktheskipper said:
you totally can, put the zip-file on your device, got to twrp-recovery and flash the zip file. if you wanna make sure you aren`t running into any trouble download the supersu.zip from here: http://download.chainfire.eu/346/SuperSU/ and flash it after flashing the update.
Click to expand...
Click to collapse
http://download.chainfire.eu/supersu

1. Go into SuperSu settings to enable survival mode.
2. Download the OTA directly on your Nexus as you would without root and restart to install.
3. It will be installed by TWRP, root will be kept, but TWRP will be gone.
4. Reflash TWRP in Fastboot.

Cannot install CWM over TWRP

I've been at this for about 5 hours now, and I can't seem to get CWM installed.
I decided to flash to stock fw (4.2.2) so I could carrier unlock my phone. After I flashed to stock, I used the CASUAL tool to do this.
After I had root, I tried getting CWM back so I could restore my backup, prior to this whole process, however every time I have attempted to flash CWM the phone reboots to TWRP.
I thought I knew about this kind of stuff, but now it's just starting to get to me
Has anyone encountered this or know of a fix?
Thanks.

tasiv said:
I've been at this for about 5 hours now, and I can't seem to get CWM installed.
I decided to flash to stock fw (4.2.2) so I could carrier unlock my phone. After I flashed to stock, I used the CASUAL tool to do this.
After I had root, I tried getting CWM back so I could restore my backup, prior to this whole process, however every time I have attempted to flash CWM the phone reboots to TWRP
I thought I knew about this kind of stuff, but now it's just starting to get to me
Has anyone encountered this or know of a fix?
Thanks.
Click to expand...
Click to collapse
You messed up. You have an i337 and are now on mf3 firmware. You can't put on a custom recovery. Safestrap is you're only option
Sent from my Nexus 5

jd1639 said:
You messed up. You have an i337 and are now on mf3 firmware. You can't put on a custom recovery. Safestrap is you're only option
Sent from my Nexus 5
Click to expand...
Click to collapse
I'm currently running JDQ39.I337UDUAMDB (galaxy s4 stock FW v4.2.2). I came from the latest Google Edition rom posted by Danvdh.
When I run CASUAL that flashes a recovery. If I now have a mf3 device, how could I have flashed TWRP with CASUAL?
I have somehow managed to get another recovery installed using the following instructions:
download the two files in the instructions
su
cd /data/local/tmp
chmod 755 *
./lok_flash recovery recovery.lok
reboot recovery
That allowed me to change the recovery, but I really have no idea what that did.
I don't think I have an mf3 device now. Is there any way to verify this?

Check your baseband. You probably still are on mdb. Are you flashing a zip to get back to cwm? Which one
Sent from my Nexus 5

jd1639 said:
Check your baseband. You probably still are on mdb. Are you flashing a zip to get back to cwm? Which one
Sent from my Nexus 5
Click to expand...
Click to collapse
baseband = I337UCUAMDB
I'm not flashing a zip, it's apparently a (IMO) bastardized version of clockwork mod. Hell, it could be a zip, but I know I'm running a terminal command to write the recovery. I don't think I can paste links...
I have no problem flashing the google edition firmware or AOSP based firmware when I have TWRP installed. It's just trying to get rid of TWRP and go back to CWM that I want to do (because I backed up my phone in CWM and now I can't get back).

tasiv said:
baseband = I337UCUAMDB
I'm not flashing a zip, it's apparently a (IMO) bastardized version of clockwork mod. Hell, it could be a zip, but I know I'm running a terminal command to write the recovery. I don't think I can paste links...
I have no problem flashing the google edition firmware or AOSP based firmware when I have TWRP installed. It's just trying to get rid of TWRP and go back to CWM that I want to do (because I backed up my phone in CWM and now I can't get back).
Click to expand...
Click to collapse
Flash this in your current twrp, it'll replace twrp and put in cwm 6.0.4.7
Edit, PS to carrier unlock I think you need to be on mdl firmware

jd1639 said:
Flash this in your current twrp, it'll replace twrp and put in cwm 6.0.4.7
Edit, PS to carrier unlock I think you need to be on mdl firmware
Click to expand...
Click to collapse
OK, so I have TWRP right now, and I ran that utility you created for me. It failed.
here's what I can make out of the log:
assert failed: package_extract_file("orecovery-clockwork-6.0.4.7-jflteat
E:Error executing updater binary in zip '/sdcard/Download/jjd-recovery-c
Error flashing zip "/sdcard/Download/jjd-recovery-clockwork-6.0.4.7-jflt
updating partition details...
it's cut off on the right, but I think you can tell that...

tasiv said:
OK, so I have TWRP right now, and I ran that utility you created for me. It failed.
here's what I can make out of the log:
assert failed: package_extract_file("orecovery-clockwork-6.0.4.7-jflteat
E:Error executing updater binary in zip '/sdcard/Download/jjd-recovery-c
Error flashing zip "/sdcard/Download/jjd-recovery-clockwork-6.0.4.7-jflt
updating partition details...
it's cut off on the right, but I think you can tell that...
Click to expand...
Click to collapse
Sorry, I had a typo in it try this

jd1639 said:
Sorry, I had a typo in it try this
Click to expand...
Click to collapse
I feel useless.... Now It's giving me the "system software not authorized by AT&T has been found on your phone" I attempted to flash lokidoki, but I think that's just for the rom...

tasiv said:
I feel useless.... Now It's giving me the "system software not authorized by AT&T has been found on your phone" I attempted to flash lokidoki, but I think that's just for the rom...
Click to expand...
Click to collapse
Does your baseband and build number both say your on mdb firmware?
Sent from my SAMSUNG-SGH-I727

jd1639 said:
Does your baseband and build number both say your on mdb firmware?
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
currently my baseband = I337UCUAMDB
and my build number = JDQ39.i337UCUAMDB
so, yes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

tasiv said:
currently my baseband = I337UCUAMDB
and my build number = JDQ39.i337UCUAMDB
so, yes
Click to expand...
Click to collapse
Idk, what to say now. I'm thinking it's because you're on mdb and not mdl. Mdb is really old. You might try flashing mdl. You'll still be able to put on a custom recovery and flash roms just like you currently are. Just don't flash mf3 or higher. If you go that route you'll want to make sure to freeze the update.apk so the ota didn't work.
Sent from my Nexus 5

jd1639 said:
Idk, what to say now. I'm thinking it's because you're on mdb and not mdl. Mdb is really old. You might try flashing mdl. You'll still be able to put on a custom recovery and flash roms just like you currently are. Just don't flash mf3 or higher. If you go that route you'll want to make sure to freeze the update.apk so the ota didn't work.
Sent from my Nexus 5
Click to expand...
Click to collapse
I appreciate the help you've given me.
I think I may try that, I'll just have to find a copy of it somewhere. I've got my phone back into a state where I (almost) left it thanks to titanium backup and the ROM I've been using. I really liked CWM, but the features of TWRP seem promising. I've been having a little trouble backing up the phone though (I think I'm exceeding max file size of backup?) but I'm sure it'll eventually work.

[VK810] Official Kit Kat Update Information

We're all in the process of receiving and installing this update, and there are many questions about recoveries, rooting, etc. This is a thread to gather all the info we know so people don't have to be searching through tons of posts.
(I'm in the process of installing now, so I'll answer as many of these questions as I can. I will also update the OP with info from other users. If anything I state is untrue, please post and let me know.)
Can I take the update while rooted?
Yes! If you are on 4.2 and rooted but on STOCK RECOVERY, you can take the OTA and keep root.
Can I take the update with TWRP installed?
No! You will bootloop into recovery.
Is there an alternative/manual/TWRP method of installing?
Yes, see below post.
How am I supposed to update if I installed TWRP?
See below post, "README if you are currently on JB4.2.2"
Alternative method: "download flashify from the play store, backup twrp, then flash the recovery.img from OP. No pc needed & 100% pain free." Thank you to 86shelby. Then take the OTA.
Can I root the 4.4 version?
As of 8/26, yes! Stumproot works with the Bruteforce method. http://forum.xda-developers.com/show....php?t=2850906
Can I downgrade from 4.4 to 4.2?
Yes
If anyone else has questions they'd like posted, please let me know, and I'll put them in.

NOTE: If you want root/twrp in KK4.4.2, you'll need to pre-root in JB4.2.2 before OTA update(towelroot works in JB4.2.2, but not in KK4.4.2)
Looks like Stumproot works with KK4.4.2
README if you have a non-booting device
If you tried OTA update with TWRP recovery and get stuck in a bootloop for TWRP
Do one of the options below:
A) If you still want 4.4.2 via Verizon OTA, flash stock recovery
Go into TWRP, restore stock recovery via link below
http://forum.xda-developers.com/showpost.php?p=52975059&postcount=65
B) If you want to stop the bootloop, and flash 4.4.2 via TWRP backup from below...
Go into TWRP, wipe OTA partition (which signals the device to keep going into recovery)
http://forum.xda-developers.com/showthread.php?p=51749086#post51749086
Click to expand...
Click to collapse
If I mess everything up and device doesn't boot
Restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)​
README if you are currently on JB4.2.2
If you already have TWRP, you can flash 4.4.2 via the TWRP backup below (probably can just flash over 4.2.2 without factory reset... do factory reset only if something goes wrong)
http://forum.xda-developers.com/showthread.php?p=53043541#post53043541
If you want to apply update via Verizon OTA, READ below first
If you have TWRP installed, you'll need to flash stock recovery. Either (A)
restore stock recovery only, or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
NOTE: some people have problems with OTA even after restoring stock recovery. You'll have to restore using the (B) method, and lose everything
[*]If you want root in 4.4.2, you'll need to apply root BEFORE OTA (via towelroot, ...?). root is allowed during OTA, will be maintained after OTALooks like stumproot works
Apply OTA, hope nothing goes wrong
Yay!
Click to expand...
Click to collapse
README if you are currently on KK4.4.2
Splitwindow/multiwindow on 4.4.2
http://forum.xda-developers.com/lg-...10-splitwindow-multiwindow-stock-4-4-t2837326
Root on 4.4.2: Use Stumproot
TWRP on 4.4.2
Root ? (Towelroot isn't working though)
Flash 4.2.2 aboot.img and TWRP.img
A) Upload aboot.img from 4.2.2 to device, then do
Code:
adb shell
su
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
B) Follow steps in TWRP thread to install TWRP
Click to expand...
Click to collapse
4G LTE does not work on 4.4.2?
Flash modem from 4.2.2 -> http://forum.xda-developers.com/showpost.php?p=54584896&postcount=5
Going from 4.4.2 back to 4.2.2
Install TWRP (see section above)
Get 4.2.2 TWRP backup from here and restore
or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
Click to expand...
Click to collapse
​

Guess I got lucky - never got around to installing the custom recovery. I MEANT to do that....

https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot

So this is what I get when I check for update. I'm stock unrooted I even did a FDR. Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT1080 using Tapatalk

Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.

modus81 said:
Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.
Click to expand...
Click to collapse
have you tried other root methods?
ioroot, or this root below? (
http://forum.xda-developers.com/showthread.php?t=1886460&highlight=4+2+2

paperWastage said:
https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot
Click to expand...
Click to collapse
How do I install this?
Sent from my VK810 4G using Tapatalk

gfullwr70 said:
How do I install this?
Sent from my VK810 4G using Tapatalk
Click to expand...
Click to collapse
you don't. go through Settings-> System update

paperWastage said:
you don't. go through Settings-> System update
Click to expand...
Click to collapse
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk

gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Same here

Flashing comletely stock via .kdz file
I'm getting the 0X13E error. Does anyone have the the process for this? I saw a different thread that directed to a droidreviews.com website but one of the files it said to download, my Chrome browser scanned as malicious so I stopped pursuing that route.

ssinn said:
Same here
Click to expand...
Click to collapse
gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123

paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
Thanks this is what I was looking for. I'll give it till tonight to see if the ota shows up then I'll try this method.
Sent from my XT1080 using Tapatalk

paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?

prana22 said:
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?
Click to expand...
Click to collapse
first one.... my tablet wasn't able to find an OTA on 4G LTE (on t-mobile's network), but wifi works fine

Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.

rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
That's interesting, and good to know. Can anyone else verify this? I didn't think the update would go through if you were rooted. Now I might downgrade through kdz again and root before I take the OTA.

rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
go flash TWRP, make backup of stock and share it please?

How can I revert to stock recovery in OSX? All I see is the LG Mobile tool for windows?