Develop Bugs

[Solved] Unbricking Solution for LG Nitro HD | Confirmed Working on Bell Optimus

Standard disclaimer:
This tutorial is for people who have bricked their phone due to messing about with important files/partitions on their Nitro HD and found that it won't boot up afterward. Prior to attempting this, see if you can access your phone while booting with adb in order to fix your problem. The method used in this tutorial should only be used as a last resort. Don't hold me responsible if this method somehow makes your problem worse (although, really, how much worse can it get than a phone that won't boot?).
Now that's out of the way, let's move on...
Things you'll need:
1) ADB: You can get this in the Android Developer SDK <-Once installed, install platform-tools and add the directory containing ADB to your PATH. Alternately, you can just grab the ADB folder from your SuperOneClick folder, copy it to C:/, and then add that directory to your PATH. Hell, you could even run all the commands from wherever you have the ADB folder, just make sure you have it.
2) LG P930 drivers: http://s3.amazonaws.com/lgforum.com/resources/assets/680/original/LGP930.zip
3) LG Mobile Software Update Tool: http://csmg.lgmobile.com:9002/client/app/B2CAppSetup.exe
4) UpTestEX_mod2_marwin/KDZ_FW_UPD_EN: http://www.filesonic.com/file/2255759914/KDZ_FW_UPD_EN.zip
5) LG SU-640 firmware V10F_00.kdz: http://www.megaupload.com/?d=31XABWWJ
6) A method of rooting your phone. My preferred method is the latest SuperOneClick due to its simplicity. I won't really cover how to root your phone in this tutorial as it's covered elsewhere.
The following should only need to be downloaded if you were stupid like me and bricked your device before you made backups of the necessary partitions (This will be explained elsewhere, but needless to say it's as simple as switching the "if=" argument and "of=" argument in the dd commands toward the bottom):
7) boot.img: http://fileape.com/dl/OCowIxMnbDUMiPW6
8) recovery.img: http://fileape.com/dl/jFMlB8I3kkSMOYWN
9) firmware.img: http://fileape.com/dl/4gHHDDUhODLiJGHM
10) baseband.img: http://fileape.com/dl/TMsvdaKOa7VG4mVT
11) system.img: http://depositfiles.com/files/f0ke241ew
Alright, now that you have everything you need, let's move on to fixing your phone. I'm going to assume you are competent enough to install ADB (Android SDK or folder included to with SuperOneClick) to your system PATH. Go ahead and install the LG Mobile Software Tool and then install the drivers for LG P930 if you haven't already. Extract the KDZ_FW_EN.zip file. Note, in my case, I didn't have to do anything with the mfc42.dll or run WindowsEnabler as mentioned in similar tutorials elsewhere, but your mileage may vary.
Flashing the SU-640 rom:
1) Put your phone in download mode: power off the phone if it's not already, unplug the usb charging cable, and simultaneously hold the volume up button and plug the usb charging cable back in.
2) Open up UpTestEX_mod2_marwin. (If you know what you're doing, I've been told you can use KDZ_FW_UPD_EN as well, but since I didn't use it, I'm not going to discuss it)
3) Hit the folder icon next to the "Select kdz file" line and browse to the SU-640 v10f_00.kdz
4) Select "CSE web upgrade test", a new window with some options including an "Upgrade Start" button should appear.
5) Take a deep breath...there's no going back Press "Upgrade Start".
6) At this point in time another dialog box will appear asking what country and language the LG Mobile Upgrade tool should use. Since this guide is written in English, I assume you'll want to change it from Republic of Korea to All other countries and Korean to English. This affects the language that output messages are displayed in in the LG Update tool only, it doesn't affect anything with the rom (that'll be all Korean on initial startup lol).
7) The update tool will proceed to flash your phone, but it should never complete "normally" (mine never made it past 4% according to the tool and other users have reported similar behavior). However, your phone should reboot once or a couple of times and then just be sitting idle waiting for you to go through the setup wizard. At this point, just kill the LG update tool process in task manager, don't wait for it to complete because it won't.
Rooting your phone:
1) Now, on your phone you should see the standard Android startup wizard...in Korean. Hit the left button confirming you want to go through it, and on the next screen should be an option to switch the language to English. Ah, much better.
2) Go through the rest of the setup wizard if you want, but it's not necessary and you won't be able to set up accounts anyway unless you somehow have wifi.
3) Put the phone in USB debug mode and allow 3rd party sources. Don't freak out if the phone spontaneously reboots when you do this. It rebooted on me every single time I put it into debug mode for the first time (I flashed it several times lol).
4) Once it's rebooted itself, you should be able to connect in debug mode and connect via PC mode. Go ahead and root it using your preferred method. We're almost there!
Restoring Nitro HD partition images:
1) Open up a command prompt and navigate to the folder you saved your recovery images to (hopefully you put them in the same folder, it'll make your job easier)
2) Push all the image files to the phone's sdcard using the command:
Code:
adb push filename.img /sdcard
Alternately, you can just mount up your phone in My Computer and copy and paste the files over.
3) Now the real fun begins! Use the following commands:
Code:
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
4) You won't be able to issue a reboot command, so just hold power down on your phone til it's off and hold the volume down button so that it comes back up in factory data reset mode. You will want to pull your sdcard at this time if you don't want your data erased.
5) Hit power twice and your phone should go through its reset process and (hopefully!) come back up in a working (and rooted) AT&T "stock" rom
If you have any issues, it's possible I've forgotten some steps, so I'll address them in this thread. At this point, I'd like to thank specific people who helped me immensely getting a working phone again: bytecode64, gordec, schwin97, belth219, sukudos, and ziiljuks. (If I've missed you, I'm sorry, I'm thankful to this entire forum!)
Original post:
So I was messing with fonts (actually trying to get the "look of disapproval" from Reddit to display) and substituted DroidSansFallback with a kannada font using Font Installer *Root*. Well, long story short, it was causing issues with other non-english characters so I tried to restore *all* my fonts using the "stock" option that comes with Font Installer.
When I rebooted, my phone only got to the LG Screen and that's as far as it has gotten since. I can't do anything with it, but I can get to Factory Data Reset mode and Download mode. I tried plugging the phone into my computer, but it doesn't appear to get far enough to mount the disk. Odin recognizes it's attached when I put it in download mode, but obviously Odin doesn't work with our phones.
Does anyone know if there will ever be hope for my phone or should I pursue getting a replacement? I'm actually completely shocked that simply replacing fonts has bricked my phone to the point where it doesn't even boot. This has seriously made me reconsider tinkering with Android at all until recovery methods are possible. I'm more than willing to be a guinea pig at this point until I try to send it in for a replacement (within the next few days probably).
Click to expand...
Click to collapse

do a factory data reset ? my phone gets stuck on LG logo too when i try to move all my apps to SD using titanium backup . factory data reset option resolves it however . see if that works ?

Unfortunately factory reset won't help in this case, the app messed up something in the system.
But as long as it gets to the point when you can use adb (it comes with SuperOneClick if you don't have it installed), then yes, there still a chance
To make it easier, can you contact the app's author and ask what exactly that app changes in the system, which files, so if necessary we can provide you with these files.

[email protected],
I have adb from SuperOneClick, how would I know if I can use adb?
Edit, I guess what I'm asking is do you have a quick guide to connecting a phone using adb and pushing files that you can hit me with a link to?

open CMD window and type:
adb devices
It should show you your phone.

adb devices
If that comes back with a device listed you can still save your system. Good luck...

Okay, I'm at work now, but I'll check when I get home. I do believe I tried that command and it didn't show any connected devices, but I can't remember if I only tried that while I had it in Download mode or also while I was trying to boot it. I'm keeping my fingers crossed lol.

You should searching for the file named KDZ_FW_UPD_EN,and install LGMobile Support Tool which can be downloaded on the LG Official website.And then you should download the *.kdz file that matches your phone.
Finally launch the KDZ_FW_UPD_EN flash your phone with the kdz file.
I use the tool bring my bricked device back.
Good luck.

belth219,
Problem is I can't find a .kdz for my P930. This seems like it'd be really easy to do otherwise.

Alright, I've created a tutorial in the first post describing how I unbricked my phone. I don't think it's quite back to "stock", but I don't think anybody who bricks their phone will care about that.

You have done the great job.Thanks for the baseband.img.It made my SU640 closer to PERFECT!EDGE enabled!!
Sent from my LG-SU640 using XDA App

I can't claim credit (or blame lol) for creating any of the images in this tutorial. Gordec is responsible for 3/5 including the baseband and I am so glad he responded quickly with each image correctly copied!
Sent from my LG-P930 using xda premium

my 4g lte isn't working.

My 4G wasn't working until I did a factory data reset (a second one, actually). Is it just your LTE that's not working or 4G in general?
Sent from my LG-P930 using xda premium

Will this give a version that has wifi and regular calling available right off the bat? I messed up my nitro to the point that i can only sometimes make phone calls and my market / browser won't function at all. Force close immediately.
Think I should try this as an option?
AT&T LG Nitro HD P930 is my make
Also, I use it on TMobiles prepaid network. I only get edge. I checked the bands, I think im right but wanted reassurance that edge is all i can get. Thx

To the best of my knowledge, prepaid service providers only allow maximum 4G, but vary by provider. No prepaid that i know of allows access to the LTE network, only on a post-paid plan.
If you have a AT&T unit unlocked for use on another carrier, then there's not much you can do in this case. sorry.

basically my att data itself.
att goofed up on my data plan. The thing is great thanks a lot!

csmg.lgmobile.com:9002/swdata/WEBSW/LGSU640/ASKTBK/V10i_00/V10i_00.kdz
I couldn't get the version with the f's in the original post to work. Will this one do? It's 460 mb.

nope because you cant root the ...i version thus making it worthless.

Sandpapers,
I'm uploading the V10f_00.kdz to megaupload right now. I'll update my tutorial as soon as it's done. Sorry I didn't do this sooner.
Sent from my LG-P930 using xda premium

Cannot connect to mobile network???

Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.

First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...

Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore

jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
I tried a simple way which is format everything and flash another ROM but the problem remains.

TRS_80 said:
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
Click to expand...
Click to collapse
I don't know that we are in the same situation since at home I often got a good signal and this happened to me only since yesterday.

jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.

Dan Law 001 said:
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Click to expand...
Click to collapse
Results..??
Sent from my GT-I9001 using xda premium

jabrif said:
Results..??
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
I need to get the firmware first... since I already passed the download quota for today... need to wait until tomorrow...

Mmm... I heard that you mentioned clearing the EFS in your given procedure, but I do not think that I modified that folder... However, about few days ago, since I want to gain better control on the volume on my headphone remotes, I did modify the file called Generic.kl in system/usr/keylayout, but I restore it after since it didn't work. However, I don't think that this modification will trigger something in the efs folder since it has different directory. By the way, I did some research online and they say that the efs contains information about the carrier on the phone, so will there's a greater chance that the problem is caused by the possible modification on the efs than any other factor and will there also something else that possibly trigger the similar effects?
Sent from my GT-N7100 using xda premium

Still nothing

[Q] Baseband: Unknown, Modem boot timeout, Couldn't find 'rild' socket.

Hello all and a good day.
Device: Samsung Galaxy Note 8.0 GT-N5100 (3G) - XME (Malaysia)
What I did: Nothing unusual! Device mainly used for text reading and some writing. After updated to Android 4.2.2 (PDA: N5100XXCMI1, CSC: N5100OLBCMH2, MODEM: N5100XXCMI1) via ODIN, the symptom # 1 appeared. The firmware for Malaysia was downloaded from the sammobile.com.
Same time I came to know the importance of /efs backup, so rooted (1st time) the device, backed-up /efs via EFS Pro, used Triangle Away, unroot, and flashed the stock. Since the symptom # 1 continued, I did a factory reset, and then all other symptoms appeared.
Symptoms:
1) Tablet doesn’t vibrate.
2) Kies is unable to detect the tablet.
3) SIM Cards are not detected. A prohibition sign is shown at the cell signal (left to the battery indicator) (see image 1).
4) In “Settings > About device”, and in “Settings > About device > Status”, many fields are stated as “Unknown”, e.g.:
Baseband and IMEI (see image 1 and image 2). Incorrect Serial number (/efs has the correct one as in the back cover).
5) Camera view is upside down.
6) Proximity sensor doesn’t work. In the *#0*# Test mode, Proximity value is 1.0. If exit and check again value becomes 0.0.
7) Regardless of Flight mode or not Cell standby drains the battery a lot. Once activated, Flight mode turns grey (see image 3).
8) [SOLVED, see 5th post] Several times (not always), a white screen appeared at the boot screen (model name), and also when plugged to power source while the tablet switched off. I guess something to do with param partition.
9) [SOLVED, see 5th post] "No command" error message in the stock recovery (3e).
9) “Modem boot timeout” and “Couldn't find 'rild' socket” errors in logcat -b radio.
10) When tried to use the tablet as a modem from Windows 7, it gives an Error 692, and the diagnostics states, “Timed out waiting for response from modem”.
Solutions tried (no success): As many, I too tried various /efs based solutions mentioned in XDA, and flashed all the five firmwares available for the device, but the problem stays same. I tried to solve this without troubling others much, but now I am lost.
Help needed: Is this problem can be fixed by me with some guidance, which would be great since to claim warranty the tablet need to be send to another country. Or is it a hardware problem, therefore I should send it straight to Samsung service without wasting more time?
Attached files, if they help:
1) Outputs of the following commands
logcat -b radio
logcat *:E
dmesg
ls -la /efs
ls -la
mount
cbd -t xmm626x -o t
2)
- recovery log from - CivZ_rev1.1-PhilZ 5.1.1 (touch)
- build.prop file
Thank you for reading. Greatly appreciate any help and guidance. Sorry, if I violate any XDA rules in this post. Kind regards!

