Can't go back to stock on Nexus 4 (4.2.2)! - Nexus 4 Q&A, Help & Troubleshooting

Hi, so today I was trying to go back to stock, so I tried to use the Nexus Root Tookit and my phone was on and working so I used the Flash Stock + Unroot in Device is on/Normal and I tried to install the Android version 4.3.0 build JWR66V so I downloaded it and then used it and the program sent my phone into bootloader mode and the list of commands showed up and it said this:
Flash Stock + Unroot...
sending 'bootloader' <2201 KB>...
OKAY [0.073s]
writing 'bootloader'...
OKAY [0.305s]
finished. total time: 0.380s
rebooting into bootloader...
OKAY [0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
Bootloader Version...: MAKOZ20i
Baseband Version....: M9615A-CEFWMAZM-2.0.1700.48
Serial Number..........: 04c2f29fcf178bb2
checking product...
OKAY [0.002s]
checking version-bootloader...
OKAY [0.002s]
checking version-baseband...
FAILED
Device version-baseband is 'M9615A-CEFWMAZM-2.0.1700.48'
Update requieres 'M9615A-CEFWMAZM-2.0.1700.84'
finished. total time: 0.0114s
My phone's on stock 4.22 JDQ39 and rooted and with TWRP v 2.5.0.0! Can someone please help me!

The error you are getting afterwards is telling you the solution.
Device version-baseband is 'M9615A-CEFWMAZM-2.0.1700.48'
Update requires 'M9615A-CEFWMAZM-2.0.1700.84'
The package is looking for a newer baseband. To solve this just flash the latest radio.img. You can find that in the Google factory image packages on their site. Then try flashing stock again.

edited

https://developers.google.com/android/nexus/images#occam

Okay, this is a very common problem. You can.just click "force flash" and it should work
Sent from my Nexus 4 using Tapatalk 2

Related

[M200][REF] All OTA and Available Full ROM Packages

---------------------------------------------------------------------------
I HAVE CEASED UPDATING THIS THEAD.
The old information contained below will remain for posterity, but will no longer be updated. From this point forward, all updates to this information will be found at http://www.randomphantasmagoria.com/firmware/nexus-s
---------------------------------------------------------------------------
Below is a list of all available OTA and full ROM packages for the Nexus S, model M200.
THIS IS FOR M200 ONLY. IF YOU HAVE ANOTHER VARIANT, PLEASE FIND THE THREAD FOR YOUR VARIANT.
Typical disclaimer where I tell you that all of this stuff is at your own risk and I'm not responsible if you mess up your phone, yadda yadda.
These updates are 100% stock and are NOT rooted.
HOW TO FLASH
I'm not giving instructions on how to flash ZIP files. If you don't know how to do that, you probably shouldn't be looking for stuff in this thread. There are plenty of threads on how to flash zips through recovery. Do a little reading before proceeding.
The recovery-flashable full ROM packages will only flash if your phone has no ROM, any custom ROM, or a stock ROM that's older than the version you're trying to flash. For instance, the 2.3.4 full ROM package will flash over the stock 2.3.3 ROM, but not over the stock 2.3.6 ROM.
With fastboot images, you can flash any version over any other version.
WHAT HAPPENS IF I GET AN ERROR WHILE FLASHING?
If you get an error flashing a recovery-flashable full ROM package, it means that you are running a stock ROM that's newer than the version you're trying to flash. If you're trying to downgrade, then you must install ClockworkMod recovery, then wipe system, boot, data, cache, and Dalvik cache. You will then be able to flash the older version. Optionally, you can also flash fastboot images of a version older than the version you're trying to flash.
If you get an error flashing an incremental update, it means one of four things. Either you don't have an M200, you aren't running a stock ROM, you have changed something with your stock ROM (this includes build.prop changes, radio or bootloader changes as well), or you're running Android 4.X and trying to update manually. These incremental updates only work if you are running a completely, perfectly stock ROM exactly the way Google provides it, with the right radio and the right bootloader. There are no exceptions to this rule. Furthermore, Android 4.X ROMs can no longer be updated manually in stock recovery. See below.
A NOTE ABOUT ANDROID 4.X OTAs
Beginning with Ice Cream Sandwich, Google has made a change to stock recovery that prevents you from flashing future OTA updates manually. Instead you are now required to wait for the OTA notification on your phone and then tap "Reboot and Install."
If this pisses you off, you have the option of unlocking your bootloader, installing either a stock Gingerbread recovery or ClockworkMod recovery, and then flashing the OTA updates manually.
LATEST VERSION
The latest Android version available for M200 is Gingerbread version 2.3.6, build GRK39F.
BUILD REFERENCE
GRI54 - Android 2.3.3
GRJ22 - Android 2.3.4
GRK39F - Android 2.3.6
FULL ROMS
FASTBOOT IMAGES
If you're comfortable with fastboot, you can flash these images to return your phone back to raw stock.
Generally the best way to do this is to perform the following steps:
Put all six fastboot images in one folder, unlock your bootloader, perform the fastboot flashes, then lock the bootloader:
fastboot oem unlock
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
FLASHING FASTBOOT IMAGES WILL ERASE ALL OF YOUR PHONE'S DATA AND WILL RETURN YOU TO A FACTORY STOCK, UNROOTED STATE.
Android 2.3.6/GRK39F/KRKC1 Radio/KA3 Bootloader
Official factory fastboot images, must be flashed using fastboot on an unlocked bootloader. Contains recovery, radio, and bootloader.
THESE IMAGES MUST BE FLASHED USING BOOTLOADER VERSION I9020XXKA3
RECOVERY-FLASHABLE ROMS
Android 2.3.4/GRJ22/KRKC1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Still need ROMs for:
Android 2.3.3/GRI54/KRKB3 Radio/KA3 Bootloader
Android 2.3.6/GRK39F/KRKC1 Radio/KA3 Bootloader
INCREMENTAL UPDATES
The links provided here are to Google's official update package for each version. Sometimes Google provides a small incremental update package for upgrading between versions, other times they just provide full ROM packages for bigger version upgrades. For instance, Google pushed a small incremental update to upgrade from 2.3.4 to 2.3.6. If your phone was running 2.3.3, there is no 2.3.3 to 2.3.6 incremental update, so Google would push the 2.3.6 full ROM package.
Android 2.3.3 (Build GRI54/KRKB3 Radio/KA3 Bootloader)
2.3.3 -> 2.3.4
Android 2.3.4 (Build GRJ22/KRKC1 Radio/KA3 Bootloader)
2.3.4 -> 2.3.6
This does not mention ICS for the Korean Nexus S. Is that because it's not available or supported, yet? Are these only "official" ROMs?
I've been scanning these pages for an hour, and I cannot find a clear, simple answer to whether or not I can get ICS working on my Korean SHW-M200.
Frustrating.
Why doesn't XDA just offer upgrades as a service? Hell, I'll pay someone 10 bucks to just do it and get it over with, ffs.
abundantmind said:
This does not mention ICS for the Korean Nexus S. Is that because it's not available or supported, yet? Are these only "official" ROMs?
I've been scanning these pages for an hour, and I cannot find a clear, simple answer to whether or not I can get ICS working on my Korean SHW-M200.
Frustrating.
Why doesn't XDA just offer upgrades as a service? Hell, I'll pay someone 10 bucks to just do it and get it over with, ffs.
Click to expand...
Click to collapse
No. It isn't available yet.
Sent from my Xoom using Tapatalk
oldblue910 said:
No. It isn't available yet.
Click to expand...
Click to collapse
What I'm trying to find out is if there is an ics ROM that will work on my phone. If I have to wait for KT to issue an official version of ics OTA, then I'll be waiting for another year...possibly forever. Where's the fun in that?
Surely, somebody must be working on this.
abundantmind said:
What I'm trying to find out is if there is an ics ROM that will work on my phone. If I have to wait for KT to issue an official version of ics OTA, then I'll be waiting for another year...possibly forever. Where's the fun in that?
Surely, somebody must be working on this.
Click to expand...
Click to collapse
Dude, just use those ics roms in the Nexus S development section. Every rom and kernels work on M200 varient.
Sent from my Nexus S using Tapatalk
no they don't, E: signature verification fail everytime
edit: still on 2.3.4 can't get beyond it without having to flash cwm, which i dont want to do
rorio82 said:
no they don't, E: signature verification fail everytime
edit: still on 2.3.4 can't get beyond it without having to flash cwm, which i dont want to do
Click to expand...
Click to collapse
whats ur nexus s model?
I have updated the original post with some new notes and also added the 2.3.6/GRK39F fastboot images for M200.
Is is possible to flash another Stock ROM to get ICS?
Is there a tutorial for getting ICS to the M200? I just installed CyanogenMod 9 on my German Galaxy S and it was a piece of cake compared to the SHW-M200
I tried to follow this guide, but when I try to flash the herring.img (step 5), I just get an Android standing before a big warning sign.
Code:
$ ./fastboot flash recovery ~/Downloads/recovery-clockwork-herring.img
< waiting for device >
but unfortunately, you can use i9020/i9023 ICS package in M200 without any problems at all...
Well guys the Nexus S has been an amazing phone for me, but I have moved on to the Galaxy Nexus. I will still be keeping these stock images threads up to date for the remainder of the Nexus S' OTA life cycle. I know these threads have helped a lot of people so it's the least I can do to help a community of people who are so passionate about such a great device. Cheers!
Sent from my Xoom using Tapatalk
---------------------------------------------------------------------------
I HAVE CEASED UPDATING THIS THEAD.
The old information contained below will remain for posterity, but will no longer be updated. From this point forward, all updates to this information will be found at http://www.randomphantasmagoria.com/firmware/nexus-s
---------------------------------------------------------------------------
Your effort is really appreciated
oldblue910 said:
---------------------------------------------------------------------------
I HAVE CEASED UPDATING THIS THEAD.
The old information contained below will remain for posterity, but will no longer be updated. From this point forward, all updates to this information will be found at http://www.randomphantasmagoria.com/firmware/nexus-s
---------------------------------------------------------------------------
Click to expand...
Click to collapse
Thanks. The blogging at randomphantasmagoria is very useful.
I managed to locate all the official firmware for the Nexus S (M200). Cheers and enjoy your Galaxy Nexus
4.1.1 now dead
rorio82 said:
no they don't, E: signature verification fail everytime
edit: still on 2.3.4 can't get beyond it without having to flash cwm, which i dont want to do
Click to expand...
Click to collapse
I have update m200s with 4.1.1 sojuk-jro03e and now phone is dead. no sign of life.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\ahmed soft>cd c:\
C:\>cd C:\android-sdk-windows\platform-tools
C:\android-sdk-windows\platform-tools>fastboot flash recovery touch-crespo.img
error: cannot load 'touch-crespo.img'
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery-clockwork
-touch-5.8.0.2-crespo.img
< waiting for device >
sending 'recovery' (3464 KB)...
OKAY [ 0.438s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.891s
C:\android-sdk-windows\platform-tools>adb reboot bootloader
error: device not found
C:\android-sdk-windows\platform-tools>adb reboot bootloader
error: device not found
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-cresp
o-i9020xxlc2.img
sending 'bootloader' (1536 KB)...
OKAY [ 0.188s]
writing 'bootloader'...
OKAY [ 0.359s]
finished. total time: 0.547s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash radio radio-crespo-m200krkc
1.img
sending 'radio' (12288 KB)...
OKAY [ 1.547s]
writing 'radio'...
OKAY [ 1.688s]
finished. total time: 3.234s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android-sdk-windows\platform-tools>fastboot -w update image-sojuk-jro03e.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: M200KRKC1
Serial Number........: 3435FC23CACE00EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (3964 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.500s]
sending 'recovery' (4308 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.547s]
sending 'system' (294030 KB)...
OKAY [ 36.828s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 39.000s
C:\android-sdk-windows\platform-tools>adb reboot bootloader
At end says fail and now dead. on other version stop at startup. now need help.
Thanks
br, raja
raja16sep said:
I have update m200s with 4.1.1 sojuk-jro03e and now phone is dead. no sign of life.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\ahmed soft>cd c:\
C:\>cd C:\android-sdk-windows\platform-tools
C:\android-sdk-windows\platform-tools>fastboot flash recovery touch-crespo.img
error: cannot load 'touch-crespo.img'
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery-clockwork
-touch-5.8.0.2-crespo.img
< waiting for device >
sending 'recovery' (3464 KB)...
OKAY [ 0.438s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.891s
C:\android-sdk-windows\platform-tools>adb reboot bootloader
error: device not found
C:\android-sdk-windows\platform-tools>adb reboot bootloader
error: device not found
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-cresp
o-i9020xxlc2.img
sending 'bootloader' (1536 KB)...
OKAY [ 0.188s]
writing 'bootloader'...
OKAY [ 0.359s]
finished. total time: 0.547s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash radio radio-crespo-m200krkc
1.img
sending 'radio' (12288 KB)...
OKAY [ 1.547s]
writing 'radio'...
OKAY [ 1.688s]
finished. total time: 3.234s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android-sdk-windows\platform-tools>fastboot -w update image-sojuk-jro03e.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: M200KRKC1
Serial Number........: 3435FC23CACE00EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (3964 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.500s]
sending 'recovery' (4308 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.547s]
sending 'system' (294030 KB)...
OKAY [ 36.828s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 39.000s
C:\android-sdk-windows\platform-tools>adb reboot bootloader
At end says fail and now dead. on other version stop at startup. now need help.
Thanks
br, raja
Click to expand...
Click to collapse
Just unlock bootloader and execute ***.bat file.
Sent from my Nexus S using Tapatalk 2
But How Sir,
Articudos said:
Just unlock bootloader and execute ***.bat file.
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Thanks for Answer but Phone has no sighn of life. its not powering on or not going in download mode,Nothing complete dead. Can not attach to computer. Even donot donot take Chargeing_________________ Which ***.bat file where it is?
Br, Raja
install drivers for your pnone first
open run and type
devmgmt.msc
you should see android adb interface or fastboot something,...
if u dont see them,.. please install drivers
raja16sep said:
Thanks for Answer but Phone has no sighn of life. its not powering on or not going in download mode,Nothing complete dead. Can not attach to computer. Even donot donot take Chargeing_________________ Which ***.bat file where it is?
Br, Raja
Click to expand...
Click to collapse
Maybe...As far as I remember, there is just one "bat" file. If you are running windows, just execute it.(4.1+)
(You have to run fastboot mode befor executing "bat" file)
Sent from my Nexus S using Tapatalk 2
Power Ic Problem.
Thanks for help. The phone was restarting before. After flash now there is problem in its Power Ic. Because its getting hot. Let repaired by Hardware then try other solutions.
thanks
Br, Raja
Can anyone pls upload M200 Sbl.bin.Thanks

[Q] Can't restore nexus 7

Hi all,
Since I'm new to this forum I was not allowed to post on the developers threat, so I made a new one hoping some one could help me.
My new nexus 7 arived a few days ago and I had rooted it using the Nexus root Toolkit 1.5.4. (android 4.1.2)
Than I installed a new custom rom (PARANOIDANDROID 2.2) on the nexus but I did not like that rom so I wanted to restore it back to the stock rom.
When I tried that using the Nexus root toolkit 1.5.4 I kept saying FAILED.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2092 KB)...
FAILED (data transfer failure (Too many open files in system))
finished. total time: 0.098s
rebooting into bootloader...
FAILED (remote: (Nv3pBadReceiveLength))
finished. total time: 0.005s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.41
Baseband Version.....: N/A
Serial Number........: Not relevant I guess...
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4896 KB)...
OKAY [ 0.585s]
writing 'boot'...
OKAY [ 1.763s]
sending 'recovery' (5240 KB)...
OKAY [ 0.628s]
writing 'recovery'...
OKAY [ 1.342s]
sending 'system' (446268 KB)...
FAILED (data transfer failure (Too many open files in system))
finished. total time: 6.425s
I think it's going wrong with the first step (Sending 'bootloader').
I'm restoring to android 4.1.2 because that one is using bootloader 3.41 and if I try to restore to android 4.1.1 I get some other error messages with the bootloader.
This is on a windows 7 x64 bit machine, I tried 2 different cables, the stock cable and the cable from my nexus s3 with both didn't fix anything and I tried every usb port (for some reason only usb3.0 ports work with my computer...)
I even tried restoring to stock + unroot on 2 other computers (win 7 x64 and win 2008 r2 x64) and both are stuck at: sending 'bootloader' (2092 KB)...
So basicly I do get in to fastboot, but I can't get any further than that, Recovery mode gives my an open android with a "!" in its "belly" and the option "Start" get me stuck at the bootlogo from the custom rom (PARANOIDANDROID 2.2).
I hope you guys can help me with this anoying problem.
Btw. I'm sorry for my bad english, this isn't my motherlanguage and it's late.
EDIT: the tablet is stuck on "google" with an unlocked lock logo when I try to turn it on.
EDIT2: On windows 8 x64 it is saying too many links.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2092 KB)...
FAILED (data transfer failure (Too many links))
fisnished. total time: 0.124s
rebooting into bootloader...
FAILED (coomand write failed (Unknown error))
finished. total time: 0.639s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (Unknown error))
finished. total time: 0.703s
fixed!
kanuva said:
Hi all,
Since I'm new to this forum I was not allowed to post on the developers threat, so I made a new one hoping some one could help me.
My new nexus 7 arived a few days ago and I had rooted it using the Nexus root Toolkit 1.5.4. (android 4.1.2)
Than I installed a new custom rom (PARANOIDANDROID 2.2) on the nexus but I did not like that rom so I wanted to restore it back to the stock rom.
When I tried that using the Nexus root toolkit 1.5.4 I kept saying FAILED.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2092 KB)...
FAILED (data transfer failure (Too many open files in system))
finished. total time: 0.098s
rebooting into bootloader...
FAILED (remote: (Nv3pBadReceiveLength))
finished. total time: 0.005s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.41
Baseband Version.....: N/A
Serial Number........: Not relevant I guess...
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4896 KB)...
OKAY [ 0.585s]
writing 'boot'...
OKAY [ 1.763s]
sending 'recovery' (5240 KB)...
OKAY [ 0.628s]
writing 'recovery'...
OKAY [ 1.342s]
sending 'system' (446268 KB)...
FAILED (data transfer failure (Too many open files in system))
finished. total time: 6.425s
I think it's going wrong with the first step (Sending 'bootloader').
I'm restoring to android 4.1.2 because that one is using bootloader 3.41 and if I try to restore to android 4.1.1 I get some other error messages with the bootloader.
This is on a windows 7 x64 bit machine, I tried 2 different cables, the stock cable and the cable from my nexus s3 with both didn't fix anything and I tried every usb port (for some reason only usb3.0 ports work with my computer...)
I even tried restoring to stock + unroot on 2 other computers (win 7 x64 and win 2008 r2 x64) and both are stuck at: sending 'bootloader' (2092 KB)...
So basicly I do get in to fastboot, but I can't get any further than that, Recovery mode gives my an open android with a "!" in its "belly" and the option "Start" get me stuck at the bootlogo from the custom rom (PARANOIDANDROID 2.2).
I hope you guys can help me with this anoying problem.
Btw. I'm sorry for my bad english, this isn't my motherlanguage and it's late.
EDIT: the tablet is stuck on "google" with an unlocked lock logo when I try to turn it on.
EDIT2: On windows 8 x64 it is saying too many links.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2092 KB)...
FAILED (data transfer failure (Too many links))
fisnished. total time: 0.124s
rebooting into bootloader...
FAILED (coomand write failed (Unknown error))
finished. total time: 0.639s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (Unknown error))
finished. total time: 0.703s
Click to expand...
Click to collapse
I just kept trying and it fixed itself, eventually I let the battery die than I charged it for 2 hours and I tried it again on my windows 7 machine wich gave this error message: FAILED (data transfer failure (Too many open files in system)).
I'm getting the same "Too many open files in system" error
kmad86 said:
I'm getting the same "Too many open files in system" error
Click to expand...
Click to collapse
I'm getting similar errors
well i fixed this by putting the usb cable into a usb 2.0 port instead of the 3.0 one.
So try another usb port if you still have problems.
Same here. Fixed it afterall!
Was about to give up on Nexus 7 2012 due to write failed messages when flashing the larger files like system.img and complete roms including factory roms 4.4.4 to 5.1.1. (upon booting stuck on animated google logo)
I did notice the error messages were different in output as was the time at which they apeared after pressing the enter(return) key. Another indication may have been the slowing down in responseness of the fastboot commands (erase,format,reboot-bootloader etc).
The less obvious solution, which makes no sense at all to me, was to switch USB ports on my MAC 27 (late 2013) . I ended up with sucesfull flashing using the last USB port on the right. That is on the right when sitting in front of it while the ports are on the back....
To sum it up: Not all USB ports are the same afterall? Wether 2.0 or 3.0 or voltages i have no idea. Suppose same may be true for PC's of any brand.
Don't try giving up.
Same here. USB 2.0 FTW!

