Screwed up flashing 4.2.2 - Nexus 4 Q&A, Help & Troubleshooting

Last night I flashed a 4.2.2 zip file from one of the threads. I was rooted with TWRP only. I wiped dalvik cache and the file installed fine, then rebooted. On my home screen where the power control widget was it now says "Select a VPN profile to always remain connected to. Network traffic will only be allowed when connected". I thought WTF, so I tried to go into settings and I keep getting a FC. If I cant get into settings to enable usb debugging then I cant flash a stock image and start over. When I try to get into stock recovery I get an android guy with a red triangle and when I try to get into bootloader mode manually the screen just briefly flashes and thats its, nothing else. I think I've tried everything here....

if you made a mistake just get the old 4.2.1 rom from the official google nexus rom site and reflash; then reapply the OTA.
you don't need debugging to re-flash official roms you just need to be in fast boot.
also android guy with red triangle IS the stock recovery you need to press power then vol up to get the options.

noobdeagle said:
if you made a mistake just get the old 4.2.1 rom from the official google nexus rom site and reflash; then reapply the OTA.
you don't need debugging to re-flash official roms you just need to be in fast boot.
also android guy with red triangle IS the stock recovery you need to press power then vol up to get the options.
Click to expand...
Click to collapse
Would you mind elaboratting on how I can flash official roms in fast boot?

Bronk93 said:
Would you mind elaboratting on how I can flash official roms in fast boot?
Click to expand...
Click to collapse
Well, I used this quide. But i was fully stock.. so dont know if its somehow different in your case.

DuudX said:
Well, I used this quide. But i was fully stock.. so dont know about the differences.
Click to expand...
Click to collapse
Yeah, that guide wont work for me because I can't enable USB debugging on my device.

Bronk93 said:
Last night I flashed a 4.2.2 zip file from one of the threads. I was rooted with TWRP only. I wiped dalvik cache and the file installed fine, then rebooted. On my home screen where the power control widget was it now says "Select a VPN profile to always remain connected to. Network traffic will only be allowed when connected". I thought WTF, so I tried to go into settings and I keep getting a FC. If I cant get into settings to enable usb debugging then I cant flash a stock image and start over. When I try to get into stock recovery I get an android guy with a red triangle and when I try to get into bootloader mode manually the screen just briefly flashes and thats its, nothing else. I think I've tried everything here....
Click to expand...
Click to collapse
You don't wipe anything when installing an update just flash the zip file in recovery and let it do its thing. Wiping the dalvik cache is probably what caused your problems.
Her's the thread for flashing a factory image. This will wipe your phone of all data and restore it to factory settings.
http://forum.xda-developers.com/showthread.php?t=2010312

kzoodroid said:
You don't wipe anything when installing an update just flash the zip file in recovery and let it do its thing. Wiping the dalvik cache is probably what caused your problems.
Her's the thread for flashing a factory image. This will wipe your phone of all data and restore it to factory settings.
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
I can't follow that guide because I have no way of enabling USB debugging because everytime I go to settings I get a FC.

You don't need usb debugging. That is an unnecessary step in that guide. You just need to get into recovery from the boot loader, and pick the sideload from adb option and go from there. Granted, this is all with the stock recovery so who knows with the one you have.
Sent from my Nexus 4 using xda premium
---------- Post added at 08:39 AM ---------- Previous post was at 08:34 AM ----------
Yes you can. The guide flat out says enabling debugging is "not required"
Sent from my Nexus 4 using xda premium

Bronk93 said:
I can't follow that guide because I have no way of enabling USB debugging because everytime I go to settings I get a FC.
Click to expand...
Click to collapse
USB debugging isn't required for fastboot. The guide I linked to will flash a factory image putting your phone back into the state it was when you first received it, start with Step C or just go to Step D and see if fastboot recognizes your phone (boot into fastboot, power + volume down and then plug your phone into the pc, then open a command window and type fastboot devices).

Yes you can click the build number in settings 5 times
Sent from my Nexus 4 using xda app-developers app

OK, I was able to send the factoy image occam-jop40d-factory-ca7602f0.tar to the phone however after verifying update package it says installation aborted

