Hi,
I've got a Nexus 4 Device that has unknown IMEI and BaseBand, hence i can't connect to any mobile network.
the things i've tried to do:
1. Flash to factory image from google (tried several version 4.2/4.4) using ADB fastboot which ran succesful all the way, i just got stuck on the nexus logo when it tries to load ( and yes i tried to delete cache and wipe data before and afterwards, it doesn't work)
2. tried to install different types of radio images on the device regardless of Roms.
3. tried to install various custom roms.
Perhaps it's important to emphasis that, everytime after i tried to install an original google Rom (later than 4.2, my current) it just gets stuck on the nexus logo. BUT, awkwardly, when i install the 4.2 version it does manages to load it succesfully but then again, the IMEI is missing and so does the broadband.
I remember that, originally, this issue occured right after downloading and installing from Google Play store the Root explorer app, when I wasn't actually rooted. I'm not sure exactly how it damaged my deviced that badly, though i find it hard to believe it was the original reason. Rationally thinking, I simply shouldn't be able to access root files in the first place, not lose my IMEI.
*note - I've heard of a HW device called OctoplusBox, that can rewrite the IMEI, though im not sure if even that could help since the baseband is also lost, I may need an expert on this.
i'll do my best to fill in everything i've got right here:
Current version: 4.2.2
Model Number: Nexus 4
Kernel Version: 3.4.0-perf-g7ce11cd android [email protected] #1
Build number: JDQ39
*in the "Status", everything including IMEI/svIMEI/broadband is all unknown.
Thanks in advance,
Let me know if your in a need of any additional information regarding the device.
Related
Hard- and Software specifications:
Modelnumber: GT-P6800, bought in Austria
Android Version: 3.2
Baseband: P6800XXLA3
Kernel-Version: 2.6.36-P6800XXLA-CL614409 [email protected] #3 SMP PREEMPT Thu Jan 5
Buildnumber: HTJ85B.XXLA3 P6800XXLA3
History:
I successfully rooted my device with root_P6800_P6810.zip according to:
http://forum.xda-developers.com/showpost.php?p=21930246&postcount=7
In the following hours I installed, updated and used a couple of apps, among them LBE and Permissions Denied. I didn't do anything spectacular to the device IMO.
It's hard to remember, but I dare to day, that somehow Permissions Denied is involved in the "death" of the WIFI module, as it was one of the last actions on the device.
No matter how hard I try, it's no longer possible for me to receive any data over WLAN as well as GSM/3G.
It's however odd to see that the P6800 is still connected to my WLAN router and replies to PINGs.
Phone calls are still possible.
Measures I did so far:
At first I checked every possible setting that is associated with the device, WLAN and so on.
I did a factory reset through the corresponding phone code. No cure.
Having read numerous of threads and postings in XDA I successfully reverted back to P6800XXLA3_P6800OXALA3_ATO, most likely the firmware the P6800 came originally with, through Odin. But no cure for the WIFI module.
Strangely, I can still see an icon for "Superuser"(?)
I would be pleased if some kind soul could help me to get my device out of the state it is currently in.
Thanks.
You should try doing a factory reset (under settings->privacy). That's the reason that the Superuser app is still there, though it shouldn't work any more since you flashed a stock ROM. If it still doesn't work after that, you could try reflashing a stock ROM through Odin, but if your router is still seeing your tab, then it's probably not a hardware problem.
FULL wipe in CWM recovery, including System partition etc
Then immediately boot into download mode and flash your stock firmware.
Edit : if all good, root and reinstall CWM recovery again
Sent from my GT-P6810 using xda premium
i just upgraded my nexus 7 to 4.2.1 and now i get Unknown Baseband in Settings, and when i try clicking the Mobile Network in settings, i get a Force Close, i've tried reflashing the radio from the factory image bundle, but still the same, any help please?
i googled and found out it has something to do with the efs (/factory) being corrupted, but all i did was update to 4.2.1 and root it, no even using any sim card since i'm in afghanistan for my tour..any help is really appreciated
For transparency's sake, describe exactly how you upgraded. I think I read in another thread you forced/faked the update? It (hopefully!?) is the reason, the fix..... Is there a stock image for the 3G N7 out there yet? Although no idea if that includes /efi and if you can/cannot use it from another device.
i used the file CUSTOM_RECOVERY-65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56 to update it, because if i tried using the OTA link, it would get stuck at build.prop edit since the recovery is not for tilapia roms..after that i re-rooted using the toolkit, and then re-installed the recovery..yes there is a stock image for N73G, i've setup tons of stuff so if anything else doesnt help, i guess wipe will be the only option
https://developers.google.com/android/nexus/images#nakasig
this is the file; http://forum.xda-developers.com/showthread.php?t=2020438
reflashed the stock rom and everything is good now, trying to root now lets see
Hi all, really need your help. 2 weeks ago I bought this device, before never used android. 3 days ago by connecting it to a computer, the Kies software has given the message
"that there is a new version", I agreed, and then device as if replaced, it start to work slowly stucking on some screens, such as phone book or phone itself, it gives a strange message, that he had to stop the work of a program. Then I tried to solve the problem, but everything i did not fixed the issue, I even think that made it worse. I did the following things.
I tried to root device, did it as it was written on some site, after a Odin has finished, I found SuperSu program, but SuperSu wrote that the binary ihe s not installed, checking the Root, no root access. 2 Performed Data factory reset twice did not helped, Performed to flash again the latest official firmware, but also did not helped, the problem not solved, Uninstall SuperSu. no longer know how else to help themselves, need professional help.
Please write me what should i do? how can return the previously firmware, or how to root it correctly and install new Rom.
My device is Galaxy S4 i9505 T-Mobile Germany version.
RoM version: I9505XXUDMH9
Kernel: 3.4.0-1220396
[email protected]#1
Build Number JDQ39.I9505XXUDMH9
sgotfrid said:
Hi all, really need your help. 2 weeks ago I bought this device, before never used android. 3 days ago by connecting it to a computer, the Kies software has given the message
"that there is a new version", I agreed, and then device as if replaced, it start to work slowly stucking on some screens, such as phone book or phone itself, it gives a strange message, that he had to stop the work of a program. Then I tried to solve the problem, but everything i did not fixed the issue, I even think that made it worse. I did the following things.
I tried to root device, did it as it was written on some site, after a Odin has finished, I found SuperSu program, but SuperSu wrote that the binary ihe s not installed, checking the Root, no root access. 2 Performed Data factory reset twice did not helped, Performed to flash again the latest official firmware, but also did not helped, the problem not solved, Uninstall SuperSu. no longer know how else to help themselves, need professional help.
Please write me what should i do? how can return the previously firmware, or how to root it correctly and install new Rom.
My device is Galaxy S4 i9505 T-Mobile Germany version.
RoM version: I9505XXUDMH9
Kernel: 3.4.0-1220396
[email protected]#1
Build Number JDQ39.I9505XXUDMH9
Click to expand...
Click to collapse
Try Emergency Firmware Update in Samsung Kies, it will full format your phone and reinstall the stock version for your phone
I installed TWRP bootloader onto my OEM Unlocked Samsung Galaxy Core Prime G360P Via Odin, and afterwords attempted to boot into Bootloader.
Upon doing so the phones screen goes black, and it acts like its turned off. My computer can't detect it with ADB, and I can't boot it back on without removing the battery and then inserting it again, after which it boots normally.
So yes my phone is working, but I need to get the bootloader working, I don't even have the normal android one right now because of this odd bug, i have rooted phones and tablets before both via Kingroot, and ADB depending on the needs of the device, and have some slight experience with it but limited technical knowledge, i have found seemingly similar problems but all said to solve via ADB, which doesnt really work as my ADB cant detect my phone when it is in this dead state it goes into instead of bootloader.
I would like a fix that will allow me to have TWRP installed, nothing that requires root as i have attempted all one-click rooters and none work for my phone, and i cannot install a custom OS as I am on textnow wireless and getting it to work with one is the biggest pain on earth (plus my calling would become sh^te without the custom textnow rom calling)
So basically i need to fix the bootloader without installing a new OS altogether, without deleting any of my inbuilt apps, and without factory resetting as I cant get to the bootloader to factory reset anyway, honestly i just need a way to get TWRP to work. If the answer involves another way of rooting my phone via Odin (yes i can still get to the odin downloader) and then running a root requiring app to fix my recovery thats fine but i dont know how to do that or what it would entail
im using: twrp-3.0.2-0-cprimeltemtr
Textnow wireless uses a custom os that is slightly modified from the default, I don't know what that entails but i know that affects what fixes may/may not work so i am mentioning it
before i get the same answers i have tried:
redownloading TWRP and flashing the new copy instead in case of corrupted image
removing the battery after flashing and then booting directly into bootloader so as to stop it restoring anything
I have tried flashing other recoverys, however upon doing so found that when i tried to boot into the bootloader it would then boot to Odin instead and give me an error saying it was unable to boot normally, so i reflashed the TWRP one and it gave me the same blackscreen once again.
Any advice would be very helpfull, im at my wits end and id like to be able to recover my phone should it have problems later, id much prefer i not get stuck
Software Version: G360PVPS2APE2
Hardware Version: G360P .03
Model #:SM-G360P
Android Version : 4.4.4
Android Security Patch Level: 2016-06-01
Kernel Version:2.10.28-675169
Build #: TNG360PVPS2APE2
SOLVED
http://forum.xda-developers.com/gal...ime-sm-g360p-root-t3217885/page2#post70113291
I found something that worked highly reccomend this autoinstaller for Odin
Search the forums for stock rooted deodexed sm-g360p, thats the TWRP that I use ... almost to much. The rom is also alot more susceptible to root,mods,and tweaks. The rom is sprint, boosts a sprint partner. Its helped me get the 4glte i couldnt pickup with the boost. But definitely find that post. Twrp isn't official to our variant(that i know yet) but it works the same tho a lil dated.
Is anyone having problems with Bluetooth on their device? Just need to enable it on mine because I used 2FA with my Google account, & have a security token.
Model Number: BTV-W09
Build Number: NRD90M test-keys
EMUI Version: 5.0
Android Version: 7.0
Everything else seems to be working, at least so far. Still only seeing 2.4 GHz frequency with WiFi, but getting 5.0 GHz working is something I can work on later.
My Bluetooth seems to be working fine. I am on EMUI 5 / Android 7.
the second update file likely did not install correctly when attempting the dload method correct? the solution is to install the second update file as a zip from twrp. that fixes the problem, and updates your system version to the correct btv-w09c128b350 (if your using us version) if you don't have the second update file you can download it using firmware finder app, be sure its the full ota version, as the others do not work with this method.
tomchism said:
the second update file likely did not install correctly when attempting the dload method correct? the solution is to install the second update file as a zip from twrp. that fixes the problem, and updates your system version to the correct btv-w09c128b350 (if your using us version) if you don't have the second update file you can download it using firmware finder app, be sure its the full ota version, as the others do not work with this method.
Click to expand...
Click to collapse
I love how people here use abbreviations so frivilously. TWRP?? I googled that and it seems to be a root method. Rooting the tablet isn't a solution to this and we need bluetooth and 5ghz working for US. I had an EU update installed before this, then I hear the US update is out and I hoped it fixed the bluetooth issue. But now I have a USA version with a disabled bluetooth and no 5ghz wifi radio. This tablet is becoming more of a pain than anything....
When it comes to Android, your best solution is not a Google search but a search of the forums here at XDA, TWRP, is a recovery system that can be installed on the device. Once installed it can be used to perform system backups and restores, install firmware install root, wipe a device, do all sorts of nifty things.
To install TWRP you need to unlock your device, the instructions for doing that are in a different forum. Once unlocked you will need to set up adb which instructions can be found in the install TWRP forum, each version of TWRP is device specific, so you have to get the right one. If you really want to dig into figuring out how to do this, you will need to spend several hours reading the forums about this device, or find a friend who knows how to do this that you can trust not to brick your device.
tomchism said:
When it comes to Android, your best solution is not a Google search but a search of the forums here at XDA, TWRP, is a recovery system that can be installed on the device. Once installed it can be used to perform system backups and restores, install firmware install root, wipe a device, do all sorts of nifty things.
To install TWRP you need to unlock your device, the instructions for doing that are in a different forum. Once unlocked you will need to set up adb which instructions can be found in the install TWRP forum, each version of TWRP is device specific, so you have to get the right one. If you really want to dig into figuring out how to do this, you will need to spend several hours reading the forums about this device, or find a friend who knows how to do this that you can trust not to brick your device.
Click to expand...
Click to collapse
does the above mentioned operation void my guarantee for the tablet ?
That's a difficult question to answer. The device comes with two recovery systems built in. There are not many scenarios where you can hard brick the device and are unable to restore it back to factory settings, locked unrooted and like new. Any warranty issue are likely to be hardware not software.
Hmm. I am in the process of using the dc-unlocker client to unlock my bootloader. When the client reads my phone, it shows the build number as NRD90M test-keys, but when I look at device info on the phone, it shows a normal build number. Does anybody know what this means?