(i made sure to do a backup)
Let me sum up what I have done:
I've managed to follow a guide on a wiki(I lost the link however, since I ATTEMPTED to give up on this) that involved me downgrading my firmware, then do some steps to install cyanogen 1.4. Afterwards, I got to step that required me to rename some file to update.zip. I followed that step and noticed my computer didn't convert the file to a zip file(it remained as a img file) but continued anyway while finding that odd.
Afterwards, cyanogen tells me that it cannot find the zip file. I've search most of google and a bit of this site, and i've seen various solutions that failed me such as:
-renaming the update.zip to update
-using android sdk(which i have no clue on how to use)
Anyways, finding out that I was foolish to do all of this without prior knowledge, I decided to go back to my original firmware. However, on the phone's reboot, cyanogen came up again for some reason, and didn't let the update be applied.(I don't recall the error)
Anyways, I selected reboot and got to my phone's main menu then some music started playing automatically. I should note, before I did the update, I placed all of my backed up data(while still having the original copy on my pc) on my phone so it might've been some music that the original owner had. Now, on the menu, i'm getting this error "The process android.process.acore has stopped unexpectedly. Please try again." all the time. Since this error constantly pops up, I can't do anything.
So if you managed to read my long and boring story, let me ask one question:
How do I get my phone back to normal if rooting is impossible at this point?
First question is what firmware is your htc magic currently on? And by reading everything I guess your phone isnt rooted...
Dataslycer said:
First question is what firmware is your htc magic currently on? And by reading everything I guess your phone isnt rooted...
Click to expand...
Click to collapse
It's on 1.5 currently. Also as a little update:
I fixed the "not being able to do anything on the menu" problem by doing a factory reset. Afterwards, I learned the SDK a little bit more and have the tools, pc driver, and fastboot on my pc. However, i'm getting the error:
FAILED (remote: not allow)
Just a bump. I need all the help I can get on this one. Even a premade update.zip would help me GREATLY.
One last bump. I promise.
[SUMMARY] - If you're bored or find this kind of thing funny you could read this post from the bottom up and watch a noob go from freaking out, to learning how to troubleshoot then finally resolving his issue... all of this just by reading the FAQ thread and following some advice found there. I've learned my lesson... read XDA *before* trying to flash a new ROM.
[SOLVED] - Solution was to flash the boot.img from stock ROM. Once I did that the phone rebooted and went into the typical device setup. Now I guess I can update my ROM.
[FIRST UPDATE]
Turns out a lot of exactly what I was looking for is on the FAQ page (first bullet in Q15, no less). Trying what I found there. Please don't blast me with, Maybe you should have read the FAQ... I've been all over the place trying to find something that would work quickly... I only have one phone and I commute into Philly for work so I need a working phone... Now that I've found the XDA HTC ONE X + FAQ, I think I'll be fine. Thanks for the great site... so much info on here to read... good for long train rides.
[ORIGINAL POST]
Hi, I ran into a problem trying to flash CM to my HOX+ (AT&T). I followed the instructions here (wiki.cyanogenmod.org/w/Install_CM_for_enrc2b), but that was for the International version, not the AT&T... Dumb? Guess so, I don't know much about the difference, but it's what happened. I've tried to connect to the phone (per the instructions on the wiki) to adb push the ROM I want to flash, but I keep getting the device not found error. The instructions warn of possible driver error on the PC, but I haven't found a driver yet that will allow me to connect. I can get into recovery (CWM-based Recovery v6.0.2.7) but with no ROM on the sdcard I have nothing to flash and can't figure out how to get the file onto the device. The wiki should probably mention putting the ROM on the device prior to going through the HTC unlock steps, just in case, but maybe they assume a more cautious user than I am. I've tried to flash from sideload, but don't know if that is even possible?
Can someone point me in the right direction, or start asking questions to help me figure out what my next step is? Just want to get back to a working phone...
Thanks!
Signature?
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.
[SOLVED]
My device: OnePlus5 A5000
First of all I want to mention that I am kind of a novice on rooting so please do not go hard on me, mistakes happen. So I was running the lastest version of Android on my phone (Version 5.1.7) and decided to root my phone and use Magisk. So I unlocked my bootloader and I was going to work with TWRP. But I did a terrible mistake and wiped the system while experimenting. I know this is a very stupid mistake but it sadly happened. So my phone is basicly empty and has no OS running everytime with a black screen whenever I enter the system . The only thing I am able of doing is transfering files from my PC to my phone and using TWRP. I downloaded the original and latest OS version from OnePlus' site and moved it inside my phone. I then went on to install it via TWRP but I faced "Error 7". I did a research on that and I found out that it happens because it detects if it is a compatible ROM with the whole "assert" thing in META-INF in the "updater-script". I went on to unzip it and edit it with NotePad++to remove "assert" but "assert" was no where to be found since it was the original version. I then went on to try installing the lineage version for OnePLus 5 not knowing if it was going to work and it turned out to not work at all. I also want to mention that whenever I tried removing the "assert" from the lineage version I got an error of "Invalid zip file format!". Finally I want to mention that in order for me to view the files I worked by repairing the partition and converting it to FAT and exFAT(I did NOT convert it back to EXT4 yet). In case I am missing something or there is a way of solving it please let me know, I would really appreciate it! Also if you do not mind be as decscriptive as possible since I am a novice and I do not know everything like other individuals. I will though make a deep research on every single comment I get, I am not waiting for an easy solution on such a subject. I hope I can fix my phone with your help in the near future. Thanks in advance!
Files that I have downloaded (if necessary):
1)ADB Files
2)Original version of latest OnePlus 5 Update (5.1.7) (.zip file)
3)Lineage ROM for One Plus 5 (15.1-20181127-nightly-cheeseburger-signed)
4)TWRP (3.2.3-0-cheeseburger)