Related
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
I'm having the exact same problem with a GT-i9020 so would be interested in any help on this!
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Highl1 said:
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Click to expand...
Click to collapse
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
I'll wait for your link and instructions, it's obvious that I am doing something wrong
Thanks mate!
RANDYRKELLY said:
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
But I have stock recovery and can't copy anything to internal memory, since my phone doesn't boot
Highl1 said:
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
Click to expand...
Click to collapse
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
surdu_petru said:
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
Click to expand...
Click to collapse
Same thing mate, I ran it, click two times in console, can't unlock the bootloader, I always get stuck on it
Trying to update the drivers for Nexus S : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
and after that try to run.bat...Good luck!
I'll try today, but my problem is that adb cannot find the device, fastboot can
I would try downloading the full OTA from this thread, rename it to update.zip (for easy typing), place it in a directory where you can run fastboot, then use the command:
Code:
fastboot update update.zip
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Is the problem solved？
szk5230 said:
Is the problem solved？
Click to expand...
Click to collapse
Not so far, I'm still having trouble with the phone, and no solution so far helped
Highl1 said:
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Click to expand...
Click to collapse
Sorry my bad, haven't tried that before either...
If it bugs you the bootloader isn't unlcoked before flashing can't you just use
fastboot oem unlock
then commence with flashing your stock image?
Edit - Nevermind...I see you tried that.
any other suggestion? I'm out of ideas
I had this problem in December. I tried everything you tried without any luck so eventually took it back for warranty repair. Unfortunately I had some water damage from 9 months before so they wouldn't touch it. Luckily I got it replaced on my phone insurance but they said it couldn't repaired.
As far as I know it's a hardware fault. With CWM it looked like I could transfer files into the sd but they would disappear! I was able to use Fastboot and Odin but no joy. I had the same errors when trying to apply update using fastboot and never found answers about the "missing" files.
Sorry to come with bad news and good luck! I'm worried it'll happen to my replacement handset so keen to know if you resolve it.
I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.
did you install any mods, kernels, change any files? if so its been documented all over the forums.
No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.
danielvago said:
No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.
Click to expand...
Click to collapse
It didn't work. I have no idea what to do, can I sideload the APK?
Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).
danielvago said:
It didn't work. I have no idea what to do, can I sideload the APK?
Click to expand...
Click to collapse
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
Theory said:
Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).
Click to expand...
Click to collapse
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.
wantabe said:
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.
Click to expand...
Click to collapse
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
What is the error when the OTA fails?
Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data
try incremental install
danielvago said:
I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.
Click to expand...
Click to collapse
try sideloading 4.4.1 first. .and then sideload 4.4.2 after that. see if that works.
EddyOS said:
Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data
Click to expand...
Click to collapse
I just updated a new 2012 N7 from 4.1 to 4.4.2 and I couldn't get removing the -w flag to work. I think the script needs more editing than just removing the -w part. Something new I had never tried before which I actually don't personally have much use for because it still flashes the stock recovery over a custom recovery if you are using one. Anyway.. flashing the bootloader and radio separately and then flashing the update zip with "fastboot update image-hammerhead-kot49h.zip" would be a little bit of a shortcut versus flashing ALL of the images and you don't lose data.
Never had an issue myself, but I always prefer to flash each image manually one at a time
EddyOS said:
Never had an issue myself, but I always prefer to flash each image manually one at a time
Click to expand...
Click to collapse
I've always flashed each image separately also, I was just being lazy and experimenting. Removing the -w from the .bat and/or the .sh wouldn't work for me.
---------- Post added at 10:33 AM ---------- Previous post was at 10:27 AM ----------
danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.
wantabe said:
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.
Click to expand...
Click to collapse
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?
danielvago said:
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?
Click to expand...
Click to collapse
Your path to adb isn't correct. Put the zip file in the same folder as adb
jd1639 said:
Your path to adb isn't correct. Put the zip file in the same folder as adb
Click to expand...
Click to collapse
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.
danielvago said:
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.
Click to expand...
Click to collapse
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something
jd1639 said:
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something
Click to expand...
Click to collapse
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?
danielvago said:
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?
Click to expand...
Click to collapse
Ok, so you're doing an adb sideload while in recovery?
jd1639 said:
Ok, so you're doing an adb sideload while in recovery?
Click to expand...
Click to collapse
Yes.
Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance
drunken monkey said:
Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance
Click to expand...
Click to collapse
Are you rooted or having custom kernel?
kaushikd said:
Are you rooted or having custom kernel?
Click to expand...
Click to collapse
I'm currently running stock recovery, stock os rooted and unlocked bootloader
I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.
drunken monkey said:
I'm currently running stock recovery, stock os rooted and unlocked bootloader
Click to expand...
Click to collapse
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.
I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img
So while sideloading it should I unroot as well?
jsgraphicart said:
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.
Click to expand...
Click to collapse
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?
drunken monkey said:
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?
Click to expand...
Click to collapse
That correct
Sent from my Nexus 5 using XDA Free mobile app
pauleyc said:
I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img
Click to expand...
Click to collapse
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.
jrronimo said:
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.
Click to expand...
Click to collapse
It won't cause any data loss. It's about the only way to get the ota to work. But in your case, since you have twrp you should also flash the stock recovery.img
Sent from my Nexus 5 using XDA Free mobile app
No data loss (well, apart from root) if you flash just the radio, system and boot images. Worked great for me.
Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?
jrronimo said:
Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?
Click to expand...
Click to collapse
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Good thing I didn't get past this step -- I had downloaded the wrong factory image. D: That'll explain things a bit...
---------- Post added at 02:13 PM ---------- Previous post was at 01:54 PM ----------
Alrighty! New problem: After the phone boots, I get the battery and signal icons in the top right, but a black screen otherwise. If I hit the power button to put it in sleep mode and then hit the power button again, I get a quick flash of the "Welcome to Android, select your language" screen. Any pro-tips?
If I have to set up from scratch, it's no big deal. Most of the important stuff should be backed up; it'd just be annoying. All that Desert Golfing progress!!!
Finally managed to get around it. Ended up updating TWRP and re-flashing most of the .imgs a bunch, then using TWRP to first let me back up data to my computer and then wipe partitions. I'm on 5.0.1 again.
Welp, that was painful, haha. I'm sure I did something wrong leading into this, but I'm not sure what that was...
If i just flash the whole Firmware that i downloaded from Google, will i be able to flash it and loose root?
I am OK with loosing root and beeing back to stock.
At this moment i have Lolipop 5.0 that is rooted with Chainfire.
I was running rooted stock 5.0 with TWRP and had already flashed the 5.0.1 radio, so I just fastboot flashed the 5.0.1 system.img and rerooted. All is well so far.
jd1639 said:
That correct
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So if I unroot and then sideload it will I loose all my data ?
P.s I'll be rooting it back immediately after I get 5.1
So is there any way which can avoid a data loss?
I still have a doubt, I saw rootjunky's video in which he sideload 5.1 to his nexus 7 using nrt..
Even I followed the same method but it didn't succeed for me
pauleyc said:
I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.
Click to expand...
Click to collapse
So after flashing your stock kernal and stock recovery did the sideload work.. I mean that it didn't get stuck at the 61% mark?
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Edit: My issue has been solved. Flashing the Full OTA.zip file will install KitKat over Lollipop. No need to manually flash each file through fastboot. I wish guides would tell you that instead.
BlackDave said:
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Click to expand...
Click to collapse
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Keithn said:
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Click to expand...
Click to collapse
Those are the same files as the ones I downloaded in the other thread.
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Your best bet might just be to try getting a full OTA and flashing it through cwm or something. I'll try with mine when I have some time to backup and flash, probably later tomorrow. If I find anything out I'll post.
Sent from my SHIELD Tablet
BlackDave said:
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Click to expand...
Click to collapse
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Iams1002 said:
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Click to expand...
Click to collapse
No I wipped internal data since I keep everything on external and it still didn't work.
Keithn said:
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
Click to expand...
Click to collapse
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
BlackDave said:
No I wipped internal data since I keep everything on external and it still didn't work.
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
Click to expand...
Click to collapse
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Keithn said:
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Click to expand...
Click to collapse
I flashed the 1.2.1 OTA update and it worked. The first time I tried, I did using the TWRP recovery but for some reason, that recovery fails to flash OTAs, so I went with CWM and flashed the 2.1 update and all worked again. After a while, I got tired of all the issues lollipop gave me so that's why I tried following that guide to downgrade.
In the end, using CWM and flashing the OTA is the best way to go. Thank you all for you help.
Hi Everyone!
Because of having issues i can´t fix on my OnePlus, i´m finally asking for some professional help here, as it´s getting more and more complicated and i don´t want to ruin my phone.
What was my plan?
Installing CM11S 44S on my OPO, which had the 05Q Version as factory setting.
Also i wanted to install a franco kernel.
I hoped, if i do both steps successfully, my OPO will have a good battery life (44S seemed to be the most efficient version, according to some forums).
What did i do so far?
First i set up an adb backup for my data, but not for the OS. However, i installed SDK plus tools and drivers.
Next step was installing a new recovery, which is able to flash a new version of CM11S, so i set up TWRP with fastboot, which means my device is "unlocked" now.
Everything worked well so far, i also made an backup in TWRP.
The problem:
I wanted to reboot my OPO at some point and TWRP asked me for rooting my device. Accidentally i swiped over so it started rooting process, but i didn´t want to root it, so i immediately shut the device down.
By now TWRP recovery/fastboot is working, but my OS 05Q is lost and i can´t install a new ROM because im getting the Report:
--
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
Error flashing zip /<path to .zip file>
--
Can anyone help me to get 05Q back or the 44S with the franco kernel?
I know there might be some other threads that deal with similar problems, but actually none of them helped me so far. For example: do i need a fastboot image or signed flashable zips (which i have)? In which order do i install the kernel and the ROM?
Some Information:
I can access my device via fastboot and my OPO is also shown as a adb device on my MAC.
When starting in TWRP, i can also access the device in USB Mode, transfering files is also possible.
I´m not really competent with android modding or programming, so i will need some noob-friendly answers, but i bet you guys know how to help me out here.
Thank you very much for your help, i really don´t know what to do anymore.
EDIT:
I found out how to place a md5 file to the referring version, but it still sais: MD5 does not match.
I´m so done with it right now that i wish i had my OPO back as it was few days ago.
Well, i cant really help here as i have not face this problem but ur mistake was that u Immediately shut the device down the moment it was installing root. It may have corrupted the partitions of the phone and left it at that state, so maybe restoring the partitions of that section may help. Like i said im not knowledgeable about this
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Thyrix said:
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Click to expand...
Click to collapse
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Heisenberg said:
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Click to expand...
Click to collapse
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Thyrix said:
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Click to expand...
Click to collapse
You need the fastboot images.
Heisenberg said:
You need the fastboot images.
Click to expand...
Click to collapse
Got stuck at step 2: It Terminal said error: cannot determine image filename for sbl1.mbn - although the name is correct and the file is in the correct folder :/
EDIT:
Fixed it, forgot to type sbl1 2 times, im sorry
And it worked, thank you sooooo much!!!