Bronk93 said:
OK, I was able to send the factoy image occam-jop40d-factory-ca7602f0.tar to the phone however after verifying update package it says installation aborted
Click to expand...
Click to collapse
I think you're getting that because you already have the update installed even though it was a borked installation it won't install again as it does a version check first. Did you have any nandroid backups made of the old version? First option would be to try and get back into TWRP and restore a backup. If you replaced TWRP with the stock recovery when you updated which happens by default you should be able to flash a custom recovery image in fastboot. By teh way CWM asked if I wanted to keep the custom recovery and root before the rebooting the phone to finish installing the update.

kzoodroid said:
I think you're getting that because you already have the update installed even though it was a borked installation it won't install again as it does a version check first.
Click to expand...
Click to collapse
Im trying to install the factory 4.2.1 image not the 4.2.2 update, any ideas?

Bronk93 said:
Im trying to install the factory 4.2.1 image not the 4.2.2 update, any ideas?
Click to expand...
Click to collapse
I edited my post above to included trying to restore a backup. Do you have any nandroid backups you made in TWRP? Also teh factory image doesn't flash like a zip file.
---------- Post added at 10:28 AM ---------- Previous post was at 10:24 AM ----------
The factory image goes into your tools-platform folder, teh same folder fastboot is in, on the pc and is flashed from fastboot not from the phone. I think that's your problem
https://developers.google.com/android/nexus/images#occamjop40d

Bronk93 said:
Yeah, that guide wont work for me because I can't enable USB debugging on my device.
Click to expand...
Click to collapse
You don't need USB Debugging to be enabled IN ANDROID to use ADB or Fastboot in RECOVERY or Fastboot.
Sent from my Nexus 4 using Tapatalk 2

I was able to fix it, thanks for everyone to helped me out.

Related

Flashing Rom always ends in boot loop?

I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm
could that be the problem? that my cwm is just outdated already?
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.
Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!

[Q] Data not wiping and cannot flash rom

