Delete
I was warned to delete this thread because of the Xda rule.
Bye.
Close the thread!
I think it's just the common adb fastboot bootloader lock command
ExtraDan said:
I think it's just the common adb fastboot bootloader lock command
Click to expand...
Click to collapse
Maybe, but I don't know the principle.
China user
andy_zhang said:
Maybe, but I don't know the principle.
China user
Click to expand...
Click to collapse
Whats the tool? I would like to check it out.
TheMadScientist said:
Whats the tool? I would like to check it out.
Click to expand...
Click to collapse
I've been warned. I'm sorry, I cann't answer.
China user
andy_zhang said:
I've been warned. I'm sorry, I cann't answer.
China user
Click to expand...
Click to collapse
Sounds fair enough
@andy_zhang Why have you been warned by someone? The useage of the tool is completely legal, like other such tools IF you use it for legal reasons only and not things related to theft and so on. The way how they do it as far as I know on the LG is "nuking" the laf as how we called it back in the days, so the removal of the LG Download mode as it results in the access to the fastboot mode. After the reboot in the bootloader they execute the fastboot erase config command on their devices to remove the google account. And so on. The tool is just a collection of those methods and firmware flashing/restore tools. I believe that for that software you needed some kind of box though.
Btw @andy_zhang if you want to keep it secret I would suggest to remove the image.
wulsic said:
@andy_zhang Why have you been warned by someone? The useage of the tool is completely legal, like other such tools IF you use it for legal reasons only and not things related to theft and so on. The way how they do it as far as I know on the LG is "nuking" the laf as how we called it back in the days, so the removal of the LG Download mode as it results in the access to the fastboot mode. After the reboot in the bootloader they execute the fastboot erase config command on their devices to remove the google account. And so on. The tool is just a collection of those methods and firmware flashing/restore tools. I believe that for that software you needed some kind of box though.
Btw @andy_zhang if you want to keep it secret I would suggest to remove the image.
Click to expand...
Click to collapse
Well the name of the program is censored so they should be safe.
Also don't be pressured to tell the name of the software not even in PM, it doesn't worth your well being and safety, we don't have as many developers or hackers around this forum anyway so we wouldn't be able to discover how to reverse whatever the program doing anyway
@ExtraDan don't worry I won't be pressured by people. And the tool isn't some tool really meant to be secret or so. It's just not as popular in the public. And there's no need to reverse engineer anything, just seeing it function makes you realise how it works (if you have some more then basic knowledge on certain topics like fastboot and lg related things in this case). It's just that the tool is using methods that are already available publically on the internet, the only thing that the tool does is combining all those things and instead of typing just pressing a button more like. Even if the G5 doesn't have many developers, enough people still visit the G5 forums with basic android and searching knowledge.
And it isn't so safe even though the censoring but it also doesn't has to be kept safe either as it's nothing illegal if the program isn't used for illegal reasons.
Sent from my LG-H850 using Tapatalk
also I am not associated with the sources so I most likely dont think I break any law, but i found this
https://www.clangsm.com/forum/index.php?showtopic=434367&st=40&p=1717691&#entry1717691
Making an account will reveal the full name of the program on comment #49
Looking up the name brings up this thread
http://forum.gsmhosting.com/vbb/f453/lg-2-3g-tool-9-36-a-2228171/
And this is the download they provided in the last comment
https://mega.nz/#!nw4QRBII!JYvpldxFfTOiJ-EWjx-hq5C1F6Q6_L9kPy_DFvg7wE0
I havent downloaded it nor tested it, so its on your own risks, remember to scan your stuff on VirusTotal before doing anything
Seems like searching the name also shows up a lot of videos of the program being cracked, im not entirely sure what it does, but from my assumption I think its related to unlocking and locking devices to carriers, but it might be much more
this version requires the smart cards and zx3 box nothing bad here other than pricey
Related
Hurrah! this has been fixed WOO!.
see here.
well done guys, you have made me a happy g2 owner again!!
Hi Everyone,
i figured we might need to clean up the
http://forum.xda-developers.com/showthread.php?t=805024
conversation.
as i see it, there are 2 issues
1. people receive an unlock code, the phone accepts it but then it cannot find any network
2. people receive an unlock code, have troubles entering the code but eventually get it in ok.
please do not post anything "setting" related - apn's, bands etc as this has been tried and shown not to work (yet)
it might be helpful if people who have issue number 1 could post some answers to some questions.
as i am not at all smart enough to work out what we need to know from these people, id appreciate it if those in the know could pm me what they think could be useful, and ill make a template for people to follow
troubleshooting template
----
----
----
----
Current Theories: (please PM me if i have anything wrong here or if i need to add details.)
-------------
Theory #1
Ghul99: the code is accepted, but the phone is still locked?
http://forum.xda-developers.com/show...&postcount=121
------------
interesting information
this seems to support theory #1
1. i unlocked phone - code entered successfully, and i was no longer prompted to enter an unlock code
2. i perm-rooted my phone - all went to plan
3. i put the vision rom on my phone (http://forum.xda-developers.com/showthread.php?t=834450) loaded ok
4. i put a sim in my phone and now i am prompted for an unlock code.
5. i tried to re-enter my code but it would not accept it (it is the same code from step 1)
Nice idea for taking the initiative to clean up the thread which was getting excessilely long!
I'm hoping we can see some progress in a few days as I'm really missing being able to get any cell reception on a MOBILE PHONE!?
Regards.
I will summerize my knowledge later but one thing upfront.
IntuativNipple posted today in IRC that he found the way to get real S-OFF which would also allow SIM-unlock without code.
So there is hope for a solution, but keep your patience.
Sent from my T-Mobile G2 using XDA App
guhl99 said:
I will summerize my knowledge later but one thing upfront.
IntuativNipple posted today in IRC that he found the way to get real S-OFF which would also allow SIM-unlock without code.
So there is hope for a solution, but keep your patience.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
That's really exciting.
Thanks for bring up the good news!
Sent from my T-Mobile G2 using XDA App
guhl99 said:
I will summerize my knowledge later but one thing upfront.
IntuativNipple posted today in IRC that he found the way to get real S-OFF which would also allow SIM-unlock without code.
So there is hope for a solution, but keep your patience.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Just to help guhl and catch up with some unnecessary posts.
Common solutions like Reboot, different sims to try, Hard reset, flash stock ROM or trigger the unlock window to reenter the code doesn't work
Summary of my knowledge so far
For case 1 which was the original problem my theory is the following.
Cause:
Because of problems with the write procedure to the emmc memory the MCCMCN to which the phone is locked did not get cleared but set to an arbitrary value in my case "C3AB".
The CID value is still the same as it used to be (and also in case of a successful unlock would stay the same) which is "T-MOB010". The CID is a 8 character string and the case where all characters are the same (i.e. "11111111") is called Super-CID.
It is of no relevance if you use or used the hardware or software keys, T-Mobile or third party sources. The only reason where it would be your fault is if you pulled the battery!
The unlock-code that we possess (regardless if official or from a different source) is not valid to unlock the phone from this value "C3AB". If one tries again (directly with the modem, using my modified libril.so or a different ROM) the lock counter will increase.
Potential ways to repair this state:
1. Give it back to T-Mobile if you can In my opinion this is a clear warranty case
2. Find someone who has the MegaSIM and the HTC-diag software.
This will definitely work but it is going to be hard to find someone because the SIM is rare and very new.
3. Wait until (or help achieving) the so called "real S-OFF" state of the phone (when also the radio has security disabled) is reached.
When this is achieved one can disable the SIM-lock without any code.
There are still some very good developers after this goal even if for different reasons.
Which information could help us:
1. The output of the following AT-Command sequence from successful and unsuccessful unlocks
Code:
ATE1
ATV1
[email protected]?
[email protected]?AA
[email protected]?40
[email protected]?80
I will try to write a HowTo later for Windows.
For linux see the following posting from the old thread (http://forum.xda-developers.com/showpost.php?p=8750299&postcount=121)
2. The next thing that would help is a logcat from the first unlock process itself.
Howto:
Start the first logcat using the USB-cable and adb before you boot the phone with the foreign SIM.
Code:
adb logcat -b radio > lc_unlock.txt
leave the logcat running and complete the unlock procedure till the phone reboots (the logcat will end automatically)
As soon as the first logcat exits start a new one using:
Code:
adb logcat -b radio > lc_after_unlock.txt
leave it running for 1 minute and then stop it using <Ctrl>-C
3. The next thing that really would help is that you do not post anything in this thread (use the old one instead) that has to do with:
- the APN
- trying another SIM (you would be very lucky if you had one that fits the arbitrary SIMlock)
- reboot, factory reset, use a stock or non stock firmware
- use the hw/sw-keyboard, wait for the right outside temperature or other esoteric procedures
Finally I would like to ask moodecow to edit his original posting and incorporate or link everything that he finds important or helpful in his posting so that it will stay an top.
That is some very exciting news, thank you for the update!
One quick question, when we achieve radio-s off it esssentially would mean everyone could unlock their phones for free?
Thanks.
Sent from my T-Mobile G2 using XDA App
I have 2 ideas, which can help:
1. For people before unlock - maybe performing S-off before unlock will help.\
2. For people after unlock: in bootloader there is "SIMLOCK" option. When you open it, it shows file not found etc. As I think, it can be used to simlock phone for operator, whose numbers are in some file. There is my solution - find what that files are in phone's source code or by any other method, then put them in right place, enter numbers of operator you want to use, open that "SIMLOCK" and lock phone to your network. I don't know if it will work, but it makes some sense.
ms93 said:
I have 2 ideas, which can help:
1. For people before unlock - maybe performing S-off before unlock will help.\
2. For people after unlock: in bootloader there is "SIMLOCK" option. When you open it, it shows file not found etc. As I think, it can be used to simlock phone for operator, whose numbers are in some file. There is my solution - find what that files are in phone's source code or by any other method, then put them in right place, enter numbers of operator you want to use, open that "SIMLOCK" and lock phone to your network. I don't know if it will work, but it makes some sense.
Click to expand...
Click to collapse
Your first idea sounds reasonable and I would support it.
Your second idea is something that is worked on, but you do not only need the correct file (which is actually called DMCID.dat) but there also has to be some "magic number" (like on a gold card) on the micro-sd card.
an important piece of info to carryover from other thread:
1- No APNs are listed
2- if you try to define one, it doesnt save
No APNs being listed is related to the rom more or less, not the issue we're having.
APN is software issue, correct me if I'm wrong so either way it shouldn't pose as an issue to us.
im saying its a symptom that seems to go along with the problem in the title of this thread, so, worth noting.
ie: i think everyone who has the post-unlock no-connection problem, cannot save APNs. all others can.
if you are a counterexample please say so. that would help.
guhl99 said:
For case 1 which was the original problem my theory is the following.
Cause:
Because of problems with the write procedure to the emmc memory the MCCMCN to which the phone is locked did not get cleared but set to an arbitrary value in my case "C3AB".
The CID value is still the same as it used to be (and also in case of a successful unlock would stay the same) which is "T-MOB010". The CID is a 8 character string and the case where all characters are the same (i.e. "11111111") is called Super-CID.
It is of no relevance if you use or used the hardware or software keys, T-Mobile or third party sources. The only reason where it would be your fault is if you pulled the battery!
The unlock-code that we possess (regardless if official or from a different source) is not valid to unlock the phone from this value "C3AB". If one tries again (directly with the modem, using my modified libril.so or a different ROM) the lock counter will increase.
Potential ways to repair this state:
1. Give it back to T-Mobile if you can In my opinion this is a clear warranty case
2. Find someone who has the MegaSIM and the HTC-diag software.
This will definitely work but it is going to be hard to find someone because the SIM is rare and very new.
3. Wait until (or help achieving) the so called "real S-OFF" state of the phone (when also the radio has security disabled) is reached.
When this is achieved one can disable the SIM-lock without any code.
There are still some very good developers after this goal even if for different reasons.
.
Click to expand...
Click to collapse
i have got HTC MEGA SIM and Almost all DIAG files but
T-mobile G2 case =After putting unlock code NO NETWORK cant be solved because when we give s58 clear command it shows SIMLOCK CORRUPTED
i can post the detailed info and pictures if you want it would be a pleasure if could help in any kind of DEVELOPMENT
BTW
if we don t put code in the same version,same country,purchased in the same lot of handsets and use MEGASIM directly without touching anything than it works perfect
kabir_del said:
i have got HTC MEGA SIM and Almost all DIAG files but
T-mobile G2 case =After putting unlock code NO NETWORK cant be solved because when we give s58 clear command it shows SIMLOCK CORRUPTED
i can post the detailed info and pictures if you want it would be a pleasure if could help in any kind of DEVELOPMENT
BTW
if we don t put code in the same version,same country,purchased in the same lot of handsets and use MEGASIM directly without touching anything than it works perfect
Click to expand...
Click to collapse
Posting any further details and/or pictures would be much appreciated!
So if megasim has failed due to corruption I think that the only way to solve our issue is to write directly to emmc partition holding locking information. And I don't now how easy and plausible this is...
I think if we get S-Off for Radio, we'll be able to write to that partition. I hope
andrewklau said:
I think if we get S-Off for Radio, we'll be able to write to that partition. I hope
Click to expand...
Click to collapse
I am a little bit worried about writing this information directly because the partition will be encrypted.
And also copying the complete partition from a working phone or one that is still unlocked will not be an option because the IMEI will also be there and we would not want to overwrite that.
So my hopes are more that there is some kind of a restore procedure from a secure area (I know that Nokia phones can do this, but HTC ?) or that we can lock the phone again with the SIMLOCK option in hboot.
Sent from my T-Mobile G2 using XDA App
well I guess time will tell, does tmobile or htc do replacements (or has anyone tried) for phones no longer on a contract or that are now unlocked?
Sent from my T-Mobile G2 using XDA App
andrewklau said:
Posting any further details and/or pictures would be much appreciated!
Click to expand...
Click to collapse
here we go Pictures first Video coming soon
First Red colour is the error we get on when we try the command
1=clear s58 data
2ND IMAGE is the one when we press the DEVICE INFO
today is sunday not much time will upload the full clear video tommorow and still i have not tried to the all options of the diag maybe it can repair it but sure i will do some more things tomm.
88
I have tried to use my HTC vision G2 as I unlocked it but after that I am unable use as I am unable to find anything which would be hlpful for me as I have the first case problem. I just want to know that would it help me that if someone would flash my HTC Vision G2. I just want to know about that as now I am in Pakistan
Sent from my T-Mobile G2 using XDA App
when I do ADB devices on my play (R800x) it gives me a string of random numbers for the device and when I put in the first 14 digits on the sony site to get a key to unlock the bootloader it gives me one but I have no clue if this is even something i should poke w/ or does everyone have random numbers under adb devices?
List of devices attached
43x2354x314350x73238 device
( i put x for some of the numbers as I have no idea if this is a unique number to me or what and if so dont want that floating around XDA )
Ignore this it just shows things are working
/....now to figure out the missing 3 numbers and then I can steel his credit card numbers mwwwahaaahaaa
seriously it's not a unique identifier for "your" phone
b00sted said:
when I do ADB devices on my play (R800x) it gives me a string of random numbers for the device and when I put in the first 14 digits on the sony site to get a key to unlock the bootloader it gives me one but I have no clue if this is even something i should poke w/ or does everyone have random numbers under adb devices?
List of devices attached
43x2354x314350x73238 device
( i put x for some of the numbers as I have no idea if this is a unique number to me or what and if so dont want that floating around XDA )
Click to expand...
Click to collapse
its your imei number i beleve, it shows that your device is connected if the sony website gives you an unlock code, and you can connect your device in fastboot mode, you are able to unlock your bootloader.
It's not your IMEI number (check it with *#06# and you'll find that it doesn't begin with a 4, e.g.), but it is indeed unique to every device, and not safe to post in its wholeness
BTW, if you don't know what you are doing, you should leave the matter of unlocking the bootloaders to rest. You won't be able to update OTA if you unlock them...
can someone give me the URL to get my code?
ncaissie said:
can someone give me the URL to get my code?
Click to expand...
Click to collapse
Try searching it does wonders
Sent from my R800i using XDA App
Logseman said:
It's not your IMEI number (check it with *#06# and you'll find that it doesn't begin with a 4, e.g.), but it is indeed unique to every device, and not safe to post in its wholeness
BTW, if you don't know what you are doing, you should leave the matter of unlocking the bootloaders to rest. You won't be able to update OTA if you unlock them...
Click to expand...
Click to collapse
but that is the whole point of unlocking it, I dont care about OTA's I really wish some more devs would pop up as CWM & unlocked phone = sexy and once all that happens can just flash the OTA's via CWM.
You said:
I have no clue if this is even something i should poke w/
Click to expand...
Click to collapse
and that's why I tell you what I tell you. Give these forums a read, search the relevant concepts and methods, and then you'll be empowered enough to decide what to do.
I just made a video on how to use fastboot to factory reset back to 100% stock, as I could not find a helpful video on how to do so.
http://youtu.be/ZtRSrQrzIPI
please like and subscribe for more helpful videos to come! :good:
UbuntuBrandon said:
I just made a video on how to use fastboot to factory reset back to 100% stock, as I could not find a helpful video on how to do so.
http://youtu.be/ZtRSrQrzIPI
please like and subscribe for more helpful videos to come! :good:
Click to expand...
Click to collapse
?
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
samwathegreat said:
?
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
yea i saw the text guide with that video, but i wanted to do one with a little more production value. it helps people when they can see what youre doing better.
UbuntuBrandon said:
yea i saw the text guide with that video, but i wanted to do one with a little more production value. it helps people when they can see what youre doing better.
Click to expand...
Click to collapse
Ok, in that case, thanks.
Here's a suggestion: what would *really* be helpful would be an additional video for Linux / Mac users with links to the relevant "motofastboot" binaries for those respective OS's. I find that since there is no guide, I'm having to type -everything- out each time I help someone on Linux or Mac. In all reality, I should have written one long ago (at this point it would have saved me tons of time)....but your username suggests you are Linux-savvy.
Really, the only difference (as you likely already know) is that the Linux variant of the mfastboot binary is called "fastboot" (though you can use it for all commands), and the mac variant has yet another filename.
Additionally, the windows mfastboot binary -can- be used for all flashing and not just system.img -- I often have users use mfastboot for all flashing commands just for simplicity's sake.
Good Luck. I hope to see many more videos to come. :good:
samwathegreat said:
Ok, in that case, thanks.
Here's a suggestion: what would *really* be helpful would be an additional video for Linux / Mac users with links to the relevant "motofastboot" binaries for those respective OS's. I find that since there is no guide, I'm having to type -everything- out each time I help someone on Linux or Mac. In all reality, I should have written one long ago (at this point it would have saved me tons of time)....but your username suggests you are Linux-savvy.
Really, the only difference (as you likely already know) is that the Linux variant of the mfastboot binary is called "fastboot" (though you can use it for all commands), and the mac variant has yet another filename.
Additionally, the windows mfastboot binary -can- be used for all flashing and not just system.img -- I often have users use mfastboot for all flashing commands just for simplicity's sake.
Good Luck. I hope to see many more videos to come. :good:
Click to expand...
Click to collapse
Appreciate the feedback! I plan on doing my videos in series with one another, where if one process has a linux counterpart, I will make a corresponding video before I move too far past the topic into different videos.
I would appreciate if anyone has ideas/guides that they would like me to make into a high-quality, in-depth production.
I rarely post but read a lot.. I want to thank you for providing this...its great
UbuntuBrandon said:
Appreciate the feedback! I plan on doing my videos in series with one another, where if one process has a linux counterpart, I will make a corresponding video before I move too far past the topic into different videos.
I would appreciate if anyone has ideas/guides that they would like me to make into a high-quality, in-depth production.
Click to expand...
Click to collapse
Just use a virtual box to emulate a Linux system and a MacOS system.
Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
How to enable the experiment:
Download the attached APK
Sideload the APK
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[ ] com.pixeloembypass" is in the list
Type in "cmd overlay enable com.pixeloembypass", and hit enter
Reboot the phone
Go into Developer Options to see if "OEM unlocking" can now be toggled on. If so, congratulations!
If "OEM unlocking" is able to be enabled, do so, and reboot the phone into fastboot mode. Unlock as per directions on the factory images site.
NOTE: As usual, if bootloader is unlocked/relocked, a factory reset will be performed.
How to uninstall the experiment:
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[x] com.pixeloembypass" is in the list
Type in "cmd overlay disable com.pixeloembypass", and hit enter
Go into Settings->Apps, and uninstall "Pixel OEM Bypass"
Reboot the phone
This is amazing! Will try it here in about an hour and report back
Maybe tell these guys. They've been at it for a while. You might even get the bounty.
https://forum.xda-developers.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk
djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So? Come on dj! Lol
Sent from my Pixel 2 using XDA-Developers Legacy app
djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Click to expand...
Click to collapse
have more faith.. john mccain posted it after all
Hope it works
Sent from my Pixel 2 XL using Tapatalk
PresidentMcCain said:
Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
Click to expand...
Click to collapse
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Edit:
I downloaded it on my phone just to see what permissions is calls for and it doesn't open the file.
Didn't work for me. Any tips to try?
thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything
elliwigy said:
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything
Click to expand...
Click to collapse
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.
thompatry said:
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.
Click to expand...
Click to collapse
i understand lol.. when im lazy i just use a file browser n view as an archive lol
collinjames said:
Didn't work for me. Any tips to try?
Click to expand...
Click to collapse
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
That's okay, it's completely understandable. I agree - typically, you wouldn't want to install a random APK built by a stranger.
I wish I could test it myself, but both my Pixels are from the Google Store, and shelling out $650+ for a test device for a shot-in-the-dark experiment doesn't sound like very responsible spending.
Tried on my P2XL device and no luck..
nelsonTituaAa said:
Tried on my P2XL device and no luck..
Click to expand...
Click to collapse
Thanks for volunteering...have you gave this a try?
PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse
nelsonTituaAa said:
oops.. no haha.. will try again
Click to expand...
Click to collapse
PresidentMcCain said:
Thanks for volunteering...have you gave this a try?
Click to expand...
Click to collapse
tried it and still no luck.
PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse
Tried the command and doesn't seem like it disable android.auto_generated_rro__ on the overlay list.
tried this plus added recommendation and no luck. Verizon Pixel, 8.1
Anybody tried this on a Verizon Pixel 2? I'm willing to give it a shot, but would need a little more detail on the procedure if anyone is willing to help out.
Hello everyone, I need help. As English is not my native language, please forgive me for grammar and spelling errors if there is any. I am a Chinese student and our school uses a modded version of the Lenovo TB-X605M for teaching, which has restricted recovery (unable to mount any storage device) , no recovery mode (you have to scan a QR code provided by the service provider to enter) and no developer options (which means I cannot use ADB).
Now I’d like to use it for more purposes, so I decided to flash it through EDL mode (9008).
I read from online that this tablet uses the programmer file “prog_emmc_firehose_8953_ddr.mbn”, but I can’t find this file, and I also can’t find ROM for fastboot flashing (where I can extract the file).
Does anybody have the programmer file or the ROM for fastboot flashing? In addition, will it be OK to use programmer files for the same SoC but designed for other OEMs? I need your help. Please comment below. Thank you very much.
Did you try all these? https://github.com/bkerler/Loaders/tree/main/qualcomm/factory/msm8953
You might have a chance.
In any case, you need to start trying an EDL client (before you find a loader) to get the HWID and Hash.
Renate said:
Did you try all these? https://github.com/bkerler/Loaders/tree/main/qualcomm/factory/msm8953
You might have a chance.
In any case, you need to start trying an EDL client (before you find a loader) to get the HWID and Hash.
Click to expand...
Click to collapse
Thank you for replying.
No. I'd like to try it later as I don't want to risk too much.
For EDL Clients , will "QPST Tool" be OK? And does HWID and Hash do? I never read about them on Chinese Android forums. Anyway, I am going to check out if I can connect to it and try to find them in QPST Tool and write them down.
I've never mixed it up with any of those tools.
I keep it simple, just a bare EDL client.
With them it's not likely you can click a button and accidentally flash all the partitions on your device.
Finding a loader will be the toughest part. You should start now instead of waiting for something to flash.
Just querying for HWID/Hash has zero risk.
Trying out random Firehose loaders has a very small risk.
Renate said:
I've never mixed it up with any of those tools.
I keep it simple, just a bare EDL client.
With them it's not likely you can click a button and accidentally flash all the partitions on your device.
Finding a loader will be the toughest part. You should start now instead of waiting for something to flash.
Just querying for HWID/Hash has zero risk.
Trying out random Firehose loaders has a very small risk.
Click to expand...
Click to collapse
Thank you for your advice.
As I have said before, I have never heard of what is HWID and Hash and I don't know what they do. What I am going to do is to wipe userdata , and I have no idea whether I need to know about HWID and Hash to do this. I am going to try some loaders I found on a Chinese forum. I will start trying from some other Firehose files for the same SoC.
Moreover, I viewed the link in your first reply and found all these files are with the extension name .bin , instead of .mbn . Are they loaders? If they are , how should I use them?
I am just an ordinary student and I am not familiar with command lines. I seldom use it unless I can't do it with GUI.
The HWID tells your processor, the Hash tells you who signed it.
To get a loader to work the two must be compatible.
I am not responsible for the content on Chinese forums.