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
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
AndriyEtch said:
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
Click to expand...
Click to collapse
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
cva_kabil said:
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
Click to expand...
Click to collapse
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
AndriyEtch said:
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
Click to expand...
Click to collapse
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
cva_kabil said:
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
Click to expand...
Click to collapse
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
I dont think so... I hv not tried... But as of i know if u edit it wrongly, u will not be able to flash that file. . Try others methods first... Hope it works
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
Hi OP, sorry for joining late to the party
So the thing is the OnePlus X is at opposites now since the official MM release on 29th September. The thing is if you are running the old bootloader (OxygenOS 2.x.x) or any ROM based on it, then the New TWRP will not boot, neither will the Stock Recovery that is hosted on the OnePlus download section for the X, which is where i assume you download the stock recovery from, right ? Also note that the official recovery hosted on the TWRP website is also yet to be updated, we're working on that.
So you are on the old Bootloader. Simple stuff. I have posted my guide a lot of time around the forums, its gained a lot of merit. You could follow it for your update process. I'll leave a link below. In case you wanna verify that the old bootloader is causing the issue my Index Thread pinned in the general section has a link for the Stock recovery for Old bootloader, try flashing that via fastboot, if it successfully boots then you're set.
Comprehensive guide to Update to Marshmallow Bootloader
The above guide is centered to the thread i have posted it on but the process is 99% the same. In the end, you could just stay with Oxygen OS 3.1.3, or flash any custom ROM based on the new Bootloader.
Now regarding your query about editing the META of the ROM, well Yes to an extent it IS risky if you ain't careful because my guide guides you to delete the one single line that removes the device check, so as long as you use the modified zip on OnePlus X only, there will be no issues.
Let me know for any further clarifications, also you're welcome to join our support group on Telegram, all of our developers are active there. Ping me (@ mellogang_unite) for an invite
I have this canadian version of Huawei honor 5x, and I've been scouring to find answers to whether if am i able to flash a custom rom such as cyanogenmod or not. Can anyone please help me out with this; I've already made several post and it get unanswered. Sofar I've managed to unlock the bootloader, flashed twrp, and rooted it. When I tried installing CM 13 from a thread on this site, I always get the "error 7" and I tried deleting the 2nd line in the meta-inf and rezipping the rom and reflashing; results remain the same.
Here's more info on my phone:
Build#: KII-L05C654B330
EMUI 4.0
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Chaos Storm said:
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Click to expand...
Click to collapse
Hai bud , he mentioned that he is on emui 4 . So we have necessary proof that he is on marshmallow which we require to flash a rom on 5x:highfive:
And after thinking for a while , the last version (latest updates) have modem issues so custom roms may have stopped working for u due to this. I have solutions for u .
Hi Chaos Storm!
I'm fellow Canadian and just got GR5 on kijiji for my daughter.
Just couple quick questions: what ROM do you have now? (i.e. which one you recommend?)
Are there any tricks to flash? I'm having issue now - unlocked bootloader, flashed TWRP, SU. But when I try to boot into TWRP I get stock recovery. Can boot into TWRP only from TWRP app or ADB command...
Then I tried to flash LinOS 14 but got Error 7...
Thanks in advance!!!
Chaos Storm said:
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Click to expand...
Click to collapse
Goldenmeadow said:
Hi Chaos Storm!
I'm fellow Canadian and just got GR5 on kijiji for my daughter.
Just couple quick questions: what ROM do you have now? (i.e. which one you recommend?)
Are there any tricks to flash? I'm having issue now - unlocked bootloader, flashed TWRP, SU. But when I try to boot into TWRP I get stock recovery. Can boot into TWRP only from TWRP app or ADB command...
Then I tried to flash LinOS 14 but got Error 7...
Thanks in advance!!!
Click to expand...
Click to collapse
Not sure what happened there. When you unlocked the bootloader did you reboot at least once to allow it to reset all data? I've had issues before if I unlock a bootloader then immediately flash something.
I know TWRP should ask you if you want to prevent stock recovery from being restored when you exit, always say yes. (It should only ask once)
Did you edit the updater-script in the Lineage install zip? You need to remove the first line or two where it says: "assert device" or something like that.
If all else fails, boot the phone into fastboot, flash twrp again, and make sure you "fastboot reboot recovery" so the unit doesn't have a chance to try and restore the factory recovery. Then try flashing your rom again.
Thanks for reply! With the help of fellow members I figured it out - I was holding POWER button TOO LONG And if that happens, phone goes into built in recovery... You suppose to let button go once you see first splash screen.
So it's all good!
Thanks!!!
Chaos Storm said:
Not sure what happened there. When you unlocked the bootloader did you reboot at least once to allow it to reset all data? I've had issues before if I unlock a bootloader then immediately flash something.
I know TWRP should ask you if you want to prevent stock recovery from being restored when you exit, always say yes. (It should only ask once)
Did you edit the updater-script in the Lineage install zip? You need to remove the first line or two where it says: "assert device" or something like that.
If all else fails, boot the phone into fastboot, flash twrp again, and make sure you "fastboot reboot recovery" so the unit doesn't have a chance to try and restore the factory recovery. Then try flashing your rom again.
Click to expand...
Click to collapse
Chaos Storm said:
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Click to expand...
Click to collapse
Would I be able to get a copy of your ROM? I am with Cityfone (Rogers subsidiary), and am looking to network unlock, I can't seem to find my backup from when I started flashing custom ROMs
kenneth_82614 said:
Would I be able to get a copy of your ROM? I am with Cityfone (Rogers subsidiary), and am looking to network unlock, I can't seem to find my backup from when I started flashing custom ROMs
Click to expand...
Click to collapse
I will have a look. As things would be, I also need to restore my GR5 so I'll find it for both of us.
So far my device is magisk rooted and unlocked, with a few run of the mill tweaks here and there. Is anyone aware of this device supporting custom recoveries after unlocking? I suspect TWRP might work with minimal modification if any, but I haven't yet tried to flash anything beyond magisk and figured I would ask for other people's experiences here before I attempt to do so.
Thanks!
706trades said:
So far my device is magisk rooted and unlocked, with a few run of the mill tweaks here and there. Is anyone aware of this device supporting custom recoveries after unlocking? I suspect TWRP might work with minimal modification if any, but I haven't yet tried to flash anything beyond magisk and figured I would ask for other people's experiences here before I attempt to do so.
Thanks!
Click to expand...
Click to collapse
Somebody help i also have a new phone samsung a11 and successfully rooted it with magisk unlocked bootloader and rom that i found on sammobile (same model same CSC) and i want to also know if its possible getting the TWRP on a magisk rooted device without having any trouble
https://drive.google.com/file/d/1DydHY_Q_paR4QcLhhyE8ih3hYZpqK3RM/view?usp=drivesdk is the device tree with a bootctrl error right now I don't have time to keep working on it for a while but if we get it working we can build ROMs and twrp
Working TWRP but very unofficial! But very useful!
Hi, so I just got this phone and I see there's not much on the postings like with links to a working TWRP, in particular. So I did some digging around and experented, and found this TWRP. It's from the Moto G9 Play (guamp). But it works, at least...
forum.xda-developers.com
See instructions by me to boot it from Android or use fastboot to boot it