Installed cutom rom now stuck on google screen :( - Nexus 7 Q&A, Help & Troubleshooting

Ive checked other nexus 7 threads... but this isn't the case.
My nexus 7 is stuck on the google Boot I cannot rub Fastboot or recovery from the toolkit .. nothing at all. It cant find the device .
When I plug in the usb it still makes the sound on windows and so on.
It happened when I was prepairing to install a Custom ROM using JROMFlasher..
I followed all the steps, and when it came to install the ROM to the SD card it just rebooted (transferred to quickly I thought)
And then Ever since it has Just been stuck on the google screen.
I am quite pissed :L
Any Ideas?

I would be quite pissed at your self for using a toolkit. this is a Nexus device and is easily unlocked manually with the proper tools that google provides themselves. Boot into fastboot mode (Hold Power and the two volume keys). Once in fastboot mode you can flash a recovery and then once in recovery you can adb push a ROM to the tablet and flash the ROM the correct way. You really should read up on how to do thing manually instead of resorting to the quick and easy method.
Download the zip located here : platform-tools.zip Extract the contents to a folder name the folder Nexus7 or whatever you want.
Once thats done go ahead and open a command prompt window in that folder you can do that by Shift+Right clicking inside the folder and selecting "Open Command Prompt Here" or if on XP then open CMD and
Code:
cd C:\Users\Name-of-User\Desktop\Nexus7
Once in the CMD issue the command
Code:
fastboot devices
To see if the computer recognizes the device in fastboot mode. It should spit out a gibberish looking code with ....... Device at the end.
Then you going to flash the recovery to do that you issue this command
Code:
fastboot flash recovery name-of-recovery.img
inside the zip the openrecovery-twrp-2.3.1.0.img that is what you will put in place of "name-of-recovery.img" it will show on the screen writing recovery when its done hit the volume up button until the "START" Turn to "Recovery Mode." Then hit the power button you will boot into recovery mode. Once in recovery mode place the ROM.zip you want to flash in the same folder as the stuff you extracted to.
Then issue this command
Code:
adb push Name-of-ROM.zip /data/media
Of course you will replace name-of-ROM.zip with the actual name of the ROM you are flashing. Make sure you also have a gapps packaged which can be found on goo.im/gapps/ latest package is gapps-jb-20121011-signed.zip you will want to adb push that as well.
IF all is done correctly you should be able to install that ROM please follow this procedure.
1. Go to Wipe
2. Factory Reset (this will delete all your apps and apps data not the sd card)
3.Wipe Cache Partition
4. Wipe Dalvik Cache
5. Format System
6. Go to install and find the two ROM.zip and Gapps package at the bottom of the root of the sd card (/sdcard0)
7. Select to flash the ROM and then the Gapps
8. Reboot
Click to expand...
Click to collapse
You should be good to go now.

ÜBER™ said:
I would be quite pissed at your self for using a toolkit. this is a Nexus device and is easily unlocked manually with the proper tools that google provides themselves. Boot into fastboot mode (Hold Power and the two volume keys). Once in fastboot mode you can flash a recovery and then once in recovery you can adb push a ROM to the tablet and flash the ROM the correct way. You really should read up on how to do thing manually instead of resorting to the quick and easy method.
Click to expand...
Click to collapse
Your a good man Yeah I'm not claiming to know anything about Android at all I have literally just started looking into how the system works.. But I have learnt from my quick attempt at everything mistake now.. Once again thanks.

QuantumCipher said:
Your a good man Yeah I'm not claiming to know anything about Android at all I have literally just started looking into how the system works.. But I have learnt from my quick attempt at everything mistake now.. Once again thanks.
Click to expand...
Click to collapse
Its all good wrote you up a quick guide follow that and it'll get you back on track .

ÜBER™ said:
Its all good wrote you up a quick guide follow that and it'll get you back on track .
Click to expand...
Click to collapse
It's flashing the Stock now Thanks for your time. And for also sending me in the right direction (Y)

QuantumCipher said:
It's flashing the Stock now Thanks for your time. And for also sending me in the right direction (Y)
Click to expand...
Click to collapse
Not really necessary but alright. remember going back to stock deletes the entire tablet memory So make sure to back up your important data.

ÜBER™ said:
Not really necessary but alright. remember going back to stock deletes the entire tablet memory So make sure to back up your important data.
Click to expand...
Click to collapse
It was formatted anyway there was no Important data .. Actually you maybe able to answer something for me.
When I rooted my Nexus before all this.. It was rooted as I done previous tests.
What do you use to move files to and from the tablet such as root files? As I want to modify the "X" boot logo animation. I noticed it is just a bunch of PNG images that need replacing..

QuantumCipher said:
It was formatted anyway there was no Important data .. Actually you maybe able to answer something for me.
When I rooted my Nexus before all this.. It was rooted as I done previous tests.
What do you use to move files to and from the tablet such as root files? As I want to modify the "X" boot logo animation. I noticed it is just a bunch of PNG images that need replacing..
Click to expand...
Click to collapse
Acutally its a zip of multiple components not just png's. The bootaniamtion.zip as a whole is what makes up that boot up animation. If you want to change the bootanimation you would replace that entire zip with one that you want. And then set the permissions and reboot. Some will even have a flashable. In order to modify system files you need root and a root explorer. There are multiple on the play store i would recommend Root Explorer if you have the money otherwise ES File Manager or Solid Explorer.

Bricked after wiping with twc
When I look for fastboot devices, nothing happens...
where do I go from here?

http://forum.xda-developers.com/showthread.php?p=35777264
Sent from my Nexus 7 using xda premium

Related

flashing custom roms different method.

****IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.****
************* ok so in this root process of flashing custom roms it requires using the recovery menu. my trackball is F***ED up and i cant move it down to select any other option then reboot phone. is there another method of flashing a custom rom rather then using the recovery menu? can i use some sdk tool or cmd to flash this? how about renaming the custom rom to PB0000 or whatever it is than flashing it like i did to get 2.1root? please someone reply im dieing to get wireless tether for my xbox for my roadtrip this weekend please reply!!!!!
Umm, you could possibly make a .img file with the contents of the \system\ folder of the rom and then user "fastboot flash system system.img" to put it on there. Not 100% sure if that'd work, but it should.
Umm, you could possibly make a .img file with the contents of the \system\ folder of the rom and then user "fastboot flash system system.img" to put it on there. Not 100% sure if that'd work, but it should.
One question...
Why?
jcase said:
One question...
Why?
Click to expand...
Click to collapse
my trackball is F***ED up and i cant move it down to select any other option then reboot phone.
Click to expand...
Click to collapse
reading > you
GrdLock said:
reading > you
Click to expand...
Click to collapse
care < you
LOL.
Fastboot 1.5 back in
Return the phone
How about:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot reboot
^^
ill try your method after I get home from school, unless my dad takes me to Verizon. my trackball limits me a lot from what I can do (wish I could drive haha)
Sent from my Eris using the XDA mobile application powered by Tapatalk
I don't know if it would work but you could to run the MR2 RUU and replace the rom.zip with the one for the 1.5 rollback (renamed rom.zip). I think it will probably give you the version difference error but if nothing else works it's worth a shot.
You'll need to use mkyaffs2image to create a .img file of the \system\ folder of the ROM you want to install. Or maybe someone else will make one for you.
haha I'm not that lucky no one would make one for my sped Eris
Sent from my Eris using the XDA mobile application powered by Tapatalk
DISCLAIMER: I accept no responsibility for the outcome of this. I think it will work, but I can't promise anything.
K, you can try this.
Download these files and place them in your SDK's tools directory.
boot.img: http://www.sendspace.com/file/l404hq
system.img: http://www.sendspace.com/file/7eclsz
Open your command prompt and switch to your tools folder. Boot your phone into FastBoot mode. You can either power it down, then hold VolDown + Power, and select fastboot, or type "adb reboot bootloader" and select fastboot.
Now type these commands in your command prompt.
fastboot flash boot boot.img
fastboot flash system system.img
If that works, it'll install my eris21official-root ROM onto your phone. Then you can download the wireless tether app off my website and install it. Be sure first thing you do "adb shell" then "su" and allow the Superuser popup that will come on your phone before you attempt to tether.
i love you expect a donation comming ur way and i brought my droid to verizon and im gettign a free one shipped to my house and i keep mine so im double lucky, i can use that as a text droid if u need me to test any roms or anytihng
next task, how to make vinilla sence flash
WAIT while flashing system.img it says FAILD :remote data length is too large
Palmbxr said:
WAIT while flashing system.img it says FAILD :remote data length is too large
Click to expand...
Click to collapse
Your phone has a warranty. Downgrade fully to 1.5 and call them.
Or, if you want to completely make sure it's void, but have a working trackball, put in a new one.
http://forum.xda-developers.com/showthread.php?t=657468

think i bricked my nexus s please help

ok, i was running 2.3.3 on my ns and finally got it unlocked then i decided to go for it and root it. my biggest mistake was not backing up anything after the unlock and then when i was rooting the phone it got stuck in the google screen
now i can get to the bootload screen but when i go to update from sd; it takes me there but i have nothing to back it up from
ive been trying to figure out a way to load a recovery backup to sd but the pc will not read the sd card anymore...
how can i fix this or am i stuck with an expensive paper weight?
please help
Question: Do you have clockworkmod on it?
(I figure you unocked and roote via adb/Fastboot - but if you can do it some other way and you did here they are]
Get ADB and Fastboot - figure out how the commands work (from Terminal/console/Command Prompt).
U need to put the files u want to flash (*.imgs in the same place as fastboot/ADB unless you're good a remembering your paths, if you have OS X simply drag and drop commands and files into terminal)
See if you can find a clockwork recovery image,
Download a stock rom - report back
Basically:
fastboot flash boot example.img
Fastboot flash recover example-recovery.img
that should work. I'll keep an eye on this thread.
After flashing CWR, go to mounts and storage and select mount USB storage, from there you can access your sdcard and copy files over.
The USB storage might take a minute or so to show up on your computer, if you're on windows go to my computer and click refresh until it shows up.
Sent from my Nexus S using XDA Premium App
been trying all day to do this and i cant seem to figure out the command prompt...as many times as i try cant get it to get anywhere.....tomorrow i will post pics of what the phone shows on screen
thanks for all the help
i do have a clockwork recovery but , not in the phone
i know that doesnt do any good and i did move files to adb but still would not do anything
redlilcivic said:
i do have a clockwork recovery but , not in the phone
i know that doesnt do any good and i did move files to adb but still would not do anything
Click to expand...
Click to collapse
Are you on a windows PC? If so I can give you all the files necessary and step by step instructions to fix your phone.
Sent from my Nexus S using XDA Premium App
yes i am on windows pc
please send if you can today ....i will not go to sleep until i have this phone up and running again
thanks
redlilcivic said:
yes i am on windows pc
please send if you can today ....i will not go to sleep until i have this phone up and running again
thanks
Click to expand...
Click to collapse
Here are the steps to get your phone back up and working:
1.Download this platform-tools.zip and extract it to your desktop
2.Connect your phone to the PC and enter bootloader mode
3.Press and hold Shift while right-clicking the folder you extracted 'platform-tools'
4.Click 'Open command window here' from the pop-up menu. cmd.exe window will open.
5.If the Bootloader is Unlocked continue to the next step. Type in the cmd.exe window 'Fastboot oem unlock' and follow the steps on the phone screen.
6.Type in the cmd.exe window 'fastboot boot cwr.img'.Your phone will restart and enter ClockWork recovery(CWR).
6.In CWR navigate with the volume keys and highlight 'mounts and storage' and select it by pressing the power button.
7.Then navigate down and select 'mount USB Storage'
8.On your PC, go to 'My computer' and press the refresh button until a 'removable disk' drive appears.
9.Double click on 'removable disk', You now have access to your SDcard on your phone!
10.Copy over a flashable .Zip Rom to the SDcard that you want to install on your phone, ie. Stock 2.3.4: Link(only for i9020T and i9023, dont install if you have i9020A), CM7: Link, etc.
11.Select 'unmount' in CWR when done copying files over. Then 'Go Back' to go to the CWR main menu.
12.Select 'wipe data/factory reset' in CWR and confirm with 'yes'
13.Select 'install zip from sdcard', then select 'choose zip from sdcard', then select the zip file you want to install and confirm.
14.Wait until the Rom installation is complete, then 'select reboot system now'.
15.Your phone will reboot and be up and running! Custom Roms tend to take longer to boot so be patient.
Let me know what happens.
WOW !!!
you are the man , i so appreciate it so much !!!
a couple of little things thoug....the android market not in the system and now when i try to mount the phone memory thru the pc wont mount.... do you know why?
thank you so much for all of your help !!!
redlilcivic said:
WOW !!!
you are the man , i so appreciate it so much !!!
a couple of little things thoug....the android market not in the system and now when i try to mount the phone memory thru the pc wont mount.... do you know why?
I suggest flashing cm7 stable.
thank you so much for all of your help !!!
Click to expand...
Click to collapse
Are you using CM7 nightly? I think it has a USB mount bug and the google apps including market are not in the CM7 rom and have to be flashed separately from the rom.
Sent from my Nexus S using XDA Premium App
USB Storage won't mount
The usb storage isn't showing up after I run cwm
Another restoration method you could try is using Odin to flash back to stock and retry the whole root process step by step ....I am on my phone right now so its hard for me to dig for threads but I know there are instructions and a stock Odin image floating about
Sent from my Nexus S using XDA App
ok my nexus is bricked and i followed the steps above with no luck. my pc wont recognize my phone, i can access clockword mod, but when i click mount usb storage nothing happens. im stuck at the google screen.
nickcash said:
ok my nexus is bricked and i followed the steps above with no luck. my pc wont recognize my phone, i can access clockword mod, but when i click mount usb storage nothing happens. im stuck at the google screen.
Click to expand...
Click to collapse
can you get into fastboot(power on pressing the volume up button and the power button together)?
simms22 said:
can you get into fastboot(power on pressing the volume up button and the power button together)?
Click to expand...
Click to collapse
yes, i can access clockwork mod also, but it the usb storage wont show up.....
Follow these instructions:
1. Slap self in head.
2. Power on phone while holding volume up&power button.
3. Now on the pc, Get the fastboot folder to the root of hard drive, I.E. C:\fastboot\. Also add to this folder your *.img files (radio, recovery, boot, system, data, etc.)
4. Open start menu.
5. In search box type cmd and press enter.
6. Now command window is open, type in that
cd C:\fastboot
fastboot flash * *.img
Replace the * with appropriate .imgs.
recovery, system, data, boot, radio.
Example
fastboot flash recovery recovery.img
7. Now that that is finished type
fastboot -w
fastboot reboot
8. Now the phone will reboot. BE PATIENT AS THIS MAY TAKE UP TO TEN MINUTES TO FULLY REBOOT INTO ANDROID!!! Disturbing it in anyway can cause corruption. I had this happen to my phone before. Literally walk away and come back in ten. Don't touch it, don't breath on it nothing. If you have any further problems either post here or PM me. Getting the .img files and fastboot is up to you. By the previous replies you should have them already.
Sent from my Nexus S using XDA Premium App
nickcash said:
ok my nexus is bricked and i followed the steps above with no luck. my pc wont recognize my phone, i can access clockword mod, but when i click mount usb storage nothing happens. im stuck at the google screen.
Click to expand...
Click to collapse
I think I had the same problem. first you need to check if your pc has the correct driver to accept the nexus s in bootloader mode. when that is done and you have colckword mod , you can but a custom rom on the sd card and flash that, then you'll be able to use your phone again.

[Q] phone won't boot....please help!

Last night I was using my Nexus 4 and it wouldn't connect to any web pages so I thought I'd reboot to see if that fixed it. I powered off then back on and it won't get past the Nexus logo on the start up screen.
I'm unlocked and rooted but haven't installed any Roms ever. I used Wug's toolkit to root.
the only thing I can think of is that I was copying fonts from the system folder and maybe I moved a font instead of copying it, but I really don't think moved anything without replacing. Either way, i really don't think that moving a font would cause the phone to not boot up.
The phone booted up just fine an hour or so before this happened, so the font thing is the only thing I can come up with. I tried to use Wug's toolkit to push the font file to the N4 but the script gets stuck when trying to reboot.
Please help!! any suggestions?
------
addt'l info:
CWM not installed, phone does not bootloop, just gets stuck at X
nvillamob said:
Last night I was using my Nexus 4 and it wouldn't connect to any web pages so I thought I'd reboot to see if that fixed it. I powered off then back on and it won't get past the Nexus logo on the start up screen.
I'm unlocked and rooted but haven't installed any Roms ever. I used Wug's toolkit to root.
the only thing I can think of is that I was copying fonts from the system folder and maybe I moved a font instead of copying it, but I really don't think moved anything without replacing. Either way, i really don't think that moving a font would cause the phone to not boot up.
The phone booted up just fine an hour or so before this happened, so the font thing is the only thing I can come up with. I tried to use Wug's toolkit to push the font file to the N4 but the script gets stuck when trying to reboot.
Please help!! any suggestions?
------
addt'l info:
CWM not installed, phone does not bootloop, just gets stuck at X
Click to expand...
Click to collapse
do a factory reset via recovery
by copying system fonts which are not made for jb, your system could be damaged and thats the reason why you are in a bootloop..
What font did you push and how?
Sent from my HTC6435LVW using Tapatalk 2
pa.pn2 said:
do a factory reset via recovery
by copying system fonts which are not made for jb, your system could be damaged and thats the reason why you are in a bootloop..
Click to expand...
Click to collapse
I'd really like to avoid doing a factory reset if possible, but that may be inevitable.
What I did was copy (move?) fonts from the system folder to a folder on the sd card so the fonts would be accessible to something I was making in UCCW.
When I boot into recovery all I see is the Android laying on its back with a red triangle and beneath that it says "No command."
And this is why you don't use a toolkit. It gives you ability to do things when you didn't know how to get there.
You should just factory reset and get your phone booting. I don't think you're in a position to be trying to save your data because you did things without know what was going to happen. Don't ever touch things in system unless you truly know what you're doing. Especially not without a nandroid backup.
Sent from my Nexus 4 using xda premium
I'm in over my head now, but I knew what I was doing at the time. I *think* I moved a ttf file instead of copying it. A brain fart led to all this. Live and learn and hopefully the community can help me out.
I do have a nandroid from a couple weeks ago that I'd be happy to flash but I'm not familiar with adb but I'm willing to give it a shot if anyone could help. Google hasn't brought me much luck.
nvillamob said:
I'm in over my head now, but I knew what I was doing at the time. I *think* I moved a ttf file instead of copying it. A brain fart led to all this. Live and learn and hopefully the community can help me out.
I do have a nandroid from a couple weeks ago that I'd be happy to flash but I'm not familiar with adb but I'm willing to give it a shot if anyone could help. Google hasn't brought me much luck.
Click to expand...
Click to collapse
Best thing I can say is to fastboot flash back to stock. Google on how to do it, there's a guide on XDA on how to restore factory stock images.
Start all over as if you just got your phone and don't do the same mistakes again. Spend the 25-30 minutes and read how to use fastboot, and don't do things without asking or thinking beforehand. If you don't know what you're going to be modifying or whatever, don't do it.
You don't flash a nandroid. You restore it via recovery in recovery mode.
So I booted into recovery, chose wipe data/factory reset.
After that runs, I reboot the phone and I'm still stuck on the X.
I've got the factory image tgz file but I don't know how to flash it
nvillamob said:
So I booted into recovery, chose wipe data/factory reset.
After that runs, I reboot the phone and I'm still stuck on the X.
I've got the factory image tgz file but I don't know how to flash it
Click to expand...
Click to collapse
Use search + read stickies in the future.
Here is the thread you're looking for, http://forum.xda-developers.com/showthread.php?t=2010312
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10l.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.33.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional (NOT optional for n00bs) -- Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Click to expand...
Click to collapse
the files within the tgz will contain those imgs that you need. you may skip on fastboot flashing the radio, recovery, bootloader
do flash the system and boot flash for sure.
thanks again. I must be awful at searching because I can never find what I'm looking for.
In the mean time, I figured out how to use the toolkit to flash the stock image and I'm back in business. i sincerely appreciate the help.
nvillamob said:
thanks again. I must be awful at searching because I can never find what I'm looking for.
In the mean time, I figured out how to use the toolkit to flash the stock image and I'm back in business. i sincerely appreciate the help.
Click to expand...
Click to collapse
It's all good, I mainly use Google and type random tags on google like "how do i restore nexus 4 back to stock" or something between those lines and something would pop up. In general, Q&A there are stickied threads that has an index with a link to all the other pages that you're looking for.
It all comes with experience.
Errrrrrrr. Um.... you kinda killed me when you said toolkit. Don't use them it's what got you in this situation in the first place. Learn from your mistakes. The toolkit didn't necessarily bring you to this situation but you're not familiar with what the toolkit is actually doing and you're doing changes to the system because you aren't aware of what's going on in your surroundings.
http://forum.xda-developers.com/showthread.php?t=1469909 is a good thread on why you don't use toolkits. How do you think I know all this knowledge? Certainly not by using a toolkit. You have to know how to do these things, otherwise the next problem you'll have you'll ask questions some more. Please just take the time and read it and figure it out how to do it. It's not difficult by any means.
Good luck and glad I can help. I hope I could change your mind on the dangers of using toolkits and do it the traditional way with backgrounds of why you're doing this and that. If everyone used a toolkit then no one would be in Q&A forums could help others, like myself. If i used a toolkit, i wouldn't know how to fix your situation either. Thanks.

[Q] Factory image restore fail : stuck at writing system

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.

Stuck In BootLoop While updating lollipop

i used nexus root tool kit to update nexus 4 from 4.4 to 5.0... all done in pc but mobile is stuck in boot loop. can anyone tell me how can i restore my phone to normal working...
Please help me i am noob here
is there any one who can help me here
i thought i will get ans with in 1hr... still waiting if someone can help
letsnexus said:
i thought i will get ans with in 1hr... still waiting if someone can help
Click to expand...
Click to collapse
This is why we don't recommended using tool kits. You should try flashing the factory image using fastboot.
Sent from my Nexus 9 using XDA Free mobile app
Same here, i tried re-flashing many times. Darn that nexus root toolkit
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
I am currently in the same position ! Used a toolkit too, always have.
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follows.
1. Download factory image
2. Download ADB files
3. Make a folder and extract the adb files and factory image inside the same folder.
4. Plug the phone in bootloader mode or simply type adb reboot bootloader (Developer options must be enabled and USB Debugging) by exiting the folder, holding shift, right clicking the folder and pressing open command window and typing the command.
5. Every factory image comes with a flashall.bat, double click it and voila. Updates like it should. (User data will be wiped)
If you don't want your userdata to be wiped, simply open flashall.bat with notepad++, erase the '-w' in "fastboot -w update image" and save the file and launch it again.
Sent from my HTC One_M8 using Tapatalk
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
hazwheel said:
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
Click to expand...
Click to collapse
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
letsnexus said:
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
Click to expand...
Click to collapse
although the link is for kitkat but the same method applies to flashing lollipop
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
moorthidaniel said:
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
Click to expand...
Click to collapse
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
hazwheel said:
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
Click to expand...
Click to collapse
OK great. Cheers, I helped someone today in this forum.
bett3rthan said:
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
Click to expand...
Click to collapse
That did NOT work for me, the getting into recovery and wiping the device DID work though.
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
moorthidaniel said:
OK great. Cheers, I helped someone today in this forum.
Click to expand...
Click to collapse
Yes, Thanks, unfortunately, she has withdrawn the offer of an early upgrade :silly:
thax
Misledz said:
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follow
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you alot, you help in really good manner
and teached us not to use toolkit
will learn more abt rooting and flashing thank you once again
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Tried going to boot-menu and did factory reset and it booted good after ~10 mins.
sububack said:
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Click to expand...
Click to collapse
Power off, hold Vol Down + Power, when you get to the Android laying down, press volume up + pwr, then wipe the /cache from the menu (you do not need to do a full factory wipe, just wiping cache will do), and then reboot and wait. It will boot this time properly. @WugFresh is aware of the issue and said will put a fix in 1.9.9 for the N4
Thanks , I have tried clearing the cache and started waiting for an hour. Since it was still looping tried after factory reset/wiping user data. And then after 10min it came good.
I post this on Google Product Forum 2 days ago. Hope it helps
https://productforums.google.com/fo...ce=footer#!msg/nexus/Lv8fHtyJOPQ/wDzRUm4b2UsJ
(updated 29/11/2014)[not perfect but it is a SOLUTION]
The idea of this is to downgrade your nexus 4 without wiping your data, which means stuff you will need includes:
1. adb and fastboot on your computer (I am using mac but you can find it on windows as well. There are tones of website and forums telling you the latest method of getting it onto your computer)
2. factory image of nexus 4(I use 4.4.4, since that's what it was. I don't have the time and energy to try to do the same thing with lollipop. you can try can leave a comment).
update: do NOT try to flash 5.0 rom using this method. You will be stuck at boot loop again
3. usb cable
4. nexus 4 with unlocked bootloader(the process of unlocking bootloader will wipe your device)
5. computer
steps
1. unzip the factory image (something.tgz)
2. for me, after unzipping the .tgz, I still find another .zip inside. unzip that too.
3. hold vol+, vol-, and power button simultaneously to enter fastboot mode
4. open terminal(mac)(it would probably be cmd for windows)
5. connect your nexus 4(in fastboot)
6. to make sure it connect successfully, type "fastboot devices". if something like "005040c0d54bb291 fastboot" appears, you are good. Otherwise, try reconnect your device/boot to fastboot again/use another usb cable
7.now we need to tell the terminal to navigate to the location of the unzipped factory image. to do that, i suggest you put the unzipped folder to somewhere easy to find, like desktop. these are some commands to help you navigate:
"ls" allows you to look at whats inside the current directory of the terminal. For example, this is the output after typing "ls" for me:
some folder Photos
nexus4image.tgz how many folders do you have
5.zip occam-ktu84p
more folder occam-ktu84p.zip
after knowing where you are, use "cd" (below) to go to your folder
"cd" means change directory. For example. "cd Photos" will brings me to the "Photos" folder. And then if I type ls, I will see a whole bunch of photos in my photos. If you go to the wrong folder, type "cd ..", and it will bring you back to the previous folder.
8. flash bootloader.
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash bootloader bootloader-mako-makoz30d.img
9. reboot bootloader. just copy and paste
fastboot reboot-bootloader
10. flash radio
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
11. reboot bootloader. just copy and paste
fastboot reboot-bootloader
12. flash system
system.img is located inside the zip, use ls to help you navigate. This steps takes the longest time, total time on this step is 87 seconds while the others are less then 1 second
fastboot flash system system.img
13. flash boot
boot.img is located inside the zip, use ls to help you navigate.
fastboot flash boot boot.img
14. flash recovery
fastboot.img is located inside the zip, use ls to help you navigate.
fastboot flash recovery recovery.img
15. format cache(not the memory, so everything should be fine)
fastboot format cache
16. reboot and wait
this will reboot your device. You probably have to wait for a while to initialise all the apps. after than you are good to go!
fastboot reboot
credit: my friend for giving me this idea + http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 + HelpMyNexus

Categories

Resources