New Problem: "There is no PIT partition."
Last night managed to fix a part of the problem (customer.xml error in logcat) in the above post thanks to the guidance from civato. In an attempt to fix other problems, last night I had mistakenly executed the following cmd in ADB while in recovery.
Code:
dd if=/data/media/0/efs.img of=/dev/block/[B]mmcblk0[/B]
The correct one should have used is mmcblk0p3 (/efs partition in Note 8.0). At least I managed to do some damage, otherwise all the credit goes to Samsung.
Now I can go to download mode only. A white screen flashes if try recovery mode or normal boot or even connect to a power source to recharge. Since charging or not also unsure (before this happened battery was 100%), I have a limited time to use the device to get it to work properly. Other problem is, if fail, can’t claim warranty as there’s no way to use the Triangle Away in this situation.
Now when try to flash via ODIN:
1) normal way - it failed stating, "There is no PIT partition." (see image 1).
2) with kona3g.pit I have - it failed stating, "Re-partition operation failed." (see image 2).
Even when the device was working properly, 2nd option never worked for me.
My kona3g.pit read well by PIT Magic 1.3.10.
Can anyone provide me a working .pit for Note 8 GT-N5100. Thinking of trying Heimdall Suite 1.4.0 tonight, but need some reading as I never used it and limited battery time for flashing.
Any advice to recover my device is highly welcome.
King regards.

