Title nearly says it all. I have a full set of backups for all the partitions on this phone. I overwrote the CID partition with a backup from a different XT1526.
The result of overwriting the CID with the wrong phone's CID is that it immediately only boots into fastboot. I cannot get into recovery or any other setting except "BARCODES". The bootloader now shows locked as well.
fastboot getvar all returns (extra info deleted):
cid: 0xDEAD
channelid: 0xDEAD
ro.build.fingerprint[0]: motorola/surnia_boost/surnia_cdma:
ro.build.fingerprint[1]: 5.1/LPI23.29-18-S.12/39:user/relea
ro.build.fingerprint[2]: se-keys
I have the CID partition ready to reload, however the bootloader is now locked so I cannot do so.
In the process of trying to get back to a semi-working state I have:
- Attempted to re-unlock the bootloader - but the phone returns "fastboot oem lock currently disabled"
- Issued the command to relock the bootloader (it was already locked from the result of CID corruption)
- attempted to use RSD lite to flash SURNIA_BOOST_5.1_LPI23.29-18-S.2_cid9_subsidy-DEFAULT_CFC.xml - but that fails
Is there anything that I can try?
Thank you,
Nathan
I am tempted to issue the command "fastboot erase all". I have seen on other devices where that allowed the device to boot, but it turns your IMEI to 0. I do have the backups to the partitions so if I can get this to boot and I can still unlock the bootloader I think I can recover from the IMEI issue. If I could get to TWRP recovery, that could prove to be helpful, however I'm not sure if I attempted to overwrite the recovery partition with the stock version.
I will hold off on the erase all command for now though.
---
I ended up performing the fastboot erase all command and that didn't touch the CID folder. I still cannot boot and the phone still shows the correct IMEI in the barcodes section of the bootloader.
The 'fastboot erase all' command performed the following:
(bootloader) erasing modemst1 ...
(bootloader) erasing modemst2 ...
(bootloader) erasing hob ...
(bootloader) erasing dhob ...
(bootloader) erasing fsg ...
(bootloader) erasing fsc ...
(bootloader) erasing clogo ...
(bootloader) erasing keystore ...
(bootloader) erasing carrier ...
(bootloader) erasing cache ...
(bootloader) erasing userdata ...
Are there any programs that may allow me access wipe out and recover my CID partition from my dd backup?
My device is failing booting with the following in the bootloader logs:
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
I have also downloaded XT1526_SURNIA_BOOST_5.1_LPI23.29-18-S.12_cid9_subsidy-DEFAULT_CFC.xml and that flashes better, but it still fails when attempting to flash the system with - (bootloader) Invalid signed image; (bootloader) Preflash validation failed
Any help is appreciated.
I wanted to write one thing that seems interesting,
When I attempted to re-unlock this phone by getting the unlock code and submitting it to motorola, the emailed unlock code that they sent me is the same code as the device that I copied the CID partition from.
I have attempted to unlock with the unlock code that was previously used and also the new one, neither work.
NathanJ988 said:
I wanted to write one thing that seems interesting,
When I attempted to re-unlock this phone by getting the unlock code and submitting it to motorola, the emailed unlock code that they sent me is the same code as the device that I copied the CID partition from.
I have attempted to unlock with the unlock code that was previously used and also the new one, neither work.
Click to expand...
Click to collapse
I can think of one thing for as writing the imei over. It's a program called spc something. Google it that's all I can think of
Sent from my XT1526 using XDA-Developers mobile app
You screwed up your EFS partition. Since the imei is 0 you have to ability to write it back. There are plenty of tools you can use, like DFS Tools or QPST is the best one. I can't say much else about since, screwing with your imei is illegal in most countries, therefore forbidden on XDA.
sirhc said:
You screwed up your EFS partition. Since the imei is 0 you have to ability to write it back. There are plenty of tools you can use, like DFS Tools or QPST is the best one. I can't say much else about since, screwing with your imei is illegal in most countries, therefore forbidden on XDA.
Click to expand...
Click to collapse
Please don't spread false info. Trying to return the IMEI to what it was from the factory is not illegal in the US and I really doubt it is illegal anywhere. That simply is repairing a phone you legally own. There is nothing illegal or wrong with repairing a phone you legally own.
Trying to CHANGE THE IMEI to something other than it was from the factory may present an issue but I have yet to see a US law that says it is illegal UNLESS YOU ARE TRYING TO STEAL SOMEONE'S CELL PHONE SERVICE OR YOU DON'T OWN THE IMEI YOU CHANGED YOUR IMEI TO.
JulesJam said:
Please don't spread false info. Trying to return the IMEI to what it was from the factory is not illegal in the US and I really doubt it is illegal anywhere. That simply is repairing a phone you legally own. There is nothing illegal or wrong with repairing a phone you legally own.
Trying to CHANGE THE IMEI to something other than it was from the factory may present an issue but I have yet to see a US law that says it is illegal UNLESS YOU ARE TRYING TO STEAL SOMEONE'S CELL PHONE SERVICE OR YOU DON'T OWN THE IMEI YOU CHANGED YOUR IMEI TO.
Click to expand...
Click to collapse
Tampering with the imei period is illegal. If there's an issue with your partitions, manufacturers recommend you send your device to them to fix, not DIY. I never said that returning it to it's original state was illegal, which is why I gave names of the tools that can do the job. I also stated this kind of talk on XDA isn't permitted. Because it isn't. Instead of whining about what's legal or what's not, go and use the resources provided to you, otherwise this conversation is done
Sent from my XT1526 using Tapatalk
Thanks for the possible fixes, I will look into those. I don't think I lost my IMEI though, it is still showing up when I perform a 'fastboot getvar all' command. It is displayed in the barcode section, too.
I am certain however that I overwrote the 'cid' partition.
I found someone with an XT1032 - Moto G - that had the same issue and was able to recover the original cid partition. http://forum.xda-developers.com/showpost.php?p=63494655&postcount=16
My phone only boots into the bootloader. I am unable to boot into BP tools or any other option. I don't think I will be able to use QPST or the DFS because the guides I have seen show booting using the BP option of the bootloader.
I tried qpst 2.7.422 but it does not show my device. The only device I have in windows is "Motorola ADB interface".
sirhc said:
Tampering with the imei period is illegal.
Click to expand...
Click to collapse
First - what do you mean by tampering? If you mean restoring it to what it was, then YOU ARE WRONG AND DON'T KNOW WHAT YOU ARE TALKING ABOUT. STOP SPREADING FALSEHOODS AND EDUCATE YOURSELF.
If you mean what I said CHANGING the IMEI, cite the law. Otherwise you are just making things up that you know nothing about.
Cite the law or STFU.
JulesJam said:
First - what do you mean by tampering? If you mean restoring it to what it was, then YOU ARE WRONG AND DON'T KNOW WHAT YOU ARE TALKING ABOUT. STOP SPREADING FALSEHOODS AND EDUCATE YOURSELF.
If you mean what I said CHANGING the IMEI, cite the law. Otherwise you are just making things up that you know nothing about.
Cite the law or STFU.
Click to expand...
Click to collapse
Let's calm down there buddy!!!! No need for all of that!!!!
Sent from my XT1526 using XDA-Developers mobile app
903tex said:
Let's calm down there buddy!!!! No need for all of that!!!!
Click to expand...
Click to collapse
I think there is and you aren't the boss of me.
Hi
Is there anybody to help me. I have bricked my moto g3 2015. First i ran erase all and then override cid. It was originally XT1550 but now its showing XT1547 .. cid: 0xDEAD , bootloader locked, unlocked: not supported
Related
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
Problem:
This is the ultimate warning, and you likely don’t want to see this message show up on your screen. Shall this appear, it would mean your device is not safe to use, not trusted and/r corrupted. The OS could still work, but there’s high chances you will encounter performance and security issues.
Consequence:
Before your device begins to start it will be shown:
Android system
There’s an internal problem with your device. Contact your manufacturer for details nexus 6p
Also:
The camera may be no longer properly work
Fixxed:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
mfastboot flash system system.img
reboot bootloader
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastboot reboot-bootloader
fastboot flash vendor vendor.img
Important:
fastboot flashing lock_critical
Enjoy!
@tlip
A couple of notes. You should never advise anyone to flash the userdata.img, it'll result in the minimum commercially available storage size (32gb) being allocated to the device regardless of the actual storage size. So flashing userdata is only compatible with 32gb devices. The correct way to wipe/format the userdata is with this command:
Code:
fastboot format userdata
Also, bootloader reboots are only required after flashing the bootloader and the radio, so the sequence should be like this:
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot format userdata
fastboot reboot
And one more thing, you need to take more care when typing these instructions, you made a few errors, I'll highlight them:
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
[Color=red]m[/color]fastboot flash system system.img [Color=blue](extra m at beginning of command)[/color]
[Color=red]reboot bootloader[/color] [Color=blue](missing "fastboot" prefix, and hyphen between reboot and bootloader (fastboot reboot-bootloader))[/color]
fastboot flash cache cache.img
[Color=red]fastboot flash userdata userdata.img[/color] [color=blue](incorrect command as outlined above)[/color]
[Color=red]fastboot reboot-bootloader[/color] [Color=blue](unnecessary)[/color]
[Color=red]fastboot reboot-bootloader[/color] [Color=blue](another one?)[/color]
fastboot flash vendor vendor.img
I have that message when rebooting. Is this something I should be concerned about? My ignorance had me believing this was a standard screen for all unlocked bootloaders.
sandfreak said:
I have that message when rebooting. Is this something I should be concerned about? My ignorance had me believing this was a standard screen for all unlocked bootloaders.
Click to expand...
Click to collapse
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
EDIT: This info only applies for "Bootloader MAY BE Corrupt" and not "IS Corrupt". Different situation from the OP
Thanked @Heisenberg
Please OP, you give instructions that you expect people to follow and if they type in the wrong info could be fatal...
Seriously, this thread needs closed asap. All the above info( besides Heisenberg) is careless in itself, let alone posting it for others. Stop....just stop. Smh
Heisenberg said:
@tlip
A couple of notes. You should never advise anyone to flash the userdata.img, it'll result in the minimum commercially available storage size (32gb) being allocated to the device regardless of the actual storage size. So flashing userdata is only compatible with 32gb devices. The correct way to wipe/format the userdata is with this command:
Click to expand...
Click to collapse
I have for sure made this mistake before... One lesson learned the hard way
Dissmeister said:
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
Click to expand...
Click to collapse
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
CNLiberal said:
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
Click to expand...
Click to collapse
That's exactly right, locking the bootloader means you can't flash anything to the device.
CNLiberal said:
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
Click to expand...
Click to collapse
Your post made me google this and I did find some people who did have issues like that, though they mention they cant unlock again. If this is what you're talking about, I'd say its a device specific issue; technically as far as Nexus (or correct flashing protocol) is concerned, you should be able to unlock and re-lock as you see fit. As Heisenberg mentioned, you cant flash anything on a locked b/l in the first place.
Personally I've never seen a reason to relock b/l after unlock but it depends on your circumstances.
Dissmeister said:
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
Click to expand...
Click to collapse
Actually if it says your bootloader may be corrupt which is normal. If it says your bootloader is corrupt that's bad. It can say Two different things. He said the second one
dontbeweakvato said:
Actually if it says your bootloader may be corrupt which is normal. If it says your bootloader is corrupt that's bad. It can say Two different things. He said the second one
Click to expand...
Click to collapse
That is one hell of a silly mistake. You're right, I apologize for not seeing that earlier. Will fix my previous reply so others dont get the wrong info from it. Thanks for that :good:
Dissmeister said:
Your post made me google this and I did find some people who did have issues like that, though they mention they cant unlock again. If this is what you're talking about, I'd say its a device specific issue; technically as far as Nexus (or correct flashing protocol) is concerned, you should be able to unlock and re-lock as you see fit. As Heisenberg mentioned, you cant flash anything on a locked b/l in the first place.
Personally I've never seen a reason to relock b/l after unlock but it depends on your circumstances.
Click to expand...
Click to collapse
The way I understood it, after I re-lock then need to unlock again, the phone will force a wipe. The old app Unlock Bootloder would lock and unlock in Android. You wouldn't have to reboot. I guess the developer believes that the new 6P can't perform this same function due to the nature of new locking/unlocking.
Hi Heisenberg,
as being rather new to the topic of unlocking and stuff that means, that I have to follow this (your) sequence for not running into that issue?
Does this hold true also for already having this problem, though?
Cheers, Rovaine
Rovaine said:
Hi Heisenberg,
as being rather new to the topic of unlocking and stuff that means, that I have to follow this (your) sequence for not running into that issue?
Does this hold true also for already having this problem, though?
Cheers, Rovaine
Click to expand...
Click to collapse
This "guide" is very poorly written, don't follow the instructions here. If you need instructions you can visit my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
As long as you're careful and follow my instructions properly you shouldn't haven't this problem.
Heisenberg said:
This "guide" is very poorly written, don't follow the instructions here. If you need instructions you can visit my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
As long as you're careful and follow my instructions properly you shouldn't haven't this problem.
Click to expand...
Click to collapse
Actually, I've tried to follow your guide to the point, but did -obviously- something wrong, hence this issue.
You've got any advice for starting all over -propperly- for getting rid of this issue?
I had this issue too after having "dirty flashed" Android 6.0.1 over Android 6.0.
I flashed system.img and boot.img, as usual through fastboot and never had any problems on "older" devices.
On my Nexus 6P I got this error too and the camera did not work. Having checked the logs I found the error.
You need to flash vendor.img too in order to fix it. You don´t have to relock your bootloader.
Gorgtech said:
I had this issue too after having "dirty flashed" Android 6.0.1 over Android 6.0.
I flashed system.img and boot.img, as usual through fastboot and never had any problems on "older" devices.
On my Nexus 6P I got this error too and the camera did not work. Having checked the logs I found the error.
You need to flash vendor.img too in order to fix it. You don´t have to relock your bootloader.
Click to expand...
Click to collapse
Just for getting it straight...
Initial situation:
Rooted device, latest Cyanoge installed, showing the described issue
How to solve:
Get angler-xxxxxx-factory-xxxxxxxx, unzip ...
"fastboot flash vendor C:\angler\images\vendor.img"
Gratulation issue solved?
Or do I have to get back to a certain state, like factory image fully restored or alike, of my device?
Exactly, you need the latest Factory Image for the Nexus 6P. Extract all content and only flash the vendor.img through fastboot.
Rovaine said:
Just for getting it straight...
Initial situation:
Rooted device, latest Cyanoge installed, showing the described issue
How to solve:
Get angler-xxxxxx-factory-xxxxxxxx, unzip ...
"fastboot flash vendor C:\angler\images\vendor.img"
Gratulation issue solved?
Or do I have to get back to a certain state, like factory image fully restored or alike, of my device?
Click to expand...
Click to collapse
Rovaine said:
Actually, I've tried to follow your guide to the point, but did -obviously- something wrong, hence this issue.
You've got any advice for starting all over -propperly- for getting rid of this issue?
Click to expand...
Click to collapse
Flash the factory images, instructions are in my guide.
WARNING: This ABSOLUTELY HAS THE POTENTIAL TO BRICK YOUR DEVICE. Please tread carefully. I am NOT responsible if you damage your device. This can be very dangerous, PLEASE do not do this unless you know you absolutely want/need to. You have been warned.
Important information:
This is for US Model x727 running the 5.8.019s version of the US ROM. If you flashed the chinese ROM, this will not help you at all.
Afterwards you should still have US ROM and features at version 5.8.019s
Your device should be persistently unlocked after successfully performing this procedure.
This zip file replaces the aboot and xbl (basically, the bootloader) with the versions from the LE_ZL1_LEX720-CN-FN-WAXCNFN5801811021S-5.8.018S.zip ROM file. I can't guarantee this will work for everyone (or even anyone). I can only tell you that it worked for me.
NOTE: If this makes you happy, please consider donating by clicking on the "donate to me" button under my handle at the left. I am broke and trying to recoup the cost of this device
Requirements (what I *think* you'll need):
US Le Pro3 running the US ROM updated to 5.8.019s OTA (If you're running the chinese ROM because you were impatient and didn't want to wait for the grownups to work out a procedure, this will not help you).
TWRP Image (I used the chinese one)
Zip File listed below
Somewhere to put the zip file for flashing if you don't want to have to wipe your device (I've heard of people successfully using an OTG storage device? I just wiped mine so you're on your own to figure this out)
This is the procedure I followed:
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
Run "fastboot oem device-info" to verify unlock status
Run "fastboot boot recovery_twrp.img" (or whatever the twrp image filename is on your computer) to boot up to TWRP
NOTE: If you don't read chinese and you haven't done this before, you'll be presented with a screen in chinese with two buttons next to each other and a swipe underneath them. THE BUTTON ON THE RIGHT lets you change the language. Press it, thank me later.
If you have an OTG device with the bootloader replacement zip on it, skip this step. If you have to use your device's storage, and your storage is encrypted, you'll have to wipe all the data. Go to Wipe, choose Format Data and follow the instructions. YOU WILL LOSE EVERYTHING ON YOUR DEVICE. Be warned.
If you wiped your data partition, you'll need to push the zip file to the storage. Run "adb push x727-5.8.019s_bootloader-unlock.zip /sdcard/"
Now press "Install", select the x727-5.8.019s_bootloader-unlock.zip file and flash it.
Reboot back to your system. If you wiped data, your device will now proceed to re-initialize itself as if from the factory
Your system should still be running the full US ROM, but it should also now be persistently unlocked. Don't do any updates, your device likely won't remain unlocked if you run an update. And there's no guarantee you'll be able to re-unlock after doing so.
NOTE: If you flash TWRP to the recovery partition, the OS will likely reset it to the factory recovery UNLESS YOU ROOT THE SYSTEM. Your device is still unlocked, the recovery was just restored by the system, don't freak out. Be warned. I don't have time to answer stupid questions, neither does anyone else.
Download: x727-5.8.019s_bootloader-unlock.zip
MD5: 8eff2a1e29c9959259e7db1dd5c74a67
Special thanks to @hondajohn88 for taking the leap and experimenting with the chinese rom on his own device.
Reserved
Is it possible to have the chinese bands with the US rom on the x727? because I'm bringing the phone to asia and i need band 41
How about pulling us the modem image from the US version now since you have it unlocked. The Grossoshop is great except a few of us have flashed this over the CN ROM and the CN modem seems to be lacking a few bands.
awesome job! i knew we'd figure out root/unlock eventually. wonder if Le Eco accidently let this happen or did it on purpose so they can have plausible deniability
edit - did you also by chance backup the stock bootloaders?
Kick ass man!!! I get my phone next week when my dad comes down to visit me in Colombia. Can't wait to do this once it arrives
I was happy till I saw .. "Run "fastboot oem unlock-go" to unlock your device temporarily"
for some reason I don't get it to work like you guys do. it will give the same error as with the original firmware. Ill try but I doubt it will work for me
Its going to be pointless for me to try .. I don't understand why you guy can have temp bootloader while I cant
And yes, I am on 19s
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
C:\adb>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.091s]
finished. total time: 0.094s
bulls4ever said:
I was happy till I saw .. "Run "fastboot oem unlock-go" to unlock your device temporarily"
for some reason I don't get it to work like you guys do. it will give the same error as with the original firmware. Ill try but I doubt it will work for me
Click to expand...
Click to collapse
Yeah I absolutely have tried like 6 different adb/fastboot's and nothing works for me either.
Not my first rodeo with annoying Windows drivers too.
I reset it to factory.. downloaded the 19s and upgraded again .. nothing will make it to allow oem unlock
If i try to run "fastboot boot recovery_twrp.img" will it brick the phone or just wont work?
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
can you upload the "ADB/Fasboot tools" you used? maybe that is the problem but i doubt it
Just to make sure, you guys are checking "OEM Unlocking" in developer options, correct?
bulls4ever said:
I reset it to factory.. downloaded the 19s and upgraded again .. nothing will make it to allow oem unlock
If i try to run "fastboot boot recovery_twrp.img" will it brick the phone or just wont work?
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
can you upload the "ADB/Fasboot tools" you used? maybe that is the problem but i doubt it
Click to expand...
Click to collapse
It won't be the fix. If adb/fastboot recognize the devices, changing versions shouldn't work. Sorry :-/ That being said, I suppose there's no hurt in trying. FWIW this is what worked for me on my Windows 7 box:
Code:
C:\Users\dr4stic>adb version
Android Debug Bridge version 1.0.36
Revision 19394af606f6-android
C:\Users\dr4stic>fastboot --version
fastboot version 19394af606f6-android
I got them by installing the Android SDK. The SDK manager indicates that my "Android SDK Platform Tools" (that the tools come from) are at version 24.0.4 and I can upgrade to revision 25.
This may be a dumb question, but I'm assuming you've set the "allow device bootloader unlocking" (or whatever it's called) in the developer settings... right?
ExTREmE99 said:
awesome job! i knew we'd figure out root/unlock eventually. wonder if Le Eco accidently let this happen or did it on purpose so they can have plausible deniability
edit - did you also by chance backup the stock bootloaders?
Click to expand...
Click to collapse
I did, but I didn't really need to. They're in the 5.8.019s OTA. They're the emmc_appsboot.mbn and xbl.elf files in the firmware-updates folder.
dr4stic said:
It won't be the fix. If adb/fastboot recognize the devices, it won't work. Sorry :-/
This may be a dumb question, but I'm assuming you've set the "allow device bootloader unlocking" (or whatever it's called) in the developer settings... right?
Click to expand...
Click to collapse
yes, i did
ITs bizarre that some can get the tem unlock and some don't.
Like I said . I reset to fabric, re-updated using the 19s that is in the forum. Enabled developer tools. Enabled OEM unlock and USB dev. I tried to mimic a brand new update to 19s ...
I wonder if it actually enable OEM but adb/fastboot wont say it is unlocked? unlikely but .. hey.. I'm desperate at this point lol
---------- Post added at 06:36 PM ---------- Previous post was at 06:33 PM ----------
My version is 1.0.32 ...
---------- Post added at 06:39 PM ---------- Previous post was at 06:36 PM ----------
no donuts
C:\adb>adb version
Android Debug Bridge version 1.0.36
Revision e02fe72a18c3-android
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.015s
C:\adb>
bulls4ever said:
yes, i did
ITs bizarre that some can get the tem unlock and some don't.
Like I said . I reset to fabric, re-updated using the 19s that is in the forum. Enabled developer tools. Enabled OEM unlock and USB dev. I tried to mimic a brand new update to 19s ...
I wonder if it actually enable OEM but adb/fastboot wont say it is unlocked? unlikely but .. hey.. I'm desperate at this point lol
---------- Post added at 06:36 PM ---------- Previous post was at 06:33 PM ----------
My version is 1.0.32 ...
Click to expand...
Click to collapse
Who knows, maybe the lower version is misinterpreting the output. If you're really determined you can try upgrading your version of adb/fastboot. Like I said I use the sdk from google, so it's as updated as it'll get. Anything else is just someone repackaging what already exists.
After you "fastboot oem unlock-go" try booting the twrp image anyway. I doubt it'll work if it's misinterpreting the response (it would have be interpret it properly to send the boot image to the device for booting), but who knows. Maybe it will work anyway.
Saikou0taku said:
Just to make sure, you guys are checking "OEM Unlocking" in developer options, correct?
Click to expand...
Click to collapse
yes
Going to try the Android SDK shortly
bulls4ever said:
yes, i did
ITs bizarre that some can get the tem unlock and some don't.
Like I said . I reset to fabric, re-updated using the 19s that is in the forum. Enabled developer tools. Enabled OEM unlock and USB dev. I tried to mimic a brand new update to 19s ...
I wonder if it actually enable OEM but adb/fastboot wont say it is unlocked? unlikely but .. hey.. I'm desperate at this point lol
Click to expand...
Click to collapse
You know... if worse comes to worst and you desperately want to unlock, couldn't you just try installing the Chinese ROM listed by some of the other users? I don't know how that ROM would react to your phone being that it isn't unlocking at all, maybe it'll brick it, maybe it won't (I doubt it). The consequences of that would completely be of your own undertaking...
That being said, the chinese rom people talk about is signed by LeEco and thus would likely install without question. And it's bootloader would then be unlocked. We could make plans to return you to stock US firmwares at a later date. I suspect we're gonna have to get a solution together for that at some point anyway... My only suggestion would be that you do it while coming from the 5.8.019s (which you already are) because that's where my firmwares are coming from.
Android SDK will give the same results as expected ...
Not that desperate ... I'm desperate to keep LeEco cause I like it. But do not want to go to Chinese way as it will lose bands and currently we don't even have ways to come back to US rom.
My "desperation" is that the deadline to decide if I will keep the phone or return is approaching.
What I need to figure it out is why some have tem unlock and some don't. My windows is 10. Maybe windows issue (I doubt it)? will try windows 7 later
bulls4ever said:
Android SDK will give the same results as expected ...
Not that desperate ... I'm desperate to keep LeEco cause I like it. But do not want to go to Chinese way as it will lose bands and currently we don't even have ways to come back to US rom.
My "desperation" is that the deadline to decide if I will keep the phone or return is approaching.
What I need to figure it out is why some have tem unlock and some don't. My windows is 10. Maybe windows issue (I doubt it)? will try windows 7 later
Click to expand...
Click to collapse
No, windows should have nothing to do with it. I'm assembling a "return to US" rom as we speak... but I won't feel comfortable about releasing it until it's been tested. And also I need lunch...
dr4stic said:
No, windows should have nothing to do with it. I'm assembling a "return to US" rom as we speak... but I won't feel comfortable about releasing it until it's been tested. And also I need lunch...
Click to expand...
Click to collapse
I'm going to use this method later today and can report back any issues. By the way, you are the man!
Is super super flash able after bootloader is unlocked?
yeah .. windows wasn't the issue. I tested on Ubuntu and it was a no go.
Is it possible that LeEco released like 2 versions being the first a mistake of leaving the bootloader sort of unlocked and then a second with it locked?
I am running out of reasons for not being able to unlock it while some are able to
Hey Guys,
I got a few LG G5 h850 and was thinking to create and maintain a "Master-ROM" (LOS14.1, Magisk 17.2 ...) with a" Mother Device" so I can back it up with NanDroid/by TWRP and TiBackup, and flash it to all Children devices after.
While trying to restore the TWRP Backup to the first phone, I was an idiot and marked all partitions. Guess I should have left out some:
After restoring the Backup and Booting I get the "Your device is corrupted" Error.
With a Fastboot Linux Host machine I tried flashing TWRP again, but the device is locked against flashing..
The first unlocked bootloader is locked again:
When I tried to flash the unlock.bin again, I discovered that the IMEI of the "Mother-ROM Device" got implemented,
causing a difference in IMEI vs. OEM ID, causing the unlock.bin not to work.
I ****ed up.
I researched and tried "$ fastboot oem writeimei 123456789012347" with Linux ADB shell, but that command is only for a modified fastboot libary.
1. Question:
Well - anybody have any idea how to write the original IMEI into the device again, so I can fastboot flash unlock, fastboot flash recovery it again?
In the meantime I will try if the LGs website will generate me another unlock.bin with the "wrong" IMEI and correct OEM ID,
so I might be able to unlock it again - and than change the IMEI maybe again for the correct one, and unlock it again with the "correct" unlock.bin.
Click to expand...
Click to collapse
LGs Website is smart enaugh. Nope...
2. Question:
So, if I am allowed to ask in here aswell while I do my research: How to skip my IMEI Issue in the next time? I guess not "restoring" the Mothers-EFS Partition to a Childrens Device should be it - or is the information located in another Partition?
Click to expand...
Click to collapse
Wow. I bricked a second device. Have tried not to Flash Recovery and EFS. Seems like it´s located on Misc or Boot or something like this ...
Damn it.
Anybody knows something more precise?
Thanks
Would going into 9008 and wiping the boot partitions suffice? I'm asking because I'm taking advantage of my warranty before it expires and already have approval for a new device for saying mine will not boot....not sure if they would do any digging.. The rep said they ship my new device before mine even gets there..
To erase boot partition
Code:
fastboot erase boot
Thank you sir, you dont think this would leave anything in the logs? or do they even go that far
jwoegerbauer said:
To erase boot partition
Code:
fastboot erase boot
Click to expand...
Click to collapse
I research in security of android devices and their tamper-resistance. I've seen that in Pixel devices, you can locally unlock your bootloader by enabling OEM unlocking and then executing fastboot flashing unlock command to unlock the bootloader which means unlike other OEMs, Pixel doesn't rely on unlock code. I think OnePlus is another device which does the same.
When fastboot flashing unlock command is executed, bootloader must be storing its unlocked state somewhere to keep it persistent across boot. Wherever Pixel stores its unlock state, how that partition is protected from physical tampering using UFS flash chip programmer?
If UFS flash chip programmer can modify bootloader state by directly tampering with the partition that stores it, how Pixel is safe from physical theft and data compromise? A thief could be able to modify the state without the data getting erased. The data is erased only when you ask bootloader to set unlock state using fastboot. Once the thief modifies the state using the said programmer, he could be able to flash custom recovery to erase screen lock code.
This whole setup depends upon where blootloader state is stored and how it is protected against physical flash chip tampering.
The location of tamper flag simply is a byte in a specific file which can be queried by means of Fastboot.
My guess is that this file is stored in Android's /misc and/or /param partition ,
jwoegerbauer said:
The location of tamper flag simply is a byte in a specific file which can be queried by means of Fastboot.
My guess is that this file is stored in Android's /misc and/or /param partition ,
Click to expand...
Click to collapse
What prevents a thief to modify this tamper flag using UFS flash chip programmer in order to unlock the bootloader of a stolen device and then reuse the device as his own?
Can not mentally comprehend what locking/unlocking an Android device's bootloader has to do with device's ownership. Sorry for this.
jwoegerbauer said:
Can not mentally comprehend what locking/unlocking an Android device's bootloader has to do with device's ownership. Sorry for this.
Click to expand...
Click to collapse
What I mean is that if an attacker is able to unlock bootloader, he can reuse the stolen device as his own. Under locked bootloader condition, factory reset protection prevents attacker to reuse the stolen device.