I have found the correct vzw factory image for the pixel 4 but i am having trouble figuring out how to flash the device. i have flashed samsung devices in the past and found that was much easier. i am wanting to flash the device due to facing many software issues and the fact google does not want to help resolve any issues. i have triied factory reset through settings and through recovery mode and still have issues so i am hoping flashing the device will resolve the issues. if anyone can help would be greatly appreciated
Would it be the same as following a good to unroot and flash a unlocked pixel 4 back to stock. Minus the bootloader parts.
Related
I was on stock android version 4.2.2 with stock recovery and unrooted when I received the 4.3 version notification after updating the boot animation remained stuck on the X logo for hours and clearing cache,data from stock recovery didn't help it boot. I flashed the factory 4.2.2 image and it finally booted but I had no phone signal only wifi was working. On inspection I discovered that the baseband was 'unknown' and IMEI number, IMEI SV reset to zero. Strangely the baseband was being detected while in bootloader mode. I have tried both custom recoveries, flashed various roms through custum recovery as well as stock factory images right uptil kitkat. These are my findings:
All Android 4.2.2(and 4.2.1) based roms boot but with baseband unknown and IMEI 0 rendering the phone unable to make calls and send/receive text messages.
All Android 4.3 roms don't boot are stuck at boot animation(flashing old radios like 0.48 and other older versions didn't help)
All Android 4.4 roms also behave the same way as 4.3 i.e stuck at boot animation.
Bottom line is I am stuck on Android 4.2x with a non working radio IMEI=0.... My device is now a mere tablet with inability to be updated. I have seen many people with similar problems but all such threads remain unresolved. I don't know what bug in 4.3 has done this to my phone I even tried the 99 percent working unbrick method but to no avail. I am considering selling this phone at a big loss(cant do much because I am in Pakistan) if any experienced developer is able to help me with fixing my phone(if that's even possible) then I shall be really grateful. Otherwise its bye bye Nexus 4.
liquidmetal88 said:
I was on stock android version 4.2.2 with stock recovery and unrooted when I received the 4.3 version notification after updating the boot animation remained stuck on the X logo for hours and clearing cache,data from stock recovery didn't help it boot. I flashed the factory 4.2.2 image and it finally booted but I had no phone signal only wifi was working. On inspection I discovered that the baseband was 'unknown' and IMEI number, IMEI SV reset to zero. Strangely the baseband was being detected while in bootloader mode. I have tried both custom recoveries, flashed various roms through custum recovery as well as stock factory images right uptil kitkat. These are my findings:
All Android 4.2.2(and 4.2.1) based roms boot but with baseband unknown and IMEI 0 rendering the phone unable to make calls and send/receive text messages.
All Android 4.3 roms don't boot are stuck at boot animation(flashing old radios like 0.48 and other older versions didn't help)
All Android 4.4 roms also behave the same way as 4.3 i.e stuck at boot animation.
Bottom line is I am stuck on Android 4.2x with a non working radio IMEI=0.... My device is now a mere tablet with inability to be updated. I have seen many people with similar problems but all such threads remain unresolved. I don't know what bug in 4.3 has done this to my phone I even tried the 99 percent working unbrick method but to no avail. I am considering selling this phone at a big loss(cant do much because I am in Pakistan) if any experienced developer is able to help me with fixing my phone(if that's even possible) then I shall be really grateful. Otherwise its bye bye Nexus 4.
Click to expand...
Click to collapse
try this for reference http://blog.falcondai.com/2013/10/fixing-galaxy-nexuss-imei-number.html
But this post specifically required the IMEI number to be exactly the SAME as mentioned otherwise it says the method wont work and it also seems to be T-Mobile blocked IMEI or something I don't think this fix is for my issue(correct me if I am wrong I am a noob lol)
My IMEI issue seems to linked to the Android 4.3 update which has broken something and this problem seems quite common on Nexus 4 as I came across many threads with people with exactly the same issue as mine. All the replies given usually say wipe cache and/or flash factory image sadly the problem remains.
I am really disappointed at my decision to buy the Nexus 4(my year long experience with the Galaxy Nexus was without issues) I never expected Google to release an update that breaks radios of many users(just google this problem many seem to have exactly the same symptoms as mine but the problem remained unresolved) and then remain silent despite many complaining on their product support forums.
Seems the device is beyond repair like most affected Nexus 4 phones(some have luckily got fixed by themselves it seems and IMEI appeared again)
Guess I will have to sell it at a very low price. I am skeptical about buying even the Nexus 5 now should I run into another dreaded unfixable IMEI issue caused by Google's own update(just paranoia I guess)
If only someone comes up with some fix I guess that will help plenty of disappointed Nexus 4 owners.
liquidmetal88 said:
But this post specifically required the IMEI number to be exactly the SAME as mentioned otherwise it says the method wont work and it also seems to be T-Mobile blocked IMEI or something I don't think this fix is for my issue(correct me if I am wrong I am a noob lol)
My IMEI issue seems to linked to the Android 4.3 update which has broken something and this problem seems quite common on Nexus 4 as I came across many threads with people with exactly the same issue as mine. All the replies given usually say wipe cache and/or flash factory image sadly the problem remains.
I am really disappointed at my decision to buy the Nexus 4(my year long experience with the Galaxy Nexus was without issues) I never expected Google to release an update that breaks radios of many users(just google this problem many seem to have exactly the same symptoms as mine but the problem remained unresolved) and then remain silent despite many complaining on their product support forums.
Seems the device is beyond repair like most affected Nexus 4 phones(some have luckily got fixed by themselves it seems and IMEI appeared again)
Guess I will have to sell it at a very low price. I am skeptical about buying even the Nexus 5 now should I run into another dreaded unfixable IMEI issue caused by Google's own update(just paranoia I guess)
If only someone comes up with some fix I guess that will help plenty of disappointed Nexus 4 owners.
Click to expand...
Click to collapse
Your IMEI information should be on your box if you still have it. Now there has to be a tutorial out there somewhere to enter IMEI info for your phone. I know I found some stuff when trying to this to a Galaxy S3.... I would keep looking or contact Google for a RMA
Still no luck. Now flashing the just released Kitkat image, who knows it may work.
Edit: Still the same result.
Wonder why only 4.2.2 based roms boot but 4.3x and 4.4 based ones do not. I also don't get why baseband is detected in the bootloader mode but not within the OS.
And what is the process of this RMA thingy? Is it applicable for countries outside US? I am from Pakistan btw and got it from a local shop. Nexus 4 can't be bought from Play Store in my country
Any Luck yet?
liquidmetal88 said:
Still no luck. Now flashing the just released Kitkat image, who knows it may work.
Edit: Still the same result.
Wonder why only 4.2.2 based roms boot but 4.3x and 4.4 based ones do not. I also don't get why baseband is detected in the bootloader mode but not within the OS.
And what is the process of this RMA thingy? Is it applicable for countries outside US? I am from Pakistan btw and got it from a local shop. Nexus 4 can't be bought from Play Store in my country
Click to expand...
Click to collapse
Hi @[liquidmetal88] did you get any solution, exactly the same issue as yours. Please share if you have solved it, would be of great help
sambitshankar said:
Hi @[liquidmetal88] did you get any solution, exactly the same issue as yours. Please share if you have solved it, would be of great help
Click to expand...
Click to collapse
Am also facing this issue...only the 4.2.2 boots with no basebanc versiono no IMEI no. and doesn't detects any Sim card
Unlike Samsung phones, the imei cannot be re-injected into the phone's file system. People have had to return the phone to Google to have it fixed.
If you try to install a stock 4.3 or 4.4 ROM, the phone will not even boot to the desktop.
Yesterday I noticed that there was no network service on the phone in my room and thought a reboot might solve the problem. I rebooted and it got stuck in the "Android is upgrading" screen. This is what I've tried so far:
-Factory resets
-Flashing a couple other ROMs I had in the SD Card
-Flashing Factory Images - The only factory image that booted was 4.2.2, but without IMEI or network connectivity. Any attempt to upgrade or flash a different factory image results in being stuck at the bootlogo.
-Using adb to do wipes and flash a custom ROM after flashing a factory image.
Any ideas on what I should do? I'm not sure if I can take it to warranty because even though it's only a few months old, I bought it from someone else on eBay, and the receipt is on that person's name. Any help or insight is very much appreciated. Thanks.
If flashing a factory image doens't solve the problem, it might be a hardware failure.
Try to send it back to LG/Google. The name on the receipt can be anybody.
Yeah I am having the same issue 3 days after my year mark, Google basically told me contact lg.
Sent from my Nexus 4 using Tapatalk
I have read other posts where anything newer than 4.2.2 will not boot if the imei is messed up.
So I've searched around the past few hours and can't seem to find a solution to my issue. I have a friend that is currently down on his luck and staying at a homeless shelter, he bought this phone because phones are pretty much a necessity nowadays, samsung galaxy on5, trouble is that the phone was locked when he turned it on so he was stuck with a paperweight, it's been a long time since I tinkered with phones but I figured I could help him out by booting into recovery and doing a factory reset. I had no idea about samsung factory reset protection and now were back to paperweight mode. I downloaded jodin3 and heimdall, but it never shows as connected. Can I root the phone while in recovery or load the factory rom so I can get the phone working again? Thanks for any help.
No, the only options are either ordering a remote unlocking service or find a guide on YouTube. The YouTube way will involve some patience and trial and error. Many guides don't specify what update on the phone they are working on and/or will state that their particular method works for EVERY phone. The stock recovery will tell you what update that it is on by the build number. This might help pinpoint which method to work.
FRP = Google Factory Reset Protection
Samsung Reactivation Lock is a different beast.
Which one does the phone have?
Ok lets see, I'll try to keep this as brief as possible.
I have a Nexus 6p with Cricket Wireless.
I was running PureNexus 7.1.2 which kept crashing, so I decided to revert back to 7.1.1. After successfully flashing factory image Angler N4F26T, I've noticed my device is now showing...
Code:
Build number
NOF27C (Pixel XL Rogers Only??????????)
Vendor version
NUF26N
PureNexus version
7.1.1-20170317-OFFICIAL
Kernel Version
3.10.73-ElementalX-N6P-4.06
So what the heck, guys? I used the flash-all script found within the factory image zip, I'm not getting a warning about vendor mismatch or anything like that. My 6p thinks its a Pixel XL and the Rogers Only bit concerns me. I know nothing about Rogers but I know my carrier is GSM, will this have any effect on me? Any help is greatly appreciated.
Hi everyone,
I had issues with the update of my OnePlus 5 as stated on this thread : https://forum.xda-developers.com/oneplus-5/help/oneplus-5-update-fails-t3866533
I tried the solutions that were given to me but it wouldn't work, since TWRP kept returning ERROR 7.
I finally managed to install OnePlus5Oxygen_23_OTA_040_all_1811051816_c6670cf.zip thanks to twrp-3.2.1-1-cheeseburger.img without getting any error but my phone got stuck at the "Dots turning" logo when I boot.
I looked around a lot trying to find a solution and as far as I understood, it may be due to the addition of Treble to OnePlus. I tried to wipe everything thanks to TWRP and flash my phone back to OxygenOS 5.1.3: OnePlus5Oxygen_23_OTA_036_all_1806131715_b5381c0ef26d9e.zip but it's still stuck.
Could anyone help me ?
Thanks a lot
This guide will help you: https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
A HUGE thank you ! It worked perfectly.
Note for people who might see this thread : it locked my bootloader, I had to unlock it back (and wipe all data). Flashed TWRP and Magisk, everything works perfectly