Related
NC Rooted
cm 10-20130421 nightly
TWRP on sd card boot 2.3.0.2 encore 1gb sdimg
TWRP zip installed to emmc 2.3.0.1 encore cigned . zip
Questions
Is there a User Guide? I looked at the dev TWRP site and all over this NC forums, yes searched.
Why is the boot/install TWRP version different from the internal zip?
Had problems with INTERNAL TWRP
Backup reported ran ok, review of file and attempted restore showed no partitions backed up?
I had 4 backups. 2 had the 3 partitions, others none
All backed to EXT SD
Tried a restore. FAILED with /BOOT not restored error
NC bricked. No boot
I was able to finally get it to boot from Sd after a 'number' of 'press and hold ' of the power button.
I had to do a full wipe-install.
Ran a bckup from internal TWRP. The file shows the 3 partitions.
Summary
User Guide?
What went wrong with backup files
What went wrong with the failed restore
Thanks
TWRP?
Anyone?
Did I post to the correct forum?
Did I ask my question or state the issue correctly?
I have done many searches for the answer
My current process is
Make a backup
Validate all partitions are backed up
Run a recovery to make sure it works.
Another issue
I read a few of the pros/devs do NOT use nor 'care' for TWRP.
Is CWMR better safer ?
Looking for some guidance
RR
vmaxept said:
Anyone?
Did I post to the correct forum?
Did I ask my question or state the issue correctly?
I have done many searches for the answer
My current process is
Make a backup
Validate all partitions are backed up
Run a recovery to make sure it works.
Another issue
I read a few of the pros/devs do NOT use nor 'care' for TWRP.
Is CWMR better safer ?
Looking for some guidance
RR
Click to expand...
Click to collapse
Don't know much about TWRP, still using Clockwork, it just does what I need, try here for TWRP info http://forum.xda-developers.com/showthread.php?t=1397513&highlight=twrp
You might also want to look at this thread http://forum.xda-developers.com/showthread.php?t=1941858
Re TWRP
WB thanks for the reply.
Yes, I have read both the suggested links. Read at least 2 to 3 times. Before I posted the questions. TWRP has many options that are not self-evident to me.
I might burn the img for the new CMW-R 6.xx and see what it does.
I have used the older 3.xx with no issues.
I just wanted to try the GUi of TWRP. I did watch a number of videos about TWRP.
There are a number of pro/devs that prefer one product over another.
This has been a self taught process for me. As long as I dont brick the nook I can keep doing what I can while I learn.
Thanks for the response
RR
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 ? "
Hi, I rently bought a Galaxy S7 Edge and i wanted to install the SUPERMAN custom ROM so :
I followed the tutorial to root the phone => ok
the tutorial to install TWRP => OK
Then the tutorial to install the ROM, and thats when the problems started to appear.
When I tried backing up before the installation in TWRP, I had a couple of error message like "unable to mount data". As the phone was new, I did not have any personnal data on it I thought "Backup is not necessary (grave error?)
so I skiped and went directly to ROM installation (the ROM was on an external microSD card) => installation OK
BUT I forgot to wipe Dalvik cache before rebooting, and as i understand it, it can cause a bootloop, it apparently did!
Here, as it was late, I started to lose my cool, so I am not entirely sure about the sequence of what I have done, but I am trying my best to be precise so that you can find a way to help me.
- I went back to TWRP, I tried to wipe dalvik cache and other types of wipe, but had the same error "unable to mount data" on every try.
-I googled a little bit and found a video tutorial ecplaining that I need to wipe => advanced wipe => tick system => change file system => then choose a type (i chose exFat) => It went on for 10-15 minutes without any sign of evolution so I reached the peak of my stupidity (really lost my cool), and forced reboot (not sure if I used volume UP or DOWN
-I dont think I did anything else after this, when I tried going into TWRP, I got stuck on the TWRP presentation page
The phone starts normally in download mode (am I saved?)
But it does not completely start in TWRP mode, it gets stuck on the presentation page (where there is the name of the team and the version number)
I tried installation other versions of TWRP with Odin but I still get stuck on the presentation page, although the version number changes adequatly to the version installed.
Please help me! :crying::crying::crying::crying::crying:
thank you.
Good news, is yes you can restore your device. Download your stock rom , unzip and flash in odin.
The is a dedicated thread on XDA for TWRP, in the steps the is a no-verity-opt-encrypt.zip which you should download.
Once you reach twrp again you should swipe to allow mod, then click on wipe, format data and type in yes when prompted.
After which flash the zip mentioned above. Now you will have access to the system in twrp, and flash whatever rom you like.
trust this helps
@soka said:
Good news, is yes you can restore your device. Download your stock rom , unzip and flash in odin.
The is a dedicated thread on XDA for TWRP, in the steps the is a no-verity-opt-encrypt.zip which you should download.
Once you reach twrp again you should swipe to allow mod, then click on wipe, format data and type in yes when prompted.
After which flash the zip mentioned above. Now you will have access to the system in twrp, and flash whatever rom you like.
trust this helps
Click to expand...
Click to collapse
thank you, I will try this later today and let you know how it goes!
thanks.
lass93 said:
thank you, I will try this later today and let you know how it goes!
thanks.
Click to expand...
Click to collapse
Best of luck buddy.
It worked thanks a lot man!
Now, onto the next step, I guess the tutorial I followed initialy was not good enought. So where can I get this "no-verity-opt-encrypt.zip", and how should I install it exactly? Unless I missed something, it is not explained in the xda tutorial
http://forum.xda-developers.com/s7-edge/development/rom-s7-edge-rom-v1-1-t3356699
Thank you all
Follow these instructions, the links for the latest recovery and the zip I mentioned are all there. If you need further help. I will help.
http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
You do have a G935F right?
@soka said:
Follow these instructions, the links for the latest recovery and the zip I mentioned are all there. If you need further help. I will help.
http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
You do have a G935F right?
Click to expand...
Click to collapse
Yes I do
Ok Thx. Will let you know!
lass93 said:
Yes I do
Ok Thx. Will let you know!
Click to expand...
Click to collapse
I Followed the instructions of your link, then I followed the instructions of the tutorial to install SuperMan ROM bug at the last reboot (after installation) I got stuck on the "Samsung Galaxy Edge 7" screen, the starting screen...
Hope I can install this ROM, I dont want to go back to stock.
Have you updated the modem and bootloader as dev instructed?
First initial boot will take time , remember you wiped everything but you Internal storage and SD card.
"9. Reboot and wait around 10 minute's (deodexed roms need longer to boot the first time)
10. Don't interrupt the process of booting the phone, even when it restarts"
How long did you leave it on the Samsung S7 Edge screen?
@soka said:
Have you updated the modem and bootloader as dev instructed?
First initial boot will take time , remember you wiped everything but you Internal storage and SD card.
"9. Reboot and wait around 10 minute's (deodexed roms need longer to boot the first time)
10. Don't interrupt the process of booting the phone, even when it restarts"
How long did you leave it on the Samsung S7 Edge screen?
Click to expand...
Click to collapse
Yes I followed the instructions and downloaded the too exact files he said, flashed it with odin
I wiped everything (even internal storage) but micro sd card
I left it more than 30 minutes.
One thing I did I'm not sure about, during root, I followed the tutorial (the link you gave me) to root and install twrp, during this step, I flashed both superSU and dm verity... step 11 ( http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084 ) Is that ok?
My method, that works for me is as follows :
Flash my stock firmware via odin.
Boot up, select OEM and USB debugging on.
Flash latest TWRP in odin.
Boot up phone, then switch off and enter recovery.
In recovery page i swipe to allow mod, select wipe /format data and type in yes when prompted.
Then , flash the no-verity zip.
I then boot up the phone normally and let it settle for about five min, switch off and get back into TWRP.
Now there shouldn't be any red error msg's in TWRP of cant mount. ( That is important ) otherwise rom wont flash properly.
After which i will flash a rom, most custom stock roms already have SU.
@soka said:
My method, that works for me is as follows :
Flash my stock firmware via odin.
Boot up, select OEM and USB debugging on.
Flash latest TWRP in odin.
Boot up phone, then switch off and enter recovery.
In recovery page i swipe to allow mod, select wipe /format data and type in yes when prompted.
Then , flash the no-verity zip.
I then boot up the phone normally and let it settle for about five min, switch off and get back into TWRP.
Now there shouldn't be any red error msg's in TWRP of cant mount. ( That is important ) otherwise rom wont flash properly.
After which i will flash a rom, most custom stock roms already have SU.
Click to expand...
Click to collapse
Exactly what I did except for the SU part that i mentionned. i asked on another Forum, they said there might be a problem with the zip I used. So i'm gonna try downloading a new zip for this ROM, but i can't find any alternative links...
I redownloaded the zip from the link in the tutorial, it worked!! thanks for your help!
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).
My phone is bootloader unlocked & rooted + TWRP but still using the original Nougat firmware from ZTE. Now, for some unexplained reason I cannot install any custom ROM that does NOT have Gapps incuded, like Resurrection Remix or similar slim ROMs without Gapps. TWRP just gives the usual can't install error.
Moreover, even if I install a ROm with Gapps successfully I cannot go past the 'Google verifying account' (have to wait for 24 hours) nonsense.
Any advise appreciated.
xectis said:
My phone is bootloader unlocked & rooted + TWRP but still using the original Nougat firmware from ZTE. Now, for some unexplained reason I cannot install any custom ROM that does NOT have Gapps incuded, like Resurrection Remix or similar slim ROMs without Gapps. TWRP just gives the usual can't install error.
Moreover, even if I install a ROm with Gapps successfully I cannot go past the 'Google verifying account' (have to wait for 24 hours) nonsense.
Any advise appreciated.
Click to expand...
Click to collapse
What's your TWRP version?
I guess you are installing the Universal Bootloader, right? Do you install a newer TWRP img after that?
Which are the ROMs that fail?
What's the failure error?
Have you ever formatted data? What's its filesystem?
Choose an username... said:
What's your TWRP version?
I guess you are installing the Universal Bootloader, right? Do you install a newer TWRP img after that?
Which are the ROMs that fail?
What's the failure error?
Have you ever formatted data? What's its filesystem?
Click to expand...
Click to collapse
Thanks for the response. I used Axon7 Toolkit for all actions, including boot unlocking (no idea which version Axon Toolkit installed). It also installed TWRP 3.1.1.0 alisa which I've had all the time.
The ROMs that failed were 'XenonHD-170609-Unofficial.zip' and 'Resurrection Remix' (RR-N-v5.8.5-20171108-axon7-Official.zip). Also I installed successfully 'A2017G(N-B06)_AROMA_SL!M2+DF!NR_by_raystef66.zip' which has Gapps included....but the problem was that I could not get past the google account verification, even though I know my google details. It says I had to wait 24 hours before signing in.
The failure error from XenonHD and Resurrection Remix ROMs was: Updater process ended with error: 7
Yes I formatted data each time I installed a ROM.
I don't know how to find out what the file system is.
xectis said:
Thanks for the response. I used Axon7 Toolkit for all actions, including boot unlocking (no idea which version Axon Toolkit installed). It also installed TWRP 3.1.1.0 alisa which I've had all the time.
The ROMs that failed were 'XenonHD-170609-Unofficial.zip' and 'Resurrection Remix' (RR-N-v5.8.5-20171108-axon7-Official.zip). Also I installed successfully 'A2017G(N-B06)_AROMA_SL!M2+DF!NR_by_raystef66.zip' which has Gapps included....but the problem was that I could not get past the google account verification, even though I know my google details. It says I had to wait 24 hours before signing in.
The failure error from XenonHD and Resurrection Remix ROMs was: Updater process ended with error: 7
Yes I formatted data each time I installed a ROM.
I don't know how to find out what the file system is.
Click to expand...
Click to collapse
I believe you forgot to flash the Universal Bootloader. That's an error on your end.
Basically, what the Universal Bootloader does is change your device's info to something 'universal' (it somewhat standardizes A2017s, A2017Us and A2017Gs into an intermediate so that you can flash any custom ROM on any of the 3). It also installs TWRP 3.0.2-N or sth like that. So basically you need to have TWRP-3.1.1-0.img on your phone, then flash the Universal Bootloader, then the modem for your device (get the latest from Raystef66's download center), then the ROM and whatever ZIPs you want to install (ALWAYS install SuperSU or Magisk or you'll get the internal storage encrypted and you'll have to format the internal storage every time you want to change ROM), and lastly Install Image - the TWRP.img - install to recovery partition.
You can get the Universal Bootloader from the LOS thread. There are also modem files for the 3 models but they are rather old, so just get the B09 modem from the download center
Choose an username... said:
I believe you forgot to flash the Universal Bootloader. That's an error on your end.
Basically, what the Universal Bootloader does is change your device's info to something 'universal' (it somewhat standardizes A2017s, A2017Us and A2017Gs into an intermediate so that you can flash any custom ROM on any of the 3). It also installs TWRP 3.0.2-N or sth like that. So basically you need to have TWRP-3.1.1-0.img on your phone, then flash the Universal Bootloader, then the modem for your device (get the latest from Raystef66's download center), then the ROM and whatever ZIPs you want to install (ALWAYS install SuperSU or Magisk or you'll get the internal storage encrypted and you'll have to format the internal storage every time you want to change ROM), and lastly Install Image - the TWRP.img - install to recovery partition.
You can get the Universal Bootloader from the LOS thread. There are also modem files for the 3 models but they are rather old, so just get the B09 modem from the download center
Click to expand...
Click to collapse
Thanks for your help and your suggestions. Will try a few things as I go along. Thanks again.
xectis said:
Thanks for your help and your suggestions. Will try a few things as I go along. Thanks again.
Click to expand...
Click to collapse
Just two things, you mentioned "and lastly Install Image - the TWRP.img - install to recovery partition". I already have TWRP 3.1.1.0 installed so did you mean to install it again after flashing the Universal Bootloader and modem?
Also, is this the correct link for the LOS thread you mentioned: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
xectis said:
Just two things, you mentioned "and lastly Install Image - the TWRP.img - install to recovery partition". I already have TWRP 3.1.1.0 installed so did you mean to install it again after flashing the Universal Bootloader and modem?
Also, is this the correct link for the LOS thread you mentioned: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Click to expand...
Click to collapse
Yes and no
The Universal bootloader flashes an old TWRP version. After you reboot and enter the recovery again you will get an old TWRP. So to avoid this you have to flash the Universal Bootloader and then TWRP 3.1.1 or 3.2.1
That's the download center... I mean the LineageOS thread over at the ROMs section. By Unjustified Dev
Choose an username... said:
Yes and no
The Universal bootloader flashes an old TWRP version. After you reboot and enter the recovery again you will get an old TWRP. So to avoid this you have to flash the Universal Bootloader and then TWRP 3.1.1 or 3.2.1
That's the download center... I mean the LineageOS thread over at the ROMs section. By Unjustified Dev
Click to expand...
Click to collapse
I see. All clear now. You've been most helpful, thank you again.
[/QUOTE]
xectis said:
I see. All clear now. You've been most helpful, thank you again.
Click to expand...
Click to collapse
Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.
Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.[/QUOTE]
You have to format the internal storage, because it is encrypted. Do this:
You need to have Magisk 15.1 or 14 or SuperSU 2.79 ready. I recommend the latest Magisk. If you have an SD card, put it there. If not, leave it on your PC and have the phone connected.
Go to TWRP, Wipe, Advanced Wipe, Format data. Be sure that it formats as ext4 (it will say 'formating using make-ext4fs or something, if it says f2fs then leave it format and then use Change filesystem to ext4).
Right after that, install Magisk. If you have the SD card it's easy, if you don't, try to connect the phone to the PC, if it appears as a mass storage option then put it there and flash it with Install. If it doesn't appear as mass storage use adb sideload
NEVER leave the phone without SuperSU or Magisk! If you change the ROM, ALWAYS install Magisk or SuperSU right after you install the ROM. Otherwise you'll have to format the internal storage again the next time you change the ROM.
Choose an username... said:
Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.
Click to expand...
Click to collapse
You have to format the internal storage, because it is encrypted. Do this:
You need to have Magisk 15.1 or 14 or SuperSU 2.79 ready. I recommend the latest Magisk. If you have an SD card, put it there. If not, leave it on your PC and have the phone connected.
Go to TWRP, Wipe, Advanced Wipe, Format data. Be sure that it formats as ext4 (it will say 'formating using make-ext4fs or something, if it says f2fs then leave it format and then use Change filesystem to ext4).
Right after that, install Magisk. If you have the SD card it's easy, if you don't, try to connect the phone to the PC, if it appears as a mass storage option then put it there and flash it with Install. If it doesn't appear as mass storage use adb sideload
NEVER leave the phone without SuperSU or Magisk! If you change the ROM, ALWAYS install Magisk or SuperSU right after you install the ROM. Otherwise you'll have to format the internal storage again the next time you change the ROM.[/QUOTE]
I did everything you suggested but I still get the 'To start Android use your password'. No wories I'll go back to my old ROM. Thanks anyway.
***Update*** I made a mistake in formatting SYSTEM instead of DATA. Now it works fine installing the ROM's I mentioned. You are a champ!
Now all I need is to somehow find a way to raise the in-call volume (ear speaker).
xectis said:
Now all I need is to somehow find a way to raise the in-call volume (ear speaker).
Click to expand...
Click to collapse
Try this
https://forum.xda-developers.com/axon-7/how-to/patch-enable-ak4490-hifi-dac-custom-rom-t3707738
It'll probably not work but you'll end up with the AK4490 anyways
Choose an username... said:
Try this
https://forum.xda-developers.com/axon-7/how-to/patch-enable-ak4490-hifi-dac-custom-rom-t3707738
It'll probably not work but you'll end up with the AK4490 anyways
Click to expand...
Click to collapse
Thanks for the link, however I recently discovered that with the 'XenonHD-170609-Unofficial' ROM the in-call volume is pretty loud as well as the sound from the normal sounding speakers. It also has just about everything I'd want in a lite ROM. So far it's the ROM I'll keep.
xectis said:
Thanks for the link, however I recently discovered that with the 'XenonHD-170609-Unofficial' ROM the in-call volume is pretty loud as well as the sound from the normal sounding speakers. It also has just about everything I'd want in a lite ROM. So far it's the ROM I'll keep.
Click to expand...
Click to collapse
Use the zip anyways
Choose an username... said:
Use the zip anyways
Click to expand...
Click to collapse
Ok I'll give it a try.