Hi guys
Im currently using Energy rom on romslot1 aa daily rom. I downloaded tripping bean and was trying to install on the stock rom slot. I did factory reset cache wipe dalvik cache wipe and system wipe. But when i tried to install the rom Im getting an error " set_perm - some changes failed " status 7 error ... googled it out and it said to try downloading the rom again. but i downloaded again and did md5 check and it was same and installing still not working. not sure whats wrong. Also i tried to wipe data but im getting an error unable to wipe data. Im guessing somehow these two errors are related?
jcxmej said:
Hi guys
Im currently using Energy rom on romslot1 aa daily rom. I downloaded tripping bean and was trying to install on the stock rom slot. I did factory reset cache wipe dalvik cache wipe and system wipe. But when i tried to install the rom Im getting an error " set_perm - some changes failed " status 7 error ... googled it out and it said to try downloading the rom again. but i downloaded again and did md5 check and it was same and installing still not working. not sure whats wrong. Also i tried to wipe data but im getting an error unable to wipe data. Im guessing somehow these two errors are related?
Click to expand...
Click to collapse
Wiped /system on stock? D'OH!
You're probably bricked...
jcxmej said:
Hi guys
Im currently using Energy rom on romslot1 aa daily rom. I downloaded tripping bean and was trying to install on the stock rom slot. I did factory reset cache wipe dalvik cache wipe and system wipe. But when i tried to install the rom Im getting an error " set_perm - some changes failed " status 7 error ... googled it out and it said to try downloading the rom again. but i downloaded again and did md5 check and it was same and installing still not working. not sure whats wrong. Also i tried to wipe data but im getting an error unable to wipe data. Im guessing somehow these two errors are related?
Click to expand...
Click to collapse
Can you boot into fastboot?
sloosecannon said:
Wiped /system on stock? D'OH!
You're probably bricked...
Click to expand...
Click to collapse
seriously? :crying: .... im such a noob . i actualy am new using safestrap. not sure of dos and donts. anyways what can i do now to make stock slot working.. because now i am using slot1 . i cant flash anything into stock slot.
/EDIT/
Im not sure it is bricked because i was trying different roms and i did flash one rom into stock slot and it did rebooted into the rom but the problem was the launcher kept force closing that i couldnt virtually get anything done.
timpohladthomas said:
Can you boot into fastboot?
Click to expand...
Click to collapse
sorry im not sure. how do boot into fastboot. i am rooted with safestrap recovery only. i can get inside safestrap. i dont have CWM.
Can someone please help me. I cant install on stock rom slot. Im using my daily rom on rom slot1.
jcxmej said:
Can someone please help me. I cant install on stock rom slot. Im using my daily rom on rom slot1.
Click to expand...
Click to collapse
You need to get into fastboot mode but first download Matt's utility 1.20 and follow the interactions.
http://forum.xda-developers.com/showthread.php?t=2249773
to get into AP fastboot mode turn off you're device and hold power+ vol up + vol down and then when you get to a black and white screen use vol down to navigate, scroll down to where it says AP fastboot and press vol up
in Matt's utility it gives you the options to flash stock 4.1.2 in fastboot mode.
it's option 1 I think.
if you decide the option to root you has to be in USB debugging. (phone needs to be booted up)
it would be nice if you unlocked you're device's bootloader, and Flash TWRP recovery. it's a better option than safestrap now anyways good luck.
ktracho13 said:
You need to get into fastboot mode but first download Matt's utility 1.20 and follow the interactions.
http://forum.xda-developers.com/showthread.php?t=2249773
to get into AP fastboot mode turn off you're device and hold power+ vol up + vol down and then when you get to a black and white screen use vol down to navigate, scroll down to where it says AP fastboot and press vol up
in Matt's utility it gives you the options to flash stock 4.1.2 in fastboot mode.
it's option 1 I think.
if you decide the option to root you has to be in IAN debugging. (phone needs to be booted up)
it would be nice if you unlocked you're device's bootloader, and Flash TWRP recovery. it's a better option than safestrap now anyways good luck.
Click to expand...
Click to collapse
Do not use utility version 1.20, unless you have updated to 4.1.2. You will have issues. If you have not updated, you need to use utility version 1.10.
ktracho13 said:
You need to get into fastboot mode but first download Matt's utility 1.20 and follow the interactions.
http://forum.xda-developers.com/showthread.php?t=2249773
to get into AP fastboot mode turn off you're device and hold power+ vol up + vol down and then when you get to a black and white screen use vol down to navigate, scroll down to where it says AP fastboot and press vol up
in Matt's utility it gives you the options to flash stock 4.1.2 in fastboot mode.
it's option 1 I think.
if you decide the option to root you has to be in USB debugging. (phone needs to be booted up)
it would be nice if you unlocked you're device's bootloader, and Flash TWRP recovery. it's a better option than safestrap now anyways good luck.
Click to expand...
Click to collapse
Thanks man. So much to do i guess. But I have a doubt. If I flash stock in fastboot mode using the utility, do i lose the safestrap and the slots and roms in it. I mean if i do this it will be like brand new? and unrooted?
jcxmej said:
Thanks man. So much to do i guess. But I have a doubt. If I flash stock in fastboot mode using the utility, do i lose the safestrap and the slots and roms in it. I mean if i do this it will be like brand new? and unrooted?
Click to expand...
Click to collapse
Please tell me you saw my post above yours and you used the correct utility?
RikRong said:
Please tell me you saw my post above yours and you used the correct utility?
Click to expand...
Click to collapse
I did see your post afterwards. But I havent started doing it because I will lose all my roms n data if i do it. I had got my razr m on 4.1.1 and then i had rooted and installed safestrap and had flashed several roms on the stock slot also. So the rom in the stock slot is 4.1.2. But I cant boot into it. The rom in rom slot 1 (my daily rom) is 4.1.1. So can i use utility 1.20? or should i use 1.10? Whats the difference?
jcxmej said:
I did see your post afterwards. But I havent started doing it because I will lose all my roms n data if i do it. I had got my razr m on 4.1.1 and then i had rooted and installed safestrap and had flashed several roms on the stock slot also. So the rom in the stock slot is 4.1.2. But I cant boot into it. The rom in rom slot 1 (my daily rom) is 4.1.1. So can i use utility 1.20? or should i use 1.10? Whats the difference?
Click to expand...
Click to collapse
If you updated to official Verizon update in stock slot (4.1.2), then you need to use utility 1.20. 1.20 is designed for 4.1.2 and it includes all the fastboot files for 4.1.2. The key here is whether or not you flashed the official update. There are only a couple of 4.1.2 based aftermarket ROMs available, and they're over on DroidRzr.com (cm10.1 doesn't count because it's not a stock based build). If you didn't take the Verizon update and didn't flash any of MHouse's DST or FXZ ROMs, then you should still be on 4.1.1. If you are on 4.1.1, then use the utility version 1.10. Honestly, you just need to get over the fact you're going to lose ROMs and data, and fastboot the phone back to stock. Then, start from scratch. If you have any important data, save it to your external SD or computer. You'll be able to flash everything again, once you have a good, clean stock install. Then, after fastbooting, unlock your bootloader and stop dealing with SafeStrap. Install a custom recovery, and flash until your heart's content.
Yeah my bad, I didn't know it could cause issues. Anyway, it doesn't matter if you lose safestrap because right now unlocking your bootloader and flashing a custom recovery is safer, lol. if you do decide to install a custom recovery make sure you backup you're stock ROM.
If you don't wanna lose your roms and stiff back up with ss and put it on so doesn't take but about 10 mixtures after fastbooting to go back the way it was
Sent from my XT907 using Tapatalk 2

