Related
So I've got a Sprint-branded Optimus Black. Rooted the device via SuperOneClick, and installed Clock Work Recovery Mod. Unable to flash any rom, get error "error in /sdcard/<romname>.zip Error Status 1". Checked MD5s, all match.
So I decide to restore to factory defaults. I go to Settings, Privacy, Factory data reset. When I do this, the phone only restarts to Clockwork Recovery mod. It will only boot into CWM unless I "wipe cache partition". After this, I can boot into stock OS.
So what the hell is going on here? My goal is to get CM7 running on this device.
What do I need to do to get this going?
I didn't see any solutions in my forum search. I would appreciate some input.
Sprint-branded eh ?
are you talking about Black or Maquee ?
cuz they're both twin brother, but Marquee runs in CDMA
CMIIW
agent205 said:
Sprint-branded eh ?
are you talking about Black or Maquee ?
cuz they're both twin brother, but Marquee runs in CDMA
CMIIW
Click to expand...
Click to collapse
But though doesnt have anything to do with booting problems, he only wouldnt have network.
Your issue can be solved as follows.
As u said, u want CM7 on your device, download the nightly version, that you like.
boot to recovery, make full wipe (factory reset, wipe cache, wipe dalvic, wipe battery stats (both under advanced) ), go to install zip from SD card, choose zip, install it, reboot and enjoy
But as it seems, that your not that familiar with modding, flashing and so on, better first read some on those topics, in order to get the needed knowledge
I've already attempted to install CM7. My first post explains this. Let's review the situation:
* Rooted
* Installed CWM
* Attempted to install CM7, got status 1 error.
* Attempted to wipe phone, but it only boots into CWM.
I'm not sure what the problem is. I want to restore the phone to stock, and install CM7.
Anyone got a solution? If I can provide any other info that would be helpful, let me know.
N00BY0815 said:
But though doesnt have anything to do with booting problems, he only wouldnt have network.
Your issue can be solved as follows.
As u said, u want CM7 on your device, download the nightly version, that you like.
boot to recovery, make full wipe (factory reset, wipe cache, wipe dalvic, wipe battery stats (both under advanced) ), go to install zip from SD card, choose zip, install it, reboot and enjoy
But as it seems, that your not that familiar with modding, flashing and so on, better first read some on those topics, in order to get the needed knowledge
Click to expand...
Click to collapse
yes,i don't know why
toilet_duck said:
I've already attempted to install CM7. My first post explains this. Let's review the situation:
* Rooted
* Installed CWM
* Attempted to install CM7, got status 1 error.
* Attempted to wipe phone, but it only boots into CWM.
I'm not sure what the problem is. I want to restore the phone to stock, and install CM7.
Anyone got a solution? If I can provide any other info that would be helpful, let me know.
Click to expand...
Click to collapse
where did you flash CM7 from ?
Rom Manager ? or Recovery ?
it boots into CWM,then, can you wipe it from CWM ?
Did u follow all my steps? Download (maybe try a different nightly version), Boot to CWM, Wipe EVERYTHING, as mentioned above, flash zip and everything should be fine
I've tried flashing cm7 both via rom manager, and directly in recovery. Same error (status 1).
It seems I am somehow unclear about my problem. Here are some images:
If I try to factory reset via Settings, Privacy, Factory Data Reset, the phone restarts, and boots into ClockworkRecovery Mod.
https://imgur.com/pFTh6
It will not boot to the Android OS until I perform "wipe cache partition".
If I try to flash cm7 (I've try five different nightlies) via CWM, I get this.
https://imgur.com/BNMsp
Again, I have full root. I have CWM installed. I have tried several versions of cm7, checked the MD5 on each one.
What the hell is going on here?
agent205 said:
yes,i don't know why
where did you flash CM7 from ?
Rom Manager ? or Recovery ?
it boots into CWM,then, can you wipe it from CWM ?
Click to expand...
Click to collapse
I've performed a full wipe from CWM, yes. I still get the same error.
Update ur cwm... u have version 3.x i think 4 or 5 should be normal... so go to rom manager, select install cwm and install latest version. It might also be, that ur phone isnt compatible with cm.
Is it really p970, or is it maquee, or p970h? Check it pls ;-)
Sent from my LG-P970 using Tapatalk
N00BY0815 said:
Update ur cwm... u have version 3.x i think 4 or 5 should be normal... so go to rom manager, select install cwm and install latest version. It might also be, that ur phone isnt compatible with cm.
Is it really p970, or is it maquee, or p970h? Check it pls ;-)
Sent from my LG-P970 using Tapatalk
Click to expand...
Click to collapse
If I go to Settings, About Phone, it is listed as Model # LG-LS855.
If I go to ROM Manager and select "Flash ClockworkMod Recovery", it detects the phone as a "LG-LS855". Then it throws up an error that says:
"LG-LS855 does not have any officially supported ClockworkMod Recovery yet. Have you installed a ClockworkMod based recovery manually?"
To which i can answer yes, or no.
So, how should I go about updating my CWM if Rom Manager tells me it isn't officially supported?
Just checked and my version is v5.0.2.6
Edit
I just checked your pics and it seems you have lg marquee and there are no nightlies availiable yet...
Check here:
http://forum.xda-developers.com/showthread.php?p=22062280
Maybe google lg marquee cm7 and see if you can find a port... otherwise ur bound to stock rom i guess...
Sent from my LG-P970 using Tapatalk
N00BY0815 said:
Just checked and my version is v5.0.2.6
Edit
I just checked your pics and it seems you have lg marquee and there are no nightlies availiable yet...
Check here:
http://forum.xda-developers.com/showthread.php?p=22062280
Maybe google lg marquee cm7 and see if you can find a port... otherwise ur bound to stock rom i guess...
Sent from my LG-P970 using Tapatalk
Click to expand...
Click to collapse
Interesting... Thanks for your help.
So since I have a Marquee, I'd like to remove the CWM I have installed and just stay on stock with root.
How do I remove CWM?
The best probably is, to simply flash a fresh version of your software via B2C, then noone will see it has ever been rooted.
I'm trying to install clockworkmod through odin and I cant find any downloads that work for the galaxy note t879. Anyone recently added cwm or twrp that works? Where did you get it from?
If you Google "twrp sgh-t879" the first result will be the twrp page for this phone. There will be three different ways to install listed. As well as download links for the files.
srpanadero said:
If you Google "twrp sgh-t879" the first result will be the twrp page for this phone. There will be three different ways to install listed. As well as download links for the files.
Click to expand...
Click to collapse
Thanks! I got twrp to work then I flashed cyanogenmod 10.1 and rebooted and now all it will do is show the cyanogenmod logo on the screen ??any suggestions?
Well dunno. How did you flash? Did you flash gapps as well? Did you wipe cache and dalvik after flashing but before rebooting?
It can take a loong time for the first reboot going from stock to custom ROM iirc.
usually takes about 5 mins to load and settle...I just installed 10.1 20130816-NIGHTLY-quincytmo on my note and so far everything works good...no reboots yet...this is what I did in TWRP...first I backed up my current rom (for safety) then I went to wipe and wiped system/factory reset/cache/delvik in that order....then I went to install so I flashed (in this order) darkside super swipe went to add zip and added the nightly rom then added gapps for 10.1 CM in CM website labeled gapps-jb-20130812-signed.zip and added zip file flash counter reset and install....after all that installs wipe cache/delvik and rebooted...I let it settle for about 5 to 10 mins and went on my way....idk if other guys do it differently but for me that worked....do some more research but try it like this...hope this helps....
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
Was flashing my friends i9305 and now it wont boot any rom I flash... always gets stuck on the first boot screen until I take out battery.
I flashed CWM 6.0.4.7 using odin.
I have tried flashing several roms (CM 11, CM 10.1, PACman 4.3)... Each one will flash with no errors, then when I reboot after correct GAPPS it just gets stuck on the loading screen forever and won't boot up into ROM.
Wipe data/cache, wipe dalvik, wipe system > Install rom from zip, install GAPPS from zip > reboot (even here I wipe system/data/cache - still doesnt work).
Any ideas on why it won't load up the roms....
only4dank said:
Was flashing my friends i9305 and now it wont boot any rom I flash... always gets stuck on the first boot screen until I take out battery.
I flashed CWM 6.0.4.7 using odin.
I have tried flashing several roms (CM 11, CM 10.1, PACman 4.3)... Each one will flash with no errors, then when I reboot after correct GAPPS it just gets stuck on the loading screen forever and won't boot up into ROM.
Wipe data/cache, wipe dalvik, wipe system > Install rom from zip, install GAPPS from zip > reboot (even here I wipe system/data/cache - still doesnt work).
Any ideas on why it won't load up the roms....
Click to expand...
Click to collapse
I have same problem here.. no one help me... I dont know I was in i9000 thread and lot of time I got answers.. miss that thread so much .
1Ishara said:
I have same problem here.. no one help me... I dont know I was in i9000 thread and lot of time I got answers.. miss that thread so much .
Click to expand...
Click to collapse
Well I figured it out... since it was never flashed or anything before (from stock rom)... I just went into the Mounts and Storage menu, and formated /cache /system /data manually and it finally worked.
Hope that helps