Related
I am using TPRW recovery 2.7.1.0 to sideload the latest cyanogenmod cm-11.0-XNPh25R. I use the apply update option and sideload it from the internal storage. The error I am getting is E:footer is wrong E:signature verification failed. Can someone kind enough to help me? Please.. Thanks.
peacewar said:
I am using TPRW recovery 2.7.1.0 to sideload the latest cyanogenmod cm-11.0-XNPh25R. I use the apply update option and sideload it from the internal storage. The error I am getting is E:footer is wrong E:signature verification failed. Can someone kind enough to help me? Please.. Thanks.
Click to expand...
Click to collapse
Am I not supposed to sideload a rom?
peacewar said:
Am I not supposed to sideload a rom?
Click to expand...
Click to collapse
Whatever, the problem is resolved. I just fastboosted the phone to flash the latest version of cyanogenmod. There was no point rooting the phone anyway and It was a bad part of me to try to flash it via recovery mode.
can you tell me how to do this?
peacewar said:
Whatever, the problem is resolved. I just fastboosted the phone to flash the latest version of cyanogenmod. There was no point rooting the phone anyway and It was a bad part of me to try to flash it via recovery mode.
Click to expand...
Click to collapse
can you tell me how to do this?
i have the same problem
xravivx77 said:
can you tell me how to do this?
i have the same problem
Click to expand...
Click to collapse
You need to be specific about what your problem is.
Transmitted via Bacon
signature error
timmaaa said:
You need to be specific about what your problem is.
Transmitted via Bacon
Click to expand...
Click to collapse
now i have XNPh25R and when i try to manual update i got signature error.
xravivx said:
now i have XNPh25R and when i try to manual update i got signature error.
Click to expand...
Click to collapse
Come on, details, details, details.
Transmitted via Bacon
timmaaa said:
Come on, details, details, details.
Transmitted via Bacon
Click to expand...
Click to collapse
i have oneplus one that i bought to months ago from pandawill and since i got it i never get updates for him.
i try to check for update in the phone but it say i dont have any.
i try to manual update but got error : Signature verification failed
i really need your help to update my phone because it got a loot of problems in the screentouch and battery.
xravivx said:
i have oneplus one that i bought to months ago from pandawill and since i got it i never get updates for him.
i try to check for update in the phone but it say i dont have any.
i try to manual update but got error : Signature verification failed
i really need your help to update my phone because it got a loot of problems in the screentouch and battery.
Click to expand...
Click to collapse
The update is failing for a reason. What is your current version? What version is the update you're applying? Do you have any modifications to your current setup at all?
Transmitted via Bacon
timmaaa said:
The update is failing for a reason. What is your current version? What version is the update you're applying? Do you have any modifications to your current setup at all?
Transmitted via Bacon
Click to expand...
Click to collapse
i dont know this is stay like i got it 2 month ago .
im pretty sure that when i order it from pandawill they do root because they got the phone with oppo and change it to cm11 before the shipping.
cyanogenMod - 11.0-xnph25r
android - 4.4.2
build num - kvt49l
xravivx said:
i dont know this is stay like i got it 2 month ago .
im pretty sure that when i order it from pandawill they do root because they got the phone with oppo and change it to cm11 before the shipping.
cyanogenMod - 11.0-xnph25r
android - 4.4.2
build num - kvt49l
Click to expand...
Click to collapse
I think the best idea for you is to start from scratch. Unlock the bootloader (if it isn't already unlocked), install TWRP recovery, then install Calkulin's stock rooted 38R ROM. From there you should have no problems receiving further updates.
Transmitted via Bacon
timmaaa said:
I think the best idea for you is to start from scratch. Unlock the bootloader (if it isn't already unlocked), install TWRP recovery, then install Calkulin's stock rooted 38R ROM. From there you should have no problems receiving further updates.
Transmitted via Bacon
Click to expand...
Click to collapse
when you say that it sound easy
do you have GUIDE for me?
xravivx said:
when you say that it sound easy
do you have GUIDE for me?
Click to expand...
Click to collapse
Yep, I have a guide thread, the link is in my signature.
Transmitted via Bacon
timmaaa said:
Yep, I have a guide thread, the link is in my signature.
Transmitted via Bacon
Click to expand...
Click to collapse
can you tell me which step i need to do?
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
xravivx77 said:
can you tell me which step i need to do?
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Steps 1, 2, 3, and 5, in that order.
Transmitted via Bacon
normal people and incorrect e-footer
Hi guys. I'm trying to flash the rom on a galaxy S4 to get rid of bloatware and free up memory. It's been a bit of a learning curve. I softbricked the machine and rescued it with odin but of course that is a stock rom and not what I want. EVERY CUSTOM ROM I HAVE TRIED ABORTS INSTALL DUE TO FAILED SIGNATURE VERIFICATION. incorrect e-footer or whatever. Does anybody KNOW how this is caused? Why are files not being copied bit for bit?
I want to say first that I have done a fairly thorough search of your archives to no avail. That is because most related threads are *****ing about the threads or the personalities involved along with mixtures of real and perceived breaches of this sites code of conduct and etiquette in general. I am not interested in any of that. Neither do I want to hear from the guy who danced widdershins round a cauldron waving his phone in the air telling me it fixed it for him. Please, can somebody that knows reply? Once I know the why I hope to fix it with a binary file editor. If somebody knows the why and the "how to fix" even better.
many thanks
Warwick
warwick512 said:
Hi guys. I'm trying to flash the rom on a galaxy S4 to get rid of bloatware and free up memory. It's been a bit of a learning curve. I softbricked the machine and rescued it with odin but of course that is a stock rom and not what I want. EVERY CUSTOM ROM I HAVE TRIED ABORTS INSTALL DUE TO FAILED SIGNATURE VERIFICATION. incorrect e-footer or whatever. Does anybody KNOW how this is caused? Why are files not being copied bit for bit?
I want to say first that I have done a fairly thorough search of your archives to no avail. That is because most related threads are *****ing about the threads or the personalities involved along with mixtures of real and perceived breaches of this sites code of conduct and etiquette in general. I am not interested in any of that. Neither do I want to hear from the guy who danced widdershins round a cauldron waving his phone in the air telling me it fixed it for him. Please, can somebody that knows reply? Once I know the why I hope to fix it with a binary file editor. If somebody knows the why and the "how to fix" even better.
many thanks
Warwick
Click to expand...
Click to collapse
You're in the wrong section, this is the OnePlus One section. You need to find the S4 section and ask there.
Heisenberg said:
You're in the wrong section, this is the OnePlus One section. You need to find the S4 section and ask there.
Click to expand...
Click to collapse
This is hopeless. My comments about moderation have met more moderation. Apparently this is the type of site that likes to flood its own archives with spam. goog on ya Anyways there seems to be little or no evidence that the verification problem is device specific. quite the opposite in fact. Maybe somebody that KNOWS will respond. i'll give it a week and see
cheers
warwick512 said:
This is hopeless. My comments about moderation have met more moderation. Apparently this is the type of site that likes to flood its own archives with spam. goog on ya Anyways there seems to be little or no evidence that the verification problem is device specific. quite the opposite in fact. Maybe somebody that KNOWS will respond. i'll give it a week and see
cheers
Click to expand...
Click to collapse
We have device sections for a reason. Each device has its own quirks, requirements, and problems. It's important for you to post in the right place because then you'll be able to get assistance from people who are familiar with your device and those quirks, requirements, and problems that come with it. There's Q&A section for your phone, that's where you need to be addressing the problem you're having. I'm not moderating you, I'm trying to help you get the help you need. Posting in the wrong device section isn't going to achieve that. If you drive a Ford you wouldn't post in a VW forum for help, the same logic applies here.
I just updated to Lollipop. I tried to run TWRP without flashing (use fastboot boot command) and it run smoothly. However, after I encrypted my phone TWRP cannot decrypt the storage like it could in Kitkat even though I enabled encryption in Kikkat too
nerodarknight said:
TWRP cannot decrypt the storage like it could in Kitkat
Click to expand...
Click to collapse
Correct.
rootSU said:
Correct.
Click to expand...
Click to collapse
So no worry then, I thought it's only my phone lol. Do you happen to know if TWRP or CWM will make it compatible with Lollipop encryption?
nerodarknight said:
So no worry then, I thought it's only my phone lol. Do you happen to know if TWRP or CWM will make it compatible with Lollipop encryption?
Click to expand...
Click to collapse
Forget CWM, it doesn't even support encryption for KK.
Anybody know how long it has taken the devs of TWRP to update to the new encryption for previous versions? Just curious about when this will work again.
Thanks for any info,
Fly
FlyOnTheWall43 said:
Anybody know how long it has taken the devs of TWRP to update to the new encryption for previous versions? Just curious about when this will work again.
Thanks for any info,
Fly
Click to expand...
Click to collapse
It will come when it comes.
Lethargy said:
Forget CWM, it doesn't even support encryption for KK.
Click to expand...
Click to collapse
Forget encryption, It doesn't even support /sdcard for JB!
Lethargy said:
It will come when it comes.
Click to expand...
Click to collapse
Is it just me or are these responses the least productive thing on the internet?
I would understand if I came in here demanding an exact ETA, but I feel like I respectfully asked for estimated past turn around times so that I could have a basic idea (2 weeks/2 months/2 years) of when I'll be able to use TWRP on my phone again.
And I understand that the devs are probably working very hard on getting this done (I see that there is version 2.8.2 for the Nexus 9 that allows decryption on Lollipop, so maybe they're really close), and although I am an entry level programmer, this kind of stuff goes way over my head, I do really appreciate the work that they do.
I am fairly new to the wonderful world of this level of Android customization and I'm just trying to learn how the process works.
Does anybody else have any useful info?
FlyOnTheWall43 said:
Is it just me or are these responses the least productive thing on the internet?
I would understand if I came in here demanding an exact ETA, but I feel like I respectfully asked for estimated past turn around times so that I could have a basic idea (2 weeks/2 months/2 years) of when I'll be able to use TWRP on my phone again.
And I understand that the devs are probably working very hard on getting this done (I see that there is version 2.8.2 for the Nexus 9 that allows decryption on Lollipop, so maybe they're really close), and although I am an entry level programmer, this kind of stuff goes way over my head, I do really appreciate the work that they do.
I am fairly new to the wonderful world of this level of Android customization and I'm just trying to learn how the process works.
Does anybody else have any useful info?
Click to expand...
Click to collapse
There isn't anything else to say other than what I did in the post. Check repos and see if there is any progress.
But still.
As mentioned, we don't know anything. We haven't had any feedback. You have access to the same info we do (TWRP dev thread and github). There is no point asking us the answer. You'd be more upset if no one answered at all.
Again, I wasn't asking for when the next version will be released, I understand nobody knows that... I asked for:
FlyOnTheWall43 said:
for estimated past turn around times so that I could have a basic idea (2 weeks/2 months/2 years)
Click to expand...
Click to collapse
Just a rough guess, that's all I'm wondering.
FlyOnTheWall43 said:
Again, I wasn't asking for when the next version will be released, I understand nobody knows that... I asked for:
Just a rough guess, that's all I'm wondering.
Click to expand...
Click to collapse
Without knowing the complexities of encryption and the development involved and the fact that past development turn around has nothing to do with the future, we can give only the same answer.
I'd say you can only ask the dev, but since that's against the rules, you'll just have to wait and find out when everyone else does. You have the same information available as we have, including past turn around dates.
New 2.8.2.0 with Android 5 encryption support is available at the TWRP site and confirmed working on my Nexus 5
I'm on AT&T Snapdragon 512gb S22U locked firmware AVG6. I want to sideload the ONE UI 5 Beta but I don't want to lose my data. Has anyone had success using this method and keeping their files?
I keep seeing mixed responses, some people on S908U1 were able to keep all their data and people on S908U were not able to keep data.
Any help would be appreciated.
I know flashing from U to U1 usually requires a clean install, but installing a beta shouldn't require that.
I think you can Samsung backup and sideload this update. Backups are a good habit.
No files were lost after my device was updated
If you don't want to risk losing data, then don't do it. Beta isn't for people who are scared of losing data.
Samsung Smart Switch is for backup of data, so I don't think that this is topic to open !!
peacey8 said:
If you don't want to risk losing data, then don't do it. Beta isn't for people who are scared of losing data.
Click to expand...
Click to collapse
I've actually installed many Betas in the past, and I've never had to wipe my phone or do a clean install. I'm not "scared", it's just inconvenient and time-consuming.
Kris_b1104 said:
I've actually installed many Betas in the past, and I've never had to wipe my phone or do a clean install. I'm not "scared", it's just inconvenient and time-consuming.
Click to expand...
Click to collapse
I have too, but by definition beta software is unstable and many problems can happen that can irrevocably cause data loss. It's best practice to backup and be prepared to lose data in case it happens, unless you don't care about your data.
You should only need to clean install if you are changing region firmware (ex U/U1). I'm not sure why you're trying to go the sideload method of getting on OneUI 5? Why aren't you just enrolling through the members app and OTA updating? OTA guarantees you won't lose any data. Going with sideloading, if you flash the wrong variant say goodbye to all your data because you'll probably soft-brick and have to factory reset. I'm just not sure I see any benefits to sideloading over going OTA unless I'm missing something here
1dopewrx05 said:
You should only need to clean install if you are changing region firmware (ex U/U1). I'm not sure why you're trying to go the sideload method of getting on OneUI 5? Why aren't you just enrolling through the members app and OTA updating? OTA guarantees you won't lose any data. Going with sideloading, if you flash the wrong variant say goodbye to all your data because you'll probably soft-brick and have to factory reset. I'm just not sure I see any benefits to sideloading over going OTA unless I'm missing something here
Click to expand...
Click to collapse
Because the Beta is not open to locked U firmware AT&T models. Can't use Samsung members to get in.
Sideloading is done when OTA is unavailable, as in my case.
peacey8 said:
I have too, but by definition beta software is unstable and many problems can happen that can irrevocably cause data loss. It's best practice to backup and be prepared to lose data in case it happens, unless you don't care about your data.
Click to expand...
Click to collapse
Thanks, I know all of this.
I've never had a Beta that caused any data loss.
Unless I manually did a clean install myself.
Update U1 variant no data was wiped
S908B, Exynos, beta didn't wipe anything.
U1 256GB unlocked from best buy. I didn't lose any data.
S22U Exynos, no data wipe when sideloaded beta...even the previously applied HEX theme was preserved
I'm more looking for people with locked U firmwares to share their experience.
I already know Exynos and Unlocked firmwares don't have data wipe after install.
@Kris_b1104 You've been asking this for several days now. It literally would have taken you less time to just backup, update, and restore if it wiped. At this rate, by the time enough people answer you, the beta is going to be over.
peacey8 said:
@Kris_b1104 You've been asking this for several days now. It literally would have taken you less time to just backup, update, and restore if it wiped. At this rate, by the time enough people answer you, the beta is going to be over.
Click to expand...
Click to collapse
Isn't this what the forum is for? Why do you have a problem with my question? Just ignore it and move on.
I see you asking multiple times in other threads how to change your CSC, but when I ask a question it seems to be an issue for you. Go touch grass.
Kris_b1104 said:
Isn't this what the forum is for? Why do you have a problem with my question? Just ignore it and move on.
I see you asking multiple times in other threads how to change your CSC, but when I ask a question it seems to be an issue for you. Go touch grass.
Click to expand...
Click to collapse
You can ask whatever you want, I'm just telling you time is running out to test the beta while you're being indecisive!
And actually I am at the park right now and touching grass! It is a beautiful feeling with the wind in my hair and the blades of grass running through my fingers while I play with One UI 5 beta. So cheers to that!
peacey8 said:
You can ask whatever you want, I'm just telling you time is running out to test the beta while you're being indecisive!
And actually I am at the park right now and touching grass! It is a beautiful feeling with the wind in my hair and the blades of grass running through my fingers while I play with One UI 5 beta. So cheers to that!
Click to expand...
Click to collapse
Thanks for your concern about my indecisiveness. I think I'll manage.
Enjoy the beta!
Kris_b1104 said:
I'm more looking for people with locked U firmwares to share their experience.
Click to expand...
Click to collapse
If you had stated this in the title of the thread , you would not have got all the answers you were not looking for......
brouwerchris said:
If you had stated this in the title of the thread , you would not have got all the answers you were not looking for......
Click to expand...
Click to collapse
It's implied in the first post...
Why is everyone so salty on XDA lately? It's quite humorous.
my POCO X3 PRO was in the ArrowOS A13 ROM, I modified some things like the Adreno Drivers to version 615 worked perfect, the next day I updated via OTA with OrangeFox and everything was still 100% after 2 days I was editing a video and it crashed It got stuck and didn't respond, then when it restarted it didn't start the ROM (it stayed in the POCO logo)... It goes into recovery but it takes at least 30 seconds to go in, I saw that I got 3 new partitions that weren't there (System_EXT, Product, ODM,) does not recognize the storage (the Micro SD does) the VAYU has dynamic partition, but my VAYU says that it has not tried to recover by My flash. it flashed ok but it didn't work. gives an error called (Block device required)
linuxinho said:
my POCO X3 PRO was in the ArrowOS A13 ROM, I modified some things like the Adreno Drivers to version 615 worked perfect, the next day I updated via OTA with OrangeFox and everything was still 100% after 2 days I was editing a video and it crashed It got stuck and didn't respond, then when it restarted it didn't start the ROM (it stayed in the POCO logo)... It goes into recovery but it takes at least 30 seconds to go in, I saw that I got 3 new partitions that weren't there (System_EXT, Product, ODM,) does not recognize the storage (the Micro SD does) the VAYU has dynamic partition, but my VAYU says that it has not tried to recover by My flash. it flashed ok but it didn't work. gives an error called (Block device required)
Click to expand...
Click to collapse
Other recovery like twrp, relocked bootloader? Block device required? You use Google? There are many threads about this error
joke19 said:
Other recovery like twrp, relocked bootloader? Block device required? You use Google? There are many threads about this error
Click to expand...
Click to collapse
I already tried different recoveries, and nothing, I can't find information about the problem, I don't know if it's a hardware problem or if it has to be repaired, I didn't expect that, I had been with the VAYU for 9 months and I've changed everything and nothing had happened to me. my bootloader is unlocked
Flash stock fw with fastboot
cuynu said:
Flash stock fw with fastboot
Click to expand...
Click to collapse
I already tried it, with my flash
linuxinho said:
I already tried it, with my flash
Click to expand...
Click to collapse
You use Google? In the morning I had read something over flash stock recovery and sideload... XDA and the net have many threads
joke19 said:
You use Google? In the morning I had read something over flash stock recovery and sideload... XDA and the net have many threads
Click to expand...
Click to collapse
I don't use google, I use the rom clean without gapps, I never use google services
Search for your error with Google
linuxinho said:
I don't use google, I use the rom clean without gapps, I never use google services
Click to expand...
Click to collapse
joke19 said:
Search for your error with Google
Click to expand...
Click to collapse
there is no information about the error, on the internet
linuxinho said:
there is no information about the error, on the internet
Click to expand...
Click to collapse
Okay
joke19 said:
Okay
Click to expand...
Click to collapse
I think I'll have to take it to a specialized technician
Use original fastboot rom from xiaomi. That's fixed my issues.
eliasnico said:
Use original fastboot rom from xiaomi. That's fixed my issues.
Click to expand...
Click to collapse
did you have the same error as mine?
A similar issue happened to me on stock ROM as well. I'm wondering if the boot partition is just dead and requires service?
linuxinho said:
my POCO X3 PRO was in the ArrowOS A13 ROM
Click to expand...
Click to collapse
Ok, although I don't understand why would you even use 13... but ok...
linuxinho said:
modified some things like the Adreno Drivers to version 615 worked perfect,
Click to expand...
Click to collapse
First mistake. You THOUGHT it worked perfect. Can you confirm that with dmesg and logcat? Absolutely no errors or crashes related to the gpu? Come on, man!
linuxinho said:
after 2 days I was editing a video and it crashed It got stuck and didn't respond,
Click to expand...
Click to collapse
How come, since it works perfectly?! I often encode, recode, cut and edit video on my unmodded ArrowOS 11 Poco X3 Pro, and have no issues. Unbelievable!
99 percent of Poco bricks on this forum are caused by inept people tinkering with parts of firmware they should not tinker with. Well, besides indian Poco versions, those were abysmal.
I had this issue also, i fixed it by flashing xiaomi.eu fastboot rom, used batch file (present in rom zip) for clean install.
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/xiaomi.eu_multi_POCOX3Pro_V13.0.4.0.SJUMIXM_v13-12-fastboot.zip/download
<Moderator Edit>: Deleted quote since I deleted the quoted post.
One can express such things in a different, non hurting way, remaining objective and not senseless aggressive. Finaly we all have made +/- stupid things in the past und hoped to get help from experts
<Moderator Note>: Thread cleaned.
Everyone, please always follow XDA Developers Forum Rules , especially in this instance, Rule 2.3:
2.3 Flaming / Lack of respect: XDA is about sharing, and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
Whenever anyone breaks any of our rules, please use the Report button in the lower right corner of their post and let us know so that we may address it, and at the same time please don't respond to the posts that break our rules - only report them. Thank you!
I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?
Hi,
Can you boot into bootloader?
Press power button until phone reboots while keeping volume down pressed.
From there you can install a factory image.
What version are you actually on?
Good luck,
Sébastien.
niftyXD said:
I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?
Click to expand...
Click to collapse
Flash the stock kernel (partitions) via Fastboot.
most users having issues like this end up getting it up and running using Google's official Android Flash Tool . It takes a lot of guesswork and/or misfires that a lot of users end up hitting the wall at...
I suggest making sure to check "don't wipe" or "keep data" (sorry, I've only used it twice, so going off of memory is foggy) so it doesn't return the device to stock...
niftyXD said:
I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?
Click to expand...
Click to collapse
did you disable Verity and verification before flashing the kernel?
It's frustrating when someone posts a problem then never follows up
HipKat said:
It's frustrating when someone posts a problem then never follows up
Click to expand...
Click to collapse
It's why I've relegated myself to editing the title "SOLVED" for members on their threads, as a service for those of us who roam around here assisting and helping...
it's not much, but it's sometimes helpful to be able to see in the title and/or be able to tell from a glance if/when someone followed up...
simplepinoi177 said:
It's why I've relegated myself to editing the title "SOLVED" for members, as a service for those of us who roam around here assisting and helping...
it's not much, but it's sometimes helpful to be able to see in the title and/or be able to tell from a glance if/when someone followed up...
Click to expand...
Click to collapse
Hey,
Most likely solved it by himself, since he didn't show up since 5 minutes after his post
Anyways, hopefully, people's experiencing the same issue will find this thread with possible solutions (before opening a new thread).
Cheers,
Sébastien.