Related
I did a search but couldnt find any answers so please point me to the relevant post if this has already been answered, but is there any guide for the functions of TWRP 2.0? im coming from CWM on SGS II so would like to clear up a few things:
TWRP gives options to backup/restore 6 things - system, data, boot, recovery, cache, and .android_secure. Im mainly concerned about boot and recovery.
1) If we have TWRP and FIREFIREFIRE isntalled and working normally - then under normal circumstances should there ever be a need to restore boot or recovery, normally we would only restore system right?
2) If I was to restore the recovery while in recovery, could I not potentially brick/break recovery? If not, then I assume then either restoring/intalling a .zip containing the stock boot, recovery and system will return my kindle to stock (and ensure I no longer break warranty!!)?
Thanks in advance
Alchemist07 said:
I did a search but couldnt find any answers so please point me to the relevant post if this has already been answered, but is there any guide for the functions of TWRP 2.0? im coming from CWM on SGS II so would like to clear up a few things:
TWRP gives options to backup/restore 6 things - system, data, boot, recovery, cache, and .android_secure. Im mainly concerned about boot and recovery.
1) If we have TWRP and FIREFIREFIRE isntalled and working normally - then under normal circumstances should there ever be a need to restore boot or recovery, normally we would only restore system right?
2) If I was to restore the recovery while in recovery, could I not potentially brick/break recovery? If not, then I assume then either restoring/intalling a .zip containing the stock boot, recovery and system will return my kindle to stock (and ensure I no longer break warranty!!)?
Thanks in advance
Click to expand...
Click to collapse
I have read many forums of people boot bricking their kindles with twrp I would be very careful if thinking about doing this until a good tutorial is out that confirms this working with no bugs, just to be on the safe side. whatever your choice good luck and please post anything you find out so that we all can benefit from others experiences...! I am currently working on a good way to do just this and will post back to this forum when I work it out completely
Just bumping this in case anyone has answers for these questions yet?
Thanks,
Hi folks,
5 day ago i rootet my tablet 16GB WE and installed Koshu`s CWM step by step like discribed in his threat [http://forum.xda-developers.com/showthread.php?t=1831161]. At the end there was an error message..., i was too quick and made an reboot bevor i could read it.
But i tested if i rooted the tablet succesfully and the superuser-app said that i am root now....
Then i installed the v.0.8.1 Version and everything was fine!
a few days later i got reboots during normal use.
Now i cant boot in the OS, there are bootloops the hole time.
I think that i have not installed the CWM correct...
Any ways to check this with adb commands or something else?
It would be great if someone could help me....
Sorry for my bad english!
Thomas
tpauli said:
Hi folks,
5 day ago i rootet my tablet 16GB WE and installed Koshu`s CWM step by step like discribed in his threat [http://forum.xda-developers.com/showthread.php?t=1831161]. At the end there was an error message..., i was too quick and made an reboot bevor i could read it.
But i tested if i rooted the tablet succesfully and the superuser-app said that i am root now....
Then i installed the v.0.8.1 Version and everything was fine!
a few days later i got reboots during normal use.
Now i cant boot in the OS, there are bootloops the hole time.
I think that i have not installed the CWM correct...
Any ways to check this with adb commands or something else?
It would be great if someone could help me....
Sorry for my bad english!
Thomas
Click to expand...
Click to collapse
You can still boot into CWM? Well you could make a backup of the installed recovery (like shown in the CWM thread) and check if the md5sums are equal to the downloaded image. Btw. linebreaks in the logcat would really help reading it
Koshu said:
You can still boot into CWM? Well you could make a backup of the installed recovery (like shown in the CWM thread) and check if the md5sums are equal to the downloaded image. Btw. linebreaks in the logcat would really help reading it
Click to expand...
Click to collapse
yes i can Boot into CWM, but i cant restore my backup. I tried to install cm10 clean again but after rebooting CWM and booting the OS Android is updating the apps. But i did a full wipe bevor.Thats why i think that the CWM is not in an good state.
i am in the road and maybe i can later check the md5sum.
I can attach an picture from the CWM during trying formating and fixing permissions.
thank you!
Problem solved
tpauli said:
yes i can Boot into CWM, but i cant restore my backup. I tried to install cm10 clean again but after rebooting CWM and booting the OS Android is updating the apps. But i did a full wipe bevor.Thats why i think that the CWM is not in an good state.
i am in the road and maybe i can later check the md5sum.
I can attach an picture from the CWM during trying formating and fixing permissions.
thank you!
Click to expand...
Click to collapse
Koshu helped me! The problem was, that my data partion was read only and my wipes befor and installs was more or less unusefull!
Big thanks to koshu!!!!!
tpauli said:
Koshu helped me! The problem was, that my data partion was read only and my wipes befor and installs was more or less unusefull!
Big thanks to koshu!!!!!
Click to expand...
Click to collapse
Hi. I have the same Problem. Can you tell me how Koshu helped to fix the problem.
the checksum and stuff. thx
florian1985 said:
Hi. I have the same Problem. Can you tell me how Koshu helped to fix the problem.
the checksum and stuff. thx
Click to expand...
Click to collapse
I linked a zip file in the CM10 Thread that formats the data partition: http://forum.xda-developers.com/showthread.php?t=1846044
You can find it in the "addition steps" section. Beware that it will delete all your personal data including the internal sd-card (also nandroid backups if you have stored them on the internal sdcard). So make sure you have EXTERNAL backups if you want to keep some of the data.
I have same problem
After install CM10 ,my TPT cant boot
I turn on My tablet and see loop forever logo : Lenovo ==> CyanogenMod....
Please help me, how to fix it ????
cachlanhuong said:
I have same problem
After install CM10 ,my TPT cant boot
I turn on My tablet and see loop forever logo : Lenovo ==> CyanogenMod....
Please help me, how to fix it ????
Click to expand...
Click to collapse
I have nearly the same problem.
I rooted my TPT a few weeks ago, today I was reading about Cyanogen and decided to install CWM. After some issues with the adb drivers, I managed to install the clockwork recovery.
Now I followed the steps from the cm-thread. I did a nandroid backup and wiped my tablet. After that, I flashed CM10. But all I get is the CyanogenMod logo spinning around.
I tried to go back to my nandroid backup, but it seems broken somehow.
I also tried several several CM-versions and downloaded them several times, without success. But I realised, that the installation procedure of CM was very quick, too quick maybe? Could it be that my clockworkmod isn't installed correctly, because the installation of CM and the nandroid backup won't work.
I hope you guys can help me out. Because I only could find nandroid backups for ROW and US version. I also don´t have adb access anymore.
TPT 16GB 3G WE
Ottilooping said:
I have nearly the same problem.
I rooted my TPT a few weeks ago, today I was reading about Cyanogen and decided to install CWM. After some issues with the adb drivers, I managed to install the clockwork recovery.
Now I followed the steps from the cm-thread. I did a nandroid backup and wiped my tablet. After that, I flashed CM10. But all I get is the CyanogenMod logo spinning around.
I tried to go back to my nandroid backup, but it seems broken somehow.
I also tried several several CM-versions and downloaded them several times, without success. But I realised, that the installation procedure of CM was very quick, too quick maybe? Could it be that my clockworkmod isn't installed correctly, because the installation of CM and the nandroid backup won't work.
I hope you guys can help me out. Because I only could find nandroid backups for ROW and US version. I also don´t have adb access anymore.
TPT 16GB 3G WE
Click to expand...
Click to collapse
Koshu helped me!
I linked a zip file in the CM10 Thread that formats the data partition: http://forum.xda-developers.com/showthread.php?t=1846044
You can find it in the "addition steps" section. Beware that it will delete all your personal data including the internal sd-card (also nandroid backups if you have stored them on the internal sdcard). So make sure you have EXTERNAL backups if you want to keep some of the data.
tpauli said:
Koshu helped me!
I linked a zip file in the CM10 Thread that formats the data partition: http://forum.xda-developers.com/showthread.php?t=1846044
You can find it in the "addition steps" section. Beware that it will delete all your personal data including the internal sd-card (also nandroid backups if you have stored them on the internal sdcard). So make sure you have EXTERNAL backups if you want to keep some of the data.
Click to expand...
Click to collapse
But how can formatting my data partition help? You mean after a format, the installation of cm would work?
And how do I use the .zip, just flashing with cwm?
Ottilooping said:
But how can formatting my data partition help? You mean after a format, the installation of cm would work?
And how do I use the .zip, just flashing with cwm?
Click to expand...
Click to collapse
You have to download the formatdata.zip on your external sd-card.
After that you can boot in the recovery and flash this .please dont juse the cwm! Do you know how to boot into the recovery?
Power on and during that you should drop-down the volume + key a few seconds.
This helped me and others.
Please read in this threat: http://forum.xda-developers.com/showthread.php?t=1831161
tpauli said:
You have to download the formatdata.zip on your external sd-card.
After that you can boot in the recovery and flash this .please dont juse the cwm! Do you know how to boot into the recovery?
Power on and during that you should drop-down the volume + key a few seconds.
This helped me and others.
Please read in this threat: http://forum.xda-developers.com/showthread.php?t=1831161
Click to expand...
Click to collapse
But I have no recovery anymore. The cwm replaced the "normal" recovery.
Ottilooping said:
But I have no recovery anymore. The cwm replaced the "normal" recovery.
Click to expand...
Click to collapse
Send me an photo from your "recovery"...
tpauli said:
Send me an photo from your "recovery"...
Click to expand...
Click to collapse
https://www.dropbox.com/s/xl9fx8rb8bpqgkf/IMG_20130212_110830.jpg
Here is the photo.
I was thinking about 2 possible solutions right now.
1. get another nandroid backup (Problem didnt see any for the 16gb WE version)
2. try no reflash another CWM version or maybe ventana cwm and try again to flash Cyanogen (don't know if its possible to just flash another recovery as an image with the current working recovery)
So what do you guys think?
Ottilooping -
You were running ICS before flashing to CM, right?
da_reeseboy said:
Ottilooping -
You were running ICS before flashing to CM, right?
Click to expand...
Click to collapse
Yes, thats correct.
Ottilooping said:
https://www.dropbox.com/s/xl9fx8rb8bpqgkf/IMG_20130212_110830.jpg
Here is the photo.
I was thinking about 2 possible solutions right now.
1. get another nandroid backup (Problem didnt see any for the 16gb WE version)
2. try no reflash another CWM version or maybe ventana cwm and try again to flash Cyanogen (don't know if its possible to just flash another recovery as an image with the current working recovery)
So what do you guys think?
Click to expand...
Click to collapse
That looks good!
My suggestion: Flash the formatdata.zip and than install the last v0.9.2 from koshu located here: http://forum.xda-developers.com/showthread.php?t=1846044
I was coming from ics too.
Problem solved. CM is running. Thanks for your help, exspecialy to you tpauli.
The formatdata.zip was the key
One last question. I am using the folio keyboard with an european layout (qwertz), but with Cyanogen it is us layout (qwerty). How can I change this?
yes i read before posting. first let me tell you wut i did.
1) installed schizoid pac rom on nook color......
2) as per instructions i formatted system and cache.
3)flashed rom
4)worked slow but fine. decided this rom isnt worth keepin on.
5)as per instructions when transferring from these types of roms to any other 10.1.x roms i formatted system/cache again
^^^^^^^^^^^^^^^^^this last step broke my clockwork recovery. :crying:
----now i am unable to boot after rom,gapps flash.
----receive following messages when cwm is pulled up
-----E:\ unable to mount system, cache and all the other ones that u can manually mount and dismount via cwm
so i can flash jus not boot up.
tried flashing stock image .zip for a stock recovery via sd boot and i get passed *read forever* and then i hit the big gigantic "n" with copywrite details and such but won't go passed that screen.
wanted to try the adb restore thingy but i need to be able to boot up the nook to enable debug right? so i can't do that......unless im stupid which quite possibly is the case. i had a moment complaining about kit kat earlier and am sorry so if i can't get help i understand. thx guys
newbtrigger69 said:
yes i read before posting. first let me tell you wut i did.
1) installed schizoid pac rom on nook color......
2) as per instructions i formatted system and cache.
3)flashed rom
4)worked slow but fine. decided this rom isnt worth keepin on.
5)as per instructions when transferring from these types of roms to any other 10.1.x roms i formatted system/cache again
^^^^^^^^^^^^^^^^^this last step broke my clockwork recovery. :crying:
----now i am unable to boot after rom,gapps flash.
----receive following messages when cwm is pulled up
-----E:\ unable to mount system, cache and all the other ones that u can manually mount and dismount via cwm
so i can flash jus not boot up.
tried flashing stock image .zip for a stock recovery via sd boot and i get passed *read forever* and then i hit the big gigantic "n" with copywrite details and such but won't go passed that screen.
wanted to try the adb restore thingy but i need to be able to boot up the nook to enable debug right? so i can't do that......unless im stupid which quite possibly is the case. i had a moment complaining about kit kat earlier and am sorry so if i can't get help i understand. thx guys
Click to expand...
Click to collapse
Go to my NC partition repair thread linked in my signature and flash the repair and format zips. That should then let you put any ROM you want back on it, including stock.
You may have to go to my NC Tips thread to make a bootable recovery SD first though.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Go to my NC partition repair thread linked in my signature and flash the repair and format zips. That should then let you put any ROM you want back on it, including stock.
You may have to go to my NC Tips thread to make a bootable recovery SD first though.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
thx, will try when i get off work. again thx for the response
GENIUS!
GENIUS!:highfive:
Hey all.
Hope I am in the correct forum section.
I am having difficulty with flashing a custom rom and was hoping for some direction.
Can someone please confirm i am in the correct forum section I will give details of what has happened, what I have tried in my next post.
No1Daemon said:
Hey all.
Hope I am in the correct forum section.
I am having difficulty with flashing a custom rom and was hoping for some direction.
Can someone please confirm i am in the correct forum section I will give details of what has happened, what I have tried in my next post.
Click to expand...
Click to collapse
Device/Phone model number?
Any samsung bootllop can be solved here though
"If someone helps, never forget to hit thanks ? "
Thanks for the reply
Some details then
Model is Samsung S4 GT-I9505
I rushed into booting and selected an aokp rom and then selected the latest apps file for it and got stuck in an endless boot loop.
I am now trying to install a GPE Rom
gpe-rom-for-galaxy-s4-android-4-4-4
I am still able to get into recovery and download mode.
I flashed philz_touch_6.15.6-jflte.tar.md5 using odin3 on windows then rebooted into recovery and did a clean up for new rom and factory reset then attempted to move the rom onto my phone and thats where I have run into trouble. I am trying to use adb to push the file into it because I seem to have somehow wiped the sdcard(i.e. in phil recovery under mounts and storage there is no /sdcard to mount or unmount.
Thins I tried:
Using a micro sd card and copying the file to it and inserting it in the phone and installing from /sdcard1 but it just aborts the install and gives me a failed error
I tried to push the file with adb by opening terminal cd to downloads where the rom is located and used
Code:
adb push rom.zip /data/media/0 rom.zip
but this never completes. it is supposed to return the size of the files but nothing happens. I know adb can see the phone as when I type adb devices I get back a response saying recovery
Can anyone give me any pointers or advice. Happy to start from scratch but so far every tutorial/discussion on installing roms etc i have followed has failed.
Incidentally I do not have a backup because I thought I made one successfully when I fist rooted but when I went to restore it it gave me a md5 hash invalid error
Thanks
Have you tried a different recovery? You can try TWRP 2.8.1.0 and see how it goes. Just us odin to flash the recovery and use a usb card reader to put the rom onto the SD Card. To be safe you can also try a different rom, if you are after a GPE rom, I recommend Dan's GPE rom.
http://forum.xda-developers.com/showthread.php?t=2557353
That is one of the roms I was hoping to install before I successfully flashed it back to stock.
Will look into it.
I couldn't use a card reader to put the rom on because I was having difficulty reading the external sd card in recovery.
I tried many different recoveries. TWRP, CMR and Philz but had no luck with any of them.
Do you know if all packages get made into a complete rom to install with Odin? like I did with my stock rom?
Just seemed an easier way to install it.
My english is very bad.
Your back Stock Rom with Odín download firmware SamMobile.
Custom, download custom again its possible corrupt download, wipe data, system, caché, Factory reset.
You have use one recovery or not installing previous backup for MD5 Missmatch
Format SD in the phone.
Proccess very slow with Odín install Stock Rom, root, recovery, install custom
Try with recovery using for previous backup for restore backup.
Mi inglés es muy malo, en inglés no te lo puedo explicar mejor.
No1Daemon said:
That is one of the roms I was hoping to install before I successfully flashed it back to stock.
Will look into it.
I couldn't use a card reader to put the rom on because I was having difficulty reading the external sd card in recovery.
I tried many different recoveries. TWRP, CMR and Philz but had no luck with any of them.
Do you know if all packages get made into a complete rom to install with Odin? like I did with my stock rom?
Just seemed an easier way to install it.
Click to expand...
Click to collapse
Dont flash a custom rom on an already bootlooped phone.
Either flash your stock rom or you can restore a backup via recovery.
Then start experimenting again..as flashing and more flashing and more more flashing on a bootloop can cause a few things to go crazy.
It is not recommended. But then your choice. Its not a big task of coming to a stock firmware then continuing with things...
"If someone helps, never forget to hit thanks ? "
DeepankarS said:
Its not a big task of coming to a stock firmware then continuing with things...
Click to expand...
Click to collapse
I found it a big task and I am used to this sort of thing. I got there eventually but thanks for the advice. Will keep that in mind in case I get stuck in a boot loop again.
Will pay more attention to backups etc when I flash the next one.
No1Daemon said:
I found it a big task and I am used to this sort of thing. I got there eventually but thanks for the advice. Will keep that in mind in case I get stuck in a boot loop again.
Will pay more attention to backups etc when I flash the next one.
Click to expand...
Click to collapse
No generally what happens it people skip things while being hyper relating to flashing.
Basics are never to be left out. When adb terminals and things weren't there, the tedious processes were used to recover.
(flash stock..flash recovery..flash things then when you're in a boot loop if factory reset doesn't work)
And you should always have a backup+updated stock firmware handy.
If either doesn't work for you always have a support
"If someone helps, never forget to hit thanks ? "
Caveat emptor: adopt/follow this guide at your own risk.
Below is a procedure that can be used to update your HD+ EMMC to LN14.1 from CM11 (if your HD+ is currently running stock ROM, use the process described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810/).
Download the following files to a location in your user content-media storage space on the HD+:
amaces' flashable TWRP zip file, e.g., twrp-3.0.1-0-ovation.zip ( https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778)
amaces' flashable LN14.1 ROM zip file, e.g., lnos_ovation-ota-NMF26Q.170104.zip from https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778
the flashable zip file of the Gapps pico package open_gapps-arm-7.1-pico-2017[mmdd].zip from http://opengapps.org/
Boot into your current EMMC recovery.
Select install zip and install the TWRP recovery zip file obtained in step 1(a).
Power off the Nook.
Boot into the new TWRP recovery flashed in the step 3 (press and hold the Home button, then press and hold the Power button until after the CyanoBoot Universal Bootloader screen comes on, then release both buttons).
Select wipe /data & factory reset.
Select install zip and install the LN14.1 zip file.
Select install zip and install the Gapps zip file.
Reboot into the new LN14.1.
Once the Nook completes the boot (be patient as it takes quite a bit of time), set up the Wifi connectivity and your Google account info. Note that the Apps you previously have on CM11 will not be auto-downloaded/restored into your new LN14.1.
If you run into problems during initial setup:
- absence of WiFi network setup step: see this post
- setup process crashes (as have been reported with some combos of ROM and GApps build versions): retry the clean install process with the sequence of steps # 6, #7 & #9 (i.e., skipping over step #8 flashing GApps) and complete the initial setup, then reboot into TWRP to flash GApps; see also https://forum.xda-developers.com/showpost.php?p=72104906&postcount=37 for solution for other setup crash causes.
To enable "Root", see https://forum.xda-developers.com/showpost.php?p=72185622&postcount=1915.
Notes
If you encounter errors in step 3 (using your existing CWM recovery to flash the new TWRP zip file):
- If you have a SD card handy, consider using the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
- Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Please post any comment/question on the features or performance of AOSP & LN ROM builds on the Developer's thread at https://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269.
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
stupid_nut said:
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
Click to expand...
Click to collapse
Is your device a Nook HD+?
digixmax said:
Is your device a Nook HD+?
Click to expand...
Click to collapse
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing TWRP through their official app? I think I also had trouble trying to flash TWRP through CWM, but the app worked at the time.
You could also flash internal TWRP through Amaces's multi mode bootable SD recovery. It does mean you'd need to setup a spare SD card for it, but it can be good to have handy anyway [emoji6]
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
I can't tell why the update script doesn't identify your device as "ovation".
If you have an SD card handy, I'd suggest that you try the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810. Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Thanks guys!
I just ended up using the SD card procedure. TWRP app failed as well. CM11 was slowing to a crawl on the NookHD+ so hopefully Lineage will give it new life!
error 20 on gapps (you don't have Android 7)
Hi, had CM11 on my HD+ for over a year. Unfortunately I left it on til battery completely discharged the other night, and even after charging to 100%, it would only go in a boot loop. (cyanogenmod bootloader, then robot face, then cyanogenmod bootloader again, then robot face again, etc, nonstop). So I thought, why not wipe it and put Lineage on?
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader? And if I press "N" I see TWRP as an option, as well as CM (legacy) So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
So something isn't right here, or I'm missing some steps? Any help please?
baytee said:
...
So something isn't right here, or I'm missing some steps? Any help please?
Click to expand...
Click to collapse
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
digixmax said:
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
Click to expand...
Click to collapse
YES I tried both procedures. In fact I tried that link you have for "installing new" procedure first But it failed on the Gapps part. And like I said the previous CM11 (at least boot part) seems corrupt as its stuck in a boot loop. So ideally if it's not riskier, I was attempting to wipe off the old system. (unless by checking all the boxes except SD, under Wipe, Advanced, I did accomplish that? and just the boot/bootloader portion remains?
baytee said:
...
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader?
Click to expand...
Click to collapse
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
And if I press "N" I see TWRP as an option, as well as CM (legacy)
Click to expand...
Click to collapse
These are just the choices of TWRP & CWM recovery available on the SD.
So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
...
Click to expand...
Click to collapse
You should never need to wipe anything other than /data and /cache (/system typically gets wiped automatically (aka reformatted) as part of the process of flashing a new ROM version).
digixmax said:
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
.
Click to expand...
Click to collapse
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
So, any hope for my HD+ ? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet? Why would my battery going to zero screw things up so badly?
baytee said:
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
To flash stock ROM you need CWM version 6.0.2.8 attached at the end of the post I referenced.
So, any hope for my HD+? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet?
Click to expand...
Click to collapse
If your EMMC is dead, you can try to run CM11 entirely off an SD card -- see https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
baytee said:
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
That "tool" for unbricking the NT also boots and runs off a SD card.
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
baytee said:
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
Click to expand...
Click to collapse
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
digixmax said:
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
Click to expand...
Click to collapse
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
baytee said:
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
Click to expand...
Click to collapse
The stock rom you tried to install was the rooted version that I customized. Try a plain stock rom from that same thread. Try an older version. That error was a common one for some devices.
Sent from my SM-T707V using XDA Premium HD app
Will this guide also work on the Nook HD? (Using the equivalent Hummingbird files, of course).