Hi All,
Thought I'd just quickly share this out here and wonder if anyone else has come across this and can either help or point in a right direction...
Basically we received a Nexus 4 brand new from our carrier in Norway. Upon starting it up we got no signal from the SIM card and in the about status we had "Baseband: Unknown, IMEI: Unknown, IMEI SV: Unknown" and that was that. Completely dead phone.
After reading the threads here and elsewhere we tried the usual tactics (flashing stock ROM, flashing stock 4.2.1 ROM) and still nothing.
It was at this point I saw a thread which involved erasing the cache. I thought I would do this through recovery but upon trying to boot into recovery all I got was the Android with red exclamation mark belly. From the stock ROM.
I proceeded to flash CWM-touch which flashed ok and went into recovery OK. Upon booting into the phone, the issue was resolved and we now have the radio working.
So a few questions are:
1. Why won't our phone boot into the stock recovery mode? Ideas?
2. Why would flashing a new recovery affect the radio functionality?
3. Anyone else seeing the recovery not booting issue?
But anyway, if someone comes across the IMEI unknown issue, try unlocking and flashing the CWM recovery to see if that fixes it.
Thanks,
Stoobert
Might need to find a baseband image and flash that to see if it works. If not, then the radio may be a dud. I'd say request an RMA or return the device, if thats possible.
We are looking at an RMA.
It just seems weird that the radio works fine if using a custom recovery and not the stock one in the 4.2 image.
Stoobert said:
We are looking at an RMA.
It just seems weird that the radio works fine if using a custom recovery and not the stock one in the 4.2 image.
Click to expand...
Click to collapse
Did you do anything else? someone I know has the exact same problem and flashing CWM didn't help.
Stoobert said:
I thought I would do this through recovery but upon trying to boot into recovery all I got was the Android with red exclamation mark belly.
...
1. Why won't our phone boot into the stock recovery mode? Ideas?
Click to expand...
Click to collapse
Um... I think that might actually be normal. I don't have Nexus 4 but on the GNex, you need to press power+volume up when seeing red triangle. See this: http://support.verizonwireless.com/clc/devices/knowledge_base.html?id=51446#alternate
I guess you need to press the same or similiar key combination.
I don't see why flashing a recovery will fix IMEI problem, but sure worth trying.
I'm having the same problem but I didnt do any flashing or modding at all. Bought it, put a sim in it and it worked for 6 hours. Then I remember accidentally dropping it a few times but not sure if that was what caused it. No IMEI no baseband. I tried to do as above but it won't proceed from recovery mode. Never gives me an option panel and just blacks out after I press volume up and power buttons when I see the lying android and red exclaimation sign.
The folks at whirlpool said people here might be able to help
I followed as the instructions but I noticed on the "recovery" screen their last item is lock state "unlocked" but mine is "locked" does that make a difference?
I did nothing to the new phone save install lookout, tripview lite, tumblr, accuweather, farmtower, JA sensei, adobe reader, JED and whatsapp.
Please help?
Thanks in advance,
Yannie
I was playing around with the *#*#4636#*#* testing screen and I was switching the IMS registration,required, SMS over IMS and lye ram dump on and off at random and I manage to get the IMEI and baseband back again. So I turned off the phone and put my sim in but I lost it again after the restart. I don't remember what exactly I did to bring the values back so I guess I'll keep playing with it with my sim in...
Yea u need to hold power and volume up to access stock recovery.
was there any solution to this problem? I have this issue at the moment....
hachoo said:
was there any solution to this problem? I have this issue at the moment....
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showpost.php?p=37702678&postcount=33
My Gnexi said:
Try this:
http://forum.xda-developers.com/showpost.php?p=37702678&postcount=33
Click to expand...
Click to collapse
thanks for this. i did flash to google factory image reset and it's fixed.
my imei and baseband lost when uninstalling busybox by stericson, and flash a faux kernel reset.
here's efrant's guide on how to return to stock google factory image: http://forum.xda-developers.com/showthread.php?t=2010312
[BASEBAND / RADIO] Brazil Radio Baseband For Nexus 4
I do not know if I'm in the right place.
I bought a Nexus 4 in the U.S.. And the sign here in Brazil is very weak. You get what for Radio Operators in Brazil?
jossanjp said:
I do not know if I'm in the right place.
I bought a Nexus 4 in the U.S.. And the sign here in Brazil is very weak. You get what for Radio Operators in Brazil?
Click to expand...
Click to collapse
Okay so today my Nexus 4 got problem updating to TWRP 2.6.1.0 so I went to CWM and then using fastboot flashed TWRP. After this I did factory reset and BAM. No Cell reception, no IMEI, nothing. I dont get how is it possible that factory reset from TWRP erased/messed up radio but restoring nandroid fixed my situation.
Right now I am trying the factory reset again to see what happens...Always backup guys!
Baseband unknown
Stoobert said:
Hi All,
Thought I'd just quickly share this out here and wonder if anyone else has come across this and can either help or point in a right direction...
Basically we received a Nexus 4 brand new from our carrier in Norway. Upon starting it up we got no signal from the SIM card and in the about status we had "Baseband: Unknown, IMEI: Unknown, IMEI SV: Unknown" and that was that. Completely dead phone.
After reading the threads here and elsewhere we tried the usual tactics (flashing stock ROM, flashing stock 4.2.1 ROM) and still nothing.
It was at this point I saw a thread which involved erasing the cache. I thought I would do this through recovery but upon trying to boot into recovery all I got was the Android with red exclamation mark belly. From the stock ROM.
I proceeded to flash CWM-touch which flashed ok and went into recovery OK. Upon booting into the phone, the issue was resolved and we now have the radio working.
So a few questions are:
1. Why won't our phone boot into the stock recovery mode? Ideas?
2. Why would flashing a new recovery affect the radio functionality?
3. Anyone else seeing the recovery not booting issue?
But anyway, if someone comes across the IMEI unknown issue, try unlocking and flashing the CWM recovery to see if that fixes it.
Thanks,
Stoobert
Click to expand...
Click to collapse
I have tried above steps and not only that tried every steps mentioned in this post. Still my radio signal is not coming. Can you please suggest me exact problem for this issue as well as solution. I am not sure why this is happening. And all this started when I do OTA update of 4.3 .
Can anybody suggest me the stable build and baseband image of 4.2 so that my phone will work normally. Or it is not going to get normal ?
fix unknown baseband
flash to older cwm n reflash ur rom n radio .... it fix due to SELinux
This is correct. I was experiencing this error while attempting to install Paranoid Android myself. The solution was to download this version of CWM and flash it. (fastboot flash recovery <filename>)
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-mako.img
Afterwards, I proceeded to reset the process. (Factory reset/wipe, Install Bootloader/Radio zips, Install ROM, Install GAPPS) and everything worked perfectly.
Perhaps all the steps were not needed, I am not sure which are. But I did them all just to be sure.
Stoobert said:
Hi All,
Thought I'd just quickly share this out here and wonder if anyone else has come across this and can either help or point in a right direction...
Basically we received a Nexus 4 brand new from our carrier in Norway. Upon starting it up we got no signal from the SIM card and in the about status we had "Baseband: Unknown, IMEI: Unknown, IMEI SV: Unknown" and that was that. Completely dead phone.
After reading the threads here and elsewhere we tried the usual tactics (flashing stock ROM, flashing stock 4.2.1 ROM) and still nothing.
It was at this point I saw a thread which involved erasing the cache. I thought I would do this through recovery but upon trying to boot into recovery all I got was the Android with red exclamation mark belly. From the stock ROM.
I proceeded to flash CWM-touch which flashed ok and went into recovery OK. Upon booting into the phone, the issue was resolved and we now have the radio working.
So a few questions are:
1. Why won't our phone boot into the stock recovery mode? Ideas?
2. Why would flashing a new recovery affect the radio functionality?
3. Anyone else seeing the recovery not booting issue?
But anyway, if someone comes across the IMEI unknown issue, try unlocking and flashing the CWM recovery to see if that fixes it.
Thanks,
Stoobert
Click to expand...
Click to collapse
it didn't fix my phone
ReCreate said:
This is correct. I was experiencing this error while attempting to install Paranoid Android myself. The solution was to download this version of CWM and flash it. (fastboot flash recovery <filename>)
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-mako.img
Afterwards, I proceeded to reset the process. (Factory reset/wipe, Install Bootloader/Radio zips, Install ROM, Install GAPPS) and everything worked perfectly.
Perhaps all the steps were not needed, I am not sure which are. But I did them all just to be sure.
Click to expand...
Click to collapse
Dear Member...
please also share the Bootloader, Radio, Rom you used to stable the phone........
Today Android 4.4.3 was released, will mako's baseband reappear?
Android 4.4.4 will fix our baseband???
Related
I'll be as descriptive as possible.
I must have did a bad flash with CWM, so I tried to reflash with CWM, TWRP, and even the OEM recovery. When attempting to boot to recovery, the screen goes blank. My pc attempts to connect every drive letter I've got when I plug in the usb. Among which, I can access an image folder on the device. Can't figure out how a bad recovery flash does this, but I can't find a fix for the life of me. Phone works as it should. My problem is anything involving recovery will give me a black screen, so factory wipe will not work.
Any ideas would be well appreciated.
Thanks
I tried following this guide: http://forum.xda-developers.com/showthread.php?t=2471370
The program get's stuck at analyzing device and doesn't flash or download anything. It would be nice if I can perform at least a factory reset in case something wants to blow up in my face. If anyone has some ideas (ridiculous or not), feel free to let me know.
slicknessessity said:
I'll be as descriptive as possible.
I must have did a bad flash with CWM, so I tried to reflash with CWM, TWRP, and even the OEM recovery. When attempting to boot to recovery, the screen goes blank. My pc attempts to connect every drive letter I've got when I plug in the usb. Among which, I can access an image folder on the device. Can't figure out how a bad recovery flash does this, but I can't find a fix for the life of me. Phone works as it should. My problem is anything involving recovery will give me a black screen, so factory wipe will not work.
Any ideas would be well appreciated.
Thanks
Click to expand...
Click to collapse
Hey man you could try just using Flashify to flash a recovery...its a app...then boot to recovery
I tried using that method. It gives me the same thing. Maybe somewhere in the recovery location (or associated locations) seem to may have gotten damaged somehow during the bad flash? Flashing the phone completely I'm sure would do the trick. I came from the droid 4, so sbf/fastboot flash would solve all my problems. Searching around landed me to a kdz, which seemed to be an equivalent, but isn't working or maybe I'm doing something wrong? Any advice on this would be greatly appreciated.
I went and did a full flash using this method: http://forum.xda-developers.com/showthread.php?t=2448960. Since I couldn't find a recovery fix per se, I decided to flash the whole thing and start fresh (oh well).
It downgraded to 11A in the process, so the same can probably be said for 10B for compatible custom builds.
Could someone please offer some advice, i really am stumped on this one. I have a nexus 4 which is rooted has an unlocked bootloader and is running on the stock version of kitkat. Last week i changed network and as bizarre as it sounds when i got disconnected from three my phone bricked and got stuck on the boot logo.
Since then i went home and got the skipsoft toolkit up and running to essentially put a fresh rom on. Unfortunately no luck, i have gone into the bootloader and recovery,factory/wipe reset -- still no luck it's stuck on the boot logo. Now i realised that adb isn't working only fastboot which has also limited my options. i have tried multiple version of roms/recoverys etc.. they install which confirmed by the change of boot logo but that's it just hangs again.
Is there something else i can try? I would really appreciate some direction on it. Thanks very much in advanced.
airrunner said:
Could someone please offer some advice, i really am stumped on this one. I have a nexus 4 which is rooted has an unlocked bootloader and is running on the stock version of kitkat. Last week i changed network and as bizarre as it sounds when i got disconnected from three my phone bricked and got stuck on the boot logo.
Since then i went home and got the skipsoft toolkit up and running to essentially put a fresh rom on. Unfortunately no luck, i have gone into the bootloader and recovery,factory/wipe reset -- still no luck it's stuck on the boot logo. Now i realised that adb isn't working only fastboot which has also limited my options. i have tried multiple version of roms/recoverys etc.. they install which confirmed by the change of boot logo but that's it just hangs again.
Is there something else i can try? I would really appreciate some direction on it. Thanks very much in advanced.
Click to expand...
Click to collapse
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK..www.wugfresh.com/youtube
---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------
WelfareBaby said:
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK..www.wugfresh.com/
Click to expand...
Click to collapse
[/COLOR]
WelfareBaby said:
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK
Click to expand...
Click to collapse
I meant literally that i changed network from three to ee, which i also brought my original number over with it. The day my number transfered to ee my phone bricked and it's been stuck on boot loop since.
I have never used wugfresh before but i followed your instructions and spent sometime with it this morning. It's a very simple piece of software and i must admit i was feeling hopeful it might have fixed my boot-loop issue, but it hasn't. I have done factorywipes/wiped cache, flashed multiple version roms. As far as recovery i had TWRP running on my device, but for some reason i am no longer able to go into it only the bootloader. When i do click on recovery i got the android on its back with the exclamation mark, which obviously gives me the wipe options which i have done.
If there is anything else you can think of i would be greatly appreciative.
airrunner said:
[/COLOR]
I meant literally that i changed network from three to ee, which i also brought my original number over with it. The day my number transfered to ee my phone bricked and it's been stuck on boot loop since.
I have never used wugfresh before but i followed your instructions and spent sometime with it this morning. It's a very simple piece of software and i must admit i was feeling hopeful it might have fixed my boot-loop issue, but it hasn't. I have done factorywipes/wiped cache, flashed multiple version roms. As far as recovery i had TWRP running on my device, but for some reason i am no longer able to go into it only the bootloader. When i do click on recovery i got the android on its back with the exclamation mark, which obviously gives me the wipe options which i have done.
If there is anything else you can think of i would be greatly appreciative.
Click to expand...
Click to collapse
.
I really have no clue what changing network to ee is did you not create a backup if so you could restore it but since you can't once you get in bootloader and scroll to recovery you get dead android use to toolkit I told you and flash stock+unroot option it should work
---------- Post added at 12:57 AM ---------- Previous post was at 12:56 AM ----------
WelfareBaby said:
.
I really have no clue what changing network to ee is did you not create a backup if so you could restore it but since you can't once you get in bootloader and scroll to recovery you get dead android use to toolkit I told you and flash stock+unroot option it should work
Click to expand...
Click to collapse
If not pm me try to help you figure it out
I am very grateful you taking the time to help me with the boot issue. But i have actually just managed to sort it, finally!
It came down to me changing to an older radio version for 4.4.4., then i installed a 4.3 rom which it worked! I then upgraded to 5.01 and hey presto it's back to normal.
Thanks again nexus root tool-kit is definitely an essential
airrunner said:
I am very grateful you taking the time to help me with the boot issue. But i have actually just managed to sort it, finally!
It came down to me changing to an older radio version for 4.4.4., then i installed a 4.3 rom which it worked! I then upgraded to 5.01 and hey presto it's back to normal.
Thanks again nexus root tool-kit is definitely an essential
Click to expand...
Click to collapse
Your welcome glad I could help we all been in some situation before since you back up and running don't forget to make a backup of current rom always good idea to have that handy in case.. Cheers...
Hi everyone...
I have an awkward issue here with my Nexus 4...
It is in an eternal loop in bootlogo 5.1.1
I already did anything I found in Google search
Flashed ALL firmwares stock, tried some Cyanogenmod and nothing!
I already used simple .bat/.sh in stock folder, used Nexus Toolkit with bricked/bootloop ticked, SkipSoft Tookit and even a tutorial saying to use LGNPST to flash a developer version... this last one worked... but like said in tutorial, the rom is encrypted and the user can do nothing! After that, flashed stock rom and still got stucked in logo!
I did not say, but yes.. I always run ALL wipes
I do not know what else I can do! The phone seems to work normally. I can entry,
download mode, fastboot, recovery but system..
Any ideas?
Thanks for now and sorry about english!
Are you flashing the userdata.img file?
yes and no!
The same result... =/
After flashing userdata.img in fastboot, are you going into recovery using the power and volume buttons to perform a factory wipe?
yes... I already did that too!
Today in the morning, I installed a developer version 4.2 through LGNPST... The phone worked, but it is a old version, I want the last one 5.1.1 and I got the problem that internal memory shows 8GB instead of 16GB...
And I could not resolv this, even reading tutorials from xda forum
If anyone could give me a BIN file of 5.1.1 to use in LGNPST...
no one???
I'm facing the exact same issue, here my post
http://forum.xda-developers.com/nexus-4/help/nexus-4-stuck-animation-android-t3419997
Did u solved it?
No man...
unfortunately I ditched the device!
I've installed Android 4.2.2 and block OTA updates rooting the device, the problem is internally in the device, maybe is a hardware problem, I already made a test of the sensors and none works, for know I'm gonna use it just for phone calls and wapp...
thanks for answer....
I unlocked my bootloader and rooted all went well. I flashed Z.A.D Rom and all was good. i decided to give CM 13 a try so I made a backup in TWRP (checked all boxes to back up everything) flashed CM13 played around with it for a bit didnt like it so I went back to TWRP wiped everything and restored my back up. When the phone booted back up got message NO SIM and my wifi wouldn't work. So I thought maybe a bad flash I'll try to restore my back up again. Same results no sim and no wifi. So I Tried to flash CM 13 again because that was the last thing that worked. That now freezes at boot then power downs the phone (tried everything to get it to boot). So I then tried to Flash the Boot stack again and stock rom. That will boot but again no sim and no wifi. I'm at a loss right now and dont know what else to try. Can someone please help me.
killathenoob said:
I unlocked my bootloader and rooted all went well. I flashed Z.A.D Rom and all was good. i decided to give CM 13 a try so I made a backup in TWRP (checked all boxes to back up everything) flashed CM13 played around with it for a bit didnt like it so I went back to TWRP wiped everything and restored my back up. When the phone booted back up got message NO SIM and my wifi wouldn't work. So I thought maybe a bad flash I'll try to restore my back up again. Same results no sim and no wifi. So I Tried to flash CM 13 again because that was the last thing that worked. That now freezes at boot then power downs the phone (tried everything to get it to boot). So I then tried to Flash the Boot stack again and stock rom. That will boot but again no sim and no wifi. I'm at a loss right now and dont know what else to try. Can someone please help me.
Click to expand...
Click to collapse
To answer your own question, a simple search in the Q&A section will help you.
You might want to grab version B20 and roll back, on the bottom left of the page select "Software Updates"
https://www.zteusa.com/axon-7#support
Then follow this thread to use the proper commands:
http://forum.xda-developers.com/axon-7/how-to/please-check-wifi-flashing-bootloops-t3451544
killer23d said:
To answer your own question, a simple search in the Q&A section will help you.
You might want to grab version B20 and roll back, on the bottom left of the page select "Software Updates"
https://www.zteusa.com/axon-7#support
Then follow this thread to use the proper commands:
http://forum.xda-developers.com/axon-7/how-to/please-check-wifi-flashing-bootloops-t3451544
Click to expand...
Click to collapse
I dont know how i didnt find that I searched every section of this fourm I was trying everything for about 5 hours last night. But thank you very much i will do this now.
Hello all. I am about done with this phone. Let me give you a quick timeline.
I had a bootloader error, so I flashed the NPN25.137-35 images to get it working
I used it for about 1 week, installing all of the OTA security updates
One morning, my phone had restarted (I know because "You must enter your pattern after a restart")
Over the course of this day, google apps starting force closing and opening some of them would soft reboot the phone.
The next day, random apps were doing it too
Finally, after one crash, the OS never came back up, it was bootlooping
Upon a hard restart, the phone only boots into bootloader.
This is where I am now. I have downloaded NPN...35-5, NPNS...93-10, and NPNS...92.14. Unfortunately, trying to flash any of these give me a "prevaildation failed security update downgrade" error on every partition I try to flash. The phone just bootloops when I try to restart it.
Things I have tried:
Using fastboot to manually install one of the 3 packages mentioned above.
Using a toolkit to automate the install of the 3 packages.
Using Motorola Device Manager (Never got it to launch)
Flashing the blankflash bin (No usable image file found)
Android OEM unlock setting was not set before this crash, so I cannot unlock the bootloader.
Praying to various deities.
Unzipping the packages, editing the *info.txt file into androidinfo.txt and rezipping to use as an update package (Invalid info.txt error)
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
=~=~=~=~= SOLUTION FOUND =~=~=~=~=
This may not be a good solution for anyone else that has this issue, but recently Oreo came out and the OTA update was captured. I was able to flash the new OTA because it had a higher security level and at least got the phone bootable.
Do you know what software channel you were on? E.g. retus, retla, etc? If your phone was completely up to date with the OTA, then you can't use a firmware version of less than 92-14 or 93-14. Whether or not you use 92 or 93 depends on the channel.
Locked bootloader limits other possibilities unfortunately.
Retus. I can't guarantee it, but that looks familiar to me, like I had seen it somewhere in the "about phone" section. Is there a released Stock image that has the current security patch? I can't find it on XDA and I'm not trusting androidfixfiles.info or a link in a youtube video.
93-14 hasn't been leaked yet. So you'll be stuck for now.
Kilo__ said:
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
Click to expand...
Click to collapse
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
pastorbob62 said:
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
Click to expand...
Click to collapse
The phone was completely stock. It has the stock recovery and bootloader.
Kilo__ said:
The phone was completely stock. It has the stock recovery and bootloader.
Click to expand...
Click to collapse
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
pastorbob62 said:
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
Click to expand...
Click to collapse
I've tried that with a locked bootloader myself, it doesn't allow a non-signed image to boot. OP should give it a go as a 'hail Mary' attempt, but I wouldn't be holding my breath.
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
jhs39 said:
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
Click to expand...
Click to collapse
I agree. :good:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Kilo__ said:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Click to expand...
Click to collapse
Try flashing just the stock recovery, as it sounds like that is corrupt. Ideally you'd want to get a recovery that was the same build as you were on after all the OTAs had installed. At least you'd hope that that would give you the factory reset option.
If that doesn't work, there's fastboot commands to erase user data, cache, which would be pretty much what a factory reset would do. Hope you had your data backed up.
Oreo OTA came out recently. Someone grabbed the update file and uploaded it. I was able to flash it and get the phone to boot. The verdict is still out on if it'll be stable.