Related
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???
I got a bootloop after flashing a recovery, it would it bootloop at the and flash the recovery splash screen.
I can't boot into the phone
Which method do I use to switch recoveries?
This G2 is my pride and joy, and I am panicking quite a bit :/
I have additional info on the last post here V
http://forum.xda-developers.com/lg-...1-0-materialised-splash-t2926322#post56459568
To whoever finds me the solution, I will buy you a lunch!!
Hello. The only way of switching recoveries when you can't access your current custom recovery is by going back to stock using the "how to go back to stock" method that's stickied in the G2 General section.
Make sure you download the right firmware for your device, that you have the right drivers installed and that your phone (and computer is charged).
Everything else you might need can be found here: http://forum.xda-developers.com/showthread.php?t=2432476
Hello, I am not a noob and I have been rooting phones for quite a while!
I was on an Android N ROM, WETA and tupac, with TWRP 3.0.2-1 working just fine.. all of a sudden I couldn't boot into recovery or into my ROM.. so I decided to say screw it and booted into bootloader and used fastboot commands to stock MTC20F.. flashed all of it except userdata, but I did format userdata at the end. I then rebooted the phone and I still cannot get past the Google logo.. it just reboots the phone everytime.. Not sure where I went wrong but being on Project Fi, I can't just go into a store and get a new phone.. So I a have a big issue right now and have no idea where something went wrong.. I would greatly appreciate some help or guides of how to go about fixing this.. I don't know why but normally fastboot always fixes my issue!!
sorry i did not read fully,
your pc does not recognize the phone during the boot at all?
There are some ongoing issues with reverting back from N to MM..... Not sure if you are faced with the same issue or not, but I know a few people are in your boat, with no resolution at this time.
Heisenberg said:
[SIZE=+1]14. How To Update To Android 7.0 Nougat[/SIZE]
....
....
Please note: If you decide to upgrade to Nougat, at this stage you cannot return to Marshmallow. Trying to downgrade to MM has seen multiple bricks occur. I don't know why this is happening but it's happening.
Click to expand...
Click to collapse
Please join this thread to help troubleshoot.
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was the first boot I expected a decently long wait, after about 25 minutes I followed the guide's instructions for Verizon since it did say some Verizon users were experiencing long first boot times. I took the battery out like it said, put it back in, then proceeded to fastboot boot2.img, like the guide said. After letting it sit for an hour this time, I got the idea that something was obviously wrong. After multiple attempts with no success I tried to fix it myself. So far I have learned that on the fastboot screen it says my bootloader is locked again, even after unlocking it. I have tried flashing TWRP as a recovery, just to at least have a recovery boot, that does not work either unfortunately. So as of right now, all I have is a v20 that has no OS, a locked bootloader, no way of booting recovery, I can fastboot with no ADB, and its virtually a paperweight. If anyone has a solution to at least get back to Stock, I would greatly appreciate it! Thanks!
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Did you get it fixed?
frome901 said:
Did you get it fixed?
Click to expand...
Click to collapse
He has not responded to my pm
What roms can we use with dirty santa root?
me2151 said:
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Click to expand...
Click to collapse
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
TheDantee said:
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
Click to expand...
Click to collapse
In his case we needed to redo from step 3.
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc) http://www.hardreset.info/devices/lg/lg-v20/
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Bricked T-Mobile v20
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was flash a new rom on it then i get boot loop with TWRP. so i decide to OEM LOCK again after that everything was stuck on my phone just boot loop with LG so any solutions please help me...... THx u for help me.
Kinda nerve wrecking to read about all these "bricked" phones popping up after trying this method lol.. Perhaps I'll just wait until a more tried and true way comes out...
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
For anyone that isnt on sprint that has "bricked" their phone. There are kdz's that will allow you to reflash back to 'stock". Someone had an issue with the kdz, but it was an easy fix. If you failed the process, it can be restored. Just if it doesnt want to boot, just lock and unlock the bootloader...
If your phone doesnt have a kdz, I know TeamDev is working on a custom kdz for such phones. Don't bug him if it isn't finished as I type this.
Anyone that can't get into TWRP, or has failed the process. Either start back at step 3, or if you have TWRP installed but can't get to it, the manual way to get into TWRP is a pain.
Keep your back cover off and hold the volume down button for ease. Now press the power button and as soon as you see an LG logo, let go and repress the power button. Its tricky.... If you get the corrupted screen, pop your battery out and put it back in quick and repress volume down and power. Usually if Im quick enough the first LG logo will hang a lot longer than usual and that gives me time to enter TWRP. A factory reset screen will pop up. Hit Yes twice.
Please help urgent
lcovel said:
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc)
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Click to expand...
Click to collapse
Please can u help ke unbrick mine i bought this mobile in my country its expensive and has no support. I have tried all tools but still getting the error model unknown please help sir
Jaistah said:
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
Click to expand...
Click to collapse
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
yuppicide said:
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
Click to expand...
Click to collapse
it means dirty santa root got a high posibility rate of bricking a device compared to other root methods for other devices and if you have no experience in bricking phones before then you're screwed if it happens to you
Actually, if you follow the directions, almost none of the problems create a true brick-- which means unrecoverable. For most of the cases, you might get a soft brick, meaning you have to back out, use a KDZ to repair it or reflash something else, or start over from scratch and try again-- but usually (maybe with some help from here) you can pull the phone back into a usable state.
I would hazard to guess for the vast majority the process works fine, maybe with a hiccup, but I've not seen many reports of a truly unrecoverable brick from this method. It's complicated, yes, and you need to be ready to read a LOT to understand what's going on, but it seems pretty difficult to end up with a $700 paperweight with this.
So i have been trying tonroot my sprint lg v20 and everytime i try and go to the phone on mobile terminal to enter id
Then enter the apply patch /system/bin/atd /storage/emulated/0/dirtysanta i get this message and i cant go to step 2 to boot into recovery
Any help would be appreciated: i have a sprint v20 and i wanted to know if i have to flash the stock sprint rom or can i just flash lineage rom following this guide? I have it running on AT&T and i want to keep it on AT&T...
can you please assist
Could you help out, please? I don't believe I have hard bricked my LG V20 H910. However, I have read and tried all of the unbrick info out. It seems my screw up is unique. I completed dirty Santa then went to flash a custom. in the boot between that. I get a black screen and cant do anything even download mode will not come up. My PC does make its usual noises when i connect or disconnect, but my phone does nothing.
Ok, I managed to brick mine too. It's a VS995, it was running stock 1AC. I used the LGUP tool to downgrade it to VS99512A, and then did Dirty Sanata and TWRP. After booting into TWRP I decided to try lineage OS with Android 8.0, I did not make a backup of the Stock ROM, which was very stupid. Lineage OS 15.1 flashed but I had no cell service so I panicked and instead of wiping it in TWRP and using the backup of stock I should have created, I just opened LGUP and tried to downgrade it back to stock VSS99512A. Well LGUP said it worked, but when it went to boot it would hang at the Verizon logo with 4 pastel dots. Device manager could see an ADB device and I could connect to it with ADB. So I did and read the logcat. I could see it was trying to update as part of the rollback, but it appeared that some components from Android 8x could not be "upgraded" to Andoird 7.x. There was a repeated error about failing to update SQLite instance version from 3 to 1.
The one feature that could fix this is if the refurbish function worked with any of the VS995 KDZ files we all have access to. But alas, none work instead we only get the upgrade function... or so I thought. Somewhere in my search for the past 2 weeks I found a modified LGUP https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
**Please be warned what I did was absolutely ****ing stupid, and it was sheer luck I didn't screw anything up.**
From what I can tell if you only flash ("LGUP Upgrade") the KDZ from the same model it never clears the partition it just adds to it. My problem was there was stuff from lineage OS 15 stuck on one of the partitions that was making the rollback to stock fail because it kept saying it couldn't update the SQLLite DB from 3 to 1. So no "upgrade" within LGUP would work because the upgrade function does not clear internal storage. But the link above is to a version someone modded so you can force a partition update from any KDZ onto the system. So I started playing around with forcing KDZs from other models onto my VS995, and I noticed when using the Partion DL function with non-VS995 KDZ files it would say something about the partition changing. All I can assume is that the partition layout is so different on each model and it forces LGUP to re-partition the storage.
**Again I state for the record this was stupid, and I'm only fortunate it worked.**
I forced Partion DL of H91510d_00_VTR_CA_OP_1110.kdz, then H990N10b_00_OPEN_HK_DS_OP_1017.kdz, then back to VS99512A_06_1114_ARB00.kdz, then when it booted it gave the Verizon hello, and moved on finally but the setting service kept crashing while it was trying to load the Secure Boot screen. So I yanked the battery and went into the boot menu and did the Factory Reset function, and it worked.
Lesson learned, always make a backup and don't be so hasty to use tools that aren't fully functional (LGUP).
Perhaps what I've done may help others, maybe I've found out how to reimage or unbrick our V20s. Or maybe I just got really stupid lucky.
Started off by unlocking the bootloader on the December update (just got device the other day)
Used @munchy guide to install twrp and root the device
everything looked great
backed up stock
flashed everything but internal storage
installed lastest version of AOSiP
crashed during install so I thought ok, bad download. did a restore and got an error that system wasn't mounted. unchecked the box under mount, and restored. I reboot and all hell has broken loose. Fore close left and right. I go back to try and get to TWRP, and it's stock Recovery.
Follow guide again and get back into TWRP. I see that all my stuff is still there. So I do some reading and saw some folks having similar problems with TWRP not sticking, so I find some instructions in the TWRP thread that I need to flash the TWRP image to both slots, run the install patcher and should be all set. I do that...wipe again, restore and now I am in a continuous bootloop. I tried to switch slots, do a restore on the other slot....bootloop.
I feel really stupid and really bummed out that even with all my years and experience, I somehow found myself in this noob trap. Is anyone able to help me at least get back to just stock? All I really want at this point is to be back on stock with root so I can run an ad blocker. Thanks everyone
Mods - could you please close? I know have a hardware issue (lol), a rubber ring on the inside of USB port has come out and wedged inside the port, rendering the device defective. Thank you