[Q] Nexus 4 problems.

I'm having a big problem with my Nexus 4 here lately. I tried to root it about 2 days ago, and it did not work. So i downloaded TWRP and my computer read it the same as the Nexus 4 root toolkit by WugFresh. I opened TWRP and it asked me to flash or boot (it was on flash), and i think i clicked "Recovery" and it made my Nexus not boot up, it was just at the logo screen. Then i tried to flash TWRP to the bootloader and System and it flashed TWRP, now it won't go into android. It just takes me into the TWRP interface. In the TRWP interface there are 8 options( Install, Wipe, Backup, Restore, Mount, Settings, Advanced, and Reboot). I pressed "Reboot" and i when press System, Recovery, or Bootloader it tells me that the is no OS installed, I've looked up how to install OS back via WugFresh's toolkit, but it's still not working (maybe because I'm on a old computer). So I'm kinda panicking, is there anyone i can call,or take my phone to, or can you guys help PLEASE!?!
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Okay, i'll try that right now..
chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??
Yiddish said:
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??
Click to expand...
Click to collapse
Try install these drivers: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
chromium96 said:
Try install these drivers
Click to expand...
Click to collapse
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?
Yiddish said:
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?
Click to expand...
Click to collapse
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app
chromium96 said:
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app
Click to expand...
Click to collapse
Recovery mode is when the Android is on it's back with a red exclamation over it right??
Yiddish said:
Recovery mode is when the Android is on it's back with a red exclamation over it right??
Click to expand...
Click to collapse
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
Oh, i see. Okay here i go
chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
Okay, it got past the Google screen, now it's been on the multicolored X for about 10 minutes+ not doing anything
chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
How long will i be on the X loading screen??
Yiddish said:
How long will i be on the X loading screen??
Click to expand...
Click to collapse
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Thanks! I think it was just the ROM i chose. I just downloaded Slim Bean, this seems to be working( the startup screen looks cool ) I'm on the "Android is upgrading..." screen and it says "Starting apps." at the moment.
Okay, SlimBean took more than 10 minutes, so i factory reset and tried again, and it's still not booting up. ):
BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Any ideas why it's still not working??
Yiddish said:
Any ideas why it's still not working??
Click to expand...
Click to collapse
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.
BobWalker said:
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.
Click to expand...
Click to collapse
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??
Yiddish said:
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??
Click to expand...
Click to collapse
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.
BobWalker said:
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.
Click to expand...
Click to collapse
Where do i get Gapps??

nexus 7 doesn't startup!!

