Guys I need help right away! I accidentally flash a S4 AOSP ROM on my nexus 4. I try to flash the factory images, everything goes smooth but it boots so slow now, and WiFi, signal and other radio stuff doesn't work! How is this possible if I flash the factory images? Please help!:crying::crying:
edit: also my IMEI shows unknown know, and when i connect to the pc the internal storage is faulty(?). i cant copy files there. but the phone is turn on and works! i can go to drawer, apps do things and stuff. strange..
Thats the biggest **** up wow umm im not a pro at this but clear dalvik cache reg cache factory reset then re flash stock again
Sent from my Nexus 7 using xda app-developers app
beastint said:
Thats the biggest **** up wow umm im not a pro at this but clear dalvik cache reg cache factory reset then re flash stock again
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i tried this but doesnt work. everytime the same thing. it boots but radio stuff doest work. also my IMEI is unknown now.
johnxarma said:
Guys I need help right away! I accidentally flash a S4 AOSP ROM on my nexus 4. I try to flash the factory images, everything goes smooth but it boots so slow now, and WiFi, signal and other radio stuff doesn't work! How is this possible if I flash the factory images? Please help!:crying::crying:
edit: also my IMEI shows unknown know, and when i connect to the pc the internal storage is faulty(?). i cant copy files there. but the phone is turn on and works! i can go to drawer, apps do things and stuff. strange..
Click to expand...
Click to collapse
Well, if what you say is true and you are correctly flashing the factory images with fastboot ( including the radio )
your screwed.
trentreed said:
Well, if what you say is true and you are correctly flashing the factory images with fastboot ( including the radio )
your screwed.
Click to expand...
Click to collapse
thanks for the reply. any solution maybe? :/
anyone? please if someone knows a fix or something to try please tell me
johnxarma said:
anyone? please if someone knows a fix or something to try please tell me
Click to expand...
Click to collapse
Download a nexus 4 ROM and flash that.
Next time do not ever ever flash a rom that is not meant for the device. Is your phone a S4? No. Is it a HTC One? No. Stick with ROMs and kernels meant for your device and you'll be good.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Download a nexus 4 ROM and flash that.
Next time do not ever ever flash a rom that is not meant for the device. Is your phone a S4? No. Is it a HTC One? No. Stick with ROMs and kernels meant for your device and you'll be good.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
He said he ACCIDENTALLY flashed the ROM of a gs4. No need to rip him apart for a mistake, I think he is going to suffer enough by having to replace his defective phone.
Sent from my Nexus 4 using Tapatalk 4 Beta
scream4cheese said:
Download a nexus 4 ROM and flash that.
Next time do not ever ever flash a rom that is not meant for the device. Is your phone a S4? No. Is it a HTC One? No. Stick with ROMs and kernels meant for your device and you'll be good.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
as i said i accidentally flash a wrong rom. thanks for the reply but i can copy files to internal storage, somehow it damaged by the rom(?) :/ i dont know..
maybe can i use this way to fix it? anyone tried maybe, so can help me? http://forum.xda-developers.com/showthread.php?t=1976057
Did flash the factory images via Fastboot ?
Sent from my Nexus 4 using xda premium
Tough luck mate
I'm no expert, but obviously you've overwritten your modem/radio partition, maybe even corrupted. I don't know if you could zero that partition (with dd codes) and then flash one of our radios... Not sure if that would work...
Edit:
http://forum.xda-developers.com/showthread.php?p=43096832
Check this post, seems like he made the same thing, see if he solves it, he might help you.
Sent from my Nexus 4 using xda premium
Didn't your custom recovery stop you from flashing another's phone software
Sent from my Nexus 4 using xda app-developers app
Exodian said:
Did flash the factory images via Fastboot ?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
yes i did. same problem
mattoaida said:
Didn't your custom recovery stop you from flashing another's phone software
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
no. it was an aosp rom for galaxy s4, so maybe because of aosp(?)
johnxarma said:
yes i did. same problem
Click to expand...
Click to collapse
Did you flash all the files? System, boot loader, radio... Something like 6 files? If not I would flash all the files. If so I would flash them again.
Sent from my Nexus 4 using xda premium
johnxarma said:
no. it was an aosp rom for galaxy s4, so maybe because of aosp(?)
Click to expand...
Click to collapse
No, it's not because it's aosp. Nexus 4 uses aosp but the drivers and all are different on each device.
I'm sorry if I sounded like a total jerk before.
Sent from my Nexus 4 using Tapatalk 2
Install 4.1 via nexus toolkit. Then 4.2. This should install the nexus radio as well.
Exodian said:
Did you flash all the files? System, boot loader, radio... Something like 6 files? If not I would flash all the files. If so I would flash them again.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
yes of course, all the files. i follow efrant's how to guide step per step.
scream4cheese said:
No, it's not because it's aosp. Nexus 4 uses aosp but the drivers and all are different on each device.
I'm sorry if I sounded like a total jerk before.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
its ok mate i just need a solution because i dont want to sent it for service..
Related
I need help.
Today i tried flashing the faux kernel using CWM and when my phone rebooted got stuck at boot (google screen)
I rebooted in recovery and tried flashing again but the same problem happen.
Now im stuck,
I can't load any file because on the computer i am using the drivers are not installed.
What shall I do?
sampy14 said:
I need help.
Today i tried flashing the faux kernel using CWM and when my phone rebooted got stuck at boot (google screen)
I rebooted in recovery and tried flashing again but the same problem happen.
Now im stuck,
I can't load any file because on the computer i am using the drivers are not installed.
What shall I do?
Click to expand...
Click to collapse
So you have no backup or another file you can flash? If not, install drivers...
This also belongs in QA.
Sent from my Nexus 4 using Tapatalk 2
Install correct drivers and flash stock rom with adb. Else use the toolkit.
CMNein said:
So you have no backup or another file you can flash? If not, install drivers...
This also belongs in QA.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Sorry i tought i posted it in QA.
I can't get to install drivers with the phone turned on in fastboot.
sampy14 said:
Sorry i tought i posted it in QA.
I can't get to install drivers with the phone turned on in fastboot.
Click to expand...
Click to collapse
Are you running Windows?
Sent from my Nexus 4 using xda app-developers app
Ace42 said:
Are you running Windows?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
yes I am
We can't debug your windows pc... Fast boot drivers can/will install fine. Try another computer and see if the toolkit will get you going.
Edit: all you need to do is read, read the stickies and read tutorials on how to return to stock. The drivers will install without being inside Android
Sent from my Nexus 4 using xda premium
sampy14 said:
yes I am
Click to expand...
Click to collapse
Remove the current n4 drivers with device manager in windows. Then find the proper drivers here on xda in the n4 general section. After that you should be able to use the toolkit to boot to recovery or flash a stock build.
Sent from my Nexus 4 using xda app-developers app
Haha
i managed to install the drivers. Now im downloading the stock image and i'll flash it with the toolkit
sampy14 said:
i managed to install the drivers. Now im downloading the stock image and i'll flash it with the toolkit
Click to expand...
Click to collapse
Btw when you used cwm did you use the clockwork app or the actual recovery?
Sent from my Nexus 4 using xda app-developers app
Why not just flash the ROM your on ?
Sent from my Nexus 4 using Tapatalk 2
Ace42 said:
Btw when you used cwm did you use the clockwork app or the actual recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
the actual recovery.
anyway i fixed it.
I just flashed the franco kernel and it worked.
sampy14 said:
the actual recovery.
anyway i fixed it.
I just flashed the franco kernel and it worked.
Click to expand...
Click to collapse
I know why it went into bootloop. To flash other kernals aside frmo Francos...you need to flash stock boot image. Francos kernal has you flash his boot image in order to flash his kernal. I dont know why this is the case on the nexus 4, maybe because he is building blindly without a nexus 4 present with him.
The Gnexus wasnt like this but.....thats why you went into boot loop. I just skimmed his thread and found out your case was due to the above.
kioshi said:
I know why it went into bootloop. To flash other kernals aside frmo Francos...you need to flash stock boot image. Francos kernal has you flash his boot image in order to flash his kernal. I dont know why this is the case on the nexus 4, maybe because he is building blindly without a nexus 4 present with him.
The Gnexus wasnt like this but.....thats why you went into boot loop. I just skimmed his thread and found out your case was due to the above.
Click to expand...
Click to collapse
yes you are totally right. I have never had any problem with my galaxy nexus, thats why i didn't think twice before doing it.
Think the op should change the title of the 3d as it is misleading and blame faux for nothing
Sent from my Nexus 4 using Tapatalk 2
kaiowas82 said:
Think the op should change the title of the 3d as it is misleading and blame faux for nothing
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
3d? Funny way to spell thread
you were supposed to flash reset kernel first then faux kernel!! read the op!!! >.<
You can't brick a Nexus LOLs. Just download the toolkit. Easy way to fix your phone.
Sent from my Nexus 4 using Tapatalk 2
kioshi said:
I know why it went into bootloop. To flash other kernals aside frmo Francos...you need to flash stock boot image. Francos kernal has you flash his boot image in order to flash his kernal. I dont know why this is the case on the nexus 4, maybe because he is building blindly without a nexus 4 present with him.
The Gnexus wasnt like this but.....thats why you went into boot loop. I just skimmed his thread and found out your case was due to the above.
Click to expand...
Click to collapse
Franco uses his own ram disk. Other kernels do not. This is why you need to flash back to stock first.
Sent from my Nexus 4 using Tapatalk 2
I dont have any roms in my internal storage
I cant mount USB from recovery mode(using twrp)
I dont have any roms installed in my phone.
how can I install roms again?
I'm assuming you ignored every piece of advice ever and don't have a nandroid backup on the phone to restore from?
Sent from my Nexus 4 using xda app-developers app
darkrom said:
I'm assuming you ignored every piece of advice ever and don't have a nandroid backup on the phone to restore from?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
yes i ignored every advice.
i did nandroid but i deleted my whole internal storage accidentally using twrp wipes.
You can push rom with "adb push" or flash factory rom with fastboot
Sent from my Nexus 4 using Tapatalk 2
omrij said:
You can push rom with "adb push" or flash factory rom with fastboot
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
found a different way to fix it but thanks anyways.
a mod can close this now.
P00t said:
found a different way to fix it but thanks anyways.
a mod can close this now.
Click to expand...
Click to collapse
Can you tell us how you fixed you so anyone in the future with the same problem can easily refer to this thread instead of creating another thread just to ask the same question.
It just disappeared like idk how, can't find it nowhere..
Any solutions?
paulo111 said:
It just disappeared like idk how, can't find it nowhere..
Any solutions?
Click to expand...
Click to collapse
did you flash a rom and then forget to flash the gapps package?
simms22 said:
did you flash a rom and then forget to flash the gapps package?
Click to expand...
Click to collapse
No, I wasn't doing anything on the phone..!
Tried download a apk but didn't work, it can't install..
Also I'm not rooted but got bootloader unlocked.
Try installing from here: http://forum.xda-developers.com/showthread.php?t=2160817
Then reboot and see how you go?
says file not found the link :\
Sent from my Nexus 4 using Tapatalk 2
Try reflashing gapps, thats what I did when my Google play store got messed up.
Make sure to do a nandroid in case something messes up
Sent from my Nexus 4 using XDA Premium HD app
idk how to do that.. :/ im a noobie.. isnt there anything simpler?
Sent from my Nexus 4 using Tapatalk 2
solved it, it was desactivated, didnt even know that was possible, tyvm though for thr help!
Sent from my Nexus 4 using Tapatalk 2
So all right, I thought that when a newer version of Android came out and I am for example on CM10.1, I can update the android version and ROM by flashing a new bootloader and baseband, then flash the ROM and Gapps you want.
But today I read about someone who didn't accomplish to install a 4.2.2 ROM when he was on 4.2.1 so he installed factory image.
Can someone now please tell me what you need to do, so I am prepared when KLP arrives.
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Please search. There are a gazillion amount of the same post laying around here. It would help you and others.
Sent from my Samsung Galaxy S3 using tapatalk 2
scream4cheese said:
Please search. There are a gazillion amount of the same post laying around here. It would help you and others.
Sent from my Samsung Galaxy S3 using tapatalk 2
Click to expand...
Click to collapse
I know but everyone says different things...
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
I know but everyone says different things...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2145848
[INFO] Nexus OTA Help-Desk
Sent from my Nexus 4
Thibaultvw said:
So all right, I thought that when a newer version of Android came out and I am for example on CM10.1, I can update the android version and ROM by flashing a new bootloader and baseband, then flash the ROM and Gapps you want.
But today I read about someone who didn't accomplish to install a 4.2.2 ROM when he was on 4.2.1 so he installed factory image.
Can someone now please tell me what you need to do, so I am prepared when KLP arrives.
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Best advice I can give you is to learn fastboot. You can download images from Google once released and manually flash each thing that you want to update. You just unzip the files and fastboot flash them to your phone.
Sent from my Nexus 4 using Xparent Cyan Tapatalk 2
I think I am misunderstood.
I meant how to upgrade android version if going from a custom rom to another custom rom.
So for example CM10.1 Android 4.2.2 and going to Xenon HD Android 5.0
Thats possible right?
Sent from my Nexus 4 using xda app-developers app
Most developers list instruction on how to install from different custom roms in the install method if they differ (example post#2 in http://forum.xda-developers.com/showthread.php?t=2075444). If not, you could post in the thread of the custom rom to see if there are any special steps for that rom. I would advise reading through the first few posts of the custom rom to make double sure they didn't explain how to first.
Most developers list instruction on how to install from different custom roms in the install method if they differ (example post#2 in http://forum.xda-developers.com/showthread.php?t=2075444). If not, you could post in the thread of the custom rom to see if there are any special steps for that rom. I would advise reading through the first few posts of the custom rom to make double sure they didn't explain how to first.
Click to expand...
Click to collapse
Yeah but not when a newer android version comes out.
Sent from my Nexus 4 using xda app-developers app
1. Download new factory image
2. Flash bootloader and radio
3. Flash new custom ROM
4. Done
It's not that hard really
EddyOS said:
1. Download new factory image
2. Flash bootloader and radio
3. Flash new custom ROM
4. Done
It's not that hard really
Click to expand...
Click to collapse
But I do have to flash factory image in fastboot? No other ways by just using CWM?
Sent from my Nexus 4 using xda app-developers app
You don't, bootloader and radio should be enough, but you WILL need fastboot to get that bit done
EddyOS said:
You don't, bootloader and radio should be enough, but you WILL need fastboot to get that bit done
Click to expand...
Click to collapse
There is a flashable zip for that. So I can just use CWM when upgrading ROMs?
Sent from my Nexus 4 using xda app-developers app
I personally prefer to use fastboot but if there is a ZIP then you could try that...
EddyOS said:
I personally prefer to use fastboot but if there is a ZIP then you could try that...
Click to expand...
Click to collapse
Why do you prefer that even of you install the same file? But the answer on my question is that I can install a 5.0 ROM if I just flash the new bootloader and baseband?
Thank you for helping me!
Yes, as I answered that earlier
As for why I prefer fastboot - I always like to do everything manually. I then know I'VE done things right as an updater-script in a CWM ZIP file could be wrong/corrupt. It's a safety thing. Plus, once it's done it's done so I wouldn't have to do it again unless I wanted to downgrade Android to 4.x
EddyOS said:
Yes, as I answered that earlier
As for why I prefer fastboot - I always like to do everything manually. I then know I'VE done things right as an updater-script in a CWM ZIP file could be wrong/corrupt. It's a safety thing. Plus, once it's done it's done so I wouldn't have to do it again unless I wanted to downgrade Android to 4.x
Click to expand...
Click to collapse
But with CWM you also have to flash once I think? Because you dont flash it on a ROM, but before a ROM so the baseband and bootloader will last untill you install another I think?
Sent from my Nexus 4 using xda app-developers app
Fastboot flashing is permanent - once flashed you don't have to do it again. A CWM ZIP can do the same but I, personally, DO NOT LIKE DOING IT THAT WAY. I don't know what else you want me to say?
Do what YOU want to do
EddyOS said:
Fastboot flashing is permanent - once flashed you don't have to do it again. A CWM ZIP can do the same but I, personally, DO NOT LIKE DOING IT THAT WAY. I don't know what else you want me to say?
Do what YOU want to do
Click to expand...
Click to collapse
All right. Thanks for the help.
Sent from my Nexus 4 using xda app-developers app
Just upgrade the ROM. The developer will update his ROMS as new android comes out
Sent from my Nexus 4 using xda app-developers app
aanonymoushuman said:
Just upgrade the ROM. The developer will update his ROMS as new android comes out
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah but CM11 (or whatever it may be called) wont be ready as yes as Android 5.0 comes out, and I may use the stock ROM the first day it comes out, which I will flash in CWM so I wanted to know if I needed to do something else.
Hey guys,
I've recently updated to android 4.3
I've installed franco kernel on top of the os and it seems to screw up my phone
the phone restarted and its stuck on the google logo
I've tried to use nexus root toolkit of WUG to install stock + unroot in the soft brick mode
and its still stucked on the google logo
tried factory reset from bootloader and now it tells me I dont have OS hehe
mmm dont know really what to do from here and not sure
I did the above mentioned steps as I should.
I dont have problem to delete everything and to do a factory reset if possible
Also I'd like to have 4.2.2 .. loved it more as I could work with franco kernel
would much appriciate any guidence on to follow up from here
as I am preety lost.
thanks alot mates!
That is soft bricked and there is like a million ways to fix it.
If you want you can sideload a custom rom of your choice or you can just use the Nexus Stock Images which allows you to install 4.2.2 or 4.3.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
That is soft bricked and there is like a million ways to fix it.
If you want you can sideload a custom rom of your choice or you can just use the Nexus Stock Images which allows you to install 4.2.2 or 4.3.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
If its softbricked, you can also restore a nandroid and it will boot I think?
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
If its softbricked, you can also restore a nandroid and it will boot I think?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Since it is just Soft bricked then yes, just boot to recovery with volume up and power, scroll to recovery, select and restore your backup.
Sent from my Nexus 4 using Tapatalk 4
Thanks for the quick responses guys
but unfortanantly I dont have a nandroid backup
my recovery is Team Win Recovery Project v2.6.0.0
can you please address me to a tut or guide that shows how to overcome this issue?
biotech326 said:
Thanks for the quick responses guys
but unfortanantly I dont have a nandroid backup
my recovery is Team Win Recovery Project v2.6.0.0
can you please address me to a tut or guide that shows how to overcome this issue?
Click to expand...
Click to collapse
There is a way to put it on complete stock but it will literally wipe EVERYTHING, would you like to proceed?
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
There is a way to put it on complete stock but it will literally wipe EVERYTHING, would you like to proceed?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
yes mate thanks!
biotech326 said:
yes mate thanks!
Click to expand...
Click to collapse
Choose your android version here, choose the Mako/Occam type.
https://developers.google.com/android/nexus/images#occamjwr66v
From the looks of it there is no Fastboot binary in it so you need to copy them over to that folder making sure your in the bootloader and you have drivers.
Sent from my Nexus 4 using Tapatalk 4
Follow this guide.
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Choose your android version here, choose the Mako/Occam type.
https://developers.google.com/android/nexus/images#occamjwr66v
From the looks of it there is no Fastboot binary in it so you need to copy them over to that folder making sure your in the bootloader and you have drivers.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
mmm how do i copy the fastboot binary and how do i make sure i have drivers?
biotech326 said:
mmm how do i copy the fastboot binary and how do i make sure i have drivers?
Click to expand...
Click to collapse
Follow the guide I posted...
Sent from my Nexus 4 using xda app-developers app
biotech326 said:
mmm how do i copy the fastboot binary and how do i make sure i have drivers?
Click to expand...
Click to collapse
Extract the zipped file where the flash all batch file is, it is attached to this post.
Has for the drivers you have to go here.
thanks alot mates you both helped me a great deal and its solved now
cheers
biotech326 said:
thanks alot mates you both helped me a great deal and its solved now
cheers
Click to expand...
Click to collapse
And now you will laugh any time you soft brick the phone again because you'll realize how easy it is to fix it. I was in the same boat as you and learning how to use ADB/Fastboot really changed the game for me.
sn0warmy said:
And now you will laugh any time you soft brick the phone again because you'll realize how easy it is to fix it. I was in the same boat as you and learning how to use ADB/Fastboot really changed the game for me.
Click to expand...
Click to collapse
hehe for sure
before I had the nexus 4 I had galaxy s1
and everytime with Odin flashing stock and kernel was preety much it for me
everyone scared me about brick
Now after dealing with the softbrick I feel unbeatable
cheers mate
biotech326 said:
hehe for sure
before I had the nexus 4 I had galaxy s1
and everytime with Odin flashing stock and kernel was preety much it for me
everyone scared me about brick
Now after dealing with the softbrick I feel unbeatable
cheers mate
Click to expand...
Click to collapse
I had this same issue you had, and I noticed it happened because i was flashing franco kernel for 4.2.2 over JB 4.3
Make sure you are downloading the correct version of franco if you still want his kernel.
Something similar Happened to me today.....i flashed the franco kernel via the CWM recovery.....and when i rebooted the screen turened into some blue-pink coloured array....of squares.....and it doenst go over from there??? what should i do now/??
sPaMFouR said:
Something similar Happened to me today.....i flashed the franco kernel via the CWM recovery.....and when i rebooted the screen turened into some blue-pink coloured array....of squares.....and it doenst go over from there??? what should i do now/??
Click to expand...
Click to collapse
Can you get into recovery and/or the bootloader?
sPaMFouR said:
Something similar Happened to me today.....i flashed the franco kernel via the CWM recovery.....and when i rebooted the screen turened into some blue-pink coloured array....of squares.....and it doenst go over from there??? what should i do now/??
Click to expand...
Click to collapse
that just means that your room has CM in it. you must need to have a CM kernel.
Sent from my Nexus 4 using XDA Premium 4 mobile app
---------- Post added at 03:44 AM ---------- Previous post was at 03:41 AM ----------
sPaMFouR said:
Something similar Happened to me today.....i flashed the franco kernel via the CWM recovery.....and when i rebooted the screen turened into some blue-pink coloured array....of squares.....and it doenst go over from there??? what should i do now/??
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/development/unofficial-cm-compatible-franco-faux-t2487246
here's the link.
Sent from my Nexus 4 using XDA Premium 4 mobile app