Related
I tried editing my reg. for a while and could not get anything to work, then came across this:
http://forum.xda-developers.com/showthread.php?t=907169
and followed his instructions
the result is this .xap file which changes your reg to allow max number of unsigned apps..
deploy it to your device,
press the green button,
after done uninstall the xap on your device
restart just to be sure..
hope this helps someone .... or even makes the process easier ..
thanks to xboxmod for the instructions on how to do this...
thanks for your time and sorry if I am not supposed to post this--advise me if so..
When the phone connects to Zune doesn't it go back to 10 or 3...? Thank you
I actually don't know, but for me I have not had to re install / re-apply it or anything like that...
I have a dev unlocked HD7 btw (& updated to the latest updates)
Here is a MUCH easier way:
http://forum.xda-developers.com/showthread.php?t=916098
Also, search for a tool: Advanced Config. It is in there too.
If you reconnect to ZUNE, it will bring it back to 3 or 10. But running the hack after you've connected to zune allows more on once again.
the above method did NOT work on my Sprint HTC Arrive. The linked method and Advanced Config in this message DID work.
Good luck!
CopyCounsler said:
Here is a MUCH easier way:
http://forum.xda-developers.com/showthread.php?t=916098
Also, search for a tool: Advanced Config. It is in there too.
If you reconnect to ZUNE, it will bring it back to 3 or 10. But running the hack after you've connected to zune allows more on once again.
the above method did NOT work on my Sprint HTC Arrive. The linked method and Advanced Config in this message DID work.
Good luck!
Click to expand...
Click to collapse
Advanced Config did not work for me, sorry and that is why I had to resort to this method... I had not had any problems with it being set back to 3 (from what I can tell) because I can still install xaps just fine without having to run anything again.....
I have a German rooted P880, but the bootloader is locked. I remember there was a link to check if the firmware is unlockable, but I can't find it anymore. It was a search in an online database. AFAIR it was a hidden note.
I have read http://forum.xda-developers.com/showthread.php?t=2224020 and can't find it there. Also I read http://forum.xda-developers.com/showthread.php?t=2147879 . There have been written so many things since the last months, so I am interested if there is something new.
I have found the link now at http://forum.xda-developers.com/showpost.php?p=38898981
I have a German ADEUWH but I still don't know what a 234 device is. Any help or link where to go on with reading is appreciated.
lg-optimus said:
I have found the link now at http://forum.xda-developers.com/showpost.php?p=38898981
I have a German ADEUWH but I still don't know what a 234 device is. Any help or link where to go on with reading is appreciated.
Click to expand...
Click to collapse
This thread shows whats that 234.
unlocking method if not 234 is here
.
and those links i didnt even search to find them. in help it sais frequenty asked questions..... everything is in there.
kessaras said:
This thread shows whats that 234.
unlocking method if not 234 is here
.
and those links i didnt even search to find them. in help it sais frequenty asked questions..... everything is in there.
Click to expand...
Click to collapse
Yes, I know these threads, but I do not know if I have a 234. How do I find out this? Thanks!
lg-optimus said:
Yes, I know these threads, but I do not know if I have a 234. How do I find out this? Thanks!
Click to expand...
Click to collapse
AT THAT LINK , THREAD No6. pffffffffffffffffffffffff
You told me to read http://forum.xda-developers.com/showpost.php?p=38934517&postcount=6 right? Here is explained how to change the IMEI-Nr. of another phone. Hmmh, I don't know if it is a good idea to use a faked IMEI for unlocking the bootloader.
Maybe I found, what I didn't understand. I have to check the Software-version in the phone-menu and it says P88020a-262-000. So I do not have a 234 phone. It is so easy, if you know it.
any and all Jellybean versions of our phone can have their bootloader unlocked. you haven't been on the forum for few months, so at first only eur-xxx versions were unlockable, but then the method to unlock ALL other versions appeared by editing fuse. search for more info please
edit:
do NOT change your IMEI. there is no need.
Flying_Bear said:
any and all Jellybean versions of our phone can have their bootloader unlocked. you haven't been on the forum for few months, so at first only eur-xxx versions were unlockable, but then the method to unlock ALL other versions appeared by editing fuse. search for more info please
edit:
do NOT change your IMEI. there is no need.
Click to expand...
Click to collapse
Thanks for the info.
[TUT] Unlocking 262 000 ADEUBK and all other
http://forum.xda-developers.com/showthread.php?p=40611776
Just issuing echo 40000000c8 > /sys/firmware/fuse/odm_reserved as root and doing a reboot unlocked my Bootloader
So I hope my phone (ADEUWH, P88020a-262-000) is other
SInce I use Linux, I would like to know, if I could build a ssh-connection to my rooted phone and execute in a shell on the phone "echo 40000000c8 > /sys/firmware/fuse/odm_reserved". Looks very easy. Should I ask this in http://forum.xda-developers.com/showthread.php?p=40611776 ?
But what I am unsure, if it is possible to relock the bootloader again in case of warranty. http://forum.xda-developers.com/showthread.php?t=2229566 speaks only of maybe it could work.
lg-optimus said:
Thanks for the info.
[TUT] Unlocking 262 000 ADEUBK and all other
http://forum.xda-developers.com/showthread.php?p=40611776
Just issuing echo 40000000c8 > /sys/firmware/fuse/odm_reserved as root and doing a reboot unlocked my Bootloader
So I hope my phone (ADEUWH, P88020a-262-000) is other
SInce I use Linux, I would like to know, if I could build a ssh-connection to my rooted phone and execute in a shell on the phone "echo 40000000c8 > /sys/firmware/fuse/odm_reserved". Looks very easy. Should I ask this in http://forum.xda-developers.com/showthread.php?p=40611776 ?
But what I am unsure, if it is possible to relock the bootloader again in case of warranty. http://forum.xda-developers.com/showthread.php?t=2229566 speaks only of maybe it could work.
Click to expand...
Click to collapse
If you are prepared to unlock your phone then you have to assume that you cannot relock it - because even if you do, LG can see what you have done.
If something goes wrong in the warranty period, such as the screen dying, they should repair it (but may not).
Simply, if you are worried about your warranty then leave you phone alone.
it's possible to relock it i think, but as SimonTS said, they can easily check (by checking fuse file)
and yeah, on linux it should be as easy as echoing the right value into the file. if that doesnt work, try copying the file into temporary folder, echo proper value in that file, then replace the original file with the temp file. good luck!
I am very unsure if I should unlock at the moment, because I noticed some strange things which could be a hardware or a software error. One problem is, that the screen stays black if I call one and he doesn't answer, looks like it is a sensor problem, but sometimes it works, espcecially after a restart. The 2nd problem is a character problem with music-metadata. The mad thing is, that some Arabic, Greek, a.s.o characters are displayed correctly, while others are not. The same files are correct with other android phones. I think it is LG related.
lg-optimus said:
I am very unsure if I should unlock at the moment, because I noticed some strange things which could be a hardware or a software error. One problem is, that the screen stays black if I call one and he doesn't answer, looks like it is a sensor problem, but sometimes it works, espcecially after a restart. The 2nd problem is a character problem with music-metadata. The mad thing is, that some Arabic, Greek, a.s.o characters are displayed correctly, while others are not. The same files are correct with other android phones. I think it is LG related.
Click to expand...
Click to collapse
about sensor issue, you can fix it by recalibrating your proximity sensor via hidden menu (also, i dont have this problem on most custom roms i used).
dont really know about the issue with characters, so cant give you any advice
Thank you for pointing me to http://forum.xda-developers.com/showpost.php?p=34669449&postcount=8
I fear the character problem with mp3-metadata is a very special one. One could be, that UTF-8 is generally used, which is wrong with ID3v2.3, because this supports UTF-16 only. But if mp3s are coded with UTF-8 and v2.4 the problem remains. I do not know any other Android-Phone or Bada-phone (Samsung) which has problems with such files, only the P880 does. The strange thing is too, that the default music-player has this problem, as well as PlayerPro, but RocketPlayer shows the characters correctly.
Hei guys can somebody help me?I'm using the guide to interop unlock samsung ativ s but when i click toast notification i remain with this.(see on photos)
And i can't acces registry editor.How can i acces registry?
The phone is dev unlocked with official GDR3.
Try this
I'm gonna give this a try but how can I acces phone/data?Its seems to not appear on computer.
*Sigh*
Reading. You should try it sometime, before trying to run hacks you don't understand.
Tell me: What does the second line (you know the one with bold text tell you you're doing wrong?
@sp4rt4n-i17: The problem isn't that his RPC is blocked (although it is), it's that Samsung removed the registry editor from the version of Diagnosis built into their latest firmware. I'm pretty sure that if Diag has been installed *prior* to the update it would work, but it seems that this is not the case here.
You need to either downgrade, or install one of the "custom ROMs" that just make the relevant changes. Check the Dev&Hacking sub-forum.
Hi, i'm new at this forum and i found a thread to tweak the registry (2486387)
I wants to set the security limit on 'never' on mine Samnsun Ativ-S.
Can anyone explain to me, the steps i have to do, to get this done?(please step by step)
I included a print screen of the phone-settings.
Thanks for your help.
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
BlackStorm94 said:
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
Click to expand...
Click to collapse
Same thing happened to me after I unbricked my device using the exact same tutorial. However, even with IMEI 0 I can still make and receive calls and text messages. But I'm not sure if I should leave my device like this. If someone has any solution to provide I would be very grateful! I hope it doesn't involve flashing any ROM again cause I'm really afraid that I may brick my phone again ...
Hey guys, I had exactly the same problem. I tried different things including flashing various Roms and Bootstack, but nothing seemed to work. Since I’ve been searching for a solution quite a while, I now have the honor to help you out and everyone with an L90, who stumbles upon the same issue.
First of all, I made a backup of my EFS, so that I could restore the state my phone was in (IMEI=0, but working baseband). You can do that easily with TWRP (thx to shoxxy . By the way, this is something which we all should have done beforehand. It would have been much easier to restore our IMEIs.
But don’t worry, if you follow the instructions in this video (https://www.youtube.com/watch?v=nwzgs1Cmr9k) you should be able to get your IMEI working again. For those, who feel more comfortable following written instructions I copied the following procedure using this thread (http://forum.xda-developers.com/showthread.php?t=1960918) as a model and edited them a little to the way it just worked for me.
Do this on your own responsibility! And better double-check with the video our other threads.
Before you start:
Download this package (http://www.mediafire.com/download/figdbxb75j5kyry/package.rar), it belongs to the user who made the video on youtube (PremiumRepair).
Make sure your phone is rooted and USB-Debugging is enabled (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Procedure :
Install Drivers. Either you use LG Support Tool or download them directly. For me the LGUnitedMobileDriver+3.14.1_ML_WHQL.exe worked just fine. Don’t forget to uninstall old drivers or you could run into problems.
Install QPST v2.7.378. Microsoft Visual C++ 2005 Redistributable is a prerequisite, just confirm it.
Plug your device into your PC (USB port)
Run QPST Configuration from your Windows Start menu. Switch to the second tab ("Ports") and choose "Add new port" (bottom left button). You should see a COM port associated with "USB/QD Diagnostic". Select it, then press Ok. You can close the QPST Configuration window now.
Open Windows Explorer and browse to "C:\Program Files\Qualcomm\QPST\bin" (or wherever you installed QPST) and launch RF_NV_Manager.exe. In RF NV Manager, Go to "Settings / Comport". You should see your COM port in the dropdown box. Select it, then press OK.
Go to "File" and choose "Read from phone". RF NV Manager will read all NV items from the phone. Now if you see item #550, you will be able to alter it (see below). If you can’t find it, go to “File” and choose “Read supported RF NV Items”. If you still can't find it, there is a way to create it. Take a look at the thread I linked to.
Now comes the critical step of altering the IMEI. Select item #550 and you'll see 9 boxes on the right, a "Write NV" button and an "Hex" checkbox. Check the "Hex" checkbox.
Now, you'll have to enter the IMEI in the 9 boxes in a very specific way. The easiest way is to use the IMEI converter (for other method see linked thread). Put your IMEI in, convert it and put the digits in the boxes (two number per box).
Now you can then press "Write NV" to write the IMEI value to your phone.
Once done, unplug the device, and reboot it. Now you IMEI should be changed. If it’s not your number, take a look at the step seven again and check the video.
Please give a feedback, if it worked for you (incl. Details about your device, ROM, etc.) so that other users can profit from it. Thanks
Edit: @ BlackStorm94 - Don't worry about the warning. It will vanish if you install a different ROM.
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Lazgeor said:
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Click to expand...
Click to collapse
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
mhikel said:
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Click to expand...
Click to collapse
So, I rooted the phone successfully, but the phone is still not recognized by QPST Configuration or RF NV Manager. My pc recognizes the phone and I can do everything properly, but these programs say that there is No Phone ... I don't know what to do ...
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
mhikel said:
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
Click to expand...
Click to collapse
I'm going to try on a new computer tomorrow afternoon and I'll let you know how it went. I uninstalled all drivers associated with my phone on my computer and after reinstalling them I still got no results. I guess I may have confused it So that's why I'll try on a new one. Thanks for your help
Hello, sorry for the late reply. I just wanted you to know that even though I tried with another computer, my phone was still not recognizable. It doesn't really matter tho, cause even with the IMEI 0 I still have service and it works normaly for about a month now. If you have any solution then I would like to try it, but if not then it's okay. Thanks for your time
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
[/COLOR]
mhikel said:
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Click to expand...
Click to collapse
Yeah yeah, I had USB Debugging enabled every time I plugged my phone into both of my PCs. But I don't think that's the reason this tutorial isn't working on my phone. When I unbricked the device, I had to use the L90 D405 loader.img in order to reflash the bootloader and recovery. But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n. I hope you understood this cause I know it's a bit weird I see options to activate NFC but I never use it so I can't tell you if it works. However I can activate it properly. Anyway, about the IMEI, as I told you, it basically works without problems even with 0 because I think that my service provider doesn't block anybody except someone reports the device as stolen. If you have any further solutions then let me know but if not the don't worry, I'm okay!
Lazgeor said:
But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n.
Click to expand...
Click to collapse
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
mhikel said:
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
Click to expand...
Click to collapse
It's okay I don't want to bother you any further. I'll buy a new phone soon anyways and since I'll give this one to my small brother, I don't think he'll really worry if his IMEI is 0 If at some point this device gets blocked by a service provider then I'll start searching for ways to fix it again. That bootstack page you mentioned seems useful. I'll try that if I do have any problems. Thank you very much for your help
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
mhikel said:
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
Click to expand...
Click to collapse
Update: I actually fixed it I know I told you that I would leave it as it is for now, but today I had nothing to do, so I decided to try my best and fix it. What I did was, as the post you told me said, I had to install the Kit Kat bootstack and the easiest way to do that is by flashing the Kit Kat rom. So I downgraded to android 4.4.2 using the stock rom I found on another post, and then I used your tutorial on the Kit Kat version. This time I was able to pass step 6 because my phone was getting recognized properly. I also didn't needed root access after all, since the new rom was just installed and it worked. After finishing the tutorial and restarting the phone, my IMEI was back! Then I upgrated my phone to the lollipop version, and when the upgrade finished, my IMEI was still there. So now I'm in lollipop with a working IMEI. I'm so thankful to you now, thank you very much for helping me and providing me these useful tutorials. I really appreciate it
Wow, that's just great!=) congratulations, you can be proud! Happy for you, that was quite an issue. You are welcome=) Well, someone from this forum helped me out, when I seeked for help and I am happy to give something back. Thank you for sharing your solution! That should be helpful for the next one stumbling over this problem. Enjoy your completely restored phone!=)