hi everyone:laugh:,as in the title,if I turn on my nexus he stay on nexus logo freverrrrrrr!!
this photo explain that:
http : // goo.gl /8pb2Q5
delete distances^^
*I tried to flash stock rom by Nexus Root Toolkit,but profitless.
*I also used format factory reset from recovery,but profitless:crying:.
please is there any solution??
**I'm sorry for my English
​
now the device wihtout recovery*_*​
Use nexus root toolkit to temporarily boot into recovery and wipe everything, then flash a ROM, or download a factory image from Google and run the flash-all.bat
Sent from my Nexus 7 using xda app-developers app
datallboy said:
Use nexus root toolkit to temporarily boot into recovery and wipe everything, then flash a ROM, or download a factory image from Google and run the flash-all.bat
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Does not work
salmn23 said:
hi everyone:laugh:,as in the title,if I turn on my nexus he stay on nexus logo freverrrrrrr!!
this photo explain that:
http : // goo.gl /8pb2Q5
delete distances^^
*I tried to flash stock rom by Nexus Root Toolkit,but profitless.
*I also used format factory reset from recovery,but profitless:crying:.
please is there any solution??
**I'm sorry for my English
​
Click to expand...
Click to collapse
Can you get to the bootloader? If so, fastboot flash the factory image.
charesa39 said:
Can you get to the bootloader? If so, fastboot flash the factory image.
Click to expand...
Click to collapse
yes I did,but doesn't work.
salmn23 said:
yes I did,but doesn't work.
Click to expand...
Click to collapse
If you need help we need more than "doesn't work".
What exactly happens? Error message? Does it flash normally but once you reboot goes into bootloop again? Be precise, I know english doesn't seem to be your first language but we need to know more
charesa39 said:
Can you get to the bootloader? If so, fastboot flash the factory image.
Click to expand...
Click to collapse
MidnightDevil said:
If you need help we need more than "doesn't work".
What exactly happens? Error message? Does it flash normally but once you reboot goes into bootloop again? Be precise, I know english doesn't seem to be your first language but we need to know more
Click to expand...
Click to collapse
yes yes "it flash normally but once you reboot goes into bootloop again"
this is my peoblem^_^
Thank you for your response
salmn23 said:
yes yes "it flash normally but once you reboot goes into bootloop again"
this is my peoblem^_^
Thank you for your response
Click to expand...
Click to collapse
After flashing it, did you go into the stock recovery to factory wipe data before booting it up? You have to do this or else you will get stuck at the Nexus bootup screen. Happened to me once. Apparently you have to do this on the Nexus 5 and Nexus 7 because flashing it doesn't properly wipe the partition.
charesa39 said:
After flashing it, did you go into the stock recovery to factory wipe data before booting it up? You have to do this or else you will get stuck at the Nexus bootup screen. Happened to me once. Apparently you have to do this on the Nexus 5 and Nexus 7 because flashing it doesn't properly wipe the partition.
Click to expand...
Click to collapse
Hloo m.charesa,of course I wipe data,partition after flashing many times(I watched the clip in youtube does that),But unfortunately due to the nexus logo.
It seems that the problem is not to activate the USB debugging , because after opening bootloader or installing stock rom returns the device to its origin and must be activate (usb debugging) again .. Question: Is there a way to activate it without the operation the system (because its not operation originally)??​
salmn23 said:
It seems that the problem is not to activate the USB debugging , because after opening bootloader or installing stock rom returns the device to its origin and must be activate (usb debugging) again .. Question: Is there a way to activate it without the operation the system (because its not operation originally)??​
Click to expand...
Click to collapse
USB Debugging is only necessary if you are trying to use ADB when the phone is on and booted into the OS already. It's not necessary when you are in Fastboot mode (at the bootloader). Not sure why it's not working flashing the factory image. This is why I prefer not to use toolkits and do everything manually. That way, you know where things went wrong.

[Q] Help Please!