Here you go, unzip it and in Odin select repartition and then Odin a new stock rom. (PDA)
Or look here for the 5110 pit file it should alos work on the 5100 as the modem partition is also created.
reinstall your csc also after rom onstallation
PS try the included Odin

Working kona3g.pit for GT-N5100
civato said:
Here you go, unzip it and in Odin select repartition and then Odin a new stock rom. (PDA)
Or look here for the 5110 pit file it should alos work on the 5100 as the modem partition is also created.
reinstall your csc also after rom onstallation
PS try the included Odin
Click to expand...
Click to collapse
Brilliant and thank you! The Odin3_v3.07.exe you provided missing an Odin3.ini (see image). I used an Odin3.ini (see attached files) that I have (for the same version) together with your Odin3_v3.07.exe and kona3g.pit, and the flashing went perfectly without any errors. So your kona3g.pit is a genuine working one. Thank you
I’ll continue further tonight and post here. My friend share his laptop with me, therefore I have limited time.
EDIT: When looked from the PIT Magic 1.3.10, the GT-N5110.pit is same as the GT-N5100 one (kona3g.pit). But when looked from the HxD - Hexeditor 1.7.7.0, the signatures at the end of the files are different, so it might not work on the sister device. Also, your GT-N5110.pit has trailing zeros after the signature, somewhere I read that these zeros must be deleted from a hexeditor for it to work.
Kind regards!
Image:

