Database Users

Please Help may have accidently wipe stock ROM without a restore point.

1) Used the toolKit to unlock Bootloader
2) install twrp using Toolkit
3) transfered AOKP rom to device using airdroid
4) Went to TWRP, System Wipe 3 times, Clear cache 3 times
5) attempt to flash AOKP ZIP
6) ZIP failed to install no idea why
7) Tried to restart and now stuck at the GOOGLE logo
Please help is there anything i can do?
Hmm could i use the toolkit to flash an img file? Im dling a stock img atm.

First off.. Don't panic ... It wasn't your fault it failed ... I know because it happened to me . don't get it from "downloads" or goomanager .. Get it from the second post I. That thread on the latest date
Second . I don't think otg works in twrp so you will have to use adb to load the ROM
Sent from my Nexus 4 using Tapatalk 2

italia0101 said:
First off.. Don't panic ... It wasn't your fault it failed ... I know because it happened to me . don't get it from "downloads" or goomanager .. Get it from the second post I. That thread on the latest date
Second . I don't think otg works in twrp so you will have to use adb to load the ROM
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I did get it from the second post though, and how can i load into ADB?

italia0101 said:
Second . I don't think otg works in twrp so you will have to use adb to load the ROM
Click to expand...
Click to collapse
OTG does work in TWRP. I have found that it doesn't like some flash drives - no idea why. I've tried quite a few, some of mine work all the time, other just won't work.

adoute said:
OTG does work in TWRP. I have found that it doesn't like some flash drives - no idea why. I've tried quite a few, some of mine work all the time, other just won't work.
Click to expand...
Click to collapse
Ok went to twrp and used the ADB sideload feature but it said OTG cable fail to mount.

FIXED
WOOO FIXED IT NVM! Mod please delete thanks for help guys

Someone with more experience correct me if I'm wrong, but shouldn't we be avoiding wiping system in TWRP prior to flashing ROMs? I believe I read a thread (probably on RootzWiki) that said wiping system messes things up as you lose the ability to flash a ROM in the "traditional" manner. I wipe cache, dalvik, then click factory reset. I leave system alone and I've never had a problem with flashing ROMs.

[Q] Nexus 4 No OS. Only fastboot [SOLVED]

I recently tried to flash PA on my nexus.
Installed cwm on my phone. Then downloaded the PA ROM and moved to the device storage.
Rebooted into CWM and performed all the wipes.
I accidentally wiped the system and the internel partitions too.
when i tried to install ROM from sdcard. it says "NO FILES FOUND"
Iam stuck here. Phone wont boot into Android... any suggestions? please help!

How did you wipe system within CWM?
But since you say you wiped internal partitions too, it seems to me that you wiped your internal emulated sdcard... so I think your only option now is to flash stock images again... Read this: http://forum.xda-developers.com/showthread.php?t=2010312

If you don't want to flash the stock images you can also push a rom to your phone with adb while booted in a custom recovery
adb push nameofrom.zip /sdcard/

Thanks guys. Found a solution.
Flashed TWRP and sideloaded the ROM file. And flashed it.
Earlier the same process with CWM was not successful. Now the phone is loaded with PA ROM!
Thanks guys! and can u point me to the google stock images??

njarun said:
Thanks guys! and can u point me to the google stock images??
Click to expand...
Click to collapse
Glad you solved it
Here are the stock OTA and images from google and mirrored http://forum.xda-developers.com/showthread.php?t=1971169

My dad said he knew how to fix this, and wiped my system, thats all, and now I can't boot. Any help on this?

mrjoeltan said:
My dad said he knew how to fix this, and wiped my system, thats all, and now I can't boot. Any help on this?
Click to expand...
Click to collapse
wiped /system? have you tried simple re-flashing your ROM from the .zip ?

