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.
Related
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!
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.
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
Hi All,
I'm using Mac Terminal, have latest SDK, adb and fastboot installed. I have Nexus 7 (2012) Wifi - Nakasi
I followed the pinned post to upgrade my 4.3 (JWR66Y) to KitKat 4.4. I rebooted into fastboot and started ./flash-all.sh
Mid way through the process had stalled so I 'control C' out of the process.
$ ./flash-all.sh
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.993s]
finished. total time: 0.994s
erasing 'cache'...
OKAY [ 1.059s]
finished. total time: 1.059s
erasing 'recovery'...
OKAY [ 0.854s]
finished. total time: 0.855s
erasing 'system'...
OKAY [ 0.490s]
finished. total time: 0.490s
erasing 'userdata'...
OKAY [ 6.154s]
finished. total time: 6.154s
sending 'bootloader' (2100 KB)...
OKAY [ 0.302s]
writing 'bootloader'...
OKAY [ 9.666s]
finished. total time: 9.969s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d2d4226501005
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.024s]
sending 'boot' (4990 KB)...
OKAY [ 1.045s]
writing 'boot'...
OKAY [ 1.047s]
sending 'recovery' (5530 KB)...
OKAY [ 3.340s]
writing 'recovery'...
OKAY [ 1.381s]
sending 'system' (611878 KB)...
^C
Click to expand...
Click to collapse
I ran same process and it was hanging again at the same spot. I exited the same way. Now terminal cannot find device in adb devices. I can still boot into recovery mode.
$ ./adb devices
List of devices attached
Click to expand...
Click to collapse
$ ./flash-all.sh
< waiting for device >
Click to expand...
Click to collapse
I'm not sure what to do now!!! any help would be...helpful. Please.
You need to wait a but, because the system image us about 630MB, which may take round about two minutes to get transferred and flashed.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
You need to wait a but, because the system image us about 630MB, which may take round about two minutes to get transferred and flashed.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I waited 20 minutes the first time and 15 minutes the second time.
I tried flashing using different method from fastboot (http://forum.xda-developers.com/showthread.php?t=2010312). Problems happen when flashing system.img (~600MB).
Has anyone else found out the checksums aren't working? I get an error "E:signature verification failed" when using "flash-all.sh" from recovery mode (different method i've tried)
Note: no problems updating my nexus 4
Just wanted to update you on a solution if anyone has a similar problem.
I erased the system image through fastboot.
./fastboot erase system
Click to expand...
Click to collapse
Flashed the system image for old stock 4.3
./fastboot flash system system.img
Click to expand...
Click to collapse
Ran the flash-all script
./flash-all.sh
Click to expand...
Click to collapse
System was updated and worked! I back-dated to android 4.3, then did a second flash-all script to update to the current version of android 4.4. I believe that the original factory image for 4.4 was not working. The factory image was updated a day later - this is the file i used.
Thanks to everyone in xda. The many posts I read - even not directly related to my problem - provided a solution.
I hope my next post isn't so noob
whitext said:
I waited 20 minutes the first time and 15 minutes the second time.
I tried flashing using different method from fastboot (http://forum.xda-developers.com/showthread.php?t=2010312). Problems happen when flashing system.img (~600MB).
Has anyone else found out the checksums aren't working? I get an error "E:signature verification failed" when using "flash-all.sh" from recovery mode (different method i've tried)
Note: no problems updating my nexus 4
Click to expand...
Click to collapse
Well,I got the similar problem the other day on my Nakasig when I was flashing factory images through Fastboot.
Not only did I try the "flash-all.bat" command, but I also manually inputted each command line one after another.
However, I still encountered the same issue and waited for more 30 minutes during the "sending system" process.
Even worse was that I unplugged my N7 and tried to boot it,which led me to be stuck with the Google logo.:crying:
After removing the battery and booting it into Fastboot again,this time I decided to use Wug's toolkit to flash it.:good:
And thankfully,it worked and I can grab the delicious Kitkat now.
BTW, my N7 still failed to pass Hashcheck while using Wug's automatic method, therefore I just downloaded the Factory images and used Wug's tool to navigate to the .tgz file and then flash it.It spent me around 2 minutes to complete the "sending system" process this time.
Hi all, first off, yes I have read quite a bit and I am completely stumped on this one.
A buddy from work dropped off his Nexus 4 and asked about the "bootloop" it is stuck in. Looking at it, this is not a boot loop as far as I can tell. He said he used the http://www.wugfresh.com/nrt/ to do a root, but it apparently went wrong (he said it reported successful completion).
What I have done thus far:
Download Google stock rom and flashed that following their instructions in the "flash-all.sh" file for Kit-Kat. Tried to go into recovery, but the recovery just gives the android with the red triangle above it and hangs. On boot the screen shows the "Google" logo with the unlocked symbol and then shows the kit-kat boot animation but just sits there and never finishes. I gave it about 30 minutes but no luck.
I can get into bootloader and then flash a recovery (CWM for Mako), which then allows me to get into CWM and either flash a custom ROM (tried latest PA beta) with the same hang on boot.
Tried to custom erase system, boot, recovery with the instructions below:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-clockwork-6.0.4.7-mako.img
boot to recovery
set up for sideload in CWM
adb sideload pa_mako-4.1-BETA2-20140310.zip
reboot
Same result, just hangs on reboot with animation for boot.
I tried flashing the radio and bootloader back to 4.3 and then flashing the stock rom for the Google ROM occam-jwr66y-factory-74b1deab.tgz which is where I am at now with it just sitting at animation if the X lighting up.
I just noticed that when I plug it in to my workstation it recognizes the device sort of and shows that it is mountable, but then just hangs and never loads the directory structure like normal.
Another thing to note, when I mount /system and /data in CWM and "adb shell" into the phone, the /sdcard/0 location shows empty, which as far as I know this should be populated with the usual sdcard user directories, maybe??
Any help would be appreciated. I noticed that if I hold both the volume up and volume down buttons it says it is in "Download" mode, didn't know that was a thing outside of Samsung devices.
Ouput from flashing with Google stock 4.4.2 ROM:
sudo ./flash-all.sh
[sudo] password for jscott:
sending 'bootloader' (2203 KB)...
OKAY [ 0.089s]
writing 'bootloader'...
OKAY [ 0.311s]
finished. total time: 0.401s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.790s]
writing 'radio'...
OKAY [ 2.541s]
finished. total time: 4.332s
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...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.98
Serial Number........: 0221a297d9d67206
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6340 KB)...
OKAY [ 0.253s]
writing 'boot'...
OKAY [ 0.356s]
sending 'recovery' (6888 KB)...
OKAY [ 0.287s]
writing 'recovery'...
OKAY [ 0.398s]
erasing 'system'...
OKAY [ 0.579s]
sending 'system' (713960 KB)...
OKAY [ 26.844s]
writing 'system'...
OKAY [ 40.883s]
rebooting...
finished. total time: 69.615s
Recovery was broken again.
Had to flash recovery again to get in but I can "adb shell" the phone no problems.
If more information is needed or someone has a sure fire way to fix this same problem please hit me up, but at this point I am at a loss.
Just found out that the phone may have died when the "wugfresh" script was running, but he said that it died afterwards, since I wasn't there I don't know for sure how this all played out.
Oops, I just posted the same problem a few minutes ago. In my defense to the moderators, your thread wasn't posted when I started writing mine.
Anyhow, have you tried flashing the 4.2.2 factory image? That is the only one I manage to boot, but my IMEI and network are gone...
MtG92 said:
Oops, I just posted the same problem a few minutes ago. In my defense to the moderators, your thread wasn't posted when I started writing mine.
Anyhow, have you tried flashing the 4.2.2 factory image? That is the only one I manage to boot, but my IMEI and network are gone...
Click to expand...
Click to collapse
Same thing on my side with the 4.2.2 ROM. Loads fine, but no IMEI or anything like that. Not sure what the deal is with it.
Allowed OTA update and now I get the android bot with the red triangle when trying to go into recovery, but it says "no command" under it. On boot the device just hangs at "starting apps." and doesn't move past that.
Sideloaded PA 3.99 mako for the phone and it just hangs on boot animation as it has done previously before successfully flashing the 4.2 factory image. Not sure what the deal is but a solution for this would be awesome as I am totally stumped.
I have been dealing with this for a few months, and what I have done to get it to work is let it sit for a few hours. Then give it a shot. About half the time my phone boots up. Once it's booted up everything works, but if I need to reboot for any reason your screwed for a few hours.
It started happening for me once the 4.4 update rolled out, and ever since it has been doing this. I asked on here a few time and got no responses.
Sent from my Nexus 4 using Tapatalk
NeCr0mStR said:
Same thing on my side with the 4.2.2 ROM. Loads fine, but no IMEI or anything like that. Not sure what the deal is with it.
Allowed OTA update and now I get the android bot with the red triangle when trying to go into recovery, but it says "no command" under it. On boot the device just hangs at "starting apps." and doesn't move past that.
Sideloaded PA 3.99 mako for the phone and it just hangs on boot animation as it has done previously before successfully flashing the 4.2 factory image. Not sure what the deal is but a solution for this would be awesome as I am totally stumped.
Click to expand...
Click to collapse
I met the same problem. My nexus 4 met this problem about 4 or 5 times. at first time, I tried restarting the phone and sometimes it might boot successfully, then everything works fine. Second time the reboot doesn't work any more, but flash stock with the newest factory ROM works fine(4.3 at that time), at this time I backup all my data. After I met this more, I found this problem arose only when the phone automatically shutting down because of the dead battery. Yesterday I met this problem again because of the dead battery, and at this time only reboot the phone with 4.2.0. I tried all other factory stocks from 4.2.0 to 4.4.2. Hope you can solve this early. And ask me any information you need.
NeCr0mStR said:
Hi all, first off, yes I have read quite a bit and I am completely stumped on this one.
A buddy from work dropped off his Nexus 4 and asked about the "bootloop" it is stuck in. Looking at it, this is not a boot loop as far as I can tell. He said he used the http://www.wugfresh.com/nrt/ to do a root, but it apparently went wrong (he said it reported successful completion).
What I have done thus far:
Download Google stock rom and flashed that following their instructions in the "flash-all.sh" file for Kit-Kat. Tried to go into recovery, but the recovery just gives the android with the red triangle above it and hangs. On boot the screen shows the "Google" logo with the unlocked symbol and then shows the kit-kat boot animation but just sits there and never finishes. I gave it about 30 minutes but no luck.
I can get into bootloader and then flash a recovery (CWM for Mako), which then allows me to get into CWM and either flash a custom ROM (tried latest PA beta) with the same hang on boot.
Tried to custom erase system, boot, recovery with the instructions below:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-clockwork-6.0.4.7-mako.img
boot to recovery
set up for sideload in CWM
adb sideload pa_mako-4.1-BETA2-20140310.zip
reboot
Same result, just hangs on reboot with animation for boot.
I tried flashing the radio and bootloader back to 4.3 and then flashing the stock rom for the Google ROM occam-jwr66y-factory-74b1deab.tgz which is where I am at now with it just sitting at animation if the X lighting up.
I just noticed that when I plug it in to my workstation it recognizes the device sort of and shows that it is mountable, but then just hangs and never loads the directory structure like normal.
Another thing to note, when I mount /system and /data in CWM and "adb shell" into the phone, the /sdcard/0 location shows empty, which as far as I know this should be populated with the usual sdcard user directories, maybe??
Any help would be appreciated. I noticed that if I hold both the volume up and volume down buttons it says it is in "Download" mode, didn't know that was a thing outside of Samsung devices.
Ouput from flashing with Google stock 4.4.2 ROM:
sudo ./flash-all.sh
[sudo] password for jscott:
sending 'bootloader' (2203 KB)...
OKAY [ 0.089s]
writing 'bootloader'...
OKAY [ 0.311s]
finished. total time: 0.401s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.790s]
writing 'radio'...
OKAY [ 2.541s]
finished. total time: 4.332s
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...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.98
Serial Number........: 0221a297d9d67206
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6340 KB)...
OKAY [ 0.253s]
writing 'boot'...
OKAY [ 0.356s]
sending 'recovery' (6888 KB)...
OKAY [ 0.287s]
writing 'recovery'...
OKAY [ 0.398s]
erasing 'system'...
OKAY [ 0.579s]
sending 'system' (713960 KB)...
OKAY [ 26.844s]
writing 'system'...
OKAY [ 40.883s]
rebooting...
finished. total time: 69.615s
Recovery was broken again.
Had to flash recovery again to get in but I can "adb shell" the phone no problems.
If more information is needed or someone has a sure fire way to fix this same problem please hit me up, but at this point I am at a loss.
Just found out that the phone may have died when the "wugfresh" script was running, but he said that it died afterwards, since I wasn't there I don't know for sure how this all played out.
Click to expand...
Click to collapse
You have to keep flashing the Stock ROM...that's what saved me
Sent from my Moto G
GameAware said:
You have to keep flashing the Stock ROM...that's what saved me
Sent from my Moto G
Click to expand...
Click to collapse
So you had the same problem and managed to solve it by flashing the stock rom multiple times? How many times did you have to do it, and have you had that problem since?
MtG92 said:
So you had the same problem and managed to solve it by flashing the stock rom multiple times? How many times did you have to do it, and have you had that problem since?
Click to expand...
Click to collapse
Yes I had the same problem and flashed the ROM the first time, but still nothing. I then flashed it again and it booted up as normal. No problems since.
Sent from my Moto G