Related
I've noticed that a lot off people get the update, try to apply it, then are disappointed when all the get on reboot is an android with an exclamation mark so I figured I would shed some light on how to minimize this and it comes down to checking the updater-script which I'll tell you how I do. First thing I do after getting the prompt for an update is let it download. After it downloads I use root explorer(since I am rooted) and copy the update from /cache to /sdcard because one thing I've noticed is that I can't get the prompt to update again if it fails so this way I've got my own backup of the update. Now, instead of accepting the update I first append .zip to the dlpkgfile in /sdcard so that I can open it. Open it and navigate to "\META-INF\com\google\android\" and open "updater-script" which should open in the text editor. This file is exactly what the update is running when it starts. First in the file is a list of asserts and these are what generally cause the update to fail. What they do is check to make sure the file it is going to patch is unmodified so that it can successfully patch it. If it detects the file it's checking is modified it kicks to the !. 8.6.5.6 initially didn't work for me but by checking the script I found the problem was my srs_processing.cfg file because I tried to fix my speaker balance and this was a file that the script asserted. After restoring the original file I was able to update with stock recovery even though I had modified other system files including kernel. As long as the specific files the update checks are ok the update will proceed. If you have never modified anything and are completely stock then you don't have to do this, it's just nice knowing what's going on.
Here is a list of everything that is checked:
Code:
system/app/AWS.odex
system/app/ApplicationsProvider.apk
system/app/ApplicationsProvider.odex
system/app/AsusReader.apk
system/app/AsusReader.odex
system/app/AsusSetupWizard.odex
system/app/Bluetooth.apk
system/app/Bluetooth.odex
system/app/BooksTablet.odex
system/app/Browser.apk
system/app/Browser.odex
system/app/CMClient.apk
system/app/CMClient.odex
system/app/Calculator.apk
system/app/Calculator.odex
system/app/Calendar.apk
system/app/Calendar.odex
system/app/CalendarProvider.apk
system/app/CalendarProvider.odex
system/app/Camera.odex
system/app/CertInstaller.apk
system/app/CertInstaller.odex
system/app/ChromeBookmarksSyncAdapter.odex
system/app/Contacts.apk
system/app/Contacts.odex
system/app/ContactsProvider.apk
system/app/ContactsProvider.odex
system/app/DLNA.apk
system/app/DLNA.odex
system/app/DMClient.apk
system/app/DMClient.odex
system/app/DefaultContainerService.apk
system/app/DefaultContainerService.odex
system/app/DeskClock.odex
system/app/Dictionary.odex
system/app/DownloadProvider.apk
system/app/DownloadProvider.odex
system/app/DownloadProviderUi.apk
system/app/DownloadProviderUi.odex
system/app/DrmProvider.apk
system/app/DrmProvider.odex
system/app/Email.odex
system/app/EmailWidget.apk
system/app/EmailWidget.odex
system/app/Exchange.odex
system/app/FacebookPoster.odex
system/app/FileManager.apk
system/app/FileManager.odex
system/app/Finsky.odex
system/app/GalleryNew3DGoogle.odex
system/app/Gmail.odex
system/app/GoogleBackupTransport.odex
system/app/GoogleCalendarSyncAdapter.odex
system/app/GoogleContactsSyncAdapter.odex
system/app/GoogleFeedback.odex
system/app/GoogleLoginService.odex
system/app/GooglePartnerSetup.odex
system/app/GoogleQuickSearchBox.odex
system/app/GoogleServicesFramework.odex
system/app/HTMLViewer.apk
system/app/HTMLViewer.odex
system/app/HoloSpiralWallpaper.apk
system/app/HoloSpiralWallpaper.odex
system/app/Keyboard.odex
system/app/Kindle-OEM.odex
system/app/LatinImeGoogle.odex
system/app/Launcher2.apk
system/app/Launcher2.odex
system/app/Layar.odex
system/app/LiveWallpapersPicker.apk
system/app/LiveWallpapersPicker.odex
system/app/MEar.odex
system/app/Maps.odex
system/app/MarketUpdater.odex
system/app/MediaProvider.apk
system/app/MediaProvider.odex
system/app/MediaUploader.odex
system/app/ModemUpdateService.odex
system/app/Music2.odex
system/app/MyCloud.odex
system/app/MyGazine.odex
system/app/MyWater.odex
system/app/NVIDIATegraZone.odex
system/app/NetworkLocation.odex
system/app/OneTimeInitializer.odex
system/app/PCSyncLauncher.odex
system/app/PRAndroid.odex
system/app/PackageInstaller.apk
system/app/PackageInstaller.odex
system/app/Phone.apk
system/app/Phone.odex
system/app/PicoTts.odex
system/app/PixWe.odex
system/app/PolarisOffice.apk
system/app/PolarisOffice.odex
system/app/Screenshot.apk
system/app/Screenshot.odex
system/app/Settings.apk
system/app/Settings.odex
system/app/SettingsProvider.apk
system/app/SettingsProvider.odex
system/app/SetupWizard.odex
system/app/SoundRecorder.apk
system/app/SoundRecorder.odex
system/app/StrAsus.odex
system/app/Street.odex
system/app/SystemUI.apk
system/app/SystemUI.odex
system/app/Talk.odex
system/app/TelephonyProvider.apk
system/app/TelephonyProvider.odex
system/app/TtsService.apk
system/app/TtsService.odex
system/app/UpdateLauncher.apk
system/app/UpdateLauncher.odex
system/app/UserDictionaryProvider.apk
system/app/UserDictionaryProvider.odex
system/app/Vending.odex
system/app/Vibe2.odex
system/app/VideoEditorGoogle.odex
system/app/Videos.odex
system/app/VoiceSearch.odex
system/app/Weather.odex
system/app/XT9IME.apk
system/app/XT9IME.odex
system/app/YouTubeTablet.odex
system/app/ZinioReader.odex
system/app/ZinioSettingsProvider.odex
system/bin/brcm_ram_plus
system/bin/debuggerd
system/bin/fu
system/bin/vold
system/bin/wpa_supplicant
system/buildrop
system/framework/am.jar
system/framework/am.odex
system/framework/androidolicy.jar
system/framework/androidolicy.odex
system/framework/android.test.runner.jar
system/framework/android.test.runner.odex
system/framework/apache-xml.jar
system/framework/apache-xml.odex
system/framework/bmgr.jar
system/framework/bmgr.odex
system/framework/bouncycastle.jar
system/framework/bouncycastle.odex
system/framework/com.android.future.usb.accessory.jar
system/framework/com.android.future.usb.accessory.odex
system/framework/com.android.locationrovider.jar
system/framework/com.android.locationrovider.odex
system/framework/core-junit.jar
system/framework/core-junit.odex
system/framework/core.jar
system/framework/core.odex
system/framework/ext.jar
system/framework/ext.odex
system/framework/framework-res.apk
system/framework/framework.jar
system/framework/framework.odex
system/framework/ime.jar
system/framework/ime.odex
system/framework/input.jar
system/framework/input.odex
system/framework/javax.obex.jar
system/framework/javax.obex.odex
system/framework/monkey.jar
system/framework/monkey.odex
system/framework/pm.jar
system/framework/pm.odex
system/framework/services.jar
system/framework/services.odex
system/framework/sqlite-jdbc.jar
system/framework/sqlite-jdbc.odex
system/framework/svc.jar
system/framework/svc.odex
system/lib/drm/libdrmwvmplugin.so
system/lib/hw/gralloc.tegra.so
system/lib/libandroid_servers.so
system/lib/libbcc.so
system/lib/libereader.so
system/lib/libinput.so
system/lib/libjSebring.so
system/lib/libnvomx.so
system/lib/libsensors.mpl.so
system/lib/libsrsprocessing.so
system/lib/libstagefright.so
system/lib/libwebcore.so
system/lib/libwvdrm.so
system/lib/libwvm.so
system/lib/modules/bcm4329.ko
system/lib/modules/scsi_wait_scan.ko
I can remember with an old 2.1 tablet we used to modify the actual update script and remove the part of the script that it checks against, so the update would go ahead without checking anything.
Guys, supposing the FOTA update has gone wrong (that's my case, and i understood why... most probably the issue is related to my modified wpa_supplicant this time) ... Is there any way to re-trigger the update procedure?
As far as I've understood the update is cached after download in the tablet, is there any way to retry in case something's gone wrong?
Otherwise, as far as I know, the only way is to bring everything to stock using Nvflash and original ROM and wait for Asus to put on their site the update. That seems to be related to the fact that Asus servers track any FOTA request for a device and let you download it only once.
If you're US you can get the update from here http://forum.xda-developers.com/showthread.php?t=1231635 rename the update to EP101_SDUPDATE.zip put it on the root of a microsd card then boot the transformer into recovery and it will update. As for the wpa_supplicant, use the stock 3.1 in the OP of this post http://forum.xda-developers.com/showthread.php?t=1093778 and you should be able to update.
alex5790 said:
If you're US you can get the update from here http://forum.xda-developers.com/showthread.php?t=1231635 rename the update to EP101_SDUPDATE.zip put it on the root of a microsd card then boot the transformer into recovery and it will update.
Click to expand...
Click to collapse
Can I use CWM recovery or stock recovery required?
rufik said:
Can I use CWM recovery or stock recovery required?
Click to expand...
Click to collapse
I'm pretty sure you have to have stock recovery. If you have CWM you could try it and the worst thing that could happen is just the update failing. Also make sure you have a U.S. transformer because that specific update is U.S.
Hmm, I dont have the compass issues so Im trying to decide here if its worth restoring my old SystemUI (I am running the stock buttons) because that is the only thing I changed when rooted in order to update or just wait for someone to put out a deodexed version.
alex5790 said:
I'm pretty sure you have to have stock recovery. If you have CWM you could try it and the worst thing that could happen is just the update failing. Also make sure you have a U.S. transformer because that specific update is U.S.
Click to expand...
Click to collapse
Is there a quick and easy way to restore/flash the stock recovery? I have CWM and want to get the stock recovery back, but so far the only ways I've found to do that require using nvflash and wiping everything. Am I wrong? It seems like there should be an easier way. On my Evo 4G I was able to flash back and forth between recoveries.
My firmware has been downloaded but is not in /cache. Is there another location where it could have downloaded to? What is the file name of the update?
kenlperry said:
Is there a quick and easy way to restore/flash the stock recovery? I have CWM and want to get the stock recovery back, but so far the only ways I've found to do that require using nvflash and wiping everything. Am I wrong? It seems like there should be an easier way. On my Evo 4G I was able to flash back and forth between recoveries.
Click to expand...
Click to collapse
For the transformer I don't know of a easy way that would be a question for a dev.
GiantSeaturtle said:
My firmware has been downloaded but is not in /cache. Is there another location where it could have downloaded to? What is the file name of the update?
Click to expand...
Click to collapse
It should be named dlpkgfile. If you are not running a file explorer as root the /cache directory will appear empty. I personally use root explorer because it runs as root by default. I'm not sure what other file explorers can run as root.
I was one of the dumb ones and ran the update while still rooted ( thought I wasn't but I guess I was). I then used the Nvflash and original ROM to get back to stock US 8.6.5.6. I then followed the direction in the post to get he dlpkgfile and renamed it EP101_SDUPDATE.zip and put it on the root of the SDcard and booted into the RCK and I am still getting the Yellow ! mark. All I did while rooted was apply the netflix patch but I was under the assumption that if I ran the NvFlash back to root that it put back the original file for libnvomx.so. Is that not the cause and has anyone been able to use this dlpkgfile to get to the updated version?
Thanks
dugout2929 said:
I was one of the dumb ones and ran the update while still rooted ( thought I wasn't but I guess I was). I then used the Nvflash and original ROM to get back to stock US 8.6.5.6. I then followed the direction in the post to get he dlpkgfile and renamed it EP101_SDUPDATE.zip and put it on the root of the SDcard and booted into the RCK and I am still getting the Yellow ! mark. All I did while rooted was apply the netflix patch but I was under the assumption that if I ran the NvFlash back to root that it put back the original file for libnvomx.so. Is that not the cause and has anyone been able to use this dlpkgfile to get to the updated version?
Thanks
Click to expand...
Click to collapse
It has to be the external microsd card, not the internal sdcard.
alex5790 said:
It has to be the external microsd card, not the internal sdcard.
Click to expand...
Click to collapse
Thanks, I went ahead and ran it from the MicroSD card and I am getting still getting the yellow !. I would have thought had I done the nflash to the current rom it would have reset all the files under system.
dugout2929 said:
Thanks, I went ahead and ran it from the MicroSD card and I am getting still getting the yellow !. I would have thought had I done the nflash to the current rom it would have reset all the files under system.
Click to expand...
Click to collapse
The only other asserts are:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/US_epad/EeePad:3.2/HTJ85B/US_epad-8.6.5.6-20110726:user/release-keys"
and
assert(getprop("ro.product.device") == "EeePad"
so unless those are different it should work especially if you nvflashed it back to stock. Does it immeadiately go to ! or does the green bar at least progress a little? Also what region eg. US,WW,TW
alex5790 said:
The only other asserts are:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/US_epad/EeePad:3.2/HTJ85B/US_epad-8.6.5.6-20110726:user/release-keys"
and
assert(getprop("ro.product.device") == "EeePad"
so unless those are different it should work especially if you nvflashed it back to stock. Does it immeadiately go to ! or does the green bar at least progress a little?
Click to expand...
Click to collapse
It does a the progress bar for about 1 sec or so. It is the US version.
kenlperry said:
Is there a quick and easy way to restore/flash the stock recovery? I have CWM and want to get the stock recovery back, but so far the only ways I've found to do that require using nvflash and wiping everything. Am I wrong? It seems like there should be an easier way. On my Evo 4G I was able to flash back and forth between recoveries.
Click to expand...
Click to collapse
You can use nvflash to "download" partition 5 which is the SOS/recovery. You can reflash the stock and apply the stock OTA. There will be no --create flag in the nvflash command.
A modded OTA won't work with the stock recovery because of signature checks.
CWM should be able to flash everything but the blob, but you have to mount system first. You can mount staging and then the blob will flash as well (after a manual reboot to recovery). I have to admit that it is a pretty convoluted process if your android-fu is weak.
sent from my cyanogen(mod) vision
dugout2929 said:
It does a the progress bar for about 1 sec or so. It is the US version.
Click to expand...
Click to collapse
Possibly there could be something wrong with the rom used to nvflash. What you could try next is go to Asus's site and get the 8.6.5.6 update, unzip it once so that it is only a single zip file, rename it to EP101_sdupdate put it on the root of the microsd and try to flash that then try to flash 8.6.5.9 again
alex5790 said:
Possibly there could be something wrong with the rom used to nvflash. What you could try next is go to Asus's site and get the 8.6.5.6 update, unzip it once so that it is only a single zip file, rename it to EP101_sdupdate put it on the root of the microsd and try to flash that then try to flash 8.6.5.9 again
Click to expand...
Click to collapse
I was able to do this and it worked perfectly, I was thinking maybe the file dlpkgfile that I got was corrupt but I am able to unzip it etc. I guess I will just need to wait for Asus to put it out on their site.
Thanks for all the help.
dugout2929 said:
I was able to do this and it worked perfectly, I was thinking maybe the file dlpkgfile that I got was corrupt but I am able to unzip it etc. I guess I will just need to wait for Asus to put it out on their site.
Thanks for all the help.
Click to expand...
Click to collapse
If you think it might be corrupt you could try the one from this post http://forum.xda-developers.com/showthread.php?t=1231635
Flashing the official gingerbread in u8800 its irreversivel process, at least for now.
If you flash it you have to keep it as no way of going back.
If you root it using the only available method, bye bye!
Everytime you reboot the endless bootlooping starts and the only way to stop it is formatting data.
Which means everytime you reboot = bye bye all data and apps etc.
I think is something that its major importance and no one is mentioning this!!!!
I don't know, maybe I've been preaching to deaf ears or something...but...you can re-install the old ROM back, the CWM recovery won't work with the official GB - that much is true - but you will be able to downgrade to an official 2.2.2 (I used the B162) version with the regular update method (at least I was and everything is working just as normal as it used to).
So, irreversible - I don't think so
with the current CWM recovery - it's a no-go
edit: that being said, what works for me, doesn't necessarily work for everyone, so be careful and blame the guy in the mirror -not me, if it doesn't work for you. =)
I think Huawei says wrong here. I flashed 2.3 yesterday. After that, because of the haptic issue I flashed back to official 2.2. Only problem after the 2.2, recovery console had opened. I did factory reset there and phone started without a problem. Then, I had upgraded to 2.3 again. Still haptic don't vibrate. Other than, no problem here. Maybe, I will go back again to 2.2.
Well you are lucky then because you are the only one.
Perhaps what is saying in the official intructions that will be impossible to dowgread after this upgrade won't apply to you.
I have try it with at least 8/9 versions of official release and nothing works!!!!
what 2.2 version is that and you did it after or before rooting?
Have you tried with internal sd? I copied dload folder to internal and started the upgrade process from Storage-Upgrade Firmware. Where did your phone stuck?
Edit: I didn't root my phone. Waiting proper solution. I had used B138.
no, I'm using external SD.
now I'm downloading another official release to try to downgrade using another one...
this time is U8800 V100R001C17B162CUSTC17D001
Druida69 said:
Well you are lucky then because you are the only one.
Perhaps what is saying in the official intructions that will be impossible to dowgread after this upgrade won't apply to you.
I have try it with at least 8/9 versions of official release and nothing works!!!!
Click to expand...
Click to collapse
Well, like I said, what works for me doesn't necessarily work for you.
Anyway, this is what I did and it worked, maybe it can help others.
0. Copy the original B162 ROM ("dload"-folder which has two files, UPDATE.APP AND UPDATE_CUST.APP) to the root of your SDCARD
1. Update to B162 by holding down +- keys while turning on the phone
2. After the first reboot, it's giving error messages for not being able to mount this and that...just ignore it and...
--> Wipe data / factory reset --> remove battery
3. Update the B162 again --> this time everything should go OK, if so, your phone is back to stock B162 and you're ready to use it or update a custom rom (just install Clockwork recovery like you used to and start from there)
The last point (3) may be unnecessary, but I did so just to make sure everything's ok.
Edit: OK, and I meant b162, not b160...
Druida69 said:
no, I'm using external SD.
now I'm downloading another official release to try to downgrade using another one...
this time is U8800 V100R001C17B162CUSTC17D001
Click to expand...
Click to collapse
For me it also works. I have downgrade without any problem and I use to the b 162 version. Now Ian back to oxygen
Sent from my u8800 using XDA App
yes I made it with this B162.
**** this **** I'm going back to custom rom.
No point of using this official release if future customs will use the libs from this one.
Druida69 said:
yes I made it with this B162.
**** this **** I'm going back to custom rom.
No point of using this official release if future customs will use the libs from this one.
Click to expand...
Click to collapse
And then there's the fact that the official gb is still beta, it's not supposed to work perfectly. But as long as the dev team here stays active, I think that I'm gonna stick with custom roms too.
ho my god.
didn't work.
is always booting into recovery
I am stuck here also (
Nothing worked
I tried clockwork recovery - it doesnt get to. It is just rebooting.
I tried with various dload UPDATE.IMG's (GB Overseas, GB orig chinese,B162,B138) nothing is working - stucked in "Step 1/2 Unpacking" window forever.
Anyone has solution for this ?
Two weeks ago I've flashed the U8800Pro version - real mistake
I've started a topic here:
http://forum.xda-developers.com/showthread.php?t=1327715
katu2006 and on the second page flibblesan gave me a method to start my phone working well.
Post #4, #11 and #13.
Maybe this will help you,too?
sbasil said:
Anyway, this is what I did and it worked, maybe it can help others. (...)
Click to expand...
Click to collapse
You sir are a LEGEND. My phone "lives" again! On CM7 again...
manage to install miui.
several versions now up to the newest one.
I noticed on all of them that it mount the SD card when connected to USB but only shows the system files and not allow writing, copy, cut, etc.
Saying that I dont have permission to change the SD
Druida69 said:
Flashing the official gingerbread in u8800 its irreversivel process, at least for now.
If you flash it you have to keep it as no way of going back.
If you root it using the only available method, bye bye!
Everytime you reboot the endless bootlooping starts and the only way to stop it is formatting data.
Which means everytime you reboot = bye bye all data and apps etc.
I think is something that its major importance and no one is mentioning this!!!!
Click to expand...
Click to collapse
I have just flashed with new U8800V100R001C00B517G001(Beta1.0)(Overseas Normal)(Gingerbread) but after flashing I kept waiting for start my phone. I restasted many times but same, then I format data its worked and when restarted again it goes in same condition any help ?
until flash disk is writable and it is - there will always be way to go back to old versions it just files.. like reinstalling windows on your pc.
Since the new Rom is public I have read all posts about it here. Maybe I had lucky, or simple due it without messing with the files.
Yesterday I made the upgrade to the new rom, directly from the last Oxigen version, without downgrade to 2.2. I simply create the dload folder on SD card, put there de update file, boot with +- Power, and chose upgrade from SD card.
After step 2 I reboot the phone a install step 3 upgrade. Everything as installed fine, no boot loops, nothing...
Also the root method decribed in this forum as work on first time.
24 hours after the upgrade, and some reboots to test, I never se the boot loops, and the phone is working well.
The new ROM, even in beta stage, to me is a great improvement.
Well either you were lucky or me and the majority were unlucky.
But issues only start to happens when rooting.
So that you can see it fried me the 1 USB cable. This cable is only good to charge the battery now....
Also, ****ed the device USB storage MOUNT.
I connect it to the computer and the computer sees it as a CD drive not allowing any changes.
Also when press the button to mount the USB on the device it never gets mounted and gives the messages that the SD can now be removed.
So I have put this issue many times but up to the moment no one even reply to help.
Can anyone please help?
I have a Samsung Note 3 SM- n9005 Jellybean 4.3
I successfully rooted the phone about 7 months ago with odin
I tried to run game-cheats I think it was called about 2 months ago and it said it didnt have root privileges and wouldnt find or change the coin values in some games i wanted to play around with. I know i can use modded games and I know how to find "coin/RP etc. value" and change the number that way.
I talked to a technician in a local phone shop and he advised me that the root had not been installed properly. To un-root phone and then re-root it.
I think it was superSU? I had and I pressed the permanent un-root.
I tried to use the same tar file to re-root phone and it boot-looped (SE-android not enforcing caper). which I fixed after searching through the forums for answers
I was very careful to get the correct 4.3 tar file and not the 4.4 file. I have downloaded the file 2 or 3 times and it still bootloops but says PASS.
I have installed CWM.
I have tried to re root phone with Kingo (making sure KIES is turned off), which says phone rooted successfully(but root checker says its not rooted), I then tried framaroot apk, Vroot, rootgenius and another program. (all saying its a tough phone and it cant be rooted)
Why cant the phone be re-rooted?
Has the permanent unroot with superSU done exactly that?
Will getting rid of the bootloop with a recovery tar unroot the phone?
why is odin bootlooping the phone? (I have used the latest odin and I have also tried earlier versions as suggested in some forums)
If I do a factory reset will that be sufficient to allow me to root the phone again?
If I get the official 4.3 quallcom firmware and install that will it let me root the phone again?
if I update to KitKat 4.4 will that let me re-root?
Could I be having troubles because Knox has been tripped?
Im not really worried if I hardbrick the phone, ill just get another one, but im stubborn and I dont really want to let it beat me.
If possible could the reply not be to technical all I really want to do is understand whats happening/what I have done
Then What can I do to re-root the phone? because if what has to be done is to technical it would be easier to get a new phone and start again
mickeyjack01 said:
Can anyone please help?
I have a Samsung Note 3 SM- n9005 Jellybean 4.3
I successfully rooted the phone about 7 months ago with odin
I tried to run game-cheats I think it was called about 2 months ago and it said it didnt have root privileges and wouldnt find or change the coin values in some games i wanted to play around with. I know i can use modded games and I know how to find "coin/RP etc. value" and change the number that way.
I talked to a technician in a local phone shop and he advised me that the root had not been installed properly. To un-root phone and then re-root it.
I think it was superSU? I had and I pressed the permanent un-root.
I tried to use the same tar file to re-root phone and it boot-looped (SE-android not enforcing caper). which I fixed after searching through the forums for answers
I was very careful to get the correct 4.3 tar file and not the 4.4 file. I have downloaded the file 2 or 3 times and it still bootloops but says PASS.
I have installed CWM.
I have tried to re root phone with Kingo (making sure KIES is turned off), which says phone rooted successfully(but root checker says its not rooted), I then tried framaroot apk, Vroot, rootgenius and another program. (all saying its a tough phone and it cant be rooted)
Why cant the phone be re-rooted?
Has the permanent unroot with superSU done exactly that?
Will getting rid of the bootloop with a recovery tar unroot the phone?
why is odin bootlooping the phone? (I have used the latest odin and I have also tried earlier versions as suggested in some forums)
If I do a factory reset will that be sufficient to allow me to root the phone again?
If I get the official 4.3 quallcom firmware and install that will it let me root the phone again?
if I update to KitKat 4.4 will that let me re-root?
Could I be having troubles because Knox has been tripped?
Im not really worried if I hardbrick the phone, ill just get another one, but im stubborn and I dont really want to let it beat me.
If possible could the reply not be to technical all I really want to do is understand whats happening/what I have done
Then What can I do to re-root the phone? because if what has to be done is to technical it would be easier to get a new phone and start again
Click to expand...
Click to collapse
just choose a firmware from sammobile.com
download it
flash it using Odin
boot it normally
flash CF-Autoroot
mickeyjack01 said:
Can anyone please help?
I have a Samsung Note 3 SM- n9005 Jellybean 4.3
I successfully rooted the phone about 7 months ago with odin
I tried to run game-cheats I think it was called about 2 months ago and it said it didnt have root privileges and wouldnt find or change the coin values in some games i wanted to play around with. I know i can use modded games and I know how to find "coin/RP etc. value" and change the number that way.
I talked to a technician in a local phone shop and he advised me that the root had not been installed properly. To un-root phone and then re-root it.
I think it was superSU? I had and I pressed the permanent un-root.
I tried to use the same tar file to re-root phone and it boot-looped (SE-android not enforcing caper). which I fixed after searching through the forums for answers
I was very careful to get the correct 4.3 tar file and not the 4.4 file. I have downloaded the file 2 or 3 times and it still bootloops but says PASS.
I have installed CWM.
I have tried to re root phone with Kingo (making sure KIES is turned off), which says phone rooted successfully(but root checker says its not rooted), I then tried framaroot apk, Vroot, rootgenius and another program. (all saying its a tough phone and it cant be rooted)
Why cant the phone be re-rooted?
Has the permanent unroot with superSU done exactly that?
Will getting rid of the bootloop with a recovery tar unroot the phone?
why is odin bootlooping the phone? (I have used the latest odin and I have also tried earlier versions as suggested in some forums)
If I do a factory reset will that be sufficient to allow me to root the phone again?
If I get the official 4.3 quallcom firmware and install that will it let me root the phone again?
if I update to KitKat 4.4 will that let me re-root?
Could I be having troubles because Knox has been tripped?
Im not really worried if I hardbrick the phone, ill just get another one, but im stubborn and I dont really want to let it beat me.
If possible could the reply not be to technical all I really want to do is understand whats happening/what I have done
Then What can I do to re-root the phone? because if what has to be done is to technical it would be easier to get a new phone and start again
Click to expand...
Click to collapse
Have u tried to update supersu from playstore?
if yes and it is still not rooted, try to flash stock firmware as advise, boot into stock recovery after that and do full wipe/factory reset.
after that u shld be able to root.
pls note wiping in srock recovery will erase all ur internal storage.
Sent from somewhere under the sky, at the corner of this rounded earth.
sammobile seems a ?
hi thanks.
I have tried about 10 times now after opening up an account, to download file from sammobile going to firmware and typing model getting to note 3LTE Telstra model the file wont unzip. What have you got to pay to get a zip that will unzip??? I have just downloaded another zip program both saying errors inside zip
is there any other place that would likely have the telstra file i need?
yes i tried updating SuperSU and it wont update. Reading up on the problem which seems common the answer requires me to copy zip files to sd card and then unzip them inside CWM its now starting to get too technical for me which is why I have started asking you guys questions. I have tried SU update fixer, nothing. and the equivalent for Superuser ,they wont update. Over the last month I have tried uninstalling ,deleting and wiping cache and wiping delvek cache with CWM.
some where inside CWM it said something about press this to root phone what is that for ? or has that to do more with zip files?
and yes I know i can do a factory reset and yesterday i bought an sd card to transfer the game data etc to.
how come using APPMGR111 and APP2sdand they say apps can be transferred to sd card(My sim card) which is much to small to accommodate all the apps but cant be transfered to External card (32 gb card bought yesterday morning) so do I need to do something silly like formatting external SD
Oh, If its important I am only interested in using the phone as a media and game playing device and as such i have turned off the sim card but left it in the phone and transfered the phone number to another simcard and given it to my wife for her S2 which uses a larger card. I just access google play etc through wifi.
also, i have tried using different cables as well as different USB ports, but do you think another computer??? completely. I go back to work next week so anything like that has to be done over the next couple of days while I am home.
And I was told in the shop yesterday when I bought the sd card to tap android version several times because sometimes what you can see (4.3) is different for some reason but it just has a picture of a Jellybean and says 4.3 (the man said here it might say 4.2.1)
will I have to flash stock firmware first? or can i just go strait to factory reset, if I have to go down that road. If so then I wont need to worry about Sammobile and the unzippable file????? I can just do the factory reset strait from CWM?? Or doesnt it work like that??
mickeyjack01 said:
hi thanks.
I have tried about 10 times now after opening up an account, to download file from sammobile going to firmware and typing model getting to note 3LTE Telstra model the file wont unzip. What have you got to pay to get a zip that will unzip??? I have just downloaded another zip program both saying errors inside zip
is there any other place that would likely have the telstra file i need?
yes i tried updating SuperSU and it wont update. Reading up on the problem which seems common the answer requires me to copy zip files to sd card and then unzip them inside CWM its now starting to get too technical for me which is why I have started asking you guys questions. I have tried SU update fixer, nothing. and the equivalent for Superuser ,they wont update. Over the last month I have tried uninstalling ,deleting and wiping cache and wiping delvek cache with CWM.
some where inside CWM it said something about press this to root phone what is that for ? or has that to do more with zip files?
and yes I know i can do a factory reset and yesterday i bought an sd card to transfer the game data etc to.
how come using APPMGR111 and APP2sdand they say apps can be transferred to sd card(My sim card) which is much to small to accommodate all the apps but cant be transfered to External card (32 gb card bought yesterday morning) so do I need to do something silly like formatting external SD
Oh, If its important I am only interested in using the phone as a media and game playing device and as such i have turned off the sim card but left it in the phone and transfered the phone number to another simcard and given it to my wife for her S2 which uses a larger card. I just access google play etc through wifi.
also, i have tried using different cables as well as different USB ports, but do you think another computer??? completely. I go back to work next week so anything like that has to be done over the next couple of days while I am home.
And I was told in the shop yesterday when I bought the sd card to tap android version several times because sometimes what you can see (4.3) is different for some reason but it just has a picture of a Jellybean and says 4.3 (the man said here it might say 4.2.1)
will I have to flash stock firmware first? or can i just go strait to factory reset, if I have to go down that road. If so then I wont need to worry about Sammobile and the unzippable file????? I can just do the factory reset strait from CWM?? Or doesnt it work like that??
Click to expand...
Click to collapse
the zip file from samfirmware.com is not flashable by cwm.
u have to unzip using any of the zip program, till u got the tar or md5 (i forgot ), then flash it from odin. there's instructions on the download page as well.
u can't unzip from cwm.
If u have tried to unzip from any pc software and still can't unzip, means u got a corrupted download.
the factory reset in cwm is different from the stock recovery.
Sent from somewhere under the sky, at the corner of this rounded earth.
sorry missunderstanding
didnt try to use CWM for flashing am using Odin but zip file wont open to access tar file for odin.
That is what I thought the file I am trying to open is corrupted.My question was, seeing as how the file is corrupted is there anywhere else that I can get the file other than sammobile?
mmmm ok thanks then please just for interest what is the root button for inside CWM?
Sorry my questions do jump around a bit
I also read that nobody has found a way to access the built in recovery mode of note smn9005
that is why we have to use programs like CWM-recovery??
the other coment about factory reset. So georgesmh comment about flashing cf-autoroot. Seeing as how file is corrupted and if I cant get a copy from another source. all I have to do to factory reset is hit that particular button inside CWM? is that correct?
and i think I have an answer for my other question about the sd card the answer is No I cant save the games to the sd card I have lost them if I do a fActory reset. The only way to seems to be is to have a phone that is already rooted to use titanium something or other.
Thats alright really I had fun with the games before and it would be fun to do it again.
doing a factory reset is there any chance I can brick the phone?
mickeyjack01 said:
sorry missunderstanding
didnt try to use CWM for flashing am using Odin but zip file wont open to access tar file for odin.
That is what I thought the file I am trying to open is corrupted.My question was, seeing as how the file is corrupted is there anywhere else that I can get the file other than sammobile?
Click to expand...
Click to collapse
you can try from here. but I don't think the thread is updated to the latest one.
mickeyjack01 said:
mmmm ok thanks then please just for interest what is the root button for inside CWM?
Click to expand...
Click to collapse
this one I don't understand
but, to root with CF-autoroot, you don't need CWM. you only need the correct file for your device and for your firmware from CF-autoroot thread, and flash it through ODIN PC at PDA / AP tab in device download mode.
mickeyjack01 said:
Sorry my questions do jump around a bit
I also read that nobody has found a way to access the built in recovery mode of note smn9005
that is why we have to use programs like CWM-recovery??
Click to expand...
Click to collapse
this one also I'm not quite understand your question
what do you mean by access the built in recovery ?
in N9005, stock (built in) recovery is used for doing factory reset (mainly and mostly), to have a clean internal storage, you have to do factory reset (full wiping - system/data/cache) from stock recovery.
Stock recovery can be used to flash zip files as well, BUT, only those are being digitally signed by Samsung can be flashed here. Otherwise, it won't flash.
Most of custom-ROM, custom-Kernel, custom-MOD, custom-Themes are not digitally signed by Samsung, because this is a 3rd party developers' products (here in XDA, and maybe from other forums). Therefore, to flash these type of zip files, you will need a custom recovery (CWM, Philz touch CWM, or TWRP).
mickeyjack01 said:
the other coment about factory reset. So georgesmh comment about flashing cf-autoroot. Seeing as how file is corrupted and if I cant get a copy from another source. all I have to do to factory reset is hit that particular button inside CWM? is that correct?
Click to expand...
Click to collapse
sorry, this one i don't understand what you mean at all
mickeyjack01 said:
and i think I have an answer for my other question about the sd card the answer is No I cant save the games to the sd card I have lost them if I do a fActory reset. The only way to seems to be is to have a phone that is already rooted to use titanium something or other.
Click to expand...
Click to collapse
Factory reset, in builtin (stock) recovery, WON'T delete anything on your external SD card. ONLY your internal storage
So if you need a backup of anything, do the one you store inside internal storage.
mickeyjack01 said:
Thats alright really I had fun with the games before and it would be fun to do it again.
doing a factory reset is there any chance I can brick the phone?
Click to expand...
Click to collapse
If you flashed a correct firmware for your device, and doin the factory reset from inside stock recovery, I never heard got ppl can brick the phone by doing this.
This brick thing only happen earlier on Note 1 (due to emmc brick bugs), but not on Note 2 and note 3.
I might be misunderstood of your questions
Sorry if I ever did that
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
vsriram92 said:
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
Click to expand...
Click to collapse
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
So nice of their support site to be down...
tomlogan1 said:
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
Click to expand...
Click to collapse
Instructions > https://forum.xda-developers.com/honor-5x/how-to/guide-force-installing-stock-ota-t3502874
What are the bug fixes???
Are there any new features???
I am currently on custom ROM and would like to know the answers to these questions to see if it's worth it to go back to stock rom
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
m0ndul said:
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
Click to expand...
Click to collapse
So much miss information .. no one bothers to find the truth
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
animeme said:
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
Click to expand...
Click to collapse
Link below or install the Huawei Firmware Finder form the Google Play Store and set it up to get OTA files in settings.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=kiw-l24
deleted
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
What he said.
I'm hoping it's nothing more than a VoLTE update that LOS maintainers warn against anyway, if there's actually no one to further explain what it is
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
my kiwi-L24 got re-flashed today, it is weird that this B351 update is no longer available from B331's update check
searched on internet, there is news about "honor 5c" getting a B351 nougat update
This came up on one of the 5X's that I have. Updated and forgot to put back stock recovery. Don't be like me and forget to do that. Now it won't work properly and I can't get to start any apps to try and fix it. I can put back TWRP and wipe it, but I don't want to lose my data. I also have that problem now where it keeps telling that the SD card is corrupted. I backed up the data and scrubbed the card in the phone but it keeps coming back with the same thing.
If someone did an actual successful update properly (with stock recovery) then please update and say if everything is working. If not, I'm going to have to find some way to backup the data and then scrub it.
*EDIT*
I believe something like this happened to me before. I was on B151 and went to B331 with TWRP installed by accident. What happened was that the OS was still running EMUI 3.1 but the build was saying B331. After fighting with it (and community support) I managed to get it to B331 fully and EMUI 4.0 - since then and a few custom ROMs I'm back on B151 EMUI 3.1 due to stability. Games and some apps just didn't work on the new one. The second phone was on B331 fully though - then I made the same mistake and it went to B351. This time though, the phone seems screwed. No apps will load. I can get into settings and the file manager, but no Titanium Backup and no Flashify. Going to put back TWRP and try to flash GAPPS and see if it will help me get into Play Store. From there I'll try to reinstall Flashify and flash the ZIP of the update. Will post back once done.
*EDIT*
Well that didn't work. Even after going back and trying to root the device again - then checking the option for it to not detect the dirty flash - still didn't work. Kept complaining that stock apps are already present.
I'm going to try and get some files off the device, but keep having issues. Not sure why. May just have to scrub. Will update again.
*EDIT*
With TWRP on I used "ADB PULL" to get certain files from the root system which I couldn't access otherwise for some reason. Then copied the other things (photos and such) and will now be using the UPDATE.APP to get it working. For this I formatted the SD from within TWRP and created the DLOAD folder (with no caps - so that's dload - but I'm not sure if it matters) and will be copying the UPDATE.APP. Not sure which version yet, because there was some problem with one I had downloaded before. So I need to double-check and re-download.
*EDIT*
So I've successfully flashed the UPDATE.APP from the SD card (same one the phone was claiming is corrupted). Just for reference, here is the file information and hashes.
File Name: Honor 5X_Firmware_KIW-L24_Android 6.0.1_EMUI 4.0_C567D003_United States.zip
Size: 1762266487 bytes
ADLER32: 27cb0c31
CRC32: 1d9379b9
MD2: 6517c34dc9bac0cd8680e3c4fd09d8d9
MD4: 4a803765c0ed54cb5d6853a9f365cd3b
MD5: 04f60b067d546ad71f556e44a7934dc7
SHA1: 8d2718568ac6509a40c95e42857d400395eb88d2
SHA256: 82975923172b3800d3f09f76691f2a694ab98110e3f909084a02bd566448386f
SHA384: da53b58b8e20395595590fd0cec30e56fa6a62e638ec53e46a74ebf58d051fdd7576602019bd3130ca5c00cc432715a0
SHA512: 806e0e8969c293ca8b497a786699ee306352ad6ef434552f2d23decff8a5279c7fd605e046c13f11c2f87947f5a2bdf23d78fdec6263661e68f023fd72bf4381
RIPEMD128: 9d963e5d51c9df9554fa3422da84dd27
RIPEMD160: a1e5b8f08b65dd2bb08e04d62db270ad8f4cf51a
TIGER128: 66fb4e4e4ce11cb30626aea807355f83
TIGER160: 66fb4e4e4ce11cb30626aea807355f8345f1dd79
TIGER192: 66fb4e4e4ce11cb30626aea807355f8345f1dd79dbb39488
GOST: 93774537f6ca49d4406f9d3a0316d014e1e099b34fc1cd9b968dacc870700827
The file name may be different, but as long as you got the right one you should be OK. If you have issues when copied to an SD card - verify that the file on the SD card has the correct hashes. To make it faster use CRC32. For more surety, use MD5. You can get a tool like WinMD5 to check. It's free.
So now that it's done, I'm going to set it up as a new phone and wait to see if the update comes back on. If it does, I'll get it down and upload the B351 recovery. After that I'll need to remember that I have to put back the stock recovery before running any updates. Flashify FTW.
BTW - during the initial setup after connecting to wireless it came back with the update. Pics to follow.
Files will be uploaded here: https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
*EDIT*
So the files are uploading to the folder. The screenshot is attached. Had one issue where after the update I couldn't get back into the phone. Had to wipe/factory reset. I've used FASTBOOT BOOT TWRP.IMG to take the backups of the BOOT and RECOVERY. Hopefully one of the gurus can use that and give the IMG files. I'm going to try root and get FLASHIFY to backup the stock recovery and add to the folder.
khat17 said:
This came up on one of the 5X's that I have...............
Click to expand...
Click to collapse
I don't really like to do double replies, but I guess for ease of finding the info it's better this way. Unless a mod thinks differently and wants to merge all the info.
Google Drive Link With Files
https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
This contains TWRP backups of the recovery and boot images. There's also a file called KIW-L24-B351 which was created with Flashify. I assume you can add the IMG extension to it and flash as needed.
Basically I had this update run on another phone (my wife's) and it messed with the phone due to the recovery being TWRP and not stock. My fault - forgot to do that before handing the phone back to her. I believe it happened to me before but it never messed up the phone this way. Nothing would work except core apps like settings and the stock file manager. The Play Store wouldn't even open.
Anyways - back to factory with UPDATE.APP then run the automatic update from an OTA update on wireless, then FASTBOOT BOOT TWRP.IMG and capture the backups. Then flash SuperSU to get root. Then Flashify. Files are uploaded for your convenience.
Warning that during the initial OTA it took a while. And after it was done I couldn't get into the phone with the password. Had to factory wipe/reset again and setup again. Disable passwords just in case I guess. Hope this helps others - have fun.
No major differences. I haven't really used the stock OS6 but some things look a little different. Nothing major. Will see when she's using it if it lags or has improved memory and such. Not sure if I'll be able to test with apps that wouldn't run previously for me, but will see. Tested with TransDrone and it failed. Once SeedBox information is loaded it still crashes. Only happens on OS6 so I'm sticking with OS5 on mine. Does not happen with custom roms however (from what I recall - would have to check back).
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
raulpcamara said:
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
Click to expand...
Click to collapse
Follow this video if don't know how to flash back stock recovery through adb. Then take a look at those threads how to downgrade, here, here, here. Hope it helps.
bluesky299 said:
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
Click to expand...
Click to collapse
Same here.
It had been too many months of the Honor 5X in the closet so i almost lost track what to do but what i did was revert all the way back to Stock ROM (had to flash an extracted/saved Recovery.IMG) and then do the UPDATE.APP from Dload complete and repeat on up to the current B351.
Of course lost Root but when ready can add that back too.
Yes the Honor 5X runs much smoother now than before plus that Battery Drain issue (Remember That?) where we had to dig deep to change 4 to 0 i think, well Battery Life is also greatly improved on mine.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
I tried to update as the previous user did using TWRP and got the corrupted SD card message. I then tried to go back to stock ROM. Went into bootloop.
Been having a hell of a time getting anything to work properly since.
Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Neskobar said:
Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Click to expand...
Click to collapse
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Choose an username... said:
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Click to expand...
Click to collapse
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Neskobar said:
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Click to expand...
Click to collapse
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
raystef66 said:
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
Click to expand...
Click to collapse
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Neskobar said:
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Click to expand...
Click to collapse
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
raystef66 said:
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
Click to expand...
Click to collapse
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
edit - I renamed the zip to "update.up" and couldn't get that to work either. It's not detected in the update section of settings, and I still get the same "Sorry, you can't sdcard upgrade" message.
edit #2 - I tried naming it to "update.up.zip" and it detected it this time, trying to run the update now.
Neskobar said:
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up, when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
Click to expand...
Click to collapse
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
raystef66 said:
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
Click to expand...
Click to collapse
Ah, I should have mentioned that. This is the message I'm getting when I try that:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Click to expand...
Click to collapse
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Neskobar said:
Ah, I should have mentioned that. This is the message I'm getting when I try that:
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Click to expand...
Click to collapse
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
raystef66 said:
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
Click to expand...
Click to collapse
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
raystef66 said:
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
Click to expand...
Click to collapse
Ok, I attached it to this post, hope it works.
Neskobar said:
Ok, I attached it to this post, hope it works.
Click to expand...
Click to collapse
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
raystef66 said:
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Click to expand...
Click to collapse
Yes, that's what I was concerned about. The very first update i tried to install was N-B09, and everything else has been an older update after that, so maybe it won't overwrite the newer files, or something? Or possibly something else went wrong in the first update, so everything else just wouldn't work because of that?
I'm putting N-B01 onto my SD card right now, so I'll test that, and if it doesn't work I'll wipe the phone and start again. If I do need to wipe the phone, however, which update would you recommend trying first? N-B09? That might confirm if it was just bad luck on the first try, or whatever.
RobboW said:
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Click to expand...
Click to collapse
Agreed, that sounds like a possibility to me. I'll probably end up wiping and starting over.
Choose an username... said:
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
Click to expand...
Click to collapse
Yes the tab autocomplete works on the "u" of update.zip and "o" of ota.zip, when I tried both. I have to admit, I was quite excited to see your suggestion there, as I thought that would be a really easy way to confirm if something isn't right with adb, but never mind.
I still don't understand why it gives me this error then, though: * cannot read 'update.zip' *.
ramnkc said:
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
Click to expand...
Click to collapse
Thanks for the suggestion, and yes, I did confirm that I renamed the right zip file. That would have been easy thing to fix though, sadly.
edit - I tried the same adb commands with windows powershell too, and got exactly the same error messages.
What ROM was on it before you flashed B09?
Updating to N-B01 worked! I've no idea why this happened the way it did, nor why adb didn't work for sideloading, but I'm really glad that it finally worked.
The order of events:
1) Installed N-B09 via transfer to SD using the android updater, no difference in android version, but appeared in update history.
2) Installed MM-B11, same as above.
3) Tried various methods of installing MM-B11, including:
- SD transfer
- recovery mode SD update (which the phone wouldn't let me do, saying, "Sorry, you can't sdcard upgrade").
- ADB sideload (which never worked even slightly. I always got the message, * cannot read 'update.zip'/'ota.zip'/'update.up.zip' *)
- Tried the above methods with variously named zip files, including "update, ota, and update.up".
- Tried the above methods, but wiping the cache in between processes.4) Installed N-B01 via transfer to SD using the android updater. This time the process took a lot longer and after rebooting the phone, went through the process of optimizing apps, which it had never done before.
Ok, I think that's everything.
The only theory I can come up with is that: Something (I have no idea what, though) went wrong with the first update attempt and every subsequent attempt to update to an older version didn't work because it didn't want to overwrite newer android version files? That doesn't seem quite right to me, though, as I would assume that whatever is in the update.zip would just overwrite everything as standard, because the assumption would always be that these files are newer than the existing ones.
What would you recommend that I do next? Should I try to push through the latest N update now, then? Has this outcome helped you figure out what the problem was/is?
Whatever the case, I'm happy to finally get an update working. Thanks very much for all your help and suggestions, guys. It was much appreciated!