Related
Help | Mistakenly installed JB 4.3 for Samsung S3 on Nexus 4
Now sdcard/storage is gone, doesnt connect to mobile network, wifi/bluetooth doesnt turn on, camera gives message, mount storage
Keeps laging, in short i have bricked it.
Flashed Factory image, unrooted it, flashed it again, installed android emulator and wrote IMEI back thinking IMEI was compromised but still doesnt connect to network
PLEASE ADVICE !!!!!!
@nexus4 said:
Help | Mistakenly installed JB 4.3 for Samsung S3 on Nexus 4
Now sdcard/storage is gone, doesnt connect to mobile network, wifi/bluetooth doesnt turn on, camera gives message, mount storage
Keeps laging, in short i have bricked it.
Flashed Factory image, unrooted it, flashed it again, installed android emulator and wrote IMEI back thinking IMEI was compromised but still doesnt connect to network
PLEASE ADVICE !!!!!!
Click to expand...
Click to collapse
Time to get a new Nexus 4.
Here's the guy who did what you did:
http://forum.xda-developers.com/showthread.php?t=2344920
@nexus4 said:
Help | Mistakenly installed JB 4.3 for Samsung S3 on Nexus 4
Now sdcard/storage is gone, doesnt connect to mobile network, wifi/bluetooth doesnt turn on, camera gives message, mount storage
Keeps laging, in short i have bricked it.
Flashed Factory image, unrooted it, flashed it again, installed android emulator and wrote IMEI back thinking IMEI was compromised but still doesnt connect to network
PLEASE ADVICE !!!!!!
Click to expand...
Click to collapse
why the heck would you install a samsung galaxy rom on your nexus 4? by your actions im not sure, but i hope that you are able to read, this brainiac did the same thing that you did http://forum.xda-developers.com/showthread.php?t=2347060
simms22 said:
why the heck would you install a samsung galaxy rom on your nexus 4? by your actions im not sure, but i hope that you are able to read, this brainiac did the same thing that you did http://forum.xda-developers.com/showthread.php?t=2347060
Click to expand...
Click to collapse
I had downloaded pacman-mako latest nightly and JB 4.3 for a frnd and without checking properly which ROM i had selected, I simply clicked yes to install and boom...
Any way to fix this??
@nexus4 said:
I had downloaded pacman-mako latest nightly and JB 4.3 for a frnd and without checking properly which ROM i had selected, I simply clicked yes to install and boom...
Any way to fix this??
Click to expand...
Click to collapse
in the link i left, the op did the same as you, with trial and error he fixed it and brought his phone back to life. so he wrote it up.
@nexus4 said:
I had downloaded pacman-mako latest nightly and JB 4.3 for a frnd and without checking properly which ROM i had selected, I simply clicked yes to install and boom...
Any way to fix this??
Click to expand...
Click to collapse
He already gave you a link to fix it.
http://forum.xda-developers.com/showthread.php?t=2347060
simms22 said:
in the link i left, the op did the same as you, with trial and error he fixed it and brought his phone back to life. so he wrote it up.
Click to expand...
Click to collapse
Thank you so much, started downloading files already, hope to unbrick it
@nexus4 said:
Thank you so much, started downloading files already, hope to unbrick it
Click to expand...
Click to collapse
good luck!
I smell a new trend of installing incorrect phone ROMs.
This is what...the 3rd or 4th person this has happened to? It's a shame it really is and accidents happen. I hope people take more precaution in the future. :/
SpartusTana said:
I smell a new trend of installing incorrect phone ROMs.
This is what...the 3rd or 4th person this has happened to? It's a shame it really is and accidents happen. I hope people take more precaution in the future. :/
Click to expand...
Click to collapse
new trend??
this is the third this week in these forums..
simms22 said:
new trend??
this is the third this week in these forums..
Click to expand...
Click to collapse
I hope it doesn't catch on any more haha
simms22 said:
new trend??
this is the third this week in these forums..
Click to expand...
Click to collapse
HAPPY !!!! Got it unbricked :victory:
Just that its become 8 gig version, but on the post there is a fix for that too.
Its 2:10am now in where I am, m too happy that my phone is up will work to restore the missing 8gig tomorrow.
Thank you Simm22 and everybody at XDA ! Salute :good:
Dear all
I just have a big problem that I still cannot solve by myselft and all the things I searched on Internet
I downloaded the Android 4.3 stock rom from Google dev site. Then, I tried to install it by Google Nexus Toolkit 1.6.4 but it was not successful
( Perhaps the universal driver is not fully compatible with Windows 8, I often have this problem on Windows 8 )
Then I changed to use Google Nexus 7 Toolkit v5.0.0 and flash the stock ROM
This tool could do a little bit further. It extracted, deleted user data, send file to machine but after that, it flashed unsuccessfully
The screen is still in bootloader mode. So I decided to press Start to check whether the ROM had been installed successfully or not
And it said boot failed
I turned off the device and then couldn't turn it on till now. I plugged into laptop and it said lacking of APX driver.
I searched and know that this is a mode only for NVIDIA processor devices
I tried so many ways on Internet to turn it on, but still cannot
So can you help me wake it up ?
Thank you so much
Sorry for bad English
thangpq.fuhl said:
Dear all
I just have a big problem that I still cannot solve by myselft and all the things I searched on Internet
I downloaded the Android 4.3 stock rom from Google dev site. Then, I tried to install it by Google Nexus Toolkit 1.6.4 but it was not successful
( Perhaps the universal driver is not fully compatible with Windows 8, I often have this problem on Windows 8 )
Then I changed to use Google Nexus 7 Toolkit v5.0.0 and flash the stock ROM
This tool could do a little bit further. It extracted, deleted user data, send file to machine but after that, it flashed unsuccessfully
The screen is still in bootloader mode. So I decided to press Start to check whether the ROM had been installed successfully or not
And it said boot failed
I turned off the device and then couldn't turn it on till now. I plugged into laptop and it said lacking of APX driver.
I searched and know that this is a mode only for NVIDIA processor devices
I tried so many ways on Internet to turn it on, but still cannot
So can you help me wake it up ?
Thank you so much
Sorry for bad English
Click to expand...
Click to collapse
Having the same problem like u. ANdroid 4.3
However, i download the 4.2.2 version, using same procedure to do, it works.... i`m thinking about the 4.3 image file got problem?
evangelism said:
Having the same problem like u. ANdroid 4.3
However, i download the 4.2.2 version, using same procedure to do, it works.... i`m thinking about the 4.3 image file got problem?
Click to expand...
Click to collapse
My problem is cannot wake up my device.
thangpq.fuhl said:
Dear all
I just have a big problem that I still cannot solve by myselft and all the things I searched on Internet
I downloaded the Android 4.3 stock rom from Google dev site. Then, I tried to install it by Google Nexus Toolkit 1.6.4 but it was not successful
( Perhaps the universal driver is not fully compatible with Windows 8, I often have this problem on Windows 8 )
I tried so many ways on Internet to turn it on, but still cannot
So can you help me wake it up ?
Thank you so much
Sorry for bad English
Click to expand...
Click to collapse
Not completely sure, but I have seen this before, I think you got the bootloader corrupted somehow.
tikoracer said:
Not completely sure, but I have seen this before, I think you got the bootloader corrupted somehow.
Click to expand...
Click to collapse
Yep so what is the solution for this ?
I searched for nvflash but it seems that it's not for Nexus 7 ( at least now )
thangpq.fuhl said:
Yep so what is the solution for this ?
I searched for nvflash but it seems that it's not for Nexus 7 ( at least now )
Click to expand...
Click to collapse
As per now... you are stuck in APX mode. No solution for that in the Nexus 7 device. Asus cover that in warranty, you´ll have to go that way... It happened the same to me.
Ashade said:
As per now... you are stuck in APX mode. No solution for that in the Nexus 7 device. Asus cover that in warranty, you´ll have to go that way... It happened the same to me.
Click to expand...
Click to collapse
Thank you . I already sent it to the Warranty service
thangpq.fuhl said:
Thank you . I already sent it to the Warranty service
Click to expand...
Click to collapse
No problem. Just hope you get it back fast.
Ashade said:
No problem. Just hope you get it back fast.
Click to expand...
Click to collapse
I don't know if they can't fix it, they will give me a new one or not
Mee too
thangpq.fuhl said:
Dear all
I just have a big problem that I still cannot solve by myselft and all the things I searched on Internet
I downloaded the Android 4.3 stock rom from Google dev site. Then, I tried to install it by Google Nexus Toolkit 1.6.4 but it was not successful
( Perhaps the universal driver is not fully compatible with Windows 8, I often have this problem on Windows 8 )
Then I changed to use Google Nexus 7 Toolkit v5.0.0 and flash the stock ROM
This tool could do a little bit further. It extracted, deleted user data, send file to machine but after that, it flashed unsuccessfully
The screen is still in bootloader mode. So I decided to press Start to check whether the ROM had been installed successfully or not
And it said boot failed
I turned off the device and then couldn't turn it on till now. I plugged into laptop and it said lacking of APX driver.
I searched and know that this is a mode only for NVIDIA processor devices
I tried so many ways on Internet to turn it on, but still cannot
So can you help me wake it up ?
Thank you so much
Sorry for bad English
Click to expand...
Click to collapse
Hey, the same with me, after trying to update to android 4.3 with nexus root tool kit 1.64.
In this case the bootloader was deleted. Waiting for the feedback of asus....
Based upon this evidence I suggest you don't use a tool kit to flash 4.3 and do it manually
Sent from my Nexus 7 using xda app-developers app
Ashade said:
As per now... you are stuck in APX mode. No solution for that in the Nexus 7 device. Asus cover that in warranty, you´ll have to go that way... It happened the same to me.
Click to expand...
Click to collapse
What if I already unlocked the device, does it still cover in the warranty
jin_hw said:
What if I already unlocked the device, does it still cover in the warranty
Click to expand...
Click to collapse
I'm not an expert but I would say there is no way for them to know at this point. So yes, you are covered. They need to completely wipe the device to get it back to life. This is something that happened to people updating OTAs as well, so it's not an uncommon issue.
thanhsubasa said:
Hey, the same with me, after trying to update to android 4.3 with nexus root tool kit 1.64.
In this case the bootloader was deleted. Waiting for the feedback of asus....
Click to expand...
Click to collapse
The problem I think here is the not fully compatible driver with Windows 8
thangpq.fuhl said:
The problem I think here is the not fully compatible driver with Windows 8
Click to expand...
Click to collapse
Hi,
How your Nexus been? I've just received the Nexus 7 with new mainboard replaced and... no fees. So happy!!!
Now it's time to sell it, get the new nexus 7, and expect it not to be that easy to brick. XD
Sent from my SGH-T889 using Tapatalk HD
Ashade said:
Now it's time to sell it, get the new nexus 7, and expect it not to be that easy to brick. XD
Sent from my SGH-T889 using Tapatalk HD
Click to expand...
Click to collapse
Thank you. the warranty service told me that they had repaired it successfully. Tomorrow I'll take it
Glad to hear that. I cannot even imaging being without my tablet for one day, I don't want to think about weeks...
Sent from my SGH-T889 using Tapatalk HD
Ashade said:
Glad to hear that. I cannot even imaging being without my tablet for one day, I don't want to think about weeks...
Sent from my SGH-T889 using Tapatalk HD
Click to expand...
Click to collapse
But I have been waiting for whole week
Actually, I don't have dual monitor system so I often use my tablet as ebook reader to read instruction while coding
Tried to update Nexus 7 4.2.2 rooted with Nexus Toolkit too..but got stuck at a APX mode Nexus 7.
Nothing could revive it, so had to send to Asus for warranty claim
They changed a new motherboard and all is well now.....with 4.3..but wifi reception still sucks
I was on a phone call suddenly phone turned off. Tried booting it it would go past the GOOGLE logo. I went into recovery but nothing is able to mount. Trying flashing stock img through TOOLKIT errors, I guess cause won't mount. Any solutions? I heard it might be the EMMC chip?
Try flashing the factory images manually
http://forum.xda-developers.com/showthread.php?t=2010312
Sent using xda-developers app
Chromium_ said:
Try flashing the factory images manually
http://forum.xda-developers.com/showthread.php?t=2010312
Sent using xda-developers app
Click to expand...
Click to collapse
No :crying: like nothing can be flash. Every time I try it ends up with "flash write failed"
theedon323 said:
No :crying: like nothing can be flash. Every time I try it ends up with "flash write failed"
Click to expand...
Click to collapse
Last resort: http://forum.xda-developers.com/showthread.php?t=2347060
Yeah looks like the telltale sign of a dead emmc, like the Samsung Galaxy S3, sorry.
xda app
Chromium_ said:
Last resort: http://forum.xda-developers.com/showthread.php?t=2347060
Click to expand...
Click to collapse
Tried it and nothing. It's just not able to write into the system, fails everytime. I appreciate your help. LG G2 is next I guess.
eksasol said:
Yeah looks like the telltale sign of a dead emmc, like the Samsung Galaxy S3, sorry.
xda app
Click to expand...
Click to collapse
I think so. Do you know the reason for it? Do you think it was because i had the XPOSED framework mod?
theedon323 said:
I think so. Do you know the reason for it? Do you think it was because i had the XPOSED framework mod?
Click to expand...
Click to collapse
I use Xposed framework, I don't see that being the issue and how it could cause a hardware failure. I have heard this issue before when tons of people had their S3 died suddenly, there is a big thread of it in its forum.
You'll probably want to wait for the Nexus 5.
sent from xda premium app
eksasol said:
I use Xposed framework, I don't see that being the issue and how it could cause a hardware failure. I have heard this issue before when tons of people had their S3 died suddenly, there is a big thread of it in its forum.
You'll probably want to wait for the Nexus 5.
sent from xda premium app
Click to expand...
Click to collapse
That was my plan but I can't go another day without a phone D; isn't the Nexus basically a LG G2 just little tweaks and Kit Kat
theedon323 said:
That was my plan but I can't go another day without a phone D; isn't the Nexus basically a LG G2 just little tweaks and Kit Kat
Click to expand...
Click to collapse
Well it would be better if you have a backup phone. It will be based on the LG G2 and gsmarena.com even post is specs, but until it's officially announced by Google it's all speculation.
You could use get the G2, but since it's not the nexus you won't get the same software experience and developer support, price is a big deal as well. Also rumor is the Nexus 5 will support all LTE bands, but that's to be seen.
sent from xda premium app
So this happened to my phone. Brought it to a repair shop and said the EMMC was dead.
Long story short, credit card company refunded the purchase price, I bought a Nexus 5, but I still kept the dead Nexus 4.
Is it possible to buy a replacement part/motherboard to replace this, or is it completely shot (fine with that)?
If it is dead, I was going to recycle it or offer it up for parts. With an EMMC brick, is there anyway to recover any of my personal information that was on the phone?
Thanks!
You'd have to get a new motherboard. Check eBay. No way to get your info off out that I know.
Out of curiosity, what were your symptoms of the phone?. Did you ever try to lock the bootloader and it wouldn't lock?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You'd have to get a new motherboard. Check eBay. No way to get your info off out that I know.
Out of curiosity, what were your symptoms of the phone?. Did you ever try to lock the bootloader and it wouldn't lock?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Motherboard ~$100. Might give it try. The teardown instructions dont' seem too daunting. Do I have to worry about this IMEI stuff?
As for symptoms. I was completely stock, and locked bootloader. I was doing something and then it froze on me.
Went to reboot, and it was stuck on the boot animation (merging dots).
Ended up trying a tool kit to flash the phone. It worked, got back into the system and as it was downloading apps, it froze again.
This time, when I went to reflash, it would error would error with a "failure to write to flash".
recovery.img flashing
your emmc is not corrupt. you want to flash single file of recovery.img.this file is in the firmware find by extract firmware by winrar and 7zip. first flash recovery.img than flash whole firmware by adb 100% it works . and also take help from nexus toolkit in future
owaisali said:
your emmc is not corrupt. you want to flash single file of recovery.img.this file is in the firmware find by extract firmware by winrar and 7zip. first flash recovery.img than flash whole firmware by adb 100% it works . and also take help from nexus toolkit in future
Click to expand...
Click to collapse
You realize this thread is two years old right ?
but i read it know
boltthrower56 said:
You realize this thread is two years old right ?
Click to expand...
Click to collapse
dear i don't know who is you but i read it know because of that i give the solution of these problem hehehe
owaisali said:
dear i don't know who is you but i read it know because of that i give the solution of these problem hehehe
Click to expand...
Click to collapse
It could help someone here, I'm facing the same issue, could you please detail your suggestion please?
Here is my request for help...
http://forum.xda-developers.com/nexus-4/help/nexus-4-stuck-animation-android-t3419997
Newbie here... :/
Does anyone know what's the cause of this? I built Omni yesterday and it was fine, but I tried to flash another one I built today and that's what it tells me followed by the phone getting stuck during the bootanimation when the logo turns fully green. And, the thing is that I checked the zip and there is a file_contexts.
rickoslyder said:
Does anyone know what's the cause of this? I built Omni yesterday and it was fine, but I tried to flash another one I built today and that's what it tells me followed by the phone getting stuck during the bootanimation when the logo turns fully green. And, the thing is that I checked the zip and there is a file_contexts.
Click to expand...
Click to collapse
The file_context warning has nothing to do with you not being able to build. See if you can get a logcat to see what is going on.
Sent from my Xperia T using Tapatalk
scanno said:
The file_context warning has nothing to do with you not being able to build. See if you can get a logcat to see what is going on.
Sent from my Xperia T using Tapatalk
Click to expand...
Click to collapse
No no, you misunderstood. I can build fine, but I can't boot.
I saw the same warning, with no apparent ill effect, on these I just flashed:
omni-4.3.0-20131020-i9300-HOMEMADE
omni-4.3.0-20131022-m7ul-HOMEMADE
HTC One and GS3 seem to be running fine.
rickoslyder said:
No no, you misunderstood. I can build fine, but I can't boot.
Click to expand...
Click to collapse
Sorry that was a typo, I ment boot (auto correct is a pain sometimes).
But getting a logcat (if you get that far in the boot process) can help in diagnosing the problem.
Sent from my Nexus 10 using Tapatalk 4
scanno said:
Sorry that was a typo, I ment boot (auto correct is a pain sometimes).
But getting a logcat (if you get that far in the boot process) can help in diagnosing the problem.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Doesn't let me logcat. I'm gonna download Rebellos's Omni and see if that boots, probably should have done that first thing now that I think about it..
rickoslyder said:
Doesn't let me logcat. I'm gonna download Rebellos's Omni and see if that boots, probably should have done that first thing now that I think about it..
Click to expand...
Click to collapse
Hmm works with Rebellos's zip..
*sighs* Resynced and rebuilt today and it's booting first time. Don't know what changed but mods, you can lock/delete this now.
I got this trying to do adb push to a Nexus 4 and the ROM will not flash...
nvm missunderstood.
gleggie said:
I got this trying to do adb push to a Nexus 4 and the ROM will not flash...
Click to expand...
Click to collapse
Wiping data and system seems to be what made it work for me.
[NO file_context ] problem with OmniRom 4.4.2
my phone is N7000 .. and i downloaded omnirom 4.4.2 from the site and paste it into the sd ,, when i make a flash to this rom .. a message appear to me
WARNING : no file_context
plz help me :-/
I think its the issue of that particular nightly build. I too had the same experience. So I flashed with another nightly and it works fine. After this error I changed to stock ROM but the flash counter didn't reset to 0. I tried to flash 3 times and now the counter is showing as 3. Can anyone advise me to reset it
Sent from my GT-I9100 using XDA Premium 4 mobile app
I got the same warning in recovery what does it mean?
Ronii10 said:
I got the same warning in recovery what does it mean?
Click to expand...
Click to collapse
My guess would be vastly outdated recovery but who knows.
Okay how do i update?
help
i am using system extractor and repacking, but it saids needed file_contexts. i dont know is the one in the rom zip or i need to make a new one?
Hello!
I have a problem with my Nexus 4. It seems doesn't have any os or recovery installed, and when i try to flash any of them, they are flashing well, without any errors, but when i try to open the phone, it remains stuck at the Google logo. It does the same when i try to enter recovery. I don't know what the problem is, i tried everything i could. I replaced the battery, thinking this may be the problem, but still no succes. I'd be very very thankful to you if you could help me with this. Thanks in advance!
Please guys, i really need some help.
Have you tried flashing the factory image with fastboot?
Sent from my Nexus 5 using XDA Free mobile app
Yes, i tried, but it's not working.
Provided you flashed everything correctly if it's still not booting it's a hardware issue.
I was thinking at this, but i was hoping that is not true, that i can do something to fix it. But i guess it's nothing more i can do
razor11911 said:
I was thinking at this, but i was hoping that is not true, that i can do something to fix it. But i guess it's nothing more i can do
Click to expand...
Click to collapse
Try locking the bootloader and then reboot. Does it stay locked? If it doesn't your emmc may be bad. I've seen this issue before
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try locking the bootloader and then reboot. Does it stay locked? If it doesn't your emmc may be bad. I've seen this issue before
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, it remains locked.