no worry... download the nexus 4 twrp latest img from their site, and flash it to your N4
what you needed:
twrp img file
some n4 rom
adb and fastboot
instructions:
boot to fastboot, vol key down + powerbutton when n4 is off.
on your comp, , dos/terminal - fastboot flash recovery twrp.img
reboot in recovery
select the adb side load from advanced tab in the twrp.
on your comp - adb sideload rom.zip
everything done....reboot phone.
Sent from my Nexus 4 using xda premium

I have a same problem, but when i try to flash a Rom, it`s fail and said that no partition, how can i fix it? Thanks for read.

blackcatvn said:
I have a same problem, but when i try to flash a Rom, it`s fail and said that no partition, how can i fix it? Thanks for read.
Click to expand...
Click to collapse
did you wipe using fastboot erase command? if so, you need to re-format to the android supported file system to access the partitions!
try installing the twrp recovery and perform 'FORMAT DATA' from wipe. then install ROM.

N4 no OS.
njarun said:
I recently tried to flash PA on my nexus.
Installed cwm on my phone. Then downloaded the PA ROM and moved to the device storage.
Rebooted into CWM and performed all the wipes.
I accidentally wiped the system and the internel partitions too.
when i tried to install ROM from sdcard. it says "NO FILES FOUND"
Iam stuck here. Phone wont boot into Android... any suggestions? please help!
Click to expand...
Click to collapse
I need help, having the same problem you had with my N4. Cant seem to fix it. I had PA 3.69 for 3 weeks when I rebooted my N4 i had no OS on the phone. Just my Bootloader and Twrp 2500 was recently 2600 but cant do anything else. ADB works seems to fail when writing to N4. Im trying to get it back to stock. Any Ideas
Axel

Axelben said:
I need help, having the same problem you had with my N4. Cant seem to fix it. I had PA 3.69 for 3 weeks when I rebooted my N4 i had no OS on the phone. Just my Bootloader and Twrp 2500 was recently 2600 but cant do anything else. ADB works seems to fail when writing to N4. Im trying to get it back to stock. Any Ideas
Axel
Click to expand...
Click to collapse
can u get into recovery? did u check changing your USB Cable? The original nexus usb cable sucks, try another one. If you can access the fastboot/adb then it will be pretty simple..

Same problem but...
Hi, I'm having the same problem with my Nexus 4 and I have TWRP V 2.6.3.0 but I'm not sure how to push any rom to my phone because it's not showing up under my computer in Windows. How do I push roms to my Nexus 4? I'm stuck at the Google boot screen when I try to boot (Flashed Dalvik Cache, System, Data, Internal Storage, and normal cache) and I of course don't have any roms on my phone after I wiped all of the partitons. Help me plz
El Daddy said:
If you don't want to flash the stock images you can also push a rom to your phone with adb while booted in a custom recovery
adb push nameofrom.zip /sdcard/
Click to expand...
Click to collapse

Got it working
Hi, I got it to work. No worries guys
xXDustinoXx said:
Hi, I'm having the same problem with my Nexus 4 and I have TWRP V 2.6.3.0 but I'm not sure how to push any rom to my phone because it's not showing up under my computer in Windows. How do I push roms to my Nexus 4? I'm stuck at the Google boot screen when I try to boot (Flashed Dalvik Cache, System, Data, Internal Storage, and normal cache) and I of course don't have any roms on my phone after I wiped all of the partitons. Help me plz
Click to expand...
Click to collapse

njarun said:
can u get into recovery? did u check changing your USB Cable? The original nexus usb cable sucks, try another one. If you can access the fastboot/adb then it will be pretty simple..
Click to expand...
Click to collapse
i cannot get the thing to work this bloody adb command does not seems to work on my Windows 8.1
Can u please give a detailed intruction as i have my file in D Drive so where to keep this zip file

nickboy360 said:
i cannot get the thing to work this bloody adb command does not seems to work on my Windows 8.1
Can u please give a detailed intruction as i have my file in D Drive so where to keep this zip file
Click to expand...
Click to collapse
you got it working? else pm me your mail id. ill send you the necessary files and detailed info, I once composed it for one of my friend!

