Related
i have an infuse 4g that is rooted
downloaded modded e3 and installed but when i go through and change the old recovery and paste the new it dont show the old and the new files
then when i run cwm it down loads i go into reboot into recovery
it says failed to verify whole-file signature
signature verification failed
installation aborted
is this due to the two files not being there
or am i doing somthing wrong
http://www.youtube.com/watch?v=PkMo8rBehHg
follow those instructions exactly, making sure to adjust the permissions of the recovery file at the end.
download ROM manager, go to "flash clockworkmod recovery" and choose plain galaxys i9000.
then boot into recovery (probably blue), select reinstall packages 2 times, and you should be in green cwm recovery (if you boot into green the first time, ignore the reinstall packages step).
i did all that about 10 times still dont work i think i am missing somthing
---------- Post added at 10:23 PM ---------- Previous post was at 10:10 PM ----------
tryed all that to the letter still dont show the to recovery files and still gets the failure to install i dont know what to do now
ive tryed every thing i could find and none of it dont work
---------- Post added at 10:33 PM ---------- Previous post was at 10:23 PM ----------
i gave a thanks anyway but i still cant get it to work
that is just the luck i have i prob got the only phone in the world that cant get a new rom on it
I GIVE UP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Are you remembering to switch to R/W mode before tring to write the 3e recovery?
Try updating busybox.... Confirm you have system as r/w when replacing recovery....
Sent from my Samsung Infuse 4G - 1.6ghz
tryed that
i tryed everthing you guys said but still will not load packages and fails
could it be my phone that is causing this
Go here and download the "3e Recovery w/o signature verification"
http://forum.xda-developers.com/showthread.php?t=1091465
Replace your recovery with this one. Reboot into recovery. You'll still need to reinstall packages once or twice., but only only the first boot into recovery.
Did you extract the new recovery before pasting? I'm sure you did but figured id ask.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
I realize this may be a little late, but make sure you have the newest version of root explorer installed if that's what you're using. I downloaded an old version for free from a friend of mine, and it wouldn't work correctly when it came to the copy/pasting of the recovery file part of the instructions. Downloaded the newest one from market and it all worked perfectly.
Hi guys, I just received the OTA update's notification, tried to install but "/system/framework/core.odex has unexpected contents" error appeared. I tried to wipe cache but it still appear.. what can I do?
I have uninstalled xposed and modules, and other apps that modifies system's files
Same here, I get the 4.4 upgrade uk version, reboots and goes in bootloop so I had to delete the zip file. I have uninstalled exposed all modules too and turned off root no joy
Also guys Will this update fix the famous "touch to retry error"? I heard in this upgrade there is a new radio?
thanks for all your help i know your busy
---------- Post added at 08:29 PM ---------- Previous post was at 08:26 PM ----------
forgot to mention im on CWM recovery not stock and on 4.4.2 with modifications from exposed modules.
AndroidHtc101 said:
Same here, I get the 4.4 upgrade uk version, reboots and goes in bootloop so I had to delete the zip file. I have uninstalled exposed all modules too and turned off root no joy
Also guys Will this update fix the famous "touch to retry error"? I heard in this upgrade there is a new radio?
thanks for all your help i know your busy
---------- Post added at 08:29 PM ---------- Previous post was at 08:26 PM ----------
forgot to mention im on CWM recovery not stock and on 4.4.2 with modifications from exposed modules.
Click to expand...
Click to collapse
here is the zip file? if i delete the zip file, the bootloop disappear?
AndroidHtc101 said:
Same here, I get the 4.4 upgrade uk version, reboots and goes in bootloop so I had to delete the zip file. I have uninstalled exposed all modules too and turned off root no joy
Also guys Will this update fix the famous "touch to retry error"? I heard in this upgrade there is a new radio?
thanks for all your help i know your busy
---------- Post added at 08:29 PM ---------- Previous post was at 08:26 PM ----------
forgot to mention im on CWM recovery not stock and on 4.4.2 with modifications from exposed modules.
Click to expand...
Click to collapse
It has been said already countless times now.
You need to be completely stock to be able to update via the official OTA.
Flash stock recovery, stock /system and then you'll be able to update.
I get an error while updating, it just says ''error''. I have stock kernel, stock recovery, unrooted... Nothing seems to work. I think the problem might be that I have a custom boot animation. Is there any way to flash the 4.4.2 stock UK rom?
Is it possible to take a stock rom and unzip and take the recovery image and just zip it and flash it in TWRP to get stock recovery back?
Look in the development thread, I believe tdunham has a Odin flashable stock recovery. I'm not sure if anyone has made a flashable zip. I think it's possible.
---------- Post added at 06:38 AM ---------- Previous post was at 06:17 AM ----------
I have looked and can't find it. I was wondering why you want it though. Just curious.
metalfan78 said:
Look in the development thread, I believe tdunham has a Odin flashable stock recovery. I'm not sure if anyone has made a flashable zip. I think it's possible.
---------- Post added at 06:38 AM ---------- Previous post was at 06:17 AM ----------
I have looked and can't find it. I was wondering why you want it though. Just curious.
Click to expand...
Click to collapse
Because I have a client that I rooted their phone and they don't want to have customer recovery. They want the phone as stock as possible so this way if they have to take it back to sprint they can just have SuperSU uninstall itself and not worry about Sprint. I'm hoping that I can just zip with the recovery image and just flash it in TWRP.
I'm pretty sure there is a stock recovery img file floating around that you can use an app called flashify to flash it with.
SU4TL-44 Stock Image for XT1254: https://mega.nz/#!v4QWiITb!_0jWWzE4KWCEgT__C36rYe0vaTzGKcEFsZm0vvBtLBg
Flash with TWRP.
This package will flash every image in the SU4TL-44 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, revert to stock by following section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Thanks to @firstEncounter for letting me incorporate his flashable zip into this package.
Will have to download this later. Looked to go back to stock and wait for mm to come out.
Sent from my XT1254 using Tapatalk
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
No it won't relock boot loader just installed it you will not be rooted and twrp will ask you if you want to root before reboot if you click no and want to at a later point just go back into boot loader by doing vol down power combo from power off and select open boot loader and when you click to reboot it will ask you again if you want to root then you can just slide to install
schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
Correct
Can I install viper and su along with this?
MazinDLX said:
Can I install viper and su along with this?
Click to expand...
Click to collapse
Sure. Just flash the rom first and the mods second.
TheSt33v said:
Sure. Just flash the rom first and the mods second.
Click to expand...
Click to collapse
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol
MazinDLX said:
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol
Click to expand...
Click to collapse
I've never tried to install an image via ADB before. Did you mount the image elsewhere and extract the system folder, and then ADB-pushed that? If not, your bootloop is probably because there's just a big, unextracted system.img on your system partition, and not the actual files within it. Why not just flash it with TWRP? When I tested it, I flashed it via TWRP and it worked.
If you really don't want to flash it via TWRP for some reason, you can extract the system.img from the zip and flash it using fastboot (fastboot flash system system.img).
EDIT: Oh wait, I think I understand now. You just used ADB to put the zip on your phone, and then you installed it with TWRP. Got it. Well my next question is why use ADB at all? Why not just plug in your phone while it's booted into TWRP and use the native MTP to transfer files?
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.
MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
This package only flashes /system. CM flashes its own boot.img, which is why this isn't working for you. I'll try to find some time tonight to add in the other images in the stock firmware to this package. Sorry about that.
firstEncounter said:
The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.
Click to expand...
Click to collapse
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?
TheSt33v said:
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?
Click to expand...
Click to collapse
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.
MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.
firstEncounter said:
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.
Click to expand...
Click to collapse
I'm not entirely sure how to write a script to flash those in TWRP. For boot and system, it's easy because the devices that they are flashed to match the names used by fastboot. Bootloader and radio seem to be a little different though. When I list the contents of /dev/block/bootdevice/by-name, there is no "motoboot" or "radio," which is what fastboot uses when you flash these. I do see "aboot" and "modem," and I'm pretty sure those are the targets I'm looking for, but I don't want to go flashing things unless I'm 100% sure. Since there's not a huge demand for figuring that out, and boot + system is all people will need in 99% of cases, I'll leave them out. Thanks though!
Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?
MazinDLX said:
Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?
Click to expand...
Click to collapse
No, but I appreciate the thought. Donate to this guy instead. He does way more than me and also needs it way more than me: http://forum.xda-developers.com/droid-turbo/development/computerfreekunlocked1-0-t3255945
TheSt33v said:
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.
Click to expand...
Click to collapse
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.
bigv5150 said:
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.
Click to expand...
Click to collapse
Awesome! That's why we do this
So the phone failed to boot up out of no where, I could boot into download mode fine but recovery would just show blue letters and reboot without giving me the recovery menu. So from the download mode I used Odin to upload the latest bootloader downloaded from sammobile. It was a green light but now the phone won't boot up and won't even get to download mode and I still get the same recovery mode behavior. Help? What did I do and how can I fix it ? I don't know what firmware or bootloader were installed before but I assume the latest because by mistake I tried the third latest one and it would fail to upload via Odin.
cubajean10 said:
So the phone failed to boot up out of no where, I could boot into download mode fine but recovery would just show blue letters and reboot without giving me the recovery menu. So from the download mode I used Odin to upload the latest bootloader downloaded from sammobile. It was a green light but now the phone won't boot up and won't even get to download mode and I still get the same recovery mode behavior. Help? What did I do and how can I fix it ? I don't know what firmware or bootloader were installed before but I assume the latest because by mistake I tried the third latest one and it would fail to upload via Odin.
Click to expand...
Click to collapse
Give some background info on how the phone failed to boot up in the first place... And why do you not know what firmware it had previously?
thanks for the reply but i already gave up, i got lucky enough that it got in download mode and i odin back everything bl ad etc and still nothing . for info: the phone froze while in use candy crush i think and then failed to reboot, and I don't know the original firmware because I never checked
cubajean10 said:
thanks for the reply but i already gave up, i got lucky enough that it got in download mode and i odin back everything bl ad etc and still nothing . for info: the phone froze while in use candy crush i think and then failed to reboot, and I don't know the original firmware because I never checked
Click to expand...
Click to collapse
There's your issue, if you had a different firmware running on it the bootloader was probably a different version. I'd say your best bet would be to flash the latest firmware(not nougat) of all S7 variants(ex: At&t,Verizon,Sprint, Metro PCS...)
on the phone with odin and you'd know which firmware it was originally running if it boots without an issue.
---------- Post added at 07:20 PM ---------- Previous post was at 07:20 PM ----------
KillerClaw321 said:
There's your issue, if you had a different firmware running on it the bootloader was probably a different version. I'd say your best bet would be to flash the latest firmware(not nougat) of all S7 variants(ex: At&t,Verizon,Sprint, Metro PCS...)
on the phone with odin and you'd know which firmware it was originally running if it boots without an issue.
Click to expand...
Click to collapse
I'm pretty sure instead of doing this trial and error if you boot into the recovery it should show you the specific firmware version with the device model #
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
KillerClaw321 said:
There's your issue, if you had a different firmware running on it the bootloader was probably a different version. I'd say your best bet would be to flash the latest firmware(not nougat) of all S7 variants(ex: At&t,Verizon,Sprint, Metro PCS...)
on the phone with odin and you'd know which firmware it was originally running if it boots without an issue.
---------- Post added at 07:20 PM ---------- Previous post was at 07:20 PM ----------
I'm pretty sure instead of doing this trial and error if you boot into the recovery it should show you the specific firmware version with the device model #
Click to expand...
Click to collapse
And then from the successful boot you should be able to flash the T-Mobile PK1 firmware (the latest firmware at this time).
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
KillerClaw321 said:
There's your issue, if you had a different firmware running on it the bootloader was probably a different version. I'd say your best bet would be to flash the latest firmware(not nougat) of all S7 variants(ex: At&t,Verizon,Sprint, Metro PCS...)
on the phone with odin and you'd know which firmware it was originally running if it boots without an issue.
---------- Post added at 07:20 PM ---------- Previous post was at 07:20 PM ----------
I'm pretty sure instead of doing this trial and error if you boot into the recovery it should show you the specific firmware version with the device model #
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
And then from the successful boot you should be able to flash the T-Mobile PK1 firmware (the latest firmware at this time).
Click to expand...
Click to collapse
And good luck! :good:
thanks, the phone was a tmobile variant and i flashed pk1 but still got the same issue. i was never able to get into recovery because it would just say recovery booting and get stuck there or reboot to the same
cubajean10 said:
thanks, the phone was a tmobile variant and i flashed pk1 but still got the same issue. i was never able to get into recovery because it would just say recovery booting and get stuck there or reboot to the same
Click to expand...
Click to collapse
But try flashing the latest firmware from other variants... It could have been running at&t firmware or Sprint firmware... Which is why I'm suggesting you flash them regardless...