Related
Hi,
Sorry for posting in this as I couldnt find any thread for S10.
I have a S10 Pro with the following version of ROM installed.
Android 3.2
Build Version : 201107271412 (This is a strange as I couldnt find this in any other....)
Kernel Verrsion : 2.6.36.3-00055-gdb0a63d
Is it possible to update it to 569 or any custom ROM?
Thanks and Regards,
manakun
Well you listed everything but the actual useful version info: what is the oem version?
Do you understand how to use nvflash?
As you're the first one with that rom: there's no way to restore to it after you flash something over it, I'd recommend making a backup of it.
It might be possible to update to 568/9 with the 546 recovery, if you are willing to make a backup of your rom i'll give you the instructions to update.
You'll need nvflash regardless though, I dont know offhand if <whatver rom version you have>'s rec will allow you to update even.
TheManii said:
Well you listed everything but the actual useful version info: what is the oem version?
Do you understand how to use nvflash?
As you're the first one with that rom: there's no way to restore to it after you flash something over it, I'd recommend making a backup of it.
It might be possible to update to 568/9 with the 546 recovery, if you are willing to make a backup of your rom i'll give you the instructions to update.
You'll need nvflash regardless though, I dont know offhand if <whatver rom version you have>'s rec will allow you to update even.
Click to expand...
Click to collapse
Thanks for you prompt reply.
The OEM Version is GALLO1A155111
I havent used nvFlash but I shouldnt have problem using it. Will make a backup. I dont mind if it cannot be restored.
Awaiting your instructions.
Thanks,
manakun
I am yet to update S10.
Help appreciated.
Things you'll need to know:
How to use the command line
How to install drivers on windows
Windows vista or newer
Download usbNvidiaBootdriver.zip
Download NVflash.zip
Download 568 bootloader.bin
Put Device into APX mode
Hold down power and reset button
Install apx driver
Extract nvflash
Boot device into APX mode
Command to do so: "nvflash --bl <path to bootloader.bin> --go"
<path to bootloader.bin> is whereever you saved bootloader.bin to
Begin dumping each partition
Command to do so: "nvflash -r --read <N> <filename>"
<N>: number of partition to dump
Partition List - XDA wiki
Partitions we need to dump 551: 2, 3, 4, 6, 7, 8, 11
Filename is whatever you wish to name file, recommended to name them after their partition number, eg p2, p3, p4, etc
After you have it dumped please 7zip and upload somewhere
Updating to a different rom uses similar steps if you cannot use "check for updates" from inside rom
If you do not know how to use the command line, there are tutorials on the internet.
If you are using a x64 version of windows, you will need to put your device in "test signing mode" or "disable driver signature verification mode", there are also instructions on the internet.
Thanks for your prompt reply.
However I am not able to put the device into APX mode.
I tried pressing and holding the Power Btn and Reset button simultanouesly(near the sdcard slot) but the DELL logo doesnot appear.
Is my procedure wrong?
Sorry for a dumb question.
manakun said:
Thanks for your prompt reply.
However I am not able to put the device into APX mode.
I tried pressing and holding the Power Btn and Reset button simultanouesly(near the sdcard slot) but the DELL logo doesnot appear.
Is my procedure wrong?
Sorry for a dumb question.
Click to expand...
Click to collapse
Yes, try readimg here: http://forum.xda-developers.com/wiki/Dell_Streak_7/Flashing_Guide
Woops! This is for a S10 not S7!
the dell logo is not supposed to appear in apx mode, it will simply be a black screen and detected as in apx mode when connected to windows.
once you boot into apx mode will the dell logo appear
TheManii said:
the dell logo is not supposed to appear in apx mode, it will simply be a black screen and detected as in apx mode when connected to windows.
once you boot into apx mode will the dell logo appear
Click to expand...
Click to collapse
Thank you. I have entered into APX and able to get the content of the partition.
I have sent the uploaded link in PM.
I would appreciate if you guide me in flashing the official PKG.
Thank you for uploading it, I assume you have attempted to directly update to 568/9?
Since you have made a backup of your rom I would recommend simply trying downloading the 569 update pkg and updating from it.
Download 569 pkg from xda wiki
Put pkg on external sdcard
Go into recovery mode
Reset device with reset pin (required)
Hold down power and volume up until you enter recovery mode (may take multiple attempts)
"flash update pkg from sdcard" (i forget exact wording, but it should be obvious from list)
select pkg and follow onscreen instructions
If that doesnt work I'll upload the 546 recovery, I dont fully understand the S10 update process (the part where it decides if the pkg is a valid upgrade, it's very selective about upgrades).
Since you've been able to use apx mode and understand how it wont be any more difficult then what you've already done.
I havnt had internet since monday because of hurricane sandy, so I cant upload everything right away.
------------------------------
Are you positive the last 2 digits of the rom version is '11'?
This is the first time i've heard of an S10 rom not being 15 (ie mainland china), 11 is for hong kong devices.
Could I ask for details on where you got this device and when? If you're not comfortable with saying it in public you can pm me.
TheManii said:
Thank you for uploading it, I assume you have attempted to directly update to 568/9?
Since you have made a backup of your rom I would recommend simply trying downloading the 569 update pkg and updating from it.
Download 569 pkg from xda wiki
Put pkg on external sdcard
Go into recovery mode
Reset device with reset pin (required)
Hold down power and volume up until you enter recovery mode (may take multiple attempts)
"flash update pkg from sdcard" (i forget exact wording, but it should be obvious from list)
select pkg and follow onscreen instructions
If that doesnt work I'll upload the 546 recovery, I dont fully understand the S10 update process (the part where it decides if the pkg is a valid upgrade, it's very selective about upgrades).
Since you've been able to use apx mode and understand how it wont be any more difficult then what you've already done.
I havnt had internet since monday because of hurricane sandy, so I cant upload everything right away.
------------------------------
Are you positive the last 2 digits of the rom version is '11'?
This is the first time i've heard of an S10 rom not being 15 (ie mainland china), 11 is for hong kong devices.
Could I ask for details on where you got this device and when? If you're not comfortable with saying it in public you can pm me.
Click to expand...
Click to collapse
Thanks for the instructions. However I was not able to enter into recovery mode. Tried couple of times.
Advice appreciated.
BTW, is it possible to flash all the partitions manually using nvflash?
I assume you have a working recovery, you may need to be make sure the battery has enough charge.
I'm not positive, but the S10 might be like the S7 wherein it wont go into recovery mode if the battery is below 60%. Even if it is charged entering recovery takes multiple tries even if you're doing it correctly.
If you can boot into android, you can simply use adb.
Enable "android adb debugging" from settings, install the adb drivers (fastboot+adb.zip from the dev subforum) and do "adb reboot recovery" from the command line.
Adb.exe is included in the mentioned zip.
Then try again, if the recovery does not want to do a pkg update, i'll upload the 568 recovery and we can try after flashing that.
If that still doesnt work I'll keep providing more files until it does, i would like to avoid having the user (ie anyone else attempting to repeat this in the future) do a full flash.
I would strongly prefer figuring out the minimum steps needed to force update a S10, as fullflashes did far more damage then they helped for the S7 due to someone providing a fullflash including their device specific data and nuking dozens of devices that way.
Just as much I'm not sure you can flash bootloader.bin from nvflash on the S10, i've attempted it and it didnt stick. It could be user error and fastboot may be able to flash it, the rest should either be flashable or not relevent.
If it were not for the bootloader, I could simply provide 569 as an update.zip flashable with CWM/S10, but I dont know offhand if the 551 bootloader is compatable with 569 as it's android 3.1 vs 3.2.
I was able to reboot to recovery from adb.
I get "Version check not allow update" error when I try to update from 568/9 pkg file.
Is it possible for you send me the 568 recovery img? And would appreciate on guiding me on how to flash using nvflash.
BTW, The 551 I have is Android 3.2.
i will upload the 568/9 recs, if that still doesnt work ill upload 569 as an update zip and you can flash with cwm
edit:
568
bootloader.bin
recovery.img
569
bootloader.bin
recovery.img
to flash a recovery (or any file in general)
boot into apx mode
nvflash -r --download <N> <filename>
<N> is the partition number
<filename> is the path to the file being flashed
flash the 568 rec and try using the 569 rec, you can attempt to flash the bootloader if you wish.
Keep in mind that flashing the bl is seperate from using it to boot in step 1, that step only loads it into memory and is lost on reboot.
the partition numbers are in the wiki.
if none of these work i'll provide more files until it does
Thanks for the upload.
Didn't have any luck with 568/9 recovery.
Strange behaviour with S10...still getting the Version mismatch Error...
I have flashed Clockwork Mod 6.0.1.2 . Would really appreciate if you could upload the update.zip.
It should work with CWM(hopefully). Worst case scenario..should try manually flashing the required partitions.
I'll upload 569 as an update.zip, it wont help you for new released roms in the future, but who knows when dell will release another update.
Thank you. Thats alright. But I guess Dell wont be releasing another update for S10.
update-S10-Stock-569-1.zip
I do not have the original update script, though I believe I have a close approximation.
If there's any issue installing it let me know, you'll need either CWM or TWRP to install it, install those in the same manner as the stock recovery. Links are in the dev subforum, make sure you grab the S10 ones and not the S7 ones.
Thanks for the upload.
I have installed the CWM and flashed the zip as specified in the following link.
http://forum.xda-developers.com/showthread.php?t=1780133
However, the system doesnot load after the flash.
I get the Dell Logo and it doesnot boot.
Would appreciate your support.
Try these in order until something works:
Did you try fac resetting from CWM?
If that doesnt work, try flashing the 569 bootloader.bin again.
If that still doesnt work try flashing CM9mod (and fac resetting) (to see if anything boots)
If it still doesnt work after those, I'll upload an nvflash dump as a last resort
How far does the bootlogo go? Does it blink once? Does it go to the animated swirl?
Initial dell logo: cpu works
1st blink, to dell logo: kernel is loading
Animated swirl: android userland is loading
Please note: This thread is specific to the Che2-L11 model Honor 4xFor discussion pertaining to the Che1-L04 model click here.
Because there are some significant differences between the Honor 4x variants information can get confusing quite easily, therefore I decided to start a thread dedicated to the Che2-L11.
:good: Any information or discussion is welcome as long as it is about this particular model.
:fingers-crossed: Since the device is still relatively fresh, information is scarce. I will try to update and expand this post as we discover the possibilities of our shiny new phone.
Rooting the Che2-L11
There are currently no known tools or exploits that can be used to gain root under the stock firmware. Unlocking the bootloader will allow full access to the device, however at this time there are no known working custom recoveries or roms.
The official Huawei unlock page doesn't support it as of yet, neither by editing the product model information on that page like it works for some other models. Instead you can send an e-mail to [email protected] and provide the same information as requested on the unlock page.
Once you obtain the correct unlock code you can follow the unlocking procedure. Be careful when experimenting with recoveries or roms intended for other or similar models, they may brick or damage your device.
SD Cards >32GB
Although not officially supported, 64GB cards seem to work fine. The phone will recognise and use their full capacity automatically. It will most likely support 128GB cards as well but this is not yet confirmed.
Model numbers
The Honor 4x is being sold under several different model numbers divided into two basic groups: Che1 and Che2. Che stands for Cherry.
Che1 is based on the Snapdragon 410 chipset: Che1-CL10 (China/Telecom), Che1-CL20 (China/Netcom), Che1-L04 (India/Flipkart) and Che1-UL00.
Che2 is based on the Kirin 620 chipset: Che2-L11 (Europe), Che2-L12, Che2-L23, Che2-TL00, Che2-TL00H, Che2-TL00M and Che2-UL00.
Reserved
Reserved 2
Reserved 3
Reserved 4
Reserved 5
Send email to [email protected] with the model type (Che2-L11), IMEI1, S/N and Product ID and they will send you the unlock code.
I got mine within an hour after sending the email Happy rooting!
samusalo said:
Send email to [email protected] with the model type (Che2-L11), IMEI1, S/N and Product ID and they will send you the unlock code.
I got mine within an hour after sending the email Happy rooting!
Click to expand...
Click to collapse
I must have been doing something wrong then, although I did use [email protected] instead. Will try again with that address.
Have you tried any custom recoveries yet?
The reply also came from [email protected] so that must be the correct address. Just quickly tried the CWM made for Che2-TL00. It did boot once, but backup job crashed the phone and the recovery didn't boot anymore. Just flashed the stock recovery back
Have to try again this evening when I have more time.
Here's a link to the Che2-TL00 CWM recovery I used. I replaced the stock recovery in the zip-file with the Che2-L11 stock recovery. So this can be also used to bring the recovery back to stock.
https://drive.google.com/file/d/0Bxo5Ed10JsVqbHJiNDZZc2RGSHM/view?usp=sharing
I was able to flash SuperSU with it and now the device is rooted
so many different versions, support is going to be a nightmare...
tried [email protected] and [email protected] and did not receive a reply yet, it has been 2 days =( shame, really want to try new stuff on this phone, it was going to be my side project to try and port CM12 to my 4X CHE2-UL00, buy with a locked bootloader nothing I can do =(
Any other ideas where can I unlock my bootloader?
Finally replied, let the fun begin =)
Lollipop Update
I've asked Honor Europe about the lollipop update (5.x) for the Che2-L11. Here's the answer:
Thank yo for your message, It is not yet been planned for Q2, however we are working on the update to launch it soon. Stay tuned for more information. Honor Europe
So, we have to wait Q3 or Q4(!?).... maybe they update directly to 5.1?
BTW: Really need a root to install Link2SD. This would solve the (small) 8gb storage problem. Someone tried oneclick and other root tools to root the Honor 4x?
I just bought the phone not longer, I also want to root the phone.
Can you guys help me how to root the phone? Thanks!
Did you notice that you can change the preferred storage location to sdcard?
I have >3GB of apps installed and still over 1GB free internal storage. I can say I am a heavy user of different apps, and with a decent sd card (Samsung Pro U1 32GB), I have no problems to manage with the 4X, if compared to my other phones.
Unlock bootloader for Honor 4X (Che2-L11)
a) Request your bootloader unlock code from huawei by sending email to [email protected]
Provide following info
Mobile Model: Honor 4X Che2-L11
MEID/IMEI:
S/N:
Product ID:
(to get your product id, enter *#*#1357946#*#*. An 8-digit ID is then displayed)
Patiently wait for 2-3 days, you will received 16-digit number from the return email
b)Download the following files:
i) Adb fastboot tools + ClockworkMod Recovery for Honor 4x + Honor 4x (che2-L11) original recovery:
Note: Get the file from post #10
ii) SuperSU by chainfire : UPDATE-SuperSU-v2.14.zip
iii) Connect honor 4x to your pc and install HiSuite
c)Preparing the phone
-Enable ‘Developer options’ (Settings > About phone > tap on ‘Build number’ until it’s enabled)
-Go to ‘Developer options’ and enable ‘USB debugging’
-Connect Honor 4x to PC (with HiSuite successfully connected)
-Extract zip file downloaded from b) i) to a folder (e.g. adbtools)
-Run cmd to get into command prompt from PC and change directory to adbtools
-On the Command Prompt window type ‘adb devices’, and it will list down device serial number, with a word device following behind.
-Type ‘adb reboot bootloader’ to kick the phone into Fastboot mode. You will see that your phone boot into a white screen with android robot with the words 'Phone Locked' (in blue)
-Type ‘fastboot oem unlock unlockingpassword’, where ‘unlockingpassword’ is the 16-digit number you’ve obtained earlier
-If successful, the phone’s screen will now show ‘PHONE Unlocked’ in red
-Reboot the phone to make sure everything runs ok.
Flashing custom recovery for Honor 4X (Che2-L11)
To root your phone, you need to flash a custom recovery to it.
-Same as earlier step, run cmd to get into command prompt from PC and change directory to adbtools
-Type ‘adb devices’ to make sure that your phone is properly connected.
-Type ‘adb reboot bootloader’ to kick the phone into Fastboot mode.
-Type 'fastboot flash recovery cofface_recovery_che2tl00h.img' (for Kitkat android 4.4)
-If successful, you’ll get a ‘finished’ confirmation with the time it took to complete the process.
-To confirm a successful flash, power down your phone. Then go Recovery mode (stock or CWM): Press volume up + power buttons
-In case you need to turn back to stock recovery, repeat the above steps, Type 'fastboot flash recovery recovery_offical.img' instead and reboot to your original stock recovery.
Rooting Honor 4X (Che2-L11) for KitKat Android 4.4
-Download Chainfire’s SuperSU ZIP file into the phone’s SD card
-Boot the device into Recovery mode
-Navigate into the ‘install zip from sdcard’ option,
-Find the downloaded SuperSU ZIP file, and flash it.
-Once done, reboot the Honor 4x and launch the SuperSU app, install the binaries, and reboot the phone again.
-Congratulations, your device is now rooted.
Rooting Honor 4X (Che2-L11) for Marshmallow Android 6
-Download recovery file 4C Root+TWRP by [email protected]
Note: we are using TWRP for Honor 4C
- Extract and flash recovery as same step above using this new recovery img fastboot flash recovery twrp.img
- Download this file and copy to honor4x folder
- Download supersu zip and copy to honor4x folder
- Go in TWRP recovery. Do not swipe allow modifications and choose read only for system files...... and then flash that zip file named 1.zip.
- After its done, restart your phone and if it prompt to install su, ignore it....
- Open supersu app installed in your phone and let it update its binaries...when done, reboot to recovery again and this time flash BETA-SuperSU-v2.67-20160121175247.zip
- Reboot your phone.
- Now you have successfully rooted Marshmallow
- Reference: [ROOT][MARSHMALLOW][HONOR 4C]
Final words, do this on your own risks as it voids the phone warranty.
Thanks!! Now waiting the unlock bootloader password.
Just a heads up. Like mentioned before, I never received a reply from [email protected], but from [email protected] I received a reply within an hour after sending the request.
I ask the code last night. I received this morning. My Honor 4X is rooted, thank you! :good:
I am from India and I exchanged my iPhone 4S for a Moto X 2014 just this evening wanting to try my hands on the Android experience.
I do not know what the seller did to this phone but I now have two issues. I tried to call the seller immediately after I noticed these problems when I came home but the number is switched off. Shame on him!
After Google'ing I found this forum for android support so I hope posting the problems here would give me some solution
Problem #1: Every time when I boot my phone, it has the warning screen which says "Warning unlocked bootloader".
Problem #2: The warning went off and landed me on the home screen. I connected to my WiFi and saw that there is a software update. I downloaded it and chose to install it. It kept rebooting for 4-5 times and then said "System Update - Failed".
Can anyone please be patient enough to give me step by step solution with download links to get my Moto X2 back in shape as how it was out of the box?
I googled a lot for the keywords "relock bootloader moto x 2014", "unroot moto x 2014" and plenty of links with different download links came up. I do not know which one to trust. I am not dumb and I can easily follow instructions. So, please anyone wanna help?
If the OTA (software update) is failing, maybe it's because the firmware you have was installed via custom recovery, not stock, or even the firmware is custom too, that's why you get a bootloop if you try to install the update.
Can you post a screenshot of your "About phone"? (Settings>About phone).
Nek0x90 said:
If the OTA (software update) is failing, maybe it's because the firmware you have was installed via custom recovery, not stock, or even the firmware is custom too, that's why you get a bootloop if you try to install the update.
Can you post a screenshot of your "About phone"? (Settings>About phone).
Click to expand...
Click to collapse
Thank you for the reply. Attached the screenshot.
i64.tinypic.com/2nu3asn.png
I fiddled around to find out how to get into the Fastboot mode... and I observed something weird there..
AP Fastboot Flash Mode (S)
60.16 (sha-#some checksum number key with date 2015-04-02 and time#
CPU: MSM8974AC EA1.1
eMMC: 2048MB Samsung RV=07 PV=0B TY=57
Battery OK
Device i UNLOCKED. Status Code: 3
Software status: Official
I mean Seriously? I see the word Samsung in a Moto phone? I so regret buying from this seller... too much for a first Android phone :crying:
Well I also managed to Google more and installed the device drivers and the Fastboot software in my Windows PC.
Booted my device in fastboot mode and issues the below commands:
fastboot devices
#my device was shown#
fastboot oem lock
#told me to use the command with begin#
fastboot oem lock begin
#Said something like the image is ready#
Nothing happened then though. I powered on my device and I still see that warning. Still the software update is failing. :crying::crying::crying:
You don't need to unlock your bootloader, it is already unlocked, that's why the bootloader says that the "Device is unlocked", but also says your firmware is stock (Status software official).
If your firmware is stock, I don't know why its failing to apply the update, maybe is because your phone has a custom recovery. Try to enter into that option in the bootloader and see what happens.
Nek0x90 said:
You don't need to unlock your bootloader, it is already unlocked, that's why the bootloader says that the "Device is unlocked", but also says your firmware is stock (Status software official).
If your firmware is stock, I don't know why its failing to apply the update, maybe is because your phone has a custom recovery. Try to enter into that option in the bootloader and see what happens.
Click to expand...
Click to collapse
I am not trying to unlock my bootloader. I am trying to restore it back to the "out of the box" state. I mean I want to lock it and I want it to be in the state how it usually is when bought from the store.
Ok... I google'd how to go into the recovery mode and found this link (teamandroid.com/2015/01/08/enter-recovery-mode-moto-x/).
I followed those steps:
1. Turn OFF your phone.
2. Press and hold the Volume Down button for 2-5 seconds. While holding the Volume Down button, press the Power Button for 1-2 seconds and release.
3. I used the Volume down key to highlight "Recovery" and clicked on the power button to select it.
4. My screen went off. I mean the light gone.
Then I had to press and hold the power on button, it booted my phone with that warning unlocked bootloader message.
What am I doing wrong?
UPDATE:
I did a fastboot, connected phone to PC and issued the below command from PC and get below error:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
UPDATE 2:
I enabled the developers option (by tapping on the Build number multiple times)
So, I installed an app called MobileUncle Tools.
I then opened the app from my mobile and clicked on "Reboot into recover".
It says "Please root your Android first".
OK.. so looks like the phone is not rooted - which is good.
Only the bootloader is unlocked. All I need to figure out is - re-lock my bootloader and make the system update go through successfully.
Any help please?
You must unlock the Developer Options in your phone, and then activate the debugger mode to be able to use adb commands like "adb reboot recovery".
In the About phone menu in settings, press five times the option of "Build number", then the Developer options in settings will be available. Navigate to that menu and activate the Android debugging option, then you should be able to use adb from a command window in your PC.
EDIT: Also, you have to press the up volume button in the bootloader to choose an option, not the power button.
Having the bootloader unlocked doesn't affect system updates via OTA or anything if your firmware and recovery are stock. Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery.
Nek0x90 said:
You must unlock the Developer Options in your phone, and then activate the debugger mode to be able to use adb commands like "adb reboot recovery".
In the About phone menu in settings, press five times the option of "Build number", then the Developer options in settings will be available. Navigate to that menu and activate the Android debugging option, then you should be able to use adb from a command window in your PC.
EDIT: Also, you have to press the up volume button in the bootloader to choose an option, not the power button.
Having the bootloader unlocked doesn't affect system updates via OTA or anything if your firmware and recovery are stock. Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery.
Click to expand...
Click to collapse
I have one question for you:
What do you mean by "Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery".
My understanding is - you are saying my stock firmware is intact because it said Official in the fastboot screen. Right?
Ok... now back to the recovery check... I think I did it.
1. I went in the fastboot mode
2. Used volume down key to scroll down to Recovery option (2nd option)
3. Pressed Volume up key to select it
4. The phone rebooted (The white screen "warning unlocked bootloader" message was displayed this time too)
5. I saw a dead android symbol with the word "No command."
6. I pressed Power and Volume Up key. I saw the recovery screen I guess. There were many options - Wipe data, Wipe Cache, Install from SD, etc.
What do I need to check there?
EDIT:
Ok I noted this number from there:
Android system recovery <3e>
LPE23.32-25.1
followed by the options
reboot system now
apply update from sdcard
etc.
I think this is what has happened:
Google says "LPE23.32-25.1" is the Android 5.1 Lollipop update (v23.16.1, build LPE23.32-25.1)
However, the current Android version on my device "About" screen is 4.4.4
The OTA system update, my device telling me about is Android 5.0 Lollipop version: 22.21.19.en.EU (which is a lower version than my recovery's version)
My menu options look all white and after google'ing I realize that it has Android L's menu. Please see the screenshot i65.tinypic.com/14l4mmb.png
Could that be that reason? What can I do t rectify it?
1) You most likely will want to keep your bootloader unlocked, since it'll give you more freedom to deal with roms and flashing. It won't affect taking OTAs, in fact, I've just taken the 6.0 OTA and my bootloader is unlocked.
2) Don't worry about the Unlocked Bootloader Message. That can be fixed by flashing the correct logo.bin file.
3) If your device is in KitKat (4.4.4) but your bootloader is from Lollipop (5.0 or 5.1), DON'T TAKE THE OTA. There's one post here saying that it'll cause a hardbrick. Your solution will be to manually flash the correct firmware or use RSD Lite.
joseph_1802 said:
1) You most likely will want to keep your bootloader unlocked, since it'll give you more freedom to deal with roms and flashing. It won't affect taking OTAs, in fact, I've just taken the 6.0 OTA and my bootloader is unlocked.
2) Don't worry about the Unlocked Bootloader Message. That can be fixed by flashing the correct logo.bin file.
3) If your device is in KitKat (4.4.4) but your bootloader is from Lollipop (5.0 or 5.1), DON'T TAKE THE OTA. There's one post here saying that it'll cause a hardbrick. Your solution will be to manually flash the correct firmware or use RSD Lite.
Click to expand...
Click to collapse
THANK YOU SO MUCH for clearing that point 1 and 2. That is a relief!
Point #3 - "Your solution will be to manually flash the correct firmware or use RSD Lite."
What do I flash? OTA 5.1 (because my bootloader is from 5.1) or OTA 22.21.19.en.EU (because that is what I see in my phone's Software Update Available screen.
Where do I download those OTA files?
How do I flash using RSDLite? Any guide?
Thank you!
UPDATE:
Found the guide forum.xda-developers.com/showthread.php?t=2231249
I only need to know what I version I need to flash AND where can I download it from. Please?
Best option is flashing the entire firmware of your phone variant using RSDLite. The firmware you're looking for (based on what Google says) is VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3
Can you confirm this? If it's correct, then the firmware is in this folder (Firmwares 5.1 stagefright solved): https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Nek0x90 said:
Best option is flashing the entire firmware of your phone variant using RSDLite. The firmware you're looking for (based on what Google says) is VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3
Can you confirm this? If it's correct, then the firmware is in this folder (Firmwares 5.1 stagefright solved): https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Click to expand...
Click to collapse
My recovery screen showed LPE23.32-25.1
So there is just the last number change... the download link you gave is for the version ending with .3 where my recovery shows .1
That should not be a problem, or should it?
Flower07 said:
My recovery screen showed LPE23.32-25.1
So there is just the last number change... the download link you gave is for the version ending with .3 where my recovery shows .1
That should not be a problem, or should it?
Click to expand...
Click to collapse
No it's not a problem. This will give you the latest version with the stagefright patch.
Sent from my XT1095 using Tapatalk
It is .3 because it has the stagefright patch, the .1 version doesn't have that patch but both of them are basically the same, so there's no problem if you flash one or another.
When I first purchased this phone I was able to boot to the default recovery that came with the phone ( which clearly had a *fastboot option*), it came with stock 5.1, and a bunch of bloatware.
I downloaded the one click root method for the h811 which was perhaps the easiest root i've ever done. great. i also had to flash my recovery to twrp 2.8 for some reason.
Rocked out to a newely rooted device on 5.1 until the t mobile bloatware and system update notification kept bugging me, so I said * eff it, i've been holding out for a while*
So I get to the cm 13 wiki for my device, I managed to install the cm recovery ( cant remember how i did this for some reason) and then i was able to flash cm13 to my phone. CM13 is sleek, and smooth but is presenting problems.
First of all, no google play store and the gapps zip wont install through cm recovery ( fails and tells me to use twrp instead which is a problem because i can't boot this phone into fastboot mode)
I am unrooted and can not figure out how to properly root a T mobile h811 running cm13, so the twrp manager doesn't work because it "requires root" then shuts down. ( enable root access in the cm13 developer options does nothing at all and yes, for adb and apps)
FAST BOOT MODE DOES NOT SEEM TO EXIST ANYMORE ON MY PHONE - Following the many tutorials, which goes long the lines of using adb/fastboot, adb devices can see my device, but fastboot devices can't ( figures) because its not in fastboot mode. Any fast boot reboot bootloader or any variant of that command only reboots the phone, to... swipe the screen.
I've installed the lg bridge crap ( which installed an updated usb driver) that doesn't even recognize my phone " no mobile device connected". tried uninstalling and reinstalling, but nothing. When putting the phone in download mode, to see if adb would rcognize it, windows sees this as a new device , installs drivers but says " device can not start, code 10 * in device manager. :silly:
is there anything that can be done?? google searches result in obvious solutions that SHOULD work but don't, or threads where a person coincidentally has the same exact problem as I do, but their response is usually the last response in the thread that goes unanswered
summary : I've install cm13 on my lg g4 h811, I do not have root access, I can not install twrp due to ( no fastboot mode) in effect, i cant install gapps, cant root phone etc..
any help?
did you ever unlock the phone....?
Yes, unlocking the phone is one of the first things you would need to do. In Developer Options > OEM Unlock. Then in bootloader, run the unlock command. This will delete /data and internal storage so back up your files so you can transfer them back via adb or fastboot.
Then you're probably going to need to temp boot TWRP, then flash the TWRP recovery image in TWRP. THEN you can flash properly.
Carefully read through this thread:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Good luck.
Edit: oh and this thread belongs in Q&A.
Alright. Am I only to read the first post or all 30+ pages? ( not that i have a problem, just curious)
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
aoaleman said:
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
Click to expand...
Click to collapse
"ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it."
didn't work, very frustrating. any clues? on windows 8.1 by the way. tried two computers. none can see this phone. I can connect the phone to the computer and see its storage, lg usb driver is installed
You probably need to reinstall the drivers. It might be the fastboot driver. That's what worked for me.
I've reinstalled the official drivers, uninstalled them... Jusst the mobile USB driver, a combo of both, plenty of times. Don't understand why this software doesn't see my phone
Lgup, lgair, lg bridge, lg USB driver (skinned down) .. Nothing works tested on my gaming rig., and work laptop both running win 8.1 64 bit
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
TacoTuco said:
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
Click to expand...
Click to collapse
This section does get more views though haha.
Anyway I feel that the 811 is one of the more finicky devices to get into fastboot at least in my experience. I had to enable and disable dev options while plugging and unplugging device and it finally worked. No idea if that'll work for everyone though.
I reasked the question in Q and A. Please help some one.
You start over. LG bridge.
Having the same issue. I'm on Windows 10. What developer settings did you mess with to get it working, tiskewlio?
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Sunaj1 said:
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Click to expand...
Click to collapse
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
thevirgonian said:
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
Click to expand...
Click to collapse
silly question maybe, but is there a specific tutorial in getting this to work with the files provided given my situation? (commands, etc..) will this somehow bypass the the lge mobile mtp device that wont install ? I had installed the system wide adb/fastboot drivers, and already had a folder with just the minimal install of the adb but didnt have a few files in the one you provided ( lg root, busy box, etc) so not quite sure what to do with them.
Again, if possible want to flash twrp recovery to my device but can't due to * waiting for any device* and the ( device cannot start ) error
Thanks
* waiting for device* when putting phone in download mode and pushing fastboot flash twrp-2.8.7.1-h811.img.
Any help would be appreciated as I need to get the driver to work first. see attached picture.
Cha h
the issue is largly resolved as i've been able to flash the recovery and install another rom. But i'd still like to know how to get the download mode driver properly working in the event i need a computer and can't do a self contained install.
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
travisd4est said:
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
Click to expand...
Click to collapse
i dont know man, i did all that a million times over, but recently i was able to just flash the stock MM rom to the device using LGup. Think i'll just stick with stock rom and root for a while as all this stuff is a little finicky at times. Thanks for your help.
1. You need to join the beta testing program
2. You should receive an over-the-air update of ~ 250MB for Android 12L Beta 1, install the update.
3. After updating and rebooting the device, go back to the beta testing program website and click the "Disable" button.
4. You will again receive an update in the size of ~ 150 mb, this is a rollback to the stable assembly of Android 12 (SQ1A.211205.008). After installing this update, there will be a reboot and the phone will be automatically reset to factory settings.
5. We go through the initial setup, go to the settings and activate the developer mode (in the "About phone" item, tap 5 times on the build number). Go to the "For Developers" menu (Settings-> System-> For Developers).
6. Next, download the platform tools to your pc and unpack the folder to the C: \ drive. Installing the drivers.
7. We transfer the phone to fastboot mode, turn off the phone and hold down power + volume down, connect it to the PC.
8. Open the command line as administrator (Win + X-> Command line (administrator)).
cd C:\platform-tools
fastboot devices
fastboot flashing unlock
After the commands have been executed, the device will reboot and will be reset to factory settings.
We go to the settings and check
Bootloader is unlocked.
Source
dvrk__soul said:
1. You need to join the beta testing program
2. You should receive an over-the-air update of ~ 250MB for Android 12L Beta 1, install the update.
3. After updating and rebooting the device, go back to the beta testing program website and click the "Disable" button.
4. You will again receive an update in the size of ~ 150 mb, this is a rollback to the stable assembly of Android 12 (SQ1A.211205.008). After installing this update, there will be a reboot and the phone will be automatically reset to factory settings.
5. We go through the initial setup, go to the settings and activate the developer mode (in the "About phone" item, tap 5 times on the build number). Go to the "For Developers" menu (Settings-> System-> For Developers).
6. Next, download the platform tools to your pc and unpack the folder to the C: \ drive. Installing the drivers.
7. We transfer the phone to fastboot mode, turn off the phone and hold down power + volume down, connect it to the PC.
8. Open the command line as administrator (Win + X-> Command line (administrator)).
cd C:\platform-tools
fastboot devices
fastboot flashing unlock
After the commands have been executed, the device will reboot and will be reset to factory settings.
We go to the settings and check
Bootloader is unlocked.
Source
Click to expand...
Click to collapse
Hey,
I follow the instructions but when reboot after going back to Android 12 stable my bootloader still is locked. Could you help me please?
I unlocked the bootloader on my AT&T Pixel 4XL in March 2022 right after I called AT&T's (actually Asurion) support to have them carrier unlock the device. For the record, I was using the esim for my AT&T service and I had unlocked the developer options previously, but OEM unlocking was greyed out. I put in another carrier's SIM (Google Fi in case it makes a difference) and saw that it was picking up an LTE signal. I didn't have service with Fi, just a card kit I'd picked up for $2 on Amazon. I rebooted the device, checked the developer options and saw that OEM unlock was no longer greyed out. I activated it and rebooted fully back to system. Then I rebooted to the bootloader and "fastboot oem unlock"ed it. Fastboot mode shows the device state as "unlocked" in red. I was as surprised as anyone as I'd gotten the coral as a replacement from Asurion for my LG v20 two years ago and I wasn't sure the device could be bootloader unlocked.
That was lucky!
I have a 4XL which I bought second-hand. It was cheap, 180$ and the only problem was that it was locked to AT&T, and unfortunately the previous owner didn't pay the phone yet, so I am working on a method to unlock the bootloader of a locked phone.