1st comes 1st lg ls740 this is to backup the laf partition, i recomend yall bakup,recovery an boot as well just in case
Note: This assumes you've already rooted manually or with Towelroot and know what adb/fastboot is.
First, backup your LG Download mode (laf) with this code, so you can use LG Flash if necessary.(make sure phone is on and pluged in and android debuging is enabled
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img.
Run the following code to zero out laf:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(i did this and my volt told me the memory was full but this still got me into fastboot
adb reboot
For whatever reason, you won't be able to access fastboot via "reboot to bootloader" like most phones, so you've got to do a key combo:
Power Off
Unplug USB
Hold Volume Up
Plug in USB
step 2
fastboot oem device-info
should look something like this ...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.012s]
finished. total time: 0.013s
step 3, fastboot oem unlock
should look like this,
...
OKAY [ 0.004s]
finished. total time: 0.005s
DO NOT skip this step before shutting off or rebooting the phone
WHEN YOU ARE DONE IN FAST BOOT MAKE SURE TO RESTORE THE LAF.IMG
fastboot flash laf laf.img
p.s if you backup your laf.img make sure to move it off of the internal storage to the sd card or computer or you will not be able to acsess it
notreal456789 said:
1st comes 1st lg ls740 this is to backup the laf partition, i recomend yall bakup,recovery an boot as well just in case
Note: This assumes you've already rooted manually or with Towelroot and know what adb/fastboot is.
First, backup your LG Download mode (laf) with this code, so you can use LG Flash if necessary.(make sure phone is on and pluged in and android debuging is enabled
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img.
Run the following code to zero out laf:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(i did this and my volt told me the memory was full but this still got me into fastboot
adb reboot
For whatever reason, you won't be able to access fastboot via "reboot to bootloader" like most phones, so you've got to do a key combo:
Power Off
Unplug USB
Hold Volume Up
Plug in USB
step 2
fastboot oem device-info
should look something like this ...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.012s]
finished. total time: 0.013s
step 3, fastboot oem unlock
should look like this,
...
OKAY [ 0.004s]
finished. total time: 0.005s
DO NOT skip this step before shutting off or rebooting the phone
WHEN YOU ARE DONE IN FAST BOOT MAKE SURE TO RESTORE THE LAF.IMG
fastboot flash laf laf.img
p.s if you backup your laf.img make sure to move it off of the internal storage to the sd card or computer or you will not be able to acsess it
Click to expand...
Click to collapse
One question is it to unlock the phone from a carrier?
Juniluis said:
One question is it to unlock the phone from a carrier?
Click to expand...
Click to collapse
What kind of unlock is this??? Does this allow sim unlock?
???
What??
I'm confused. Is this to unlock the phone to use it in any carrier?
Bootloader unlock sounds like.
Sent from my HUAWEI Y536A1 using XDA Free mobile app
So i have both the short story with some important explanation and the long story on what I've already tried.
Short story
So my dad bought a oneplus one 16GB from someone and the phone has a bootloop when you try the boot into the system.
I tried to unlock the bootloader, but it runned the command and it just reboots to recovery and the bootloader is still locked.
Also the tamperflag is true so that means that the bootloader has already been unlocked and is relocked.
I can't also boot from a custom recovery image because the bootloader is locked (I think it can with CM11S).
Rom: I guess it is CM12S (with the blinking Cyanogen logo at startup).
Recovery: probably the recovery from CM12S (Cyanogen recovery as text and it is a touch recovery).
Long story
So I am going to tell you my story.
My dad bought an oneplus one (16GB) from someone that had a boot loop at startup.
When he told me that I just thought that it was going to be pretty easy to fix: unlock bootloader, flash custom recovery and install a custom rom.
Now, it didn’t roll out as we both expected.
When I unlocked the bootloader it told me after 10 seconds that it was OK.
Pretty weird was that it took so long.
After some research I found that you need to reboot from the rom with adb and that you then can unlock the bootloader. On all my other devices I did that, but now I couldn’t because I wasn’t able to boot inside the rom.
After I “successfully” unlocked the bootloader I did the command “fastboot oem device-info” and it told me that the bootloader was still locked but it was tampered.
I tried after that to boot from a TWRP recovery image but i wasn't able to because the bootloader was locked.
After some research I came at a post on the oneplus forum with a guy that approximately had the same issue except that I can still go into recovery.
I founded this post.
And I first wanted to see if I couldn’t go into recovery and sideload a zip that is signed. That was signed in this thread.
As it expected because I didn’t had a custom recovery it didn’t worked and also I used this tool for adb and fastboot.
I didn’t give up by that one so easily so I tried it with this to sideload the files and I renamed it this time to update.zip. Again as expected an error but this time it was another error.
There came a bunch of errors on the phone especially cache errors and one that said that I had an outdated ADB (at least version 1.0.32).
Weirdly enough I had version 1.0.32 .
And now it tried the trick they told me here.
From the thread for windows 7 and 8 here.
I first did this without “erasing the bootloader”.
I tried this both on windows 8.1 and on windows xp with both administrator rights and I switched between 3 cables each time.
As you see in the attached zip, I correctly installed the driver, this was also the fact for the pc with windows xp.
I also verified the files but there were some that failed (also in the pictures).
It flashes the file 8974_msimage.mbn and then the phone shuts down. I tried this at least three times for each computer.
Then I founded this thread.
And tried this also and exactly the same problem as with color.
Then I tried the same with erasing the bootloader and it had the same issue and I couldn’t erase the bootloader doing to that my partition table doesn’t exist(also in the pictures).
The only thing that I only think that I can do is with a flash tool that uses also the above method but I don’t find any with that I know how to use it.
Any help is appreciated.
Ps: I attached a zip file with some pictures to make it more clear and understandable and i am also dutch, so sorry if my English is bad.
ninjawulf98 said:
So I am going to tell you my story.
My dad bought an oneplus one (16GB) from someone that had a boot loop at startup.
When he told me that I just thought that it was going to be pretty easy to fix: unlock bootloader, flash custom recovery and install a custom rom.
Now, it didn’t roll out as we both expected.
When I unlocked the bootloader it told me after 10 seconds that it was OK.
Pretty weird was that it took so long.
After some research I found that you need to reboot from the rom with adb and that you then can unlock the bootloader. On all my other devices I did that, but now I couldn’t because I wasn’t able to boot inside the rom.
After I “successfully” unlocked the bootloader I did the command “fastboot oem get-lockstate” and it told me that the bootloader was locked but it was tampered.
Sadly enough when I typed the command now it takes forever to answer, after more than 10 minutes it still displays that it is waiting.
After some research I came at a post on the oneplus forum with a guy that approximately had the same issue except that I can still go into recovery.
I founded this post.
And I first wanted to see if I couldn’t go into recovery and sideload a zip that is signed. That was signed in this thread.
As it expected because I didn’t had a custom recovery it didn’t worked and also I used this tool for adb and fastboot.
I didn’t give up by that one so easily so I tried it with this to sideload the files and I renamed it this time to update.zip. Again as expected an error but this time it was another error.
There came a bunch of errors on the phone especially cache errors and one that said that I had an outdated ADB (at least version 1.0.32).
Weirdly enough I had version 1.0.32 .
And now it tried the trick they told me here.
From the thread for windows 7 and 8 here.
I first did this without “erasing the bootloader”.
I tried this both on windows 8.1 and on windows xp with both administrator rights and I switched between 3 cables each time.
As you see in the attached zip, I correctly installed the driver, this was also the fact for the pc with windows xp.
I also verified the files but there were some that failed (also in the pictures).
It flashes the file 8974_msimage.mbn and then the phone shuts down. I tried this at least three times for each computer.
Then I founded this thread.
And tried this also and exactly the same problem as with color.
Then I tried the same with erasing the bootloader and it had the same issue and I couldn’t erase the bootloader doing to that my partition table doesn’t exist(also in the pictures).
The only thing that I only think that I can do is with a flash tool that uses also the above method but I don’t find any with that I know how to use it.
Any help is appreciated.
Ps: I attached a zip file with some pictures to make it more clear and understandable and i am also dutch, so sorry if my English is bad.
Click to expand...
Click to collapse
Are you able to enter fastboot mode now?
Bobbi lim said:
Are you able to enter fastboot mode now?
Click to expand...
Click to collapse
Yes, i can also enter stock recovery but i am unable to boot from custom recovery through fastboot. Because the bootloader is locked.
ninjawulf98 said:
Yes, i can also enter stock recovery but i am unable to boot from custom recovery through fastboot. Because the bootloader is locked.
Click to expand...
Click to collapse
Have you tried "fastboot oem unlock" in fastboot mode?
Sent from my Nexus 7 using Tapatalk
Bobbi lim said:
Have you tried "fastboot oem unlock" in fastboot mode?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes, after - + 10 seconds it says ok and it reboots the phone to the stock recovery.
When i try to flash twrp it just fails because my bootloader is locked.
ninjawulf98 said:
Yes, after - + 10 seconds it says ok and it reboots the phone to the stock recovery.
When i try to flash twrp it just fails because my bootloader is locked.
Click to expand...
Click to collapse
Which stock recovery is it? ColorOS? CM? Or OxygenOS?
I had a similar issue when I tried to unlock mine when I first got my OPO
Sent from my Nexus 7 using Tapatalk
My dad bought the phone from someone and the only thing i can see is cyanogen recovery. At boot i have a blinking cyanogen text. Probably it was already unlocked because the tamper flag is tampered.
ninjawulf98 said:
My dad bought the phone from someone and the only thing i can see is cyanogen recovery. At boot i have a blinking cyanogen text. Probably it was already unlocked because the tamper flag is tampered.
Click to expand...
Click to collapse
Maybe my previous post was a bit confusing but it is still locked, i meant that the previous owner locked it and then relocked it.
Can you tell us the exact copy/paste and output of below command :
fastboot oem device-info
Regards
Girish Sharma
GirishSharma said:
Can you tell us the exact copy/paste and output of below command :
fastboot oem device-info
Regards
Girish Sharma
Click to expand...
Click to collapse
I've got the following:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle rechten voorbehouden.
C:\Windows\System32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Windows\System32>
I am not sure but, what if you paste the output of fastboot oem unlock from the adb folder, I.e just try to run the command from that directory in which fastboot.exe present. Just paste the output as you done previously.
Regards
Girish Sharma
GirishSharma said:
I am not sure but, what if you paste the output of fastboot oem unlock from the adb folder, I.e just try to run the command from that directory in which fastboot.exe present. Just paste the output as you done previously.
Regards
Girish Sharma
Click to expand...
Click to collapse
Then i've got the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
866878f3 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 10.112s]
finished. total time: 10.114s
C:\Program Files (x86)\Minimal ADB and Fastboot>
And when i do the command: "fastboot oem device-info" again.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Program Files (x86)\Minimal ADB and Fastboot>
ninjawulf98 said:
Then i've got the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
866878f3 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 10.112s]
finished. total time: 10.114s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
I don't know if this is an issue but i have both the adb and fastboot tools installed from here and the adb, fastboot and drivers here .
Since I am not an android expert, so I shall wait with you to see other member replies. Between if you can check this link too:https://forums.oneplus.net/threads/stuck-in-fastboot-with-locked-boot-loader.104446/page-2
Regards
Girish Sharma
GirishSharma said:
Since I am not an android expert, so I shall wait with you to see other member replies. Between if you can check this link too:https://forums.oneplus.net/threads/stuck-in-fastboot-with-locked-boot-loader.104446/page-2
Regards
Girish Sharma
Click to expand...
Click to collapse
I already founded that thread and did the solution that worked for him and another solution that a guy a few posts above him mentioned. Sadly enough without any results.
Anyway, thanks for the help and all the effort you did!
I just am going to mention it here before I will do it, to avoid to make the situation more worse then it already is.
So you can enter qualcomm hsloader (connect the phone to the pc, press 5-10 seconds volume up + power, screen remains dark).
And there are two tools (which have both the same base) here and here .
Now, when I follow the guide for both tools, always when it flashes the first file (8974_msimage.mbn), after flashing the phone shuts down.
And yes, I gave it administrator rights and the drivers are properly installed.
I tried it also on windows xp (completly clean test computer, yes I have a lot of them )
Now I saw on the oneplus forum a post .
And when I tried the command "fastboot erase bootloader" it gave me the following output:
C:\Windows\System32>fastboot erase bootloader
erasing 'bootloader'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.006s
Well if I try this with the command to erase the kernel partition "fastboot erase boot" I think.
Well might this then work, so that the device after flashing the first file doesn't shutdown?
Again I just want to mention it here before I make the situation more worse then it already is.
ninjawulf98 said:
I just am going to mention it here before I will do it, to avoid to make the situation more worse then it already is.
So you can enter qualcomm hsloader (connect the phone to the pc, press 5-10 seconds volume up + power, screen remains dark).
And there are two tools (which have both the same base) here and here .
Now, when I follow the guide for both tools, always when it flashes the first file (8974_msimage.mbn), after flashing the phone shuts down.
And yes, I gave it administrator rights and the drivers are properly installed.
I tried it also on windows xp (completly clean test computer, yes I have a lot of them )
Now I saw on the oneplus forum a post .
And when I tried the command "fastboot erase bootloader" it gave me the following output:
C:\Windows\System32>fastboot erase bootloader
erasing 'bootloader'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.006s
Well if I try this with the command to erase the kernel partition "fastboot erase boot" I think.
Well might this then work, so that the device after flashing the first file doesn't shutdown?
Again I just want to mention it here before I make the situation more worse then it already is.
Click to expand...
Click to collapse
Now actually i think that the partition bootloader doesn't exists but boot does (which I think containts the bootloader and the kernel).
After waiting very unpationtly -+ 24 hours I tried it.
Sadly enough again without success.
CMD copy:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle rechten voorbehouden.
C:\Windows\System32>fastboot devices
866878f3 fastboot
C:\Windows\System32>fastboot erase boot
erasing 'boot'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.057s
C:\Windows\System32>
Fried emmc. Sell it for junk.
Sent from my SM-G920T
Hi,
I am stuck with a similar issue. Only the way I landed in this situation is slightly different.
Without unlocking the bootloader (I just forgot to do that!), I ran the below command.
Code:
fastboot format cache
It erased the cache but failed to write to it because the device is still locked.
On rebooting, the device was stuck overnight on the "Cyanogen" display screen.
I forcibly powered it off using the power button.
Then I fastbooted it.
Then from the command prompt I tried to run a few commands - see output below
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
finished. total time: 0.031s
And then this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock oem
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
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> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
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
and this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
That's it. For some reason,"fastboot unlock oem" takes me to fastboot help and "fastboot flashing unlock" just goes in a long endless wait.
Any way out?
Thanks,
Deepak Gupta
Deep.G said:
Hi,
I am stuck with a similar issue. Only the way I landed in this situation is slightly different.
Without unlocking the bootloader (I just forgot to do that!), I ran the below command.
Code:
fastboot format cache
It erased the cache but failed to write to it because the device is still locked.
On rebooting, the device was stuck overnight on the "Cyanogen" display screen.
I forcibly powered it off using the power button.
Then I fastbooted it.
Then from the command prompt I tried to run a few commands - see output below
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
finished. total time: 0.031s
And then this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock oem
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
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> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
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
and this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
That's it. For some reason,"fastboot unlock oem" takes me to fastboot help and "fastboot flashing unlock" just goes in a long endless wait.
Any way out?
Thanks,
Deepak Gupta
Click to expand...
Click to collapse
The command for unlocking the bootloader is "fastboot oem unlock" not "fastboot unlock oem".
Also sometimes when you type a commando that isn't recognised by the phone it can take forever.
So, I think that the commando "fastboot flashing unlock" doesn't exist.
Anyway I think I know now for sure that the previous owner erased and/or formatted the cache.
How to Unlock the bootloader of Micromax Canvas Pace 4G:
Note: Unlocking bootloader will erase all your user data including Internal Storage
1. Go to Settings/About Phone and tap some 7-8 times on "Build Number" to enable Developer options in Settings.
2. In developer option just select "OEM unlocking" and "USB debugging"
3. Install the device Drivers.
4. Install adb and fastboot tools (Download link below)
5. Go to adb and fastboot folder in C:\ drive and hold shift and right click and select "Open command window here"
6. Then connect ur device to the System and make sure u have USB debugging enabled.
7. Type "adb devices" to check if the device is connected.
8. You will get a prompt in your device asking permission to allow USB debugging just click OK and allow.
9. Type "adb devices" again to see if ur device is connected or not and if its connected it will show something like this:
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0123456789ABCDEF device
10. To reboot into fastboot mode use this command:
"adb reboot bootloader"
this will reboot the device in bootloader
11. Now to check if the device is connected in fastboot mode use this command:
"fastboot devices"
if its connected then u will get some output like this:
C:\adb>fastboot devices
85add0d3 fastboot
12. Now to unlock Bootloader use this command:
"fastboot oem unlock"
you will get an output like this:
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
13. Use this command right after oem unlock command:
"fastboot format userdata"
you will get an optput like this:
C:\adb>fastboot format userdata
Creating filesystem with partition
Size: 4730105856
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 18043
Label:
Blocks: 1154811
Block groups: 36
Reserved block group size
Created filesystem with 11/2
target reported max download
erasing 'userdata'...
OKAY [ 3.375s]
sending 'userdata' (75693 KB
OKAY [ 2.375s]
writing 'userdata'...
OKAY [ 1.625s]
finished. total time: 7.375s
14. To check if ur device bootloader is unlocked or not use this command:
"fastboot oem device-info"
you will see a screen like this:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
15. Now time to reboot the device into system, use this command:
"fastboot reboot"
16. Disconnect the device from system and wait for it to boot up.
It might take some 3-5 mins to boot up so no need to worry
Credits:
@Santosh M for guiding me
RESERVED
Nice Guide Bro Hope You Will Start Development Soon
charansai said:
Nice Guide Bro Hope You Will Start Development Soon
Click to expand...
Click to collapse
Started already... TWRP is coming in few mins
Excepted
vibhu0009 said:
Started already... TWRP is coming in few mins
Click to expand...
Click to collapse
Thinking May Be TWRP is under construction But U made It
charansai said:
Thinking May Be TWRP is under construction But U made It
Click to expand...
Click to collapse
my be u should check this out
http://forum.xda-developers.com/android/development/twrp-recovery-micromax-canvas-pace-4g-t3350469
vibhu0009 said:
my be u should check this out[emoji14]
http://forum.xda-developers.com/android/development/twrp-recovery-micromax-canvas-pace-4g-t3350469
Click to expand...
Click to collapse
Seen
Nothing to Comment
Just cool
Custom ROM for q416
may I try it on my micromax Q415
Android 6.0.1
Android security patch level
February 1, 2017
Baseband version
.Jo.1.2.c3-00154-8909_GEN_PACK-1
Kernel Version
3.10.49
[email protected]#2
Sat Mar 4 20:28:24 CST 2017
Build number
MMX_Q415_IND_SW_V3.3_HW_V0.2_04032017
Hello sir
Give twrp link for
Micromax evok dual note E 4815
Or
Write the twrp verson / mobile modal
Micromax Canvas Magnus (a117)
Micromax Canvas Pace 4G (pace)
Because official site provide only
2 modal twrp of micromax.
---------- Post added at 04:58 AM ---------- Previous post was at 04:54 AM ----------
vibhu0009 said:
RESERVED
Click to expand...
Click to collapse
Hello sir
Give twrp link for
Micromax evok dual note E 4815
Or
Write the twrp verson / mobile modal
Micromax Canvas Magnus (a117)
Micromax Canvas Pace 4G (pace)
Because official site provide only
2 modal twrp of micromax
Hello,
I am trying to reverse engineer my phone that won't allow me to flash the partitions with an img file I took using DD. I have the following issue-
Code:
[[email protected] platform-tools]# ./fastboot flash system system.img
target reported max download size of 1073741824 bytes
Invalid sparse file format at header magi
erasing 'system'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.017s
[[email protected] platform-tools]#
[[email protected] platform-tools]# ./fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.027s]
finished. total time: 0.027s
[[email protected] platform-tools]# ./fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.012s
[[email protected] platform-tools]#
The first thing I did when I set up the phone was make sure it was unlocked in developer options.
OEM unlocking
Allow the bootloader to be unlocked
(with the slider moved over to the right)
It's almost like the settings conflict with each other. Any ideas on this? It looks like even though it is on in developer options doesn't mean that it will work in ADB. The proof is in the pudding as they say.
According to the research I have done, I am also seeing that with many phones you must set the option in fastboot mode after setting this in developer options.
I tried to compare/diff the aboot image partition in a hex editor but it did not show any differences in them. To do this I started out with the option set locked and took a DD image of aboot. I then restarted the phone and set the option to unlock and took a second DD image.
I have a full backup of all partitions of the phone and could post any additional info you need.
Turns out the easier solution is using a tool to flash the phone properly rather than unlock the bootloader. I should have realized when I wasn't getting a response that I was going down the wrong track. Now to get MPRG8909.hex and 8909_msimage.mbn files........
so i am trying to unlock bootloader in my device tecno spark 8c i enter the fastboot mode and tried the command fastboot oem unlock it say message ok but nothing happenes if i try to flash the vbmeta it says the bootloader locked and need to be unlocked how to unlock it?
What happened is that you got a OK, means phone's bootloader now got unlocked.
To deal with bootloader you run Fastboot commands from the Windows shell, either CMD or PowerShell.
no it didnt get unlock it only say message ok
i tried this command fastboot getvar unlocked
which give me message unlocked:no and i am running linux so i am using its commandline working with it and as i say it didnt get unlocked what is the problem i cant figure it out
jwoegerbauer said:
What happened is that you got a OK, means phone's bootloader now got unlocked.
To deal with bootloader you run Fastboot commands from the Windows shell, either CMD or PowerShell.
Click to expand...
Click to collapse
[[email protected]]-[~]
>>> adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
[[email protected]]-[~]
>>> adb reboot bootloader
error: insufficient permissions for device
See [http://developer.android.com/tools/device.html] for more information
[[email protected]]-[~]
>>> adb reboot bootloader
[[email protected]]-[~]
>>> fastboot oem unlock
< waiting for any device >
FAILED (remote: 'Unlock bootloader fail.')
fastboot: error: Command failed
[[email protected]]-[~]
>>> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.018s]
< waiting for any device >
Finished. Total time: 17.010s
[[email protected]]-[~]
>>> fastboot oem unlock
OKAY [ 0.001s]
Finished. Total time: 0.001s
[[email protected]]-[~]
>>> fastboot getvar unlocked
unlocked: no
Finished. Total time: 0.001s
[[email protected]]-[~]
>>>
here is the commands and the output as u see and i already enabled oem in the developer options
Reboot Android to make changes permanent
jwoegerbauer said:
Reboot Android to make changes permanent
Click to expand...
Click to collapse
u mean reboot after i did the command?
i did it nothing change
try this method
https://forum.xda-developers.com/t/is-my-life-really-worth-it.4217751/post-84295797
fastboot flashing unlock