Related
Hello, I just got a Rooted Verizon Galaxy Tab and I don't know how to flash clockworkmod recovery? I found what looks to be a great ICS rom at rootzwiki. However it need Clockworkmod recovery. Any ideas? All the links I find are dead, or no longer recommended. If you could point me in the right direction I would appreciate it. Thanks.
P.S. I looked at Verizon Tab Bootstrapper on the market but there are lots of people who experienced serious problems because of it. I'm not sure if they did it wrong or not. There is this one reviewer that says you need to be running the Original stock rom, maybe he means froyo? I can't seem to locate the original Froyo rom. Thanks.
you could start with
http://forum.xda-developers.com/showthread.php?t=1275031
that gets CWM 4.0 installed.
priyana said:
you could start with
http://forum.xda-developers.com/showthread.php?t=1275031
that gets CWM 4.0 installed.
Click to expand...
Click to collapse
That thread is for the Sprint version, would it work for the Verizon?
Also, I have a rooted stock rom installed. (or so I was told by the guy I got it from) But root checker basic says I don't have proper root access. Is that normal? Should I flash the absolute stock rom with Heimdall and do a superoneclick, rooting it myself?
Thanks.
I have a GSM device.
But I think verizon and sprint the same.
read his post. I don't think there is a superoneclick involved
If you read post #1, #2, then #3 you end up with root + CWM 4.0
priyana said:
I have a GSM device.
But I think verizon and sprint the same.
read his post. I don't think there is a superoneclick involved
If you read post #1, #2, then #3 you end up with root + CWM 4.0
Click to expand...
Click to collapse
Edit: I JUST DID IT!!! THANK YOU!!! I chanced it and used the ODIN I mention below to flash the custom kernel/custom recovery. I'm now doing a backup of the system! Next I'll flash the ICS Rom I found. THANKS!!! Also, I just realized I passed my 10th post! So Now I can post in the development threads! Thanks for that to!
Okay, also I can't seem to find ODIN for the Verizon version. I found ODIN3 v1.7 for the GT-P1000. Would that work for the Verizon version?
And he says to flash the Kernel with any EF17 installation? I don't understand. Thanks for your help.
Just follow the step. Basically, Odin flash the stock EF17 rom.
Then Odin flash the kernel that has CWM.
The Galaxy Tab doesn't have separate recovery.
Its recovery is included in the kernel. that is why you flash a kernel instead, to get CWM recovery.
And naturally you can't flash any kernel that has cwm, it has to be the one that is the same as the base kernel you already have.
BTW, his package has Odin included. you just really have to read carefully
Stock Odin/Heimdall Files: Stock EF17 Tar
Odin: Odin3_v1.7_SPH-P100 is included in tar package.
Heimdall: Homepage
The zip file below contains Odin3 v1.7, my .pit file, and full EF17 tar file including boot loaders and modem! There are no modifications or changes at all to the tar. Use this file to go back to a completely unrooted stock state. (Like you just did an OTA update)
Download stock-ef17-odin-tar-pkg.zip (Mirror) md5: b3f81ce371c3284882552cb22a38c29d
priyana said:
Just follow the step. Basically, Odin flash the stock EF17 rom.
Then Odin flash the kernel that has CWM.
The Galaxy Tab doesn't have separate recovery.
Its recovery is included in the kernel. that is why you flash a kernel instead, to get CWM recovery.
And naturally you can't flash any kernel that has cwm, it has to be the one that is the same as the base kernel you already have.
BTW, his package has Odin included. you just really have to read carefully
Stock Odin/Heimdall Files: Stock EF17 Tar
Odin: Odin3_v1.7_SPH-P100 is included in tar package.
Heimdall: Homepage
The zip file below contains Odin3 v1.7, my .pit file, and full EF17 tar file including boot loaders and modem! There are no modifications or changes at all to the tar. Use this file to go back to a completely unrooted stock state. (Like you just did an OTA update)
Download stock-ef17-odin-tar-pkg.zip (Mirror) md5: b3f81ce371c3284882552cb22a38c29d
Click to expand...
Click to collapse
Well, I flashed the custom kernel in odin and my System is still working. Although for some reason the computer wouldn't recognise the MicroSD so I had to use a reader. I rebooted into recovery and made a backup, then I wiped EVERYTHING (except SD card) and tried installing this: http://rootzwiki.com/topic/11697-rom-cdma-aosp-ics-cm9-build101-0418/ And its giving me:
Installing update...
assert failed: getprop("ro.product.device") == "galaxytab7c" | | getprop("ro.build.product") ==
"galaxytab7c" | | getprop("ro.product.device") == "plc" | | getprop("ro.build.product") ==
"plc" | | getprop("ro.product.device") == "SCH-I800" | | getprop("ro.build.product") == "
SCH-I800" | | getprop("ro.product.device") == "SPH-P100" | | getprop("ro.build.product") =
= "SPH-P100" | | getprop("ro.product.device") == "vzwtab" | | getprop("ro.build.product")
== "vzwtab
E:Error in /sdcard/(name of file).zip
(Status 7)
Installation aborted.
Any ideas? I'm doing a system restore now until I can figure it out. Someone on the thread did say we should be using CWM 5.3. I'm using 4. Where can I get 5.3?
common case for CWM 4.0 which if not mistaken can't do the assert
I don't know what you need to do to upgrade to CWM 5.0 first,
It is the best course of action if you can do it.
but there is other way,
can you use 7zip to open the zip, drag out from deep within the META-INF
there is an updater script
using wordpad, (not notepad) remove the part where it does the assert (the first few lines),
and drag the script back to the zip and flash it.
the end result, you get your cwm upgraded anyway because of the CM9/10
priyana said:
common case for CWM 4.0 which if not mistaken can't do the assert
I don't know what you need to do to upgrade to CWM 5.0 first,
It is the best course of action if you can do it.
but there is other way,
can you use 7zip to open the zip, drag out from deep within the META-INF
there is an updater script
using wordpad, (not notepad) remove the part where it does the assert (the first few lines),
and drag the script back to the zip and flash it.
the end result, you get your cwm upgraded anyway because of the CM9/10
Click to expand...
Click to collapse
Okay, first I'll try the newer official CM9.1 I found. And see if that works. If it doesn't then i'll try what you suggested. Thanks!
Electriccars said:
Okay, first I'll try the newer official CM9.1 I found. And see if that works. If it doesn't then i'll try what you suggested. Thanks!
Click to expand...
Click to collapse
Actually I am quite sure the latest cm gives the same error because you only have cwm 4
Sent from my GT-I9300 using xda app-developers app
priyana said:
Actually I am quite sure the latest cm gives the same error because you only have cwm 4
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yeah it did. DOH! lol. Funny because I looked into the updater script of CM9.1 and didn't see the asserts lines. but I missed them. I am rezipping the file with the edited script and lets see what happens!
My reason of suggesting drag out and drag in is because sometimes rezipping screwed the zip in windows.
Windows is not Posix compliant, so if the filenames within are case sensitive, unzip and rezipping screwed it up.
Sent from my GT-I9300 using xda app-developers app
priyana said:
My reason of suggesting drag out and drag in is because sometimes rezipping screwed the zip in windows.
Windows is not Posix compliant, so if the filenames within are case sensitive, unzip and rezipping screwed it up.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yeah. I only removed the specific file, changed it, deleted the old one, and inserted the edited one. I'm flashing it now...
Electriccars said:
Yeah. I only removed the specific file, changed it, deleted the old one, and inserted the edited one. I'm flashing it now...
Click to expand...
Click to collapse
Shoot, now it says:
E:Error in /sdcard/cm-9.1.0p1c.zip
(Status 6)
Installation aborted.
Any ideas?
Edit: Just found: http://forum.xda-developers.com/showthread.php?t=1585619
It says how to flash CWM 5. and flash ICS let me try that.
Did you use notepad?
The file is in Unix text, need wordpad.
Sent from my GT-I9300 using xda app-developers app
priyana said:
Did you use notepad?
The file is in Unix text, need wordpad.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
No I used wordpad. But no matter. I now have CM9.1 stable installed!!! With CWM 6! woohoo! Thank SO much for your help!
This is my first guide so if I left something out please tell me.
I do not take any credit for any of this work. I just read in a thread how another user did it. I tried it and it worked.
This isn't nessassarily the right way to do this but this is what I did, and all don't from my nexus 7.
I've only tried it on slimkat. I'm going to be testing more ROMs today.
Thanks to
Legolas93
Slimroms.net
ryanrudolf
Things you will need:
A file explorer (I use solid explorer)
Zip app to extract and compress ( included in solid explorer)
Modified TWRP recovery from this post.
1. Download the latest weekly build of Slimkat. http://slimroms.net and extract the zip file to a folder.
2. Next either download the last build from legolass of slimkat here and extract it to its own folder or download attached boot.IMG and updater-script. (Only 2 files that I found that needed to be updated.)
3. If you just decided to download the attached files, extract the archive and inside you will find 2 files. Copy boot.IMG into the root of latest slimkat that you already extracted, overwriting when prompted. Next copy updater-script to./META-INF/Com/Google/android. overwriting when prompted.
If you didn't download the files from the post and choose to do this manually. Just follow above directions and get the files from the latest slimkat f2fs. Same directories.
4. Now its time to zip up the archive so we can flash it. Zip the files so the root of the archive is the same as the one you extracted. Meta-inf, system, Boot.IMG and file_contexts.
5. Flash in twrp.
B]List of working roms.[/B]
Liquid Smooth
Slimkat
CyanogenMod (with method below)
Tested but not fully working.
Paranoid
Method for CM By ryanrudolf
CM Nightly with All-F2FS (Unofficial Method)
1. download latest CM nightly (here is link for CM Nightly already modified for ALL-F2FS http://d-h.st/9By )
2. download faux025 kernel.zip
3. open CM nightly zipfile, extract the boot.img
4. open faux025 zipfile, extract the zImage
5. unpack the boot.img in step3
6. replace the zImage in step5 with faux025 zImage (step4)
7. replace fstab.grouper with this one -
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system f2fs ro,noatime,nosuid,nodev,discard,nodiratime,inline_ xattr,errors=recover wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xat tr,errors=recover wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xat tr,errors=recover wait,nonremovable,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/tegra-ehci auto vfat defaults voldmanaged=usbdisk:auto
8. repack boot.img. place it back in the CM nightly zipfile
9. on the CM nightly zipfile, edit updater script and look for these 3 lines -
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
replace it with
run_program("/sbin/busybox", "mount", "/system");
and these lines too -
format("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
replace with -
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/APP");
run_program("/sbin/busybox", "mount", "/system");
10. save the updater script and put it back to the zipfile. CM nightly zipfile is complete and ready for flashing.
11. flash modded twrp with f2fs support. also download the formatpartitions.zip (credits to legolas http://forum.xda-developers.com/show....php?t=2678140)
12. boot to the modified twrp, flash the formatpartitions.zip. reboot back to recovery
13. flash the modified CM nightly zipfile
14. flash gapps.zip (i use slimroms minimal gapps)
15. Wipe > Format Data > yes
16. reboot
17. enjoy!
NOTE - everything is CM ramdisk, except for the fstab.grouper. If I use the original CM fstab.grouper and just edit to f2fs, it does not work.
Credits -
Legolas for the modified TWRP with F2FS
Faux for faux025 kernel with F2FS support
CM for the CM Nightlies
SlimRoms for the minimal gapps
[
Thanks again. I will give this a try very soon. Glad someone figured out what these devs are doing. I hope others will come in here and share even more information. :good:
EDIT: So, you managed to do all of this on your device? Wow nice work.
SkOrPn said:
Thanks again. I will give this a try very soon. Glad someone figured out what these devs are doing. I hope others will come in here and share even more information. :good:
EDIT: So, you managed to do all of this on your device? Wow nice work.
Click to expand...
Click to collapse
Ryanrudolf in the all f2fs slimkat thread said what files he changed. I just followed his direction.
And yes I did all this from my n7.
No problem I'm glad I could contribute.
Sent from my Nexus 7 using XDA Premium HD app
Any ROMs u want me to test? I'm about to try paranoid 4.2 beta 2 (latest)
For all the other ROMs I'm going to remove the slimroms text that scrolls in twrp when installing. I'll update the op with unbranded updater file so they can try it on other ROMs and not get confused lol.
Sent from my Nexus 7 using XDA Premium HD app
ronedogg said:
Any ROMs u want me to test? I'm about to try paranoid 4.2 beta 2 (latest)
For all the other ROMs I'm going to remove the slimroms text that scrolls in twrp when installing. I'll update the op with unbranded updater file so they can try it on other ROMs and not get confused lol.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah that would have been great, but the dev on my preferred ROM is already working himself to figure it out. I'm probably going to be testing his latest build here soon. I just want to know what you guys did so that next week, when I want to try another ROM I will have a larger menu to choose from
If you want to mess around and test several ROM's I suggest you try AOSPAL SaberDroid in your list. There will be a new build here soon, maybe today I think.
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build. (i just replaced some rows in the updater-script and replaced boot.img in the zip file)
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue.
carlo93 said:
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build.
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue (i replaced boot.img with the one you attached).
Click to expand...
Click to collapse
That is a known issue with CM, not this mod. I get that same FC when I use CM11. Its not there on Slim, or Omni or AOSPAL, using the same mod.
carlo93 said:
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build.
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue (i replaced boot.img with the one you attached).
Click to expand...
Click to collapse
Hmmm. I tried paranoid and got the same result but was keyboard throwing up error....
In the all f2fs slimkat thread another user said he tried cyanogen as well and got same error. Maybe this is just for slimkat, I thought we might have gotten lucky.
I'm going to try to compare the updater scripts for cm and pa with the slimkat script. See if there is something obvious we can change.
Actually I take that back, I never tried straight PA, just modified versions of it. I only get that message with CM11.
SkOrPn said:
Actually I take that back, I never tried straight PA, just modified versions of it. I only get that message with CM11.
Click to expand...
Click to collapse
looking at comparing files now.
in cm latest nightly there is a line of code refering to f2fs already.
symlink("../bin/fsck.f2fs", "/system/bin/dump.f2fs");
not sure what that is.
im gonna upload a updated version of the script for cm. Using notepad ++ and compare plugin, should have something shortly that i can test.
Just tried this with the latest liquid smooth build, works fine so far. no fc and running really smoothly
PatrickMac said:
Just tried this with the latest liquid smooth build, works fine so far. no fc and running really smoothly
Click to expand...
Click to collapse
sweet!. im going to update the OP with working roms.
Thanks for testing
Just a suggestion, I would rename the thread to
[Guide] Converting ANY ROM to All-F2FS Partitions - Working ROM list Included!
SkOrPn said:
Just a suggestion, I would rename the thread to
[Guide] Converting ANY ROM to All-F2FS Partitions - Working ROM list Included!
Click to expand...
Click to collapse
it wont let me rename the title
2 failed attempts at editing the updater script on paranoid.
onto 3rd attempt.......
after some testing I got paranoid to install. but when i install gapps package all kinds of errors get thrown up....
waaay over my head there. ill try again later tonight see what I can come up with. i might be close... I might be waaay off.
maybe someone will see this thread and give me some pointers.
ronedogg said:
after some testing I got paranoid to install. but when i install gapps package all kinds of errors get thrown up....
waaay over my head there. ill try again later tonight see what I can come up with. i might be close... I might be waaay off.
maybe someone will see this thread and give me some pointers.
Click to expand...
Click to collapse
Haha, that's how I felt the weekend before last when I spent 20 straight hours trying to figure this out.
I have seen a few people ask for this so i'm going to try and edit the SlimRoms SlimBean 4.3.1 version of there rom to see if i can get this working on 4.3.1 Jelly Bean Roms.
I have already edited the fstab file in the SlimBean 4.3.1 kernel/boot.img and have already edited the updater script now just doing a backup of important stuff and going to give it a try
CptKlink said:
I have seen a few people ask for this so i'm going to try and edit the SlimRoms SlimBean 4.3.1 version of there rom to see if i can get this working on 4.3.1 Jelly Bean Roms.
I have already edited the fstab file in the SlimBean 4.3.1 kernel/boot.img and have already edited the updater script now just doing a backup of important stuff and going to give it a try
Click to expand...
Click to collapse
Good luck. :good:
carlo93 said:
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build. (i just replaced some rows in the updater-script and replaced boot.img in the zip file)
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue.
Click to expand...
Click to collapse
same i got that error too on the latest nightly of CM.
will try more on weekend
Sent from my C6503 using Tapatalk
I have a problem, i install [ROM][UB][4.4.2][T/TX] Carbon Rom KK Unofficial {built from source} since recovery (T4.3_PhilZCWM_6.0.4.7_LB_v1.7)
and when it is installing, put ERROR: (Status 7)
Download zip again, might be broken.
Sent from my Xperia V using Tapatalk.
done
WhiteNeo said:
Download zip again, might be broken.
Sent from my Xperia V using Tapatalk.
Click to expand...
Click to collapse
i have it done! and it follows like before.
Takezo8 said:
I have a problem, i install [ROM][UB][4.4.2][T/TX] Carbon Rom KK Unofficial {built from source} since recovery (T4.3_PhilZCWM_6.0.4.7_LB_v1.7)
and when it is installing, put ERROR: (Status 7)
Click to expand...
Click to collapse
This is most likely due to you trying to install the build that isn't for your device. What phone do you have?
Some developers like to add a command at the beginning of the "updater-script" file that checks if your phone matches the file you're trying to install, and generally it outputs a messages. In some cases it doesn't, as is the case with several of the custom ROMs I've found here.
In my case, before flashing anything I always delete the entire first line with the "assert(getprop)..." statement, because sometimes the conditions specified in that command don't match what is specified in the ROM I'm on in the build.prop, especially when coming from Stock ROM, I think. I've done this with every ROM I've flashed, including the Carbon ROM, and deleting this line lets the installation continue.
On the other hand, this is a safeguard to prevent people from installing a ROM that is not for their phone, since there tend to be people who flash ROMs without having a clue of what they are doing or what the risks might be if something were to go wrong. So I'd make sure you have the right build for your phone, if it is, use 7zip to extract the updater-script file, delete that line, add it back with 7zip, reflash ROM.
I had the same problem. It has one solution change your recovery try with clockworkmod or philz touch
I am trying to install CM11 EMMC to my nook HD+ with stock rom on it. The instruction I followed is here
http://forum.xda-developers.com/showthread.php?t=2600572
1.Download the initial sdcard image
2.ungzip and write to sdcard using dd (winimage or whatever for those stuck on Windows)
3.Instert the card into your nook and reboot
4.Flash the recovery image
5.Flash cm11 image
6.Flash whatever other extra things you need like gapps
7.remove the sdcard
8.reboot the nook
I did wipe data and cache after step 3. I finished steps 4 and 5. However, flashing gapps in step 6 failed with information of error in gapps zip file [status 6]. The gapps is downloaded from here
http://forum.xda-developers.com/showthread.php?t=2397942
I use the mini modular package. I am quite sure the gapps zip file is good since i have finished SD install with the gapps zip file. However, it failed in EMMC install. Now the nook can boot to CM11, but without any google stuff.
Any suggestion?
I'd suggest that you try a different, smaller size package (you can always add those apps not included later from the Playstore).
Also, if needed an alternate source for Gapss is http://wiki.cyanogenmod.org/w/Google_Apps, use the "small" version.
Thanks for the suggestion. Other gapps on http://forum.xda-developers.com/show....php?t=2397942 does not work. The gapps on the wiki page works, though it is for 4.4.2. I think the orginal thread on CM11 EMMC install should notice users on the possible problem.
digixmax said:
I'd suggest that you try a different, smaller size package (you can always add those apps not included later from the Playstore).
Also, if needed an alternate source for Gapss is http://wiki.cyanogenmod.org/w/Google_Apps, use the "small" version.
Click to expand...
Click to collapse
Status 6 install error
junl2000 said:
Thanks for the suggestion. Other gapps on http://forum.xda-developers.com/show....php?t=2397942 does not work. The gapps on the wiki page works, though it is for 4.4.2. I think the orginal thread on CM11 EMMC install should notice users on the possible problem.
Click to expand...
Click to collapse
I'm a total newbie to this but I think I have the same issue.... This is what I done and the results:
Used Win32imager onto 32gb Sandisk to write unpacked image of emmc-cwm-early3.1.img.gz then loaded onto card the following files:
cm-11-20141212-NIGHTLY-ovation.zip
cwm-recovery-ovation-6.zip
pa_gapps-stock-4.4.4-20141214-signed.zip
pa_gapps-modular-mini-4.4.4-20141214-signed.zip
Re-booted and did backup of stock and cleared/formatted internal card. Installed cwmrecovery images, and CM11 nightly. Tried installing to gapps stock and mini both came up with a Status 6 failed installation error .
Tried reverting to stock and couldn't recover due to error so re-installed CM and had same error. Copied off and removed restore apks to ensure enough space and tried again - still
status 6 error.
Checked to see whether script files has LF/CR but script file is dummy and the binary all seems to be in LF format. Running out of ideas as all of this is new to me.
So looks like i'm in same situation - HD+ which boots to CM but no stock googleapps.
I know it doesn't help but looks like same issue - any ideas?
grungewort said:
I'm a total newbie to this but I think I have the same issue.... This is what I done and the results:
Used Win32imager onto 32gb Sandisk to write unpacked image of emmc-cwm-early3.1.img.gz then loaded onto card the following files:
cm-11-20141212-NIGHTLY-ovation.zip
cwm-recovery-ovation-6.zip
pa_gapps-stock-4.4.4-20141214-signed.zip
pa_gapps-modular-mini-4.4.4-20141214-signed.zip
Re-booted and did backup of stock and cleared/formatted internal card. Installed cwmrecovery images, and CM11 nightly. Tried installing to gapps stock and mini both came up with a Status 6 failed installation error .
...
So looks like i'm in same situation - HD+ which boots to CM but no stock googleapps.
I know it doesn't help but looks like same issue - any ideas?
Click to expand...
Click to collapse
Did you try using the Gapps packages from http://wiki.cyanogenmod.org/w/Google_Apps? They are for CM11, the apps are a bit dated but after installation can be updated (via Google Playstore) to their most current version.
Status 6 install error solved
digixmax said:
Did you try using the Gapps packages from your CM link. They are for CM11, the apps are a bit dated but after installation can be updated (via Google Playstore) to their most current version.
Click to expand...
Click to collapse
Deleted the pa_gapps-stock-4.4.4-20141214-signed.zip file.
Downloaded the two files from your link:
gapps-kk-20140606-signed.zip
gapps-kk-20140105-signed.zip
dropped both onto the card, re-booted and installed the larger 20140606 version which installed without any error messages. Removed card and re-booted - extra apps all look in place. Will now make sure they all run OK.
Thanks very much for your help - much appreciated. Can you tell me what the difference is in the installers that make the PA versions crash or is that too long winded?
Regards
Grungewort
Hi!
I have a Nook HD+ running CM 12.1 (Android 5.1.1). The tablet is not rooted. Right now I have TWRP v2.7.1.0 installed, but would like to update to a newer version.
Installing v2.7.1.0 was a breeze. I booted into recovery mode (ClockWorkMod at the time), then flashed an Ovation TWRP ZIP file that I downloaded online. Looking for the most recent Ovation version, it seems it's only available as an IMG file. I can't find a version of TWRP more recent than v2.7.1.0 for Ovation in a ZIP format. Since the tablet is not rooted, I can't flash the newer version using Flashify or similar apps (as far as I can tell, that is) since they all require root access. And I can't flash an IMG file with v2.7.1.0, since that feature wasn't included until a later version (v2.8.5.0 I think). Therein lies the problem. I need a newer version to update, but I can't update until I have a newer version!
I've struggled with the suggested methods of installing TWRP from an IMG file, and would really like to simply flash a ZIP file (I'm already pretty good at doing that). So I've come up with a possible method that sounds too easy and too good to be true. Examining the ZIP folder for v2.7.1.0 (using Linux Archive Manager), I can see that there is a recovery IMG file and a folder labeled META-INF. If I replaced the v2.7.10 recovery IMG file with a more recent TWRP IMG file and left the META-INF file as is, would that work? Or, does the META-INF folder only support v2.7.1.0?
Thanks for your help ... and for not laughing at my possibly nutty idea
MaydayMalone said:
Hi!
I have a Nook HD+ running CM 12.1 (Android 5.1.1). The tablet is not rooted. Right now I have TWRP v2.7.1.0 installed, but would like to update to a newer version.
Installing v2.7.1.0 was a breeze. I booted into recovery mode (ClockWorkMod at the time), then flashed an Ovation TWRP ZIP file that I downloaded online. Looking for the most recent Ovation version, it seems it's only available as an IMG file. I can't find a version of TWRP more recent than v2.7.1.0 for Ovation in a ZIP format.
Click to expand...
Click to collapse
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
...
I've struggled with the suggested methods of installing TWRP from an IMG file, and would really like to simply flash a ZIP file (I'm already pretty good at doing that). So I've come up with a possible method that sounds too easy and too good to be true. Examining the ZIP folder for v2.7.1.0 (using Linux Archive Manager), I can see that there is a recovery IMG file and a folder labeled META-INF. If I replaced the v2.7.10 recovery IMG file with a more recent TWRP IMG file and left the META-INF file as is, would that work? Or, does the META-INF folder only support v2.7.1.0?
...
Click to expand...
Click to collapse
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.
digixmax said:
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.
Click to expand...
Click to collapse
Thanks for your response. You told me exactly what I needed to know.
I have viewed D. Andrei Măceș dropbox in the past, but I neglected to check it for TWRP updates (my bad). I'll keep this in mind the next time I want to explore new possibilities for my HD+.
The idea of creating my own zip was a temptation that I couldn't resist (since I was now feeling confident that I wouldn't brick my tablet, blow up Pittsburgh, or be responsible for something equally catastrophic). So, instead of downloading a zip file from the dropbox, I used Linux Archive Manager (I switched to Linux Mint some time ago to escape the more-frequent-than-I-could-bear crashes with Windows), to delete the file named recovery.img in the v2.7.1.0 zip, then inserted a recovery.img file for TWRP v3.1.1.0 in it's place. It worked perfectly, and I feel like a genius (I'm very easily impressed)!
Thanks for letting me know that my idea wasn't as dumb as I feared it might be.
digixmax said:
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.
Click to expand...
Click to collapse
Hello,
I tried using the TWRP 3.0.1.0 - ovation and 2.8.7.5. and they both receive the status 7 error:
"This package is for device: ovation ; this device is .
E: Error in /external+sd/twrp-3.0.1-0-ovation.zip
(Status 7)
Installation aborted"
I currently run on CWM Recovery 6.0.4.6, with cyanogenbootloader, lineage os 14.1. Unfortunately I cannot turn off my device (Nook HD+) no matter what, it keeps turning itself on until it empties battery (if I don't pay attention).
I keep trying to install the zips from CWM Recovery but I cannot do it.
Is there any way for me to install TWRP from CWM?
Thank you
pnkye said:
Hello,
I tried using the TWRP 3.0.1.0 - ovation and 2.8.7.5. and they both receive the status 7 error:
"This package is for device: ovation ; this device is .
E: Error in /external+sd/twrp-3.0.1-0-ovation.zip
(Status 7)
Installation aborted"
Click to expand...
Click to collapse
Did you use one of the flashable TWRP zip files from https://www.mediafire.com/#6a4rivb8kkdfu?
I currently run on CWM Recovery 6.0.4.6, with cyanogenbootloader, lineage os 14.1. Unfortunately I cannot turn off my device (Nook HD+) no matter what, it keeps turning itself on until it empties battery (if I don't pay attention).
Click to expand...
Click to collapse
Did you tried holding down the power button for 30+ sec?
Thank you for the answer.
1. The link doesn't work (https://www.mediafire.com/#6a4rivb8kkdfu?) leads me to an upload page.
2. I tried all the options I could find online. If I let it be for 1 week (I use it for reading and sometimes youtube) it turns itself on at some point and the battery goes empty. And it is so hard to turn it on again. When I plug it for charging the battery and is completely empty, the led stays green - instead of orange - for a long time and is not responsive to anything I do until it reaches 80%+ , so I let it be for 2hrs while plugged.
3. What I try to do is actually root it for overclocking or make it a little bit faster because it lags in every thing I do with it. Although in some variants of the Android which I installed over the years it used to be more responsive.
Unfortunately I cannot root it because CWM doesn't recognize the install of SuperSU zip from Lineage website. Do you have any advice on that?
Thanks
pnkye said:
...
The link doesn't work (https://www.mediafire.com/#6a4rivb8kkdfu?) leads me to an upload page.
Click to expand...
Click to collapse
Try this link: https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook+HD+
digixmax said:
Try this link: https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook+HD+
Click to expand...
Click to collapse
Thank you very much! You really helped me with this one!
I just did it! Flashed it with the cwm.flashable.twrp zip from your link!
I run now the TWRP 3.0.1-0.
I couldn't flash any higher versions (3.2.x) directly from this installed version
Anyway my booting time is faster and so far (1min time) the turning on/off procedure works normal, as it should be.
What lineage OS version is the best one for the nook hd+?
I just installed the 14.1 version from the lnos-ovation-ota-NJH47F.181223.zip found at: https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
This version, however, has landscape mode as default viewing mode and it keeps spinning here and there.
At the moment I find myself in the latest stage of my process: rooting the device so I can try and overclock it.
Trying to install the official lineage "addonsu-14.1-arm-signed.zip" , from their website (https://download.lineageos.org/extras), but it doesn't work.
I mean it installs it successfully in the TWRP recovery. It is enabled in the developer options for both Apps and Adb. But the root checker app says it is not rooted.
Is there a proper way to root it? If so could you please share a solution when you have time?
Also any ideas on how to properly overclock (make the tablet a little snappier, besides the animation scale option from dev options)?
Cheers!
pnkye said:
I just did it! Flashed it with the cwm.flashable.twrp zip from your link!
I run now the TWRP 3.0.1-0.
I couldn't flash any higher versions (3.2.x) directly from this installed version
Click to expand...
Click to collapse
There should be an option in TWRP to "flash image" you can use to directly flash .img binary of a newer TWRP version.
What lineage OS version is the best one for the nook hd+?
I just installed the 14.1 version from the lnos-ovation-ota-NJH47F.181223.zip found at: https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
This version, however, has landscape mode as default viewing mode and it keeps spinning here and there.
Click to expand...
Click to collapse
You should be able to disable auto-rotation in Settings->Display.
At the moment I find myself in the latest stage of my process: rooting the device so I can try and overclock it.
Trying to install the official lineage "addonsu-14.1-arm-signed.zip" , from their website (https://download.lineageos.org/extras), but it doesn't work.
I mean it installs it successfully in the TWRP recovery. It is enabled in the developer options for both Apps and Adb. But the root checker app says it is not rooted.
Click to expand...
Click to collapse
Try disabling and exit Settings->Developer Options, then come back and re-enable it.
digixmax said:
There should be an option in TWRP to "flash image" you can use to directly flash .img binary of a newer TWRP version.
You should be able to disable auto-rotation in Settings->Display.
Click to expand...
Click to collapse
My device is with default landscape. If I disable it it stays in landscape and never goes to portrait.
digixmax said:
Try disabling and exit Settings->Developer Options, then come back and re-enable it.
Click to expand...
Click to collapse
It still doesn't work.
Thanks for the overall guidance!