Related
Thanks koush!
He told me what to do and I did it then the recovery works.
thanks everybody!
uploaded the kernel and its initramfs.
just remove ".zip" then the one is a tarball and the other one is cpio.
thanks
this does boot into recovery, however it's not useable because the select button (HOME) doesn't work
how exactly did you go about repacking the ramdisk and such?
also, I had to unpack the tarball and rename zImage to recovery.bin
It's alive!
Great work dkcldark. Can we try with the vibrant/captivate recovery binary in order to get the home key mapped? Also, adb doesn't seem to work..
Maybe you could let us in on your process for doing this, so we can look at the ramdisk that you used?
dkcldark, can you join #samsung-fascinate on freenode? got a bunch of folks trying to figure this out too!
Awesome guys, i see alot of fun on the horizon now
Why the hell can nobody else get on the irc channel samsung-fascinate? It says u need to be identified with services. ? Been trying for three days and starting to get pissed the Fu*k off.
they call me...kick ass
lmao.. you need to register man.. It's not like EFNET or wherever, you need to own your nick before it will let you join most channels.
google 'freenode' and nickserv
Oh.LOL I was like"these ****ers blocked me out and I've never even made a comment" I usually just sit in there and read. Thanks brandon. Or I'm assuming Brandon. Hence. Namebrandon lol
they call me...kick ass
ksizzle9 said:
Oh.LOL I was like"these ****ers blocked me out and I've never even made a comment" I usually just sit in there and read. Thanks brandon. Or I'm assuming Brandon. Hence. Namebrandon lol
they call me...kick ass
Click to expand...
Click to collapse
her name is vicky. her husbands name is brandon.
Ok guys i will upload a new kernel a few hours later see you soon
Sent from my GT-I9000 using Tapatalk
Will this work for the fascinate?
i gave dkcldark the clockworkmod initramfs for the fascinate
maybe recovery by morning or so?
fallingup said:
her name is vicky. her husbands name is brandon.
Click to expand...
Click to collapse
Oh, funny guy.. Keep it up!
so koush tweeted that you could get clockworkmod recovery going by flashing this. i'm not a noob (had a droid since launch date) but i just want to make sure before i do something stupid. by "flashing" the zimage_cwm_recovery", are you using Flash_Image or Odin? or something else. Please help. i'm eager to get a nandroid backup so I can start removing bloatware without worrying.
Lol. Okay, I have played with this enough, and no dice. Anyone who would be so kind as to post a step by step would have my gratitude.
sonofskywalker3 said:
so koush tweeted that you could get clockworkmod recovery going by flashing this. i'm not a noob (had a droid since launch date) but i just want to make sure before i do something stupid. by "flashing" the zimage_cwm_recovery", are you using Flash_Image or Odin? or something else. Please help. i'm eager to get a nandroid backup so I can start removing bloatware without worrying.
Click to expand...
Click to collapse
>>> As far as I know, you can flash a kernel with Odin. Then, this kernel should be tar'ed like I500_kernel.tar. but the first reply says that
jt1134 said:
thanks
also, I had to unpack the tarball and rename zImage to recovery.bin
Click to expand...
Click to collapse
I have no idea about the recovery.bin so I decided just to zip the zImage files.
Well odin is new to me, so I apologize for my ignorance. I installed it, then downloaded and extracted the captivate file, added .tar, and flashed it with odin. No recovery. Pulled down rom manager and tried to reboot into recovery, no dice. Rebooted and told rom manager to flash the recovery for fascinate, no dice. Told rom manager to flash recovery for captivate, no dice. Repeated the process with the cwm download file, no dice. What am I missing here?
Sent from my SCH-I500 using XDA App
Daswolven said:
Well odin is new to me, so I apologize for my ignorance. I installed it, then downloaded and extracted the captivate file, added .tar, and flashed it with odin. No recovery. Pulled down rom manager and tried to reboot into recovery, no dice. Rebooted and told rom manager to flash the recovery for fascinate, no dice. Told rom manager to flash recovery for captivate, no dice. Repeated the process with the cwm download file, no dice. What am I missing here?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Im currently testing this / creating packages for what works and what doesnt for Odin install. If you dont know how to repackage this and flash it, please hold off as this can / will brick your phone if you dont know what you are doing.
How can I turn this off so I don't get aborted installations in recovery when flashing a zip
Sent from my Eris using XDA App
iloveandroid said:
How can I turn this off so I don't get aborted installations in recovery when flashing a zip
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Are you trying to flash garbage to your phone?
OK, that was harsh; let me put that a different way.
If you get a verification error, there are only two possibilities:
1) The downloaded file was signed with the test-key and is corrupted (or truncated short)
2) The downloaded .zip file was never signed, or signed with some other key other than the "test-key" (and might, or might not also be corrupted)
ClockworkMod will allow you to turn off signature verification; that probably explains why folks end up with bricks from time to time when using Clockwork.
I don't think there are any devs in the XDA Eris forums that produce anything that is not signed (with test-key); so in that case, it is hard to imagine that signature verification is causing you any harm - if you get a verification error, it would be because your .zip file was corrupted somehow.
But - it's your phone to take risks as you see fit. If you want to flash without protection, use ClockworkMod. I would be very diligent about checking MD5 signatures, or running "jarsigner -verify" over the zips you intend to flash
bftb0
bftb0 said:
Are you trying to flash garbage to your phone?
OK, that was harsh; let me put that a different way.
If you get a verification error, there are only two possibilities:
1) The downloaded file was signed with the test-key and is corrupted (or truncated short)
2) The downloaded .zip file was never signed, or signed with some other key other than the "test-key" (and might, or might not also be corrupted)
ClockworkMod will allow you to turn off signature verification; that probably explains why folks end up with bricks from time to time when using Clockwork.
I don't think there are any devs in the XDA Eris forums that produce anything that is not signed (with test-key); so in that case, it is hard to imagine that signature verification is causing you any harm - if you get a verification error, it would be because your .zip file was corrupted somehow.
But - it's your phone to take risks as you see fit. If you want to flash without protection, use ClockworkMod. I would be very diligent about checking MD5 signatures, or running "jarsigner -verify" over the zips you intend to flash
bftb0
Click to expand...
Click to collapse
I wouldn't use Clockwork at all. Just try downloading the file directly on your phone and move it to the root after unzipping and do a md5 to make sure it's right first. It sounds like a corrupted download.
Please ignore all I love android posts.
Hungry Man said:
Please ignore all I love android posts.
Click to expand...
Click to collapse
It took me several tries but I finally parsed your post. I guess it is late. Then I poked around, and I suppose I see what you mean.
We need a special Eris sub-forum with the title "Put Your Posts in Here and They Will be Ignored".
Hang on, wait a minute... that's this forum! lolz
Or, how about a sub-forum entitled "Can I Try This?". The only rule in that forum will be that the correct, and only answer to every question posed will be the single word "Hellyagoforit!"
bftb0
I am trying to change my wifes rom on her phone and her trackball is broke. So I installed the latest version of CWM to see if it would enable and need features so I could navigate in recovery. No luck and now I can't back up her via rom manager either I just get an error. So what I am wondering is the an alternate way to work through cwm without the trackball and whats up with this error after I updated it. Thanks in advance for your help
The error is e: can't open /cache/update.zip
(Bad)
Installation aborted
Sent from my thunderbolt using XDA Premium App
superdusto said:
The error is e: can't open /cache/update.zip
(Bad)
Installation aborted
Sent from my thunderbolt using XDA Premium App
Click to expand...
Click to collapse
Make sure the backup file has no spaces between anything like backup-4627 not backup 4627 no spaces you'll get an error
Sent from my ERIS using Tapatalk
TheGratefulDead said:
Make sure the backup file has no spaces between anything like backup-4627 not backup 4627 no spaces you'll get an error
Sent from my ERIS using Tapatalk
Click to expand...
Click to collapse
That wasn't the problem just tried and am still getting the same error
Sent from my Thunderbolt using XDA Premium App
superdusto said:
The error is e: can't open /cache/update.zip
(Bad)
Installation aborted
Sent from my thunderbolt using XDA Premium App
Click to expand...
Click to collapse
I believe that this message implies that the download was bad (i.e., and incomplete file or a mis-matched MD5 signature).
I'm not that familiar with ClockworkMod or ROM manager, but have a peek at this thread: http://www.droidforums.net/forum/koush/47399-upgrade-rom-rom-manager-problem.html since it seems to describe what you are seeing.
If you are downloading your first directly to your phone, you can check your MD5 with Astro File Manager (long-press file name, select details, and wait a little bit for the MD5 checksum to appear).
You could also try my app, AFV (Android File Verifier). It has several checksum options, including MD5 and SHA1. You can use its "Verify Jar-type File" to verify the integrity of a signed file even if you don't know the MD5 checksum.
Cheers!
scary alien said:
I believe that this message implies that the download was bad (i.e., and incomplete file or a mis-matched MD5 signature).
I'm not that familiar with ClockworkMod or ROM manager, but have a peek at this thread: http://www.droidforums.net/forum/koush/47399-upgrade-rom-rom-manager-problem.html since it seems to describe what you are seeing.
If you are downloading your first directly to your phone, you can check your MD5 with Astro File Manager (long-press file name, select details, and wait a little bit for the MD5 checksum to appear).
You could also try my app, AFV (Android File Verifier). It has several checksum options, including MD5 and SHA1. You can use its "Verify Jar-type File" to verify the integrity of a signed file even if you don't know the MD5 checksum.
Cheers!
Click to expand...
Click to collapse
I am not downloading a rom I have the rom. So that doesn't help much. Any other ideas? no recovery options that doesn't use track ball?
superdusto said:
I am not downloading a rom I have the rom. So that doesn't help much. Any other ideas? no recovery options that doesn't use track ball?
Click to expand...
Click to collapse
Yeah, sorry...I wasn't exactly sure...
I know that ClockworkMod lets you navigate its menus without using the trackball, but most rooted folks use Amon_RA's custom recovery.
A while back, I created a trackball-optional version of Amon_RA's recovery for the Eris. Here's the thread I created over on AF re. this:
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
Here's the post in RA's thread over here on XDA: http://forum.xda-developers.com/showpost.php?p=9124095&postcount=83
Hope this helps!
Cheers!
Not sure if this helps but I had the same problem when I flashed my friend fascinate. But they use odin to flash their clockwork (voodoo) I had to run the root script then install the rom to fix the update.zip. Any ideas?
superdusto said:
Not sure if this helps but I had the same problem when I flashed my friend fascinate. But they use odin to flash their clockwork (voodoo) I had to run the root script then install the rom to fix the update.zip. Any ideas?
Click to expand...
Click to collapse
lol...sorry, no. I've only heard that Odin (timely Thor-related reference, eh? ) is used for the Samsung phones.
There are others around that know and have used ClockworkMod on the Eris, but they are relatively few and far between (plus, things certainly seem to be slowing down in the various Eris forums recently). There have also been some unexplained brickings of phones using CWM that have scared off potential users of that custom recovery, so most have stayed with and use Amon_RA's.
scary alien said:
lol...sorry, no. I've only heard that Odin (timely Thor-related reference, eh? ) is used for the Samsung phones.
There are others around that know and have used ClockworkMod on the Eris, but they are relatively few and far between (plus, things certainly seem to be slowing down in the various Eris forums recently). There have also been some unexplained brickings of phones using CWM that have scared off potential users of that custom recovery, so most have stayed with and use Amon_RA's.
Click to expand...
Click to collapse
Well thanks for your help so far is their a post on how to set up adb so I can flash Amon_RA. I think my problem is that I rooted with amon and just downloaded rom manager so I put CWM on it.. Must be affecting my update.zip
superdusto said:
Well thanks for your help so far is their a post on how to set up adb so I can flash Amon_RA. I think my problem is that I rooted with amon and just downloaded rom manager so I put CWM on it.. Must be affecting my update.zip
Click to expand...
Click to collapse
Yes, at the bottom of the first post in the AF forum thread are the installation instructions and one of them is how to do it with adb ("Scenario 4").
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
Sounds like you are already familiar with adb, so you should be very close .
Let me know if you need anything else.
Cheers!
You saved me Thank you so much for your time here have some thanks!!!
superdusto said:
You saved me Thank you so much for your time here have some thanks!!!
Click to expand...
Click to collapse
You are most welcome! Glad you got things going .
I keep getting these warm-and-fuzzies from folks that my efforts for building the trackball-optional recovery was well worth it (with kudos and thanks again to RA for his help in filling-in the key gaps in how to build it).
Cheers!
My trackball has not worked pretty much since I bought the phone. I have found is you plug in your usb charger and lift up firmly the trackball works with no issues at all. Just FYI. And here's to the dev's that keep our end of life eris fast and up to date. And no sense thank GOD. lol
Yep, that is a definite way to work it ... I was unable to ROOT for over 2 months after getting my Eris b/c my trackball didn't work. It wasn't until I found this advice over in DF that I was finally able to negotiate the recovery menu.
HOWEVER (!!!) After almost a year of moderate flashing/recovery use, my USB/AC charger barely works anymore. I have to put weight on the USB near the connec w/ the phone to get it to recognize & charge.
I have tried to install the Amon_ra trkball not req script but couldn't get it to work ... I just use CWM these days b/c I don't need to use the damn thing !
Good thing I am coming up for an UPGRADE
Sparticusx said:
My trackball has not worked pretty much since I bought the phone. I have found is you plug in your usb charger and lift up firmly the trackball works with no issues at all. Just FYI. And here's to the dev's that keep our end of life eris fast and up to date. And no sense thank GOD. lol
Click to expand...
Click to collapse
Earlier this week I bought a Samsung Galaxy S III for ATT. It already had Ice Cream Sandwich 4.0.4 on it and so I rooted it. Well the day after rooting it I get a message in my notification bar that there's a new software update available from ATT. Am I safe to do this update since my phone is rooted? I doubt the update is anything major, but does that make a difference?
fa7592 said:
Earlier this week I bought a Samsung Galaxy S III for ATT. It already had Ice Cream Sandwich 4.0.4 on it and so I rooted it. Well the day after rooting it I get a message in my notification bar that there's a new software update available from ATT. Am I safe to do this update since my phone is rooted? I doubt the update is anything major, but does that make a difference?
Click to expand...
Click to collapse
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
Thank you very much. I appreciate the quick response and the help.
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
would I just have to reflash the kernel I'm on now if I were to update that way?
Sent from my SAMSUNG-SGH-I747 using xda premium
jrbaker624 said:
would I just have to reflash the kernel I'm on now if I were to update that way?
Click to expand...
Click to collapse
No. There's a zip file there with the OTA but with the bootloader and kernel updates removed. You can flash that to keep your kernel. There's another zip file there with just the bootloader if you want to update that, too. Just flash both (No Bootloader No Kernel, the Bootloader).
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
UPDATE:
okay so I followed the steps in the thread you provided, and when I go to flash the update zip in recovery mode, i get an error and it aborts the installation. Heres the error:
assert failed: getprop("ro.product.device") =="
d2att" | | getprop("ro.build.product") =="
d2att"
E:Error in /emmc/I747UCALG1_OTA.zip
(status 0)
Installation aborted.
Any idea as to what this may mean?
I am also getting same error I was on team epics recovery then saw it wouldn't work for that recovery so I flashed a new recovery and still get the same error.
Tried flashing the no boot loader zip. And the no boot loader and no kernel zip
Sent from my SAMSUNG-SGH-I747 using xda premium
fa7592 said:
assert failed: getprop("ro.product.device") =="
d2att" | | getprop("ro.build.product") =="
d2att"
E:Error in /emmc/I747UCALG1_OTA.zip
(status 0)
Installation aborted.
Any idea as to what this may mean?
Click to expand...
Click to collapse
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
drothenberger said:
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Oh I see. So should I just download that file and replace the CWM zip file thats already on my phone. Or do I have to do something in Odin again?
fa7592 said:
Oh I see. So should I just download that file and replace the CWM zip file thats already on my phone. Or do I have to do something in Odin again?
Click to expand...
Click to collapse
Download OTA Rootkeeper from the play store, save root, then install the OTA. Reboot and OTA rootkeeper restore root.
drothenberger said:
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Downloaded that one instead of the third one you had linked all together and it worked. Thank you
Sent from my SAMSUNG-SGH-I747 using xda premium
Download the zip file for recovery, apply it using your current recovery, reboot recovery from the advanced menu, then apply the OTA zip.
Or use OTA Rootkeeper as also suggested. I prefer my OTA zip personally, but either way will work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
drothenberger said:
Download the zip file for recovery, apply it using your current recovery, reboot recovery from the advanced menu, then apply the OTA zip.
Or use OTA Rootkeeper as also suggested. I prefer my OTA zip personally, but either way will work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Okay. Wow. So after a lot of trial and error (i think i bricked my phone somehow in the middle of everything, but its okay I found out how to fix it) I have managed to get that update applied. Theres one last problem though. I applied the update by flashing it in CWM recovery. I know I have the update installed because now under baseband version instead of saying I747UCLEM it says I747UCLG1. And Ive tested the google search widget and it's still giving me local search results so that's all good. The problem is that in my notification bar the ATT software update notification is still there. I have currently postponed it for 8 hours, but its still there and the only button I'm able to press is the continue button. I dont want to press this because im afraid the normal ATT update will install over the modded one and the google search widget will mess up and stop displaying the local search results. Also under about device, when I click software update the option for "check for update" is grayed out. Any thoughts on this?
fa7592 said:
Okay. Wow. So after a lot of trial and error (i think i bricked my phone somehow in the middle of everything, but its okay I found out how to fix it) I have managed to get that update applied. Theres one last problem though. I applied the update by flashing it in CWM recovery. I know I have the update installed because now under baseband version instead of saying I747UCLEM it says I747UCLG1. And Ive tested the google search widget and it's still giving me local search results so that's all good. The problem is that in my notification bar the ATT software update notification is still there. I have currently postponed it for 8 hours, but its still there and the only button I'm able to press is the continue button. I dont want to press this because im afraid the normal ATT update will install over the modded one and the google search widget will mess up and stop displaying the local search results. Also under about device, when I click software update the option for "check for update" is grayed out. Any thoughts on this?
Click to expand...
Click to collapse
What does it say under build number? IMM76D.I747UCALG1? If not, then somehow you only got the modem installed.
I have the update applied, but I had frozen AT&T Software Update in Titanium Backup, so I wasn't getting the notification. I just tried unfreezing it and checking for an update and was surprised when it said there was one! I postponed it, did a Wipe Data for AT&T Software Update in TiBu, then rebooted and now all is well. When I check for an update now it says I'm up-to-date. So try that.
drothenberger said:
What does it say under build number? IMM76D.I747UCALG1? If not, then somehow you only got the modem installed.
I have the update applied, but I had frozen AT&T Software Update in Titanium Backup, so I wasn't getting the notification. I just tried unfreezing it and checking for an update and was surprised when it said there was one! I postponed it, did a Wipe Data for AT&T Software Update in TiBu, then rebooted and now all is well. When I check for an update now it says I'm up-to-date. So try that.
Click to expand...
Click to collapse
Yeah, under build number it says IMM76D.I747UCALG1.
I'll give what you said a shot and see what happens. But one thing first, what's TiBu? And also, I'm about to flash a custom ROM on my phone, so is the update issue something that can wait, or should I take care of that before I put on a custom ROM?
fa7592 said:
Yeah, under build number it says IMM76D.I747UCALG1.
I'll give what you said a shot and see what happens. But one thing first, what's TiBu? And also, I'm about to flash a custom ROM on my phone, so is the update issue something that can wait, or should I take care of that before I put on a custom ROM?
Click to expand...
Click to collapse
Sorry, "TiBu" is my shorthand for Titanium Backup. Chances are any custom ROM you install will remove the AT&T Software Update application, so you won't need to worry about this anymore.
drothenberger said:
Sorry, "TiBu" is my shorthand for Titanium Backup. Chances are any custom ROM you install will remove the AT&T Software Update application, so you won't need to worry about this anymore.
Click to expand...
Click to collapse
Oh okay. In that case I'll go ahead and put in that custom ROM and report back when everything is done. Again, thanks for the help and patience.
Okay, so I have applied the ROM and everything is good! Well for the most part. At times when there isn't a WiFi signal available and it has to use mobile data, the 4G LTE doesn't work. It will connect to HSPA or 3G. And it happens in areas I know has 4G LTE available. But other than that everything seems to be working good. Just thought I'd share in case anyone was thinking of using the AOKP ROM.
Here is the factory update zip. One may be able to flash it from stock recovery (will need to be renamed to "update.zip"), but no promises. I'm hoping a dev can take advantage of it.
update note 3 lollipop.zip
https://docs.google.com/file/d/0B2iEgzRTFjrQN2g4OTlpM19IUDQ/edit?usp=docslist_api
wow!
Awesome! Downloading now
Fantastic... I'm getting a footer is wrong - signature verification failed error, since I am rooted and probably tripped knox (had TWRP, now on stock recovery) device status custom. Any ways I can get this to work without having to odin back to stock? Just so much of a hassle I'd like to avoid if at all possible.
Delirious17 said:
Fantastic... I'm getting a footer is wrong - signature verification failed error, since I am rooted and probably tripped knox (had TWRP, now on stock recovery) device status custom. Any ways I can get this to work without having to odin back to stock? Just so much of a hassle I'd like to avoid if at all possible.
Click to expand...
Click to collapse
This might be your ticket:
http://forum.xda-developers.com/note-3-sprint/general/loolipop-pre-rooted-twrp-flash-t3088490
Is this one corrupt like the others or is it good?
Sent from my SM-N900P using XDA Free mobile app
Greaper88 said:
This might be your ticket:
http://forum.xda-developers.com/note-3-sprint/general/loolipop-pre-rooted-twrp-flash-t3088490
Click to expand...
Click to collapse
I know how to pull the update.zip. I did it for the previous update. Samsung has it encrypted. You have to act like you are gonna install the update and soon as it is done preparing to install it wants to reboot in to stock recovery to install. That's when you have to do a battery pull and use your pc to pull the unencrypted zip. Going of of bad memory but it's something like that. I know the reason everyone get a corrupt update.zip is its encrypted and the install will unencrypt just before install. Once install is aborted the proces will delete the files making you re download the update.
Sent from my SM-G900P using Tapatalk
Delirious17 said:
Fantastic... I'm getting a footer is wrong - signature verification failed error, since I am rooted and probably tripped knox (had TWRP, now on stock recovery) device status custom. Any ways I can get this to work without having to odin back to stock? Just so much of a hassle I'd like to avoid if at all possible.
Click to expand...
Click to collapse
JonSCSL said:
I know how to pull the update.zip. I did it for the previous update. Samsung has it encrypted. You have to act like you are gonna install the update and soon as it is done preparing to install it wants to reboot in to stock recovery to install. That's when you have to do a battery pull and use your pc to pull the unencrypted zip. Going of of bad memory but it's something like that. I know the reason everyone get a corrupt update.zip is its encrypted and the install will unencrypt just before install. Once install is aborted the proces will delete the files making you re download the update.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
OK. Good to know.
UPDATE!
DId the odin MK4 but everything was kept, no resetting/reinstalls required!
Then was able to download the update and all is well.
Does anybody know how to trigger the ota process if you have an update.zip on the device?
My device has modified bootloader, so I'm not eligible for OTA... but with Wanam Exposed you can fake Offical status, and it'll download the OTA, but fail to install.
If before it fails, you copy the update.zip from /data/fota/update.zip .. then you have a copy.
My issue now though is that the normal OTA process won't let me continue with the OTA dialogs... and if I try to flash the zip in stock recovery, it can't seem to open it.
Is there a way to trigger the Samsung OTA process, with root, and have it properly process and unencrypt the update.zip upon flashing?
Cheers!
Levistras said:
Does anybody know how to trigger the ota process if you have an update.zip on the device?
My device has modified bootloader, so I'm not eligible for OTA... but with Wanam Exposed you can fake Offical status, and it'll download the OTA, but fail to install.
If before it fails, you copy the update.zip from /data/fota/update.zip .. then you have a copy.
My issue now though is that the normal OTA process won't let me continue with the OTA dialogs... and if I try to flash the zip in stock recovery, it can't seem to open it.
Is there a way to trigger the Samsung OTA process, with root, and have it properly process and unencrypt the update.zip upon flashing?
Cheers!
Click to expand...
Click to collapse
Pulling the copy corrupts it.
To get to lollipop you have to factory reset, odin to nk4 then accept ota.
Sent from my SM-N900P using XDA Free mobile app