Nightlies for my Asus Infinity TF700F keep failing since December 7th. The last nightlie I have been able to install has been cm-11-2013-1207-nightly. Every nightly since then keeps failing to install, so I have to go back to December 7th and reinstall gapps 4.3 as well, because the failed install trashes the OS. Does anybody have a fix for this? Was there an updated boot-loader that occurred between then and now?
Update:
I now find out that the nightly files jumped to 190Megs (after December 7th) when they had consistently been at 170Meg prior to that. Every time I try to install a later version nightly, I get the set_metadata_recursive failure message with an error 7. Research has turned up the fact that the image size (of the more recent files) being bigger is messing me up.
midimench said:
I get the set_metadata_recursive failure message with an error 7.
Click to expand...
Click to collapse
You need to update your recovery.
I've tried that and the most current I get is cwm 6.0.3.1 for the infinity. Have you found a later version?
Sent from my Galaxy Note 3
midimench said:
I've tried that and the most current I get is cwm 6.0.3.1 for the infinity. Have you found a later version?
Click to expand...
Click to collapse
I really don't know where you were looking; you can find the latest version here on xda in the TF700 dev subforum and on the CM Wiki.
Using rom managers update screen shows version and latest version to be 6.0.3.1. I run their update and still come out the same. Even tried uninstalling and reinstalling with the same results.
Sent from my Galaxy Note 3
midimench said:
Using rom managers update screen shows version and latest version to be 6.0.3.1. I run their update and still come out the same. Even tried uninstalling and reinstalling with the same results.
Sent from my Galaxy Note 3
Click to expand...
Click to collapse
Rom Manager used to brick TF700s - I wouldn't use it personally. Switch to TWRP latest version from here and you should be OK.
Will TWRP work on the new CyanogenMod 11 .0 series (kit kat)?
Sent from my Galaxy Note 3
midimench said:
Will TWRP work on the new CyanogenMod 11 .0 series (kit kat)?
Sent from my Galaxy Note 3
Click to expand...
Click to collapse
The last version 2.6.3.2 reportedly does. But i has been released only a few days ago.
Why don't you use the official cwm provided in the CM 11 nightlies thread????
http://forum.xda-developers.com/showthread.php?t=1957660
Related
As the title says, I have been with Version 10.1.3 for some time. But as all thing, I would like to update the phone to the newly released CM 11 M9.
I am currently running ClockworkMod Recovery Version 6.0.2.3
Is it ok for me to just update the Recovery to the latest CWM, and then update to the latest CM version?
Id rather not have a borked phone.
I have been out of the loop for a while, and especially with people who are getting S3's and the bootloaders are locked, there is too much information going around not pertaining to me.
I appreciated any input.
chewyTree said:
As the title says, I have been with Version 10.1.3 for some time. But as all thing, I would like to update the phone to the newly released CM 11 M9.
I am currently running ClockworkMod Recovery Version 6.0.2.3
Is it ok for me to just update the Recovery to the latest CWM, and then update to the latest CM version?
Id rather not have a borked phone.
I have been out of the loop for a while, and especially with people who are getting S3's and the bootloaders are locked, there is too much information going around not pertaining to me.
I appreciated any input.
Click to expand...
Click to collapse
Your already on cm so you should be good to go. You can't flash custom roms as far as I know without your bootloader being unlocked. Do you remember what version of Android you were on prior to having cm installed?
And you do have the vzw S3 correct?
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Sorry, Yes I have the S3. and I got it right when the phone was released, maybe waited a month or so and then flashed. So im thinking maybe 4.2/4.3? So i know my bootloader is definitely unlocked, because i do know I unlocked it after the crack was finally available for the S3.
I was more concerned about flashing a new recovery rather than CM..cause ive heard of the newer recoveries giving people trouble.
So you think I should be good?
chewyTree said:
Sorry, Yes I have the S3. and I got it right when the phone was released, maybe waited a month or so and then flashed. So im thinking maybe 4.2/4.3? So i know my bootloader is definitely unlocked, because i do know I unlocked it after the crack was finally available for the S3.
I was more concerned about flashing a new recovery rather than CM..cause ive heard of the newer recoveries giving people trouble.
So you think I should be good?
Click to expand...
Click to collapse
Its truly up to you. I started with cwm then have used twrp and philz. The thing I like about trwp is that it's completely touch screen and doesn't rely on the buttons of the phone at all. Philz is an advanced version of CWM. It's more or less personal choice
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Hi. After I posted this message, the problem seems to be that my ROM is hopelessly old. But after following the recommendations, I still couldn't update.
I tried to install "cm-11-20141112-SNAPSHOT-M12-moto_msm8960.zip" from ClockworkMod recovery. Got this error message:
Code:
This package is for device: moto_msm8960, xt907, scorpion_mini, smq, xt926, vanquish; this device is xt925.
(Status 7)
Installation aborted.
But I was told (and the message on the CM wiki confirms it) that builds have been unified.
What should I do?
Looking for installs for xt925 specifically, the last stable is the one I have, and the few nightlies are very old as well and I doubt would solve the problem.
There is the CM12 nightly for xt925 released today, but since I'm highly dependent on my phone functioning while traveling next week and can't afford things going wrong, I'd rather avoid nightlies and experimental versions unless I have absolutely no alternative to have my phone encrypted.
Advice?
Thanks a lot.
By the way, I prefer to not make a factory reset unless it's necessary.
Is it necessary? Do I have to wipe cache? Wipe dalvik? Some sites say yes, some sites say not needed.
Is the answer different depending on whether I would be upgrading to a more recent version of CM 11 or to CM 12 nightly?
Thanks!
@taylortm Please read again what I wrote to you here: http://forum.xda-developers.com/showpost.php?p=58132610&postcount=2
You can't use moto_msm8960 CM11 builds nor xt925 CM12 build unless you update your device to stock KitKat firmware by Motorola first.
While your device is still using JellyBean bootloader/modem firmware, you can update only to moto_msm8960_jbbl CM11 builds.
That's right, I overlooked that, thank you. Was able to upgrade now.
I thought that because my Android stock was KitKat before I flashed CM11, that the bootloader would also be KK. It was a jbbl, because now it worked.
Everything seems to be working just fine, was no need to clear caches or data or anything. My compass is also now fixed.
I just started encryption and it wasn't locked in the robot anymore, it booted and now shows a progress bar with 4% complete.
Thanks, kabaldan!
Just one more question, will there be CM12 for moto_msm8960_jbbl later, or if I want to upgrade to CM12 I will have to do this kkbl workaround you mentioned?
kabaldan said:
@taylortm Please read again what I wrote to you here: http://forum.xda-developers.com/showpost.php?p=58132610&postcount=2
You can't use moto_msm8960 CM11 builds nor xt925 CM12 build unless you update your device to stock KitKat firmware by Motorola first.
While your device is still using JellyBean bootloader/modem firmware, you can update only to moto_msm8960_jbbl CM11 builds.
Click to expand...
Click to collapse
I'm giving a try again to the xtrasmooth with M using the release from 14th July and seems stable, at least during this 3 days however, I have a notice for an android update that suddenly come up that I'm not able to flash because when I reboot into recovery there is not a way to flash it.
Have any one else the same problem?
MPZ44Q or MPZ79M
mickjmickj said:
I'm giving a try again to the xtrasmooth with M using the release from 14th July and seems stable, at least during this 3 days however, I have a notice for an android update that suddenly come up that I'm not able to flash because when I reboot into recovery there is not a way to flash it.
Have any one else the same problem?
Click to expand...
Click to collapse
I couldn't wait to understand how to make this update so I flashed the xtrasmooth MPZ79M and I find soon some differences like the dark team that was not availabile and the apps grid that is not divided by letters. At the end I've came back to the MPZ44Q that is still quite stable for my use.
Remain the issue about the android update notification.
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
JJEgan said:
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
Click to expand...
Click to collapse
I've just picked up a used 10.1 (first edition) and am hoping to get it onto 5.1.1 or 6.01.
I see a custom CM ROM from Cyanogen, that states it's 6.0 official, but when I go to the site the release is really old for the 8013, and I'm not sure if it's been grouped in with the more recent beta group that is linked in the thread or if it's not.
I also see an older Cyanogen thread for 12, but that's pre 6.0 and appears to be somewhat abandoned.
My Note 3 is on phronesis 6.0.1, and I would like to get the Note 10.1 to as close to that as possible, without dealing with any major bugs.
Thank you for your assistance.
Some progress.
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Basil Rathbone said:
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Click to expand...
Click to collapse
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Still no joy
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
bladebarrier said:
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Click to expand...
Click to collapse
Basil Rathbone said:
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
I used the ARM 6.0 Stock version for CM 13. http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
I ended up swapping to the 2014 model because I got a good deal on a Verizon version (which is locked but oh well), so I don't recall the TWRP that I ran. It sounds like that sometimes gives people issues.
I do recall that using the nano version of gapps was not working for me. Could be a coincidence, but I had constant crashes when I tried using it.
This is the thread I used to grab the ROM and TWRP: http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375
It helps to read the installation notes properly
The problem(s) I was having were resolved by using twrp-2.8.7.0-gt-n8013 instead of N8013-CWM-Touch-6.04.6. I also used open_gapps-arm-6.0-stock-20160803 instead of nano but I really think it was TWRP that made everything work.
I'm now running cm-13.0-20160523-UNOFFICIAL-n8013 without any problems.
I consider this thread closed.
Basil Rathbone said:
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
Click to expand...
Click to collapse
How did you get KitKat on n8013. It was never released and no one successfully flashed 4.4 n8010 to n8013. Odin keeps giving an error. Please I've been trying for years now since it's been 2 years since update was released and doesn't look like it'll ever release (**** yoi Samsung with your update **** and regions)
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
MrAwesome75 said:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Well official only kitkat if you are international (Samsung decided not to release a lot of device updates in the us for kit kat including the s3, galaxy light, and this one). However I think you can get CM 13.1, idk about anything more recent but there is a (slightly) active community for it still left. Its a shame that this flagship tablet was neglected. I hope it doesn't happen with future Samsung ones but I've avoided buying any. I still use mine on jellybean for basic internet browsing and games
zMrAwesome75 said:
Quote:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
7.1.2 on GT-N80013
I am currently running an unoffical build I picked up here on xda it is an unofficial Lineage OS build. I haven't currently found any bugs... camera works, bluetooth works, wifi works... at least for me. The build number is 14.1-20170810-unnofficial-n8013
Hannover2k said:
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
Click to expand...
Click to collapse
I'd appreciate a link to the rom you installed. Thx.
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
cloves said:
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
Click to expand...
Click to collapse
I recently installed Lineage OS 14 and it is working great.
Tablet is stable, everything works, great battery life.
All devices work gps, etc...
The s-pen will not work like it did stock but there are apps you can get that seem to work better
Squid and Sketch for drawing....squid seems cool if you write with stylus
Install Magisk instead of supersu.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You can find download under the "Downloads" tab on the top left of this thread / post.
Or you can find it at, https://forum.xda-developers.com/devdb/project/?id=22974#downloads
XDA:DevDB Information
[ROM][7.1.2][Ovation][EMMC][UNOFFICIAL] LineageOS 14.1, ROM for the Barnes & Noble Nook HD, HD
Contributors
secretwolf98, LineageOS
Source Code: https://github.com/airend/android/tree/cm-14
ROM OS Version: 7.x Nougat
ROM Firmware Required: TWRP 3.1.1-0 and up
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: LineageOS 14.1
Stable Release Date: 2017-12-16
Created 2017-10-24
Last Updated 2017-10-24
Thanks again, i'm using it now and seems to work properly.
Downloaded and installed perfectly. Running fine - will update later.
Good job thanks
Sent from my BN NookHD+ using Tapatalk
Nemesis1278 said:
Thanks again, i'm using it now and seems to work properly.
Click to expand...
Click to collapse
Your welcome
Tight Git said:
Downloaded and installed perfectly. Running fine - will update later.
Good job thanks
Sent from my BN NookHD+ using Tapatalk
Click to expand...
Click to collapse
Your welcome
Hah, awesome, just dug the Nook up from a drawer and was wondering what to do with it, glad to see I can flash a proper updated OS!
Thanks for all your effort!
BSAB said:
Hah, awesome, just dug the Nook up from a drawer and was wondering what to do with it, glad to see I can flash a proper updated OS!
Thanks for all your effort!
Click to expand...
Click to collapse
Your welcome.
Really great work, thanks secretwolf98! Gave new life to my old Nook HD+, especially with some of my favorite apps starting to no longer support older Android versions. A few issues/questions:
How do I get root? I tried installing the official LineageOS addonsu-14.1-arm.zip as well as amaces' addonsu-14.1-arm-new.zip and they both fail in TWRP with
Code:
ApplyParsedPerms: lsetfilecon of /system/addon.d/51-addonsu.sh to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
Maybe related to the previous if it's an issue with the TWRP I have, but I couldn't find a TWRP 3.1.1-0 zip for Ovation so I just replaced the img in amaces TWRP 3.0.1-0 zip. Is there an actual 3.1.1-0 zip that this ROM requires?
When I select Power Off, my Nook reboots instead and I have to hold down the power button to get it to really shut off. Not a big deal since I rarely power off, but a strange bug.
sur4k said:
Really great work, thanks secretwolf98! Gave new life to my old Nook HD+, especially with some of my favorite apps starting to no longer support older Android versions. A few issues/questions:
How do I get root? I tried installing the official LineageOS addonsu-14.1-arm.zip as well as amaces' addonsu-14.1-arm-new.zip and they both fail in TWRP with
Code:
ApplyParsedPerms: lsetfilecon of /system/addon.d/51-addonsu.sh to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
Maybe related to the previous if it's an issue with the TWRP I have, but I couldn't find a TWRP 3.1.1-0 zip for Ovation so I just replaced the img in amaces TWRP 3.0.1-0 zip. Is there an actual 3.1.1-0 zip that this ROM requires?
When I select Power Off, my Nook reboots instead and I have to hold down the power button to get it to really shut off. Not a big deal since I rarely power off, but a strange bug.
Click to expand...
Click to collapse
Thanks, and your welcome. Install this version, https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/239817874034
then install this, https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/185013076312
Make sure to install G-Apps before ROOT. I recommend, ARM | 7.1 | Pico, from, http://opengapps.org/
Then I recommend going into system and enabling ROOT. Then play around in the system for about 5 minutes. Do a reboot back into the system. Download, https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
and make sure ROOT is working correctly. If it's working... Reboot into TWRP then wipe the 2 caches in advanced. Install my latest version, https://forum.xda-developers.com/devdb/project/dl/?id=27077
Then wipe the 2 caches again (said above), then reboot into system.... See if you have ROOT in "ROOT Checker". If you have any questions, don't be afraid to ask.
Hey I downloaded the twrp 3.1.1-0 from the official twrp site but it seems bugged, in that it doesn't read internal nor external storage. Where can I download a good version? Should I use a different version?
Nolfer said:
Hey I downloaded the twrp 3.1.1-0 from the official twrp site but it seems bugged, in that it doesn't read internal nor external storage. Where can I download a good version? Should I use a different version?
Click to expand...
Click to collapse
Use the latest ClockWorkMod here, https://forum.xda-developers.com/showthread.php?t=2062613
and install the ROM from there. I had this same problem with my first Nook HD.... I thought it was 100% Hard Bricked... But it is soft bricked. Nook's can get into soft bricks only. So I bought a new nook, and it runs better. The first Nook has been dropped so many times... After just using is for 30 seconds it felt like a oven. It was on stock... Until April-30-2016, after school I went to spend the night at my friend's house and then I used his computer to ROOT it. Bad idea only getting 30 minutes of sleep that night... Because I wanted to finish to install CM 10 on the Nook. Then a day or 2 later I installed CM 11. I was so tired on my birthday the next day. So I would say on May-9-2016 it did the same thing in the recovery like yours. I did own the Nook for like 5 years with stock.
secretwolf98 said:
Thanks, and your welcome. Install this version, https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/239817874034
then install this, https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/185013076312
Make sure to install G-Apps before ROOT. I recommend, ARM | 7.1 | Pico, from, http://opengapps.org/
Then I recommend going into system and enabling ROOT. Then play around in the system for about 5 minutes. Do a reboot back into the system. Download, https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
and make sure ROOT is working correctly. If it's working... Reboot into TWRP then wipe the 2 caches in advanced. Install my latest version, https://forum.xda-developers.com/devdb/project/dl/?id=27077
Then wipe the 2 caches again (said above), then reboot into system.... See if you have ROOT in "ROOT Checker". If you have any questions, don't be afraid to ask.
Click to expand...
Click to collapse
I tried installing the linked ROM, then gapps, then the linked addonsu and still get the same error. I'm convinced my version of TWRP is the problem. Can I use CWM instead?
sur4k said:
I tried installing the linked ROM, then gapps, then the linked addonsu and still get the same error. I'm convinced my version of TWRP is the problem. Can I use CWM instead?
Click to expand...
Click to collapse
Yes, the latest one.
secretwolf98 said:
Use the latest ClockWorkMod here, https://forum.xda-developers.com/showthread.php?t=2062613
and install the ROM from there. I had this same problem with my first Nook HD.... I thought it was 100% Hard Bricked... But it is soft bricked. Nook's can get into soft bricks only. So I bought a new nook, and it runs better. The first Nook has been dropped so many times... After just using is for 30 seconds it felt like a oven. It was on stock... Until April-30-2016, after school I went to spend the night at my friend's house and then I used his computer to ROOT it. Bad idea only getting 30 minutes of sleep that night... Because I wanted to finish to install CM 10 on the Nook. Then a day or 2 later I installed CM 11. I was so tired on my birthday the next day. So I would say on May-9-2016 it did the same thing in the recovery like yours. I did own the Nook for like 5 years with stock.
Click to expand...
Click to collapse
I solved the problem adb flashing twrp 3.1.0-0 wich worked flawlessly.
I now have another problem. I cannot change the default cfq scheduler for internal storage. Every time I change it the tablet frezes and I have to manually reboot
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
sur4k said:
I tried installing the linked ROM, then gapps, then the linked addonsu and still get the same error. I'm convinced my version of TWRP is the problem. Can I use CWM instead?
Click to expand...
Click to collapse
try flashing 3.1.0-0 TWRP
then go to developer options, disable root and then reenable for apps and adb. Reboot. Let me know
Just like to say thanks for all the work on this rom. My 4 year old Nook HD+ now does everything i need from a tablet
Sent from my SM-G935F using XDA-Developers Legacy app
edsib1 said:
Just like to say thanks for all the work on this rom. My 4 year old Nook HD+ now does everything i need from a tablet
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Your welcome
so far so good, updated both my hd and my hd+, both running smooth. Great job secretwolf98 !!!
zspeciman said:
so far so good, updated both my hd and my hd+, both running smooth. Great job secretwolf98 !!!
Click to expand...
Click to collapse
Thanks and your welcome
will not reboot, stuck at loading screen
xecutionkrk said:
will not reboot, stuck at loading screen
Click to expand...
Click to collapse
clean install, wipe everything, except where you have the ROM at.