njarun said:
you got it working? else pm me your mail id. ill send you the necessary files and detailed info, I once composed it for one of my friend!
Click to expand...
Click to collapse
Thanks for asking mate i got it done... :good:

[Q] Nexus 4: Can't wipe/Flash factory image. Semi-bricked phone.

Earlier today my phone was working fine running Stock 4.4.1/Kernel. I decided I wanted to get the franco kernel so I got the .img file from the xda thread. I flashed the .img file onto the boot partition using fastboot, and restarted my phone. After a few minutes of sitting at the "Google" screen I rebooted into the bootloader. I tried flashing the 4.4 factory image using the "flash-all.bat" without wiping anything. My phone continued to get stuck at the "Google" screen after multiple reboots. I then tried to wipe my device using fastboot. However, when using the command "fastboot erase system" I got an error that said "Failed: unknown chunk type." I kept on retrying the wipe to no avail. I found this thread: http://forum.xda-developers.com/showthread.php?t=2347060 and followed the steps. All the steps seemed to work up until I had to flash the given factory image using fastboot. I got the same "Unknown chunk type" when the cmd was trying to write files to the "system partition." Before you ask, yes my fastboot/adb is updated to the newest version. (I triple checked) And all my drivers work properly. I just flashed the 4.4.1 firmware 3 days ago using fastboot and everything went perfectly, including the wipe. Please offer any solutions you think could get me out of this situation. Thank you.

PandemicHD said:
Earlier today my phone was working fine running Stock 4.4.1/Kernel. I decided I wanted to get the franco kernel so I got the .img file from the xda thread. I flashed the .img file onto the boot partition using fastboot, and restarted my phone. After a few minutes of sitting at the "Google" screen I rebooted into the bootloader. I tried flashing the 4.4 factory image using the "flash-all.bat" without wiping anything. My phone continued to get stuck at the "Google" screen after multiple reboots. I then tried to wipe my device using fastboot. However, when using the command "fastboot erase system" I got an error that said "Failed: unknown chunk type." I kept on retrying the wipe to no avail. I found this thread: http://forum.xda-developers.com/showthread.php?t=2347060 and followed the steps. All the steps seemed to work up until I had to flash the given factory image using fastboot. I got the same "Unknown chunk type" when the cmd was trying to write files to the "system partition." Before you ask, yes my fastboot/adb is updated to the newest version. (I triple checked) And all my drivers work properly. I just flashed the 4.4.1 firmware 3 days ago using fastboot and everything went perfectly, including the wipe. Please offer any solutions you think could get me out of this situation. Thank you.
Click to expand...
Click to collapse
Never encountered something like this, but maybe from bootloader u can get into ur stock recovery & wipe cahce & wipe data.
once again I never had that issue...so its upto u...but might be worth a try...if u had made a backup or dont care about the data in ur phone then it did be easier for u u to try

Flash the factory images and erase all partitions on the device. If you want to get some data from the internal memory you could pull it through recovery. Next time read more do less. Franko's kernel uses different ram disk than the stock one. You could also try to flash a full stock kernel for your build first. Get it from the factory images and flash it through fastboot.
Sent from my Nexus 4 using xda app-developers app

i have the exact same problem here ! and i dont know what to do! its still stucked on the google logo!!!

alexvck said:
i have the exact same problem here ! and i dont know what to do! its still stucked on the google logo!!!
Click to expand...
Click to collapse
What's the exact same problem? Did you flash Franko kernel too. If so just dirty flash your current rom.

jd1639 said:
What's the exact same problem? Did you flash Franko kernel too. If so just dirty flash your current rom.
Click to expand...
Click to collapse
no i just had rooted it and loadedcwm and i was ready to flash paranoid anroid rom! and when it rebooted it stuck on the google logo! then i tried to reset my phone and load the official factory image with nexus root toolkit but when it did the usual procces with the command prmpt in some point after trying to write the new system it said "Failed: unknown chunk type." ! after that it rebooted and got stucked again in google logo!!

