Hey!
So i've just received the update, and as per instructions i rebooted to install the update. But after rebooting, clockwork recovery appeared with the options of NO, NO, NO, etc, Yes install unknown ZIP, NO, etc. Because i was doing two other things at the moment (and i'm a moron) i've clicked Cancel and rebooted.
So now i'm still on 4.2.2 and when i click on "Check for system update" in setup it says "Up to date"
Am i totally screwed with the OTA update? I'll punch myself in the face if i have to do the update manually and resetup everything on my device <.<''
Thanks!
No, you're not boned. Try this.
http://www.droid-life.com/2013/07/25/android-4-3-update/
Rirere said:
No, you're not boned. Try this.
Click to expand...
Click to collapse
With the file from my /cache folder CWM gives Status 7 - Installation aborted. (i've moved the file to my "SD card")
As far as i saw, that might pop up if the ROM is not well done, but that is the file that i got from Google
So... any ideas how shall i proceed?
Sound Anarchist said:
Hey!
So i've just received the update, and as per instructions i rebooted to install the update. But after rebooting, clockwork recovery appeared with the options of NO, NO, NO, etc, Yes install unknown ZIP, NO, etc. Because i was doing two other things at the moment (and i'm a moron) i've clicked Cancel and rebooted.
So now i'm still on 4.2.2 and when i click on "Check for system update" in setup it says "Up to date"
Am i totally screwed with the OTA update? I'll punch myself in the face if i have to do the update manually and resetup everything on my device <.<''
Thanks!
Click to expand...
Click to collapse
If you don't want to do a manual update, you can either wait it out - the OTA will come back again eventually - or, you can take a look at system/cache and see the 4.3 update.zip, move it over to your root folder, then go into CWM recovery and install that.
mlj11 said:
If you don't want to do a manual update, you can either wait it out - the OTA will come back again eventually - or, you can take a look at system/cache and see the 4.3 update.zip, move it over to your root folder, then go into CWM recovery and install that.
Click to expand...
Click to collapse
Yep, did that Now i have another issue - see post above yours.
Hi, i'm having the same problem (kinda)
i am on stock rom, twrp recovery + multirom , timur's kernel.
i got the ota, said install, went to twrp, installed, but nothing happened. Now i am on 4.2.2, system says up to date.
i cant find update.zip anywhere.
can u help me?
Sent from my Nexus 7 using XDA Premium HD app
hamid_valad said:
Hi, i'm having the same problem (kinda)
i am on stock rom, twrp recovery + multirom , timur's kernel.
i got the ota, said install, went to twrp, installed, but nothing happened. Now i am on 4.2.2, system says up to date.
i cant find update.zip anywhere.
can u help me?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I think it's because you are not using stock kernel. As far as i've gathered from reading here, there is no trouble with custom recovery in general (it seems that sometimes there are issues - mine for example), but otherwise you should be stock: Google's ROM + kernel. If i was in your situation, i would flash the original kernel (you can extract it from the 4.2.2 release image). I'm not sure about multirom, you should research that.
As for my issue, after sleeping on it i think that i'll just wipe and flash the whole 4.3 image. After that i'll setup everything again.
Turns out, that the applications i need to backup data from are not so much, and i figured out where they keep the data i'm interested in. Also i want to see if wiping will help my memory issues (almost full device = slow as hell device).
hamid_valad said:
Hi, i'm having the same problem (kinda)
i am on stock rom, twrp recovery + multirom , timur's kernel.
i got the ota, said install, went to twrp, installed, but nothing happened. Now i am on 4.2.2, system says up to date.
i cant find update.zip anywhere.
can u help me?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Me too,but i'm using stock kernel...
Sent from my Sony Xperia™ sola using XDA Premium
I got error when flashing...
Anyone please help...
Sent from my Sony Xperia™ sola using XDA Premium
Ben Ling said:
I got error when flashing...
Anyone please help...
Sent from my Sony Xperia™ sola using XDA Premium
Click to expand...
Click to collapse
Yup, thats like mine.
mine says xt9ime.apk missing, and the numbers are different!
Sent from my Nexus 7 using XDA Premium HD app
Ben Ling said:
I got error when flashing...
Anyone please help...
Sent from my Sony Xperia™ sola using XDA Premium
Click to expand...
Click to collapse
i found a way, trying right now!!! if it works, i'll let u know!
Edit 1: Failed
Edit 2: Use it, maybe it helps u
BACK UP FIRST!!!!! I DO NOT TAKE ANY RESPONSIBILITY, my device got into X mark, nothing happened.
open the zip file, go to META-INF--> com --> google --> android, copy the updater-script to your desktop, then delete it from the zip archive
open the file on your desktop with notepad
search for "systemui" or what ever your problem is
delete the whole line. starting with "set_progress" ending with "));"
in my situation it was:
"set_progress(0.448070);
assert(apply_patch_check("/system/app/SystemUI.apk", "cca620c865fb91868a3afc70f005c93dc44beb60", "3c7b5c2e77cd9296276f9e7c372f298d1913644a"));"
then search again and you will find another like bellow:
"set_progress(0.451753);
assert(apply_patch_check("/system/app/SystemUI.odex", "7ad50dd5929e3d681f4d11199fe852c1ad620ad5", "1a424ccaa5cd08e82feec972649b42aec4b8a512"));"
then again:
"set_progress(0.481089);
apply_patch("/system/app/SystemUI.apk", "-",
cca620c865fb91868a3afc70f005c93dc44beb60, 1471663,
3c7b5c2e77cd9296276f9e7c372f298d1913644a, package_extract_file("patch/system/app/SystemUI.apk.p"));"
and the last one:
"set_progress(0.484752);
apply_patch("/system/app/SystemUI.odex", "-",
7ad50dd5929e3d681f4d11199fe852c1ad620ad5, 503088,
1a424ccaa5cd08e82feec972649b42aec4b8a512, package_extract_file("patch/system/app/SystemUI.odex.p"));"
save and copy the new file to the previous location.
then install the new file.
hope it helps.
let me know if it worked.
hamid_valad said:
i found a way, trying right now!!! if it works, i'll let u know!
Edit 1: Failed
Edit 2: Use it, maybe it helps u
BACK UP FIRST!!!!! I DO NOT TAKE ANY RESPONSIBILITY, my device got into X mark, nothing happened.
open the zip file, go to META-INF--> com --> google --> android, copy the updater-script to your desktop, then delete it from the zip archive
open the file on your desktop with notepad
search for "systemui" or what ever your problem is
delete the whole line. starting with "set_progress" ending with "));"
in my situation it was:
"set_progress(0.448070);
assert(apply_patch_check("/system/app/SystemUI.apk", "cca620c865fb91868a3afc70f005c93dc44beb60", "3c7b5c2e77cd9296276f9e7c372f298d1913644a"));"
then search again and you will find another like bellow:
"set_progress(0.451753);
assert(apply_patch_check("/system/app/SystemUI.odex", "7ad50dd5929e3d681f4d11199fe852c1ad620ad5", "1a424ccaa5cd08e82feec972649b42aec4b8a512"));"
then again:
"set_progress(0.481089);
apply_patch("/system/app/SystemUI.apk", "-",
cca620c865fb91868a3afc70f005c93dc44beb60, 1471663,
3c7b5c2e77cd9296276f9e7c372f298d1913644a, package_extract_file("patch/system/app/SystemUI.apk.p"));"
and the last one:
"set_progress(0.484752);
apply_patch("/system/app/SystemUI.odex", "-",
7ad50dd5929e3d681f4d11199fe852c1ad620ad5, 503088,
1a424ccaa5cd08e82feec972649b42aec4b8a512, package_extract_file("patch/system/app/SystemUI.odex.p"));"
save and copy the new file to the previous location.
then install the new file.
hope it helps.
let me know if it worked.
Click to expand...
Click to collapse
ok,i'll try...but why do i need to change to apk.p?
---------- Post added at 12:41 PM ---------- Previous post was at 12:10 PM ----------
Can anyone provide me system/bin/app_process from Nexus 7 3G?
Sound Anarchist said:
Yep, did that Now i have another issue - see post above yours.
Click to expand...
Click to collapse
Hey,
Sorry saw that you did a clean re-install already.
I had the same problem as you. What I did was to flash TWRP (unlike CWM it allows you to ignore the verification error) and tried to take the update again. That still failed however, because I apparently had an edited debuggerd file (happens if you use the Stickmount app). I downloaded a stock one from this thread, replaced it in system/bin, and re-flashed 4.3. Finally worked.
I then re-rooted by flashing the latest SuperSU in TWRP.
Are you replacing the 'debuggerd' file within the 4.3 zip update? Or the file on the Nexus 7 before the 4.3 is flashed?
I've tried updating 4.3 using the OTA 4.3 zip & TWRP & my nexus 7 is currenly stuck the the 'X' boot logo.
hamid_valad said:
i found a way, trying right now!!! if it works, i'll let u know!
Edit 1: Failed
Edit 2: Use it, maybe it helps u
BACK UP FIRST!!!!! I DO NOT TAKE ANY RESPONSIBILITY, my device got into X mark, nothing happened.
open the zip file, go to META-INF--> com --> google --> android, copy the updater-script to your desktop, then delete it from the zip archive
open the file on your desktop with notepad
search for "systemui" or what ever your problem is
delete the whole line. starting with "set_progress" ending with "));"
in my situation it was:
"set_progress(0.448070);
assert(apply_patch_check("/system/app/SystemUI.apk", "cca620c865fb91868a3afc70f005c93dc44beb60", "3c7b5c2e77cd9296276f9e7c372f298d1913644a"));"
then search again and you will find another like bellow:
"set_progress(0.451753);
assert(apply_patch_check("/system/app/SystemUI.odex", "7ad50dd5929e3d681f4d11199fe852c1ad620ad5", "1a424ccaa5cd08e82feec972649b42aec4b8a512"));"
then again:
"set_progress(0.481089);
apply_patch("/system/app/SystemUI.apk", "-",
cca620c865fb91868a3afc70f005c93dc44beb60, 1471663,
3c7b5c2e77cd9296276f9e7c372f298d1913644a, package_extract_file("patch/system/app/SystemUI.apk.p"));"
and the last one:
"set_progress(0.484752);
apply_patch("/system/app/SystemUI.odex", "-",
7ad50dd5929e3d681f4d11199fe852c1ad620ad5, 503088,
1a424ccaa5cd08e82feec972649b42aec4b8a512, package_extract_file("patch/system/app/SystemUI.odex.p"));"
save and copy the new file to the previous location.
then install the new file.
hope it helps.
let me know if it worked.
Click to expand...
Click to collapse
Hmm ... you are preventing the update of the SystemUI.apk? Even if your modification will work, you will have a 4.3 base system with a 4.2.2 SystemUI running ...
AndDiSa said:
Hmm ... you are preventing the update of the SystemUI.apk? Even if your modification will work, you will have a 4.3 base system with a 4.2.2 SystemUI running ...
Click to expand...
Click to collapse
Yup. Also u can just delete the verification part!
Sent from my Nexus 7 using XDA Premium HD app
That's clear for me, but you are not only deleting the verification part, but the update for the SystemUI.apk, too ...
Sent from my Nexus 7 using xda app-developers app
cmberry20 said:
Are you replacing the 'debuggerd' file within the 4.3 zip update? Or the file on the Nexus 7 before the 4.3 is flashed?
I've tried updating 4.3 using the OTA 4.3 zip & TWRP & my nexus 7 is currenly stuck the the 'X' boot logo.
Click to expand...
Click to collapse
I replaced the file on the Nexus 7 (in system/bin) before flashing 4.3.
Related
The OTA beta version was posted on XDA earlier today and removed by XDA. I am sure there are legal reasons they can't host a thread with a link to the files.
Plenty of us still have the file and may share info about it. The OTA patches exploits to root methods currently known. Join the irc and help us crack the root. Id be happy to share any file i have for you to use.
Chat with us
Thanks!
10char
hopefully this won't get pulled down too
MOD EDIT: Pulled down.
You might as well take it down. It's against forum rules i believe.
Sent from my MB860 using XDA App
Is this file tied to an IMEI? Or is the update file for any phone?
unfortunate
We don't know yet if its IMEI or sig checking I think I read that it is running checks against sigs. Also I think they only used imei to push the OTA to the phones not to lock that particular update to that particular phone
Sent from my MB860 using XDA Premium App
Sorry for the newbie question, but how do I use this update?
rename the zip to update.zip and put it in the root directory of your sd card, then boot into recovery and load it. If it fails the check you may need to reflash the original sbf first.
what do you mean rename the zip? are you referring to the file name or are you referring to a specific file? and also do we need to extract the file?
In the accompanying message it said something along the lines of 'who can use this uppate/ any atrix.'
Sent from my MB860 using XDA App
need help. did alll the steps corectly, then it says finding update package, opening update package, verifying update package, failed to read footer from /sdcard/update.zip (is a directory) signature verification failed, installation aborted. am i doing something wrong?
Has anyone tried putting the update file into their cache along with the ctc or cbc (don't remember what the file ext is) and tried hitting the update button in the phone to see if it recgonizes the update as though it actually came OTA?
Sent from my MB860 using XDA Premium App
Any known new bugs as of this update?
I am referring to the .zip file of the update that is available in the 3rd post.
PAulyhoffman said:
hopefully this won't get pulled down too
Click to expand...
Click to collapse
As far as copying to the cache goes, I did not try that but renaming to update.zip and updating through recovery worked fine after I re-flashed to the stock sbf. It took a little bit longer to go through the initial boot process after the update than it did flashing an sbf file, but seems to be smoother overall so far, I only have about an hour on it though.
diedemus said:
I am referring to the .zip file of the update that is available in the 3rd post.
As far as copying to the cache goes, I did not try that but renaming to update.zip and updating through recovery worked fine after I re-flashed to the stock sbf. It took a little bit longer to go through the initial boot process after the update than it did flashing an sbf file, but seems to be smoother overall so far, I only have about an hour on it though.
Click to expand...
Click to collapse
I've renamed the file to update.zip and have put it into the sdcard directory and then rebooted but have not noticed anything updating. I've also tried sdcard-ext directory. Can you explain a little as how you got this file to work? I am not rooted, and have not done any mods so I am on the original sbf.
Thanks for your help.
James62370 said:
I've renamed the file to update.zip and have put it into the sdcard directory and then rebooted but have not noticed anything updating. I've also tried sdcard-ext directory. Can you explain a little as how you got this file to work? I am not rooted, and have not done any mods so I am on the original sbf.
Thanks for your help.
Click to expand...
Click to collapse
Place the file in the root of your sdcard ext them reboot in recovery mode and I believe it will either update or prompt for if you want to run update.zip from sdcard
Sent from my MB860 using XDA Premium App
James62370 said:
I've renamed the file to update.zip and have put it into the sdcard directory and then rebooted but have not noticed anything updating. I've also tried sdcard-ext directory. Can you explain a little as how you got this file to work? I am not rooted, and have not done any mods so I am on the original sbf.
Thanks for your help.
Click to expand...
Click to collapse
When you reboot your phone hold the volume down button until you see the Fastboot text at the top of the phone, then hit the volume down button until you see it say Android Recovery, hit the volume up key to load into recovery, once you see the android guy and the triangle tap the lower right portion of the screen, from there you will have the recovery menu, at this point you can use volume up/down to select and then tap the ok at the bottom left
drock212 said:
Place the file in the root of your sdcard ext them reboot in recovery mode and I believe it will either update or prompt for if you want to run update.zip from sdcard
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
How do you reboot into recovery mode?
I'm thinking Moto is watching this forum very carefully to gauge the success of their root access lock-down efforts (I know I would). The only counter an open forum like this has is to delay posting of any new root access methods until after Moto's offical release of the ATRIX Update software. Time is on our side, not Moto's - their release process is long and expensive with little return in $$$. I know that devs are just starting to look at this, and a new root method is wishful thinking at this point, but just had to throw in my 2 cents.
I got the ota the other day and debated installing it because my M is rooted and the bootloader is unlocked and I have flashed ClockworkMod recovery. I searched for a while to see what others were saying and didn't really find anything of note so I decided to go ahead and run the install. When the phone rebooted into recovery and tried to install the update, it gave me the following Error: E: Failed to verify whole-file signature. Then there was an option to apply unsigned update (or zip, I can't remember the wording exactly). I chose not to do this and went back in the recovery menu and rebooted back into system. The phone booted normally and then immediately rebooted on its own back into recovery to try to install the update again, ending in the same results. This happened 2-3 more times before I finally formatted the Cache Partition through cwm which ended the bootloop (not sure that you can really describe that as a bootloop since it was actually doing what it thought it should be). My question is this, is it safe to go ahead and install the unsigned update via CWM? I have also since seen threads stating that if you had removed some of the bloatware apps, that the update would fail. I have removed many of these unneeded apps, should I reinstall them? I have seen a link or two to the bloat apks...
Having a unlocked bootloader doesn't matter. You just need to be stock 4.1.1 bloatware and all.
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
bobcheeks said:
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No. You don't have to unroot. You must have modified something else.
Sent from my Nexus 7 using Tapatalk 2
antp121 said:
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Click to expand...
Click to collapse
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
bwat1009 said:
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
Click to expand...
Click to collapse
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
antp121 said:
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
I RSDed back to 4.1.1 because mine hung on the clock app. I had installed the 4.2 clock.
bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
sloosecannon said:
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
Click to expand...
Click to collapse
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
bwat1009 said:
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
Click to expand...
Click to collapse
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Alright, thanks for the tip and the link, I will give it a try and let you know...
tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
I'm pretty sure you need an unlocked boot loader to downgrade.
netizenmt said:
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
I did. It fixed an issue where my phone wasn't booting, but it did not revert me to 4.1.1. Just found your comment in the other thread about modifying the xml file.. I'll try that next. Thanks.
patehi nice
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
That worked at getting the system apps that I had removed back into the /syste/app directory and now the update appears to be installing... Will let you know if it works.
*UPDATE*
Well that worked like a charm, update installed successfully, root access maintained, cwm allowed me to prevent reflash of stock recovery so all is right with the world... Thanks you guys!
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Thank you! I had missing Amazon_IMDb.apk, Facebook.apk, Kindle.apk, PlusOne.apk files. Copied these to my phone and updated successfully!
I installed 4.4 OTA and it showed what everything is ok..
asked me if I want to install some unsecured zip (I answer Yes )
asked me if I want to fix the root (I answer Yes )
and now, right after the installation finished , it is stuck on loading screen...
please help me
http://youtu.be/W3mAJ7Gxpuc?t=7m44s (this few seconds ont ht device screen...)
I never saw Kitkat's Welcome
mizaro said:
I installed 4.4 OTA and it showed what everything is ok..
asked me if I want to install some unsecured zip (I answer Yes )
asked me if I want to fix the root (I answer Yes )
and now, right after the installation finished , it is stuck on loading screen...
please help me
Click to expand...
Click to collapse
Use wugs toolkit. It can work with bootloop.
Sent from my Nexus 7 using Tapatalk 4
ritchea said:
Use wugs toolkit. It can work with bootloop.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
OLD ::
I have no idea what to do.. but I think I need to
"Flash Stock + unroot"
it is says that It will wipe all my personal data.
can I back it up on my computer from the rocovery or with cmd..
I want to save my photos and contacts
NEW ::
Never mind. (Thanks you dropbox for saveing my photos without my permission XD)
Thank you , ritchea!!
mizaro said:
OLD ::
I have no idea what to do.. but I think I need to
"Flash Stock + unroot"
it is says that It will wipe all my personal data.
can I back it up on my computer from the rocovery or with cmd..
I want to save my photos and contacts
NEW ::
Never mind. (Thanks you dropbox for saveing my photos without my permission XD)
Thank you , ritchea!!
Click to expand...
Click to collapse
Well, you did give it permission one time when you weren't stressed. Now you've flashed stock and UN rooted. Next, re-enable adb then root and flash custom recovery in the same process using wugs.
Sent from my Nexus 5 using Tapatalk
ritchea said:
Well, you did give it permission one time when you weren't stressed. Now you've flashed stock and UN rooted. Next, re-enable adb then root and flash custom recovery in the same process using wugs.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I think everything is going well. but, Why my buttons and notification areas are not transparent?
I've read it's not available for the updates. You can get the Nova launcher beta which does give transparent. http://novalauncher.com/beta/
Sent from my Nexus 5 using Tapatalk
mizaro said:
I installed 4.4 OTA and it showed what everything is ok..
asked me if I want to install some unsecured zip (I answer Yes )
asked me if I want to fix the root (I answer Yes )
and now, right after the installation finished , it is stuck on loading screen...
please help me
http://youtu.be/W3mAJ7Gxpuc?t=7m44s (this few seconds ont ht device screen...)
I never saw Kitkat's Welcome
Click to expand...
Click to collapse
I have the exact same problem. Was on rooted by stock Nexus 4. On TWRP recovery. Said yes to 4.4 OTA. Stuck in bootloop.
Trying Wug's Toolkit...
GauharJK said:
I have the exact same problem. Was on rooted by stock Nexus 4. On TWRP recovery. Said yes to 4.4 OTA. Stuck in bootloop.
Trying Wug's Toolkit...
Click to expand...
Click to collapse
Apply this without step 2 3 and 10:
http://forum.xda-developers.com/showthread.php?t=2010312
Then reinstall TWRP and SuperSU.
I always managed this way.
looppingz said:
Apply this without step 2 3 and 10:
http://forum.xda-developers.com/showthread.php?t=2010312
Then reinstall TWRP and SuperSU.
I always managed this way.
Click to expand...
Click to collapse
Thanks! I was in a boot loop and this solved it. Everything seems to be working fine. Are there any negative effects from not having flashed the userdata image? It doesn't update or change anything needed for 4.4?
smknight85 said:
Thanks! I was in a boot loop and this solved it. Everything seems to be working fine. Are there any negative effects from not having flashed the userdata image? It doesn't update or change anything needed for 4.4?
Click to expand...
Click to collapse
This solution always worked fine to me without sideeffect (except yesterday when trying to downgrade...). If you are updated and your apps are working fine and storage is there, then I guess you are setup well!
I've been using Omni since roughly the middle of December. I've been making use of the opendelta updates...but these have stopped working since 2014-02-17. I check for updates and it tells me Your system is up to date
My phone is a N7100 (Note 2)...note sure what other information is relevant here.
Anybody else experiencing this?
cavaliersa said:
I've been using Omni since roughly the middle of December. I've been making use of the opendelta updates...but these have stopped working since 2014-02-17. I check for updates and it tells me Your system is up to date
My phone is a N7100 (Note 2)...note sure what other information is relevant here.
Anybody else experiencing this?
Click to expand...
Click to collapse
Hmm, possibly the removal of the 2/18 nightly screwed up the system.
Try manually updating to see if it restarts.
I know that the Xperia ZL updates don't automagically flash... (they download on the internal sdcard drive, but attempt to flash from the external sdcard drive...)
That doesn't seem to be the issue you're describing though...
scifan said:
I know that the Xperia ZL updates don't automagically flash... (they download on the internal sdcard drive, but attempt to flash from the external sdcard drive...)
That doesn't seem to be the issue you're describing though...
Click to expand...
Click to collapse
Browse to the internal in TWRP and they should autoflash then.
I need to look into fixing TWRP's default search path when flashing via a script.
Entropy512 said:
Browse to the internal in TWRP and they should autoflash then.
I need to look into fixing TWRP's default search path when flashing via a script.
Click to expand...
Click to collapse
I browse to them, and flash them manually and it works... but it doesn't work automatically...
scifan said:
I browse to them, and flash them manually and it works... but it doesn't work automatically...
Click to expand...
Click to collapse
I had success going into TWRP Recovery mode and unchecking the zip file signature verification box. Once I did that, the autoupdates started to work again.
Entropy512 said:
Hmm, possibly the removal of the 2/18 nightly screwed up the system.
Try manually updating to see if it restarts.
Click to expand...
Click to collapse
After updating to 2/22 manually the next updates (2/23) was picked up...when prompted to Flash Now I did so but now the update did not go through automatically as it had/has been for the previous month or so. Browsing to the update and selecting to install it manually worked.
excaliber88 said:
I had success going into TWRP Recovery mode and unchecking the zip file signature verification box. Once I did that, the autoupdates started to work again.
Click to expand...
Click to collapse
I'll have a look at this when 2/24 comes out today.
Have the same problem "updates not working issue" when I did rollback to quickly solve the wifi issue on 18 feb.
See also my thread
http://forum.xda-developers.com/showthread.php?t=2652796
I see stil see the
omni-4.4.2-20140218-n7100-NIGHTLY.zip.md5sum
file.
Can somebody remove this md5 file so i don't have to do a manual update?
This will resolve the update not working issue.
Sent from my GT-N7100 using xda app-developers app
help
cavaliersa said:
After updating to 2/22 manually the next updates (2/23) was picked up...when prompted to Flash Now I did so but now the update did not go through automatically as it had/has been for the previous month or so. Browsing to the update and selecting to install it manually worked.
I'll have a look at this when 2/24 comes out today.
Click to expand...
Click to collapse
can you please tell me how to manually update omnirom, thanks
Sorry for not answer hichem but at least I see you came right.
To report back though...update went through smoothly last night.
A small (related) thing that has been bugging me though with Opendelta updates is that sometimes it takes a few Check now presses before it finds something...then it will stop and report that your system is up to date after having verified the update file you presently have and downloading the update file...press Check now again and it now patches the file before reporting that there is an update and you can flash.
Any reason to this behaviour?
hichem jerbi said:
can you please tell me how to manually update omnirom, thanks
Click to expand...
Click to collapse
Just download the lastest version from
http://dl.omnirom.org/
and go into recovery mode to install the update omnirom you just downloaded
Sent from my GT-N7100 using xda app-developers app
Ancientsthe said:
Just download the lastest version from
http://dl.omnirom.org/
and go into recovery mode to install the update omnirom you just downloaded
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
thx man
Ancientsthe said:
Just download the lastest version from
http://dl.omnirom.org/
and go into recovery mode to install the update omnirom you just downloaded
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thanks man,,it's done.
But after installing 24/02 update manually,,today's update 25/02 couldn't be installed automaticly !!! Any idea how to fix it ??
Resolved ,, just set install from internal storage in install mode of twrp
INFO: Rooted Version of NB4, I was on 4.4.2 Kit Kat leaked. I reverted to MJ5 from the leaked version then updated to NB4 and rooted with kingo.
Thanks to...
@smokeystack76
@Otisrhw
@Jakman85
@Azrael.arach
@Budrweber
UPDATE: 3/30/14
The same method has been confirmed by @Budrweber but instead of using adb, just flash from your ext sd card.
NOTE: ADB SIDELOAD WILL NOT CAUSE A WIPE, BUT PUSHING THE UPDATE FROM EXTERNAL SD WILL WIPE ALL DATA.
Few users have reported unrooting on NB4 after changing files and downloading the OTA and updating normally.
USB DEBUGGING MUST BE ENABLED, if you are this far there is no need for me to explain how to turn it on. If your phone is unresponsive to your computer even though you have installed, re-install via Kies 3. Turn Kies 3 off before running ADB.
First of all, you are going to need an ADB Sideloader and it can be found here.
Install to directory C:\Mini-SDK
We'll come back to ADB later.
Now you're going to need the update file found here.
Rename the file to update. (DO NOT NAME UPDATE.ZIP, JUST "UPDATE".)
Place "UPDATE" into the same directory as your ADB C:\Mini-SDK
Now lets leave ADB and the Update file alone and start replacing the files on your phone!
You'll need the following files.
system/xbin/dexdump (if deleted you can find the file here or you can copy/paste & replace)
system/csc/feature.xml (If deleted find it here.
Delete the original "feature.xml" and rename "feature.xml.bak" to "feature.xml")
Download the fix.zip from this page.
You do not have to reset permissions, I did not how ever do as you feel and works for you.
Step 1 copy the mobicore-presetup.sh to /system/bin
Step 2 copy all the APK files to /system/app.
Now navigate to system/bin
You should have a "ddexe" file, if it is named "ddexe_real", rename it to 'ddexe".
This should fix all the known errors in the process of adb side loading.
If you continue to get more errors use the file dump located here.
UPDATE: app_process is another recurring error, please grab this file from the dump uploaded from @smokeystack76
Now to the fun and most anticipated part of the day...
Volume + button up, power and home button all at the same time. Release once you see Recovery mode.
Navigate to Update from ADB.
Plug up to USB.
Now, when you start windows cmd prompt, you can either start from the ADB folder is located in by control, shift + right clicking or manual cmd.exe in "run" or "search"
Once command prompt is loaded,
Type in the following command.
"CD /D C:/MINI-SDK"
Then if you are in the right directory and you placed the "update" file accordingly... type...
ADB SIDELOAD UPDATE.ZIP(the file name should not have .zip or you will get a "can not read" message.)
and now you should be on your way to 4.4.2 Kit Kat.
Not bad. The system dump is here.
Now you need to post links to this thread in the other thread
Thanks for the step by step. I'll try this tomorrow.
You were on a rooted NB4, correct? You restored to MJ5, updated to NB4, rooted, and then did this?
clownfart said:
Thanks for the step by step. I'll try this tomorrow.
You were on a rooted NB4, correct? You restored to MJ5, updated to NB4, rooted, and then did this?
Click to expand...
Click to collapse
Correct.
For anyone trying to find an easy way around this whole update mess. Just go to your local best buy store and talk to one of the Samsung reps. They don't have the kit kat update yet but however they can reflash 4.3 on your phone wiping out all your data (make sure you do a back up from home) and this will let you get the OTA update with no problems. My note 3 has been rooted twice one being last night and it worked. Just make sure your not rooted when you take your phone.
Ciberious42 said:
Correct.
Click to expand...
Click to collapse
I think you should mention that in the OP for perfect clarity.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
incisivekeith said:
I think you should mention that in the OP for perfect clarity.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
I did actually...
Ciberious42 said:
I did actually...
Click to expand...
Click to collapse
I didn't see in the OP that you rooted the NB4.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
incisivekeith said:
I didn't see in the OP that you rooted the NB4.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Oh sorry I thought it would have been pretty clear when I mentioned you would be stuck with SU
smokestack76 said:
Not bad. The system dump is here.
Now you need to post links to this thread in the other thread
Click to expand...
Click to collapse
How do I flash this?
xuanphucn said:
How do I flash this?
Click to expand...
Click to collapse
you don't, it is used by DEV's to make a flashable update
carl1961 said:
you don't, it is used by DEV's to make a flashable update
Click to expand...
Click to collapse
Did we have any safe method yet? I want to keep root
xuanphucn said:
Did we have any safe method yet? I want to keep root
Click to expand...
Click to collapse
knoxraid
http://forum.xda-developers.com/showthread.php?t=2577273
I am currently updating the UrDroid Stock KitKat
carl1961 said:
knoxraid
http://forum.xda-developers.com/showthread.php?t=2577273
I am currently updating the UrDroid Stock KitKat
Click to expand...
Click to collapse
is this one use the official 4.4.2 or the leak?
Has anyone tried doing an emergency restore (or whatever it's called) through kies first then trying to get the OTA to work without failing?
It seems like it's 50/50 on who's works and who's fails. Am I right?
xuanphucn said:
is this one use the official 4.4.2 or the leak?
Click to expand...
Click to collapse
yes custom rom with latest OTA kitkat
Thanks OP. Worked for me. I'm ok with stock on the Note 3 that's why I got a nexus
Ciberious42 said:
Oh sorry I thought it would have been pretty clear when I mentioned you would be stuck with SU
Click to expand...
Click to collapse
So did you root with Kingo too when you were on NB4? I didn't want to use Kingo, but I thought what the heck, and used it for quick rooting. Then after the Kitkat update, I realize I have SuperSU as a system app even after factory reset. Apps like CPU-Z reports my devices is rooted when it's not.
Is this the only thing that's not same as pure stock NC2?
hp79 said:
So did you root with Kingo too when you were on NB4? I didn't want to use Kingo, but I thought what the heck, and used it for quick rooting. Then after the Kitkat update, I realize I have SuperSU as a system app even after factory reset. Apps like CPU-Z reports my devices is rooted when it's not.
Is this the only thing that's not same as pure stock NC2?
Click to expand...
Click to collapse
you can re-run and use kingo to remove the root
Also if you are weary of the update, back up your files and apps then factory reset. Once you are factory reset, download the OTA but just hit "remind me later".
Do the instructions in the OP and after it installs it tells you that you have an update pending, install the update and it covers any files that may have went missing in the update.zip.
If you wanted to be 200% sure.
I am set at official and with no custom lock and Knox is 0x0.