Solutions for symptoms 8 & 9
Solution for symptom 8:
Googled for a param.bin for Note 8.0, but only found one for Galaxy S3. Anyway, being fed up with the white screen, I copied S3 param.bin to the mmcblk0p4 partition of Note 8.0, surprise it worked. But the boot screen became S3 . Later among my backups, I found a param backup of mmcblk0p4 that I took via EFS Pro. Unfortunately couldn't restore it via EFS Pro as I had renamed the tar.gz to keep things tidy. So I extracted it to get a file called param. Since this param didn't work after copying, I compared it in the hex editor with the working S3 param, and noticed EFS Pro add some data to the beginning of the file. I removed this begining data and also the trailing zeros, and renamed it to param.bin (to go along with the name in kona3g.pit, perhaps not necessary). Finally, copied it by "dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4" command, after couple of reboots white screen disappeared.
Solution for symptom 9:
Difficult to say this is a solution but it disappeared after this. In order to send for warranty claim, I restored the device to clean stock. First used Triangle Away to reset the counter. Booted and fully unroot via SuperSU. Then flashed the stock rom with the pit file, and without restart option. Shut down the device and boot into the recovery to do a full wipe, and the "No command" error wasn't there.
I must say, since my modem not working, capslock66's Android Reverse Tethering 3.15 saved my day to download the required Triangle Away add-on via laptop's broadband connection.
Since all other symptoms couldn't be solved my me after much effort, I sent the tablet for Samsung service.

