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!
Related
Hi,
I flashed my GT-i9000 (Firmware was Gingerbread BUJVY) using CF Root (CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.tar) through ODIN.
All worked fine and I was able to boot into Recovery using the regular Volume Up+Home+Power.
I then proceeded to flash CM10 nightly (23/9/12) (from my external Micro SD card) by wiping data, wiping cache and wiping Dalvik Cache.
I then navigated to the zip file for CM10 and run it. It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4).
From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
I'm hoping someone may be able to help, I would really appreciate it!
TIA!
zim_zimmer said:
It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4). From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
Click to expand...
Click to collapse
Do you know what version is your Firmware? is it 2.3.3 or 2.3.6?, IF its 2.3.3 your boot loader needs to be updated to 2.3.6 for you use , If its already 2.3.6, than you should be able to use CWM recovery to reinstall the CM 10 from your SD card. (But by doing this you may lose your IMEI as you should do a progressive upgrade , like from GB 2.3.6>ICS CM9>JB) or flash a semaphore JB kernel
Easiest way out would be for you to use a JVU ROM to recover, safe your EFS, than proceed to CM 9 and than to CM 10...
you can get a rescue kit or JVU+CFRoot from My Android Collections and or a solution from My Android Solutions
Hi there,
I was on Gingerbread 2.3.6 before I ran the above.
I have gotten a bit further than the above. I managed to mount the phone as a USB whilst in CWM and put the CM10 zip file on the actual phone memory. I then wiped data/cache/dalvik and rerun the install. It installed but didn’t reboot itself, so I rebooted manually and then the Cyanogenmod logo started up and it booted into CM10. Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Rooting this phone and flashing ROMS is more difficult than my Galaxy S3!!
Cheers
zim_zimmer said:
Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Click to expand...
Click to collapse
Since you are already on CM 10, you need to solve your home button problem, try doing a wipe in recovery, if fails, flash again the CM 10
Hmmm, it didn’t work.
What I’ve done since though is try to flash another ROM.
I’ve flashed the ‘xBean’ ROM with success, however, I did encounter the exact same problem when flashing the ROM as mentioned above
I wiped data/cache/dalvik and run the install for xBean. It stopped after the first install attempt and rebooted itself, however it just brought me back to the CWM screen (although this time different from the CM CWM).
So I wiped data/cache/dalvik, then run the install again. This time it went through the full install but again (like with CM) it didn’t rebooted automatically. I manually rebooted and then the xBean logo came up and booted in.
This time the home button is working, and pretty much everything else is too by the looks of it. So far so good!
I guess my question would be, why does the ‘ghost installs’ keep happening???
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, device is rooted, and clockworkmod recovery 6.0.4.5 installed.
ROM is JB, the official update from LG. Today device reported there is an update to the installed firmware.
I rebooted in CM recovery, took a nandroid backup, booted, and accepted to download the official update to my official JB rom. After downloading I was asked to reboot (in order to install), and the phone reboots to the CM recovery.
From there I don't know what to do. I have tried rebooting, but again find myself to the CM recovery. I have tried "reboot to bootloader" and get stuck at the LG boot screen logo with the message "Now Ready!" in tiny white letters on the upper left corner.
I would try "install zip" but I don't know where the downloaded update is (if it even is in an acceptable zip format)
Phone isn't bricked, I guess I can always restore from the recently taken backup, but I really would like to know if there is a way to install this update.
Thank you
http://forum.xda-developers.com/showthread.php?p=50645445
Could you please please please try to search the next time I've seen this question for probably 3-4 times
Sent from my LG-P880 using xda app-developers app
you can't ota over unlocked bl/cwm, you must flash update manually
moneyvirus said:
http://forum.xda-developers.com/showthread.php?p=50645445
Could you please please please try to search the next time I've seen this question for probably 3-4 times
Click to expand...
Click to collapse
You're right, but you know, sometimes you just can't nail the right keywords especially if its not your native language. I searched, but obviously not good enough.
Rudjgaard said:
you can't ota over unlocked bl/cwm, you must flash update manually
Click to expand...
Click to collapse
Sadly, this seems to be the case.. bummer.
Thanks everyone
Not even my nandroid backup can help me get to where I was before? So much for nandroid being the ultimate backup, a "snapshot image" of the device...
So, what if, I use CM recovery to install a custom rom, and then restore from my nandroid backup (being the official JB) ?
Flash with kdz flasher original ROM then flash cwm you can put back your backup. I think the problem starts that the update pushes something in the boot section that is expecting an other (read original) recovery . when you installed cwm it boots up cwm so that's why an nandroid backup doesn't work I think ( to be honest I'm not 100% sure this is correct)
Sent from my LG-P880 using xda app-developers app
I can't even flash cyanogenmod???
I downloaded latest stable build, copied it to sd card, selected it from the CM recovery ("install zip"), installed fine, reboot, still stuck at CM recovery!!!
What gives?
EPa said:
I can't even flash cyanogenmod???
I downloaded latest stable build, copied it to sd card, selected it from the CM recovery ("install zip"), installed fine, reboot, still stuck at CM recovery!!!
What gives?
Click to expand...
Click to collapse
Have you yet followed the advice and installed the KDZ?
Trying to avoid that, as it seems too much work for a phone that was working fine, and stuck to recovery due to some silly boot flag or something.
Saw it as a chance to try cyanogenmod. But it seems having CM recovery and the cyanogenmod rom on the sd card won't cut it! Talk about failure..
EPa said:
Trying to avoid that, as it seems too much work for a phone that was working fine, and stuck to recovery due to some silly boot flag or something.
Saw it as a chance to try cyanogenmod. But it seems having CM recovery and the cyanogenmod rom on the sd card won't cut it! Talk about failure..
Click to expand...
Click to collapse
I don't think you will have a choice. If you created the nandroid backup on your SD card then you aren't going to lose it, so just flash the KDZ, root again and install your backup, or accept the LG update and rebuild all your software again.
Yes, one thing is for sure. I had to install the KDZ to be able to proceed with anything..
It's just funny having a working CWM recovery and a cyanogen rom on the device and after flashing it, still not having a device that boots. A "recovery"/flash tool, should be able to "recover" from such a situation..
EPa said:
Yes, one thing is for sure. I had to install the KDZ to be able to proceed with anything..
It's just funny having a working CWM recovery and a cyanogen rom on the device and after flashing it, still not having a device that boots. A "recovery"/flash tool, should be able to "recover" from such a situation..
Click to expand...
Click to collapse
You can't blame the recovery. It is clearly stated many, many times that you should never attempt an official OTA update with a non-standard (rooted or recovery installed) device. On other devices you could even hard-brick AFAIK, so consider yourself lucky that you only had to reflash a KDZ and start again.
For restoring stock rom use this: http://forum.xda-developers.com/showthread.php?t=2682146 I can confirm it works and it is (very) easy.
Yes that's what I used and I also confirm it works and is very easy.
I'm trying to resurrect my I897 Captivate. I put it in the drawer a couple of years ago with Glitch kernel and AOKP ICS on it. My wife destroyed her Skyrocket (S2) and she needs a phone to use as a stand-in for a couple of months.
I wiped it, no nandroid backup since I had no plans to use any of the data on it, and began trying to install Cyanogenmod. I was planning to use the recent M5 snapshot of CM11 but am ok with going to 10.2.1 stable if 11M5 doesn't work.
However, I just can't get it to boot. It will go into recovery mode fine (in fact, it boots to recovery even when no buttons are pressed).
I went back, wiped everything, formatted all partitions, and started with CM7, then CM9, then CM10.2.1 to get the partition scheme updated and just to be sure it wasn't CM11M5. However none of those change the issue. It just refuses to boot anything but recovery.
I've repeatedly done wipes and factory resets, including going back and formatting the partitions. I've tried the "install CM twice" trick. The phone just does not want to boot the images.
The install processes seem to go fine. No errors reported during .zip install.
I went through many different pages that are meant to break a recovery loop, most of which just have you do the basic reset and reboot, but so far have found no way to break the cycle.
Any ideas?
jahfry said:
I'm trying to resurrect my I897 Captivate. I put it in the drawer a couple of years ago with Glitch kernel and AOKP ICS on it. My wife destroyed her Skyrocket (S2) and she needs a phone to use as a stand-in for a couple of months.
I wiped it, no nandroid backup since I had no plans to use any of the data on it, and began trying to install Cyanogenmod. I was planning to use the recent M5 snapshot of CM11 but am ok with going to 10.2.1 stable if 11M5 doesn't work.
However, I just can't get it to boot. It will go into recovery mode fine (in fact, it boots to recovery even when no buttons are pressed).
I went back, wiped everything, formatted all partitions, and started with CM7, then CM9, then CM10.2.1 to get the partition scheme updated and just to be sure it wasn't CM11M5. However none of those change the issue. It just refuses to boot anything but recovery.
I've repeatedly done wipes and factory resets, including going back and formatting the partitions. I've tried the "install CM twice" trick. The phone just does not want to boot the images.
The install processes seem to go fine. No errors reported during .zip install.
I went through many different pages that are meant to break a recovery loop, most of which just have you do the basic reset and reboot, but so far have found no way to break the cycle.
Any ideas?
Click to expand...
Click to collapse
my advice is, go to stock GB, then flash ICS, flash a KitKat kernel, reboot recovery and then flash CM 11..
hope this works for you!
Yeah that was my next plan, already have the stock ROM downloaded. Will report back. Was just hoping there was a known issue that I could fix without reverting. Not a big deal Thanks.
Stock Rom
jahfry said:
Yeah that was my next plan, already have the stock ROM downloaded. Will report back. Was just hoping there was a known issue that I could fix without reverting. Not a big deal Thanks.
Click to expand...
Click to collapse
Hello jahfry! Glad to hear you got the stock ROM. Would you mind telling me where you got it from? All the links I've found here are dead… I am in a similar situation as you - managed to get a custom rom going but have lost all trace of EFS folder/ nv_data.bin file…. Need to go back to stock to start again… Any help appreciated!
asianlight said:
Hello jahfry! Glad to hear you got the stock ROM. Would you mind telling me where you got it from? All the links I've found here are dead… I am in a similar situation as you - managed to get a custom rom going but have lost all trace of EFS folder/ nv_data.bin file…. Need to go back to stock to start again… Any help appreciated!
Click to expand...
Click to collapse
Stickied threads: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
Search goes a long way
Okay so, I'm not exactly sure if this is the right place but I'll ask here anyway.
I took my old i9000 out of the closet and started playing around with it as I want to use it on my upcoming travel. To make long story short, I used to have a custom ROM on the phone all those years ago, but I am by no means an expert on the subject.
So what I have done so far today:
1. Returned the phone to stock ROM with Odin (XWJW1 or something, most recent anyway)
2. Rooted with Semaphore 2.7.4.
3. Installed Rom Manager and Superuser to check for CWM updates (which caused some sort of a verification error when I tried to boot to CWM through the app).
4. Downloaded the appopriate Slimkat and gapps and moved them into the internal storage.
But after the last step (and after wipe cache, format system etc) when I try to install the ROM, the bar on the screen progresses only slightly and after "Installing update..." it crashes (just goes black without any error messages) and gets stuck with just "Semaphore" on the screen.
I wish to update the phone to Slimkat 4.4.2. But what causes this problem, any ideas? Am I doing something wrong? If anyone can give any help that would be much appreciated!
PS. If I wanted to install for example Philz recovery, how am I supposed to do it when the file is .img?
Anyone?
I guess no one is using this phone anymore?
Yes, you are doing many things bit wrong.... (and many people use this phone still). I hope following will help you:
*recovery and kernel are sharing the same partition on the i9000 what means that you can't flash recovery separately
*make sure to backup your IMEI if still there
*flash first CM10.2 to get updated recovery for KitKat roms and to resize the system and data partitions to those used by all KitKat roms and reboot once into the system. You will need to flash trice to make it work (1. only warning of resizing to come and data lost- and status 7 abort, 2. only recovery update, 3. successful flashing)
*flash SlimKat and latest SlimGapps (addons) for 4.4.4
*PhilZ touch screen isn't yet working well on the i9000 but if you flash Mackay KK kernel, you can get beautiful TWRP touch recovery
tetakpatalked from Nexus 7 flo