Short version first: I am trying to use the "back to stock" feature of Nexus Root Toolkit to flash a factory ROM to a soft-bricked Nexus 4. I get to a Window that says it is "booting up your freshly flashed stock device" but then nothing at all happens.
Longer story:
Today I used the Nexus Root Toolkit (NRT) to unlock and root my Nexus 4. NRT is great software and helped me through all the stages.
After I rooted successfully and restored my apps etc, I tried using an app called custom android font switcher to achieve some language related aims (installing Khmer font). Anyway, straight after that the phone restarted and I have been stuck at the X logo ever since (hours).
Now I've gone back to NRT to try and use its "back to stock" feature to recover my soft-bricked device. My phone is in bootloader mode. I have downloaded the appropriate factory image direct from google, pointed NRT to this. It gets past the next stage (hashcheck). Then it say please be patient while your file is extracted. Then it says checking fastboot status and finds the device connected. Then I press OK to flash the device. It opens a new command window titled "flashstock.bat" that says it is "booting up your freshly flashed stock device, be patient etc. However, nothing else happens either with this window or at the phone. There is no further action, even after 20-30mins. I've tried this several times.
Can anyone suggest anything I could do to help the process complete? Should NRT work for a Nexus 4, or do I have to look instead at adb / fastboot?
Found solution
Found solution, feel silly but am posting it here in case it helps someone else:
The factory image file I had downloaded from Google should have had a .TGZ extension but had been saved with a .TAR extension by my download manager (Internet Download Manager).
When I renamed the file, the process completed successfully. I can only assume that NRT "thought" it could unzip the TAR file, but could not actually extract any content out of it.
All the best.
aanon03 said:
Short version first: I am trying to use the "back to stock" feature of Nexus Root Toolkit to flash a factory ROM to a soft-bricked Nexus 4. I get to a Window that says it is "booting up your freshly flashed stock device" but then nothing at all happens.
Longer story:
Today I used the Nexus Root Toolkit (NRT) to unlock and root my Nexus 4. NRT is great software and helped me through all the stages.
After I rooted successfully and restored my apps etc, I tried using an app called custom android font switcher to achieve some language related aims (installing Khmer font). Anyway, straight after that the phone restarted and I have been stuck at the X logo ever since (hours).
Now I've gone back to NRT to try and use its "back to stock" feature to recover my soft-bricked device. My phone is in bootloader mode. I have downloaded the appropriate factory image direct from google, pointed NRT to this. It gets past the next stage (hashcheck). Then it say please be patient while your file is extracted. Then it says checking fastboot status and finds the device connected. Then I press OK to flash the device. It opens a new command window titled "flashstock.bat" that says it is "booting up your freshly flashed stock device, be patient etc. However, nothing else happens either with this window or at the phone. There is no further action, even after 20-30mins. I've tried this several times.
Can anyone suggest anything I could do to help the process complete? Should NRT work for a Nexus 4, or do I have to look instead at adb / fastboot?
Click to expand...
Click to collapse
Install adb in your pc and learn how to use fastboot commands.
It is easy and safe to mess with your phone and future android phones you might buy.
Sent from my Nexus 4 using xda premium
All you really needed to do was fastboot flash the system img. The font you flashed was installed there, then wipe cache and reboot.
Sent from my Nexus 4 using Xparent Cyan Tapatalk 2
Related
Hello everyone!
I tried to restore the stock image using Nexus 4 Tool Kit (both the original one and the Wug's one), and everytime I tried, the script stucked at "writing system".
I manually flashed system and userdata images with Wug's tool kit and everything went well but I only have 5Gb memory instead of 16.
Does anyone know why?
Try this http://forum.xda-developers.com/showthread.php?t=2033692
[HOW-TO] Fix internal storage if 16GB now shows 8GB
Sent from my Nexus 4
OP...
In future, don't use a toolkit. Do it yourself
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
4OnTheFloor said:
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
Click to expand...
Click to collapse
When going into recovery the warning sign is the splash screen for stock recovery. This likely means that you have not yet flashed a custom recovery yet, which is necessary to flash CM. First read this guide to unlock the bootloader (if you havent already), then flash a custom recovery (preferably TWRP). After you have installed the recovery, download CM as well as the latest gapps package and place them somewhere on your internal sd. Boot into recovery and go to the wipe menu, then swipe to factory reset. Finally flash the rom and gapps, and then reboot.
4OnTheFloor said:
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
Click to expand...
Click to collapse
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
noobdeagle said:
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
Click to expand...
Click to collapse
I am using the .bat file... I've also tried the toolkit, and both appear to use the same basic procedure, and they stop at "writing system" no matter what.
Does anyone happen to know how the .bat file and toolkit get access to the phone? ...because I can't see it in adb (I'm guessing it's because I can't boot the phone.) However I can get into fastboot and recovery modes on the device.
I cannot get the device (nexus 4) to boot or connect in ADB mode to my computer. What can I do??
UPDATE - PROBLEM FIXED
I un-bricked my phone
SOLUTION this is what worked for me, your mileage may vary
Install ADB drivers, etc. from Android SDK (google how to do this)
Flash custom recovery (can be done easily with Nexus 4 Toolkit here on XDA) - I used TWRP Touch Recovery.
Once that is done, shut the phone off completely and boot into Fastboot (hold volume down and power)
Use volume keys to select Recovery Mode, then hit Power
In recovery mode:
Wipe > Advanced Wipe > Check off the box beside "System" > Swipe to Wipe
Go back to recovery mode main screen:
Wipe > Format Data > Follow the instructions on the screen
I think this step is what did it. When having problems with partitions, just format everything and start over
Now we should be able to write to the System partition, meaning you can flash a ROM and get your phone to boot again.
Follow the rest of these instructions to quickly flash the stock Android image from Google onto your phone.
Go back to recovery mode main screen, once again:
Reboot > Bootloader > Follow any additional instructions it gives you
Download Google Nexus 4 factory stock image "occam" (Google it)
When that is downloaded, open it with 7zip. Inside there are some files, one of which is called image-occam-jdq39.zip. Inside are some images - unzip those as well. You'll need the system.img file in a bit...
Using Wug's Nexus Root Toolkit (Google it - install it on your Windows PC):
Open the program
Launch advanced utilities
Hit the System button to permanently flash to System partition. Hit "ok" on the window that pops up.
Find the system.img file I mentioned back on step 10 and select that, when prompted, and open it.
If all went well, your device will now boot into the stock Android ROM.
noobdeagle said:
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
Click to expand...
Click to collapse
I too am stuck at writing system. I"m not sure what you mean when you said "run flash-all.bat". Where do I get that?
Thanks.
Soundchasr said:
I too am stuck at writing system. I"m not sure what you mean when you said "run flash-all.bat". Where do I get that?
Thanks.
Click to expand...
Click to collapse
The system takes awhile to write, how long have you guys wait before you say its "stuck"?
Sent from my Nexus 4 using Tapatalk 4 Beta
About 20-25 minutes.
Yea, that's way too long.
Sent from my Nexus 4 using Tapatalk 4 Beta
Stuck, but working
I was flashing the 4.3 image using the included flash-all.bat (but I edited it to remove -w parameter so that it wouldn't wipe my data).
In the 'writing system' step, the command window got stuck. In the phone screen, at the bottom, it said 'writing' for a while and then that also went away. I waited for ~40 min, and still the command window was at 'writing system', so I closed the command window, and booted my phone by selecting start from the bootloader.
And voila! It worked. Booted in under a minute, the flash was a success, I got JB 4.3 without losing any of my data.
Lost my root and custom recovery though. But I knew that would happen. Gonna try SuperSu for 4.3 now, after flashing TWRP.
Had the same problem, tried everything! With my tiny powers, but it kept stucking at "writing system" . I thought that I bricked the device, so for the last hope, I installed WugFresh's Nexus Toolkit and did a Fast Stock + unroot. It Installed everything flawlessly! I'm gonna donate to that guy! He's a godsend savior.
Hope someone can help. I've tried updating my Nexus 4 to KitKat, and think I've borked it, as it is now stuck in the boot screen with the four coloured spinning circles.
Here's what I did:
Downloaded the 4.4 KRT16O Factory Image for Nexus 4 from Google Developers site
Unlocked the Bootloader on my Nexus 4
Went to Android SDK manager folder and Platform Tools.
Extracted the Factory Image to this folder
Enter comand prompt
Typed fastboot devices to ensure the phone is visible
Typed flash-all.bat
The phone re-boots, I get the spinning circles and nothing more.
I can get back to fastboot, and have tried reinstalling the Jelly bean image, but this also hangs at the boot screen. I've tried both Images and neither seem to get past their relevant boot screens. In both instances I can get back to fastboot.
I haven't installed a custom recovery
What to do?
I'd be grateful of any help.
dreamypuma said:
Hope someone can help. I've tried updating my Nexus 4 to KitKat, and think I've borked it, as it is now stuck in the boot screen with the four coloured spinning circles.
Here's what I did:
Downloaded the 4.4 KRT16O Factory Image for Nexus 4 from Google Developers site
Unlocked the Bootloader on my Nexus 4
Went to Android SDK manager folder and Platform Tools.
Extracted the Factory Image to this folder
Enter comand prompt
Typed fastboot devices to ensure the phone is visible
Typed flash-all.bat
The phone re-boots, I get the spinning circles and nothing more.
I can get back to fastboot, and have tried reinstalling the Jelly bean image, but this also hangs at the boot screen. I've tried both Images and neither seem to get past their relevant boot screens. In both instances I can get back to fastboot.
I haven't installed a custom recovery
What to do?
I'd be grateful of any help.
Click to expand...
Click to collapse
Boot in bootloader, then select "recovery". When you get to an android laying on his back, press "Power+Volume UP" at the same time (don't hold. Just press). A menu should appear. Select "Data wipe/ Factory reset", and reboot.
abaaaabbbb63 said:
Boot in bootloader, then select "recovery". When you get to an android laying on his back, press "Power+Volume UP" at the same time (don't hold. Just press). A menu should appear. Select "Data wipe/ Factory reset", and reboot.
Click to expand...
Click to collapse
I had a thread yesterday on the same topic. http://forum.xda-developers.com/showthread.php?p=47490462#post47490462
hope that helps.
This may work
Hi, I encountered the same problem. I had the LTE baseband radio which was not being accepted in the flash-all.bat and it kept giving me in error in install and wont complete. I used nexus root tool kit to flash the radio img extracted from the 4.4 occam file using the advanced utilities in tool kit. After that I used the tool kit again and again to install the 4.4 but it kept getting stuck in the boot animation even after successful installs. I gave up and as a last resort tried the flashall.bat again. It went through smoothly since it detected the new radio and I let it hang in there for 10-15 mins in the boot animation and viola ! I had it installed.
Hope part of this may work for you.
---------- Post added at 01:40 PM ---------- Previous post was at 01:35 PM ----------
priyab said:
Hi, I encountered the same problem. I had the LTE baseband radio which was not being accepted in the flash-all.bat and it kept giving me in error in install and wont complete. I used nexus root tool kit to flash the radio img extracted from the 4.4 occam file using the advanced utilities in tool kit. After that I used the tool kit again and again to install the 4.4 but it kept getting stuck in the boot animation even after successful installs. I gave up and as a last resort tried the flashall.bat again. It went through smoothly since it detected the new radio and I let it hang in there for 10-15 mins in the boot animation and viola ! I had it installed.
Hope part of this may work for you.
Click to expand...
Click to collapse
Also delete your old folder of ADB, download a new one and reextract. Unzip the tar>tar directly in platform tools folder. Good luck
Follow this i too had the same prob bt got it resolved through this method. jst keep ur phone on bootloader/fastboot mode.. n run this toolkit
http://forum.xda-developers.com/showthread.php?t=2531374
Sent from my Nexus 4 using xda app-developers app
Just search the forum next time this problem is on every page and on every page and thread there is a solution...... You are not the first but hope you get it fixed
Install a custom recovery
clockwork or twrp
i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)
niceguy01 said:
i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)
Click to expand...
Click to collapse
Yes, me too. I can't load anything except ADB & Fastboot. I used the Nexus 7 Toolkit to try to update to Kit Kat and now I have a soft bricked device. HELP!!!:crying:
Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?
cr0wnest said:
Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?
Click to expand...
Click to collapse
what file do i need to push in my device??
Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5
niceguy01 said:
what file do i need to push in my device??
Click to expand...
Click to collapse
Check out this sticky here, it gives instructions on how to do it and what files are required. Its quite a lengthy guide, but its the safest method. http://forum.xda-developers.com/showthread.php?t=1907796
Pirateghost said:
Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5
Click to expand...
Click to collapse
sorry im just a newbie:angel:
UPDATE: booting failed already gone by flashing cyanogen rom
the problem now is stuck in booting.see the attach picture
what is the meaning of
archive does not contain boot.sig
archive does not contain recovery.sig
archive does not contain system.sig
Got the same problem...I used RTK to flash 4.4 and ended up with a soft bricked N7.
Well initially I haven't been able to update any newer versions of CM. I was stuck on 10.2 nightly. I got a notification that there's an update so I downloaded it and tried installing. I get stuck when my N7 will go into recovery, I'll always get the droid with the red exclamation point and I have to stop the update. But I will always be able to do a system reboot and use the N7. After flashing using the RTK, all I can do is boot into the Bootloader mode. Choice at that point it Recovery, Reboot Recovert, Reboot Bootloader and Power Off. If I choose Recovery nothing happens. So the real choice is only to power off or reboot the bootloader.
I tried using fast boot but the guide I got was asking me to put the tablet in debugging mode (which I can't really do). And I get an error when doing the steps in CMD. I think I wasn't able to properly load the drivers because I am not seeing my device listed with serial number when I run >dab devices.
Kindda stuck and waiting where this thread will lead to as well so I can fix my N7.
Also, when I get the factory image (JWR66V) and run 7-zip on it, I don't see these files: bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, flash-base.sh. I only see 1 file.
As mentioned in about 5 billion threads, USB debugging has nothing to do outside of a booted OS.
Fix your drivers.
Unzip the factory image archive.
Sent from my Nexus 5
^Fixed my drivers (via SDK). PC recognised the device via fast boot devices. Ran a set of commands fast boot erase boot, cache, recovery, system, and user data. Flashed boot loader and reboot boot loader. Flashed 4.3 factory image (extracted via 7zip). Flashing/Update FAILED (I think the error was 'too mani links') and it went back to a blinking cursor.
@niceguy01 - just wait for CMD to process the entire thing. I was worried as well when I saw the system does not contain boot.sig etc error. Waited for it and started getting some scripts after. Wasn't able to complete the flash though but little steps getting there.
where should i flash radio.img?
boot,bootloader,recovery.system or userdata??see the picture
thanks
None of the above
Sent from my Nexus 5
Pirateghost said:
None of the above
Sent from my Nexus 5
Click to expand...
Click to collapse
thanks:good:
finally i got manage to fix my N7,thanks anyone who help me:good:
-----------thread close------------
i use google nexus toolkit v4 and install sdk drivers
So to make a long story short, I've been stuck on android 4.2.2 for a while now because I changed the Roboto fonts (Roboto Bold, Roboto Italic, and Roboto) After discovering this I went and re-rooted my tablet to put the fonts back on so I could OTA update. I couldn't find the fonts on any font applications that matched the SHA1 checksum, so I plugged my device into the computer to put the files on manually I downloaded earlier. This is where some problems arise. My computer has having some problems with the drivers for some reason, so the only way to move the files on was if I turned USB debugging off. So thats off, and my computer won't register that the device is plugged in. Well now we get to the part of the story where I was using ROM toolbox lite and tried installing all three of the new fonts all at once. Bad idea, I now know. So my device is stuck in a bootloop, and when I try to go into recovery mode it gives me the error: No command set. I have no idea what to do guys. Any help is very much appreciated. It is kind of upsetting how a change in fonts can brick your device.
1. Download and install Nexus Root Toolkit v1.8.0: Nexus Root Toolkit v1.8.0 | WugFresh
2.. Connect to PC and Boot in Fastboot Mode: VOL DOWN + POWER ON
3. In the toolkit, under "Back to stock" tick "Soft-Bricked/Bootloop"
4. Click "Flash Stock + Unroot"
5. When done you will (should) have a working Nexus again.
jase33 said:
1. Download and install Nexus Root Toolkit v1.8.0: Nexus Root Toolkit v1.8.0 | WugFresh[/URL]
2.. Connect to PC and Boot in Fastboot Mode: VOL DOWN + POWER ON
3. In the toolkit, under "Back to stock" tick "Soft-Bricked/Bootloop"
4. Click "Flash Stock + Unroot"
5. When done you will (should) have a working Nexus again.
Click to expand...
Click to collapse
Hello, Thank you for the helpful tip on how to fix this. I tried what you said but a problem appeared making the device fail to apply the factory image. What I am assuming is it was because the root that I used did not make me unlock the bootloader. so i'm doing that now. It should let me flash a factory image after that, right?
UPDATE: I tried unlocking the bootloader, but it didn't work. my device is not being recognized via ADB because I think the drivers are not properly installed, or it could be because USB debugging is not on. So I cannot get to the point where I can unlock my device.
JakeTheOneDude said:
Hello, Thank you for the helpful tip on how to fix this. I tried what you said but a problem appeared making the device fail to apply the factory image. What I am assuming is it was because the root that I used did not make me unlock the bootloader. so i'm doing that now. It should let me flash a factory image after that, right?
UPDATE: I tried unlocking the bootloader, but it didn't work. my device is not being recognized via ADB because I think the drivers are not properly installed, or it could be because USB debugging is not on. So I cannot get to the point where I can unlock my device.
Click to expand...
Click to collapse
I have the same kind of problem. Did you manage to unlock it?
Nexus 7 2012 32GB wifi, Stock, Unlocked, Rooted, TWRP.
I am new to adb, but have used Wug's toolkit in the past. I attempted to sideload the Lollipop OTA zip through through Wug's toolkit. Everything was going well, but for some reason I got an error that stated that there was not enough room to install the update. I figured that was the end of that, but when I tried to reboot, it went straight to the stock recovery, and will not boot past that. Did some poking around in the toolkit, and found I didn't have fastboot anymore. (Also, I did not make a backup, stupid stupid, because I had recently wiped everything, and have the factory images downloaded). So, with the toolkit not getting me anywhere, I decided to try getting back to running through ADB. Read some tutorials, downloaded SDK, get that all set up so I can see where I am at. Command window, Type "adb devices", get "serial # sideload. Tried "adb reboot recovery", got no devices.
Probably should have just stopped but, since I knew I had USB debugging on, and all the newest drivers installed (just ran the toolkit) I figured why not try to sideload from here? Not enough Space again. Tried sideloading OTA 4.4.4(KTU84P) which is what I was running up to this point, and get unexpected contents error in "system/app/basicdreams.apk" "status 7".
Top of screen says:
Android system recovery (3e)
KTU84P
Long story short; Stuck in stock recovery, No Fastboot, Apply update from ADB works, but haven't anything to finish installing.
Thanks for any help, you guys are awesome, and give me way too much info for my own good, obviously.
Got back to working at this. WUG's toolkit fixed it. Just like every answer, in every thread with similar problems said it would. Using the flash stock +unroot and the soft brick/bootloop option. Since i was on Bootloader version 4.23, I flashed 5.0. Not sure what was different this time, as I tried the same process last night.
Anyway, anyone having the same troubles should give that a try.