Android 4.3 Update

Hi There.
I just got a brand new Nexus 4 today and the first thing I tried to do was to update to the 4.3 Android version. I downloaded the factory image from Android.com. When I tried to run the flash-all.sh script I got this error:
macyccam-jwr66v trant_macbook$ ./flash-all.sh
sending 'bootloader' (2201 KB)...
OKAY [ 0.139s]
writing 'bootloader'...
FAILED (remote: not supported in locked device)
finished. total time: 0.142s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (54321 KB)...
OKAY [ 3.397s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 3.399s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ10o
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.48
Serial Number........: 027af952120bb5bf
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MAKOZ10o'.
Update requires 'MAKOZ20i'.
finished. total time: 0.012s
Click to expand...
Click to collapse
Is something wrong with my bootloader ?
xDer_ said:
Hi There.
I just got a brand new Nexus 4 today and the first thing I tried to do was to update to the 4.3 Android version. I downloaded the factory image from Android.com. When I tried to run the flash-all.sh script I got this error:
Is something wrong with my bootloader ?
Click to expand...
Click to collapse
Your bootloader seems like it's locked. You need to unlock it first with fastboot by running "fastboot oem unlock". Note that this will wipe all data on your device, which you probably don't mind since you just got the device.

[Q] nexus not accepting stock image - signature verification fail

hello all
My beloved Nexus recently crashed on me and it would boot past the "google" screen :crying:. I have done research and seen some suggestion to clear this is to flash stock image back onto the device. I have tried this via the nexus root toolkit and also via ADB. Both methods give me a signature verification failed error. can anyone please help me?
C:\Users\MA7424\Downloads\fastboot>fastboot -w update image-mantaray-jdq39.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB04MPXT
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4608 KB)...
OKAY [ 0.671s]
writing 'boot'...
OKAY [ 0.118s]
sending 'recovery' (5108 KB)...
OKAY [ 0.753s]
writing 'recovery'...
OKAY [ 0.122s]
sending 'system' (522703 KB)...
OKAY [ 75.752s]
writing 'system'...
FAILED (remote: signature verification failed!)
finished. total time: 81.264s
Glennfoot said:
hello all
My beloved Nexus recently crashed on me and it would boot past the "google" screen :crying:. I have done research and seen some suggestion to clear this is to flash stock image back onto the device. I have tried this via the nexus root toolkit and also via ADB. Both methods give me a signature verification failed error. can anyone please help me?
C:\Users\MA7424\Downloads\fastboot>fastboot -w update image-mantaray-jdq39.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB04MPXT
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4608 KB)...
OKAY [ 0.671s]
writing 'boot'...
OKAY [ 0.118s]
sending 'recovery' (5108 KB)...
OKAY [ 0.753s]
writing 'recovery'...
OKAY [ 0.122s]
sending 'system' (522703 KB)...
OKAY [ 75.752s]
writing 'system'...
FAILED (remote: signature verification failed!)
finished. total time: 81.264s
Click to expand...
Click to collapse
I had this issue one time and I solved it by flashing a different kernel. Can u still get into recovery mode (volume buttons and power at the same time)? How did u get into the bootloop in the first place because that could help solve the issue.
Sent from my Nexus 10 using xda app-developers app
yep i can get into TWRP - managed to side load slimbean rom, but i'm back to the bootlooping
Glennfoot said:
yep i can get into TWRP - managed to side load slimbean rom, but i'm back to the bootlooping
Click to expand...
Click to collapse
Did you try wiping everything first before flashing? If that doesn't work download ncry toolkit. I found that when the other root toolkit fails this one works and vice versa. I'm pretty sure you can solve the issue by just wiping and flashing new ROM. Also remember after first flashing it takes longer to turn on so wait a couple minutes to make sure. A also can you tell me what u did to get into the bootloop because it will be easier to find a solution?
Sent from my Nexus 10 using xda app-developers app
It started looping after I was watching netflix and it froze (no response to touch or physical buttons) put into recovery to be too reboot bit it simply went into bootloops. Wiped everything using twrp then reinstalled room but still loping. Wiped everything (including recovery) using fastboot command's and then attempted to load stock image but this failed. Perform oem lock and tried again. Performed oem unlock and reinstalled twrp, side loaded slim rom to sd card (as sd card had been wiped) flashed rom and gapps via twrp but back to bootloop.
Sent from my GT-N7105 using XDA Premium HD app
It's your fastboot image.. My fastboot images contain the System.sig whereas yours says it doesnt
Sent from my HTC One using Tapatalk
Do you have a link or can you post a copy of yours. Very appreciated if you could
Sent from my GT-N7105 using XDA Premium HD app
Glennfoot said:
Do you have a link or can you post a copy of yours. Very appreciated if you could
Sent from my GT-N7105 using XDA Premium HD app
Click to expand...
Click to collapse
Where did you get the stock image you're trying to install? Try downloading the factory image directly from Google. You can download either 4.2.2 (JDQ39) or 4.3 (JWR66Y).
https://developers.google.com/android/nexus/images
sharksfan7 said:
Where did you get the stock image you're trying to install? Try downloading the factory image directly from Google. You can download either 4.2.2 (JDQ39) or 4.3 (JWR66Y).
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Sadly that is where i got it from, tried both 4.2.2 and 4.3. I'm starting to think my nexus might be dead.
could my laptop be causing the problem?