T999L, failed unlock - now no imei, baseband nor nv_data

My tail of woe. From what I have read there is nothing that can be done but I thought I would ask anyhow.
I was overseas with an SGH-T999L, and took it to a man in a market to be unlocked. 2 hours later it was useless. The man said it would be OK once it was back in the US, but it wasn't. Obviously he didn't keep backups.
Dialing *#06# gives me "null/null".
I cannot turn on wifi (I slie the switch and it slides right back) but can turn on bluetooth, gps and nfc.
Baseband version is "Unknown"
Build number is JSS15J.T999LUVUBNC1
It appears that he used vRoot to get root.
According to the "odin screen"
CUSTOM BINARY DOWNLOAD: No
CURENT BINARY: Samsung Official
SYSTEM: STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER AP SWREV: 1
I used this article from techglobal101.wordpress.com 2013/05/02/how-to-solve-no-service-on-samsung-galaxy-s3/ following the imei already corrupt steps to generate
the text file with the imei in it. However the NV Reader/writer has problems. Firstly *#7284# only gives me a choice of "Modem" or "PDA". However *#0808# does give me more options including "RMNET + DM + MODEM". The bigger problem is that the SPC code of 000000 is not accepted, so NV reader/writer can not access anything.
Looking in the /efs filesystem (using "adb shell" and "su" and "busybox find /efs -size +1000k" ) does not find any files larger than 1MB (I believe the nv_data.bin should be at least 2MB) so no original ".nv_data" file, no "nv_data.bin" nor "nv_data.bak". There are smaller files, for example there is a file /efs/imei/mps_code.dat, 3 bytes long containing TMB. The /efs partition is 13716 blocks in size and is only 33% full (4556 blocks in use).
I can use adb to install and uninstall packages, and copy files.
Things which look interesting to me in the output of "getprop" are (with a valid sim card installed)
[DEVICE_PROVISIONED]: [1]
[gsm.operator.alpha]: []
[gsm.sim,state]: [NOT_READY]
[gsm.sim.unknownready]: [1]
So far I have not done anything else. In particular I have not tried using ODIN to download a stock image, nor have I tried removing the files which are in /efs.
I also have not tried creating a 2MB file of NUL characters called /efs/nv_data.bin in the hope that that would at least advance the solution.
I would be pleased to get any good advice on what to do next. Please assume I know my way around a unix command prompt, but this is my first venture into the world of Android.

