Hi all, I think it would be possible to sim-unlock a Lumia rewriting all the partition ( 9 in all ) with the same from an unlocked Lumia ( possibly never unlocked .... ). With the dd linux command could be simple. What do you think ?
is there anyone that could post the whole 9 partitions from a Lumia 710 ?
Leoman said:
Hi all, I think it would be possible to sim-unlock a Lumia rewriting all the partition ( 9 in all ) with the same from an unlocked Lumia ( possibly never unlocked .... ). With the dd linux command could be simple. What do you think ?
is there anyone that could post the whole 9 partitions from a Lumia 710 ?
Click to expand...
Click to collapse
Hi Leoman, see this thread HERE.
Cheerz,
Done but with problems. I overwrited eight partitions except the fifth, that contains the telephone data as serial number and other stuffs ( but I didn't find in it the IMEI ). Befor turning on the phone I restored the firmware ( unlocked ) trying to totally restore all the partions that could retain data not coming from my firmware. The telephone boots fine and it no more calls for the unlock code but is says "no service". Apparently I stucked the radio software. Having the qualcomm bootloader I tried to restore the NOKIA DLOAD as described in this post
http://forum.xda-developers.com/showthread.php?t=1702815
to restore the original firmware but, surprise, NCS can't no more flashing the firmware. It says that there is a problem with OSBL. I tried with other firmware without no success. I tried with windows recovery phone tools but it says that cannot restore the telephone .... I read that at least another had the same problem restoring the nokia dload with the above procedure ...
Leoman said:
Done but with problems. I overwrited eight partitions except the fifth, that contains the telephone data as serial number and other stuffs ( but I didn't find in it the IMEI ). Befor turning on the phone I restored the firmware ( unlocked ) trying to totally restore all the partions that could retain data not coming from my firmware. The telephone boots fine and it no more calls for the unlock code but is says "no service". Apparently I stucked the radio software. Having the qualcomm bootloader I tried to restore the NOKIA DLOAD as described in this post
http://forum.xda-developers.com/showthread.php?t=1702815
to restore the original firmware but, surprise, NCS can't no more flashing the firmware. It says that there is a problem with OSBL. I tried with other firmware without no success. I tried with windows recovery phone tools but it says that cannot restore the telephone .... I read that at least another had the same problem restoring the nokia dload with the above procedure ...
Click to expand...
Click to collapse
You can use NSS 0.47 (or 0.48) to easily restore the Nokia Dload. Check here http://forum.xda-developers.com/showthread.php?t=1620629
Related
I had on the phone 1600.3013.8107.11502. Then I update to 1600.3015.8107.12070. I did it by the refurbish option in the NCS. One month later i wanted to flash on 1600.3030.8773.12120
When i plug phone, the computer detected it other than ever. I saw Qualcomm CDMA Technologies MSM and removable disk with question about formatting. I clicked cancel but NCS does not detect the phone. My computer couldn't install driver for Qualcomm CDMA Technologies MSM. I tried it on others computers but on all its the same, i can't flash this ****. I was looing for solution on others forums but no one can help with this.
Thx for answers.
You have the Qualcomm bootloader. NCS does not recognize this bootloader. I f you want NCS to recognize your device, you will need the NOKIA DLOAD bootloader. However, the Qualcomm is the unlocked one, so depending on your preferences, you can leave it on the Qualcomm. With the unlocked bootloader (which you have) you will only need an other flashing method. Those can be found on the forums here.
I tried to restore nokia dload bootloader with NSS Beta but this program says my phone dosn't have qualcomm loader...
Looking for phone...Done.
Device: RM-803-NOKIA Lumia 710
Battery status: 91%
Changing phone mode...Done.
Looking for NAND disk...Not found.
Are you sure you have development Qcom loader ?
i have amlmost same problem, but my phone is dead, when i turn it on it stays ond nokia screen
Shuyn18 said:
I tried to restore nokia dload bootloader with NSS Beta but this program says my phone dosn't have qualcomm loader...
Looking for phone...Done.
Device: RM-803-NOKIA Lumia 710
Battery status: 91%
Changing phone mode...Done.
Looking for NAND disk...Not found.
Are you sure you have development Qcom loader ?
Click to expand...
Click to collapse
Your cellphone is working?
I downloaded NSS but it doesn't detect my phone
And if i had the Qualcomm bootloader,How do i go in recovery?
just want to make a nand backup for a friend and root his stock phone.
I own a sgs+ with a custom rom of andoid so i'm noob at wp.
thx,
Shuyn18 said:
I tried to restore nokia dload bootloader with NSS Beta but this program says my phone dosn't have qualcomm loader...
Looking for phone...Done.
Device: RM-803-NOKIA Lumia 710
Battery status: 91%
Changing phone mode...Done.
Looking for NAND disk...Not found.
Are you sure you have development Qcom loader ?
Click to expand...
Click to collapse
If you have this error, please check if the phone restarts in this step or just
stays in Normal mode (windows screen). There are some software versions that
will not respond to the OSBL change command. So just try to flash different
version (via .nb file) and try again.
The other option is the manual restore(hex edit), but its really risky if you don't know
what are you doing.
The problem seems to be caused by version mismatch between the OS and the
baseband firmware. Here the solution and more info.
I also has a problem like: "Are you sure you have development Qcom loader"
when trying to flash rainbow mod FW by lucifer to my lumia 710 using NSS pro v0.48. Does anyone has a same problem with me? all steps that told in http://forum.xda-developers.com/showthread.php?t=1620629 i already been followed. but still i can't flash the FW mod, FYI I already succeed in installing FW with qualcom bootloader before using NSS pro.
Cheers
Hello ! I have a problem . It irritates me any photo software from LG and would like to upload CyanogenMod . The first thing I did was to install the drivers for fastboot according to this guide :
http://forum.xda-developers.com/showthread.php?t=2119090
But I think something went wrong because the point 14 something goes wrong and the phone will not restart and I do not know if everything went about Is it possible to make sure they do that? When instalwoałem drivers in device manager I did not have the device LG P2 , and most of the pictures / videos I see that the phone is in the name. I only had the OMAP 4430 .
Secondly, I installed rom v20b open eu . I waited 30 minutes and according to this guide http://forum.xda-developers.com/showthread.php?t=2221102 I wanted to unlock the bootloader . Unfortunately, only the phone restarts . I have a bootloader version LK MAY- 2012 but apparently it has nothing to matter.
Drivers have rather all installed so it's not the drivers fault . Can anyone had a similar problem with bootloader but somehow handled ?
P. S. Sorry for my english , but I used Google Translator
Hello,
A lot of people seems to have the same problem as you. It is not linked to the bootloader version (I also have the "LK MAY- 2012" version and my bootloader unlocking was a success).
According to this post, you need an active SIM card during the 30 minutes wait : https://plus.google.com/115049428938715274412/posts/CUu6YE3C6C2
Did you have an active SIM card when you tried it ?
There are references to "permanently locked bootloader" if something was done wrong : I hope for you it is not the case .
I hope too.
Yes, I was an active sim card for 30 minutes, if the word active, we understand that is inserted into the phone Do you think that doing this on Linux which is expected to make the difference? And you had any problems with unlocking or immediately did you do it?
Hello, i have a nokia lumia 920 with 8.1, build 8.10.12393.890, and i can't seem to find anything to install more than the 2 xap limit provided by the developer unlock.The chinese jailbreak tool doesn't seem to be active anymore and doesn't do anything, (i really wanted at least to be able to install 10 xap's).Interop unlock doesn't work anymore (too late).And every other method requires an sd card, which lumia 920 doesn't have.Isn't there any way to root, vcreg, or remove that 2 xap limit?i also wouldn't install windows 10, as i don't wanna risk bricking my device.
Edit : Apparently, there is something called Wpinternal, wich unlocks the bootloader and grants root acces to the phone, the problem is now, it says there that i need a .ffu file that must match the rom image installed on my phone, i have an at&t cyan version, and i can't seem to find it anywhere, also says there's some risk of bricking, really intimidating stuff there :'(
Even later edit : So i tried to flash something to unlock the bootloader with wpinternal but used a wrong ffu file and messed everything up and bricked my phone, windows device recovery showed fatal error, and nokia recovery tool showed unhandled exception.
After realising that i may have messed up the phone forever and started crying a little, i reflashed an original image with wpinternal, and succesfully unlocked the bootloader and rooted the phone with mass storage and registry acces
Hi all,
Wishing you all a happy New Year in arrears and the very best for the next 12 months.
I've got a problem with my device, its a STF-AL10 model with international rom bought during the November Sales.
It came with STF-L09C432B150 installed, I got the bootloader unlocked, TWRP installed and rooted with Magisk and was working fine except the capacitive buttons.
I thought I could live without capacitive buttons but I didn't work out and I had the urge to find a solution. After some intensive reseach (48hrs on a weekend in my 'lab') it seems the B120 firmware had no issues with the capacitive buttons, so I tried to downgrade to that and thats when the problems started.
Coming from an ancient Sony Z2, I never had issues flashing ROMS, Kernels and the sort as it was almost always easily done in TWRP or CWM (I had a Multi boot thing going, so I chose which recovery I fancied!). Anyway this are my issues now:
- Obviously, my phone was rebranded at origin as I know for sure AL-10 is not for EU market
- I tried restoring the same STF-L09C432B150 (rollback package found on XDA) with DC-Unlocker (wasted 19 Euro) but did not work. Always stops at 5% near end of flashing.
- Tried B130. same error.
- Tried Chinese STF-AL10C00B110. Same error.
- Tried full board flash for STF-AL10 with all DC Phoenix files. Same error.
- Tried forced method with files on a Sandisk SDcard (64GB) formatted to exFAT. Fails, wrong files.
- I noticed that in ADB, it said my bootloader was unlocked but FRP locked.
- After board flash, ADB said Bootloader unlocked (nothing about FRP) but in Muli-tool it says LOCKED.
- Now all ADB commands the write to the phone give errors.
DC-unlocker support keep on saying I should use the correct firmware for my phone, ok but the phone was rebranded at source...do use a Chinese firmware first then update ?
in desperation I did another full board flash but this time I think I wiped oeminfo and Vendor partions. ( I think this is what caused the HARD-BRICK!). Now no Honor logo, no Recovery, No eRecovery, nothing but a blank black screen. ADB still works but no status about bootloader or FRP.
IMEI has changed to 0123456789ABCDEF
You can all laugh and shake your heads which I will take as my punishment but is there a solution to all this, I'm willing to pay another 19 EUR for DC-Phoenix if it helps to fix my phone and if possible get it rooted with all buttons and functions working. That was my intension all along (I'm not really interested in custom Roms, just root access!).
HCU tool for some reason does not install on my computer, and besides, the phone does not boot into an OS to be able to change OEM and VENDOR data.
I even tried the HOTA.zip in the ReBRAND HONOR 9 thread but the file is missing (link down).
And to top it all there is no UK service center.
Please advise...
I think DC unlock is not supported for thì this model. Did Did you try Huawei Funky???
Apparently all versions of Honor 9 are supported by DC-unlocker and DC-Pheonix....
ums1405 said:
Hi all,
Wishing you all a happy New Year in arrears and the very best for the next 12 months.
I've got a problem with my device, its a STF-AL10 model with international rom bought during the November Sales.
It came with STF-L09C432B150 installed, I got the bootloader unlocked, TWRP installed and rooted with Magisk and was working fine except the capacitive buttons.
I thought I could live without capacitive buttons but I didn't work out and I had the urge to find a solution. After some intensive reseach (48hrs on a weekend in my 'lab') it seems the B120 firmware had no issues with the capacitive buttons, so I tried to downgrade to that and thats when the problems started.
Coming from an ancient Sony Z2, I never had issues flashing ROMS, Kernels and the sort as it was almost always easily done in TWRP or CWM (I had a Multi boot thing going, so I chose which recovery I fancied!). Anyway this are my issues now:
- Obviously, my phone was rebranded at origin as I know for sure AL-10 is not for EU market
- I tried restoring the same STF-L09C432B150 (rollback package found on XDA) with DC-Unlocker (wasted 19 Euro) but did not work. Always stops at 5% near end of flashing.
- Tried B130. same error.
- Tried Chinese STF-AL10C00B110. Same error.
- Tried full board flash for STF-AL10 with all DC Phoenix files. Same error.
- Tried forced method with files on a Sandisk SDcard (64GB) formatted to exFAT. Fails, wrong files.
- I noticed that in ADB, it said my bootloader was unlocked but FRP locked.
- After board flash, ADB said Bootloader unlocked (nothing about FRP) but in Muli-tool it says LOCKED.
- Now all ADB commands the write to the phone give errors.
DC-unlocker support keep on saying I should use the correct firmware for my phone, ok but the phone was rebranded at source...do use a Chinese firmware first then update ?
in desperation I did another full board flash but this time I think I wiped oeminfo and Vendor partions. ( I think this is what caused the HARD-BRICK!). Now no Honor logo, no Recovery, No eRecovery, nothing but a blank black screen. ADB still works but no status about bootloader or FRP.
IMEI has changed to 0123456789ABCDEF
You can all laugh and shake your heads which I will take as my punishment but is there a solution to all this, I'm willing to pay another 19 EUR for DC-Phoenix if it helps to fix my phone and if possible get it rooted with all buttons and functions working. That was my intension all along (I'm not really interested in custom Roms, just root access!).
HCU tool for some reason does not install on my computer, and besides, the phone does not boot into an OS to be able to change OEM and VENDOR data.
I even tried the HOTA.zip in the ReBRAND HONOR 9 thread but the file is missing (link down).
And to top it all there is no UK service center.
Please advise...
Click to expand...
Click to collapse
Try stock service B130 firmware:
https://forum.xda-developers.com/honor-9/how-to/stf-l09c432b130-capacitive-buttons-100-t3729106
Instead of step 4 do forced upload: VOLUME UP + VOLUME DOWN + POWER
Hi,
I've managed to re flash b150. In doing so I got back recovery and erecovery but when you reach that final stage of the process the phone stops at 5%. When I reboot to recovery, factory reset stops at 35%
Any ideas
?
Sent from my [device_name] using XDA-Developers Legacy app
ADB now showing BOOTLOAD UNLOCKED but there is no FRP status.
Sent from my [device_name] using XDA-Developers Legacy app
ums1405 said:
ADB now showing BOOTLOAD UNLOCKED but there is no FRP status.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
FRP status is not only on Chinese phones
you need to sew firmware for al10
The phone was rebounded by the shop I bought it from.
It said STF-L09B150 indexical info when the phone was working.
So if I'm going to repair this brick what update files should I use?
Original Chinese or the b150 used when rebranded?
Sent from my [device_name] using XDA-Developers Legacy app
Hi all,
FYI, I've sent the phone back to the shop I bought it from.
I'll take my chances, better than paying money for something that may not work.
Thanks everyone for showing interest in my situation, I let you all know how I get along with this issue.
Ps.: As a community, lets push Huawei/Honor to release Kernel Sources for this model and others like the P10 Plus.
Ps: Huawei/Honor have to realise that a strong developer community adds value and desirability to a product. That's how a product becomes 'Cool' translating into more revenue/customers/profit - eg OnePlus.
.
Hi all, a quick update .....
Sent the phone back and from what I gather the phone actually had an issue with the main board.
Now enjoying a brand new MATE 10 (Non-pro with 6/128gb) in beautiful Obsidian black.
Wonderful.
Back in december/january some users reported a glitch while rebranding STF-AL10 to STF-L09 with the old nougat hwota (at oem bin flashing step).
After editing hwota script, then rebranded : they ended with a FRP locked status.
Their only way to unlock frp was with dcunlocker or funkyhuawei I don't remember.
After frp unlocked, their bootloader wasn't seen through fastboot.
I think this could be solved by regedit a value in registry.
To my knowledge the only public firmware files working with the dload way (3 buttons + usb connected) are the one titled "service repair", the others one won't work dload as they are. They are for hwota or forcing "official" ota.
So basicaly I was being lazy and in a rush. I had done something like this before on much older phone(s) with no issues...
I backed up my working LG G5 in TWRP all partitions. I brought exactly the same model for my wife and wanted to restore my backup to that phone (I have made many customisations on my rom and didnt want to have to manually do it all again for her)
However after unlocking the bootloader, flashing TWRP and installing new base rom (all went fine) I then went to restore my old backup onto this new phone, stupidly I ticked all partitions to restore. I have a feeling that I should have only done the larger partitions. Once I rebooted I got the "cant be trusted" message, I reflashed in UPPERCUT but then the phone booted and then had secureboot enabled. I hit the wrong password (as there was none) 30 times which then forced a format. Now the phone boots fine and works 100% BUT...BUT....
I now can no longer unlock the bootloader as I think its trying to use MY phones bootloader (as its unlock.img says its the wrong one, I have tried both MY phones original unlock.img and my wifes new phones unlock.img but both dont work) I cannot relock the bootloader as it says its already locked... this also now means that through LG official software I cannot recover the phone. Only UPPERCUT can see the phone. I can get to download mode and fastboot.
Also the phones IMEI now says 0, this worried me however her SIM card is working 100% fine (I guess that the IMEI
is cached somewhere, but im worried that if I use some cleaning tools it may scrub it and then she will have no network access)
So basicaly if her phone starts to play up (or I want to upgrade it to Oreo / Lineage at a later date) can anyone offer me advice on how to...
A: Fix / Restore the bootloader (I dont mean recovery) Im confused as to if this is stored on a chip or can be reflashed from the kdz firmware images.
B: Resore the IMEI (I have it written down) incase we get any network issues in the future. Can it be resored or regenerated without some fancy hardware, ie only through software.
C: I dont have Root or TWRP access it seems, any way of Getting Magisk or Super SU on a phone without bootloader unlock, root access or TWRP?
I have had many years experience and never bricked a phone but almost did this time.
I decided to post a solution here, because it was one of the first Google results when I was looking for some help.
Long story short, I did exactly same mistake of restoring all partitions, including the EFS, between two same LG devices. Turns out it messes with IMEI, which is a big no no and phone locks. Now you can't unlock the device again, because there is no IMEI to use in unlocking. Also no flashing or erasing anymore, because it just fails.
So the IMEI needs to be restored first.
My phone was in a bootloop constantly showing the "cant be trusted" message, but I managed to fix that using LGUP. Apparently not all partitions are locked, because trying to flash the same system with LGUP fixed the bootloop, but failed to flash clean system and the data that TWRP flashed was still there. Trying to restore system to factory settings also fails, but it doesn't matter.
Fortunately I was able boot the system, which made fixing it easier than you'd expect:
1. Fixing the IMEI from booted system (no root or unlocking needed):
- Access the hidden menu on your device by dialing a proper number. For LG G5 H850 it is *#546368#*#850#
Where 850 in the last part is your phone model. The number will vary for different models.
- Go to SVC Menu -> CRCWIZARD Test
- Switch tab to Auto MID
- Here you can enter your new IMEI and WiFi and BT MAC addresses, or you can just generate it.
You can also use the generate option for all values and then manually change only the IMEI for the original one.
- Press MID Write button and reboot your device.
- That's it. IMEI issue should be fixed now.
2. Now that you restored your original IMEI, you can again unlock your device using the same unlock.bin file that you used to unlock bootloader the first time.
Voila. From now on the device is again unlocked and you can just go back to flashing whatever you need.