Related
So I rooted my P6010 and installed CWM but now I'm checking for updates in anticipation of ICS (fingers crossed any day now) and I get an update (stability 17.08MB) but it won't apply as there's no stock recovery installed.
Everything it reboots to try to opens CWM obviously about to apply but can't...
No sign of a downloaded update in the obvious places.
Where do the Samsung OTAs download to?
Sent from my GT-P6810 using XDA Premium App
Jompet said:
So I rooted my P6010 and installed CWM but now I'm checking for updates in anticipation of ICS (fingers crossed any day now) and I get an update (stability 17.08MB) but it won't apply as there's no stock recovery installed.
Everything it reboots to try to opens CWM obviously about to apply but can't...
No sign of a downloaded update in the obvious places.
Where do the Samsung OTAs download to?
Sent from my GT-P6810 using XDA Premium App
Click to expand...
Click to collapse
You can flash the stock recovery back. Get your stock rom, extract the recovery.img
Make a uncompressed tar with just recovery.img in it. Then flash this tar with odin (in the pda)
Tip: dont use 7-zip to build the tar, it just wont work. You should use linux or busybox tar in your tab to create it.
This way you can switch between cwm and stock recovery as necessary.
Thanks for your help. I'm aware of this and I realise I could do this but it's a lot of hassle when I'd prefer to investigate the option of just flashing the OTA using CWM. I just need to find out where the damn file is!
Sent from my GT-P6810 using XDA Premium App
When I try
reboot fota
from a terminal as root, I get a log dumped in /cache/fota
It looks like its looking in multiple locations for a directory tmp_sec_fota.
I dont have any updates, so it all fails, but maybe a clue?
I had a good look around but can't seem to be able to find anything. Shame.
I pulled this screenshot from CWM logs and there's a lot of reference to fota but everywhere I look there's no file even approaching 17MB.
Now I have a real problem because the Tab is my only device apart from a Galaxy Nexus so I don't think I can get a copy of stock recovery. I can flash as I've got MobileOdin though. I'm wondering if it's worth the hassle to do all of this for the OTA or if I should just wait for a version I can flash with CWM.
I only really rooted to sort the rw problem out with my 64GB MSD, if Samsung had have been better devastating I wouldn't have had to.
Sent from my GT-P6810 using XDA Premium App
Stupid swiftkey. I obviously meant developers not devastating.
Sent from my GT-P6810 using XDA Premium App
Those partitions in your photo are not correct for a p6810. You must have the wrong cwm installed.
/system is on /dev/block/mmcblk0p8
on my device, and your data and preload are wrong as well.
Where did you get the cwm. Could you be using one for the p6800? It has different partitions.
See the 7.7 development thread for one suited to the p6810.
Be very careful what operations you select if you have wrong cwm!
Also, any backups you have previously made (with the wrong cwm) should probably be discarded, as the data files will be misnamed/incorrect contents.
I got it from the P6010 CWM thread...? Strange.
I've discarded it and moved back to stock, ran the updates and everything works well now. Ran into some minor permissions stuff with modin but sorted it with removal from such app.
I think a lot of people are going to bump into these problems when ICS hits if they're running CWM.
Sent from my GT-P6810 using XDA Premium App
Oh and thanks for all your help!
Sent from my GT-P6810 using XDA Premium App
Has anyone tried this method? SuperSU has a full unroot option in its settings. I have read many posts saying it is impossible to unroot at this time.
I did a little searching around and didn't find much. Just suggestions to try it and no one ever reported back if it works or doesn't.
I personally don't have the OTA and have a custom ROM, but i would like to know any confirmation of it working or not working by anyone that has tried it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I did the ota to mf3 and successfully rooted it I then realized that I had like 6gbs missing so in an effort to restore I went into the SU settings and chose the remove root option and it seemed to work I checked with root checker and I no longer had root access I still was unable to restore it just bumps me into Odin mode and I have to boot power+home+volume- then cancel to reboot my phone into working order
But as far as I can tell I have no root
Since I can't restore and try and clear up my missing storage I wanted to take it in and try and get a new one under warranty but I'm afraid to use triangle away so I'm just gonna wait it out until we get a mf3 restore firmware for Odin since my phone works fine for now
Sent from my SAMSUNG-SGH-I337 using xda premium
So that is 1 confirmation for an unroot. Basically hit unroot, it sends the phone to bootloop. Remove battery, put it back, then boot to download mode with power+volume down, then hit volume down again to cancel and reboot to a fully functional phone with no root. If that doesn't work, use power+home+volume down. Anyone else?
Btw,
Don't use triangle away. It flashes a temporary recovery to reset the binary. It will brick you or just fail.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
Has anyone tried this method? SuperSU has a full unroot option in its settings.
Click to expand...
Click to collapse
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
So delete the busybox files first, then unroot. That is 2 confirmed unroots.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ou812bkewl said:
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
Click to expand...
Click to collapse
graydiggy said:
So delete the busybox files first, then unroot. That is 2 confirmed unroots.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This method also worked for me as well. Had no problems following the steps.
3 confirmed
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
3 confirmed
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Good info to know. Thanks graydiggy
I am going to change this to a how to thread later today. Anyone else try it?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
this may be a stupid question, but if you went through the trouble of rooting after the mf3 update.. why would you want to unroot?
Warranty replacement in case of a hardware issue, testing purposes, also, some people only want a temp root to remove bloat. After that, they don't want root anymore.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
So to summarize the steps from what I've read on rooting & unrooting MF3:
Root:
Use this guide by jortex: http://forum.xda-developers.com/showthread.php?t=2387577&highlight=mf3
Unroot: http://forum.xda-developers.com/showpost.php?p=44495559&postcount=39
1. Re-root again using the same method you did before for MF3, then:
--a) Reboot, update SuperSU app and it's binary
--b) Reboot again, verify device status is back to"Official"
--c) Reboot again, verifying that, this time, the boot screen is back to normal again
2. Download a file manager app in the Play Store called "Total Commander" and enable "Root functions everywhere" in its settings.
3. Navigate to a folder called "/system/xbin"
4. Delete ONLY files in that folder with the word "busybox" within its filename or symlink path. You should end up with three files left. I did. Two of them are SuperSU related. DO NOT DELETE ANY OF THEM!
5.Open SuperSU and, in its settings, select the "Full un-root" option. Once SuperSU closes, reboot.
Click to expand...
Click to collapse
Follow step 1 if not rooted or messed up somewhere during unrooting process.
Just double checking step 2: We can use es file explorer with root explorer option as well correct?
Also I noticed superSU got updated today:
http://forum.xda-developers.com/showthread.php?t=1538053
05.09.2013 - v1.60
- Added SELinux+Enforcing compatibility (for new SGS4 ROMs)
- Fixed (newest) CWM versions asking you question that break root if answered wrongly
- Fixed issue with the TWRP/CWM binary installer
- Fixed 4.3 OTA survival looping
Click to expand...
Click to collapse
Does the new update have something to do with our mf3 baseband like SELinux?
haremmon said:
So to summarize the steps from what I've read on rooting & unrooting MF3:
Root:
Use this guide by jortex: http://forum.xda-developers.com/showthread.php?t=2387577&highlight=mf3
Unroot: http://forum.xda-developers.com/showpost.php?p=44495559&postcount=39
Follow step 1 if not rooted or messed up somewhere during unrooting process.
Just double checking step 2: We can use es file explorer with root explorer option as well correct?
Also I noticed superSU got updated today:
http://forum.xda-developers.com/showthread.php?t=1538053
Does the new update have something to do with our mf3 baseband like SELinux?
Click to expand...
Click to collapse
This worked for me! But I skipped all the steps in the beginning. They sounded useless to me. Rerouting to unroot? Hah
I deleted all busybox files and was left with 3 files then went to SuperSU and did the full unroot and restart.
I check with root checker and installed SuperSU as well. Root checker said I have no root and SuperSU fails. Status is official.
Going to restart a few times to be sure.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
WezzleD said:
This worked for me! But I skipped all the steps in the beginning. They sounded useless to me. Rerouting to unroot? Hah
I deleted all busybox files and was left with 3 files then went to SuperSU and did the full unroot and restart.
I check with root checker and installed SuperSU as well. Root checker said I have no root and SuperSU fails. Status is official.
Going to restart a few times to be sure.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Nice! Thank you. Looks like 4 confirmed. Also, was SuperSU on v1.60?
haremmon said:
Nice! Thank you. Looks like 4 confirmed. Also, was SuperSU on v1.60?
Click to expand...
Click to collapse
I'm actually not sure. Didn't look at version numbers.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
4 confirmed. Let's get 5 and I will post a how to.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ou812bkewl said:
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
Click to expand...
Click to collapse
That method worked for me also. I'm so glad it was discovered. Successfully unrooted.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
5!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
5!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to unlock as well. However my phone stopped showing the custom unlocked symbol at bootup a few days ago (before doing this) and I am at a loss as to why. So I am not sure I can count as a real confirmation.
I did your unroot process, root checker confirms I no longer have root and the unlock symbol has not come back.
Stay tuned guys. Getting everything ready to quickly make a more organized how to.
Being horribly sick is not helping
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
First off I apologize if this is in the wrong section or has been asked before, I couldn't really find the answer I'm looking for.
So I have my S4 (4.2.2 if it matters) rooted and TWRP recovery loaded on it. I was getting the ATT update message and I kept hitting ignore or remind me latter, however I noticed last night it starts to try to install and restart without giving me an option to cancel it. I quickly remove the battery to prevent my phone from updating.
My question is, how do I stop this update when I turn my phone back on? I don't want it to update the firmware and lock my boot loader. Or am I making a big deal over nothing?
Thanks in advance
Google how to stop ota i337 xda
You're not over reacting
jd1639 said:
Google how to stop ota i337 xda
You're not over reacting
Click to expand...
Click to collapse
Thanks so much.
Just one more think, I just want to make sure that when I turn my phone back on that the update won't finish installing (it was in the process of installing when I shut it off).
Thanks again for all the help.
I'm assuming that u have MDB/MDL firmware. ......Take your Att sim card out. ... u need to root your phone. ... install Titanium back up and go to Att software update app ....back up first just incase u need it to return to att and then uninstall it...... that's should stop it from OTA update
SWYPED_FROM_S4_MF3_REDVENOM
Yep, you're going to want to root and then rename or freeze those files, you found in the Google search. That will stop the update
Taking just the SIM out at this point won't help. Only way to completely stop it now since it was installing is to Odin back to MDL and start the root process.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
---------- Post added at 01:34 PM ---------- Previous post was at 01:34 PM ----------
Hopefully it didn't already blow the qfuse.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ted77usa said:
I'm assuming that u have MDB/MDL firmware. ......Take your Att sim card out. ... u need to root your phone. ... install Titanium back up and go to Att software update app ....back up first just incase u need it to return to att and then uninstall it...... that's should stop it from OTA update
SWYPED_FROM_S4_MF3_REDVENOM
Click to expand...
Click to collapse
So not to keep asking the same question, when the sim card is out of the phone, will that prevent the update from installing?
Also to clarify, I've already rooted my phone and installed TWRP recovery. Again at this point I just want to make sure that when I turn my phone on the update isn't going to automatically finish installing before I can block the app/files
Again, thanks so much for the help, can't wait to get a rom installed and start enjoying the awesomeness
I'd follow graydiggy suggestion. Don't turn it on except to go into download mode. Flash the mdl firmware, then root again and freeze the update apps or install a custom Rom
I could be wrong but I believe the update won't apply since the stock recovery has been replaced with a custom recovery . If I am wrong Im sure somone will come in and correct this statement .
SouthernEvo said:
I could be wrong but I believe the update won't apply since the stock recovery has been replaced with a custom recovery . If I am wrong Im sure somone will come in and correct this statement .
Click to expand...
Click to collapse
Won't matter
If you have a custom recovery, the update should fail the install with an error 7. However, I would still completely start from scratch by using Odin to get a clean slate without an update. You could actually use Kies and do the emergency restore. Whatever you do, do not boot the phone into the OS until it has been completely wiped by either Odin or Kies. Only download mode.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
boot into recovery and in twrp manually go erase the update.zip from cache/fota. Then wipe cache before rebooting. That, or flash the PIT file. I posted directions on how to extract the stock signed PIT file but you'll probably need someone to extract one for you since you dont want to boot to Android yet.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Oh yeah. TWRP has a file manager. Delete the update and then boot the OS and use Titanium Backup to delete the OTA stuff
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Surge1223 said:
boot into recovery and in twrp manually go erase the update.zip from cache/fota. Then wipe cache before rebooting. That, or flash the PIT file. I posted directions on how to extract the stock signed PIT file but you'll probably need someone to extract one for you since you dont want to boot to Android yet.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
graydiggy said:
Oh yeah. TWRP has a file manager. Delete the update and then boot the OS and use Titanium Backup to delete the OTA stuff
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sweet so by doing this I don't have to Odin back to stock?
Essentially.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Thank you everyone so much for your help. I seem to have got it all sorted out, don't see any changes to the baseband version and still have root access.
Thanks again.
the_windrammer said:
Thank you everyone so much for your help. I seem to have got it all sorted out, don't see any changes to the baseband version and still have root access.
Thanks again.
Click to expand...
Click to collapse
Glad you got it worked out. You had the A team, surge and graydiggy
a different approach w/ i537 jb4.2.2
on topic but with different variables... I'm not finding a detailed post on the best way to stop ATT update immediately after rooting the i537 jb4.2.2
Can someone link me here please?
Not sure if I should just delete the app or go the root explorer route and delete the knox file (not sure if that is the only file to remove either?)
I have compiled all my notes at: freehelpinghands.wordpress DOT com/2013/12/15/best-way-to-unlock-root-a-new-phone/
and the answer to my question above will likely be answered by the time this is being read.
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.
So I've had this problem for a while and I think at one point I knew what the issue was, but things came up and I guess I lost my place. I have a GS4 running 4.3 on AT&T, but if I recall correctly it took a long time (longer than it was supposed to in US) for even that update to become available to me. I'm not sure if this phone is set as a different country or something, but I seem to think that had something to do with it when I checked last time. Now when I check for updates, it does say I have an available update (KitKat?) but fails when attempting to update. Download is successful, but install is not. Baseband is I337ucuemk2 if that helps anything. Any help here would be appreciated, thanks.
Install is failing as some of the files it is trying to update has been modified. You would have to be on stock for the update to work.
Remember that there is no direct root method for KitKat yet.
http://forum.xda-developers.com/showthread.php?t=2616221 for more info
Sent from my GT-I9505 using Tapatalk
jmjoyas said:
Install is failing as some of the files it is trying to update has been modified. You would have to be on stock for the update to work.
Remember that there is no direct root method for KitKat yet.
http://forum.xda-developers.com/showthread.php?t=2616221 for more info
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I'm actually not rooted, already stock and still having errors still...any idea why that would be?
Anyone have any advice?
Anyone have any advice?
Click to expand...
Click to collapse
Have you changed any system files and do you have xposed running? They'll break the ota.
Edit, I should have read closer. I think there is an update.zip file you could flash in the general forum. I'll look and see if I can find it.
See post 2 http://forum.xda-developers.com/showthread.php?p=50667360
Sent from my Nexus 5
jd1639 said:
Have you changed any system files and do you have xposed running? They'll break the ota.
Edit, I should have read closer. I think there is an update.zip file you could flash in the general forum. I'll look and see if I can find it.
See post 2 http://forum.xda-developers.com/showthread.php?p=50667360
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for the link, so I should just flash the md5 with Odin? Appreciate the help.
Imnice777 said:
Thanks for the link, so I should just flash the md5 with Odin? Appreciate the help.
Click to expand...
Click to collapse
No, flash the update.zip in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
No, flash the update.zip in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok cool, thanks again...however now another issue. I've tried several times, I can not boot into recovery. Any time I try to the phone just goes black until I let go and then reboots. Even if I get the blue print in the top left, the phone does not boot into recovery. Any idea why this would be?
Imnice777 said:
Ok cool, thanks again...however now another issue. I've tried several times, I can not boot into recovery. Any time I try to the phone just goes black until I let go and then reboots. Even if I get the blue print in the top left, the phone does not boot into recovery. Any idea why this would be?
Click to expand...
Click to collapse
If you can get into download mode you may be better off flashing the md5 and Odin. Don't know why you can't get into recovery
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you can get into download mode you may be better off flashing the md5 and Odin. Don't know why you can't get into recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Me either, guess I'd just flash normally like I would a rom? Or would an update be different. I haven't done this in a while.
Imnice777 said:
Me either, guess I'd just flash normally like I would a rom? Or would an update be different. I haven't done this in a while.
Click to expand...
Click to collapse
If you flash the tar in Odin it's going to wipe your device so backup what you can. You'll need to download the tar file to your pc and download Odin to it too if you don't already have it. You run Odin from the pc
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you flash the tar in Odin it's going to wipe your device so backup what you can. You'll need to download the tar file to your pc and download Odin to it too if you don't already have it. You run Odin from the pc
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok so I finally got into recovery, but am I supposed to rename the file or anything? It keeps telling me:
"-- Verify the file type of MD5, Before Install /sdcard ...
-- Install /sdcard"
Imnice777 said:
Ok so I finally got into recovery, but am I supposed to rename the file or anything? It keeps telling me:
"-- Verify the file type of MD5, Before Install /sdcard ...
-- Install /sdcard"
Click to expand...
Click to collapse
Anyone ever see that error before?
Imnice777 said:
Anyone ever see that error before?
Click to expand...
Click to collapse
Are you trying to flash the update.zip? I'd re-download it. It could be a bad download
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Are you trying to flash the update.zip? I'd re-download it. It could be a bad download
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So... pretty unhappy. Downloaded the update.zip and flashed in stock recovery, it wiped my whole phone and still didn't update. I saw a couple error messages appear as it was "updating" so now I'm still on old firmware and lost everything on my phone. Luckily I did a Kies backup but still pretty ridiculous. I still lose all save data from apps and all convenience that there was from using my phone for as long as I did. Just wanted to update, shouldn't be this big of a mess. Not sure what to do next.
Imnice777 said:
So... pretty unhappy. Downloaded the update.zip and flashed in stock recovery, it wiped my whole phone and still didn't update. I saw a couple error messages appear as it was "updating" so now I'm still on old firmware and lost everything on my phone. Luckily I did a Kies backup but still pretty ridiculous. I still lose all save data from apps and all convenience that there was from using my phone for as long as I did. Just wanted to update, shouldn't be this big of a mess. Not sure what to do next.
Click to expand...
Click to collapse
Well that sucks. No idea how it works wipe you're device. It shouldn't touch the userdata. If it's truly wiped I'd Odin the nb1 tar at this point. Get it updated and start over
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Well that sucks. No idea how it works wipe you're device. It shouldn't touch the userdata. If it's truly wiped I'd Odin the nb1 tar at this point. Get it updated and start over
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That's what I did and I'm finally updated, but pretty disappointed that it took all that just for an update. Hopefully things like that don't continue in future updates...