alexvck said:
no i just had rooted it and loadedcwm and i was ready to flash paranoid anroid rom! and when it rebooted it stuck on the google logo! then i tried to reset my phone and load the official factory image with nexus root toolkit but when it did the usual procces with the command prmpt in some point after trying to write the new system it said "Failed: unknown chunk type." ! after that it rebooted and got stucked again in google logo!!
Click to expand...
Click to collapse
Use this to flash the factory image http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

jd1639 said:
Use this to flash the factory image http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
my device is bricked i cant do these stuff :/

alexvck said:
my device is bricked i cant do these stuff :/
Click to expand...
Click to collapse
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.

jd1639 said:
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.
Click to expand...
Click to collapse
yes i can get in bootloader! but i cant do sth :/ ... whats the emmc ?!

Originally Posted by jd1639<br />
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.
Click to expand...
Click to collapse
<br />
<br />
yes i can get in bootloader! but i cant do sth :/ ... whats the emmc ?!
Click to expand...
Click to collapse
Emmc is the flash memory.

jd1639 said:
Emmc is the flash memory.
Click to expand...
Click to collapse
oo okay.. so is there sth else that i can try?!

alexvck said:
oo okay.. so is there sth else that i can try?!
Click to expand...
Click to collapse
have you tired the the toolkits?

I had problem with flash system.img, solved changing usb port. I hope help you.
Inviato dal mio Nexus 4 utilizzando Tapatalk

bootlooping ,flashing twrp or stock doesn't work.

My nexus 6p has been on ressurection remix and elemental kernel for months and it'd been good. Today I was playing a gaming and my device rebooted then i thought ,well no problem. Then it kept rebooting and the starting animation got choppy until it started rebooting again. I could entered twrp and I try to wipe data and cache , then rebooted. No luck , worse, later i couldn't enter twrp anymore.
So I did:
flash twrp again, flashing went successfully, but recovery mode was not accessible.
flash stock image again, flashing succeeded, device keeps rebooting no recovery mode.
try different twrp, no hope.
I've been messing with android especially with nexii for years. This is the very first time I encounter this weird situation. I thought as long as the fastboot mode is accessible , there's no real brick.
What else can I try?

randy6644 said:
What else can I try?
Click to expand...
Click to collapse
Some users have reported using Skipsoft's Toolkit got them out of a bootloop with only bootloader mode accessible. Flash stock and choose the option to format userdata and cache.

v12xke said:
Some users have reported using Skipsoft's Toolkit got them out of a bootloop with only bootloader mode accessible. Flash stock and choose the option to format userdata and cache.
Click to expand...
Click to collapse
THX. Would you please point me to the threads. I think basically the toolkit does the same thing adb command does. Anyways, thank you for the suggestion, i'll try it out.

randy6644 said:
THX. Would you please point me to the threads. I think basically the toolkit does the same thing adb command does. Anyways, thank you for the suggestion, i'll try it out.
Click to expand...
Click to collapse
If you are comfortable with fastboot and adb, then yes ofc the scripts used by the toolkits are the same. The difference I tried to point out is that Skipsoft FORMATS the partitions. Different from erase. Try fastboot formatting userdata, cache and system as well because you were running a custom rom.

v12xke said:
If you are comfortable with fastboot and adb, then yes ofc the scripts used by the toolkits are the same. The difference I tried to point out is that Skipsoft FORMATS the partitions. Different from erase. Try fastboot formatting userdata, cache and system as well because you were running a custom rom.
Click to expand...
Click to collapse
just tried the toolkit and manually formatting. The same deal. So confused about what is going on with my device.

randy6644 said:
just tried the toolkit and manually formatting. The same deal. So confused about what is going on with my device.
Click to expand...
Click to collapse
I'm not sure why you are confused. The boot loop of death is a known issue on the 6P. There are threads dedicated to it. If you can't RMA your phone it's probably a paperweight.

