Related
This is a very simple device to root.
However if you root this device it will likely void your warranty.
There is no current method of obtaining S-OFF, so don't ask!
Requirements:
PC
Phone
USB Cable
External SDCARD (optional but highly recommended)
Internet Connection
HTC Drivers
Battery with a charge of over 50%
Ability to read
Ability to follow directions
Then you must view the following video!
If you meet these requirements then proceed to post #2.
Step #2 - Unlocking your bootloader
Copied from this thread by Revolution
Go to HTCDev.com
Make a account , here then go to this link and follow all instruction's , but make sure you go to this link , it don't show us as a supported device but this work's for all device's me & crackeyes have tried this .
Go to this link after that : here , follow all the step's , below will be my version .
1) Remove and reinsert the battery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Press Volume Down and Power to start the device into Bootloader mode.
3) Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
4) Connect the device to the computer via a usb cable
5) Make a folder in c:\ called Android & then input the file's from your android SDK their , such as
adb.exe
AdbWinApi.dll
fastboot.exe
6) Open up command prompt. ( Start > Run > Type CMD,). The window that appears is called Command Prompt.
7) Navigate to where you unzipped the ZIP file and go to the folder you just created (For Example: If you created the folder in C:\Android, then you would type in Command Prompt: cd c:\Android).
8) Type in Command Prompt: fastboot oem get_identifier_token.
9) You will see a long block of text. Copy and paste this text into the the token field below (in the command prompt: Right Click > Mark > highlight the block of text > Right click to copy).
10) Paste this string of text into the token field and hit Submit in order to receive your unlock code binary file. You will receive this information in your email.
Example:
11) On the bottom of http://www.htcdev.com/bootloader/unlock-instructions/page-3 , please input your result's & if it say's failed keep on trying & it will go threw .
Straight from HTCDev.com , & NOTE : THIS WILL VOID YOUR WARRENTY
You are about to start the process of unlocking your device. Unlocking your device allows you to install custom Operating Systems (“OS”) onto your device. Custom OS’s are not tested as thoroughly as your original OS, and unlocking your device may void all or parts of your warranty. HTC disclaims any and all liability for proper functioning of your device after the bootloader has been unlocked and for data lost in the unlocking process. To prevent unauthorized access to your data, unlocking the bootloader will delete all personal data from your device including applications, text messages and personalized settings.
Click to expand...
Click to collapse
Once you have unlocked your bootloader you can make changes to your /system partition.
The majority of you will probably never need to do this. This is because most developers use flashable zip files that will do everything for you. These files are flashed from Recovery Mode.
Let's move on to step #3
Step #3 - Installing Custom Recovery
Now that you have unlocked your bootloader you can now obtain root.
The easiest way to do this would be by installing a custom recovery.
I created a simple bat script that should update your recovery for you.
Boot up your phone and connect it to your computer by usb cable.
Go to Settings --> Applications --> Development.
Check USB debugging.
Unzip the attached file and run the Flash.bat file as Administrator.
Your phone should reboot and go to a white screen.
It should update the recovery for you automatically and reboot.
Now you should have yourself a custom recovery.
If by chance you decide that you would like to revert to the custom recovery then use the same technique with the STOCK_RECOVERY_FLASHER.zip file.
If a .bat script isn't your thing then try this thread: [TOOL] HTC Amaze 4G All-In-One Toolkit by Hasoon2000
Step #4 - ROOTING!
Now that you have your custom recovery installed it's time to flash root onto your phone.
Download a custom rom from the Development section or the HTC Amaze ROM Bible and store the zip onto your external sdcard.
If you do not want a custom rom but just want root simply download the attached Superuser-3.0.7-efghi-signed.zip file.
If you do not have an external sdcard then store it onto your internal sdcard.
The custom recovery from step #3 will default to an external sdcard if it's detected.
If the custom recovery from step #3 does not detect an external sdcard then it should default to your internal.
Now there are a couple different ways to reboot to recovery. The best way is to open the command prompt up and navigate to either directories from posts 1 or 2 that contains the adb.exe file.
For example this is from post #2.
If you stored it to your desktop directory then it would be something like:
C:\Users\Binary100100\Desktop\RecoveryInstallerForNoobs
so you may have to enter:
cd Desktop\RecoveryInstallerForNoobs
Now enter "dir" into the command prompt and press Enter and you should see something like:
c:\Users\Binary100100\Desktop\RecoveryInstallerForNoobs>dir
Volume in drive C has no label.
Volume Serial Number is 4850-996B
Directory of c:\Users\Binary100100\Desktop\RecoveryInstallerForNoobs
01/03/2012 05:04 PM <DIR> .
01/03/2012 05:04 PM <DIR> ..
11/08/2011 02:50 PM 366,661 adb
11/08/2011 02:50 PM 410,942 adb.exe
11/08/2011 02:50 PM 96,256 AdbWinApi.dll
11/08/2011 02:50 PM 60,928 AdbWinUsbApi.dll
11/08/2011 02:50 PM 127,435 fastboot
11/08/2011 02:50 PM 356,009 fastboot.exe
12/27/2011 12:37 AM 128 Flash.bat
12/27/2011 12:32 AM 5,187,584 recovery-cwm-ruby-5.0.2.7.img
8 File(s) 6,605,943 bytes
Click to expand...
Click to collapse
As long as you see adb, adb.exe, adbWinApi.dl and AdbWinUsbApi.dll you should be good to go.
Now without leaving the command prompt enter:
adb reboot recovery
Your phone should reboot and you should be looking at your recovery.
If for whatever reason you couldn't get access to recovery then go back to bootloader mode.
Remove the battery and put it back in. This is to make sure the device is completely powered off. Hold the Volume Down button while pressing power to get back to hboot mode. Just like step #1. Now if you don't see Recovery in the list then select BOOTLOADER. You should now see RECOVERY. Select that and your phone should reboot to recovery from there. Now that I know you're in recovery... let's move on.
From here you can flash your custom rom or root files.
Use the volume rocker buttons to move the highlight up and down the menu and highlight "Install zip from sdcard" then press the power button to select.
Now "choose zip from sdcard" then press power button again.
Highlight the downloaded custom rom or the Superuser-3.0.7-efghi-signed.zipfile and press power again. From here I think you have the idea.
Select the appropriate zip file and press the power button to install.
Now you can go back and then select "reboot system now" and let your device boot up.
Check the app drawer and make sure you have an app called SuperUser. If you have this app then you now have root.
If you followed the instructions like you were supposed to you should be fully rooted and unlocked the full potential of your HTC Amaze 4G phone.
Feel free to post your questions and comments here in this thread.
PLEASE! don't send me private messages asking for help. I just spent two hours making this as simple as I could to save me from all of the help requests. If you have problems then post in this thread and make sure to reference the step that you're having issues with.
Example:
Problem with Step #1 I can't follow directions. Someone do it for me. I'll be willing to pay $10,000,000 to have root.
Click to expand...
Click to collapse
Then I'm sure you will get plenty of help.
Remember to hit the thanks button to show your appreciation.
Thanks was wondering where the old sticky thread went!!! hopefully less questions with this one...It's much more clear.
seansk said:
Thanks was wondering where the old sticky thread went!!! hopefully less questions with this one...It's much more clear.
Click to expand...
Click to collapse
Which is exactly why I made it. Unfortunately the members that just got the device couldn't use the old PH85IMG.zip method because of the Main Version Older error and they couldn't use the tool that xboarder56 made because I had to remove it per request. I didn't want to make a tool that would do everything because then they would never learn for themselves. So I feel that this is a healthy balance.
Binary100100 said:
Which is exactly why I made it. Unfortunately the members that just got the device couldn't use the old PH85IMG.zip method because of the Main Version Older error and they couldn't use the tool that xboarder56 made because I had to remove it per request. I didn't want to make a tool that would do everything because then they would never learn for themselves. So I feel that this is a healthy balance.
Click to expand...
Click to collapse
good Idea I am having lots of flashing problems since 1.3 too, I didn't want to unlock it and I OTA'd...but then couldn't stand the bloatware and wanted more...now I'm having all kinds of problems, including kernel. so now If you could help me with the kernel, I posted question in general section, I'm kind of a semi-noob with kernels!!!!! lol
seansk said:
good Idea I am having lots of flashing problems since 1.3 too, I didn't want to unlock it and I OTA'd...but then couldn't stand the bloatware and wanted more...now I'm having all kinds of problems, including kernel. so now If you could help me with the kernel, I posted question in general section, I'm kind of a semi-noob with kernels!!!!! lol
Click to expand...
Click to collapse
Give me the link to your question and I'll do what I can to help.
Do you have access to fastboot and an unlocked bootloader?
Binary100100 said:
Give me the link to your question and I'll do what I can to help.
Do you have access to fastboot and an unlocked bootloader?
Click to expand...
Click to collapse
Yes, I'm familiar with all that stuff..unlocked and can get into fastboot. custom recovery is intact as well. here's the link: http://forum.xda-developers.com/showthread.php?t=1424757 post 8 and this almost the same http://forum.xda-developers.com/showthread.php?t=1328141&page=10 post 92....thanks you much in advance
Great job on this Binary!
IF PEOPLE HAVE PROBLEMS...you can always message me as well. BUT MAKE SURE TO READ AND FOLLOW DIRECTIONS FIRST...I'm am very familiar with all these procedures as well, just to take a load of binary and xboarder's backs...
seansk said:
IF PEOPLE HAVE PROBLEMS...you can always message me as well. BUT MAKE SURE TO READ AND FOLLOW DIRECTIONS FIRST...I'm am very familiar with all these procedures as well, just to take a load of binary and xboarder's backs...
Click to expand...
Click to collapse
Thank you very much! I don't have time to be 24/7 tech support.
jimczyz said:
Great job on this Binary!
Click to expand...
Click to collapse
Agreed. I wish this thread had been here when I rooted. It would have saved my hunting through 3 or 4 threads and trying to piece things together myself. Of course, I probably learned more that way.
marleyfan61 said:
Agreed. I wish this thread had been here when I rooted. It would have saved my hunting through 3 or 4 threads and trying to piece things together myself. Of course, I probably learned more that way.
Click to expand...
Click to collapse
I always encourage people to never stop learning.
When I see a script I like to open it up and see what's inside.
Knowing how things work is a great way to learn for yourself.
Before you know it, you'll be making guides like this! At the very least you'll be the A instead of the Q if you know what I mean.
Binary100100 said:
I always encourage people to never stop learning.
When I see a script I like to open it up and see what's inside.
Knowing how things work is a great way to learn for yourself.
Before you know it, you'll be making guides like this! At the very least you'll be the A instead of the Q if you know what I mean.
Click to expand...
Click to collapse
We both have the same curiosoty Binary...I alway open random files and probably break things before I fix them lol...my first computer was a packard bell 486 dx2 66 in 1993 I think. I learned everything I know by myself...including a lot of dos which we still use today for android . good old windows 3.1
Thanks a million!
I had lost my root to the most recent OTA update from t-mo, obviously I'm a noob when it comes to root only, everything else electronic wise I got the hang of. I'm not the type of person that likes things handed to me I prefer given the basic and expanding my knowledge from there, knowledge is a beautiful thing! I'm back rooted and again thanks for this post!
andyb0308 said:
I had lost my root to the most recent OTA update from t-mo, obviously I'm a noob when it comes to root only, everything else electronic wise I got the hang of. I'm not the type of person that likes things handed to me I prefer given the basic and expanding my knowledge from there, knowledge is a beautiful thing! I'm back rooted and again thanks for this post!
Click to expand...
Click to collapse
I'm glad that you found it helpful.
May be a Noob ? but I'm wondering since I use my phones hotspot to get internet on my laptop, if I can do this without the sim card in the Amaze, while using my other phones hotspot? I've searched and found no mention of this, thanks for the great guide.
Marquis63 said:
May be a Noob ? but I'm wondering since I use my phones hotspot to get internet on my laptop, if I can do this without the sim card in the Amaze, while using my other phones hotspot? I've searched and found no mention of this, thanks for the great guide.
Click to expand...
Click to collapse
As long as you have a PC connected to download the required files.
Sent from my HTC Amaze 4G using xda premium
I need someone to try this. I pulled the libs from Sprint HTC One 4.1.2 ROM and I need a tester. Can't answer for 4.2.2 yet. I did not make the zip but i placed the correct files in the zip.
If it doesn't work after the flash, you can use Root Explorer too push the individual files to the exact folder locations that are in the zip. See instructions below
BEFORE YOU START....DO A NAND BACKUP SO IF ANYTHING DOES GO WRONG, YOU CAN JUST RESTORE AND NOT HAVE TO FLASH AND SET YOUR WHOLE PHONE BACK UP.....I DEF RECOMMEND NOT SKIPPING THIS, BUT HEY SOME PEOPLE ARE COWBOYS TO INCLUDE ME.
NOTE: If you are on a 4.1.2 Sprint Based ROM like OMJ you can also try Trial Method 2 without flashing the libs to see if it will work. The 4.2.2 based ROMS from the HTC One FORUM may have the secure element already enabled and may not require the libs to be flashed, however I don't have any 4.2.2 libs I can pull and it may not be necessary. I need some testers. Your Secure element is not enabled or you need a lib fix if you get this Insufficient Secure Element Privileges for system image (release-keys).
Trial Method 1 - Patched Wallet - Sprint libs - Universal for 4.x.x Stock Sense Based ROMS - Need Confirmation
1. Download This Patched Version of Google Wallet
2. Use root explorer to push the Wallet.apk to system/app
3. Change permissions to rw-r-r
4. Change your build.prop to the Galaxy Nexus
Galaxy Nexus
ro.product.device=maguro
ro.product.model=Galaxy Nexus
ro.product.name=yakju
5. Reboot to Recovery
6. Install Sprint NFC Libs Test 1 fo 4.1.2 and 4.2.2 Test Ignore the name of the zips. We are in DEV phase need feedback before this begins to matter. (ALWAYS WIPE CACHE AND DALVICK BEFORE FLASHING ANY ZIPS).
7. Reboot Phone
8. Open and Set Up Google Wallet to 100% completion where you are ready to make a purchase. If successful move to next step
9. Change build.prop back to Stock upon successful set up of Wallet to Completion. At this point Wallet sets up all the way and you can make purchases.
AT&T HTC One
ro.product.device=m7
ro.product.model=M7
ro.product.name=m7
10. Reboot Phone
11. When Phone Boots up, Enjoy!
Trial Method 2 - Modaco Toolkit - Universal for 4.1.2 and 4.2.2 Sense Based ROMS like ViperOne ROM, Android Revolution HD, InsertCoin ect... - Need Confirmation
1. Install XposedFramework 2.1.4 (hit "Install" in the installer app afterwards). Xposed Framework Forum Found Here
2. Install MoDaCo Toolkit v26
3. Open Xposed Settings and Enable MoDaCo Toolkit Module
4. Change your build.prop to the Galaxy Nexus
Galaxy Nexus
ro.product.device=maguro
ro.product.model=Galaxy Nexus
ro.product.name=yakju
5. Reboot
6. Open MoDaCo Toolkit (Takes 5-10 Seconds Don't Touch Screen)
7. Click Google
8. Click Check Box to disable Root and Supported Locale Check of Google Wallet
9. Click Download Wallet APK or You can install from Google Market
10. Install APK you just downloaded unless you chose the Market Place (DO NOT OPEN AFTER INSTALL)
11. Reboot For Modaco Toolkit changes to take place
14. Set Up Google Wallet to 100% completion where you are ready to make a purchase. If successful move to next step
15. Change build.prop back to Stock upon successful set up of Wallet to Completion. At this point Wallet sets up all the way and you can make purchases.
AT&T HTC One
ro.product.device=m7
ro.product.model=M7
ro.product.name=m7
16. Reboot Phone
17. When Phone Boots up, Enjoy!
Screen Shots
Picture 1 - Step 6-7. / Picture 2 - Step 8-9
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Trial Method 3 - Modaco Toolkit - Sprint libs - Universal for 4.1.2 Stock Sense Based ROMS - Need Confirmation
1. Install XposedFramework 2.1.4 (hit "Install" in the installer app afterwards). Xposed Framework Forum Found Here
2. Install MoDaCo Toolkit v26
3. Open Xposed Settings and Enable MoDaCo Toolkit Module
4. Change your build.prop to the Galaxy Nexus
Galaxy Nexus
ro.product.device=maguro
ro.product.model=Galaxy Nexus
ro.product.name=yakju
5. Reboot to Recovery
6. Install Sprint NFC Libs Test 1 fo 4.1.2 and 4.2.2 Test If you get any force closes or issues after reboot....Do a nand restore of your Rom and do the process again but Download and flash Sprint NFC Lib Test 2 this time. Ignore the name of the zips. We are in DEV phase need feedback before this begins to matter
7. Fix Permissions in Recovery and Reboot
8. Open MoDaCo Toolkit (Takes 5-10 Seconds Don't Touch Screen)
9. Click Google
10. Click Check Box to disable Root and Supported Locale Check of Google Wallet
11. Click Download Wallet APK or You can install from Google Market
12. Install APK you just downloaded unless you chose the Market Place (DO NOT OPEN AFTER INSTALL)
13. Reboot For Modaco Toolkit changes to take place
14. Set Up Google Wallet to 100% completion where you are ready to make a purchase. If successful move to next step
15. Change build.prop back to Stock upon successful set up of Wallet to Completion. At this point Wallet sets up all the way and you can make purchases.
AT&T HTC One
ro.product.device=m7
ro.product.model=M7
ro.product.name=m7
16. Reboot Phone
17. When Phone Boots up, Enjoy!
The stock AT&T HTC One build.prop (Case Sensitive) so before you change your build.prop, record the current config for your device to ensure it matches what I have...The same 3 lines you change to the Galaxy Nexus you need to write down because after Wallet sets up Completely, you will need to go back to stock.
If you extract the ZIP files from the NFC Lib test because I am not 100% sure the files will flash to the correct directory, but you can manually push them and it may be a pain in the butt unless someone is great at making zips
Here is how you would manually push. DO THIS IF YOU FLASHED THE ZIP AND YOU GET INSUFFICIENT RSA KEYS OR SECURE ELEMENT MISSING ERRORS
1. Extract Zip to Desktop
2. Place folder on SD Card of Phone
3. Open Root Explorer and navigate to Folder on SD Card
4. Inside that folder on SD card will be a system folder, go Inside that system folder
5. You will see an "etc" and "lib" folder
6. Copy the nfcee_access.xml and navigate to the phones system/etc folder and copy it in there
7. Rename the current one you have to nfcee_access.xml.bak and then paste this one in the folder and change permissions to rw-r-r
8. Navigate to the Folder you copied to your SD Card
9. Go inside that system folder then look for the lib folder
10. Repeat the same steps but now you will navigate to the phones system/lib and copy the files
11. Rename the 3 individual files that are already there and add .bak like you did previously
12. Repeat the same step for the individual file thats on the SD Card in the system/lib/hw folder
13. Make sure the files all have rw-r-r permissions
14. Once all are copied then you can reboot and follow the Trial instructions above to install Wallet
THIS WAY IS A PAIN IN THE ASS BUT IF IT WORKS IT WORKS
Troubleshooting And Development
reserved
Thought people would be more all over this, its perfectly safe to try, need some feedback because I would like to have working Wallet for everyone.
I would love to test it but I'm on 4.2.2
Looking forward to seeing the progress. Would love Google Wallet on my HTC. =/
Hoping to see that it will work on 4.2.2, 4.3, etc.
Taking donation?
Sent from my HTC One using Tapatalk 4
greenrocks said:
I would love to test it but I'm on 4.2.2
Looking forward to seeing the progress. Would love Google Wallet on my HTC. =/
Hoping to see that it will work on 4.2.2, 4.3, etc.
Taking donation?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
You can give it a try on 4.2.2, just do a nandroid backup so if you have an issue you can restore like nothing ever happened
Okay, will give it a try later. Will let you you know.
Sent from my HTC One using Tapatalk 4
greenrocks said:
Okay, will give it a try later. Will let you you know.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Ok, I am adding an aditional zip to try....Do the first one still, but if you get any force closes or error flash the 2nd one after you do a nand restore.........
I am also on a Sense based 4.2.2 rom (CleanROM to be exact) but I'll give this a whirl!!!
K.AuthoR said:
I am also on a Sense based 4.2.2 rom (CleanROM to be exact) but I'll give this a whirl!!!
Click to expand...
Click to collapse
Ok I updated OP, just have to ignore the names of the zip files....
I got all the way to step 5, installed zip and fixed permissions which took a good 5 minutes, clicked reboot in cwm, then my phone rebooted into a black abyss of the backlight blinking and the buttons blinking with and without the backlight blinking. Needless to say I'm a bit scared right now, this is my first non-Nexus phone. I lost all faith until I got to Hboot for a few seconds so I sent it back to CWM where I'm now restoring my backup. I feel like as long as Hboot is safe I'm good, but that really bugs me.
Putting the brakes on for tonight, I'll give it another shot tomorrow. If I didn't require my phone for work I wouldn't be as cautious about anything, I've honestly even been reluctant to S-Off the thing.
tldr - I am using CleanRom, not stock, so that could have also caused my issue. Will keep checking this thread out and offer future testing if necessary.
K.AuthoR said:
I got all the way to step 5, installed zip and fixed permissions which took a good 5 minutes, clicked reboot in cwm, then my phone rebooted into a black abyss of the backlight blinking and the buttons blinking with and without the backlight blinking. Needless to say I'm a bit scared right now, this is my first non-Nexus phone. I lost all faith until I got to Hboot for a few seconds so I sent it back to CWM where I'm now restoring my backup. I feel like as long as Hboot is safe I'm good, but that really bugs me.
Putting the brakes on for tonight, I'll give it another shot tomorrow. If I didn't require my phone for work I wouldn't be as cautious about anything, I've honestly even been reluctant to S-Off the thing.
tldr - I am using CleanRom, not stock, so that could have also caused my issue. Will keep checking this thread out and offer future testing if necessary.
Click to expand...
Click to collapse
I have had that happen before, next time don't fix permission I am not a cwm fan. If you get the same results next time then try zip 2. It won't hurt the phone
Sent from my SGH-T889 using xda premium
Something else I just noticed, now when I reboot my phone or cold boot, the HTC logo has the "this build is for developmental purposes only" red text printed at the bottom. That was not there before I made this attempt.
Any idea what causes that?
edit: I don't recall if I had the 'fast boot' option enabled or not so my device might have been just doing fast boots before and skipping the HTC logo. Regardless, I have not seen this before unless I was entering recovery.
K.AuthoR said:
Something else I just noticed, now when I reboot my phone or cold boot, the HTC logo has the "this build is for developmental purposes only" red text printed at the bottom. That was not there before I made this attempt.
Any idea what causes that?
Click to expand...
Click to collapse
That happens when you flash a custom recovery
I believe once you go s-off, there are ways to get rid of that message, but it does no harm....
K.AuthoR said:
I got all the way to step 5, installed zip and fixed permissions which took a good 5 minutes, clicked reboot in cwm, then my phone rebooted into a black abyss of the backlight blinking and the buttons blinking with and without the backlight blinking. Needless to say I'm a bit scared right now, this is my first non-Nexus phone. I lost all faith until I got to Hboot for a few seconds so I sent it back to CWM where I'm now restoring my backup. I feel like as long as Hboot is safe I'm good, but that really bugs me.
Putting the brakes on for tonight, I'll give it another shot tomorrow. If I didn't require my phone for work I wouldn't be as cautious about anything, I've honestly even been reluctant to S-Off the thing.
tldr - I am using CleanRom, not stock, so that could have also caused my issue. Will keep checking this thread out and offer future testing if necessary.
Click to expand...
Click to collapse
I have had that happen before, next time don't fix permission I am not a cwm fan. If you get the same results next time then try zip 2. It won't hurt the phone.
For the red text, this won't touch the bootloader, that has been there you haven't noticed it, that is binary and you can fix that only in bootloader. Flashing zips will not make that happen. This happens as soon as you unlock your bootloader and run custom Roms
Sent from my SGH-T889 using xda premium
Gotcha. I was just running with the 'fast boot' power option enabled and never happened to see my HTC logo again after incorporating S-Off into the picture. lol
K.AuthoR said:
Gotcha. I was just running with the 'fast boot' power option enabled and never happened to see my HTC logo again after incorporating S-Off into the picture. lol
Click to expand...
Click to collapse
Their is a fix for it in the HTC One international thread I used it before but I don't know if the bootloader version has updated since
Sent from my SGH-T889 using xda premium
bdorr1105 said:
Their is a fix for it in the HTC One international thread I used it before but I don't know if the bootloader version has updated since
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Interesting - do you have a link for the specific thread in the forum?
I'll give this Wallet fix another goaround tomorrow when I'm home from work.
K.AuthoR said:
Interesting - do you have a link for the specific thread in the forum?
I'll give this Wallet fix another goaround tomorrow when I'm home from work.
Click to expand...
Click to collapse
Go here
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my SGH-T889 using xda premium
So for 4.2.2 roms, there are no libs to download?
Tried based on method 2 and same results as always, just sits and spins at Setting up Wallet, this may take up to 5 min and then terminates.
The issue that has been previously address is the belief that we will not be able to have Google Wallet because we don't have a secure element(this is why the GE, DEV and US variant phones) can't get or install.
I'm willing to be a tester but I think the results are always going to be the same, fail due to no secure element.
nest75068 said:
So for 4.2.2 roms, there are no libs to download?
Tried based on method 2 and same results as always, just sits and spins at Setting up Wallet, this may take up to 5 min and then terminates.
The issue that has been previously address is the belief that we will not be able to have Google Wallet because we don't have a secure element(this is why the GE, DEV and US variant phones) can't get or install.
I'm willing to be a tester but I think the results are always going to be the same, fail due to no secure element.
Click to expand...
Click to collapse
I have seen instances where it has worked on viper with screen shots....
The Sprint One has the secure element it's not blocked by the carrier and my boy has it. You can try trial 1 and flash the zip it has the libs from sprint off a 4.1.2 based Rom. I would do a nand back up incase it puts you in a boot loop. Give trial 1 a try.
Sent from my SGH-T889 using xda premium
I successfully installed Android Revolution 9.3 recently so thought I'd give some details for reference to anyone else it might help as I made a mistake (on purpose of course, just to make things interesting!) and encountered a few road blocks that made things a little tricky. I've not posted here many times and wouldn't claim to be an expert but have quite a bit of experience with Android (Kindle Fire was my first device to which was an uphill struggle all the way) and other tech experience with PC's and some Linux OS.
If you have a device with different specifications please be very careful when it comes to downloading and using software on your device. Doing so with the incorrect software (eg. software for a different device, wrong CID number...) can be disastrous so please be careful - soft-bricking is one thing but a hard-brick is always possible if you don't pay careful attention.
If anything here doesn't make sense or there are processes you don't understand, step back and re-consider before doing anything. You carry out these procedures at your own risk and I accept no liability. Think, think and think again, it's worth taking the time.
First things first, I have an HTC One m7 that I rooted and custom ROM'd almost as soon as I got it, so Root access is a pre-requisite for these procedures and everything described here is done with a Windows operating system.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
If you don't know what “Root Access” is or need help with it, here's a great guide and there is an abundance of other information on XDA for just about any question you might have.
I originally flashed TWRP 2.6.0.1 Custom Recovery and installed Trickdroid 11.0.0, an excellent, customisable ROM that gave me almost no problems apart from APEX Launcher not working, NOVA Launcher works brilliantly though. I haven't found any direct upgrades (please correct me if I'm wrong) but as it stands it's still a very smooth and stable ROM. My other interest was to improve my phone through firmware upgrades, which is a different process from those described here and require S-OFF (Security Off) unless you're using OTA (Over The Air) Updates, which requires a locked bootloader!
Initial Upgrade Problems
I'm quite fastidious when it comes to these things, researching, collecting and organising everything I need before hand so I was pretty annoyed that I missed the note towards the bottom of the Android Revolution HD (ARHD) page where it states that TWRP 2.6.3.3 or newer is required - I can confirm this is indeed the case! I also did a data wipe in TWRP before starting the AROMA installer - not sure this was problematic but it probably didn't help and certainly wasn't necessary so I would advise against doing that.
Whilst the AROMA installer completed apparently successfully (apart from one “error” message - set_perm: some changes failed), it became very clear it was not successful when the phone failed to boot normally and instead simply booted into Recovery every time. I was quite worried I was in dire straits because I didn't have any back up or alternative ROM on the SD card at the time, and was about to discover the joys Windows 8.1 brings to certain processes - more on that later.
So I was faced with a semi-useless phone that allowed me to get into the bootloader and Recovery but not much else, however it's a credit to TeamWin because TWRP continued to function flawlessly, despite my best efforts to screw everything up! No variation or combination of wiping outside of or in AROMA and re-installing ARHD achieved anything new - the partitions weren't mounting or being read correctly (the usb partition in particular “could not be mounted” according to TWRP), so it was clear I was sufficiently over the edge and needed to back up before I did any permanent damage.
Solutions
All of the steps I took may not be absolutely necessary, but because it was quite screwed up I was very keen to wipe the slate and get everything back to a point I was happy everything was fully functional.
The first problem was that fastboot was not working from the bootloader, by which I mean I was unable to use fastboot commands from Windows, and the phone wasn't recognized by the Device Manager, regardless of driver's installed, which I knew were correct - this was a Windows 8.1 quirk, however while the phone was in Recovery I was able to communicate via adb.
So connected to the computer, I opened a command prompt: simplest way to do this is opening the folder where adb is on your computer, which is usually your main hard drive eg. C:, where an adb folder will have been created during the installation of the tools, right-clicking in that folder with the SHIFT key held down, then selecting “Open command window here”:
C:\adb>adb push Trickdroid.zip /sd/
[If you don't follow that method, you simply have to open a standard Command window and navigate to the location of your adb folder eg. C:\>cd adb]
NOTE: the "/sd/" command at the end here is important as it tells adb the location for the file to go on your phone (the internal SD card). I've seen this push command in other tutorials without this part and the operation has failed.
You'll get a few lines in the command prompt window confirming the process starting and completing.
Then I followed the usual installation procedure for a custom ROM through TWRP (Install> Select Trickdroid .zip) - I used this ROM because I had it to hand and knew it worked.
Once the install was completed I had a functional phone again and could start to rebuild the shattered pieces of my pride. As mentioned before, I didn't have a backup on the phone - this was because I lost my original stock backup thanks to a self-destructing hard-drive (avoid Seagate hard drive's), so I started to hunt around. Thanks to the wonderful contributor's of XDA I found some excellent resources, but which you use depends on your preferred approach, and what you want to achieve but here are a few.
MIKE1986's STOCK ROM's
RUU Collection's
Nandroid Collection's
HTC Guru's Reset
Keep in mind - each of these resources have very important and specific processes that go along with each of them, so be very careful when it comes to using them.
Windows 8.1 Quirks
Windows 8.1 (originally) had some difficulty talking to attached Android devices through fastboot, and whilst having the correct HTC drivers is vital, I found a thread relating to a Windows Registry issue, requiring a Windows Update (which you may have already received) and an update to the Windows Registry (which is crucial).
Installing HTC Sync will give you the relevant drivers, but the program itself can interfere with many processes, plus it's a bit rubbish so if you uninstall it (just HTC Sync Manager) from the “Uninstall Programs” application in the Windows Control Panel, you'll just be left with the drivers and no unnecessary bloatware on your computer.
There's a simple download and instructions on how to apply the relevant changes to the Windows Registry which can be found here. If you haven't done anything like this before it can look quite intimidating but rest assured, follow these instructions to the letter and you'll be fine, maybe don't try screwing around with the other registry files though!
Recovery - Refresh and Upgrade
Whilst trying to get the phone to boot (in it's semi-disabled condition) I played around with the backup functions in Recovery, which unsurprisingly didn't work. I also deleted some of the folders within the TWRP “Backups” folder, thinking they might be confusing or causing some conflict.
So, to start afresh, I flashed a stock recovery, which can be found here.
Your phone needs to be in fastboot mode and attached to your computer - power off, then hold the volume down button and power button until the bootloader opens. Your recovery image needs to be in the adb folder, preferably named “recovery.img”. Open the Command Prompt for adb (right click in the adb folder whilst holding the SHIFT key) and flash the .img file over to the phone.
C:\adb>fastboot flash recovery recovery.img
Again you'll see a few lines in the command prompt window confirming the process starting and completing, once it's done shutdown and reboot the phone.
Of course the stock recovery isn't much use in terms functionality, and this process effects the ROM, essentially re-setting it - your SD will be fine but if you had eg. text messages, they'll be deleted so back anything like that up before doing this.
I shut down and re-booted once more just to be sure everything was ok, and then flashed the custom recovery in the same way as the stock, but now was the time to jump to a more up to date TWRP (or recovery of your choice) - I went with 3.0.0 in this case. Delete the stock recovery from the adb folder, then save the new custom recovery .img file (again re-naming it to “recovery.img”) in the same folder before fastboot flashing with the command prompt window:
C:\adb>fastboot flash recovery recovery.img
Sweet, now we've got a lovely new TWRP that looks a little different than the old version but with the same wonderful UI and functionality, and a few extras. The first time I booted into Recovery it asked me if I would like TWRP to be able to write onto the phone, or remain as “read only”. Whilst you might want to do this, there's no real reason and it kind of defeats the purpose of the recovery, plus you're not going to be able to do a backup or install files so just agree to that and you're good to go.
TWRP Information & Resources
System/ROM
Now running smoothly I was ready to upgrade, but to ensure there were no unpleasant ghosts in the system I went back to a stock ROM first. There's a variety of options as mentioned earlier, including any backup you may have saved yourself, but I went with a stock ROM provided by mike1986 this time which can be found here, whose incredible work and contributions can't be underestimated.
[NOTE: This *STOCK* ROM is NOT the same as the “out of the box” system my phone originally came with, which was 4.1.2 “Jellybean”, HTC Sense 5.0, however it served the purpose of wiping the phone slate clean to a stock system.]
I used the deodexed 6.09.401.12 - basically the difference between odexed and deodexed is the .apk structure - it's most specifically related to modifications and avoiding conflicts in the ROM. Here's a thread if you want to learn a bit more about it.
So just like any other ROM, copy the .zip file onto the SD card - simplest way to do this is having your phone connected to your computer, open up the browser window and navigate to your SD card, selecting a suitable location, just make sure you know where it is! (You can push it over via adb but it's really not necessary.) Then boot into Recovery, click Install, navigate to the .zip file location and select One_6.09.401.12_deodexed.zip (or whichever one you're using), then swipe to install.
The AROMA installer will kick in so just follow the on-screen instructions, reading each step carefully and soon you'll have the ROM installed with the usual Root access.
Don't forget the first boot after an install like this takes some time - that's completely normal, including an “Optimizing Apps” window before you get to the home screen so just be patient.
If you want to stop here then obviously that's your choice, however if you wanted to get/use OTA updates you'd need to follow some other steps to be totally stock, including locking your Bootloader, and there's a wealth of information here if that's your aim.
Custom ROM
Onto the Custom ROM of your choice - I recommend you do some research and check out reviews to find what you like the look of, but I've gone with mike1986's Android Revolution HD this time round. Download the ROM .zip and just like before, move it to your phone's SD card (no point in keeping the Stock ROM on the phone as well so delete that first to free up space, though you might want to keep it on just in case until the upgrade has completed successfully).
Reboot into Recovery via the bootloader, click Install and navigate to the .zip file, select Android_Revolution_HD-One_93.0_ef29f7.zip and swipe to install, carefully following the steps in AROMA and installing according to your preferences.
Once again after completion, reboot and be patient whilst the first boot runs its course and you're all set!
Don't forget you'll need to install the Xposed Framework to take full advantage of the Sense Toolbox within ARHD, without it simply won't work fully - it will work at a basic level but you'll get a warning/notification that you don't have full functionality. You can find lots of detailed information about this here - read it carefully because again, the correct software for your phone is very important - basically you need the latest installer, which is an .apk, and the relevant .zip files for your device.
For my phone (HTC One m7 - Quad-core 1.7 Ghz Snapdragon (Krait) 600 CPU, ARMv7 Soc (2Gb RAM) ARM CPU), one of the packages wouldn't install, claiming it wasn't correct for my device. Why exactly I'm not sure (because I absolutely, positively got the right packages!) so I'll update this when I know more, however the Xposed Framework software has worked fine since then, I'm not getting any error messages, it's all up to date and working fine.
That's it! Explore you're new ROM and enjoy. I hope this is helpful, if you've got any questions feel free to ask and I'll do my best to help. Much credit and thanks go to the people I've looked to for advice, and who have done incredible work compiling, modding and hosting the files used for these processes.
Thank and donate whatever you can to them so they can continue the sterling work.
Particular thanks to:
Mike1986
crushalot
matt95
sToRm1nG
… and anyone else in the XDA-Developers community I haven't named specifically but have been exceptionally helpful in sharing their knowledge and resources.
----------------------- Thread MODIFICATION LOG -----------------
Shout out to Nevertells2 and DoubleStuff who both worked hard on this documentation in 2017. ( Some of which still remains )
Date:03/10/2017 Users: DoubleStuff/Nevertells2
Modification Description: Initial Release.
05/25/2019 DoubleStuff
Major changes in 2019: updated broken ROM/GApps by including HP_TOUCHPAD's master list of ROM/GApps, also fixed the YouTube broken link, made many additions to the documentation as per the changing landscape of the HP Touchpad development, most notably HP_TOUCHPAD's HpTp Universal Optimize Swap Settings and boot.img file.
07/08/2019 DoubleStuff
Created a Main Menu, with 2 options 1) Wipe All and 2) HP ToolBox.
8/3/2019 DoubleStuff
Implemented HP_TOUCHPAD's ROM_Reducer flash files.
8/27/2019 DoubleStuff
On the 2nd Post of this thread I added DoubleStuffs annotated journeys.
8/27/2019 DoubleStuff
On the 3rd Post of this thread I added HP_TOUCHPAD's advanced topic of the HP TOUCHPAD Novacom Repair Android Tool.
----------------------- Previous Zip Statistics -----------------
"The Original"
Obsoleted doubleStuff_v03.zip 3/19/2017 - 5/25/2019 ( RIP )( 797 days )( 7876 downloads )( 53306 views )
Avg. 9.87 downloads/day
"Double Stuff II"
Obsoleted DoubleStuff.2019.zip 5/25/2019 - 7/8/2019 ( RIP )( 045 days )( 372 downloads )( 3140 views )
Avg. 8.26 downloads/day
----------------------------------------------------------------------
Introduction:
In this "new" ( circa 2019 ) method of "starting from scratch", or called "clean installing", the user will flash various ZIP files depending on the ROM version user wants to install.
The actual install of Automatic_Wipe_All_and_Create_Android_with_Swap_Partition.zip ( boot.img ) will be done by the the script TPTB_WipeAll_TWRP_v02_win.bat. Wipe_All creates a 500 Mb swap partition, and re-creates the system, cache, media and data partitions with sizes of 2200 Mb, 200 Mb, 500 Mb, and "rest of memory" respectively, also automatically installs version 3.2.1-0 of TWRP which is required for the other ZIPs.
Boot partition is always 32 Mb, its a fixed size.
To be clear: this method will erase everything, even WebOS and makes the HP Touchpad 100% Android. It will also create new media, cache, data, system and SWAP partitions, and make the HP Touchpad work as a tablet ( laptop with a touch screen ), not a smartphone in Android.
Thoughts about the video:
The Video is now semi-obsolete, because alot has changed since 2017. So you must follow the instructions in this updated thread, but the video helps because if you understand the video you will understand the instructions in this thread. The Video below is Installing Nougat, but you can use this method for ALL VERSIONS of Android since 4.4 just use the proper ZIPs.
https://www.youtube.com/watch?v=KDu1bocZHqw
Assumption:
This method assumes you already loaded and have working TP Toolbox v0.42. ( w/Novacom and Java )
--- if you don't have TP Toolbox installed on your PC please watch the video in RolandDeschain79's link from 0:00 to 2:15 RolandDeschain79Link
======================================================================
Steps to success for loading any version of Android since 4.4:
Perform the following steps on a PC to prepare it for load:
I. Download the NEW DoubleStuff.7.2019.zip:( click link below )
Download DoubleStuff.7.2019.zip
DoubleStuff.7.2019.zip contains these two key files:
1. TPTB_WipeAll_TWRP_v02_win.bat
2. uImage.WIPE
Download and extract, and place both files in the same directory as your working tptb_v42_win.bat on your PC.
II. Select and Download which version of Android ROM, Gapps and other zips you want.
Locate and download the ZIPs: I will link to HP_TOUCHPAD's Master List of Zips: ( see Master list link below ), but you can also find ZIPs in other XDA HP Touchpad threads too.
Its best to put your downloaded ZIPs into a storage folder that you have created on your PC, purely for organization.
#1 ) ROM
#2) Pick one of these three Settings files for this #2 ZIP install: These files are in the "ALL files for this ROM" zip, then look under a folder of the same name, and then select the frequency zip of your choice.
-- MAX_Kernel_Ramdisk_build_prop_Settings ( Latest HpTp_MAX_Universal_Optimize_Swap )
-OR-
-- Stock_Kernel_Changed_Ramdisk_build_prop_Settings ( HpTp_Universal_Optimize_Swap )
-OR-
-- Original_ROM_Settings ( Use the Tablet with phone settings, no swap partition )
( The first two are the magic behind the performance and speed, because these settings enables Android to use the swap partition, the third is the original settings for the ROM and you will have better battery performance. )
All the Universal Optimize Swap Settings files provide the same settings and kernel, the difference is the preset CPU frequency. As per the Boost settings always start with 1674, and after that is working good, you can try to flash a higher frequency for speed like ( 1728, 1782 or 1836 ), and you don't have to re-flash all the ZIPs again, just the UOSS file from TWRP recovery. If it freezes screen, or keeps rebooting just go back and flash lower frequency, Because those symptoms are telling you that your particular HP TOUCHPAD can't handle the higher speed.
#3) ROM Reducer ( Optional ) These files are in the "ALL files for this ROM" zip, then look under the folder with name "ROM Reducer" then out of the 3 zip files in the selected folder, first go with the ROM_reducer, later if you want to permanently remove the features/apps, or restore the features/apps, you can use the "Remove" and the "Restore" zip files.
Essentially this HP Touchpad ( circa 2011 ) has around 650 MB of free RAM (Memory), this is relatively low, so the ROM Reducer flash file "removes" some Android Features and System Apps to give the old Touchpad some extra needed RAM. So in theory this will make for a faster experience.
#4) GApps
Select platform ARM and the android version that matches ROM and the variant you want, Pico is recommended. The goal is to keep the system "lean and clean", and by doing this you will get the best performance and efficiency.
#5) SuperSu v2.82 ( Optional )
ROMs have system Read and Write enabled, download and flash SuperSu v2.82 if you want root access.
#6 ) Latest TWRP ( Optional, but if you want and/or need a different version of TWRP other than 3.2.1-0, then you need to download one. )
==========HP_TOUCHPAD's Master Link: Get ZIP ( #1, #2, #3, #4 here )===========
Note: Once you click link, you have to press page down 3 times to get to the Master List of Zips.
Find all Android version: Rom, GAPPS, HpTp MAX Universal Optimize Swap Settings, and more links as per HP_TOUCHPAD here:
================Get ZIP ( #5 here )=============================
***You can Download and Flash the latest SuperSu zip to ROOT your device***
Root access with SuperSu v2.82
http://www.supersu.com/download
================Get ZIP ( #6 here )=============================
This "latest and greatest" TWRP for ALL VERSIONS OF ANDROID.
Download Permanent TWRP Recovery.
FLINTMAN-TWRP-3.2.1-0-03-15-2018.zip
Stick with the package you select, don't mix and match versions, and stay with WIFI version unless you know better.
Set all ZIPs that you have downloaded into the storage folder on your PC for now, we will need them later.
III. Touchpad/PC Execution steps:
Boot into WebOS Recovery ( giant USB symbol ) with cable connected to PC.
Run the custom script TPTB_WipeAll_TWRP_v02_win.bat:
It will give you the option of running the TPTB where you can perform some maintenance steps. Most users will select '1' to run WIPEALL from Main Menu.
III. Touchpad/PC Execution steps: continued
Most users will START here, after pressing '1' in Main Menu.
Continue ( press "c" ) with the TPTB_WipeAll_TWRP_v02_win.bat, it will then load the uImage.WIPE, you should see a quick blue flash, and an orange header with some white text. Wait until the orange header disappears, it will then automatically reboot. ( about 2 minutes ).
At reboot, select Recovery on moboot menu, then press home key.
Wait, and you will see the automatic load of 3.2.1-0 TWRP recovery.
Wait, and you will see Touchpad drive mounted on your PC.
TWRP recovery automatically creates a folder in the /data/media directory called TWRP, on the Internal SD card ( data ).
IV. TWRP Install steps:
( If screen falls asleep, and power and home buttons don't respond, tap screen )
Once in TWRP Recovery, go to your PC which is still connected via cable to TouchPad:
Locate the storage folder on your PC where you stored your ZIPs.
Copy the ZIPs: ( drag and drop )
1) ROM, 2) Universal Optimize Swap Settings 3) ROM Reducer 4) Gapps, 5) SuperSu and 6) Permanent Recovery zip files into the /Touchpad/InternalStorage/TWRP mounted Touchpad volume.
( P.S. actually you can copy the zips anywhere in 'Internal Storage' or 'Micro SDCard' Touchpad mounts, as long as you know where to find them on your Touchpad, I am just giving you the default location for simplicity sake )
2) Once copy is complete, you can disconnect the USB cable from the PC and Touchpad.
3) These zips will then show up in the /sdcard/TWRP or /data/media/TWRP directory on your Touchpad.
4) Select INSTALL from TWRP, drill to /sdcard/TWRP directory, then load in this specific order ( pressing 'add more zips' between loads )
== ROM,
== HpTp Universal Optimize Swap Settings,
== ROM Reducer,
== Gapps,
== SuperSu
== Recovery TWRP
then swipe to flash.
It will take awhile for the system to flash these zips ( about 5 mins ) until the reboot option shows up.
press reboot system button
At Moboot menu I selected "boot Evervolv" your menu item might be a different name depending on the ROM you installed.
During my experimental testing I loaded Evervolv Nougat and it took about 15 additional minutes until I got to the Android Start screen after "boot Evervolv" selected. Mileage may vary.... but soon your HP Touchpad will be in the promised land of Android with swap.
Advanced Topic #1:
DoubleStuff's Journeys to Novacom Repair Android Tool and Universal Authority: ( with annotated pictures!! )
Journey #1: How files get populated to /boot.
Journey #2: into HP RAMDISK: Using /boot from uImage
Journey #3: to Novacom Repair Android Tool: How are the icons made
Journey #4: Exploring Planet Universal Authority
Journey #5: RAM Memory Stress Test
...
..
Advanced Topic #2:
HP Touchpad Novacom Repair Android Tool
Hello Touchpad users, if you think your HP TOUCHPAD is bricked, your probably wrong and with the tools below you maybe able to fix your HP TOUCHPAD and make it like new again. Read the guide, and download the ISO file, now remember this is an advanced topic, its not for kids. Trix are for kids.
click HERE for guide
click HERE to download ISO file
...
..
Doublestuff, bringing this to this thread since I am using your instructions to get this far.
After using the 4/13 nightly and getting setup wizard has stopped I tried the 4/6 as indicated below.
The steps I have taken are to use tptb_v42_win.bat for the toolbox to wipe the data then resize volumes to
--Media: 1024 MB,
--Cache: 200 MB,
--System: 1312 MB,
--Data: the rest of the memory
Then after shutting that down and bringing up the big USB symbol using the volume and power button again to run TWRP_TmpLoad_v03_win.bat and copy the files below into the TWRP folder on the touchpad.
ev_tenderloin-7.1.2-nightly-2017.04.06.zip
open_gapps-arm-7.1-pico-20170415.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-3-24-17.zip
Once the files were copied over I disconnected from the PC and added to the install in the order above.
The install indicates no MD5 so a check is skipped and seems to proceed to install each of the three zips fine. When I get to the end of that there are two buttons (one to wipe cache/DavLik and the other to Reboot). I tried both with and without the wipe cache before the reboot with the same results.
After the Evervolve logo with the cycling colored letters goes for a few minutes it gets to the setup screen, clicking on either copy settings or start new setup give the error "Setup wizard has stopped, Open app again" then "Setup wizard keeps stopping, close app".
The only difference I can see I resized the Media to 1024 where your instructions indicate 1000 but I cant see that as being any problem though to be honest my knowledge here is limited.
Any ideas for something else to try are appreciated.
----------------------------------------
This part I dont think I am understanding
"but remember later on you still have to load the permanent TWRP with install."
W_three said:
Doublestuff, bringing this to this thread since I am using your instructions to get this far.
After using the 4/13 nightly and getting setup wizard has stopped I tried the 4/6 as indicated below.
The steps I have taken are to use tptb_v42_win.bat for the toolbox to wipe the data then resize volumes to
--Media: 1024 MB,
--Cache: 200 MB,
--System: 1312 MB,
--Data: the rest of the memory
Then after shutting that down and bringing up the big USB symbol using the volume and power button again to run TWRP_TmpLoad_v03_win.bat and copy the files below into the TWRP folder on the touchpad.
ev_tenderloin-7.1.2-nightly-2017.04.06.zip
open_gapps-arm-7.1-pico-20170415.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-3-24-17.zip
Once the files were copied over I disconnected from the PC and added to the install in the order above.
The install indicates no MD5 so a check is skipped and seems to proceed to install each of the three zips fine. When I get to the end of that there are two buttons (one to wipe cache/DavLik and the other to Reboot). I tried both with and without the wipe cache before the reboot with the same results.
After the Evervolve logo with the cycling colored letters goes for a few minutes it gets to the setup screen, clicking on either copy settings or start new setup give the error "Setup wizard has stopped, Open app again" then "Setup wizard keeps stopping, close app".
The only difference I can see I resized the Media to 1024 where your instructions indicate 1000 but I cant see that as being any problem though to be honest my knowledge here is limited.
Any ideas for something else to try are appreciated.
----------------------------------------
This part I dont think I am understanding
"but remember later on you still have to load the permanent TWRP with install."
Click to expand...
Click to collapse
Go have a read at this page in the DevsBase forum if you haven't already. It is discussed that there have been problems with the setup wizard.<Mod Edit: Link removed. Please don't redirect members to other mobile forums. Thanks!>
Also, I see in the discussion there that the nightly builds are now 4/13 so you might try that date build and see if the problem has gone away. I also saw discussed that some folks there were installing older builds that did not have the setup problems and then using TWRP to flash the newest builds. Otherwise, from what you posted, you are doing everything right.
NT
W_three said:
The only difference I can see I resized the Media to 1024 where your instructions indicate 1000 but I cant see that as being any problem though to be honest my knowledge here is limited.
This part I don't think I am understanding
"but remember later on you still have to load the permanent TWRP with install."
Click to expand...
Click to collapse
As long as the Media is greater than 1000 MB it should be OK.....
Essentially the program TWRP_TmpLoad_v03_win.bat loads TWRP temporarily by using a novacom command to load uImage.TWRP to the HP Touchpad, but you still have to download and have as one of your 3 zips something like this FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-3-24-17.zip, so that you can have a permanent load of TWRP after all is said and done.
Hey guys! Went through all of these steps and got it to boot! However, after it booted for quite a while, it started up the setup wizard, and immediately stops whenever you choose an option, whether it be "Set up as new" or "copy your data."
Is it something I've done wrong? Any help would be appreciated!
Seatreader said:
Hey guys! Went through all of these steps and got it to boot! However, after it booted for quite a while, it started up the setup wizard, and immediately stops whenever you choose an option, whether it be "Set up as new" or "copy your data."
Is it something I've done wrong? Any help would be appreciated!
Click to expand...
Click to collapse
No your not doing anything wrong, the new nightly builds are going through a particularly buggy phase the last few builds. I am assuming you used the 4-19 nightly. Lets try an earlier Testing build.
If you have time, just for kicks and for testing purposes can you try again but use Flintmans latest testing 3-25 ROM instead of the Evervolv Nightly.
Try this ROM and lets see if it fixes the issue:
http://evervolv.com/static/builds/testing/Queo/ev_tenderloin-7.1.1-testing-2017.03.25.zip
If you notice the user "w_three" had the same issue in an earlier post on this thread....
okay I'll give that a go tonight! I noticed on the release page forums they were talking about how you had to dirty flash the newer roms on and figured that was my problem.
=UPDATE=
Ran as per the instructions with a nice clean install and it booted fine! Takes forever to boot and get through the" finishing touches" but it looks like it's working fine!! Four days ago this tablet was bricked!
Thanks for all the help!
After letting this rest for a few days I decided to give it another go.
Used the 3/25 zip you posted above DoubleStuff and finally past the set up error. Going through it now. Thanks for posting that Rom.
W_three said:
After letting this rest for a few days I decided to give it another go.
Used the 3/25 zip you posted above DoubleStuff and finally past the set up error. Going through it now. Thanks for posting that Rom.
Click to expand...
Click to collapse
Great! W_three, that you finally got it working, from what I have been reading on devs-base, Open Gapps are only running through 7.1.1, and as of April 4th (4/4) Evervolv nightlies have switched to 7.1.2. ( see pic below ) Some people have a theory that this is causing the set-up wizard to break. To get around this issue, some people have been "clean" flashing an older 3-25 ROM see link to that in post #8 ( or in theory anything before 4/4 nightly ), then "dirty" flashing the newer ROMs on top of that. I am just reporting on what I read, not sure how accurate it is.
See in below screenshot how name changes from 7.1.1 ( green ) to 7.1.2 ( red ).....just sayin'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just know that this Nougat ROM is still only in Beta, so there will be bugs and lagginess.
As Nevertells2 would tell anybody, JC Sullins KitKat 4.4.4 ROM is probably the most stable.
Setup Wizard fails
My Setup Wizard fails and I see the note below:
*NOTE: as of 4/4 since start of 7.1.2, if your having issues with setup wizard after the install you might want to flash this older ROM instead ( before 4/4 ), then dirty flash a newer ROM
How do I perform this?
How do I flash with a older ROM (before 4/4) and then dirty flash a newer ROM? Can you elaborate?
Thank you in advance.
xdakzhf2d said:
My Setup Wizard fails and I see the note below:
*NOTE: as of 4/4 since start of 7.1.2, if your having issues with setup wizard after the install you might want to flash this older ROM instead ( before 4/4 ), then dirty flash a newer ROM
How do I perform this?
How do I flash with a older ROM (before 4/4) and then dirty flash a newer ROM? Can you elaborate?
Thank you in advance.
Click to expand...
Click to collapse
Well underneath that red letter explanation in the Original Post, is a link to a 3-25 ROM, flash that using the alternative method described in OP. That is called a clean install.
Then once you get that going, you can dirty install the current 5-8 ROM, by selecting this once tablet is running:
Settings->About Tablet->Evervolv Updates->Nightly Tab->Refresh, then download the zip, and boot into recovery and flash it. If you don't understand this terse explanation, I have pasted RolandD's How to dirty flash and root video below ( from 1:19 to 3:17 is Dirty Flash )
Dirty Flash Instructions
Hi, Ive ran each step as instructed twice, just to be sure. both times I get only an external sd card selection, no internal card or data selection once files load and I run twerp it installa yet I get a failed to mount data invalid argument. what am I doing wrong?
deafasheck said:
Hi, Ive ran each step as instructed twice, just to be sure. both times I get only an external sd card selection, no internal card or data selection once files load and I run twerp it installa yet I get a failed to mount data invalid argument. what am I doing wrong?
Click to expand...
Click to collapse
Hello deafasheck, I have been following you on these boards for years, and you always get errors and issue that are different from the norm. LOL
In fact you even call J.C. Sullins by an unusual name ( JC Sullivan ) LOL, but I have seen Nevertells2 correct you a few times, so I think we are good to go there.
As far as your issue, did you load the 3-25 ROM first? Then try to dirty flash the latest nightly? I would like to know more details on the procedure you used. But you maybe in luck, because I think there is another thread today that has a similar ( mount and volume issues ) and RolandD gave him a answer and a few links...
Look HERE at post #1094
Missed a step.
Hi DoubleStuff, yeah I'm way out of my league, but have learned so much in forum, I found out what I done wrong. I didn't move file size in data only moved cashe and system to as close as could to instructions. it fixed right up once I put data size, I noticed cam still inverted, does new ROM resolve that? I'm going back and dirty flash that ROM I ove the size if this, it doesn't take up much space has less bloatware and I use UC browser which is so so Philz kk is best I have tried . but I'm gona toy on this one Ive almost mastered this touchpad insyallations even learning codeing, just not yet.. I do dislike the home launcher, so used to having one like the one in kk or nova. Ive not bricked mine yet! was worried for awhile. but any thing I need to know is on here . thanks for the reply..
im still learning how to post specs of tablet. JC Sullin huh? yeah, Im good on typos. dang laptop mouse jumps around.. well here we go, going to dirty flash newest rom, wish me luck.. thanks..
DoubleStuff said:
Hello deafasheck, I have been following you on these boards for years, and you always get errors and issue that are different from the norm. LOL
In fact you even call J.C. Sullins by an unusual name ( JC Sullivan ) LOL, but I have seen Nevertells2 correct you a few times, so I think we are good to go there.
As far as your issue, did you load the 3-25 ROM first? Then try to dirty flash the latest nightly? I would like to know more details on the procedure you used. But you maybe in luck, because I think there is another thread today that has a similar ( mount and volume issues ) and RolandD gave him a answer and a few links...
Look HERE at post #1094
Click to expand...
Click to collapse
deafasheck said:
Hi DoubleStuff, yeah I'm way out of my league, but have learned so much in forum, I found out what I done wrong. I didn't move file size in data only moved cashe and system to as close as could to instructions. it fixed right up once I put data size, I noticed cam still inverted, does new ROM resolve that? I'm going back and dirty flash that ROM I ove the size if this, it doesn't take up much space has less bloatware and I use UC browser which is so so Philz kk is best I have tried . but I'm gona toy on this one Ive almost mastered this touchpad insyallations even learning codeing, just not yet.. I do dislike the home launcher, so used to having one like the one in kk or nova. Ive not bricked mine yet! was worried for awhile. but any thing I need to know is on here . thanks for the reply..
im still learning how to post specs of tablet. JC Sullin huh? yeah, Im good on typos. dang laptop mouse jumps around.. well here we go, going to dirty flash newest rom, wish me luck.. thanks..
Click to expand...
Click to collapse
Hello deafasheck, I am glad your learning and taking the advice of Nevertells2 which is "read, my friend, read!!"
Yes the Stock Camera is still inverted, but haven't you heard? That if you go to google play store and download "Open Camera" app it works fine in Nougat, let me know what you think of it. I am glad you figured out your own problem that is telling me you are learning quite a bit since you were a "newbie" in 2014!! :good:
OK deafascheck I wish you luck in your dirty flash download? And your experiment with "Open Camera" and hope you learn how to code at least in BAT and VBS files, because when Oreo ( Android "O" ) comes out we will need to tweek the code for this Alternative method again!! I am doubling down that its called Oreo, hence my Avatar.
Thank you so much, yes got to learn code and terminal commands. on the subject of dirty flash, is that same as loading the via tptb as I did with the permanent files when Initial install ?
deafasheck said:
Thank you so much, yes got to learn code and terminal commands. on the subject of dirty flash, is that same as loading the via tptb as I did with the permanent files when Initial install ?
Click to expand...
Click to collapse
deafasheck, defasheck, defasheck, come on now we have been studying "dirty flashes" since you were a "newbie" in 2014, and our friend RolandD has made many videos on it....in fact in this ROM alternative thread in post #13 at the bottom of the post is a good video that explains "dirty flashes"....learn it, love it, live it!!!
Good Luck in all your learning Deafasheck!!! :highfive:
POST #13 for deafasheck learning dirty flashes.
Videos don't help much, I'm deaf as heck.. and getting lost in the steps.. from what I recasll dirty flash is asop I did one as I had in the original install ie placed in twerp flashed from twerp. that worked as far as I know? I'm trying to find the super user link I seen earlier, once I get ROM and SU I'm gonna get the camera app. thanks..
Hi everyone,
Just bought a used NT and I flashed cm10.1 and TWRP 2.8.4.0. After a reboot, my NT shows a pixel glitch screen after the N logo then stucks at it. I tried to press power button to hard reboot, but it doesn't change. A recovery sdcard doesn't work to it too.
So I'm here to ask if there's any way can rescue my NT. Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CherryRook said:
Hi everyone,
Just bought a used NT and I flashed cm10.1 and TWRP 2.8.4.0. After a reboot, my NT shows a pixel glitch screen after the N logo then stucks at it. I tried to press power button to hard reboot, but it doesn't change. A recovery sdcard doesn't work to it too.
So I'm here to ask if there's any way can rescue my NT. Thanks.
View attachment 5713397
Click to expand...
Click to collapse
You need to find a way to either power down or at least reboot (after that you need to remake your flashing file sdcard because there is clearly something wrong there).
Of course, you could let the battery die on its own, then boot up an sd recovery card. That will return your device to FW 1.4.2 and fix any partition issues.
So unless you can force a shutdown or reboot with the power button, you may not have many options other than to drain the battery (or open the device and disconnect the battery for a minute).
Edit: Also, that TWRP version looks way out of range for CM 10.1 Should be more something like 2.2.2. A newer TWRP version may not work at all with an older ROM like 10.1 (why 10.1, and not 11, or 12.1, or....?)
nmyshkin said:
You need to find a way to either power down or at least reboot (after that you need to remake your flashing file sdcard because there is clearly something wrong there).
Of course, you could let the battery die on its own, then boot up an sd recovery card. That will return your device to FW 1.4.2 and fix any partition issues.
So unless you can force a shutdown or reboot with the power button, you may not have many options other than to drain the battery (or open the device and disconnect the battery for a minute).
Edit: Also, that TWRP version looks way out of range for CM 10.1 Should be more something like 2.2.2. A newer TWRP version may not work at all with an older ROM like 10.1 (why 10.1, and not 11, or 12.1, or....?)
Click to expand...
Click to collapse
Thank you for your reply.
Maybe it's not clear that I explained about the reboot (sorry for my bad English, not a native speaker), I can press the power button to shut it down, or hard reboot it. The problem is that the glitch screen shows every time and stucks every time.
May I ask that how to use the sd recovery card you provide? Shut down, insert the sd card, boot up and follow the instructions, is that right?
About the TWRP, I was tried to flash lineage 14.1 to my NT but the latest version of TWRP (3.1.1.0) doesn't work on my tablet, it's just black and blank after I flashed the recovery, so I have to use the older version. Besides that, some versions of TWRP has the famous error that both internal storage and micro sd card are 0 mb size. That's strange. Because I download them all from the official site.
nmyshkin said:
You need to find a way to either power down or at least reboot (after that you need to remake your flashing file sdcard because there is clearly something wrong there).
Of course, you could let the battery die on its own, then boot up an sd recovery card. That will return your device to FW 1.4.2 and fix any partition issues.
So unless you can force a shutdown or reboot with the power button, you may not have many options other than to drain the battery (or open the device and disconnect the battery for a minute).
Edit: Also, that TWRP version looks way out of range for CM 10.1 Should be more something like 2.2.2. A newer TWRP version may not work at all with an older ROM like 10.1 (why 10.1, and not 11, or 12.1, or....?
Click to expand...
Click to collapse
P.S. my NT is 16GB version. Is your file work to my device?
CherryRook said:
Thank you for your reply.
Maybe it's not clear that I explained about the reboot (sorry for my bad English, not a native speaker), I can press the power button to shut it down, or hard reboot it. The problem is that the glitch screen shows every time and stucks every time.
May I ask that how to use the sd recovery card you provide? Shut down, insert the sd card, boot up and follow the instructions, is that right?
About the TWRP, I was tried to flash lineage 14.1 to my NT but the latest version of TWRP (3.1.1.0) doesn't work on my tablet, it's just black and blank after I flashed the recovery, so I have to use the older version. Besides that, some versions of TWRP has the famous error that both internal storage and micro sd card are 0 mb size. That's strange. Because I download them all from the official site.
Click to expand...
Click to collapse
First, yes, you insert the recovery card, boot the tablet and follow the screen instructions, mostly "are you sure?", etc. This will restore your tablet to factory condition, FW 1.4.2. Should work for either 8 or 16 GB models.
Secondly, I hope you do not really mean CM 14.1. That would be a mistake, I think. That ROM requires repartitioning and there are newer (possibly better) options that do not.
If you are set on Android 7, then I suggest either AOSP 7.0 (which is what I run on my tablet) or LNOS 14.1 (which I have only tested on an 8 GB model, so I can't give a fair assessment:
nmyshkin said:
Lineage 14.1
https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3262390066
(there are many versions of this ROM. The link takes you to the "obsolete" folder where you need to hunt down lnos_acclaim-ota-NJH47F.180211.zip. This seems to be the only version without the shut-down bug)
Flashed with emmc-based TWRP 3.0.2-0
Click to expand...
Click to collapse
For either of those ROMs you can use the sdcard version of TWRP:
nmyshkin said:
TWRP (TeamWin Recovery Project) version 2.8.6.0, e.g. twrp-2.8.6.0-acclaim-sdcard.img from https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img.html, rename it to recovery.img before copying to SD card. Be sure to use the sdcard.img file and not the one for internal emmc
Click to expand...
Click to collapse
in order to flash the higher version of TWRP to the emmc which is what you will need for flashing the ROM:
nmyshkin said:
the flashable_TWRP_3.0.2-0.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
Click to expand...
Click to collapse
If you have trouble with the TWRP from the actual website, let me know and I'll post a copy of my file. The emmc TWRP 3.0.2-0 is a little squirrely. The touch interface is shaky and you have to look carefully at what you have selected (or deselected) before going on to another step or you can end up in trouble. Not my favorite version.
Root, etc. for each of the ROMs is achieved a little differently, so when you get to that point, ask.
I don't recommend adding GApps to these unless you absolutely must have it. I do have GApps installed on my AOSP 7.0 install and it's "OK", but it would be more responsive without it. If you must have Google access then microG is probably the better way to go. You can read more about in my post on the 8 GB tablet. Everything there is applicable to the 16 GB tablet, except the ROMs I reviewed would all be expected to perform much better on the 16 GB version.
nmyshkin said:
First, yes, you insert the recovery card, boot the tablet and follow the screen instructions, mostly "are you sure?", etc. This will restore your tablet to factory condition, FW 1.4.2. Should work for either 8 or 16 GB models.
Secondly, I hope you do not really mean CM 14.1. That would be a mistake, I think. That ROM requires repartitioning and there are newer (possibly better) options that do not.
If you are set on Android 7, then I suggest either AOSP 7.0 (which is what I run on my tablet) or LNOS 14.1 (which I have only tested on an 8 GB model, so I can't give a fair assessment:
For either of those ROMs you can use the sdcard version of TWRP:
in order to flash the higher version of TWRP to the emmc which is what you will need for flashing the ROM:
If you have trouble with the TWRP from the actual website, let me know and I'll post a copy of my file. The emmc TWRP 3.0.2-0 is a little squirrely. The touch interface is shaky and you have to look carefully at what you have selected (or deselected) before going on to another step or you can end up in trouble. Not my favorite version.
Root, etc. for each of the ROMs is achieved a little differently, so when you get to that point, ask.
I don't recommend adding GApps to these unless you absolutely must have it. I do have GApps installed on my AOSP 7.0 install and it's "OK", but it would be more responsive without it. If you must have Google access then microG is probably the better way to go. You can read more about in my post on the 8 GB tablet. Everything there is applicable to the 16 GB tablet, except the ROMs I reviewed would all be expected to perform much better on the 16 GB version.
Click to expand...
Click to collapse
Thank you for these detailed instructions. Unfortunately, I write the factory reset file to a 16gb sd card, insert my NT and boot it, nothing change.
CherryRook said:
Thank you for these detailed instructions. Unfortunately, I write the factory reset file to a 16gb sd card, insert my NT and boot it, nothing change.
Click to expand...
Click to collapse
Some tablets will not boot from the sdcard unless they are plugged in to external power (either the power pack or USB from your PC). Try shutting down, then insert the power cord to make the tablet boot (it should come on by itself when power is applied). See if that helps.
OK, I should have given a lot more instructions with that file but I have never used it myself and forgot about all the stuff. Here is a link (messy...the important stuff runs down the left side of the screen) that describes how to use that zip file to restore your tablet: https://web.archive.org/web/2018082...06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
nmyshkin said:
Some tablets will not boot from the sdcard unless they are plugged in to external power (either the power pack or USB from your PC). Try shutting down, then insert the power cord to make the tablet boot (it should come on by itself when power is applied). See if that helps.
OK, I should have given a lot more instructions with that file but I have never used it myself and forgot about all the stuff. Here is a link (messy...the important stuff runs down the left side of the screen) that describes how to use that zip file to restore your tablet: https://web.archive.org/web/2018082...06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
I hate to say this but it doesn't work, still can't boot from sd card. The interesting thing is, my NT will automatically reboot after stuck at glitch screen for a while.
CherryRook said:
I hate to say this but it doesn't work, still can't boot from sd card. The interesting thing is, my NT will automatically reboot after stuck at glitch screen for a while.
Click to expand...
Click to collapse
You may need to try another card, if you can get one. This is often the problem when the tablet won't boot (did you try booting by inserting the power cord?). It may take some trial and error, and as they say in the instructions, you may need to remake the card (reformat, re-write the image) to get it all to work.
I can't think of any other approach for where you are now. The device clearly can't get to either a recovery or an OS.
With no SD card in, does it show up as some sort of USB device? Maybe 0451/d00f?
"doof" is German for stupid.
Renate said:
With no SD card in, does it show up as some sort of USB device? Maybe 0451/d00f?
"doof" is German for stupid.
Click to expand...
Click to collapse
Unfortunately no. It has no reaction on mac and when I plug it to PC, windows shows me a announcement that there's a device which doesn't work properly
nmyshkin said:
Some tablets will not boot from the sdcard unless they are plugged in to external power (either the power pack or USB from your PC). Try shutting down, then insert the power cord to make the tablet boot (it should come on by itself when power is applied). See if that helps.
OK, I should have given a lot more instructions with that file but I have never used it myself and forgot about all the stuff. Here is a link (messy...the important stuff runs down the left side of the screen) that describes how to use that zip file to restore your tablet: https://web.archive.org/web/2018082...06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
That's weird. I followed the instructions on that page but still doesn't work. everytime I boot up, I got a quick N logo show screen then the familiar pixel glitch one.
Also I tried to change the partition ID to 0x0E FAT 16 LBA according from a thread in Chinese forum, but nothing changes
I was wondering if it's any kind of hardware issues?
CherryRook said:
Windows shows me a announcement that there's a device which doesn't work properly
Click to expand...
Click to collapse
Well, that means that there is *something* there.
Go to Device Manager and look for something with an exclamation.
Go to Details and look for Instance path.
I'm not sure even with an external SD card whether it still relies on the loader in eMMC.
OTOH, it could be a case of your regular system working well enough to start (and not go to SD) but too screwed up to run.
Renate said:
Well, that means that there is *something* there.
Go to Device Manager and look for something with an exclamation.
Go to Details and look for Instance path.
I'm not sure even with an external SD card whether it still relies on the loader in eMMC.
OTOH, it could be a case of your regular system working well enough to start (and not go to SD) but too screwed up to run.
Click to expand...
Click to collapse
I checked the device manager and found nothing. Literally, nothing there even after the weird announcement popped up.
I agree with your idea: maybe my emmc and system work fine, but something of bootloader or hardware has some problem so I got a pixel glitch screen. In my observation, the pixel glitch scrolls out from the right margin of the screen and covers the n logo and adobe claim. I still can recognize the text and images from those pixel snows, so I highly doubt that something about rendering must be wrong.
CherryRook said:
the pixel glitch scrolls out from the right margin of the screen and covers the n logo and adobe claim. I still can recognize the text and images from those pixel snows, so I highly doubt that something about rendering must be wrong.
Click to expand...
Click to collapse
What you describe is "normal" for a NT booting Cyanoboot--up to a point. With a properly functioning card, first boot copies over the cyanobootloader so that subsequent boots are from the emmc (assuming the system is intact). On the 16 GB NT every boot from the powered-down state flashes the pixelated screen briefly, and all at once. On the 8 GB NT, the pixelated effect moves from one side of the screen to the center and then from there to the other side until the entire screen is covered, then boot continues. and the pixelated effect disappears.
The problem seems to be getting a boot from the sdcard. If you read through the now crippled forum, you will see that's not so uncommon. The most common solution is a different card or at least a complete re-write of the offending card.
It has been reported often that some NTs cannot boot from the sdcard unless they are connected to a power source (either the charging pack or the USB connection to a PC). I have not seen this with my two tablets, but it would not surprise me.
Even making the original cyanoboot sdcard is filled with traps. Everything has to be done just right or the card will fail to boot or--worse--wreak havoc on the system.
It occurs to me that one other approach to this situation is to prepare such a card as if you were going to flash a custom recovery and a ROM. These instruction shepherd you through the card preparation:
nmyshkin said:
1. Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on the SD card a Primary FAT32 partition, set the partition ID type for the partition to 0x0C FAT32 LBA, and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows
2. Obtain and copy to the SD card the following files:
a. first MLO, then next u-boot.bin, and finally flashing_boot.img in succulent_boot.zip obtained from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
b. TWRP (TeamWin Recovery Project) version 2.8.6.0, e.g. twrp-2.8.6.0-acclaim-sdcard.img from https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img.html, rename it to recovery.img before copying to SD card. Be sure to use the sdcard.img file and not the one for internal emmc
c. the flashable_TWRP_3.0.2-0.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
Click to expand...
Click to collapse
Every single step is important, especially step 1. In step 2a the order in which the files are placed on the card seems to be important according to some guides. So every detail is important. No shortcuts. If you can prepare such a card and get your device to boot from it (try with the power cord), into the Cyanoboot menu, you should be able to flash a good emmc recovery and then......a ROM. But if the card won't boot, you can't do any of that.
Edit: Does this work on your tablet, or is it too far gone?
Perform Factory Reset of the Nook Tablet:
PWR off the Nook Tablet.
Hold "PWR" & "∩" & "VOL+" & "VOL-" buttons simultaneously to reboot.
After reboot, release only the "PWR" & "∩" buttons after 2-3 seconds upon receiving the "∩ - Contains Reader® Mobile technology by Adobe Systems Incorporated." screen while still maintaining to hold the "VOL+" & "VOL-" buttons.
The screen may blink a couple seconds later and then you will be presented with the Factory Reset screen with the following options:
Do you want to reset your device to the factory default?
Press POWER key to exit
Press HOME key to continue
Are you sure?
This will delete all your content and restore the device to the factory default settings.
Press POWER key to exit
Press HOME key to continue
I even accidentally let go of the "VOL+" & "VOL-" buttons once while testing this a few times but quickly pushed them back down again and was still given the factory reset screen so this method works even with a little goof like that. This worked since holding down the "VOL+" & "VOL-" buttons was found to be unnecessary.
nmyshkin said:
What you describe is "normal" for a NT booting Cyanoboot--up to a point. With a properly functioning card, first boot copies over the cyanobootloader so that subsequent boots are from the emmc (assuming the system is intact). On the 16 GB NT every boot from the powered-down state flashes the pixelated screen briefly, and all at once. On the 8 GB NT, the pixelated effect moves from one side of the screen to the center and then from there to the other side until the entire screen is covered, then boot continues. and the pixelated effect disappears....
Click to expand...
Click to collapse
It's just so weird.... I booted it successfully and my NT works well again.
I made a new recovery card, here's what I did:
1. Format a 8GB Kingston card to FAT32, set partition ID type to 0x0C FAT32 LBA, then set it to main active partition;
2. Copy everything for the card (MLO, u-boot.bin, flashing-boot.img, renamed TWRP 2.8.6.0-sdcard, flashable_TWRP_3.0.2-0.zip) to the card;
3. Plug my NT to PC, insert the card, boot;
4. Pixelated screen disappears and it boots normally to the sd card cyanoboot;
5. I entered to the sd recovery and flash the 3.0.2.0 TWRP, reboot.
Now it's running but I still have some problems.
First, when I try to perform a factory reset in the sd recovery, I noticed it has a caution that "Unable to mount /bootdata/," I'm not familiar with the system structure but I think ihat where the boot files save and maybe it caused the pixel glitch;
Second, when I check the partition status in new flashed TWRP 3.0.2.0 on emmc, It doesn't show any partition except ART / Davlik Cahce in Advanced Wipe page. I'm not sure what's going here. Then I rebooted to system, which works fine, and reboot again to recovery, and all partitons come back.
I'm so confused by all these things but at least I can use it now. May I ask, if I want to flash the AOSP 7 ROM, whcih version of TWRP I need? Should I flash it with sd recovery or emmc one?
CherryRook said:
It's just so weird.... I booted it successfully and my NT works well again.
I made a new recovery card, here's what I did:
1. Format a 8GB Kingston card to FAT32, set partition ID type to 0x0C FAT32 LBA, then set it to main active partition;
2. Copy everything for the card (MLO, u-boot.bin, flashing-boot.img, renamed TWRP 2.8.6.0-sdcard, flashable_TWRP_3.0.2-0.zip) to the card;
3. Plug my NT to PC, insert the card, boot;
4. Pixelated screen disappears and it boots normally to the sd card cyanoboot;
5. I entered to the sd recovery and flash the 3.0.2.0 TWRP, reboot.
Click to expand...
Click to collapse
So it was the card. Ta-da!
CherryRook said:
Now it's running but I still have some problems.
First, when I try to perform a factory reset in the sd recovery, I noticed it has a caution that "Unable to mount /bootdata/," I'm not familiar with the system structure but I think ihat where the boot files save and maybe it caused the pixel glitch;
Click to expand...
Click to collapse
The emmc version of TWRP (3.0.2.0) is full of little goofy "error" messages. Just ignore the bootdata messages. In general, TWRP is not going to wipe out /bootdata/ unless you try really hard. That's to prevent you from ending up with a brick.
CherryRook said:
Second, when I check the partition status in new flashed TWRP 3.0.2.0 on emmc, It doesn't show any partition except ART / Davlik Cahce in Advanced Wipe page. I'm not sure what's going here. Then I rebooted to system, which works fine, and reboot again to recovery, and all partitons come back.
Click to expand...
Click to collapse
This I cannot explain, but I hope that things will settle down as you begin flashing a ROM. Just bear in mind that the emmc TWRP has a poor touch interface. Always be sure items you have checked (or unchecked) are really that way. There should be no highlighting around a checked or unchecked item. If there is, it's not really what it looks like and you need to select (or deselect) again until you have a normal checkbox.
CherryRook said:
I'm so confused by all these things but at least I can use it now. May I ask, if I want to flash the AOSP 7 ROM, whcih version of TWRP I need? Should I flash it with sd recovery or emmc one?
Click to expand...
Click to collapse
The emmc TWRP you have is the correct one for AOSP 7. Continue here: https://forum.xda-developers.com/t/...-internally-on-the-16-gb-nook-tablet.3578665/ with step 2d. I do not recommend GApps, but it's in the instructions. If you want it, here is a link to the package I used. All the packages at OpenGApps seem to auto-expand with time until they are too large for our devices. If you don't want GApps, just skip any steps that refer to it.
Then proceed to step 3d since you have already flashed the emmc TWRP.
If you want full root access you'll need the superuser control apk. Here is a link.
I know the instructions are very tedious, with a lot of rebooting, but they are what worked for me reliably, over and over again. Detail counts in this kind of thing (and luck!).
nmyshkin said:
So it was the card. Ta-da!
Click to expand...
Click to collapse
It was the card, yes.
A brand new new questions here:
When sd card is inserted, I can't reboot or reboot normally or to the recovery. I did it from the power menu then it gives me a black and blank screen until I hold the power button to force it shut. If I try to boot it from the shutdown status. I have to remove the sdcard otherwise it can't be booted.
CherryRook said:
It was the card, yes.
A brand new new questions here:
When sd card is inserted, I can't reboot or reboot normally or to the recovery. I did it from the power menu then it gives me a black and blank screen until I hold the power button to force it shut. If I try to boot it from the shutdown status. I have to remove the sdcard otherwise it can't be booted.
Click to expand...
Click to collapse
I'm not sure I understand, but the sdcard you have made is not something that you would normally leave in the device. It is for flashing purposes only or for accessing the sd-recovery for some reason (like the emmc recovery gets messed up somehow or you need to flash something that is too new/too old for the emmc recovery).
If you completed the initial cyanoboot installation corrrectly, the device should boot into cyanoboot and then to the ROM (if installed) when turned on (without the card). If you leave the sdcard in and power up without selecting the "n" button to get to the boot menu, you will get an error about "boot magic", etc., and the device will just sit there on the cyanoboot screen.
So, yes (?) you need to remove the card to boot "normally" (i.e., into the ROM), although even there if you are quick you can intercept the boot with the "n" button and go into emmc recovery (from one of the boot menu options).
Is the problem that you don't have any OS? I wasn't clear whether that survived your first attempts with the bad card.
Edit: if you want to use an sdcard with the NT for storage it will have to be a different one than the one you prepared specially for flashing cyanoboot, etc.
nmyshkin said:
I'm not sure I understand, but the sdcard you have made is not something that you would normally leave in the device. It is for flashing purposes only or for accessing the sd-recovery for some reason (like the emmc recovery gets messed up somehow or you need to flash something that is too new/too old for the emmc recovery).
Click to expand...
Click to collapse
I restored the ID type of the sd card and now my NT can boot normally with the card inserted.
Tried the AOSP 7 you recommend and it's very good, thank you for it - but I think it would be better to have more custom settings, but Xposed and something like that are too heavy to NT with AOSP 7.
I tried to flash the lineage os 14.1 in your notredame folder but it can't boot. Looped at booting animation. Also, I tried a rom from AndroidFileHost, DrM-14.1-acclaim-Root-OC, but I got the status 7 error when flashing it, nomatter I use 3.0.2.0 TWRP on emmc or 2.8.4.0 one on the sd card. Any suggestion?