Just tried it, fastboot tells that P6 bootloader is unlocked, so we can flash everything in our P6
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe, this is the reason why Huawei don't tell anything about our bootloade
Already reported that flash can be done in htcmania, with the method from 4pda.ru :cyclops:
How to check if your bootloader is unlocked:
-Open a cmd console
-Type: adb reboot-bootloader
-Type: fastboot oem get-bootinfo
-Done
S34Qu4K3 said:
Just tried it, fastboot tells that P6 bootloader is unlocked, so we can flash everything in our P6
Maybe, this is the reason why Huawei don't tell anything about our bootloade
Already reported that flash can be done in htcmania, with the method from 4pda.ru :cyclops:
How to check if your bootloader is unlocked:
-Open a cmd console
-Type: adb reboot-bootloader
-Type: fastboot oem get-bootinfo
-Done
Click to expand...
Click to collapse
Code:
:~$ fastboot oem get-bootinfo
< waiting for device >
nothing more...
---------- Post added at 05:15 PM ---------- Previous post was at 05:13 PM ----------
S34Qu4K3 said:
Just tried it, fastboot tells that P6 bootloader is unlocked, so we can flash everything in our P6
Maybe, this is the reason why Huawei don't tell anything about our bootloade
Already reported that flash can be done in htcmania, with the method from 4pda.ru :cyclops:
How to check if your bootloader is unlocked:
-Open a cmd console
-Type: adb reboot-bootloader
-Type: fastboot oem get-bootinfo
-Done
Click to expand...
Click to collapse
Code:
:~$ fastboot oem get-bootinfo
< waiting for device >
nothing more...
edit: P6-U06, Germany
TheProd said:
Code:
:~$ fastboot oem get-bootinfo
< waiting for device >
nothing more...
---------- Post added at 05:15 PM ---------- Previous post was at 05:13 PM ----------
Code:
:~$ fastboot oem get-bootinfo
< waiting for device >
nothing more...
edit: P6-U06, Germany
Click to expand...
Click to collapse
You did adb reboot-bootloader?? Make sure that phone is in MTP mode and you have the drivers
S34Qu4K3 said:
You did adb reboot-bootloader?? Make sure that phone is in MTP mode and you have the drivers
Click to expand...
Click to collapse
I did this at my linux notebook!
On Windows fastboot cmds are working (hisuite driver)... and bootloader is unlocked! :cyclops:
TheProd said:
I did this at my linux notebook!
On Windows fastboot cmds are working (hisuite driver)... and bootloader is unlocked! :cyclops:
Click to expand...
Click to collapse
Great news! We can flash now everything on our phone *0*
It has already been said that the bl shows up as unlocked. However noone has managed to flash a new kernel, and that is why they consider it to be encrypted.
zordo said:
It has already been said that the bl shows up as unlocked. However noone has managed to flash a new kernel, and that is why they consider it to be encrypted.
Click to expand...
Click to collapse
An user in htcmania flashed de b115 kernel in a b107 rom sucessfully, and somebody in Huawei official twitter said that some things can be flashed
Sent from my HUAWEI P6-U06 using xda app-developers app
Hello!
My device seems to be unlocked....but I can not managed to flash stock kernel !
The same kernel (stock) was succesfully flased by this command :
# dd if=/sdcard/boot.img of=/dev/block/......
If you want to do it, do:
-adb reboot-bootloader
-fastboot flash boot boot.img
-fastboot reboot
It should work, and remember, do it at your own risk
S34Qu4K3 said:
If you want to do it, do:
-adb reboot-bootloader
-fastboot flash boot boot.img
-fastboot reboot
It should work, and remember, do it at your own risk
Click to expand...
Click to collapse
Hi!
As I told you, on my device I can not flash stock kernel !
Please take a look here and follow all my posts to understand better !
Thanks :good:
surdu_petru said:
Hi!
As I told you, on my device I can not flash stock kernel !
Please take a look here and follow all my posts to understand better !
Thanks :good:
Click to expand...
Click to collapse
I read somewhere that you need to flash this to get it work:
fastboot fastboot.img
fastboot flash efi efi.img
fastboot flash modemimage modemimage.img
fastboot flash boot boot.img
Try it if you want
Reyncla in htcmania make this script. Work
https://mega.co.nz/#!4Y5hyILD!GzQny36sJ-Ec0wErtk4BAxD398pJFaEhHE8Z67zp0u4
JoySu said:
Reyncla in htcmania make this script. Work
https://mega.co.nz/#!4Y5hyILD!GzQny36sJ-Ec0wErtk4BAxD398pJFaEhHE8Z67zp0u4
Click to expand...
Click to collapse
Hi!
Do you tested with this script ?
Will be ok if someone can test it....I'm on holliday
Begining September I can try to make an custom cwm/twrp and also some custom roms....:good:
---------- Post added at 05:54 PM ---------- Previous post was at 05:52 PM ----------
S34Qu4K3 said:
I read somewhere that you need to flash this to get it work:
fastboot fastboot.img
fastboot flash efi efi.img
fastboot flash modemimage modemimage.img
fastboot flash boot boot.img
Try it if you want
Click to expand...
Click to collapse
Hi!
Already tried...and not work on my unlocked bl device...
Scrip works
I'm setting up a linux vm to try to port CWM I hope to make some advance in a few days
Sent from my HUAWEI P6-U06 using xda app-developers app
S34Qu4K3 said:
Scrip works
I'm setting up a linux vm to try to port CWM I hope to make some advance in a few days
Sent from my HUAWEI P6-U06 using xda app-developers app
Click to expand...
Click to collapse
Hi!
...would be nice
I can help you....but later...
Also you can send me a PM....
I'll do it, i want to port it well i don't want any brick
Sent from my HUAWEI P6-U06 using xda app-developers app
surdu_petru said:
Hi!
Do you tested with this script ?
Will be ok if someone can test it....I'm on holliday
Begining September I can try to make an custom cwm/twrp and also some custom roms....:good:
This script created by reyncla of HTCMania works in windows for p6. Only makes it easy to check if the device is locked or unlocked. The unlocked bootloader test said.
Click to expand...
Click to collapse
All this script does is automate the exact process that is outlined on the OP.
Code:
:ACTUALIZA
CLS
color 3f
ECHO. =================================================
echo. Buscando telefono...
echo.
[B]adb reboot-bootloader
fastboot oem get-bootinfo[/B]
echo.
[B]fastboot reboot[/B]
echo.
echo Oprima cualquier tecla para salir...
echo.
ECHO. =================================================
ping 127.0.0.1 -n 5 >NUL
pause >NUL 2>NUL
exit
It doesn't do anything more then tell the user the bootloader information we already gained from the manual procedure.
Edit: Ahh didn't see you'd already commented on this JoySu, my bad. Oh well double clarification.
Best Regards,
s89
fastboot boot boot.img can't be done... So i think, bootloader locked :/
Someone in our german forum told me, that she had a huawei before and there was a similar problem like here.
There was a way to flash the boot img, just set some settings before:
* # * # 2846579 # * # *
Project menu --- set back-----USB Port Configuration-----production mode -> (reboot)
* # * # 2846579 # * # *
Project menu-------LOG setting-------LOG open------LOG level-----set "VERBOSE"
adb reboot bootloader
Click to expand...
Click to collapse
I dont know if it works with our P6.
Related
How to Boot Into LG G3 Fastboot Mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-- What is Fastboot?
Fastboot allows you to re-flash partitions on your Android device. It works through PC command line and connects over a USB connection with your device.
Not every Android device manufacturer allows direct Fastboot access to end-users, and unfortunately LG is one of them. But there’s a workaround for the LG G3..
The LG G3 download mode hides the fastboot mode behind it, so if we remove the download mode (laf) from the device we get direct access to fastboot on G3. Follow the instructions below to get started:
-- STEP 1: Remove LG G3 Download mode (laf)
Important!You’ll need root access to remove (laf), so make sure you’ve rooted your LG G3 before proceeding with the steps below:
Download ADB files:
Prepare your phone:
Enable developer options: Go to your phone’s Settings » select About phone » Scroll to the bottom and tap on “Build number” seven times to enable developer options
Enable USB Debugging: Open phone’s Settings » select Developer options » Tick the “USB debugging” checkbox (under Debugging section)
Connect your phone to PC with a USB cable and if/when a pop-up screen shows up on Phone asking you to ‘Allow USB debugging?‘ for the computer, make sure you tick the checkbox and tap OK
Navigate to the folder where you have extracted the adb and fastboot recovery files and hold SHIFT key on your keyboard and RIGHT CLICK and select “Open command window here” (as shown in the below image).
Now type/paste the following ADB commands to backup LG Download Mode (laf), so you can restore it later when necessary
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
Now run the following command to remove laf and reboot your phone
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
exit
adb reboot
Your phone will now reboot
How to Boot LG G3 Fastboot Mode:There are a few ways you can accomplish this, I will go over just a few of them.
adb reboot bootloader:
Code:
adb reboot bootloader
Going into Download Mode:
Disconnect your phone from PC.
Power off your G3 and wait 4-5 seconds after lights go off.
Hold the Volume Up button on phone, and while holding it, connect the phone to PC using a USB cable.
I took this nfo from the original source listed below and made a few changes..
I will update with more nfo as to installing correct drivers for windows and setting up linux
at a later time. For now I only posted because I received a few request to do so.
Original Source: How to Boot Into LG G3 Fastboot Mode
Fastboot mode
fastboot
Could you explain why one would use this?
I HAVE used download mode in the past...
When i soft bricked my phone... I had to use download mode(i think?) to get the stock firmware back in....Would using fastboot(still dono why anyone would use it), take download mode out?
Thanks for upload
yanowman said:
Could you explain why one would use this?
I HAVE used download mode in the past...
When i soft bricked my phone... I had to use download mode(i think?) to get the stock firmware back in....Would using fastboot(still dono why anyone would use it), take download mode out?
Thanks for upload
Click to expand...
Click to collapse
download mode is LGE's version of updating your phone with their software.
as to fastboot gives you more control over what you want to update..
you have like 25 commands you could do in fastboot as to download mode you have no control over..
Download mode is just as it is, turn it on and wait..
as to fastboot, you turn it on type fastboot and see the list of commands.
example:
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
Another Example:
Code:
fastboot getvar version
The results will be the bootloader version, Mine showed up as 0.5 .................
One more thing: If you softbrick your phone and cant get into Recovery, fastboot is pretty much always there. you can fix any one of your partitions or all.
Some may not want it or like it, But anyone who does alot of flashing and experiments would like it as a life jacket just in case.
flashing a full kdz file can be a pain in the butt, while just flashing the partition that you need to get your phone to boot back up is much easier..
I bet you couldnt do all that in Download mode..
solution for fastbooting system.img on G3? always get errors related to file size or header.
everything else has always fastbooted without issue.
fun facts
1. fastboot is broken on D851 20B aboot.img... you can boot into fastboot but no images seem to actually flash or boot from it.
2. verizon has disabled fastboot entirely, trying to boot into it will get you a black screen and disco led.
in both of the above conditions.. if fastboot was your last hope you would be stuck.
Guys . maybe it's stupid question , but i need answer
So , we have unlocked bootloader on T-mobile g3 , we can access fastboot mode . bla bla bla
So long story short , can't we convert t-mobile g3 to international g3 (with 32GB and 3gb ram version) ? why? i just need it
i was doing same on g2 before and it was booting , but mine had problem with flash memory itself (which contains imei ,ect..) ,so i couldn't say anything why it wasn't stable , but it was booting up
autoprime said:
1. fastboot is broken on D851 20B aboot.img... you can boot into fastboot but no images seem to actually flash or boot from it.
Click to expand...
Click to collapse
Sorry for quoting you sir, but I have successfully flashed partitions using fastboot on 20B.
@Eliminater74 thanks for this guide.
Just one question: where is fastboot located? I mean in what img/partition?
aboot.img?
Is it work on a dead boot ? I can't boot to recovery or DL mode but my device shows as normal usb on pc but no display only black screen. I messed up my phone partitions. How to acces fastboot in this case ?
how can i get download mode back as i have the laf file
balakay4312 said:
how can i get download mode back as i have the laf file
Click to expand...
Click to collapse
you need a working phone to do that.
But the way was the reverse:
Code:
adb shell
su
dd if=/file/you/have/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
if your phone is not working, you need to use boarddiag
Thanks but i just flashed it in fastboot using fastboot flash laf laf.img
Eliminater74 said:
flashing a full kdz file can be a pain in the butt, while just flashing the partition that you need to get your phone to boot back up is much easier..
Click to expand...
Click to collapse
How can I flash a kdz file through fastboot? I know it's hard but I really want to try.
pelelademadera said:
you need a working phone to do that.
But the way was the reverse:
Code:
adb shell
su
dd if=/file/you/have/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
if your phone is not working, you need to use boarddiag
Click to expand...
Click to collapse
How can I use BoardDiag in order to get back download mode?
BarCouSeH said:
How can I use BoardDiag in order to get back download mode?
Click to expand...
Click to collapse
You need to get the phone in qualcomm 9008 mode... Or breaking the partition table, or forcing it... I dont know how, but if you google it... You must find the way
Enviado desde mi LG-D851 mediante Tapatalk
Impossible...
BarCouSeH said:
How can I flash a kdz file through fastboot? I know it's hard but I really want to try.
Click to expand...
Click to collapse
KDZ's are only for use on LAF mode, Bootloader use Fastboot to flash .img's to specific partitions...
2 Options: Restore the LAF mode on Fastboot to use KDZ or manualy search the Codefire Directory to Flash .img
Remember: LAF on LG's react the same as Samsung Download Mode, as well as their .KDZ/.TAR File Extentions.
Greetings!!!!:good:
pelelademadera said:
you need a working phone to do that.
But the way was the reverse:
Code:
adb shell
su
dd if=/file/you/have/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
if your phone is not working, you need to use boarddiag
Click to expand...
Click to collapse
where does the laf.img file have to be? my fastboot doesn't work for some reason and i'm trying to get back to download mode -- phone & recovery working.
stej16 said:
where does the laf.img file have to be? my fastboot doesn't work for some reason and i'm trying to get back to download mode -- phone & recovery working.
Click to expand...
Click to collapse
/dev/block/platform/msm_sdcc.1/by-name/laf
Enviado desde mi ZTE A2017G mediante Tapatalk
pelelademadera said:
/dev/block/platform/msm_sdcc.1/by-name/laf
Enviado desde mi ZTE A2017G mediante Tapatalk
Click to expand...
Click to collapse
not working. when i look in the root browser , there's no Block folder, just a file. the ADB command line to pull the laf.img sent it to my SDcard directory.. Can i command line from there? if possible , can i have that command line? sorry i am not good with commands.
stej16 said:
not working. when i look in the root browser , there's no Block folder, just a file. the ADB command line to pull the laf.img sent it to my SDcard directory.. Can i command line from there? if possible , can i have that command line? sorry i am not good with commands.
Click to expand...
Click to collapse
You must get there with root permissions, and to dump it, it must be done from terminal, or adb...
Enviado desde mi ZTE A2017G mediante Tapatalk
Perhaps this guide will help fellow YU's users who want to downgrade their YU from Lollipop to KitKat (OR FROM OTHER ROMs UNDER THE SAME PARTITION TABLE):
Download KitKat fastboot images from HERE.
Download fastboot.zip from HERE.
Extact all zips in ONE EMPTY FOLDER.
Open "Terminal Window" from the folder where you extracted all the zip files (right click your mouse and choose "Open command window here"):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Put your phone into fastboot mode (disconnect the phone from PC, turn off the phone, and connect the phone to PC WHILE PRESSING VOLUME UP BUTTON).
After the phone is connected go to the "Terminal Window" you have opened previously, type all the command below (ONE LINE AT A TIME) and make sure you get an "OKAY" feedback:
Code:
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf erase modem
fastboot -i 0x1ebf erase boot
fastboot -i 0x1ebf erase recovery
fastboot -i 0x1ebf erase aboot
fastboot -i 0x1ebf erase abootbak
fastboot -i 0x1ebf erase hyp
fastboot -i 0x1ebf erase hypbak
fastboot -i 0x1ebf erase rpm
fastboot -i 0x1ebf erase rpmbak
fastboot -i 0x1ebf erase sbl1
fastboot -i 0x1ebf erase sbl1bak
fastboot -i 0x1ebf erase tz
fastboot -i 0x1ebf erase tzbak
fastboot -i 0x1ebf format system
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf flash modem NON-HLOS.bin
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash sbl1bak sbl1.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash abootbak emmc_appsboot.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash rpmbak rpm.mbn
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash tzbak tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash hypbak hyp.mbn
fastboot -i 0x1ebf flash boot boot.img
fastboot -i 0x1ebf flash recovery recovery.img
fastboot -i 0x1ebf flash system system.img
fastboot -i 0x1ebf reboot-bootloader
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf reboot
Welcome back to KitKat, easy wasn't it.
Hi Quakze, could you post this procedure at YU's official forum website, as I don't have access there. I'm hopping that more YU's owner will help our mission in forcing official from YU Televentures to release all source code, include all Qualcomm signed mbn files.
------------------- Edit ----------------------
Since a lot YU's users in this thread have been insisting for a simple FLASH_ALL.bat file, so here is it. Extract it to the same folder you extracted fastboot.zip and KitKat fastboot images. However, please keep in mind that I don't recommend to use the bat file, and I am not responsible for bricked devices.
Does this really work?
rahulsingh616 said:
Does this really work?
Click to expand...
Click to collapse
Yes, of course, but please do the guide in order.
is bootloader unlock is mandatory??
Anybody tried that?!
will it hard brick the device??
i heard that infact i myself hard bricked before while downgrading from lollipop to kitakt..
jogson said:
i heard that infact i myself hard bricked before while downgrading from lollipop to kitakt..
Click to expand...
Click to collapse
Just tried it works perfect thanks bro @tirta.agung
Uh a few screenshots of this working would be better since most official mods of yuforums advise against using fastboot when upgrading from KitKat to lollipop and downgrading from lollipop to KitKat. If this works then it is really great work. Thank you. I can now try lollipop and go back to KitKat if not happy with it.
Sent from tomato using Tapatalk
baggu1984 said:
is bootloader unlock is mandatory??
Click to expand...
Click to collapse
Yes, you can't flash anything with a lock bootloader.
3andala said:
Just tried it works perfect thanks bro @tirta.agung
Click to expand...
Click to collapse
Thanks 3andala, I'm happy to help.
roy92 said:
Uh a few screenshots of this working would be better since most official mods of yuforums advise against using fastboot when upgrading from KitKat to lollipop and downgrading from lollipop to KitKat. If this works then it is really great work. Thank you. I can now try lollipop and go back to KitKat if not happy with it.
Click to expand...
Click to collapse
What kind of screenshota that you need? I'll be happy if I could help you.
tirta.agung said:
Thanks 3andala, I'm happy to help.
What kind of screenshota that you need? I'll be happy if I could help you.
Click to expand...
Click to collapse
It works for 3andala. I guess that is proof enough. Thank you for finding a clean way to revert to KitKat.
I guess you could upload desktop screenshot of the cmd window with executed commands. A photo of device first running on Lollipop and then on KitKat would be great.
Also did you try flashing cm 12 ota again after going back to KitKat?? Does it work??
Sent from tomato using Tapatalk
roy92 said:
It works for 3andala. I guess that is proof enough. Thank you for finding a clean way to revert to KitKat.
I guess you could upload desktop screenshot of the cmd window with executed commands. A photo of device first running on Lollipop and then on KitKat would be great.
Also did you try flashing cm 12 ota again after going back to KitKat?? Does it work??
Sent from tomato using Tapatalk
Click to expand...
Click to collapse
Hahahahahah, you won't believe this, but I'll post the screenshots tomorrow.
tirta.agung said:
Hahahahahah, you won't believe this, but I'll post the screenshots tomorrow.
Click to expand...
Click to collapse
Thank you[emoji5]
It's just that many bricked devices are floating around and not being able to properly revert back and forth to 32 bit builds and 64 bit builds is the only reason I haven't upgraded to lollipop yet.
KitKat is still the best with full xposed support and arm v7 is better supported by media players.
Sent from tomato using Tapatalk
Request
Can you make a file like flash-all.bat to do everything automatically other than typing the commands?
Help appreciated
onlyoneaamir said:
Can you make a file like flash-all.bat to do everything automatically other than typing the commands?
Help appreciated
Click to expand...
Click to collapse
It's very easy to do so. But not recommended. Read OP's post again. You need to get OK confirmation after every step before moving on to next. So suppose a command to erase system fails but the script proceeds to flash system image it might brick your device.
The chances of this happening are very very low. But it is important that you follow the step of commands exactly and also get OK confirmation that every command is successfully executed.
Edit: To quote the OP:
tirta.agung said:
[*]After the phone is connected go to the "Terminal Window" you have opened previously, type all the command below (ONE LINE AT A TIME) and make sure you get an "OKAY" feedback
Click to expand...
Click to collapse
Sent from tomato using Tapatalk
Points to remember?
I'm running official cm12 updated via ota with xposed . I have a nandroid backup . If something goes wrong can i restore using the backup. What are the chances of HARD bricking?
Many people have hard bricked the phone by downgrading ( the whole 64 bit, 34 bit confusion)
Awesome!
@tirta.agung
thanks man, works like a charm!! i dont think i'll be switching back until CM12 gets bug-ridden officially!
onlyoneaamir said:
Can you make a file like flash-all.bat to do everything automatically other than typing the commands?
Help appreciated
Click to expand...
Click to collapse
Nope, i don't think so. But, if you want to try it for yourself, just copy all commands to a text editor, for instance notepad or notepad++, and save it as flash-all.bat.
technowizard99 said:
I'm running official cm12 updated via ota with xposed . I have a nandroid backup . If something goes wrong can i restore using the backup. What are the chances of HARD bricking?
Click to expand...
Click to collapse
No, you can't use your CM12 (Lollipop) nand backup on CM 11 (kitkat), it will brick your YU.
technowizard99 said:
Many people have hard bricked the phone by downgrading ( the whole 64 bit, 34 bit confusion)
Click to expand...
Click to collapse
Just use my guide to downgrade your Lollipop back to Kitkat, but be sure to read carefully the guide and do the steps orderly. It works for me, and many others have also confirmed my method. By the way, I'm the OP of this THREAD, so I know what I'm doing.
kane111 said:
@tirta.agung
thanks man, works like a charm!! i dont think i'll be switching back until CM12 gets bug-ridden officially!
Click to expand...
Click to collapse
Thank you, glad that I could help.
Can I copy paste the commands?
I'm just being paranoid. But can i copy paste the commands?
technowizard99 said:
I'm just being paranoid. But can i copy paste the commands?
Click to expand...
Click to collapse
yes you can, i did the same!
When I enter in RUU mode (download mode) blue screen comes.
Before this I locked my bootloader to flash ota firmware,but it stuck on htc screen, then I relocked my bootloader but it gives me error.
Please help what to do?
are you soff?
blue screen error
plz some one help..
htc m9 asia tw
s-on
firmware update to 5.1 sudden mobile reset and now when it on after gives blue blank screen just....
just bootloader screen come while pressing vol + and vol - and power button. bt no recovery no download mode no RUU mode while going to download mode blue screen error plz someone help. what to do.
You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.
philicibine said:
You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.
Click to expand...
Click to collapse
fastboot command in bootloader screen gives error FAILED (remote: cannot flash this partition in s-on state)
please someone help to solve this problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This screen comes every time and reset htc logo and then same blue screen
Maybe try fastboot boot recovery.img and see if that works??
philicibine said:
Maybe try fastboot boot recovery.img and see if that works??
Click to expand...
Click to collapse
FAILED (remote: Not allow when s-on)
mnhs1010 said:
When I enter in RUU mode (download mode) blue screen comes.
Before this I locked my bootloader to flash ota firmware,but it stuck on htc screen, then I relocked my bootloader but it gives me error.
Please help what to do?
Click to expand...
Click to collapse
Is your error solved or are you still stuck with the blue screen as I am also the effected
LineArc said:
Is your error solved or are you still stuck with the blue screen as I am also the effected
Click to expand...
Click to collapse
Still same problem dear blue screen...
mnhs1010 said:
Still same problem dear blue screen...
Click to expand...
Click to collapse
Maybe u should take a look here their potential is to recover ur device with some fund ....better than going to HTC and screwing up alot of money
sa3d12 said:
Maybe u should take a look here their potential is to recover ur device with some fund ....better than going to HTC and screwing up alot of money
Click to expand...
Click to collapse
did your problem solved >>>>>
mnhs1010 said:
did your problem solved >>>>>
Click to expand...
Click to collapse
U mean you solved your problem or you are asking me? ..
Anyway i dont have problems with my device
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
Click to expand...
Click to collapse
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
I think you only need to flash the hosd
VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse
Thanks a lot! You have been avoided a heart attack hehe!
You my friend are a star... I thought my HTC M9 was a brick for sure.
Just to add people, remember do not try and copy through ADB installer (As I did to begin with)... It will not detect your phone... Use the Fastboot application within CMD.
VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse
VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse
does anyone have for m9 verizon ?
@VashSV, I already pressed thanks button but want to write and say thanks to you. You save my phone. Happy new year 2017
Many many many thanks to you!!! I what in this blue screen loop, thanks to your commande list I managed to write .img by .img, you are the boss.
Exact same problem
philicibine said:
You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.
Click to expand...
Click to collapse
Hello, a bit late but I have the exact same problem with my HTC one M9, can you please help me? I am s-off, unlocked and my phone is T-MOB010 with N7 corrupted firmware :/ pleaseeee
Hi guys, finally I succed in relock my XT1685 Bootloader on RETEU, so I will guide you to relock your bootloader.
DISCLAIMER:
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
YOU are choosing to make these modifications,
and if you point the finger at me for messing up your device, I will laugh at you.
and I am also not responsible for anything happens as a result of flashing these files
What you need :
1- Motorola drivers :
64-bit
32-bit
2- Minimal ADB and Fastboot:
Minimal ADB and Fastboot
3- Stock Fastboot flashable official firmware.
Here is the donwload of NPNS25.133-37-11 it should be perfect for lock BL for all RETEU users:
Mirror 1 (MEGA)
Mirror 2 (GoogleDrive)
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
Now let's start with the guide.
1- Install Minimal ADB and Fastboot.
2- Extract stock firmware to any folder.
3- Now copy all the stuff that is in Minimal ADB and Fastboot folder in the folder where you extract the firmware.
4- Connect your device in fastboot mode (power off the device and while you press VOL down button insert the USB cable).
5- Open ADB and Fastboot terminal (press SHIFT+right click on the folder where you extract the firmware and select "open command window here").
6- Now type in Fastboot terminal "fastboot devices" (without commas) to be sure that your device is recognized.
7- Type these command one by one on terminal
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Now your device will restart and your BL will be locked.
Now for be sure reflash all the complete firmware repeat the point from 5 to 7 but insert this code now
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Now you will be able to receive the OTA update with your locked BL.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to @Nirbhay2
aSaro12 said:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Click to expand...
Click to collapse
Thank you!
I like to comment that these two topics are the key points to do it right. :highfive:
manos78 said:
Thank you!
I like to comment that these two topics are the key points to do it right. :highfive:
Click to expand...
Click to collapse
Yes, this is a little but important thing. :good::good:
Duplicate Thread
Read before posting
There is already thread for relocking bootloader : https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835
siddhesh9146 said:
Duplicate Thread
Read before posting
There is already thread for relocking bootloader : https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835
Click to expand...
Click to collapse
That thread is specific for Indian Variant.
And if you read carrefully I've mentioned the writer of the thread that you've posted.
Thank you!!
That worked perfectly on XT1685. Much appreciated.
Thanks
It's works. I'm successfully re-locked my bootloader. But i have a question.
Can i get OTA updates if bootloader says me "Software status: Modified"?
SeRi0uS007 said:
It's works. I'm successfully re-locked my bootloader. But i have a question.
Can i get OTA updates if bootloader says me "Software status: Modified"?
Click to expand...
Click to collapse
My Software status is also Modified and I never got ota's I always had to manually clean flash stock images. If someone found a way I would love to know how to get ota's on stock rom.
Thank you. my phone can get OTG now.
I tried yesterday on a XT1685 with the RETAIL firmware... and I broke something because my g5 plus cannot connect to GSM anymore (PIN asked but no LTE and no call possible). Bootloader is locked so I try to send back my phone to amazon for repair (exchange)... Sometimes **** happens !
pfufux said:
I tried yesterday on a XT1685 with the RETAIL firmware... and I broke something because my g5 plus cannot connect to GSM anymore (PIN asked but no LTE and no call possible). Bootloader is locked so I try to send back my phone to amazon for repair (exchange)... Sometimes **** happens !
Click to expand...
Click to collapse
same as here... revert back to stock but no signal..
i had xt1685 RETAIL too.. what did you flashed?
what happen with Amazon?
tufoz said:
same as here... revert back to stock but no signal..
i had xt1685 RETAIL too.. what did you flashed?
what happen with Amazon?
Click to expand...
Click to collapse
I don't remember what I flashed... but I think it's what I found in this post (NPNS25.133-37-11). I sent my phone to Amazon (fr) and it should be back today; I think I won't try again to flash Lineage or other because it seems to cause some troubles with IMEI when returning to stock, as I saw here and here.
pfufux said:
I don't remember what I flashed... but I think it's what I found in this post (NPNS25.133-37-11). I sent my phone to Amazon (fr) and it should be back today; I think I won't try again to flash Lineage or other because it seems to cause some troubles with IMEI when returning to stock, as I saw here and here.
Click to expand...
Click to collapse
My phone is back with a new motherboard... and so, a new IMEI. More details :
BASEBAND : M8953_37.46.07.47R POTTER_EMEADSDS_CUST
BUILD : NPN25.137-93
pfufux said:
My phone is back with a new motherboard... and so, a new IMEI. More details :
BASEBAND : M8953_37.46.07.47R POTTER_EMEADSDS_CUST
BUILD : NPN25.137-93
Click to expand...
Click to collapse
Everyone else is getting the 137-92 update, why does yours say 137-93?
I don't know but the update came from OTA.
pfufux said:
I don't know but the update came from OTA.
Click to expand...
Click to collapse
you confirm me that amazon replaced your phone? i think i will do the same thing
Ok .. i tried the procedure again.. I used 137.33.11 cid 50 NPNS but i got this error messages..
when flashing system: invalid signed image
when flashing bootloader "security downgrade version"...
any hint?
tufoz said:
you confirm me that amazon replaced your phone? i think i will do the same thing
Click to expand...
Click to collapse
I confirm Amazon changed the motherboard of my phone. I have a new IMEI number.
I can't re lock bootloader
Hi, i am trying to install stock rom and relock bootloader because after installing custom rom, i am not getting network in my device. but now after installing stock rom(see below image for version), i cant relock my bootloader. it gives me error like security downgrade issue.
Thanks a lot
:good::good::good::good:
the indian variant relock is not correctly explained
You Have Explained It
Listen all
You will need the firmware which you were using before unlocking your bootloader then only you can relock it again
Now i can give it for warranty Thanks a Lot
Hello,
I'm trying to help my little sister with her phone, she has a Xiaomi REDMI Note 8 PRO with a stock rom, never flashed.
A few days ago her phone shut down for no reason with the battery at 80%, and now there is a boot loop :/
Can you help me ?
Do you have any ideas to solve this problem ?
But I think it is impossible to connect the phone to a computer because it instantly buckles...
RS MAN said:
Hello,
I'm trying to help my little sister with her phone, she has a Xiaomi REDMI Note 8 PRO with a stock rom, never flashed.
A few days ago her phone shut down for no reason with the battery at 80%, and now there is a boot loop :/
Can you help me ?
Do you have any ideas to solve this problem ?
But I think it is impossible to connect the phone to a computer because it instantly buckles...
Click to expand...
Click to collapse
1. You need to download the adb fasrboot drivers and Android platform tolls on your pc if you haven't done this already
2. Download latest STABLE MIUI Fastboot ROM for REDMI 8 PRO
3. Once you download this file. You will need to extract the boot.img, vendor.img, cust.img, and recovery.img...
You will need to reset the phone before flashing these files via fastboot
Nameless Foe said:
1. You need to download the adb fasrboot drivers and Android platform tolls on your pc if you haven't done this already and also unlock the bootloader
2. Download latest STABLE MIUI Fastboot ROM for REDMI 8 PRO
3. Once you download this file. You will need to extract the boot.img, vendor.img, cust.img, and recovery.img...
You will need to reset the phone before flashing these files via fastboot
Click to expand...
Click to collapse
RS MAN said:
Hello,
I'm trying to help my little sister with her phone, she has a Xiaomi REDMI Note 8 PRO with a stock rom, never flashed.
A few days ago her phone shut down for no reason with the battery at 80%, and now there is a boot loop :/
Can you help me ?
Do you have any ideas to solve this problem ?
But I think it is impossible to connect the phone to a computer because it instantly buckles...
Click to expand...
Click to collapse
Make sure you unlock the bootloader also
Nameless Foe said:
1. You need to download the adb fasrboot drivers and Android platform tolls on your pc if you haven't done this already
2. Download latest STABLE MIUI Fastboot ROM for REDMI 8 PRO
3. Once you download this file. You will need to extract the boot.img, vendor.img, cust.img, and recovery.img...
You will need to reset the phone before flashing these files via fastboot
Click to expand...
Click to collapse
Thank you for your help.
I cannot flash the phone because it is locked :/
I have a question, Locked = root mode ?
I can't unlock the phone with the official app because my sister didn't create an official Xiaomi account !
RS MAN said:
Thank you for your help.
I cannot flash the phone because it is locked :/
I have a question, Locked = root mode ?
I can't unlock the phone with the official app because my sister didn't create an official Xiaomi account !
Click to expand...
Click to collapse
Here is a guide for you
Redmi Note 8 Got Into Bootloop? Try This to Fix It | MIUI Blog
Bootloop is a situation where you cannot get into the normal Android system. This usually happens after flashing something through either bootloader mode or
miui.blog
I'm stuck on the bootloader.
Another problem, I can only connect the phone to PC for 2-3 seconds, after it reboots by itself.
He also loops in fastboot...
This problem comes from the latest official update from Xiaomi...
I think he's dead, right ?
If the phone is not stable in fastboot, is there no solution ?
What do you think ?
RS MAN said:
I'm stuck on the bootloader.
Another problem, I can only connect the phone to PC for 2-3 seconds, after it reboots by itself.
He also loops in fastboot...
This problem comes from the latest official update from Xiaomi...
I think he's dead, right ?
If the phone is not stable in fastboot, is there no solution ?
What do you think ?
Click to expand...
Click to collapse
Give me a few minutes. I'll be home in a few minutes. I'm getting off work
Hello, this is the problem !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to delete the following line, but I got an error again !
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *begonia" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *begonia" || exit /B 1
fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
Try MiFlashPro using RECOVERY.
Mi Flash Pro
Mi Flash Pro helps you to Manage your Xiaomi Smartphone. It helps you to Download Firmware, Flash Firmware, Flash Recovery.
miflashpro.com
Thanks, I'm going to try !
RS MAN said:
Thanks, I'm going to try !
Click to expand...
Click to collapse
If your device is locked, you can't downgrade the system.
So, you need to flash the same or greater versions.
Good luck
Ok thank you, but I don't know the version :/
Is it possible to see the IMEI in command line ?
RS MAN said:
Ok thank you, but I don't know the version :/
Click to expand...
Click to collapse
It will be detected by the MiFlashPro tool.
RS MAN said:
Is it possible to see the IMEI in command line ?
Click to expand...
Click to collapse
Yes. Just type
Code:
fastboot getvar all
VD171 said:
Yes. Just type
Code:
fastboot getvar all
Click to expand...
Click to collapse
Sorry for the question but, I start CMD in official MiFlash to use fastboot and command ?
RS MAN said:
Sorry for the question but, I start CMD in official MiFlash to use fastboot and command ?
Click to expand...
Click to collapse
You can use just the fastboot binary.
Here, you can find the MINIMAL ADB AND FASTBOOT: https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Just extract it and open cmd in this folder.
And then, type:
Code:
fastboot.exe getvar all
Here, you can find the great guide for how to get and install latest adb and fastboot from google sources by @jwoegerbauer :
https://forum.xda-developers.com/t/...latest-official-adb-fastboot-drivers.4185535/
I didn't see the IMEI, but I saw:
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) crc: 1
(bootloader) kernel: lk
(bootloader) product: begonia
(bootloader) is-userspace: no
(bootloader) slot-count: 0
(bootloader) version-baseband: MOLY.LR13.R1.TC8.SP.V2.P44
(bootloader) version-bootloader: begonia-cc1ef31-20200924105739-20210118
(bootloader) version-preloader:
(bootloader) version: 0.5