Related
i would like to know what everything means in htc's bootloader, whats fastboot? and whats does hboot mean, and what does everything thing in the bootloader mean and do? and why do we rename roms to PG05IMG... is that htc's way, like we like to use update.zip in custom recoverys.. thanks
anyone?????????
marcogiudice said:
anyone?????????
Click to expand...
Click to collapse
You're probably not getting a reply because these types of questions have been answered numerous times over the years - and people would probably rather ignore it than be a jerk by saying "ever heard of the search button??". Anyway... jsut Google "ADB for noobs", or "beginners guide to ADB" and you will probably find what you are looking for.
Lipmonger said:
You're probably not getting a reply because these types of questions have been answered numerous times over the years - and people would probably rather ignore it than be a jerk by saying "ever heard of the search button??". Anyway... jsut Google "ADB for noobs", or "beginners guide to ADB" and you will probably find what you are looking for.
Click to expand...
Click to collapse
i see what your saying i did google it before i posted and didnt find what i was looking for, i got adb setup correctly and have been using for it for 16 months but coming across htc bootloader it way different then motos or samsung's with some things in there that would help all the new tb users and should be posted and stickied or in the wiki thread
ok i found half my answer... this for other acquiring minds like me
Here's some (hopefully useful) information about the bootloader:
What's HBOOT?
It's immediately loaded when the phone is switched on. It's mostly responsible for checking and initialising the hardware and starting the phone's software, for flashing official software releases (RUUs via Fastboot), as well as a few other things. In some ways it's comparable to the BIOS on a PC.
How do I root HBOOT?
You can't, it makes no sense. It's a bootloader, not Android. It's like trying to play a DVD on your kettle.
What does upgrading HBOOT do?
It may add extra hardware support for new phones (e.g. SLCD displays) and may fix a few bugs. HTC doesn't release information about it.
What does downgrading HBOOT do?
The opposite. So, if you flash an SLCD phone with an old version of HBOOT that doesn't have the support, the screen won't work.
But rooting depends on HBOOT version?
It doesn't.
Why does upgrading HBOOT remove root?
It doesn't. When you flash an official update your ROM is replaced with an official one, which is why root is lost.
How do I change HBOOT version?
By installing an official RUU/update. There's no other way - the bootloader is protected by the phone's hardware security because a corrupt bootloader means a bricked phone with no way to recover. RUUs contain a version of the bootloader, which is automatically flashed.
Why do I need to downgrade HBOOT to root 0.92?
You don't. You had to downgrade Android because unrevoked3 couldn't root froyo. The new release can, so it works.
Why all the talk about HBOOT then?
Because it is confused with software release, which is the important part. An RUU won't work if the installed software is a higher version (e.g. 1.20.x won't work if you have 1.21.x), and people have mistaken that check for HBOOT version.
What about the xda 0.92 to 0.80 downgrade? It runs on froyo.
It's an engineering/test release from HTC that was leaked. It fakes its software version to 2.09.405.8 so it will run on froyo and downgrade the ROM, so long as you're not on a higher release than that. The process has nothing to do with HBOOT, but it does downgrade the bootloader to 0.80 as a side effect - and results in a dead screen on SLCD phones. It's generally a bad idea to use this hack.
Why would any of this matter?
Because instructions based only on HBOOT version are not reliable. They may not work, or may cause your phone to stop working.
OK NOW FOR FASTBOOT........
Fastboot
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images. It is disabled in the production G1 devices since USB support is disabled in the bootloader[1]. This can be changed if you get root on the device. See also [2]
Fastboot prerequisites
To be able to use fastboot, you need to be running either an ADP1 or the Engineering Bootloader on your G1.
If you are developing on a linux host, you may need to tweak UDEV to recognize the phone in fastboot mode. You may already have done this to get the phone recognized in Eclipse, but you need to do it again for fastboot, since fastboot uses a different device ID: 0bb4:0c01. The warning sign is that fastboot says "< waiting for device >" forever, even when you have the "FASTBOOT" message on the phone; if this happens, try adding the device ID 0bb4:0c01 to your UDEV configuration for Android.
For Opensuse 11.1, the following config file, in /etc/udev/rules.d/11-android.rules, seems to work:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c01", MODE="0666", OWNER="mylogname"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c02", MODE="0666", OWNER="mylogname"
NOTE: change "mylogname" to your Linux login ID. Also note that the product ID bit is optional (probably easier to leave it out), and you need to change "0bb4" to the vendor ID for your phone if it isn't made by HTC (whose vendor ID is 0bb4). You can find the vendor id using 'lsusb'. An alternative to this is just to run fastboot as root, using sudo.
Starting Fastboot
On the G1: To start fastboot, first get to the bootloader: turn off your phone and hold down the "camera" button while powering it back on. You will see a white screen with skateboarding bugdroids. If you just see the normal multicolored bootloader screen, you need to get the device side of fastboot working as noted above. Plug your phone into the usb and if you see "serial0" hit the "back" key. You should now see "fastboot" on the screen.
On the Samsung Galaxy: power down the phone, then long-press the two Call buttons. Beware that fastboot mode will continue to reboot the phone after ~30 seconds of inactivity.
Fastboot Binary
To make use of fastboot, you also need the fastboot program compiled for your host computer. If you have already built Android, you will have this file already. Its location should be:
<android source location>/out/host/{os}_{arch}/bin/fastboot
If you do not have fastboot built, you can either compile the Android source or try DarkriftX's precompiled fastboot (compiled on kubuntu x86)
Fastboot Commands
Here are the commands you can run on your host after fastboot has been started on a device connected via USB. This is a paste directly from the fastboot binary's "--help" command:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
Forcing fastboot to load on every boot
Developers who are creating new images to try out very often can remove their boot and recovery images which will force the phone to enter bootloader mode every time you boot. To fix this, you would reflash the boot and recovery images back allowing the phone to boot normally.
$ fastboot erase boot
$ fastboot erase recovery
NOW,
SO WHY DO WE CHANGE RUU.'S TO PG05IMG??????????
AND THE COUPLE OF OTHER OPTIONS DO IN BOOTLOADER?
THANK U!
I'm guessing it's because that's what it looks for. Kind of like the apply update.zip on stock android recovery. If you notice when you flash, it goes through PG05IMG.X with various file extensions trying to find it and gives a not found error before it finally gets to .zip
PJnc284 said:
I'm guessing it's because that's what it looks for. Kind of like the apply update.zip on stock android recovery. If you notice when you flash, it goes through PG05IMG.X with various file extensions trying to find it and gives a not found error before it finally gets to .zip
Click to expand...
Click to collapse
right, so ok then i was guessing right its like update.zip for stock recovery
thanks
Somewhat of an explanation of our signature checking bootloader can be found here
http://forum.xda-developers.com/showthread.php?t=1008210
Hi all,
So I spent like the whole afternoon tryin to unlock bootloader on my MB860 (rooted) with no luck. This is international version with 2.3.4 system updated OTA.
I tried to unlock bootloader with fastboot - no luck:
Code:
OEM Unlock is not implemented
So i tried flash unlocked sbf file (intl-fix-try1.sbf), still no luck:
Code:
Failed to boot 1
So, I've flashed whole sbf file: 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.20-release-keys-signed-NonEFIGSRetail-EU.sbf
Phone started and all was same as before this operation,
next - I tried another full sbf's:
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31-release-keys-signed-Retail-GB.sbf
1FF-olympus_latam-user-2.3.6-4.5.2A-51_OLL-17.8-111109-release-keys-signed-BellMobility-CA-GAS_NA_OLYMPUSGBCANADABELL_P019.sbf
On both - failed to boot 1
so in the end only sbf that actually allows me to boot my cell is 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.20-release-keys-signed-NonEFIGSRetail-EU.sbf
And the question is - how to get unlocked bootloader for this one?
You really should have searched and read up ahead of time. "Failed to boot XXX" is a perfectly normal and expected thing to happen when unlocking the BL. You shouldn't have messed with any more SBFs. You can still try running the fixer script as mentioned in that thread, hopefully you didn't mess it up too bad.
Thank you ravilov, but isn't this script only for ATT devices?
I am fairly certain it can be used on an international device as well.
Thanks, will try later on today, so what I'm lookin for is this thread:
http://forum.xda-developers.com/showthread.php?t=1182871
and option no.3 is what i should use from this script to have it fixed?
just for the records - the phone is working after i installed only sbf working, all setings and data were not affected, only will need to root it again
stingu said:
so what I'm lookin for is this thread:
http://forum.xda-developers.com/showthread.php?t=1182871
and option no.3 is what i should use from this script to have it fixed?
Click to expand...
Click to collapse
Yes.
stingu said:
just for the records - the phone is working after i installed only sbf working, all setings and data were not affected, only will need to root it again
Click to expand...
Click to collapse
Yeah, that's to be expected.
I think the worst case scenario would be that you won't be able to unlock, in which case you might be one of the unlucky people with the non-unlockable bootloader. If not, this script should help in unlocking your BL.
so, with the script and option number 3 i got the same thing:
Code:
(bootloader) OEM unlock is not implemented
OKAY [ -0.000s]
finished. total time: -0.000s
Or should i first flash small sbf and then use the script?
any other suggestions or am I stuck with soft 2.3.4?
You did flash the pudding/ihop SBF, right? If not, try doing that before you attempt to run oem unlock. If you did already... Well, I'm out of ideas then. I guess while waiting for someone else to chime in, you might as well start mentally preparing that you might indeed stay stuck with the stock firmware.
Well, made it unlocked, it was little bit tricky, so what I did:
-flashed IHOP
-got failed to boot 1 error message again - here, where i was not aware of - I pressed vol up and it switched to fastboot protocol support with boot error present
-did the script, fail to boot error was still there after reboot
-did those 2 points with flashboot application (whole instruction available here http://forum.xda-developers.com/showthread.php?t=1302423):
Code:
13.back in your command prompt window type "fastboot oem unlock" no quotes
14.You will now receive a warning along with a unique device ID
15.Type the following commands using your unique device ID (the numbers in the command prompt) in place of the ####•
fastboot oem unlock ####
fastboot reboot
Now its time to install CWM somehow...
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
I can see my device 'fastboot devices' I can see my device as fastboot device. But even if I enter 'fastboot flash' command, I see no respond, CMD freezes immediately so I can't flash any img to my device. For example when I use 'fastboot flash recovery twrp.img', CMD will freeze up. After disconnecting the device, CMD continues up and I see:
Code:
target didn't report max-download-size
sending 'recovery' (30324 KB)...
FAILED (command write failed (No error))
finished. total time: 0.017s
output.
EDIT: I asked these questions based upon the post above. We need more information. Many variants don't have full fastboot flash commands. For those that do, you may need to change ADB installations or use a different computer. AMD Ryzen doesn't work well with V30.
_________
What variant do you have? What firmware are you on?
Further questions... Have you already bootloader unlocked your phone? You have to unlock your bootloader before you can install TWRP custom recovery.
Instructions on how to do both are in the WTF thread.
Also if you've unlocked your bootloader, you know that many V30 variants don't have fastboot flash commands.
Which is why you need the WTF instructions to unlock your bootloader and install TWRP custom recovery.
Unless you have a T-Mobile H932, in which case there's an alternate set of instructions to install TWRP custom recovery... That's why we need to know what variant you have and what firmware you are on.
I think you need to read the Root Sticky Guide. Start with Post #1:
ROOT YOUR V30!
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Heroata said:
I can see my device 'fastboot devices' I can see my device as fastboot device. But even if I enter 'fastboot flash' command, I see no respond, CMD freezes immediately so I can't flash any img to my device. For example when I use 'fastboot flash recovery twrp.img', CMD will freeze up. After disconnecting the device, CMD continues up and I see:
output.
Click to expand...
Click to collapse
Sounds like you did NO Google searching and even failed to look at XDA itself to see how to root.
Also I bet you have a T-Mobile V30.
Basic Google search.
XDA root LG V30
That will bring up WTF and LAFsploit. Would have saved you a post and got what you needed 100X faster...
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Sounds like you did NO Google searching and even failed to look at XDA itself to see how to root.
Also I bet you have a T-Mobile V30.
Basic Google search.
XDA root LG V30
That will bring up WTF and LAFsploit. Would have saved you a post and got what you needed 100X faster...
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
Just searched his posts. He's not a newbie -- posted months ago -- and he has an H930 variant:
Heroata said:
I have H930G Turkey converted to H930.
---------- Post added at 04:13 PM ---------- Previous post was at 03:37 PM ----------
Which version should I use? @ChazzMatt
Click to expand...
Click to collapse
Heroata said:
Not problem. Eventually ChazzMatt saved my day.
Click to expand...
Click to collapse
So my suggestion about reading the Root Sticky Guide (which is normally good advice for everyone!) doesn't apply to him.
Unless he now has another V30 and is trying to root that one? In which case maybe he has a T-mobile H932?
ChazzMatt said:
EDIT: I asked these questions based upon the post above. We need more information. Many variants don't have full fastboot flash commands. For those that do, you may need to change ADB installations or use a different computer. AMD doesn't work well with V30.
_________
What variant do you have? What firmware are you on?
Further questions... Have you already bootloader unlocked your phone? You have to unlock your bootloader before you can install TWRP custom recovery.
Instructions on how to do both are in the WTF thread.
Also if you've unlocked your bootloader, you know that many V30 variants don't have fastboot flash commands.
Which is why you need the WTF instructions to unlock your bootloader and install TWRP custom recovery.
Unless you have a T-Mobile H932, in which case there's an alternate set of instructions to install TWRP custom recovery... That's why we need to know what variant you have and what firmware you are on.
I think you need to read the Root Sticky Guide. Start with Post #1:
ROOT YOUR V30!
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Click to expand...
Click to collapse
As you found I have H930G turned to H930. I flashed a fresh new Pie KDZ with REFURBISH option. So had to refollow WTF steps. But like in almost every time, new ADB environment occured some problems. This problem occured in 2 modern laptops. Then I tried on an old laptop and problem is just a bit decreased like sometimes it's not freezing but having write error. Then I figured out that if I plug in and out quickly then plug in persistent, it will work. I don't have any idea why i can solve it by that way but I wanted to share my exact experience.
Heroata said:
As you found I have H930G turned to H930.
Click to expand...
Click to collapse
Such a weird problem. Have you tried to use newer (or older) adb/fastboot binary? I had similar issue with my older xiaomy phone, I thought it was usb port or cable issue, then I tried to replace adb/fastboot binary with those from MiFlash app folder. Now it works as usualy does.
Are you by any chance using Ryzen CPU and using 1903 version of Windows 10?