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
Related
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.
i have tried to install a custom rom on my nexus but failed as when i meant to factory reset i deleted everything from my sd card (internal memory) so all i have is TWRP (team win recovery project) and fastboot and nothing else. also i cannot connect my nexus to my pc so i cant flash a new rom on to the device. PLEASE some one help me!
Did you make a backup? You can also use any of the multiple toolkits available to you to reload the stock ROM. Also, questions should be in the QA section to avoid clutter.
Sent from my Nexus 7 using xda premium
graydiggy said:
Did you make a backup? You can also use any of the multiple toolkits available to you to reload the stock ROM. Also, questions should be in the QA section to avoid clutter.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
can you show me the tools (i am a noob at android) or maybe help me in skype or team viewer?
Get an OTG cable and load the Nexus 7 factory image from a USB drive.
kevinperyea said:
i have tried to install a custom rom on my nexus but failed as when i meant to factory reset i deleted everything from my sd card (internal memory) so all i have is TWRP (team win recovery project) and fastboot and nothing else. also i cannot connect my nexus to my pc so i cant flash a new rom on to the device. PLEASE some one help me!
Click to expand...
Click to collapse
Do you have the stock charger? That cable works for connecting to PC.
http://forum.xda-developers.com/showthread.php?t=1766475
This is your best bet.
Boot into recovery and mount then copy across your chosen Rom from your pc and flash
Sent from my HTC One X using xda premium
Easy way out
kevinperyea said:
i have tried to install a custom rom on my nexus but failed as when i meant to factory reset i deleted everything from my sd card (internal memory) so all i have is TWRP (team win recovery project) and fastboot and nothing else. also i cannot connect my nexus to my pc so i cant flash a new rom on to the device. PLEASE some one help me!
Click to expand...
Click to collapse
i always use this method to flash roms as it cuts the hassel of copying the rom into the device for flashing and its very easy actually......just Follow these Steps.. :fingers-crossed:
Download Wug' Nexus Toolkit
Install it and Boot your device into TWRP recovery
Now (assuming that you have Proper Nexus 7 drivers) Open the Toolkit and connect you device to the PC.
Now click the launch button under "Advanced Utilities"
On your device click advanced and the ADB Sideload.
Check mark Wipe Dalvik Cache and Wipe Cache and Swipe to start Sideload.
Now on your PC, click 'sideload update' under "ADB Sideload Update".
Click ok in the next pop-up and now Browse to the custom Rom that you want to flash.
The rom will be uploaded to your device temporarily for flashing and then it will be DELETED once it is Flashed.
This can take upto 30minutes depending on your computer's SPEED.
The rom will be flashed and the device will boot up.
I AM NOT RESPONSIBLE IF YOUR DEVICE BREAKS, OVER HEATS, OR YOU SPILL COFFEE ON IT. DO THIS AT YOUR OWN RISK..!!!
HIT THANKS IF I HELPED...
hassam_tariq2003 said:
i always use this method to flash roms as it cuts the hassel of copying the rom into the device for flashing and its very easy actually......just Follow these Steps.. :fingers-crossed:
Download Wug' Nexus Toolkit
Install it and Boot your device into TWRP recovery
Now (assuming that you have Proper Nexus 7 drivers) Open the Toolkit and connect you device to the PC.
Now click the launch button under "Advanced Utilities"
On your device click advanced and the ADB Sideload.
Check mark Wipe Dalvik Cache and Wipe Cache and Swipe to start Sideload.
Now on your PC, click 'sideload update' under "ADB Sideload Update".
Click ok in the next pop-up and now Browse to the custom Rom that you want to flash.
The rom will be uploaded to your device temporarily for flashing and then it will be DELETED once it is Flashed.
This can take upto 30minutes depending on your computer's SPEED.
The rom will be flashed and the device will boot up.
Click to expand...
Click to collapse
Cuts the hassel of copying the rom into the device... how hard is it to copy a zip file from your computers download folder to your device download folder? I found it to be much easier to have all my flashables on my device for reflashing with MultiRom without the need of my computer. The majority of the time just flashing the ROM will not be sufficient; flashing gapps and patches is also needed for it to work properly. And I think it would be extremely concerning if it took up to 30 minutes, even if the computer used was USB 1 with 3400 RPM IDE hard drive. It would not be possible to use a toolkit as his device is unrecognized by his computer, does not have the proper ADB interface driver needed to interact with the toolkit and does not have USB debugging enabled.
Username invalid said:
Cuts the hassel of copying the rom into the device... how hard is it to copy a zip file from your computers download folder to your device download folder? I found it to be much easier to have all my flashables on my device for reflashing with MultiRom without the need of my computer. The majority of the time just flashing the ROM will not be sufficient; flashing gapps and patches is also needed for it to work properly. And I think it would be extremely concerning if it took up to 30 minutes, even if the computer used was USB 1 with 3400 RPM IDE hard drive. It would not be possible to use a toolkit as his device is unrecognized by his computer, does not have the proper ADB interface driver needed to interact with the toolkit and does not have USB debugging enabled.
Click to expand...
Click to collapse
Hey....Cool Down Bro..
Everybody has different opinions about everything and i am not imposing it, I am just suggesting.
Username invalid said:
Cuts the hassel of copying the rom into the device... how hard is it to copy a zip file from your computers download folder to your device download folder? I found it to be much easier to have all my flashables on my device for reflashing with MultiRom without the need of my computer. The majority of the time just flashing the ROM will not be sufficient; flashing gapps and patches is also needed for it to work properly. And I think it would be extremely concerning if it took up to 30 minutes, even if the computer used was USB 1 with 3400 RPM IDE hard drive. It would not be possible to use a toolkit as his device is unrecognized by his computer, does not have the proper ADB interface driver needed to interact with the toolkit and does not have USB debugging enabled.
Click to expand...
Click to collapse
This wouldn't help at all considering that it looks like OP panicked and did a full internal wipe.
OP, if you have TWRP working I would suggest booting into TWRP, going to Advanced > ADB sideload and then find the ROM zip you were trying to install, then open up command prompt and use adb sideload <path-to-zip> (how exactly you go about doing this last step depends on where you get adb-- any of the previously linked toolkits should include an adb.exe file though that you can run).
Rirere said:
This wouldn't help at all considering that it looks like OP panicked and did a full internal wipe.
OP, if you have TWRP working I would suggest booting into TWRP, going to Advanced > ADB sideload and then find the ROM zip you were trying to install, then open up command prompt and use adb sideload <path-to-zip> (how exactly you go about doing this last step depends on where you get adb-- any of the previously linked toolkits should include an adb.exe file though that you can run).
Click to expand...
Click to collapse
I was replying to the other persons comment, not to the OP. Obliviously he would not be able to connect his device to the computer and use a toolkit.
I'll try to make this brief.. long-time lurker, first time poster.
My Nexus 4 currently is in a brick state. I had PA 3.99 RC2 installed, and when attempting to flash a new font file, the device will now no longer boot, stalling at the boot logo. I foolishly did not make a back-up (though I thought I did.. probably tapped the wrong button). From that point, I tried a data wipe as well as a cache/dalvik cache wipe, and the same thing happens.
I have an old back-up (about a week or 2) on my phone from a different ROM (I believe MIUI) but when I attempt to restore it with Clockwork Mod Recover I get an "md5 mismatch error."
Currently, I do not have the proper Nexus 4 drivers on my computer - when I plug my device in, it does not show up for me to drag/drop anything in to it to flash it. Is it still possible to install the proper USB drivers in its current state?
I plan to try installing the drivers and android SDK and then sideloading a ROM onto it with ADB, but I'm not sure if I'll be able to install the drivers properly for the phone to show up on my computer, and I won't be able to check until I get back to my desktop computer (my laptop has restricted privileges so I can't install drivers) until tomorrow.
Anyone else have any other ideas or suggestions? Please let me know.
Kirbyscream said:
I'll try to make this brief.. long-time lurker, first time poster.
My Nexus 4 currently is in a brick state. I had PA 3.99 RC2 installed, and when attempting to flash a new font file, the device will now no longer boot, stalling at the boot logo. I foolishly did not make a back-up (though I thought I did.. probably tapped the wrong button). From that point, I tried a data wipe as well as a cache/dalvik cache wipe, and the same thing happens.
I have an old back-up (about a week or 2) on my phone from a different ROM (I believe MIUI) but when I attempt to restore it with Clockwork Mod Recover I get an "md5 mismatch error."
Currently, I do not have the proper Nexus 4 drivers on my computer - when I plug my device in, it does not show up for me to drag/drop anything in to it to flash it. Is it still possible to install the proper USB drivers in its current state?
I plan to try installing the drivers and android SDK and then sideloading a ROM onto it with ADB, but I'm not sure if I'll be able to install the drivers properly for the phone to show up on my computer, and I won't be able to check until I get back to my desktop computer (my laptop has restricted privileges so I can't install drivers) until tomorrow.
Anyone else have any other ideas or suggestions? Please let me know.
Click to expand...
Click to collapse
Adb works in recovery, so you can install adb drivers, then use "adb push" or "adb sideload". Try installing the same ROM version you had before (PA). It might work, and also save your data.
abaaaabbbb63 said:
Adb works in recovery, so you can install adb drivers, then use "adb push" or "adb sideload". Try installing the same ROM version you had before (PA). It might work, and also save your data.
Click to expand...
Click to collapse
Took awhile to get ADB drivers to work (fastboot was recognizing it fine)... pushed over the .zip file and just installed it, and everything works great! Thank you!
Nexus 7 was running slow. I had Teamwin recovery on the device and was stock 4.3 unlocked/partially rooted. Booted device into recovery and wiped cache, dalvik, usb otg, sd int, and sd ext, and data. Teamwin somehow remained. While trying to use WugFreshs tool I must have restored the recovery to stock...maybe. The device is now always on and will not turn and you cannot get into recovery but you can reboot and get to the bootloader. At this point I tried the flash stock/unroot soft-brick feature of Wugfresh and it does not work even if I enabled Force Flash Mode.
Tried doing this thru adb but have limited adb skills and with the instructions I was following it assumed USB debugging was enabled (my device was wiped so not sure about that).
Any help will be greatly appreciated! Thank you!
yagermeister said:
Nexus 7 was running slow. I had Teamwin recovery on the device and was stock 4.3 unlocked/partially rooted. Booted device into recovery and wiped cache, dalvik, usb otg, sd int, and sd ext, and data. Teamwin somehow remained. While trying to use WugFreshs tool I must have restored the recovery to stock...maybe. The device is now always on and will not turn and you cannot get into recovery but you can reboot and get to the bootloader. At this point I tried the flash stock/unroot soft-brick feature of Wugfresh and it does not work even if I enabled Force Flash Mode.
Tried doing this thru adb but have limited adb skills and with the instructions I was following it assumed USB debugging was enabled (my device was wiped so not sure about that).
Any help will be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Going to try MSkip's toolkit to see if it helps found here: http://forum.xda-developers.com/showthread.php?t=2510913
yagermeister said:
Going to try MSkip's toolkit to see if it helps found here: http://forum.xda-developers.com/showthread.php?t=2510913
Click to expand...
Click to collapse
Goo.im that hosts Mskip's image files isn't working so can't auto or manually download everything his tool needs...ideas anyone?
Mine is also knackered, I have no write access at all to the flash memory; i've even tried the wheelie option in flatline and even that can't write to it. I get the impression that all these toolkits really do is run the flashall.batch file that's in the stock recovery downloaded from google. From reading the threads, some seem to have success after flashing dozens of times. So what I'm going to do is loop the flashall.bat and leave it repeatedly flashing for a few hours. I'd also use the second most recent stock firmware to easily avoid the 4.23 bootloader issue or do what is says in the stock flashing thread. The extracted downloaded stock roms will be in wugs program files directory, just copy fastboot/adb/ dll files from the main directory and run flashall a few times.
I downloaded MSkip's toolkit a few days ago, so its on here somewhere, But for me it just crashes, doesn't even attempted to flash. Guessing it's a complied batch file which uses fastboot/ adb, so you should be capable of doing anything that it can do.
As per the title, I accepted the system update on my rooted ls980 (didnt know it would mess anything up). Ended up putting me into a boot loop to TWRP recovery. Tried to restore all my backups and none of them yielded a different result. Thought i would try a quick wipe but i accidentally wiped everything... For some reason when i try to install the newest USB drivers it tells me the install worked but never recognized the phone. I have done all the steps in this thread http://forum.xda-developers.com/showthread.php?t=2432476 but not everything installs when plugged in from download mode. Also could not get LGflashtool to register properly. I'm not exactly sure where to go from here, I have no roms, backups, or adb access. what do?
Well if u can boot ur rom into recovery, then connect s pen drive with s flashable rom inside to ur mobile via OTG cable, and then flash
Sent from my LG-D802 using XDA Premium 4 mobile app
i had the same prob. only way out foe me was to flash via sideload