Hi colleagues, I am looking for a copy to restore the partition for the LVM600TM30a model it is possible that the software will see the imei number, which is now invisible will you help me ?
someone will help me with this partition copy for my model
I just joined this community out of curiosity. I was a technical guy working for LG for over 8 years in mobile computing.
Having given my background info, let me say this that what you are seeking to restore (the IMEI plus network bands) is extremely difficult. First of all, nobody is going to give your phone the duplicate identity of their device. Period! Second, your phone is permanently locked with no operating bands. Reading through your earlier messages in this forum here is where you stand: You should buy a new phone. This one is done with! By wiping out all the partitions, you practically killed the device. If you were able to get into download mode then you could have gotten the partitions back BUT not the heart of the phone i.e., IMEI and operating bands.
Other users in this forum have already advised you the dead-end you have hit.
You will be surprised how many times I have seen some user trying to be curious and destroying their phones in the process. Your phone, for example, was working fine and then you tried to flash an unrelated firmware on it. I wonder what was the reason for doing that. Even if you were able to flash the intended firmware, it was going to give you problems because the operating frequencies would not be there.
The only option that you have is to try the MTK engineering mode app to regenerate the IMEI and operating bands. It is not guaranteed to resolve your issue but is the only option you got.
Good luck!
Since you worked in Lg, maybe you will know if sending the imei to the Lg service to repair the imei number makes sense?
LG will not honor the service you are requesting. Here is why:
1. You have unlocked the bootloader and rooted the device.
2. By deleting the partitions, you have lost the device IMEI and operational bands. That is intended misuse.
Neither of these factors are suggested by LG. So your warranty is out of the picture as well as any factory services you may seek.
I don't want the LG company to repair my phone under warranty because the warranty has expired. I just want to repair my software, of course I will be charged for this service
You are mistaking what he is clearly telling you. LG has NOTHING TO DO WITH YOUR PHONE. You have voided the usage conditions by manipulating the hardware.
Speaking for a lot of forum members, you need to put your situation to rest! You screwed up your phone permanently. Deal with it!
I contacted the LG service on the chat, I have to contact the service and send them a phone in to software repair, which I will also do on Monday
Just deal with your problems yourself, man! You have saturated this board to the hilt.
thieftime1980 said:
Hi colleagues, I am looking for a copy to restore the partition for the LVM600TM30a model it is possible that the software will see the imei number, which is now invisible will you help me ?
Click to expand...
Click to collapse
Is it a TMobile model? If yes there is a good chance it's possible to fix the IMEI.
I love how the other guy here trying to tell you to fix the IMEI with a mediatek engineering app lol
yes this is the t-mobile model I sent it to the Lg service yesterday I hope the LG service is able to fix it
>>I love how the other guy here trying to tell you to fix the IMEI with a mediatek engineering app<<
Instead of flaming a guy who is trying to give insight, it will be much better if you could provide info regarding how to recover IMEI from a deleted partition. Talking in vague terms does not help anyone including OP.
Leronex_1 said:
Is it a TMobile model? If yes there is a good chance it's possible to fix the IMEI.
I love how the other guy here trying to tell you to fix the IMEI with a mediatek engineering app lol
Click to expand...
Click to collapse
I have myself recovered phones' IMEI as well as operating bands using the MTK app. The problem is there are so many fake MTK engineering apps circulating. You sarcasm is amusing. Obviously you are not so well aware of mobile computing. Quite frankly, I challenge you to show us your way of recovering an IMEI/bands for a phone whose entire credentials have been wiped out. Enough said!
Commander_Bond said:
I have myself recovered phones' IMEI as well as operating bands using the MTK app. The problem is there are so many fake MTK engineering apps circulating. You sarcasm is amusing. Obviously you are not so well aware of mobile computing. Quite frankly, I challenge you to show us your way of recovering an IMEI/bands for a phone whose entire credentials have been wiped out. Enough said!
Click to expand...
Click to collapse
Dude I mean, come on you can do better than that. It says MTK=Mediatek and v60 is not Mediatek kekw But apparently you are a "technical guy" who "worked" with LG although for some reason you don't know what mtk actually stands for and for what CPU manufacturers this term is used lol.
Again if it is a TMobile device there is a good chance to recover the IMEI, dm me if you are interested.
That’s the irony. Even if it is originally designed for Mediatek, it DOES work for some other non-Mediatek phones. Just to open your eyes, check out some videos on YouTube! If you read earlier post, he had said that there is no guarantee that it will work for the OP’s V60. It works like a charm on LG K51, Q series.
BTW, I am still waiting to see your IMEI recovery procedure for a deleted partition! Back your claim and let us be the judge.
Royaltiger said:
That’s the irony. Even if it is originally designed for Mediatek, it DOES work for some other non-Mediatek phones. Just to open your eyes, check out some videos on YouTube! If you read earlier post, he had said that there is no guarantee that it will work for the OP’s V60. It works like a charm on LG K51, Q series.
BTW, I am still waiting to see your IMEI recovery procedure for a deleted partition! Back your claim and let us be the judge.
Click to expand...
Click to collapse
Guys you're all tripping, wtf. K51 is helio p22.
As to the imei recovery, flash the experimental tmobile image, flash 08s4 v600n efs partitions, change imei in hidden menu, reflash tmobile firmware and done.
Please elaborate on your suggested process. Where do you get the "experimental" image for V60 T-Mobile? I am assuming that you are suggesting to flash the efs partition in the download mode using LGUP partition mode?
Audio_Lover said:
Please elaborate on your suggested process. Where do you get the "experimental" image for V60 T-Mobile? I am assuming that you are suggesting to flash the efs partition in the download mode using LGUP partition mode?
Click to expand...
Click to collapse
I can only flash it with medusa, i told in my previous message to DM me if anyone is interested.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its a srf file so only flashable with my medusa box
The problem with your solution is that it is available only to you (or with individuals who have Medusa). The restricted access does not make it a viable option.
Commander_Bond said:
LG will not honor the service you are requesting. Here is why:
1. You have unlocked the bootloader and rooted the device.
2. By deleting the partitions, you have lost the device IMEI and operational bands. That is intended misuse.
Neither of these factors are suggested by LG. So your warranty is out of the picture as well as any factory services you may seek.
Click to expand...
Click to collapse
This is total bs! I know for fact that the LG service center in Ft Worth, TX will work on anything for money. Locked BL, unlocked BL, cross flashed, it doesn't matter! If you can tell 'em what your imei was or what you think it was they will slap it on a machine, reload the software to the lastest spec (I think it takes them all of 10 minutes) be it AT&T, Tmob, Verizon, whatever. Don't tell me they won't because I had to send'm a lmv600at model that I screwed up! That's the reason I learned how to use Bkerler EDL utility and created these posts so I along with a lot of other people here wouldn't have to pay LG $42 plus shipping for a software reload.
LMV600AM Restore/Ugrade Guide
This restore process is intended for the AT&T V60 (lmv600am) model and will WIPE your data so back it up if you want to keep it! This process will restore the lmv600am to original factory state for the AT&T v60 v20q build (a11). I’ve dumped all...
forum.xda-developers.com
LMV600TM Restore/Ugrade Guide a12
This restore process is intended for the Tmob V60 (lmv600tm) model and you must WIPE your data so back it up if you want to keep it! This process will restore the lmv600tm to the state directly after the ota upgrade to the a12 v30b build. I’ve...
forum.xda-developers.com
All that being said, anyone who erases their imei info deserves what they get. I know!
Related
I bought a used Lumia 800 last night. The OS version on it is "8107.WM7_Main_ship(mojobld).20111207-2014"
I can't seem to find much info on it, but from what I gather, this is a developer model? Can this phone be updated to the latest OS version? My phone tells me it's already on the latest OS but this can't be true!
Other info:
Firmware: 1600.2473.7720.11400
Hardware revision: 112.1402.2.2
Radio software: 1.6.00.24
Radio hardware: 8255
Bootloader: 7.35.0.0
The OS on the retail Lumias is easily interchangable. You can flash a chinese carrier tango variant on a french or whataver handset and it should work just fine. And then you can flash back to an old mango rom.
Well at least as long as you have hw: 112.1402.2.4 like me. Yours seems to come from an older batch.
(Zune will almost always tell you that you are up to date, don't mind it).
Please take out your sim tray and check your phone's product code. It should be something like for example 059N064.
Skrypek said:
The OS on the retail Lumias is easily interchangable. You can flash a chinese carrier tango variant on a french or whataver handset and it should work just fine. And then you can flash back to an old mango rom.
Well at least as long as you have hw: 112.1402.2.4 like me. Yours seems to come from an older batch.
(Zune will almost always tell you that you are up to date, don't mind it).
Please take out your sim tray and check your phone's product code. It should be something like for example 059N064.
Click to expand...
Click to collapse
The product code is 059L8X9 (Type RM-801). Does it matter that my hardware revision is the older one (112.1402.2.2)? Can I still flash other versions of Tango on it?
I ran NCS and it couldn't find my product code or any software updates. I couldn't refurbish it.
Edit: Apparently Zune DID find an update for my phone :S...updating it now! I just got home from work so I haven't got a chance to use Zune until now. Lets see what this does...
Edit2: The update failed . I got an error code 80180048. I really want to update this thing cause the battery drain on it is nuts! Plus, I can't live with knowing there's an updated OS out there that my device should have but can't...any thoughts on updating?
Chynkinese said:
The product code is 059L8X9 (Type RM-801). Does it matter that my hardware revision is the older one (112.1402.2.2)? Can I still flash other versions of Tango on it?
I ran NCS and it couldn't find my product code or any software updates. I couldn't refurbish it.
Click to expand...
Click to collapse
NCS will only look for updates for you product code, just like Zune.
The trick is to force a refurbish with a different variant ROM.
What I would try to do is:
- download the 1750.805.8773.1220 "Nokia 800 RM-801 Everything Everywhere UK GB Matt Black GV (059Q201)" ROM using NaviFirm
- Put the downloaded files in "C:\ProgramData\Nokia\Packages\Products\RM-801"
- replace 059Q201 with 059L8X9 in names of the three files that contain the PC
- Start NCS and put it in offline mode
- Connect your phone and click refurbish.
(If you installed NCS correctly, it should detect your phone and show its basic info. The phone has to be plugged in after starting NCS)
Now while this went perfectly smooth on my 059N1R with 112.1402.2.4 hardware, I can't guarantee it will work fine on your phone. I suspect it may work, but Nokia doesn't suport it simply because they didn't bother to test the new firmware with older hardware.
Skrypek said:
NCS will only look for updates for you product code, just like Zune.
The trick is to force a refurbish with a different variant ROM.
What I would try to do is:
- download the "Nokia 800 RM-801 Everything Everywhere UK GB Matt Black GV (059Q201)" ROM using NaviFirm or Data Package Manager
- Put the downloaded files in "C:\ProgramData\Nokia\Packages\Products\RM-801"
- replace 059Q201 with 059L8X9 in names of the three files that contain the PC
- Start NCS and put it in offline mode
- Connect your phone and refurbish.
Now while this went perfectly smooth on my 059N1R with 112.1402.2.4 hardware, I can't guarantee it will work fine on your phone. I suspect it may work, but Nokia doesn't suport it simply because they didn't bother to test the new firmware with older hardware.
Click to expand...
Click to collapse
Is the phone easily recoverable if things don't go smoothly? I made a backup using the WP7 Easy Backup Tool...but I'm still too scared to update the phone with anything haha...
I tried following the instructions for the Windows Support Tool (http://support.microsoft.com/kb/2530409) but upon holding the camera button I'm taken to a "SEARAY System Load Menu" instead of the screen with the picture of the phone and computer. The menu is loaded with some pretty scary looking options lol.
Chynkinese said:
Is the phone easily recoverable if things don't go smoothly? I made a backup using the WP7 Easy Backup Tool...but I'm still too scared to update the phone with anything haha...
I tried following the instructions for the Windows Support Tool (http://support.microsoft.com/kb/2530409) but upon holding the camera button I'm taken to a "SEARAY System Load Menu" instead of the screen with the picture of the phone and computer. The menu is loaded with some pretty scary looking options lol.
Click to expand...
Click to collapse
The word on the street is that dead Lumia phones are easy to resurrect using the Recovery option in NCS.
But a "SeaRay options menu"? Seem you've got yourself some pretty old device there, sir.
I guess it's one of those with the older Qualcomm bootloaders, which let you use custom ROMs. If you flash with newer official ROM using NCS it will not break your phone but only upgrade the bootloader to the newer locked Nokia DLOAD version.
Skrypek said:
The word on the street is that dead Lumia phones are easy to resurrect using the Recovery option in NCS.
But a "SeaRay options menu"? Seem you've got yourself some pretty old device there, sir.
I guess it's one of those with the older Qualcomm bootloaders, which let you use custom ROMs. If you flash with newer official ROM using NCS it will not break your phone but only upgrade the bootloader to the newer locked Nokia DLOAD version.
Click to expand...
Click to collapse
Hmm...in that case, maybe I should hold off on upgrading until a custom Tango ROM gets made?
Chynkinese said:
Hmm...in that case, maybe I should hold off on upgrading until a custom Tango ROM gets made?
Click to expand...
Click to collapse
In my opinion going with the official software would be safer.
Anyways, I like the look of the Everything Everywhere Tango ROM. It supports a helllot of display languages, internet sharing is unlocked, doesn't have any carrier bs installed, the only Nokia apps preinstalled are Drive, Maps and Contact Transfer, and among them only Drive is pinned to the start screen by default, the rest is just pure WP 7.5.
Skrypek said:
In my opinion going with the official software would be safer.
Anyways, I like the look of the Everything Everywhere Tango ROM. It supports a helllot of display languages, internet sharing is unlocked, doesn't have any carrier bs installed, the only Nokia apps preinstalled are Drive, Maps and Contact Transfer, and among them only Drive is pinned to the start screen by default, the rest is just pure WP 7.5.
Click to expand...
Click to collapse
I think I'll follow your advice and go with the official software. I feel like I've had my fill of custom ROMs with my last 3 Android devices.
Before I attempt this though, what is this I hear about "cabs"? Is that just a packaged and ready to go version of what is out on NaviFirm+?
Chynkinese said:
I think I'll follow your advice and go with the official software. I feel like I've had my fill of custom ROMs with my last 3 Android devices.
Before I attempt this though, what is this I hear about "cabs"? Is that just a packaged and ready to go version of what is out on NaviFirm+?
Click to expand...
Click to collapse
CABs are Zune update packages and are nothing like the complete ROMs found on NaviFirm.
CABs are like Windows MSU files, while ROMs are like WIMs or VHDs.
In fact, WP CABs are distributed through Windows Update servers just like Windows updates.
Similarly as with Windows on the PC, the updates take longer that a clean install and the process may fail. And it's even harder on the phone, since deploying too many or too litlle CABs can make your phone unupgradable.
Although the cabsender method is fine for really minor upgrades like pushing the firmware only from 12070 to 12072 to fix the volume bug. It may also be used for adding additional display languages.
I am using the Everything Everwhere ROM and I can confirm it has no branding apart from the carrier being listed here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Everything seems to be working well on my phone.
ibjaredu said:
I am using the Everything Everwhere ROM and I can confirm it has no branding apart from the carrier being listed here:
Everything seems to be working well on my phone.
Click to expand...
Click to collapse
Why is the software part of about screen showing Windows Phone 7.5 and why not 7.8 ????
Why would it show 7.8?
Would putting the everything everywhere update on my Lumia void the warranty? I found that if you use the PS tool you can download the firmwares direct from there which is always handy.. Im just reluctant to flash the phone in case it messes with the warranty??
mozza54 said:
Would putting the everything everywhere update on my Lumia void the warranty? I found that if you use the PS tool you can download the firmwares direct from there which is always handy.. Im just reluctant to flash the phone in case it messes with the warranty??
Click to expand...
Click to collapse
I wouldn't worry about it too much, you could always download your native firmware and re-flash it if necessary.
ibjaredu said:
I am using the Everything Everwhere ROM and I can confirm it has no branding apart from the carrier being listed here:
Everything seems to be working well on my phone.
Click to expand...
Click to collapse
What hardware are you running? Does it happen to be the same as mine?
Poked around a bit more and I realized my phone has apps that let me mess with the registry etc. (QC BSP Services). It also has a bunch of apps that start with "z" and seem to have access to root things in the phone (zBig Boss Settings, zCompass, zDebugMenu, zSensorView, zStart KITL). Does anyone know what these are for? Does this indicate there is a custom ROM on my phone?
My phone is a later hardware revision than yours. It definitely sounds like you have a custom firmware on there. You should be able to install the ROM I have just the same though.
ibjaredu said:
My phone is a later hardware revision than yours. It definitely sounds like you have a custom firmware on there. You should be able to install the ROM I have just the same though.
Click to expand...
Click to collapse
Ohhh, i see.
This phone is nuts. I just want to restore it to stock firmware but I'm kind of scared that it might somehow brick the phone. Although...it's now stuck on the NOKIA logo and won't boot up...earlier the phone was stuck in airplane mode. I haven't even tried flashing anything on it yet!
Edit: I did a reset with the vol down + power keys, got back into the phone but it's still stuck in airplane mode! Changing the toggle doesn't do anything...it stays in airplane mode. The wifi is on too and when I toggle the slider, it just switches itself back on after a couple of seconds. WTF?!
Has anyone had their phone get stuck in airplane mode?
Chynkinese, i would do a flash with Tango and Nokia Care Suite.
As far as i know, someone in a china forum said that he had unlocked the F600S' bootloader successfully.
He first flashed a pre-rooted 5.0 TOT and change the build.prop to h901. Then, he flashed h901 6.0 kdz to his phone and the bootloader became h901 version.
Therefore, he could unlock the bootloader simply by entering "fastboot oem unlock", flashing H901's recovery and rooted the phone.
Some users said this method works but some said didn't and even bricked their phones into "Qualcomm HS-USB QDLoader 9008" mode.
I open this thread for raising attention and investigate whether this method really works or not, but please, DO NOT intend to perform this method unless it was proved to be safe.
If you can read Chinese, here is the source (please remove this link if it violates xda's rules):
http://bbs.gfan.com/android-8325666-1-1.html
i recommend, don't... unless u needed to do that then go
I was attempting something like this awhile back. But I wasn't using the normal build.prop. There is one hiding in /cust/open_com_ds/cust_open_hk.prop that I assumed was what the LGUP program used to check vs the one in /system but apparently I was mistaken. Theoretically there isn't anything hardware wise different between the H901 and the H961N besides the dual sim. Those that don't use dual sim might try this. Otherwise I would wait. If there are any people out there that can make kdz's then all it takes is one person to do it right then everyone else can benefit. I might go ahead and try for shizas and googles.
DarkestSpawn said:
I was attempting something like this awhile back. But I wasn't using the normal build.prop. There is one hiding in /cust/open_com_ds/cust_open_hk.prop that I assumed was what the LGUP program used to check vs the one in /system but apparently I was mistaken. Theoretically there isn't anything hardware wise different between the H901 and the H961N besides the dual sim. Those that don't use dual sim might try this. Otherwise I would wait. If there are any people out there that can make kdz's then all it takes is one person to do it right then everyone else can benefit. I might go ahead and try for shizas and googles.
Click to expand...
Click to collapse
Thanks for your reply. According to the source, those people changed their build.prop as below in order to flash h901's kdz:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
By the way, as a H961N user, I also wonder that whether it works on dual sim model. Can we flash the modem and related apps separately in order to make dual sim working if bootloader has unlocked?
If memory serves correctly, Yes with an unlocked bootloader you could adb flash modem *BLAHBLAHBLAH* but idk how that works with dual sim phones.
I honestly get aggravated when I see certain users that say they make TOT or KDZ files when really they took it from other sites that aren't English and say they made it. If that was the case they would make a KDZ with stock everything for the device its for but replace the bootloader to the version from H901 and every LG v10 would be bootloader unlockable but somehow they are too busy or working on other TOTs and kdzs... Assinine lies. Sorry had to throw my two cents out there.
I'm so glad I didn't do this attempt yet. Just remembered I gave my backup phone away so I have nothing to fall back on if this fails. If no one tries this before I get it back I will try.
DarkestSpawn said:
I was attempting something like this awhile back. But I wasn't using the normal build.prop. There is one hiding in /cust/open_com_ds/cust_open_hk.prop that I assumed was what the LGUP program used to check vs the one in /system but apparently I was mistaken. Theoretically there isn't anything hardware wise different between the H901 and the H961N besides the dual sim. Those that don't use dual sim might try this. Otherwise I would wait. If there are any people out there that can make kdz's then all it takes is one person to do it right then everyone else can benefit. I might go ahead and try for shizas and googles.
Click to expand...
Click to collapse
Even though many of the pieces are the same, there could well be some fairly significant differences hardware-wise between the H901 and H961N. The two that I know are really close are the H961N (Hong Kong) and H962, if the kernel sources are identical then there isn't much difference between the two.
On the flip side though, there could be enough similarity to flash the H901's bootloader onto another device. The bootloader wouldn't need to worry about how any of the radio bits work, just avoid touching them.
DarkestSpawn said:
I'm so glad I didn't do this attempt yet. Just remembered I gave my backup phone away so I have nothing to fall back on if this fails. If no one tries this before I get it back I will try.
Click to expand...
Click to collapse
Please do report if you do this. Anyone else out there who is reading, we'd love to hear from you if you try this. While I hope you succeed, failure could well occur. Could you report what device you're thinking of trying this on?
There is a tool from Qualcomm which can allow you to write to the flash before the device boots. If your try fails, that tool could be used to write back what is "supposed" to be there and hopefully you won't have a complete brick. A simpler solution might be to use that tool to simply overwrite your device's bootloader with the H901 bootloader. Note there are 2 copies of the bootloader on the H962 and likely other devices and you'd need to get both. I imagine there are several, but here is one tool for extracting the KDZ files (my goal is to be able to construct modified KDZ files, but I haven't analyzed things enough yet, will likely take some time).
EDIT: What look to be the bootloader areas in the H901, H961N and H962 KDZ files appear to be at the same offsets and the same sizes. I cannot be certain, but this might very well be a workable strategy.
EDIT2: If someone does this, it may be helpful to know which H901BK firmware version you use. The known KDZ file is for 20c, so it may be handy to keep links to that. Once you've done the process, it would be helpful for you to dump copies of all the block devices on the phone. Knowing which one(s) have changed could lead us to how LG's bootloader marks a device as unlocked, leading to easier methods of unlocking (hmm, really need a binary diff utility).
emdroidle said:
Even though many of the pieces are the same, there could well be some fairly significant differences hardware-wise between the H901 and H961N. The two that I know are really close are the H961N (Hong Kong) and H962, if the kernel sources are identical then there isn't much difference between the two.
On the flip side though, there could be enough similarity to flash the H901's bootloader onto another device. The bootloader wouldn't need to worry about how any of the radio bits work, just avoid touching them.
Please do report if you do this. Anyone else out there who is reading, we'd love to hear from you if you try this. While I hope you succeed, failure could well occur. Could you report what device you're thinking of trying this on?
There is a tool from Qualcomm which can allow you to write to the flash before the device boots. If your try fails, that tool could be used to write back what is "supposed" to be there and hopefully you won't have a complete brick. A simpler solution might be to use that tool to simply overwrite your device's bootloader with the H901 bootloader. Note there are 2 copies of the bootloader on the H962 and likely other devices and you'd need to get both. I imagine there are several, but here is one tool for extracting the KDZ files (my goal is to be able to construct modified KDZ files, but I haven't analyzed things enough yet, will likely take some time).
EDIT: What look to be the bootloader areas in the H901, H961N and H962 KDZ files appear to be at the same offsets and the same sizes. I cannot be certain, but this might very well be a workable strategy.
EDIT2: If someone does this, it may be helpful to know which H901BK firmware version you use. The known KDZ file is for 20c, so it may be handy to keep links to that. Once you've done the process, it would be helpful for you to dump copies of all the block devices on the phone. Knowing which one(s) have changed could lead us to how LG's bootloader marks a device as unlocked, leading to easier methods of unlocking (hmm, really need a binary diff utility).
Click to expand...
Click to collapse
I think the only worry of trying this method is a complete hard brick. As you have mentioned, any qualcomm phone has a recovery mode and i guess it should be the "Qualcomm HS-USB QDLoader 9008" mode.
I have searched some information and turn out there are two 9008 mode. It depends on whether the phone messed with Qualcomm’s stuffs, if not, then the phone will enter the "new 9008 mode" and it can let you recover the phone easily by a backup emmc image. If it is, then the phone will enter the "old 9008 mode" and it required specific files and "programmer", however, file suitable for msm8992 hasn't been discovered. Therefore, if this method brick the phone into old 9008 mode, no solution at all.
The information i have refered to, don't know if it is correct:
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
EDIT: The ro.expect.recovery_id should be "0x9260d50f08bef4a761309001fe20e5ab59508e78000000000000000000000000" (if you try it, double check by yourself)
some people said that they bricked the phone because of typing it incorrectly, but i don't know whether it is true or not
I have asked the people who bricked their phones from trying this method. It seems that they really made a typo on ro.expect.recovery_id and cause brick.
Also, i am pretty sure that those phones have gotten into the "old 9008 mode", therefore, "rawprogram0.xml, patch0.xml and prog_emmc_firehose_8992.mbn" are required for using QPST the fix the hard brick.
However, no suitable prog_emmc_firehose_8992.mbn for V10 has been discovered on the internet (even for the G4).
Personally, I injected the H901 aboot into an H962 DZ and flashed it onto my device a few months ago.
Long story made short, it was completely bricked, even without 9008 mode. I recommend you guys to be cautious with this method.
Edit: As I can understand Chinese, I'm currently looking into the tutorial.
ivangundampc said:
I think the only worry of trying this method is a complete hard brick. As you have mentioned, any qualcomm phone has a recovery mode and i guess it should be the "Qualcomm HS-USB QDLoader 9008" mode.
I have searched some information and turn out there are two 9008 mode. It depends on whether the phone messed with Qualcomm’s stuffs, if not, then the phone will enter the "new 9008 mode" and it can let you recover the phone easily by a backup emmc image. If it is, then the phone will enter the "old 9008 mode" and it required specific files and "programmer", however, file suitable for msm8992 hasn't been discovered. Therefore, if this method brick the phone into old 9008 mode, no solution at all.
The information i have refered to, don't know if it is correct:
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Click to expand...
Click to collapse
Useful, though I cannot speak to the reliability of that information. A different source has a tool they say comes from Qualcomm, which may be more reliable with newer devices. Please note, this is a source of claims, I don't know how reliable they are (they also don't provide much detail on the limits of the tool).
WillyPillow said:
Personally, I injected the H901 aboot into an H962 DZ and flashed it onto my device a few months ago.
Long story made short, it was completely bricked, even without 9008 mode. I recommend you guys to be cautious with this method.
Edit: As I can understand Chinese, I'm currently looking into the tutorial.
Click to expand...
Click to collapse
I look forward to more detail/reports from that tutorial. Exact details would be invaluable.
I hoped that would work, but I feared the above possibility. The problem is which portions of the flash image sign which other portions of the image, and how many different keys does LG use? Your observation seems to suggest either the key used for signing the H901 aboot was not honored by the rest of the H962 firmware, or the key used for signing the H962 kernel wasn't honored by the non-unlocked H901 aboot (or both).
If the former case, then which are the pieces prior to aboot and can only those pieces be transplanted from a H901 while still preserving the dual-SIM functionality of the H962 (and H961N)? If the latter case, then I suspect you merely need to run a H901 kernel long enough to unlock the bootloader, then you can put back the H962 kernel and run that with the unlocked bootloader.
The other question is, which portions of the data unlock the bootloader? Is it a small change to the aboot portion? Is it changes elsewhere? Can those changes be isolated from the rest of the H901 firmware?
Just in case you didn't notice, I've got lots of questions. I hope I can figure out answers to some, but others I may not be able to answer. I'm currently targeting the kdztools portion.
@emdroidle
TBH I don't see anything not mentioned already. Basically the process is just
Flash 5.1 rooted -> modify build.prop -> flash H901 KDZ
Personally, I'm not going to do more risky experiments since I already RMA'd my last hard brick
Also, you might want to use IDA to take a look at aboot, which is basically an ELF binary. I had been doing that, but stopped after the brick.
WillyPillow said:
@emdroidle
TBH I don't see anything not mentioned already. Basically the process is just
Flash 5.1 rooted -> modify build.prop -> flash H901 KDZ
Personally, I'm not going to do more risky experiments since I already RMA'd my last hard brick
Also, you might want to use IDA to take a look at aboot, which is basically an ELF binary. I had been doing that, but stopped after the brick.
Click to expand...
Click to collapse
I understand. You're in a better position since LG will honor the warranty on your H962. They're a bit tougher if you get one outside Taiwan.
I was fearing we would have to take that approach. Worse, it looks like the firmware updates change aboot, which suggests settling on one version and trying to crack that is best. I wanted to try Plasma, but IDA is likely far enough ahead to beat Plasma. I'm just glad IDA has a Linux version.
WillyPillow said:
Personally, I injected the H901 aboot into an H962 DZ and flashed it onto my device a few months ago.
Long story made short, it was completely bricked, even without 9008 mode. I recommend you guys to be cautious with this method.
Click to expand...
Click to collapse
After some thought, I realized I should ask for some detail about the failed process you used for this. Did you flash both the aboot and abootbak slices? (/dev/mmcblock0p9 and /dev/mmcblock0p15 if I recall correctly)
If you flashed only aboot and ended up bricked, this seems to suggest it did in fact successfully execute the H901BK aboot, but the aboot decided the signature on boot was incorrect and halted. In this scenario if the portion before aboot had decided aboot had a bad signature, then it should have restored abootbak, which likely would have successfully booted the H962 kernel.
If you flashed both aboot and abootbak, this suggests the portion before aboot decided aboot's signature was wrong and it halted there. This doesn't rule out it successfully executing aboot and aboot deciding boot had the wrong signature, but it makes that less likely.
Hate to say it, but flashing only aboot doesn't really give us much information on the likelihood of flashing a full H901BK image onto a H962 being successful or not. The problem is there could be signatures in many places and any one of those could fail yet reproducing the original scenario would work perfectly.
emdroidle said:
After some thought, I realized I should ask for some detail about the failed process you used for this. Did you flash both the aboot and abootbak slices? (/dev/mmcblock0p9 and /dev/mmcblock0p15 if I recall correctly)
If you flashed only aboot and ended up bricked, this seems to suggest it did in fact successfully execute the H901BK aboot, but the aboot decided the signature on boot was incorrect and halted. In this scenario if the portion before aboot had decided aboot had a bad signature, then it should have restored abootbak, which likely would have successfully booted the H962 kernel.
If you flashed both aboot and abootbak, this suggests the portion before aboot decided aboot's signature was wrong and it halted there. This doesn't rule out it successfully executing aboot and aboot deciding boot had the wrong signature, but it makes that less likely.
Hate to say it, but flashing only aboot doesn't really give us much information on the likelihood of flashing a full H901BK image onto a H962 being successful or not. The problem is there could be signatures in many places and any one of those could fail yet reproducing the original scenario would work perfectly.
Click to expand...
Click to collapse
Hmm, I've never thought this deep. I was just like "Sxxt, my phone bricked! Must be a bad signature somwhere..." and stopped messing around with it
To answer your question, I only flashed aboot, without anything else. And for the details of the brick, you can't even see the "powered by Android" bootloader screen. The device just viberates if you want to turn it on. The only way to make the screen display something is remove the battery and connect it to a computer, for which a "no battery" icon is showed. So my guess then was the aboot signature was invalidated. But now you reminded me the existance of abootbak...
I'll do some research and thinking right now
WillyPillow said:
Hmm, I've never thought this deep. I was just like "Sxxt, my phone bricked! Must be a bad signature somwhere..." and stopped messing around with it
To answer your question, I only flashed aboot, without anything else. And for the details of the brick, you can't even see the "powered by Android" bootloader screen. The device just viberates if you want to turn it on. The only way to make the screen display something is remove the battery and connect it to a computer, for which a "no battery" icon is showed. So my guess then was the aboot signature was invalidated. But now you reminded me the existance of abootbak...
I'll do some research and thinking right now
Click to expand...
Click to collapse
Well, i think that you have bricked your phone into the "Qualcomm HS-USB QDLoader 9008" mode
The phone should be able to fix if you can see "Qualcomm MMC Storage USB Device" in "Devices Manager" when the phone is connecting to the computer.
WillyPillow said:
Hmm, I've never thought this deep. I was just like "Sxxt, my phone bricked! Must be a bad signature somwhere..." and stopped messing around with it
Click to expand...
Click to collapse
I was thinking about it, since I would very much like to somehow unlock the bootloader. While this way may or may not be tweaked to work, it does sound plausible. Analyzing failures can be very valuable.
WillyPillow said:
To answer your question, I only flashed aboot, without anything else. And for the details of the brick, you can't even see the "powered by Android" bootloader screen. The device just viberates if you want to turn it on. The only way to make the screen display something is remove the battery and connect it to a computer, for which a "no battery" icon is showed. So my guess then was the aboot signature was invalidated. But now you reminded me the existance of abootbak...
Click to expand...
Click to collapse
So this may suggest aboot successfully executed, but found a mismatched signature and halted. At which point, flashing the H901BK aboot and boot may be enough to make this work. This may though also require the H901BK recovery image. I do not know where the unlock process actually does its magic, so part of it could be in recovery.
I'd love to hear if you can get it to be successful.
Two threads relevant to this topic have shown up.
First, apparently someone somehow managed to accidentally flash a H901 firmware onto a H960A. That person was looking for help with restoring their device, but it leaves me hopeful this method could in fact work on other devices. Most likely you'd end up with a mix of some portions of the flash being copied from a H901 and some from whatever your phone is normally supposed to run, but this does confirm it is possible to run H901 firmware on other devices.
Second, a method has been found to recover devices from Qualcomm 9008 mode. This is big news since it greatly lessens the danger of a bad flash. Problem is it requires root on the phone to generate the initial image, though I suspect the images produced by my kdztools may well work for the job too.
I very much want to unlock the bootloader of my device, so I'm still doing research trying to estimate how plausible this method is. At this point there are enough reports of wrong V10 device images not being fatal to other V10-type devices for me to consider this method "likely".
Examining KDZ files for several devices, there is quite a bit of overlap between device images. There are 9 slices though which seem to warrant special attention based upon them having backup copies. These are named "sbl1", "pmic", "hyp", "tz", "rpm", "aboot", "sdi", and "raw_resources".
My guess is install a H901 image, do `fastboot oem unlock` and then you can copy everything aside these slices from your original device. My concern is these may need to remain the H901 versions in order to remain unlocked (unless all V10 devices share the unlock method, which may or may not be the case).
It may also work to use my KDZ Tools to copy the PrimaryGPT and BackupGPT areas from the target device onto a H901 image, at which point the process could be done without even needing a factory reset!
I'm pretty sure "sbl1"/"sbl1bak" are the first-stage bootloader. All the others aside from "raw_resources" look to be ELF executables.
Open request to Qualcomm here, could you please make your chips either alternate between trying to boot off of "sbl1" and "sbl1bak" (a single MRAM or PCRAM cell should take too much space, should it?), or else make them randomly choose between booting off them upon power-on? Too often one or the other gets corrupted in such a way that booting fails, but either isn't so corrupt to trigger them to try the backup, or else the primary is so badly damaged it is unable to try the backup. Alternating (and passing to the Linux kernel which one it successfully booted off of!) would greatly increase the chances of successful recovery without specialized tools.
Wiki + Likelyhood evaluation
Having examined the situation enough, I'm pretty sure this method should work. Experimentation though is risky.
I'm now working on creating 2 software tools for this project. One is a simple tool to remark the device a KDZ is for. This is pretty simple and the reports are, once this is done LGUP will happily flash a KDZ onto other devices. The second goal is a tool for modifying the GPT afterwords. While the H901 has a GPT similar to other V10s, it isn't quite identical. Of major note, many other devices have a /cust partition which has some extra software.
These two tools may actually be unnecessary. My KDZ Tools expose all of the data in an inconvenient, but workable format. The KDZ Tools can also be used to replace the GPT for the H901 with a GPT from another device, and they also expose the areas which mark which device a KDZ is for. Problem with using the KDZ Tools for this is there is what looks to be an extra checksum, and I've got no idea whether it covers the GPT (I hope not, but...).
I'm now looking to create the above two tools on GitHub, the LGE Tools. Alas, what may be more valuable is the Wiki on GitHub. I've got speculative instructions a little ways from the top. Towards the bottom I've got a list of which areas you'd need to restore from your original device. I guess I'm a bit unsure of "persist", the content is identical for my device, but the differing timestamps might trigger a flag that something has happened.
Hopefully we can get some testers who can risk needing to RMA their devices (I hope they don't need to, but this IS risky).
emdroidle said:
Having examined the situation enough, I'm pretty sure this method should work. Experimentation though is risky.
I'm now working on creating 2 software tools for this project. One is a simple tool to remark the device a KDZ is for. This is pretty simple and the reports are, once this is done LGUP will happily flash a KDZ onto other devices. The second goal is a tool for modifying the GPT afterwords. While the H901 has a GPT similar to other V10s, it isn't quite identical. Of major note, many other devices have a /cust partition which has some extra software.
These two tools may actually be unnecessary. My KDZ Tools expose all of the data in an inconvenient, but workable format. The KDZ Tools can also be used to replace the GPT for the H901 with a GPT from another device, and they also expose the areas which mark which device a KDZ is for. Problem with using the KDZ Tools for this is there is what looks to be an extra checksum, and I've got no idea whether it covers the GPT (I hope not, but...).
I'm now looking to create the above two tools on GitHub, the LGE Tools. Alas, what may be more valuable is the Wiki on GitHub. I've got speculative instructions a little ways from the top. Towards the bottom I've got a list of which areas you'd need to restore from your original device. I guess I'm a bit unsure of "persist", the content is identical for my device, but the differing timestamps might trigger a flag that something has happened.
Hopefully we can get some testers who can risk needing to RMA their devices (I hope they don't need to, but this IS risky).
Click to expand...
Click to collapse
Wow, i am very surprised that you are still working on this method! You have really paid a lot of effort on it!
After taking a look on your works, i really think that this method may really works to help us to unlock the bootloader.
In fact, the T-Mobile variant of both G5 and V20 have bootloader unlocked and so other version of G5 and V20 may also be able to unlock their booloader through a method like this, therefore, I think we should be able to draw more attention (more devs?) on studying this method.
I tried downloading something in my developer options and it seemed to work, but when my phone restarted I got a message saying, "your device is corrupt. It Can't be trusted and will not boot". The message seems to be in some sort of boot loop, (keeps restarting with the same message). Is there any way I can fix this without sending my phone in to One Plus? I purchased the phone inside of a Metro store.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your phone is from T-Mobile or Metro, check out this forum post to recover your phone: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4324431/
If your phone was factory unlocked, contact OnePlus for a repair. The easiest way to tell if your phone is a carrier device or not is to check the back of the phone. If there's an IMEI engraved on the back of the phone, it's a T-Mobile or Metro phone. If there's not IMEI engraver, its factory unlocked.
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked variant.
edale1 said:
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked var
Click to expand...
Click to collapse
Yeah that was it! Lesson learned. Thank you!
Thats how I managed to mess up my phone and is currently bricked for several months .. no msmdownload for the unlocked .. please try and get a remote session with the oneplus tech guys .. and share if possible
Hold up a second here. If you have tried to relock the bootloader (which will result in the device is corrupt and will not boot message) try this:
Hold down all 3 buttons (Vol+ Vol- and power) for about 8 seconds or so. As soon as the device vibrates quickly release the power button. When you do, the device should be in fastboot. If you are in fastboot you should now be able to connect it to the PC and type the command fastboot oem unlock. This will now attempt to unlock the bootlaoder. Chances are you have previously unlocked the bootloader and have attempted to relock it. Doing so will cause this error message on the UNLOCKED version of the device.
This will wipe the data but return the device to an unlocked state but not completely bricked on stock firmware. Go through the normal prompts to start the device and you should be good.
Remember, if you have fastboot its not COMPLETELY bricked. Not yet anyways.
I had this happened on my OnePlus Nord 200 5g literally the next day after I got it from Metro at T-Mobile. Phone updated as it should but restarted with the same message you received. They tried to accuse me of putting a virus on the phone which did not make any sense and after going through insurance who couldn't accept the claim for "software damage" ... I contacted one plus and had them remote view my laptop with downloaded tar files and had a technician try to reinstall them back to its original factory condition but to no luck. Metro being a franchise company, has the loophole not accepting returned merchandise even under the return policy stated on the receipt, and customer service technically has no control or power over any particular franchise Metro store. I suggest the only answer I had after 2 weeks of frustration from contacting everyone I possibly could to writing corporate, I finally had a CSR tell me to just get a warranty exchange at any Metro store in which I did in two days later I received a new phone which actually works this time so I would suggest just doing the warranty exchange in order to get yourself a workable phone. Hope that helps. \m/
edale1 said:
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked variant.
Click to expand...
Click to collapse
I did this exact thing. Mine is the oem unlocked variant. Is contacting oneplus support still the only option? It's on the metro/tmobile network if that matters. I really fcked up here with dsu loader. Pretty desperate right now for a fix. Please.
superspecialgueststar said:
I did this exact thing. Mine is the oem unlocked variant. Is contacting oneplus support still the only option? It's on the metro/tmobile network if that matters. I really fcked up here with dsu loader. Pretty desperate right now for a fix. Please.
Click to expand...
Click to collapse
You can try the MSM Tools and see if it works, if not, then yes, OP Support is your only option.
edale1 said:
You can try the MSM Tools and see if it works, if not, then yes, OP Support is your only option.
Click to expand...
Click to collapse
Thanks, I downloaded msm tools and there are msm tools included in https://www.terabox.com/web/share/link?surl=7fjfMJSEcdl5zCjPT92IKA
for
dre8t_10_O.05_210713.tar.bz2 -can someone point me to the stock firmware I should be using msmtools error device not match image. Can I use the ~3gb ota zips?
Taking a break and then going to look for a guide for MSM tools.
edit - as an additional point of confusion, my bootloader was unlocked, I was rooted with magisk patched upstream boot.img. Did this happen because I did not know about uninstalling magisk and installing magiosk to the inactive slot? My bootloader is still unlocked, but flashing boot backups etc does not get me out of fastboot loop, and unable to verify boot image error when I try to fastboot boot twrp or orangefox.
You're past the point I can help with, maybe someone else has some more advice for you?
Thanks. And technical support turns out is the only way and sending it in is the only way for the oem unlocked version. I requested a remote session and ended up being told the files aren't working so they can't do a remote session. If they arent working how are they going to flash my device lol...who knows.
Superspecialgueststar,
The released MSM tool is only for the carrier variant and cannot be used for the unlocked variant. There is cryptographic security in place to restrict its use.
You can still fix your unlocked device, just use an unbrick guide for the unlocked version.
[GUIDE] How to unbrick your Nord N200 5G (ALL VARIANTS) or switch bootable slot (REQUIRES UNLOCKED BOOTLOADER)
I've seen alooot of issues lately of people "bricking" their Nord N200's without a method of unbricking (at the time of writing, only T-Mobile variant has MSMTool) I've noticed a reoccurring theme. i myself am guilty of doing it and not...
forum.xda-developers.com
or use my unbrick experience and advice
Un-bricking my Nord N200
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system...
forum.xda-developers.com
Hi everyone, I accidentally locked my phone after I tried to remove the bootloader warning message that booted up everytime I turned on my phone. Now it says that my phone is corrupted in red and I can only boot to fastboot mode. My device is now locked and customer support told me that I needed to go to a OnePlus repair shop. The problem is that I don't live in the US. If anyone can help me I'll be appreciated.
twomad said:
Hi everyone, I accidentally locked my phone after I tried to remove the bootloader warning message that booted up everytime I turned on my phone. Now it says that my phone is corrupted in red and I can only boot to flashboot mode. My device is now locked and customer support told me that I needed to go to a OnePlus repair shop. The problem is that I don't live in the US. If anyone can help me I'll be appreciated.
Click to expand...
Click to collapse
Can you access fastboot? Is the bootloader unlocked or did you lock the bootloader
Kenora_I said:
Can you access fastboot? Is the bootloader unlocked or did you lock the bootloader
Click to expand...
Click to collapse
yes. i can access fastboot mode. Windows recognizes my device when I enter "fastboot devices". I accidentally locked the bootloader while running Pixel Experience 12 GSI and now it says "your device is corrupt. It can't be trusted and will not boot".
twomad said:
yes. i can access fastboot mode. Windows recognizes my device when I enter "fastboot devices". I accidentally locked the bootloader while running Pixel Experience 12 GSI
Click to expand...
Click to collapse
Try to unlock it again with fastboot flashing unlock
Kenora_I said:
Try to unlock it again with fastboot flashing unlock
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
twomad said:
View attachment 5587563
Click to expand...
Click to collapse
this is what is says in Fastboot:
-PRODUCT NAME - holi
-VARIANT - SM_ UFS
-BOOTLOADER VERSION -
-BASEBAND VERSION -
-SERIAL NUMBER - eb375f3e
-SECURE BOOT - yes
DEVICE STATE - locked
twomad said:
this is what is says in Fastboot:
-PRODUCT NAME - holi
-VARIANT - SM_ UFS
-BOOTLOADER VERSION -
-BASEBAND VERSION -
-SERIAL NUMBER - eb375f3e
-SECURE BOOT - yes
DEVICE STATE - locked
Click to expand...
Click to collapse
You'll have to try get into EDL mode, but there's no MSM tool released for the unlocked varient of this phone only the T-Mobile varient
Kenora_I said:
You'll have to try get into EDL mode, but there's no MSM tool released for the unlocked varient of this phone only the T-Mobile varient
Click to expand...
Click to collapse
exactly. I tried to follow this guide https://forum.xda-developers.com/t/...le-slot-requires-unlocked-bootloader.4401113/ but it's only applicable to bricked phones that have bootloader unlocked
twomad said:
exactly. I tried to follow this guide https://forum.xda-developers.com/t/...le-slot-requires-unlocked-bootloader.4401113/ but it's only applicable to bricked phones that have bootloader unlocked
Click to expand...
Click to collapse
Yeah unfortunately you're stuck here, without the MSM tool
You could try calling One Plus customer support, explain there are no OP repair shops locally, and request a remote session to fix it.
It's been a while since anyone tried, you might luck out and they could have the MSM tools for the unlocked variant now. (PLEASE share them if they do, they'll send you a link to download the MSM tools ahead of time for the remote session)
Barring that, they'll probably want you to mail the phone in to get it fixed.
edale1 said:
You could try calling One Plus customer support, explain there are no OP repair shops locally, and request a remote session to fix it.
It's been a while since anyone tried, you might luck out and they could have the MSM tools for the unlocked variant now. (PLEASE share them if they do, they'll send you a link to download the MSM tools ahead of time for the remote session)
Barring that, they'll probably want you to mail the phone in to get it fixed.
Click to expand...
Click to collapse
I was actually looking into this for the OnePlus 10 Pro but it seems unlikely but who knows?
A remote session is how we got the T-Mobile MSM tools. It's just every time someone's tried with the Unlocked variant, they've been told the remote support team doesn't have access to the MSM tools for the Unlocked variant. As I said, it's been a while since the last attempt, so there's a chance they may have gotten it by now.
edale1 said:
You could try calling One Plus customer support, explain there are no OP repair shops locally, and request a remote session to fix it.
It's been a while since anyone tried, you might luck out and they could have the MSM tools for the unlocked variant now. (PLEASE share them if they do, they'll send you a link to download the MSM tools ahead of time for the remote session)
Barring that, they'll probably want you to mail the phone in to get it fixed.
Click to expand...
Click to collapse
yeah, I emailed OnePlus and they immediately told me to send the phone for repair. I emailed them again so that they can provide me an MSM tool so let's see how it goes.
twomad said:
yeah, I emailed OnePlus and they immediately told me to send the phone for repair. I emailed them again so that they can provide me an MSM tool so let's see how it goes.
Click to expand...
Click to collapse
Hopefully it will work, the talk about the unlocked version of the MSM tool has kind of died down for around 2 months or so. (On this forum, at least)
Sorry if I missed something and am plucking at brain cells that have already been plucked, but has anyone tried EDL mode and emmcdl.exe with the available firehose? Its not as straight forward to do being as the n200 is UFS amd not EMMC, but it should still be do'able. Its how I managed to get my brick back to fastboot... For that matter, the UFS provisioning xml is available for QFil. You'd have to determine which storage make you have (samsung or toshiba).... Just a thought
the.real.p3y0t3 said:
Sorry if I missed something and am plucking at brain cells that have already been plucked, but has anyone tried EDL mode and emmcdl.exe with the available firehose? Its not as straight forward to do being as the n200 is UFS amd not EMMC, but it should still be do'able. Its how I managed to get my brick back to fastboot... For that matter, the UFS provisioning xml is available for QFil. You'd have to determine which storage make you have (samsung or toshiba).... Just a thought
Click to expand...
Click to collapse
Thing is we don't have the firehose, otherwise it would be easy with qfil
biff_train said:
Hopefully it will work, the talk about the unlocked version of the MSM tool has kind of died down for around 2 months or so. (On this forum, at least)
Click to expand...
Click to collapse
"About your query, we would like to inform you that, currently, we are unable to perform a remote session for OnePlus Nord N200, in this case, we request you to send the device to the serviceable region to get it repaired." I'm screwed
twomad said:
"About your query, we would like to inform you that, currently, we are unable to perform a remote session for OnePlus Nord N200, in this case, we request you to send the device to the serviceable region to get it repaired." I'm screwed
Click to expand...
Click to collapse
Yeah they did that for the OnePlus 10 Pro as well
Kenora_I said:
Thing is we don't have the firehose, otherwise it would be easy with qfil
Click to expand...
Click to collapse
Firehose should be right inside the (extracted) OPS and common to the variants, but I believe OPlus firehoses are encrypted and can't simply be used with QFIL.
AndyYan said:
Firehose should be right inside the (extracted) OPS and common to the variants, but I believe OPlus firehoses are encrypted and can't simply be used with QFIL.
Click to expand...
Click to collapse
Yeah, we tried it but it's not loading actually
hello, i am faced with the decision to get the tmobile OnePlus N20 or the N200.
I am abandoning samsung after years of being disappointed by not being able tto do witthg my phone what i choose.
I want a device i can root and tinker with and modify as i please.
so im looking at these 2 phones and obviousl the n20 wins according tto tthe specs. butt i would like tto know if anyone has been able tto roott this device yet? or do yyou foresee any major obsttacles to unlocking the boottloader? i dont wantt to be stuck yet again with a device tthat i cant mod the way i want. i would like tto eventually be able to run kali or some custom roms on it. i need a device that i can mosl replace my lapttopwith. i cant afford tthe f;lagship pohone rightt now or i would go witth tthat. if anyone has an suggestions or info i would greatly appreciate it.
also i know these are supposed tto have to be sim unlocked first but i saw in anotther thread on anotherdevice i believe it was an OPO something but there was a script hat got rid of tthe services/apps that prevented unlocking the booloader while sim locked.
does anone know if the same script could be run on this device or will i have to sim unlock i?
The unlocked variant can be rooted as easily as any, as long as you get a copy of its boot image. The TMo variant (which you're after) has yet to get its bootloader unlock token.
To me, having high refresh rate is paramount, so N20 omitting that is a critical flaw. Plus, having tried GSIs on both, I felt N20 was weirdly stuttery/unresponsive for its specs.
PsYk0n4uT said:
hello, i am faced with the decision to get the tmobile OnePlus N20 or the N200.
I am abandoning samsung after years of being disappointed by not being able tto do witthg my phone what i choose.
I want a device i can root and tinker with and modify as i please.
so im looking at these 2 phones and obviousl the n20 wins according tto tthe specs. butt i would like tto know if anyone has been able tto roott this device yet? or do yyou foresee any major obsttacles to unlocking the boottloader? i dont wantt to be stuck yet again with a device tthat i cant mod the way i want. i would like tto eventually be able to run kali or some custom roms on it. i need a device that i can mosl replace my lapttopwith. i cant afford tthe f;lagship pohone rightt now or i would go witth tthat. if anyone has an suggestions or info i would greatly appreciate it.
also i know these are supposed tto have to be sim unlocked first but i saw in anotther thread on anotherdevice i believe it was an OPO something but there was a script hat got rid of tthe services/apps that prevented unlocking the booloader while sim locked.
does anone know if he same scrip could be run on his device so as no o have o wai il i sim unlock i?
Click to expand...
Click to collapse
Get the n20 over the n200 if the final price difference is less than $60.
The n200 is a bad device for its specs because oneplus has no interest in optimizing the OS for its low end phones with 4gb ram, because oneplus has only two devices with 4gb ram: the n100 and n200. Oneplus put an OS designed for 6gb/8gb ram with mid-high end cpus on the N200 which has only 4gb ram and lower end cpu, and as a result, the N200 performs like a Motorola phone with 2gb/3gb ram.
Similarly speced Motorola phones perform much better than oneplus.
Ironically, if you update the N200 to android 12, the system will say the phone has a snapdragon 855 cpu, while it has a low end snapdragon 480 cpu. So basically oneplus software engineers just put an OS designed for high end phones onto the low end N200 without any optimization, and even forgot to change the cpu model name.
If you buy the carrier tmo/metro version, you need to obtain unlock token bin to unlock the bootloader, and you need to sim unlock first to enable OEM unlock or you can use the disabling Qualcomm uim app trick.
googlephoneFKLenAsh said:
Get the n20 over the n200 if the final price difference is less than $60.
The n200 is a bad device for its specs because oneplus has no interest in optimizing the OS for its low end phones with 4gb ram, because oneplus has only two devices with 4gb ram: the n100 and n200. Oneplus put an OS designed for 6gb/8gb ram with mid-high end cpus on the N200 which has only 4gb ram and lower end cpu, and as a result, the N200 performs like a Motorola phone with 2gb/3gb ram.
Similarly speced Motorola phones perform much better than oneplus.
Ironically, if you update the N200 to android 12, the system will say the phone has a snapdragon 855 cpu, while it has a low end snapdragon 480 cpu. So basically oneplus software engineers just put an OS designed for high end phones onto the low end N200 without any optimization, and even forgot to change the cpu model name.
If you buy the carrier tmo/metro version, you need to obtain unlock token bin to unlock the bootloader, and you need to sim unlock first to enable OEM unlock or you can use the disabling Qualcomm uim app trick.
Click to expand...
Click to collapse
Care to elaborate on what this Qualcomm uim app trick happens to be?
So I went with the n20. Actually seems to be a pretty decent phone other than the fact that it shipped with a 7 digit serial so I can't get an unlock token. Been back and forth with OnePlus trying to get it resolved but they always just tell me they will email a response within a few days. Their last response was to add a zero before the serial. But doing so just gives me an error that the serial/unlock code don't match. Hopefully I can get this taken care of and get the bootloader unlocked. OEM unlock was easy peasy to get with the debloat script found elsewhere in the opo threads here
Actually I have to say this is one of the better performing devices that I've owned. Similar to some of the flagship phones I've had. Only the refresh rate I guess would be a turn off for some though it doesn't bother me at all.
N20 of course
6/128 can make big difference from N200
Due to limit of response time, 90Hz IPS may not be better than 60Hz AMOLED
695 is like 750 according to Geekbench
PsYk0n4uT said:
So I went with the n20. Actually seems to be a pretty decent phone other than the fact that it shipped with a 7 digit serial so I can't get an unlock token. Been back and forth with OnePlus trying to get it resolved but they always just tell me they will email a response within a few days. Their last response was to add a zero before the serial. But doing so just gives me an error that the serial/unlock code don't match. Hopefully I can get this taken care of and get the bootloader unlocked. OEM unlock was easy peasy to get with the debloat script found elsewhere in the opo threads here
Click to expand...
Click to collapse
Oem unlock means sim unlock or bootloader unlock?
eagle3489 said:
Oem unlock means sim unlock or bootloader unlock?
Click to expand...
Click to collapse
in short, bootloader unlock.
OEM stands for Original Equipment Manufacturer. It refers to the manufacturer lock on the bootloader. It is a security feature to keep you from accidentally bricking your device by tampering with the system images/files or malware from being able to modify or tamper with your system. This is why SafetyNet fails when you root and many banking apps and games check SafetyNet at the beginning of execution to make sure that your running a secure system before they allow an app to open. There are some ways to get around that by hiding root/magisk with Xposed modules(LSposed) etc... Some methods work for some apps and others dont. Make sure you have everything backed up before doing any modifications to your system because its easy to brick your device(make it unbootable/nonfunctional)
I havent found a way to SIM unlock without going through the carrier. There are services out there that claim to be able to SIM unlock your device for a fee, and many have been reviewed by other members. I have not personally ever used one. But here Im referring to unlocking the bootloader so that the system on the device can be modified (rooted, non-stock ROMs, system tweaks/mods)
ScarletWizard said:
I have the n20 and was able to unlock boot loader and root with still being carrier locked.
Click to expand...
Click to collapse
Yeah, mine is rooted tooted and reasdy to be booted and is sitll carrier locked and not paid off..
ScarletWizard said:
Post your t mobile bill. Here is mine View attachment 5772795
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I read your posts and decided on the N20 as well and I must say this is an AWESOME little phone.
It came with the stock July OS. I have read many of the posts on here but I'm sort of stuck. I can't seem to figure out how to get a copy of the original OS. Read some options saying if i couldnt get a copy I could try to make one using twrp but that went down a dead end and I am back to square one. I have enabled developer mode, debug over usb, and set the setting to allow oem unlock and I'm kind of stuck at this point. My goal is to root this thing so that I can get call recording working like my older phones.
jonathandeath said:
I read your posts and decided on the N20 as well and I must say this is an AWESOME little phone.
It came with the stock July OS. I have read many of the posts on here but I'm sort of stuck. I can't seem to figure out how to get a copy of the original OS. Read some options saying if i couldnt get a copy I could try to make one using twrp but that went down a dead end and I am back to square one. I have enabled developer mode, debug over usb, and set the setting to allow oem unlock and I'm kind of stuck at this point. My goal is to root this thing so that I can get call recording working like my older phones.
Click to expand...
Click to collapse
File folder on MEGA
mega.nz
ScarletWizard said:
I brick my n20 daily trying exposed modules and I restore everytime using my boot.img backup
Click to expand...
Click to collapse
You should seriously flash this before anything and it'll save you from bootloop
Thank you so much! I am downloading now.
This is the one I picked up just for reference. 8 digit serial number on this model.
I disabled automatic updates and had the oem bootloader unlocked as well as all playstore options for updates disabled and this morning the phone updated itself without warning to the august update. It started talking about upgraded to android s and i factory reset it hoping it would roll everything back, but nope. Stuck on stupid August Update. I just wanted to get root back on it with call recording and lock down all android os updates.
ScarletWizard said:
Where do you find these zips. I haven't seen that in any repo
Click to expand...
Click to collapse
Hours and hours of shospelessly searching the bowels of th einternet my good man.
DrScrad said:
You should seriously flash this before anything and it'll save you from bootloop
Click to expand...
Click to collapse
How do I flash this first? I am starting fresh again tonight and want to do it right.
Gotcha,
So I have chosen to begin this portion with the following.
Disable DM-Verity or Android Verified Boot without TWRP
In this tutorial, we will show you the steps to disable DM-Verity or Android Verified Boot (AVB) without using TWRP Recovery.
www.droidwin.com
First step is to get a stock image file. However I have not been able to make a copy of my stock rom nor the current stock rom on my Phone now which is now on August patch 2022-09-05. I have downloaded several copies but there have been posts saying not to use just any version of stock rom so I'm trying to make sure i'm doing this right.
I am also on
Build Number CPH2459_11_A.08
Basebane version Q_V1_P14
Kernel version 5.4.147-qgki-g26211b5d5105
Hardware version CPH2459_11
I have the following files downloaded to work with.
I'm thinking of using this one.
Inside the following files can be found
If this is all right then I will try to continue with this portion of their instructional.
Does this sound about right?