First thing, don't mess with the efs. It's not relevant to the issue at hand and sounds to be just fine. Most of the NV Data is stored on different partitions. Don't assume its the same as on other devices like many others seem to advise.
Second, download your stock firmware (NC1)(root66 firmware is ok), flash via Odin on your computer, and factory reset (will wipe internal sd). This often fixes these problems without having to touch the NV data.
Something tells me that whoever you took it to may have tried to flash the 4.1.1 modem to use our free unlock method. If so, that will cause the exact same thing you are experiencing now.
If after that it is still not fixed, PM me and I will try to help get your imei restored. We are not allowed to post information, tools, links or further discuss that here, so if it comes to that, I can only help you via PM.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Question We need unbrick tool for Redmagic 6/6 pro

Hello everyone, I want to ask if there is any developer who can help us please, we need unbrick tool for Redmagic 6 and 6 pro ASAP because the RM support team doesn't answer our complaints or emails. Please help us

M5tha said:
Hello everyone, I want to ask if there is any developer who can help us please, we need unbrick tool for Redmagic 6 and 6 pro ASAP because the RM support team doesn't answer our complaints or emails. Please help us
Click to expand...
Click to collapse
i've been waiting for my paperweight turn into a phone for a month now, i don't think it will be here any soon....

Nocturne Seigneur said:
i've been waiting for my paperweight turn into a phone for a month now, i don't think it will be here any soon....
Click to expand...
Click to collapse
It’s like Cinderella turning into a pumpkin after midnight. Our devices went from being phones to paperweights overnight.
Someone get our fairy god mothers up in here to bipity bopity this crap back into a working state

Out of curiosity may I ask how did it get to this state? Also I was able to get myself out thru a combination of reflashing boot.img (i was on 4.12), unlocking and relocking bootloader, and factory resetting via recovery mode. Not in that order and each multiple times. Somehow it worked out. Possibly worth a try if you are just waiting anyways with not too much to lose?
I found that a locked bootloader is good at telling whether you didn't quite flash an img right. It kept telling me that things are corrupt and whatnot, and all of a sudden it booted.

So I'm pretty close to getting a working TWRP for this device. I have extracted a basic TWRP.img file and merged it with the boot image for the Red Magic 6. When I flashed it, the logo shows up but nothing happens.
When I have time this weekend, I'll mess around with it some more.
That way we can unbrick it with twrp and not have to worry about waiting for an unbrick tool.

Nocturne Seigneur said:
i've been waiting for my paperweight turn into a phone for a month now, i don't think it will be here any soon....
Click to expand...
Click to collapse
I didn't unlock my bootloader, so I can't do anything to unbric this **** device

M5tha said:
I didn't unlock my bootloader, so I can't do anything to unbric this **** device
Click to expand...
Click to collapse
I’m in the same boat but Nubia is having me send my phone back to them to check out.