[Q] help unbricking nexus 4 stuck in bootloop

Hey guys/gals,
Need some help here. I've been rooting/loading custom roms for almost 7 or so years. I'm not a programmer but know my ways around software well enough..
My problem is my nexus 4 started to bootloop and couldn't ever get it to start up. I had been using one of the purity builds (was a stable kitkat build i think) for a few months. Then one day I started getting force close type errors for a specific app... can't remember which.. so decided to restart the phone just like i would when this usually happens.. after that it wouldn't start up...
I've tried using all available tips and drivers/software and can't get it to successfully restore it. Googled a lot and read many posts.. i keep getting errors... i took a picture of that error which happens..
This is the first time I've bricked a phone so hopefully someone has come across this with a fix or is it truly a bricked phone?
thanks
also.. tried another toolkit and this is the error I get..
"***************************************************************
One-Click Unroot to Stock 4.4 Kit Kat for LG Nexus 4!
Brought to you by AndroidRootz.com
***************************************************************
This script will: Unroot your Nexus 4 to Stock 4.4 & Lock your Bootloader
For more details go to AndroidRootz.com
***************************************************************
Warning! This will delete everything on your phone! BACKUP your phone!
First make sure your in FASTBOOT MODE!
Press enter to continue
sending 'bootloader' (2203 KB)...
OKAY [ 0.071s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.075s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.436s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 1.439s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ20i
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.98
Serial Number........: 0042c881549801cf
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MAKOZ20i'.
Update requires 'MAKOZ30d'."
I can't update the required bootloader as this toolkit suggests since I can't even access the system etc..
Also, I can get into recovery no problem... but can't mount USB storage or sdcard.. system and firmware seem to be able to be mounted.. but all together can't really do much..
thanks again for any help
Hi
I don't think it is you who bricked it. According to this thread, the phone dies on its own. I'm not sure if your problem is the same as theirs, but the symptoms surely look identical.
Out of all the 10+ cases in that thread, only 1 phone was fixed when the owner did a factory reset; others had to get a replacement.
I'm sorry for not providing an actual/helpful answer and being a bearer of bad news, but I just thought you should know what happened to similar devices. I hope you get it fixed.

Categories

Resources