Related
UNLOCKED BOOTLOADER REQUIRED
Here it is: TWRP 2.6.3.0
I've tested backing up / restore, wiping, and installing an old backup (from ver. 2.6.0.0) and all seem to work. I also included the flag "HAVE_SELINUX := true" so it should be compatible with the newer 4.3 based ROMs (needs tested).
To install:
Download and unzip file ("img" was a few bytes over the 8mb forum limit)
Code:
fastboot flash recovery XT901-XT907-TWRP-2.6.3.0-recovery.img
BUGS: I have had the screen start very dim. Sometimes restarting the recovery would fix it, otherwise go to settings / screen, and set the timeout short so it goes out. Press power to turn on and it is at full brightness.
Enjoy!!
Thanks to:
TeamWin for TWRP.
Hashcode and Dhacker for STS-Dev Team source.
Djrbliss for unlocking the bootloader & providing root in the first place.
and mattlgroff
Thank you! Just tested it briefly and it works great. Glad the recovery is finally fixed to be able to use ADB. Was unable to use any TWRPs from 2.5.0.0+ as ADB was broken in the recovery.
CM 10.2 Build removed due to errors.
jbaumert said:
OP updated with link for TWRP compiled with CM10.2 sources
Click to expand...
Click to collapse
The recovery built with the 10.2 sources seems to have an issue with mounting the internal storage and sdcard, but the 1st one built is running perfect. I made a flashable zip of the 2.6.3.0 recovery for anyone who wants to simply flash it in recovery.
@mic213, Thanks for the sanity check. Any chance you have tried backup / restore of a 4.3 build?
Sent from my XT901 using Tapatalk 4
I was able to backup with it. Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
netizenmt said:
Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Do you mean when you reboot from TWRP? I noticed that on other builds, but didn't think much of it.
Recovery Tools is a free app on Google Play. Simply download the Recovery IMG. file from this post, and then open the Recovery Tools app. Grant it root, and now you can simply flash the img. file from the app without having to go into fastboot or compress the file into a flash able zip. Once recovery is flashed phone will reboot into whichever recovery is the most recently flashed. About as basic and straight forward as can be.
---------- Post added at 09:34 PM ---------- Previous post was at 09:22 PM ----------
The recovery file works great, only bug after about 4 days of use would be the dim menu screen in recovery. Still very readable even when bug pops up. Thanks for the great upload
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
scottocs said:
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
Edit....ehh maybe. Still working on it.
Click to expand...
Click to collapse
just make sure everything is wiped and that you are using 4.3 Gapps, also look up the SuperSU 1.65 update, some people have had trouble keeping root when rebooting into 4.3. Flash 4.3 ROM then GAPPS followed by SuperSU update, I would suggest running 4.3 on TWRP 2.5 or 2,6 first. Once your able to run 4.3 on one of those, then good ahead and try flashing 2.6.3. If anything on your phone is 4.2 and trying to load onto 4.3 it will never make it far past the boot screen.
Edited because I started rambling and couldn't delete.
Long story short, I have been having issues wiping, installing, and recovering.
I was flashing from a 4.3 ROM to another 4.3 ROM and decided it would be a good idea to wipe internal. Messed me up good.
I went back to 4.2 finally fixed booting issue on getting stuck at boot image. (Wasn't even making it to the boot animation.) I'll wipe everything except internal like I did before and go from 4.2 to 4.3. Last time I did this I didn't have issues.
motoroid7 said:
I'm not sure what I did, but some ROMs suggest that you wipe internal memory. I did this but now I have the issue after installing a ROM and booting it up... playing with it, if I then go to reboot the phone at all I just get stuck on my boot image (not the animation.) This happens on regardless of what ROM I've installed.
I also now can't go back to my backups. They fail on restoring. [Most recent backup was made on 2.5.0.0, previous to that 2.3.2.3]
How do I fix my phone? I'm wondering if I need to fxz back to a rooted stock ROM to fix what's going on?
Click to expand...
Click to collapse
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
RikRong said:
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
Click to expand...
Click to collapse
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
motoroid7 said:
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
Click to expand...
Click to collapse
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Kyles1329 said:
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Click to expand...
Click to collapse
To piggy back on general advice: I found I was having all sorts of problems going from 4.2 to 4.3. What finally did the trick was I wiped Dalvik, System, Cache AND I formatted data. The formatting was what did the trick.
When you wipe in twrp 2.5+ the recovery does not delete data/cache from internal (system) unless user mounts system prior to wipe. Wiping system cache, data, and dalvik cache is a full system wipe. Recommended if switching ROM rather than flashing nightly. This way no files from a AOKP ROM stick around and try to associate with your new CM based ROM.
Sent from my XT907 using Tapatalk 2
Thanks for the advice guys.
I was finally able to successfully getting my phone to work again last night (very early in the AM). It's very strange. I actually had 0 issues going from LiquidSmooth v2.9 to LiquidSmooth v3.0 (4.2 to 4.3). Though it was from the same dev could be part of it. It wasn't until I tried flashing from SlimROM/4.3 to CM10.2 nightly (where I wiped internal memory requiring me to type "yes".) Another thing is strange is even though it was saying I lost root in TWRP, I'm not sure that I ever did, unless TWRP just re-installed it when I reboot recovery automatically... because I finally told it no when asked if I wanted to re-install root? Then I was finally able to get LiquidSmooth v2.9 bootable and stable.
Again, thanks for all the help guys. I just wish I had a little bit understanding what I all did to finally get it to boot up. It was pretty early in the morning... going on 5/6AM. So I was pretty tired doing all of this. I just knew I couldn't let my phone not be up and running by morning.
I did a backup last night, flashed a 4.3 ROM which had reboot issues, and then restored with this version. I had zero issues, unlike when I was trying to restore with the previous version. Thank-you for your work.
It works with the xt902 too. Thanks!
What's the difference between the link in the first post and the one in the fourth? One of the is broken? Which one has been built with the CM10.2 sources?
I'm using a CM10.2 ROM... Which one should I peek?
Thanks!
Flashable ZIPs of Kitkat stock 4.4 Rom & KOT49H 4.4.2 update for nexus 7 (WIFI-2012)
Google has finally released stock Kitkat images for nexus 7 (WIFI-2012) so here you go:
4.4 factory images repacked to flashable ZIPs. No changes, no root, no anything. Can be used to install 4.4 into MultiROM or to upgrade existing stock 4.3 ROM without losing data.
dev-host: http://d-h.st/ceH
goo.im: http://goo.im/devs/Tassadar/stock_zips/grouper_krt16o.zip
and now new 4.4.2 update :
applying the OTA update via sideload:KOT49H from KRT16O
http://android.clients.google.com/p...signed-nakasi-KOT49H-from-KRT16O.6d652363.zip
Read before doing anything:
I take no credits for this as it's not my work.
I take no responsibility for any damage caused to your device.
No gapps needed, it's stock Kitkat.
Flashable zip is made by Tasssadar so go to his post and click "THANKS" button as the guy deserves it
Sweet
Nice! Thanks for posting this. Have been looking for an flashable zip.
Sent from my Nexus 7 using Tapatalk 4
Thank you for the posting this, I'd rather wait for an AOKP version but like most I want to see what all the fuss is about with kit kat.
Stock 4.4 Kitkat Zip works, thanks !!
Yes, I can confirm that this worked for my fairly easy & painless upgrade to the latest KitKat 4.4 on the 2012 Nexus 7 WiFi model. It was running on Smooth Rom v5.3 with custom kernel (thus, rooted & non-stock) - backed data with TB first & save to external HDD, uninstalled Lookout Security & a few Apps first, just in case they hang or freeze. Newest CWM 6.0.4.5 is the recovery - and, I have stock 4.2.2 back up saved in the CWM folder. Battery is full - 95% charged still.
Next, boot into recovery, wipe cache & dalvik, factory reset and restore 4.2.2 - reboot, check for functionality. Everything working - still rooted with CWM. Recheck to make sure that JWR66Y zip, SuperSU-v1.69zip and new Grouper_KRT16o zip freshly downloaded here are on the device. Device is almost pure stock & System Update check now showing 4.3 download is available OTA - skip it.
Next, boot into recovery, select & install JWR66Y zip - finished & reboot system, wait for apps to be updated (took a short coffee break) All is good - now running 4.3 with stock kernel, WiFi and userdata preserved, Play Store updating with Google account signed in, etc.
Finally, boot into recovery, wipe cace & dalvik, factory reset and install the new Group KRT160 zip here - this take a little longer, be patient. Next, install SU zip file first to root again (just to be sure,) then reboot system and allow apps to upgrade during booting process, the "X" is now the 4 bouncing balls - loooooooking good, success, I think. Finally, home screen came up after a few minutes & Play Store proceed to upgrade the apps - etc.
About tablet - Android 4.4 Kernel 3.1.10-gee1a0b2 (Wed Oct 16 17:06:02 PDT 2013) and Build number KRT160
Yay ! Next, boot back into CWM Recovery - do a Backup of the new 4.4 first before proceeding to clean up the various screens since many of the apps had been updated & all over. Total time involved from download to planning to completion - about 90 minutes.
Obviously, there are other ways to do it - this one works for me. Had updated ADB and prepared to do it the old fashion way, manually - just in case - and checked to make sure that I can connect with the micro-usb cable & reboot to bootloader & recovery, recognize device & had all the latest/proper drivers running (oh - running Windows 7 Ultimate 32 bit OS)
Thanks - I'm guessing the stock kernel that's included won't work with Multirom, right?
Sent from my VS980 4G using XDA Premium 4 mobile app
Letitride said:
Yes, I can confirm that this worked for my fairly easy & painless upgrade to the latest KitKat 4.4 on the 2012 Nexus 7 WiFi model. It was running on Smooth Rom v5.3 with custom kernel (thus, rooted & non-stock) - backed data with TB first & save to external HDD, uninstalled Lookout Security & a few Apps first, just in case they hang or freeze. Newest CWM 6.0.4.5 is the recovery - and, I have stock 4.2.2 back up saved in the CWM folder. Battery is full - 95% charged still.
Next, boot into recovery, wipe cache & dalvik, factory reset and restore 4.2.2 - reboot, check for functionality. Everything working - still rooted with CWM. Recheck to make sure that JWR66Y zip, SuperSU-v1.69zip and new Grouper_KRT16o zip freshly downloaded here are on the device. Device is almost pure stock & System Update check now showing 4.3 download is available OTA - skip it.
Next, boot into recovery, select & install JWR66Y zip - finished & reboot system, wait for apps to be updated (took a short coffee break) All is good - now running 4.3 with stock kernel, WiFi and userdata preserved, Play Store updating with Google account signed in, etc.
Finally, boot into recovery, wipe cace & dalvik, factory reset and install the new Group KRT160 zip here - this take a little longer, be patient. Next, install SU zip file first to root again (just to be sure,) then reboot system and allow apps to upgrade during booting process, the "X" is now the 4 bouncing balls - loooooooking good, success, I think. Finally, home screen came up after a few minutes & Play Store proceed to upgrade the apps - etc.
About tablet - Android 4.4 Kernel 3.1.10-gee1a0b2 (Wed Oct 16 17:06:02 PDT 2013) and Build number KRT160
Yay ! Next, boot back into CWM Recovery - do a Backup of the new 4.4 first before proceeding to clean up the various screens since many of the apps had been updated & all over. Total time involved from download to planning to completion - about 90 minutes.
Obviously, there are other ways to do it - this one works for me. Had updated ADB and prepared to do it the old fashion way, manually - just in case - and checked to make sure that I can connect with the micro-usb cable & reboot to bootloader & recovery, recognize device & had all the latest/proper drivers running (oh - running Windows 7 Ultimate 32 bit OS)
Click to expand...
Click to collapse
WOW. All I did was do backup of my apps with TiBu, did a complete backup of partitions with TWRP, factory reset, install the KitKat zip. TWRP asked me if I was aware root was lost and did I want to flash it, I did.
Why did you go through all of that as if you needed to start from a previous factory image? The entire point of waiting for the zip was to do what I outlined.
Excellent!
BobbaLouie said:
WOW. All I did was do backup of my apps with TiBu, did a complete backup of partitions with TWRP, factory reset, install the KitKat zip. TWRP asked me if I was aware root was lost and did I want to flash it, I did.
Why did you go through all of that as if you needed to start from a previous factory image? The entire point of waiting for the zip was to do what I outlined.
Click to expand...
Click to collapse
Good question, for the sake of another N7 owner's stock 4.2.2 device that I plan to "work" on and to document the steps to retrace in case of errors - reading some of the other posts about folks bricking theirs attempting the upgrade, etc. The short path & fast track in using the zip file would take 10 or 15 minutes.
Wiping cache & dalvik before flashing & upgrading, I now have a smooth running KitKat 4.4 including Google Now on the 2012 N7, had to update the apps and in some cases, uninstall & then re-install - it's refreshing & extending useful life span for another 18 months as support for 4.4 has just begun - not to mention XDA.
Flashable zip worked like a charm over my stock 4.3 w/ CWM recovery. Didn't even wipe data or anything. Thanks a bunch!
Any flashable bootloader of kitkat floating around?
Nvm. It looks that kitkat's bootloader it's the same with 4.3.
Sent from my Nexus 7 using xda app-developers app
Allright, so I wiped the system partition and flashed this, but got an error. Do I have to flash it over the stock 4.3. Or since I have currently wiped the **** out of my tablet, could I adb sideload the original Google image via TWRP adb sideload?
Can i flash it through twrp? I' m running cm10.2 an going back to stock doesn't work on My Windows 8 machine because of problems with adb and drivers.
sjondenon said:
Can i flash it through twrp? I' m running cm10.2 an going back to stock doesn't work on My Windows 8 machine because of problems with adb and drivers.
Click to expand...
Click to collapse
YES
Hi! I am using the PAC man ROM installed via TWRP. My nexus 7 is rooted. Am I going to lose the root if I install the kit kat ROM using TWRP?
Thanks a lot!
Flashed this over rooted deodexed JB 4.3 JWR66Y via TWRP and kept root & all data.
Thanks
Can someone guide What is the procedure download the zip
And flash the zip in recovery mode like cwm recovery ?
By doing that will i loose the data and all ?
Plz someone answer this.
pleasant said:
Can someone guide What is the procedure download the zip
And flash the zip in recovery mode like cwm recovery ?
By doing that will i loose the data and all ?
Plz someone answer this.
Click to expand...
Click to collapse
1. Download
2. Install via cwm/twrp "install zip from sdcard" function.
3. (Optional) format cache/dalvik cache
4. (Optional) flash supersu 1.69 (if already installed prior to kitkat, it will retain it, but if you want to update to this latest version, now is as good of a time as any)..
5. Reboot
6. Enjoy KitKat!
All previous apps/data is saved. Nothing is lost.
After the initial boot, I booted back into recovery and flashed the oxy kernel.. I notice a definite performance increase compared to jelly bean.
Hope this helps.
Sent from my Nexus 7 using Tapatalk 4
Hi there ,
I was going to flash it over Clean Rom, but it was failed ! Why this happened to me !?
Thanks.
Spannaa said:
Flashed this over rooted deodexed JB 4.3 JWR66Y via TWRP and kept root & all data.
Thanks
Click to expand...
Click to collapse
+1
Thanks!
--
best regards
fingerr
Hi There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers
Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk
Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!
So I have done the following steps:
Rooted my phone using Kingo root
Did a backup using Droidexplorer
Unlocked bootloader (check by entering secret menu)
Flashed CWM Touch recovery from their site for the LG Optimus 4x HD
Made a backup using CWM
Did a factory reset
Flashed Vanir 4.4 rom, I used the bottom one from here: http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/p880/
Rebooted, did not get past LG logo after leaving for 15 minutes, removed and reinserted Battery
Rebooted into recovery wiped the cache and dalvik cache
Rebooted again and did not get past LG logo again after leaving for 15 minutes
I have no idea which Vanir 4.4 release is stable as the first post isn't updated here: http://forum.xda-developers.com/showthread.php?t=2609285
I also cannot find a Vanir 4.3 release as the download points to the same page as the 4.4 version which only shows a limited amount of releases.
What is my next step?
WitchHunterNL said:
So I have done the following steps:
Rooted my phone using Kingo root
Did a backup using Droidexplorer
Unlocked bootloader (check by entering secret menu)
Flashed CWM Touch recovery from their site for the LG Optimus 4x HD
Made a backup using CWM
Did a factory reset
Flashed Vanir 4.4 rom, I used the bottom one from here: http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/p880/
Rebooted, did not get past LG logo after leaving for 15 minutes, removed and reinserted Battery
Rebooted into recovery wiped the cache and dalvik cache
Rebooted again and did not get past LG logo again after leaving for 15 minutes
I have no idea which Vanir 4.4 release is stable as the first post isn't updated here: http://forum.xda-developers.com/showthread.php?t=2609285
I also cannot find a Vanir 4.3 release as the download points to the same page as the 4.4 version which only shows a limited amount of releases.
What is my next step?
Click to expand...
Click to collapse
I suggest using TWRP Recovery instead from Adams Omni thread, flash that like a zip in recovery and then re-reboot to recovery and load TWRP.
go to wipe>Advanced Wipe
And select cache, Dalvik Cache, System, and Data, and swipe to wipe them at the bottom.
Then go back to install, and find the Rom Zip and flash the Rom and then reboot, if it still isnt working, re-download the file, or choose a different rom and see if that one boots for you.
I don't think the recovery can be the problem here, so I would start with checking the download, and perhaps trying another ROM.
© Nexus 7 (2013)
Its probably an outdated recovery version you're using I know that only twrp 2.6.3.0 and up support flashing KitKat Roms
don't forget to hit thanks!
abhi08638 said:
Its probably an outdated recovery version you're using I know that only twrp 2.6.3.0 and up support flashing KitKat Roms
don't forget to hit thanks!
Click to expand...
Click to collapse
If he was using an outdated recovery, in the case of CWM anything below 6.0.4.4, he wouldn't even be able to pass the installation as he would get a status 7 error. Since he got to the point where he was ready to boot, again I don't think it's the recovery's fault. But to clear things up, would the OP mind sharing his recovery version?
If you do want to stick with Vanir, another thing you could try is to flash a custom kernel on top of the ROM and see if it boots then. Good luck!
© Nexus 7 (2013)
Hi, I'm unable to flash the stock image because my CWM version is too high (staus 7 errors), however, I'm unable to downgrade CWM.
I've tried flashing it from ROM Manager/similar apps, Writing and booting to SD, flashing from inside CWM. I've even tried TWPR, but it just always boots back to the original CWM.
Any ideas?
What rom did you have before attempting to flash back the stock? This happened to me yesterday, and I had to play with it to get it to work. I had to restore a TWRP backup that was on Succulent's CM10.2 because it automatically installed TWRP 2.6.3.0. I then was able to flash an earlier rom and/or restore to a LATER rom. Confusing situation, but I figured it out.
What I would do is backup your current rom, factory reset, and then flash a rom that automatically installs an earlier version of recovery. The only one I know of is Succulent's CM10.2 (because to want to downgrade your recovery, not go to TWRP 2.7.1.0) and then flash the desired earlier recovery.
Tl;dr: Backup your current rom, factory reset, flash Succulent's CM10.2 then flash Old CWM, then flash stock rom
irimolsjik572 said:
What rom did you have before attempting to flash back the stock? This happened to me yesterday, and I had to play with it to get it to work. I had to restore a TWRP backup that was on Succulent's CM10.2 because it automatically installed TWRP 2.6.3.0. I then was able to flash an earlier rom and/or restore to a LATER rom. Confusing situation, but I figured it out.
What I would do is backup your current rom, factory reset, and then flash a rom that automatically installs an earlier version of recovery. The only one I know of is Succulent's CM10.2 (because to want to downgrade your recovery, not go to TWRP 2.7.1.0) and then flash the desired earlier recovery.
Tl;dr: Backup your current rom, factory reset, flash Succulent's CM10.2 then flash Old CWM, then flash stock rom
Click to expand...
Click to collapse
Current ROM is the last stable CM11 build.
You wouldn't happen to have a link for that would you? I've searched but no luck.
goo.im/devs/succulent then keep going through the directory until you get to the ovation rom builds
WillyVWade said:
Hi, I'm unable to flash the stock image because my CWM version is too high (staus 7 errors), however, I'm unable to downgrade CWM.
I've tried flashing it from ROM Manager/similar apps, Writing and booting to SD, flashing from inside CWM. I've even tried TWPR, but it just always boots back to the original CWM.
Any ideas?
Click to expand...
Click to collapse
If you go to my HD/HD+ CWM thread linked in my signature and look at item 5, I have a flashable CWM (v6036) that is flashable with the newer recoveries. Just use your newer one to flash it and it goes back down to 6036. That way you can flash older zips if you want.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
If you go to my HD/HD+ CWM thread linked in my signature and look at item 5, I have a flashable CWM (v6036) that is flashable with the newer recoveries. Just use your newer one to flash it and it goes back down to 6036. That way you can flash older zips if you want.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I swear I flashed just about everything in that thread. You're a bloody genius!
WillyVWade said:
I swear I flashed just about everything in that thread. You're a bloody genius!
Click to expand...
Click to collapse
Actually I modified that zip just for that purpose. I suppose I should explain that in that thread.
Edit: Done.
Sent from my SM-T900 using XDA Premium HD app