Guys the unbrick tool is already in this forum: https://forum.xda-developers.com/t/unbrick-tool-edl-flash-switch-from-cn-to-eu.4284797/
Note if you are rooted before going to EDL mode (9008) you should backup EFS via QFIL QCOM tool as a few people lost their IMEIs - I think it's in EFS Explorer the tool is free just Google it. Then do an EFS backup and save where you can't lose it. Here's a guide just ignore the Lenovo part, but you must go into diag mode Qualcomm 901D which is (try dial code *#7678# first it worked on the Red Magic 5 series, probably puts you in diag mode still) otherwise: adb shell; su; setprop sys.usb.config diag,adb before QFIL will see it: https://forums.easy-firmware.com/showthread.php/29143-How-To-Restore-Backup-QCN-EFS-on-Qualcomm-devices-(Giuide)
You can also back up the partition if you are rooted via adb shell. From memory, enable dev options (click build # under system until it shows up), patch your boot.img with Magisk Manager (should be in the ROM zip file you downloaded, copy to phone), flash back to the phone with fastboot (it will be in Downloads/magisk_patched_xyz.img "xyz" changes names just depends on Magisk) command is just after reboot to fastboot: fastboot flash boot magisk_patched_xyz.img; reboot and you should be rooted. Then from ADB do an ADB shell (it will ask to trust the device connected) adb shell (on PC), su (will ask for root access, grant it), $ dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img and copy that to your PC. That's your persist partition in case it gets messed up you should be able to: $dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist that assumes you copied persist.img back to your /sdcard/ in internal memory.
If I messed up a step feel free to correct it, this is all from memory no PC in front of me on vacation...

mslezak said:
Guys the unbrick tool is already in this forum: https://forum.xda-developers.com/t/unbrick-tool-edl-flash-switch-from-cn-to-eu.4284797/
Note if you are rooted before going to EDL mode (9008) you should backup EFS via QFIL QCOM tool as a few people lost their IMEIs - I think it's in EFS Explorer the tool is free just Google it. Then do an EFS backup and save where you can't lose it. Here's a guide just ignore the Lenovo part, but you must go into diag mode Qualcomm 901D which is (try dial code *#7678# first it worked on the Red Magic 5 series, probably puts you in diag mode still) otherwise: adb shell; su; setprop sys.usb.config diag,adb before QFIL will see it: https://forums.easy-firmware.com/showthread.php/29143-How-To-Restore-Backup-QCN-EFS-on-Qualcomm-devices-(Giuide)
You can also back up the partition if you are rooted via adb shell. From memory, enable dev options (click build # under system until it shows up), patch your boot.img with Magisk Manager (should be in the ROM zip file you downloaded, copy to phone), flash back to the phone with fastboot (it will be in Downloads/magisk_patched_xyz.img "xyz" changes names just depends on Magisk) command is just after reboot to fastboot: fastboot flash boot magisk_patched_xyz.img; reboot and you should be rooted. Then from ADB do an ADB shell (it will ask to trust the device connected) adb shell (on PC), su (will ask for root access, grant it), $ dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img and copy that to your PC. That's your persist partition in case it gets messed up you should be able to: $dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist that assumes you copied persist.img back to your /sdcard/ in internal memory.
If I messed up a step feel free to correct it, this is all from memory no PC in front of me on vacation...
Click to expand...
Click to collapse
I locked the bootlooder the screen is black, the only way to connect to the device is on a PC "COM",
I tried this link but and the next steps but it doesn't work, I don't know what to do with the phone and still it doesn't work,
I think I need the firmware RED MAGIC 6 "NX669J_NON EU Common".
PLEASE HELP ME
https://mega.nz/file/ntBSxDKa#h9vUPGoWVyqtyDYWYmSgz8bE1_vNimBMAqTp9csvv-w
2) Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)
3) Open the MiTool application
4) in MiTool, select the folder images
5) Put your phone in EDL mode
6) Once connected, Click flash - the brushing process will start automatically.

Good evening I found a guy who unlocked the phone for me at 150 dollars.
the phone quickly repaired without any problems so the problem is solved.

Marofyxx said:
I locked the bootlooder the screen is black, the only way to connect to the device is on a PC "COM",
I tried this link but and the next steps but it doesn't work, I don't know what to do with the phone and still it doesn't work,
I think I need the firmware RED MAGIC 6 "NX669J_NON EU Common".
PLEASE HELP ME
https://mega.nz/file/ntBSxDKa#h9vUPGoWVyqtyDYWYmSgz8bE1_vNimBMAqTp9csvv-w
2) Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)
3) Open the MiTool application
4) in MiTool, select the folder images
5) Put your phone in EDL mode
6) Once connected, Click flash - the brushing process will start automatically.
Click to expand...
Click to collapse
i tried running it and now the phone is on but no display . who can help me ?
my device is :
Model: NX669J-P
Red magic OS :V4.5
Build number : NX669J_CNCommon_V7.14
Adroid version :11
Hardware version : NX669J_V1AM
I will pay for the software for you if I have to . Hope your help!

Hello,
I can give you the email of the person who repaired my phone but it's expensive 150dollar

manhdoan1601 said:
i tried running it and now the phone is on but no display . who can help me ?
my device is :
Model: NX669J-P
Red magic OS :V4.5
Build number : NX669J_CNCommon_V7.14
Adroid version :11
Hardware version : NX669J_V1AM
I will pay for the software for you if I have to . Hope your help!
Click to expand...
Click to collapse
Hello,
I can give you the email of the person who repaired my phone but it's expensive 150dollar

guide

Marofyxx said:
Hello,
I can give you the email of the person who repaired my phone but it's expensive 150dollar
Click to expand...
Click to collapse
i can pay it 150 usd . give me email

Ok

hey guys..
can u pls share qcn or especially xqcn for NX669J..?