Hey guys! I'm not a developer. I unlocked the bootloader of my Nexus 4 and rooted it. Along with that i even installed a matrix kernel. So now what happened is my phone wouldn't display anything after starting up but it was connecting to my PC as i had enabled USB debugging mode. But as the phone wasn't starting, i formatted everything except the sd card, cleared the cache and dalvik cache and reinstalled the franco kernel. Even that didn't start so i downloaded CM 11 nightly version and tried to install it, but it didn't get installed. I installed the matrix kernel again and tried to install CM 11 but even then it didn't get installed. Now my phone is stuck on the google logo and the only thing i can do is go to the bootloader, recovery etc. but I can't connect it to my PC as i had factory reset it, the USB debugging had stopped. Basically i just need help in figuring out what should i do. I'm ready to have my phone back to its stock settings and i'm even ready to keep my phone rooted. I just need a way for it to start working. Please guys!! Some help here!!
Don't panic. The first thing you need to do is flash the factory image in fastboot. After you get your phone back then you need to read a lot before you flash anything again
Sent from my Nexus 5 using XDA Free mobile app
hm.madkhn said:
Hey guys! I'm not a developer. I unlocked the bootloader of my Nexus 4 and rooted it. Along with that i even installed a matrix kernel. So now what happened is my phone wouldn't display anything after starting up but it was connecting to my PC as i had enabled USB debugging mode. But as the phone wasn't starting, i formatted everything except the sd card, cleared the cache and dalvik cache and reinstalled the franco kernel. Even that didn't start so i downloaded CM 11 nightly version and tried to install it, but it didn't get installed. I installed the matrix kernel again and tried to install CM 11 but even then it didn't get installed. Now my phone is stuck on the google logo and the only thing i can do is go to the bootloader, recovery etc. but I can't connect it to my PC as i had factory reset it, the USB debugging had stopped. Basically i just need help in figuring out what should i do. I'm ready to have my phone back to its stock settings and i'm even ready to keep my phone rooted. I just need a way for it to start working. Please guys!! Some help here!!
Click to expand...
Click to collapse
Relax!
Download the Nexus 4 factory image from Google and flash it using fastboot from your PC.
This will revert the phone to pure stock unrooted settings and then just try rooting the phone again from there.
Check of your kernel and ROM files were proper, if they were corrupted then it could have lead to the bootloop
rondias18 said:
Relax!
Download the Nexus 4 factory image from Google and flash it using fastboot from your PC.
This will revert the phone to pure stock unrooted settings and then just try rooting the phone again from there.
Check of your kernel and ROM files were proper, if they were corrupted then it could have lead to the bootloop
Click to expand...
Click to collapse
Hey! Thanks for the help but the USB debugging mode in my phone is switched off as i had reset it. So basically i can't connect it to my PC.
It shows under device manager etc but doesn't show in My Computer. I'm running Windows 8 64 bit.
rondias18 said:
Relax!
Download the Nexus 4 factory image from Google and flash it using fastboot from your PC.
This will revert the phone to pure stock unrooted settings and then just try rooting the phone again from there.
Check of your kernel and ROM files were proper, if they were corrupted then it could have lead to the bootloop
Click to expand...
Click to collapse
And by the way, I downloaded CM11 Nightly but it couln't get installed due to some error and before installing the ROM i installed the matrix kernel but after installing, the phone didn't start. It showed the starting animation but did not start the phone up. Can you please tell me how to enable USB Debugging from CWM Recovery? Coz it's stuck on the Google logo and i can't start it, so neither can I enable the USB debugging mode.
Is your recovery up to date? If not please flash the latest one or flash trwp recovery instead. Use adb sideload, since you cant access your usb debugging
hm.madkhn said:
Hey! Thanks for the help but the USB debugging mode in my phone is switched off as i had reset it. So basically i can't connect it to my PC.
It shows under device manager etc but doesn't show in My Computer. I'm running Windows 8 64 bit.
Click to expand...
Click to collapse
You don't need USB debugging for fastboot. Download the factory stuff from google, turn off device, hold volume down and boot up device (i.e. into bootloader), and run the "flash-all.bat" (after extracting the downloaded file) .. This will wipe your data. If you want to keep data, open the flash-all.bat file and remove the "-w" from the last line.
Marvlesz said:
You don't need USB debugging for fastboot. Download the factory stuff from google, turn off device, hold volume down and boot up device (i.e. into bootloader), and run the "flash-all.bat" (after extracting the downloaded file) .. This will wipe your data. If you want to keep data, open the flash-all.bat file and remove the "-w" from the last line.
Click to expand...
Click to collapse
Remove userdata.img too or it will overwrite your apps
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

Categories

Resources