jhs39 said:
I'm not sure why you are confused. The boot loop of death is a known issue on the 6P. There are threads dedicated to it. If you can't RMA your phone it's probably a paperweight.
Click to expand...
Click to collapse
Yeah, i just went through several threads here and figured that out. Sorry for having posted something that had been already posted here. I hadn't been to XDA for months so I thought my case was the only one. lol

Stop advising to use Skipsoft . If he can't get to TWRP the device is dead.

Not booting

Hey guys question. Ever since yesterday for some reason anything i try to install will not boot. I have tried different roms and cant figure it out. any help would be appreciated. this is my only phone.

What have you tried, what model?
If you used Dirty Santa , I've seen a lot of people able to fix boot issues by following this step in his guide
me2151 said:
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
Click to expand...
Click to collapse

TGtheImmortal said:
What have you tried, what model?
If you used Dirty Santa , I've seen a lot of people able to fix boot issues by following this step in his guide
Click to expand...
Click to collapse
I have tried about 4 different roms and completely wiping and installing. the only thing that works is re flashing my stock backup i made after i rooted. I will try flashing boot2. Do roms change boot images when you flash? I am on the verizon verient.

pcwizkid1994 said:
I have tried about 4 different roms and completely wiping and installing. the only thing that works is re flashing my stock backup i made after i rooted. I will try flashing boot2. Do roms change boot images when you flash? I am on the verizon verient.
Click to expand...
Click to collapse
I'm not sure if you should flash the boot if you're on a custom rom. I am no expert so I don't want to make you brick your device.
Full wipe including formatting data when you are reinstalling custom roms?

TGtheImmortal said:
I'm not sure if you should flash the boot if you're on a custom rom. I am no expert so I don't want to make you brick your device.
Full wipe including formatting data when you are reinstalling custom roms?
Click to expand...
Click to collapse
Yes sir.

pcwizkid1994 said:
Yes sir.
Click to expand...
Click to collapse
Are you getting any errors whilst flashing custom roms?
The only thing I can think of right now would be following the steps from step 4 and reinstall and root a stock Verizon rom to see if it fixes your issue.
If that doesn't work someone else will have to come along and suggest some things.

TGtheImmortal said:
Are you getting any errors whilst flashing custom roms?
The only thing I can think of right now would be following the steps from step 4 and reinstall and root a stock Verizon rom to see if it fixes your issue.
If that doesn't work someone else will have to come along and suggest some things.
Click to expand...
Click to collapse
No nothing. Everything is flashing like it should.

Are /system and /data mounted in TWRP under mount before/after you flash a custom rom?

TGtheImmortal said:
Are /system and /data mounted in TWRP under mount before/after you flash a custom rom?
Click to expand...
Click to collapse
Now I am getting a system mount error when I try to back up my stock Rom... Will check when on break at work

TGtheImmortal said:
Are /system and /data mounted in TWRP under mount before/after you flash a custom rom?
Click to expand...
Click to collapse
Cach and data are the only things mounted

pcwizkid1994 said:
Cach and data are the only things mounted
Click to expand...
Click to collapse
/system definitely needs to be mounted before flash and after flash as well, otherwise it cannot override your stock rom.
Are you getting an error while trying to mount it? Or only during backup procedure? I was able to fix some mounting issues by simply rebooting TWRP.

TGtheImmortal said:
/system definitely needs to be mounted before flash and after flash as well, otherwise it cannot override your stock rom.
Are you getting an error while trying to mount it? Or only during backup procedure? I was able to fix some mounting issues by simply rebooting TWRP.
Click to expand...
Click to collapse
Ok so i went back into recovery and the only way I can get system to be cheacked is if I mount it as read only

TGtheImmortal said:
/system definitely needs to be mounted before flash and after flash as well, otherwise it cannot override your stock rom.
Are you getting an error while trying to mount it? Or only during backup procedure? I was able to fix some mounting issues by simply rebooting TWRP.
Click to expand...
Click to collapse
Hey. I emailed you back. Did you get my pm? Thanx