Hello!
I apologize if I have posted this in the wrong place. I have searched high and low for a solution to my issue and I cannot find one. I have the 16GB Nook Tablet and I followed the [HOW TO] guide in order to install android 7.0 by nmyshkin I believe it was. Anyways, when I try to install the .zip file for aosp Acclaim, I get an error that says "Can't install this package over newer build" ERROR 7. Any idea on how to fix this? The tablet was previously rooted a few years ago with CM; however, I do not know what I did with it at the time. Right now I am just trying to get my tablet back in running condition as there is no OS on it at all right now and the CM bootloader and TWRP are the only things on it as far as I can tell. Any help would be great!
DrHouseParty said:
Hello!
I apologize if I have posted this in the wrong place. I have searched high and low for a solution to my issue and I cannot find one. I have the 16GB Nook Tablet and I followed the [HOW TO] guide in order to install android 7.0 by nmyshkin I believe it was. Anyways, when I try to install the .zip file for aosp Acclaim, I get an error that says "Can't install this package over newer build" ERROR 7. Any idea on how to fix this? The tablet was previously rooted a few years ago with CM; however, I do not know what I did with it at the time. Right now I am just trying to get my tablet back in running condition as there is no OS on it at all right now and the CM bootloader and TWRP are the only things on it as far as I can tell. Any help would be great!
Click to expand...
Click to collapse
In my experience that error is produced by attempting to use the wrong recovery. Did you use the TWRP recovery listed in the instructions?
nmyshkin said:
In my experience that error is produced by attempting to use the wrong recovery. Did you use the TWRP recovery listed in the instructions?
Click to expand...
Click to collapse
I did and no luck...I'm going to start from scratch again and make sure I did not miss anything, starting with brand new files. Wish me luck I suppose!
*SUCCESS*
So I am not entirely sure what happened, but I deleted, redownloaded, wiped, and then reinstalled all of the files from the tutorial and now everything is working. Tablet is still booting up so lets cross our fingers that all boots well!
Related
Hi!
This is my first time ever posting here and although I've found some topics relating to my issue, none have helped me out.
My problem:
I downloaded an app called Flashify.
From the app, I downloaded android 4.4 KitKat because I wanted to update my ROM.
When I booted my phone into recovery (stock <3e>), I clicked on install from SD card, installed the .zip file but I got an error...
It read:
"E:failed to verify whole-signature"
"E:signature verification failed"
"E:update fail and delete temp files"
"formatting /cache..."
Instalation aborted.
Now, if I try to set up my phone again, I'll get as far as the welcome screen and it will always say:
"Unfortunately, Setup Wizard has stopped."
Please help.
I've tryed everything and I can't get rid of that error!
Thank you
Oh by the way, I forgot to give some details
The phone is a Huawei Ascend g330 U8825-1
Android 4.0.4 ICS
Rooted
Running stock everything (or at least it was...)
The file I tryed to install is called: "gapps-kk-20140105-signed-4.4.zip"
Did you even look at a guide on how to update your phone? Actually, I am quite sure you didn't or else you completely misunderstood everything you read. Neither is a good thing when trying to do something complicated like updating your phone unofficially.
1) You can't install a custom rom with stock recovery.
2) You didn't even download a rom - those are the Google Apps that are to be installed along with a custom rom like CyanogenMod.
3) You have to unlock the bootloader to install the custom recovery that will allow you to install updates not signed directly by Huawei.
I suggest you read through this thread:
http://forum.xda-developers.com/showthread.php?t=2198908
There are links in the later pages to a version of 4.4.2 from the Modaco forums, as well as links to the original firmware, which you will probably need to re-install if a factory reset doesn't help.
es0tericcha0s said:
Did you even look at a guide on how to update your phone? Actually, I am quite sure you didn't or else you completely misunderstood everything you read. Neither is a good thing when trying to do something complicated like updating your phone unofficially.
1) You can't install a custom rom with stock recovery.
2) You didn't even download a rom - those are the Google Apps that are to be installed along with a custom rom like CyanogenMod.
3) You have to unlock the bootloader to install the custom recovery that will allow you to install updates not signed directly by Huawei.
I suggest you read through this thread:
http://forum.xda-developers.com/showthread.php?t=2198908
There are links in the later pages to a version of 4.4.2 from the Modaco forums, as well as links to the original firmware, which you will probably need to re-install if a factory reset doesn't help.
Click to expand...
Click to collapse
I'm new to all of this and I thought that the app that I downloaded could do it all in one operation.
I wanted to take a chance and see would happen, thinking that any consequences that may occur, could be fixed with a factory reset.
Thanks for the link and the advice.
I'll have a read, now
Is it a serious problem or is there any way to fix it?
I tryed unlocking the Bootloader in DC-Unlocker but to no avail.
Just a quick question about "bump"ed TWRP images and why they might/might not work. I got my G3 a few days ago (came with Lollipop 5.0 stock) and finally got around to rooting it today. Naturally, I wanted to install TWRP after that so I could fire up some custom ROMs later on. I followed the guide in the official Bump! thread and ended up with recovery that wouldn't boot due to a "secure boot error". I then tried flashing the same, bumped, 2.8.7.0 image with Flashify, with the same result. Then I moved on to AutoRec, and for some reason that did the trick - after letting it flash TWRP, I could boot into recovery with no problems. I then flashed the (newer) bumped image I got from the Bump! thread that hadn't worked before and to my bewilderment, it worked as well. Can someone explain to me in broad strokes what exactly made the difference? And, if there is an additional step involved beyond just flashing a bumped TWRP, why is that not mentioned anywhere in the Bump! thread?
Also, from what I understand, "bump"ing an image just means signing it with LG's key that was extracted by the Bump! and open bump! developers. If that is the case, why are there still un-bumped recovery images floating around? What use are those to anyone, if aboot will refuse to boot them?
Cheers,
George
P.S. If there is a thread/post already out there somewhere (I'm pretty sure there is, but I couldn't find anything) with the information I'm looking for and/or more general information on the unlocking/signing process, I'd love to read it - I just haven't found anything like that so far.
Bump
THIS IS A CLOSED CASE, GO HOME. The answer is Hairybean found in step 2 of here [ROM] [TF201] KatKiss 5.1.1 - v30 [MultiWindow] [Stable] [RRO] Read the rest of this post if you're a sadist or want to know of people in the same pain boat as you.
Part 1: My life's story. Skip to Update if you just want to hear of my current problem.
So approximately 12 hours ago, I decided, "Hey, I want to upgrade my tablet so I can download the newest and coolest apps. Since I need to upgrade to a newer OS (ICS>KK ?) I may as well go through the extra hurdle and download a nice, fast custom ROM because the stock feels like crap for the lightweight that is the TF201."
Now me, not having ever touched an android in my life before this tablet, knew this was going to be a challenge. After doing plenty of research into unlocking, flashing a custom recovery, general custom ROM flashing etiquette, and following this guide ([ROM] [MM 6.0.1] KatshMallow v29 [TF201]), I encountered my first of many hurdles. This being: I was able to boot just fine, but the Wifi was in a perpetual state of "Wifi turning on..." I put a total of a couple or so hours into researching this and easily found others having the same issue, albeit not specifically to the exact ROM and device in question. I also tinkered a bit in these hours, reflashing and rebooting and all that jazz. I eventually settled upon one of three conclusions:
The "/persist" folder had gotten deleted which contains vital wifi/network configuration data
wlan0 was borked on a hardware level and I managed to completely kill an hope of wifi on my device
There was a MAC address somewhere that I needed to manually edit (that WASN'T in the persist file)
Considering the fact that I could not see nor change directory via adb terminal (yes, with su) into a "/persist" folder, and that the hardware-broken devices other users had were most if not all cellphones, I pushed on ahead assuming #1 to be my problem. ("See" includes dropping and installing a file explorer onto the tablet as well.)
With this is mind, the next course of action was to somehow get this "/persist" folder back. It seemed like the best way to do this would be to flash a stock ROM (link in Part 2) or ask the community to give me files without even trying to solve things on my own. So in the spirit of remaining a lurker I chose the former. Flashed fine, booted fine, ran.... okay-ish (the status bar "System UI" would crash every 10 seconds, ROM was a means to an end so I didn't care), but the Wifi WORKED! However, I still didn't find a /persist folder and the tablet didn't show up in windows... "Weird but okay, whatever let's do this." Load up recovery again, wipe everything, see if I can get Katshmallow to load again...
Part 1.5: And here we are. tl;dr I'm a scrub at anything android and after 12+ hours of tom****ery, I'm in a bootloop using Katshmallow v29 (v27 made no difference). The "bootloop" is in the form of the ASUS logo appearing with the usual "UnLocked" message in the top for a minute or two, then a reset, rinse, repeat. I am able to boot into recovery and mess around in TWRP just fine, so my ignorance hasn't completely wrecked me... yet.
The information that I believe is most pertinent to my current issue is:
I unlocked using ASUS' utility for the TF700. It worked no problem and with how compatible things seem to be between the two, I don't think this is an issue (especially considering I've flashed and booted system more-or-less just fine).
The most recent ROM I flashed was this [ROM] TF201 JB JRO03C 10.4.2.15 (US) Stock Deodexed + Mods [Unlocked BL]. I figure that this did something (maybe changed the bootloader?) that Katshmallow does not agree with. If I hadn't already spent the better half of a day working on trying to get things working, maybe I would do more research and figure out the inner workings on my own, but I'm done bashing my head against a brick wall that's only pushing me further back.
I am currently running KANG TWRP 2.8.7.2 for the TF201T (yes, the device I'm specifically running). The problem existed with some TWRP 2.8.x for the TF300 as well.
The bootloader message is "Android card-hu-user bootloader <1.00e> released by "US_epad-10.4.2.15-20120917" A03 ... Oh son of a-
Part 2: So I'm a dumb*** who can't read. Okay, I need to know how to get from my current bootloader (10.4.2.15) to the one Katshmallow requires (10.6.1.27.1). In typing this, I realized that the stock ROM I used to test stuff is why I've been screwed for the past 5 hours (coupled with my ignorance of course). In my quick 2 minutes of research I found this: [GUIDE][13/11]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices. I fancy methods 2 and 3, I can do those, but that doesn't change the fact that I know NOTHING about the bootloader and what I need to update it (but apparently I know how to give myself a headache by downgrading it).
Any help will be greatly appreciated. Oh, and if you know of how to solve the Wifi issue or the likely related /persist folder issue in the wall of text above, please I beseech you to tell me.
Disclaimer: My "research" is not at all limited to the links in the post. I've spent 90% (or more) of what's now probably 13-14 hours working on getting this piece of- getting things to just go right. So... tired...
Update: The problem has changed to my second post that I will be pasting here to save people the trouble:
So the problem as it stands now. I'm cannot seem to flash a different custom recovery and whenever I try to flash a ROM I get "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". I give up for now... Maybe I'll try again tonight. I'm running bootloader 10.4.2.15 and TWRP KANG 2.8.7.2 (which seems to require a 14.10 bootloader). In this mess, I don't know what to fix nor how to fix it. The angles I see are fix the custom recovery or fix the error/symlink problem since the bootloader version seems to be dependent on successfully flashing ROMs.
Update2: So I managed to upgrade the bootloader by somewhat forcefully flashing Hairybean. While Katshmallow said "JB 4.2.1 BOOTLOADER VERSION 10.6.1.27.1," I glazed over this because I didn't know the importance of the bootloader and there was no other mention of the bootloader in the post (no mention of Hairybean or a download link or a "More information" link). I still have no one but myself to blame, just bitter that I have to blame myself in the first place.
For the time being, I'm following the somewhat better instruction on found in this thread([ROM] [TF201] KatKiss 5.1.1 - v30 [MultiWindow] [Stable] [RRO]) and will be picking up Katshmallow at the "wipe" step (currently waiting on the /data format). I downloaded the newest version of TWRP for TF201T and it's working just fine (note how that thread also doesn't mention anything aside from "MUST BE ON THE HAIRYBEAN BOOTLOADER ENDING IN 27.1" While that's such an obvious and blatant statement that should have inspired some research, my ignorance blinded me).
Now that I know for a fact that I am running the right TWRP and the right bootloader, I am going to pray that I can at VERY LEAST flash and boot into Katshmallow. Whether or not the Wifi problem persists will be for another thread.
IT BOOTS! YAAASSS. How do I close this embrassment of a thead?
Sorry I can't be of more help but what I CAN say is:
- read instructions thoroughly with any release. Sometimes a modified TWRP or other file is posted that you must use even if you have a newer version. You might also have to bounce around to other posts along the way to install/update all of the necessary files.
- keep a written log of changes you've made with notes on reversing them. Changing the bootloader means you can't go back unless you revert it back first. I can back track everything I've done based on my own notes, much easier to understand than someone else's notes or directions.
Good luck and be patient. Don't make more than one change at a time and get it working or revert back before trying something totally different.
Sent from my LG-H811 using Tapatalk
HorthLithperer said:
Sorry I can't be of more help but what I CAN say is:
- read instructions thoroughly with any release. Sometimes a modified TWRP or other file is posted that you must use even if you have a newer version. You might also have to bounce around to other posts along the way to install/update all of the necessary files.
- keep a written log of changes you've made with notes on reversing them. Changing the bootloader means you can't go back unless you revert it back first. I can back track everything I've done based on my own notes, much easier to understand than someone else's notes or directions.
Good luck and be patient. Don't make more than one change at a time and get it working or revert back before trying something totally different.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Thank you for replying nonetheless. I'll keep the note thing in mind. Regarding the bouncing around to get the files necessary, I've done plenty of that. When installing a new ROM, I made sure to follow the links as they were given and did further research where things weren't clear. My current problem stems from that fact that, 1: I have no point in which to restore back to due to my aforementioned ignorance and oversight of basic Android terminology; and 2: The next step is to revert the bootloader, that of which I have no clue how to do or where to start since my preliminary google search. Even if I had been taking notes, no one mentions how to do this without a backup. And so I'm on a hunt to find this information and for posterity, I'll post my quest here:
Google search: "tf201 bootloader version"
Upgrading from ICS Bootloader > [ROM] [TF201] [JB Bootloader] CyanogenMod 10 Unofficial - JZO54K - Oct 30 2012 - I learned that apparently certain ROMs can overwrite the bootloader, extrapolated from:
4) Needs the new Jelly Bean 10.4.2.15 bootloader [IMPORTANT: Flashing over an incorrect bootloader can permanently brick you device. The Oct 13 2012 build includes the bootloader upgrade and can be flashed over any ROM/bootloader]
Google search: " update tf201 bootloader"
[GUIDE] How to manually update/restore firmware (TF101, TF201, TF300, TF700, TF701) - Post #2 sent me to ASUS official support wherein I downloaded "V10.4.2.18." This is a test in hopes that I can get a ROM running and see if the bootloader changes. I'm not able to use the methods in that thread as I do not have a system nor a microSD, as such I'll flash it the way I have been. Same custom recovery as before. Run the usual wipe (Dalvik, System, Cache, Data, Internal). Drop ASUS ROM onto pad's internal. Attempt flash... Error: "E:Error executing updater binary in zip"
More research, now trying to find out what this error is. Tried this and read a couple pages from here. Settled on reflashing TWRP. While looking up the command again, I came upon here, then went to the first post of that thread here, then from the TWRP link in that post to here (yes, I see the big TF700T at the top, I also see the big MUST BE ON A BOOTLOADER ENDING IN 14.10).
Okay so, I have 10.4.2.15 and am going to have to jump through several hoops to get to the mysterious 10.6.1.27.1. Annnnd It seems as though I have a custom flash that doesn't support my bootloader (which I feel should've been an issue up until now?) I just want to boot into A ROM, so either I find a ROM that supports the bootloader and probably flash a recovery that does as well...
Googled: "10.4.2.15 tf201" Came upon this, tried to flash twrp2.3.1.0 for the tf201 (downloaded straight from their website)... Still in 2.8.7.2 ... Okay, what? FINE! Screw it, redownload the stock ROM that got me into this mess (here) and see if I can even flash that. Wipe all the usual but internal storage because I'm lazy and afaik it doesn't need to be wiped anyway. Error: "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". Popped into here, unmounted the things, reformatted /data to f2fs (this may just be a Marshmallow thing though... it was ext_4 before I reformatted) Same error... Kill me.
So the problem as it stands now. I'm cannot seem to flash a different custom recovery and whenever I try to flash a ROM I get "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". I give up for now... Maybe I'll try again tonight. I'm running bootloader 10.4.2.15 and TWRP KANG 2.8.7.2 (which seems to require a 14.10 bootloader). In this mess, I don't know what to fix nor how to fix it. The angles I see are fix the custom recovery or fix the error/symlink problem since the bootloader version seems to be dependent on successfully flashing ROMs.
I'm sure there's someone out that that can point to me the correct tree in this forest using their superior knowledge of the subject. Having grown up with computers, even a new error message is something to work with. But when you can't even get results (success nor detailed failure), then it becomes downright no fun.
So, about like a week ago, I made a post on XDA developers named "Well, I f**ked up. Badly.." and basically, this is what it contained.
Alright, here goes.
So one day I was interested in flashing a new custom ROM (Preferably LineageOS) to my Huawei Mate 10 Lite. Long story short, it's now soft bricked. Only TWRP is working.
But, that's not enough information. Here's the fully story.
After realizing I could not get the Bootloader unlock code using the official method, I've tried DCUnlocker. I paid, and got my code.
I've installed HiSuite, 274829 drivers and finally unlocked the Bootloader. Now, the phone said "This device is unlocked and can't be trusted", but it booted fine. YES!
After that, I downloaded LineageOS 15.1 and flashed it. Before flashing it, I formatted everything, wiped cashe, davlick ect... And.. made my biggest mistake.
Not making a nandroid backup (dammit).
Don't ask me why, I thought it would go well (ugh).
Anyways, I flashed it, error 7. Alright, removed the assert lines. Flashed it again, and it worked, but right at the end, another error? It was error 7, again, but a little different.
This time, it said "failed to mount /dev/block/bootdevice/by-name/vendor at /vendor: device or resource busy"
Okay, now I'm starting to get worried. Like, REALLY WORRIED.
It also said it failed to execute a line in the updater script, one of the last lines. But I would not delete it, just in case.
When I tried to boot, nothing. Went back to Google.
At this point, I learned that any Treble ROM will NOT work with Android version of 7.1. shhhiiii
I was on EMUI 5.1 aka 7.0, and this was worrying. At this point, I tried to return to EMUI 5.1, but since there was no backup, well...... To Google we go!
I did not find any stock room that running EMUI 5.1, but only found EMUI 8.0. I did find a stock room on 7.1, but I'm not paying 15 dollars for it. Not about that life.
I tried the dload method, but apparently my sdcard is on FAT32, and because of that I cannot upload the UPDATE.APP to it.
I've also tried eRecovery, but to no avail. "Failed to get package".
So now I'm stuck on a couple of options, and I need help from you, the XDA community.
1) Remove the line that's causing the issue but at the cost of it maybe not working
2) Somehow format the sdcard and somehow upload the update.app to it
3) Somehow update Android's system to Project Treble, although not sure it's possible since there is no OS.
4) ?????????????????
Please, help me. I'm in hell right now.
Anyways, I've tried restoring the phone for 3 days straight to EMUI stock rom, so I could update it manually to Oreo 8.0 and THEN install LineageOS 15.1. However, I literally could not find ANY SINGLE ROM on planet earth for Huawei Mate 10 Lite, on EMUI 5.1. I was so desperate to fix the phone that I just gave up and installed Elemental which was based on EMUI 5.1. Sure, phone working great, but not what I wanted.
I wanted LineageOS 15.1, not a rom based on EMUI. So, my question is, how do I update it to 8.0?
In the post, people suggested to manually flash the stock rom (8.0), but I couldn't find the stock rom. Also, yes, I tried TeamMT's site, xml tree not working blah blah blah site's dead.
So, what do I do?
Here's the link to the post, if anybody wants to read the replies
https://forum.xda-developers.com/mate-10/help/fked-badly-t3868233
I'm trying to flash the most current/last official ROM from the ASUS website. I'm using TWRP. I currently have a custom Android 7.1 ROM installed.
I wiped the table with TWRP and am trying to install the ASUS ROM. It looks like it's working and then I get a red error message that says something about failing with ERROR: 7.
Any suggestions?
Sorry to raise this old topic but ...
This is the precisely the issue I'm having now. It appears the official ASUS ROM fails to install on a modified (or rooted?) tablet.
What I've been experimenting with instead is the information in this thread.
It looks promising, but I'm having a bit of trouble finding some of the files it mentions as the post is rather old, and some of the things it references don't appear to be hosted.
Give it a try, and see if you get further than I did (and let me know if you do get it work, how you did it!).
Cheers, and good luck.
JoeDrunk said:
I'm trying to flash the most current/last official ROM from the ASUS website. I'm using TWRP. I currently have a custom Android 7.1 ROM installed.
I wiped the table with TWRP and am trying to install the ASUS ROM. It looks like it's working and then I get a red error message that says something about failing with ERROR: 7.
Any suggestions?
Click to expand...
Click to collapse
try following this thread. if i recall right, this guide worked.
[Q] TF201 cannot go into recovery and cannot boot, only in fastboot
Hello xda people, I tried to flash my TF201 with stock 4.1.1 ROM and 10.4.2.18 bootloader and I think I messed up the bootloader because now it can only go into USB mode - RCK, Wipe Data and Android all return "unrecoverable bootloader error"...
forum.xda-developers.com
Fytdyh said:
try following this thread. if i recall right, this guide worked.
[Q] TF201 cannot go into recovery and cannot boot, only in fastboot
Hello xda people, I tried to flash my TF201 with stock 4.1.1 ROM and 10.4.2.18 bootloader and I think I messed up the bootloader because now it can only go into USB mode - RCK, Wipe Data and Android all return "unrecoverable bootloader error"...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for this, but I have tried these. I keep hitting the same obstacles, the biggest one being that the files needed for these solutions are no longer available in many cases.
NotTheLips said:
Thank you for this, but I have tried these. I keep hitting the same obstacles, the biggest one being that the files needed for these solutions are no longer available in many cases.
Click to expand...
Click to collapse
which files are no longer available ? for me the asus official stock roms are still working and the adb installer (the latest version) as well. tested just now.