Hello fellow internet users, I've been trying to resolve a problem I've been having with my Nexus 4 device, but given that I failed, I came here hoping somebody here could help me.
Recently I wanted to update CM Mod on my device (to the latest version supporting Android 4.3), but little did I know that it'd replace my recovery program from TWRP to ClockwordMod. Afterwards I proceeded to install Franco Kernel (r. 193) since from what I read it should have been compatible with my recently downloaded version of CM. After I flashed it, all the tints of blue on my screen turned into tints of orange/yellow (and vice versa). Afterwards I tried to fix it with flashing one of the supposedly stock kernels I found on the internet, however all it achieved was to make it unable for my phone to boot - now when I turn it on in normal mode all I see is a weird blue screen with intermittently flashing pink squares that create a checkered pattern. I tried to access the android root kit to unroot the phone and bring back the default kernel + rom, but so far I've been unable to access my phone from my PC. And in case you wonder, yes, I was stupid enough to not store any backups on the internal storage.
I hope there is a work around it, since I really need my phone to work , thanks in advance to whoever can provide me with some sound advice.
cubeth said:
Hello fellow internet users, I've been trying to resolve a problem I've been having with my Nexus 4 device, but given that I failed, I came here hoping somebody here could help me.
Recently I wanted to update CM Mod on my device (to the latest version supporting Android 4.3), but little did I know that it'd replace my recovery program from TWRP to ClockwordMod. Afterwards I proceeded to install Franco Kernel (r. 193) since from what I read it should have been compatible with my recently downloaded version of CM. After I flashed it, all the tints of blue on my screen turned into tints of orange/yellow (and vice versa). Afterwards I tried to fix it with flashing one of the supposedly stock kernels I found on the internet, however all it achieved was to make it unable for my phone to boot - now when I turn it on in normal mode all I see is a weird blue screen with intermittently flashing pink squares that create a checkered pattern. I tried to access the android root kit to unroot the phone and bring back the default kernel + rom, but so far I've been unable to access my phone from my PC. And in case you wonder, yes, I was stupid enough to not store any backups on the internal storage.
I hope there is a work around it, since I really need my phone to work , thanks in advance to whoever can provide me with some sound advice.
Click to expand...
Click to collapse
It sounds you had flashed a wrong version of kernel for JWR and JSS. If you can boot into recovery, then just download another ROM and save it to your phone. Wipe factory reset and then flash the new ROM.
taodan said:
It sounds you had flashed a wrong version of kernel for JWR and JSS. If you can boot into recovery, then just download another ROM and save it to your phone. Wipe factory reset and then flash the new ROM.
Click to expand...
Click to collapse
Thank you for the swift reply. The problem is, while I can boot into recovery, I can't save anything to my phone right now since I can´t access it from my PC.
cubeth said:
Thank you for the swift reply. The problem is, while I can boot into recovery, I can't save anything to my phone right now since I can´t access it from my PC.
Click to expand...
Click to collapse
Were you able to connect your phone to your PC prior to flashing the CM mod? If yes, then you can mount it while in recovery. If no, then I suggest you might want to spend some time reading the materials which software that you will need in order to connect your phone to your PC.
taodan said:
Were you able to connect your phone to your PC prior to flashing the CM mod? If yes, then you can mount it while in recovery. If no, then I suggest you might want to spend some time reading the materials which software that you will need in order to connect your phone to your PC.
Click to expand...
Click to collapse
Yes, the problem is that I did all the previous operations on another computer (on which nexus usb drivers were installed too), which I'll have access to in around 10 days. I was simply curious whether it is possible to find a workaround the fact that the computer I'm using currently doesn't recognise my device/can't install drivers, regardless of the mode my phone is in (bootloader, recovery or normal).
cubeth said:
Yes, the problem is that I did all the previous operations on another computer (on which nexus usb drivers were installed too), which I'll have access to in around 10 days. I was simply curious whether it is possible to find a workaround the fact that the computer I'm using currently doesn't recognise my device/can't install drivers, regardless of the mode my phone is in (bootloader, recovery or normal).
Click to expand...
Click to collapse
You'll have to install drivers manually.
Your problem is easily fixed. You don't need to wipe anything; that would be unnecessary. All you have to do is flash your ROM again. You can't use custom kernels with cm unless they are made specifically for it.
Sent from my Nexus 7 using Tapatalk
korockinout13 said:
You'll have to install drivers manually.
Your problem is easily fixed. You don't need to wipe anything; that would be unnecessary. All you have to do is flash your ROM again. You can't use custom kernels with cm unless they are made specifically for it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for your advice, I'll try to follow it and see if it works as soon as I've got back home.
Related
Had a problem which I thought was down to spilling wine on my phone (yeh not a good idea) however it may turn out to be the update to 2.3.4. Now the problem is that my computer wont recognise the phone at all and I have tried allsorts and after searching the web it seems the update has derped some peoples phones.
The problem now is that I went back to stock and now cant boot into recovery. Is there a way of putting the recovery img on to the phone via say Awesome drop or an alternative? I am still unlocked but got a stock rom on?
Haizum74 said:
Had a problem which I thought was down to spilling wine on my phone (yeh not a good idea) however it may turn out to be the update to 2.3.4. Now the problem is that my computer wont recognise the phone at all and I have tried allsorts and after searching the web it seems the update has derped some peoples phones.
The problem now is that I went back to stock and now cant boot into recovery. Is there a way of putting the recovery img on to the phone via say Awesome drop or an alternative? I am still unlocked but got a stock rom on?
Click to expand...
Click to collapse
If you still have root access you can use either the flash_image binary or Rom Manager to flash a new recovery.
If you do not then you will need to use fastboot and flash recovery manually.
Use terminal on your phone and flash recovery that way.
Sent from my Nexus S 4G using XDA App
No, not got root (just checked). Not 100% how to go about this if my comp isnt recognising my phone. Any ideas? Cheers
Maybe you could try another computer....or a Mac perhaps? (I have both, when one's acting up, i use the other)
Tried another and the same, it seems strange that it could be the USb port on the phone when its only happened after installing 2.3.4
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
calavera-pw said:
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
Click to expand...
Click to collapse
before you do anything, use your recovery to see if the rom zip is located in /data/media/0/. if its there, flash it from that location.
Are you able to boot into recovery?
If yes, it could be as simple as plugging your tablet into the computer and mounting the usb, drag and drop the rom, and flash it without using a toolkit (only recovery). I'm not familiar with jrom flasher, but i will say the more variables there are, the more chance of a problem.
If no, you're best off running the stock factory image through your computer, found here: https://developers.google.com/android/nexus/images#nakasi. I had your problem at one point, and could not even boot into recovery. After trying to install cwm through adb (which failed), and a number of toolkits, the factory image was what brought my nexus back to life.
I remember reading that sometimes a wipe can delete your recovery as well as your system (and whatever else you have on your n7), although i dont know if that was ever fixed, as i got my tab replaced a month or two ago and havent rooted it again yet. There was some type of command or .zip or something that should be used to keep recovery after wipes. When i expirienced problems such as yours, it was also from a bad wipe from a toolkit. Using just the recovery afterwards, i never expirienced any issues, even without the recovery fix.
I would definitely try simms suggestion first if you can access recovery. If that fails, try one of the above processes.
PS, even if you can access recovery, if at this point you just want to go completely stock, the factory image will work regardless.
cheers
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
calavera-pw said:
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
Click to expand...
Click to collapse
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
appoos said:
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
Click to expand...
Click to collapse
ADB
Sent from my Galaxy Nexus
Pirateghost said:
ADB
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This dint work in my windows 8
appoos said:
This dint work in my windows 8
Click to expand...
Click to collapse
You're holding it wrong. ADB works on my Win8 machine
Pirateghost said:
You're holding it wrong. ADB works on my Win8 machine
Click to expand...
Click to collapse
can you tell me the procedure..
appoos said:
can you tell me the procedure..
Click to expand...
Click to collapse
no.
in the other thread that YOU created, you were given links to follow and the instructions are already there. i dont hold hands
I could do it with ADB..thanks guys
I panicked and probably did something quite stupid...
So I tried to flash the new cyanogenmod rom to have a taste of kit kat, but then I had the status 7 error.
This never occurred to me before, I didn't keep a backup to fall back onto... ( yes, I am an idiot, I learned my lesson, the hard way)
Than the device won't boot, it shows the Google logo twice, and then goes into the clockwork mod, where you choose to flash roms
and I am stuck.
I tried Nexus Root Toolkit, doesn't help because my device is not booting up, no way can it install the drivers properly...
and I think I did something more ingenious... I just tried anything on the Toolkit, and I got my rooted Nexus 7 locked...
But it's still the same, I am stuck at the clockwork mod thing just as before... Wiped whatever I can. and even formatted the sdcard and system...
Some Android Wizard out there... Please help...
If at boot you go to recovery directly... You have had to flash new version of recovery in wrong partition. You must flash it last version of recovery with "fastboot flash recovery yourrecovery.IMG" (see 'recovery' as partition to flash). Then flash boot and system partitions from factory image (in XDA have you multiples threads about it) if you want to keep your data. If not, flash factory image from usual ways (this wipes your data) and then flash recovery like I say above.
After that, try to flash CM again.
PS: I recommend TWRP instead of CWM.
Sent from my Nexus 7 (grouper) using Tapatalk.
but its more serious than that... My computer doesnt recognize the tablet because of some driver issues... I am not sure, at this moment, whether the USB debugging thing still works
i can only get to the clockwork mod page, bootloader and thats it.
I cant flash anything, I cant transfer files from the PC to tablet....
please, please help.
bump!,
Im in a similar boat. I bricked my tablet while trying to force an update. It wouldnt autoupdate (there was always an error about cant find zip file...) so I tied to install it with Skipsoft program. After 20 minutes i realize my computer has frozen....So I waited 2 hours and nada. So I had to reboot my desk top. At that time my tablet is now bricked....what do we do?
Vishnuisgod said:
bump!,
Im in a similar boat. I bricked my tablet while trying to force an update. It wouldnt autoupdate (there was always an error about cant find zip file...) so I tied to install it with Skipsoft program. After 20 minutes i realize my computer has frozen....So I waited 2 hours and nada. So I had to reboot my desk top. At that time my tablet is now bricked....what do we do?
Click to expand...
Click to collapse
hello friend.
1. we can pray
2. i think we have to look at some software that can do something more "fundamental" than wugus nexus tool kit, and communicate with the tablet
i am just guessing, i crashed my tablet, so....
dangercl0se said:
hello friend.
1. we can pray
2. i think we have to look at some software that can do something more "fundamental" than wugus nexus tool kit, and communicate with the tablet
i am just guessing, i crashed my tablet, so....
Click to expand...
Click to collapse
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im update with kitkat and it updating to 4.4.2
Vishnuisgod said:
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im update with kitkat and it updating to 4.4.2
Click to expand...
Click to collapse
hey
can you post links to where u got the stuff?
coz looks like the skipsoft homepage is not working
dangercl0se said:
hey
can you post links to where u got the stuff?
coz looks like the skipsoft homepage is not working
Click to expand...
Click to collapse
it was already on computer....
make sure you look for "android tool kit"....
Hi, I wanted to reply in the multirom thread but can't because I am still too newb. Hopefully someone here can point me in the right direction? I've tried everything I know how to do. I really appreciate any help I can get!
So here is my problem. I downloaded multirom for my n4, then I updated. I reopened, and noticed I had the red line of text saying I was missing a kernal or something, so I clicked that and install (so instead of just updating the app I updated my kernal? and I also clicked update recovery). I needed to finish in recovery mode so it rebooted. Then it soft bricked. It goes to the load screen (with countdown timer) and then just black screens indefinitely tmk (5+ minutes of adhd agony). I had already downloaded cm 10.2 and gapps on the device in preparation for multirom, so I rebooted into recovery again, launched multirom and added cm 10.2 with gapps. I first tried with sharing kernal because I don't have my laptop to install 4.3 .tar, but that failed, so I installed ROM without sharing kernal. It runs fine, except I can't use bluetooth or wifi... so it really doesn't run fine =/ everything else seems okay though.
All my data is already backed up on my hdd so no worries on losing that, but I would like my phone functioning sooner than later.
I'm on vacation and don't have laptop with me, any ideas on how I can fix this? I have my Nexus 7 too, so I can download stuff, but I don't know how to:
a) install 4.3 so I can get cm 10.2 fully running?
b) reinstall 4.4.2 to stock (I tried factory reset but it didn't do anything either)
I think the biggest problem is lack of laptop because I could easily just reset the phone with that and run my nandroid (which is on laptop too.... ftl) but if there is a solution please let me know! Thanks!!!
krkeco said:
Hi, I wanted to reply in the multirom thread but can't because I am still too newb. Hopefully someone here can point me in the right direction? I've tried everything I know how to do. I really appreciate any help I can get!
So here is my problem. I downloaded multirom for my n4, then I updated. I reopened, and noticed I had the red line of text saying I was missing a kernal or something, so I clicked that and install (so instead of just updating the app I updated my kernal? and I also clicked update recovery). I needed to finish in recovery mode so it rebooted. Then it soft bricked. It goes to the load screen (with countdown timer) and then just black screens indefinitely tmk (5+ minutes of adhd agony). I had already downloaded cm 10.2 and gapps on the device in preparation for multirom, so I rebooted into recovery again, launched multirom and added cm 10.2 with gapps. I first tried with sharing kernal because I don't have my laptop to install 4.3 .tar, but that failed, so I installed ROM without sharing kernal. It runs fine, except I can't use bluetooth or wifi... so it really doesn't run fine =/ everything else seems okay though.
All my data is already backed up on my hdd so no worries on losing that, but I would like my phone functioning sooner than later.
I'm on vacation and don't have laptop with me, any ideas on how I can fix this? I have my Nexus 7 too, so I can download stuff, but I don't know how to:
a) install 4.3 so I can get cm 10.2 fully running?
b) reinstall 4.4.2 to stock (I tried factory reset but it didn't do anything either)
I think the biggest problem is lack of laptop because I could easily just reset the phone with that and run my nandroid (which is on laptop too.... ftl) but if there is a solution please let me know! Thanks!!!
Click to expand...
Click to collapse
WHY DID THE ERROR HAPPENED?:Because multirom app sets the default kernel to 4.2.2 one, since you werent on 4.2.2 it soft bricked.
DO I NEED TO REINSTALL STOCK TO GET CM FULLY WORKING?: Nope, just search in the general section of our device, for the hybrid modem thread, download the hybrid .84 and flash on recovery
PS: I think you will need OTG to pass the file from your n7 to your n4 since no bluetooh,no data and no wifi....
Or search like crazy around google to see if there is a way to pass files thru nfc
Thanks for the quick reply, is that the 27 or the 33 / 84 download?
sites.google.com/site/bpearuploads/
Or does it not matter?
opssemnik said:
WHY DID THE ERROR HAPPENED?:Because multirom app sets the default kernel to 4.2.2 one, since you werent on 4.2.2 it soft bricked.
DO I NEED TO REINSTALL STOCK TO GET CM FULLY WORKING?: Nope, just search in the general section of our device, for the hybrid modem thread, download the hybrid .84 and flash on recovery
PS: I think you will need OTG to pass the file from your n7 to your n4 since no bluetooh,no data and no wifi....
Or search like crazy around google to see if there is a way to pass files thru nfc
Click to expand...
Click to collapse
Got it figured out thanks to your help!
Good morning.
So I'm running KitKat on my Nexus 4 and everything was fine until I decided to install TouchControl to avoid using the power button that much. I'm not an expertise over kernel's so I followed the prompted instructions and I ended up flashing the stock kernel I guess.
So after that my phoned rebooted, and since then I can not connect to Wifi, it only says connecting. I don't have CWM on my phone because I have a problem connecting my phone to my computer since it got wet some weeks ago so now it only charges but I can not transfer any files into my phone.
I restored my phone to factory settings and nothing.
I know this will be tricky but I also know you guys can help me, I know the main issue will be the fact that I can not transfer files over USB.
Please your help you will be of so much help.
Thanks in advance
grillaxo said:
Good morning.
So I'm running KitKat on my Nexus 4 and everything was fine until I decided to install TouchControl to avoid using the power button that much. I'm not an expertise over kernel's so I followed the prompted instructions and I ended up flashing the stock kernel I guess.
So after that my phoned rebooted, and since then I can not connect to Wifi, it only says connecting. I don't have CWM on my phone because I have a problem connecting my phone to my computer since it got wet some weeks ago so now it only charges but I can not transfer any files into my phone.
I restored my phone to factory settings and nothing.
I know this will be tricky but I also know you guys can help me, I know the main issue will be the fact that I can not transfer files over USB.
Please your help you will be of so much help.
Thanks in advance
Click to expand...
Click to collapse
Does ADB work?
If the phone is rooted, grab Flashify off the Play Store and install CWM or TWRP from there.
Have a custom/stock kernel zip to flash on your sdcard.
PR0XiMA said:
If the phone is rooted, grab Flashify off the Play Store and install CWM or TWRP from there.
Have a custom/stock kernel zip to flash on your sdcard.
Click to expand...
Click to collapse
He can't. His internet connection doesn't work.
abaaaabbbb63 said:
He can't. His internet connection doesn't work.
Click to expand...
Click to collapse
Did it say that 3G didn't work?
Problem fixed
So at the end I figure that the problem was caused by the Touch Control App, I did not put the required attention to the prompted instructions and the kernel was flashed.
So, using my phone's BT I transferred the files to install CWM and then I flashed it with the stock ROM.
That's the way I recovered the WiFi Capability.
Thanks for your advice guys.
Cheers.