Database Users

[help][L7] Secure booting error on recovery?

Hi guys. I have a small problem with my LG L7.
My phone had stock rom with prerooted v10k rom. (no unlocked bootloader,no cwm)
I tried to flash the bootloader from the L7CWM.zip bat,and there was no error.
I didn't flash the recovery from the .bat,i installed it from ROM Manager and everything well.
Now the phone works,but if i try to enter recovery i get a this error:
Secure booting error!
Cause: boot certification verify
Why? I thought the bootloader was unlocked.
ROM Manager says I have the ClockworkMod 6.0.2.8,but I can't boot on it.

Solved. I just reflashed the bootloader 2 times,installed the cwm from the .bat and then again from ROM Manager.
Now everything works very well,i was just stupid trying to install the recovery from ROM Manager directly

Nik2468 said:
Solved. I just reflashed the bootloader 2 times,installed the cwm from the .bat and then again from ROM Manager.
Now everything works very well,i was just stupid trying to install the recovery from ROM Manager directly
Click to expand...
Click to collapse
Ive got the same problem.
What exactly did you do? Could you describe whole process step by step?
Thanks

Have same problem.Had version v20d, flashed cwm and cianogen mod, but had no signal.
Cant install v10k Homero2 via kdz , always get error wparam100 lparam1002 .
Tried with stock europian v10k but same error.
Can instal normaly v20D, but now cant get to CWM secure booting error
Can normaly flach and use v20D but i want to go to cianogen mod.
What should I do ?
SOLVED
Again installed cwm, on other computer and made it.
Then instaled V10K but Russian version via KDZ, than via CWM installed CM10 and all works well for now.

I dont know what should I do.
I have v10K rooted, downloaded CWM package, pluged my L7 via USB cable, USB debbugging activated,
then I run "flash_bootloader.bat", something blinks on PC screen (cant see or read because it is very quick), and nothing happens.
Restarted the phone, and nothing. Trying also "flash_recovery.bat", the same result.
Doing something wrong?
Help, please..

Run flash_bootloader script in cmd, then read what it says.
Sent from my Sensation using xda app-developers app

thanks, but
cmd window disappear very quick.. cant see or read anything

First open cmd (from 'Run' in menu Start) then run this script via cmd.
Sent from my HTC Sensation Z710e using xda app-developers app

CMD says:
adb push emmc_appsboot.bin /data/local/tmp/emmc_appsboot.bin
cannot stat 'emmc_appsboot.bin': No such file or directory
c:\l7cwm\adb shell su -c "dd if=/data/local/tmp/emmc_appsboot.bin of=/dev/block/mmcblk0p5 bs=4096"
/data/local/tmp/emmc_appsboot.bin: cannot open for read: No such file or directory
but "emmc_appsboot.bin" file realy is in directory L7CWM..
SO, WHAT NOW ??

needhelp_l7 said:
CMD says:
adb push emmc_appsboot.bin /data/local/tmp/emmc_appsboot.bin
cannot stat 'emmc_appsboot.bin': No such file or directory
c:\l7cwm\adb shell su -c "dd if=/data/local/tmp/emmc_appsboot.bin of=/dev/block/mmcblk0p5 bs=4096"
/data/local/tmp/emmc_appsboot.bin: cannot open for read: No such file or directory
but "emmc_appsboot.bin" file realy is in directory L7CWM..
SO, WHAT NOW ??
Click to expand...
Click to collapse
It needs to be in /data/local/tmp/ directory.
Sent from my HTC Sensation Z710e using xda app-developers app

ok, i moved it to that directory.. NOW CMD SAYS:
c:\l7cwm\adb shell su -c "dd if=/data/local/tmp/emmc_appsboot.bin of=/dev/block/mmcblk0p5 bs=4096"
64+1 records in
64+1 records out
264960 bytes transferred in 0.693 secs (382337 bytes/sec)
c:\l7cwm\adb reboot
THAT IS IT ?? ive got unlocked bootloader ??
EDIT == YES !! SUCCESS ! tested, it works!
thank you (mrjabol61) for helping me )

How did you solve the problem?
I do not have any /data/local/tmp/ directory! Where should I find it?

arkantos91 said:
How did you solve the problem?
I do not have any /data/local/tmp/ directory! Where should I find it?
Click to expand...
Click to collapse
Read from post #9 to #11
Sent using Tapatalk

Sorry I don't understand.
I also tried to create manually those directories in the phone and put the apps boot.bin file in it... but the same error shows in cmd .
Are there any other ways to unlock the bootloader?
Inviato dal mio Nexus 5 utilizzando Tapatalk

[WIP] Rooting Procedure for X2

Hello there users. I'm currently a dev for Nokia X but I would love to help you guys out.
So, I'll be giving out ways on how you can try to get Root on your device. This is a discussion thread.
As I don't have the device myself, I'm counting on people who have purchased it.
So lets start. In order to get development for your device, you need to get a system dump of your whole/entire device.
But for that, you need Root. Heres an app that I think might root the device. http://www.cydiaimpactor.com/
Goto the link, download it and test it out. Give feedback.

And nothing happens. Maybe I`ve done somthing wrong...
So, in a dev options i`ve point usb debuging.
On my pc i got two new devices - Nokia composite adb interface and nokia 2 with yellow mark.
Then run cidia from admin name - usb - driver scan - no device found.
I tried with rooted nokia xl - just to see what happens - error - no such device.

stutofa aregercisr are
Thanks for your help, I tried it out and got this error all the time

Altivex said:
And nothing happens. Maybe I`ve done somthing wrong...
So, in a dev options i`ve point usb debuging.
On my pc i got two new devices - Nokia composite adb interface and nokia 2 with yellow mark.
Then run cidia from admin name - usb - driver scan - no device found.
I tried with rooted nokia xl - just to see what happens - error - no such device.
Click to expand...
Click to collapse
tdiddy.2 said:
Thanks for your help, I tried it out and got this error all the time
Click to expand...
Click to collapse
Okay, so that didnt work.
Now, goto this link and download the adb and fastboot drivers for Nokia X and install them.
After that, go HERE and flash CWM Recovery for Nokia X using the instructions given in the thread.
DONT DO THE ABOVE METHOD! As there is no backup, if something goes wrong, you'll lose the device. For now, wait and let me find more exploits. Till then, do install the adb and fastboot divers.
After that, goto ADB folder and Open command prompt from there (Shift + Right mouse button). Then type this:
Code:
adb reboot bootloader
fastboot -i 0x0421 devices
And see if the device gets recognized.
Then type:
Code:
fastboot -i 0x0421 reboot

You can try this method too: http://forum.xda-developers.com/showthread.php?t=803682

Okay will try. For the recovery, I tried both Nokia X's CWM and TWRP already, none of them worked However it's not going to brick my device haha

On fastboot - nothing. I coudn`t install adb from this tread
http://forum.xda-developers.com/showthread.php?t=2744191
Installer told me-unsupported language and close)
I used cmd.exe ,and path to android tools - on fastboot i got nothing. No list of devices. But.
On reboot or others command - answer is - Waiting for device
Super one click - runs adb server around 3 times, then program freez on - Waiting for device =)
If i click on button driver chek - no issues found.
Maybe i`ve got some trouble with drivers ?
I got them from here
http://developer.nokia.com/resources/library/nokia-x/getting-started/device-setup.html
But i haven`t adb_usb.ini where it should be...

Altivex said:
On fastboot - nothing. I coudn`t install adb from this tread
http://forum.xda-developers.com/showthread.php?t=2744191
Installer told me-unsupported language and close)
I used cmd.exe ,and path to android tools - on fastboot i got nothing. No list of devices. But.
On reboot or others command - answer is - Waiting for device
Super one click - runs adb server around 3 times, then program freez on - Waiting for device =)
If i click on button driver chek - no issues found.
Maybe i`ve got some trouble with drivers ?
I got them from here
http://developer.nokia.com/resources/library/nokia-x/getting-started/device-setup.html
But i haven`t adb_usb.ini where it should be...
Click to expand...
Click to collapse
adb_usb.ini is important as it is the key that recognizes the adb device to the computer.
Do all the above steps in the guide fully including the adb_usb.ini step.

mmmm, Nokia XL got connected without this file...
I tried all instructions on 3 different pc - this file is missed....
So,i just created this file.
on ADB devices i got answer - 188bde4a device
on command fastboot -i 0x0421 devices-
188bde4a fastboot
then i reboot device.
i`ve try out some comands - i lost recovery....
fastboot -i 0x0421 oem unlock
unlocked
fastboot -i 0x0421 flash recovery recovery img.
7seconds flash - and i coud not boot recovery....
i tyed this one
http://forum.xda-developers.com/showthread.php?t=2704379
but - phone boots up in normal mode...
ok,good news - got stock firmware from navifirm!
Just need stock recovery)

Okay, i tried superoneclick, not work :crying:
---------- Post added at 11:02 AM ---------- Previous post was at 10:58 AM ----------
And for the Fastboot...
Code:
Tungs-MacBook-Air:~ md232llaoption$ fastboot -i 0x0421 devices
f901c863 fastboot
Tungs-MacBook-Air:~ md232llaoption$

I think i goot rooted my device....
with root_backup
or towelroot.
So, if I`ll install gaps- that would be great. But i really need custom recovery)
http://forum.xda-developers.com/showthread.php?t=2783157
or in attach.
Copy all data to phone, then go to folder "1" install tr.apk
Make shure you`ve got internet connection.
in folder "2" is SUpersu apk.
In folder"3" - root explorer.
Also you`ll find apk for backup phone.

Altivex said:
mmmm, Nokia XL got connected without this file...
I tried all instructions on 3 different pc - this file is missed....
So,i just created this file.
on ADB devices i got answer - 188bde4a device
on command fastboot -i 0x0421 devices-
188bde4a fastboot
then i reboot device.
i`ve try out some comands - i lost recovery....
fastboot -i 0x0421 oem unlock
unlocked
fastboot -i 0x0421 flash recovery recovery img.
7seconds flash - and i coud not boot recovery....
i tyed this one
http://forum.xda-developers.com/showthread.php?t=2704379
but - phone boots up in normal mode...
ok,good news - got stock firmware from navifirm!
Just need stock recovery)
Click to expand...
Click to collapse
Thats it. You got the fastboot recognized. Now try Bin4ry Root Method and see if it'll work.
tdiddy.2 said:
Okay, i tried superoneclick, not work :crying:
---------- Post added at 11:02 AM ---------- Previous post was at 10:58 AM ----------
And for the Fastboot...
Code:
Tungs-MacBook-Air:~ md232llaoption$ fastboot -i 0x0421 devices
f901c863 fastboot
Tungs-MacBook-Air:~ md232llaoption$
Click to expand...
Click to collapse
You also got fastboot recognized. f901c863 is your fastboot device number.
Try Bin4ry root method.
Altivex said:
I think i goot rooted my device....
with root_backup
or towelroot.
So, if I`ll install gaps- that would be great. But i really need custom recovery)
Click to expand...
Click to collapse
Wait. Did you get Root? HOWWW?! Share if you did. Cause this is what the thread is about.

Dom3616 said:
Wait. Did you get Root? HOWWW?! Share if you did. Cause this is what the thread is about.
Click to expand...
Click to collapse
Towelroot in attach. Idk will it work on clear device,or you need to unlock bootloader. Cos on oem unlock- unlocked something=)

Altivex said:
Towelroot in attach. Idk will it work on clear device,or you need to unlock bootloader. Cos on oem unlock- unlocked something=)
Click to expand...
Click to collapse
Very good. I'll be updating this thread soon.
Now, next step is to goto this thread and make a full dump of your device: http://forum.xda-developers.com/showthread.php?t=2450045

Dom3616 said:
Very good. I'll be updating this thread soon.
Now, next step is to goto this thread and make a full dump of your device: http://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
Yes yes!!

Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?

Altivex said:
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Click to expand...
Click to collapse
Yes, you can use this also: http://forum.xda-developers.com/showthread.php?t=1620255
After creating the backup, upload it to Google Drive or any other server.

Altivex said:
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Click to expand...
Click to collapse
I tried to pull and got the recovery img for ya hope this work

Native recovery or custom?)
native I`ve restored yesterday from navifirm. And custom will make our life a bit easyer)

I`ve made a twrp backup, with nandroid . Backup have files with .win extension....

ASUS ME176C/CX- Unlock Bootloader & Install TWRP

Please note: the information in this thread is out of date. I recommend installing me176c-boot instead, found in https://forum.xda-developers.com/me...tloader-me176c-boot-asus-memo-pad-7-t3780225.
DISCLAIMER: I am NOT responsible for anything that goes wrong with your device. This tablet's very resilient and theoretically unbrickable, but it can still happen.
@social-design-concepts is working on a bootloader "unlock" for all Intel Bay Trail devices running Lollipop. It's working fine on our tablet, so he's given me permission to release the unlock for this device, as well as a TWRP image.
Download the images from here:
https://www.androidfilehost.com/?fid=312978532265362065
UPDATED! TWRP is now version 3.0.2!
MAKE A BACKUP OF ESP AND RECOVERY IN CASE ANYTHING GOES WRONG. YOU'VE BEEN WARNED.
These images aren't in a Nandroid or anything, you'll have to flash them manually via dd.
REQUIREMENTS
ASUS ME176C or ASUS ME176CX with root (duh )
and either-
Terminal Emulator must be installed on the tablet, and given root access
or
Access to a computer w/ ADB installed
INSTALLATION
Download the linked file from above, then unzip them to somewhere on your tablet. This directory will be noted as /path/to/unzipped/zip in this tutorial.
Open up a command prompt and plug in your tablet (if you're on PC) or just launch Terminal Emulator on your tablet.
This first command can be skipped if you're installing this without a computer, but if you're using ADB, then first run
Code:
adb shell
The next steps are universal for both Terminal Emulator and the PC command prompt or terminal.
While we could use tethered TWRP to back up these partitions, it cannot properly back up the ESP, so we'll be backing up the partitions manually. To do so, run the following to get root permission and back up the original recovery and ESP.
Code:
su
dd if=/dev/block/by-name/ESP of=/path/to/unzipped/zip/stock_ESP.img
dd if=/dev/block/by-name/recovery of=/path/to/unzipped/zip/stock_recovery.img
Then, to install:
Code:
dd if=/path/to/unzipped/zip/ESP.img of=/dev/block/by-name/ESP
dd if=/path/to/unzipped/zip/recovery.img of=/dev/block/by-name/recovery
Finally, reboot the tablet to make sure it worked. The ASUS screen should be replaced with an Intel one.
Volume Down + Power will give you an option of either fastboot or recovery, instead of just booting to fastboot like the stock bootloader.

do we still get otas? what happends if the ota contains a uefi update will it become locked again?

Ruben Craveiro said:
do we still get otas? what happends if the ota contains a uefi update will it become locked again?
Click to expand...
Click to collapse
Becouse the firmware update is for unknown reason always included in the esp.img, then the answer is yes no matter how unlogical it is.
P.S anybody still having 16GB whole emmc dd backup? Some guy from my country who doesn't speak English contacted me on PM, he tried to run some KK to LP update from 4pda.ru while already on lollipop. Now he is stuck in Aptio Setup Utlility (lying to him saying it's BIOS ) and so far this seems to be the only option to help him.
P.P.S I have finaly ordered a Y OTG cable from ebay so next month when I get it I can start debugging my debirf-xkiosk running on kali kernel to find out what's the problem.
*EDIT ilogical maybe?
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
Why your tutorial can be in general and mine was moved to Q&A? It's unfair :'(

I got this 'Read only file system' message when I tried the first backup.. this shouldn't be happening, right? Presumably the backup failed?
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]_1:/ $ su
su
[email protected]_1:/ # dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd: /recoverystuff/stock_ESP.img: Read-only file system
1|[email protected]_1:/ #

Worked perfectly with your instructions. Used Terminal Emulator on the tablet.
Sent from my K013 using Tapatalk

seamo123 said:
I got this 'Read only file system' message when I tried the first backup.. this shouldn't be happening, right? Presumably the backup failed?
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]_1:/ $ su
su
[email protected]_1:/ # dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd: /recoverystuff/stock_ESP.img: Read-only file system
1|[email protected]_1:/ #
Click to expand...
Click to collapse
Try doing it through Terminal Emulator, see if that helps.

jerbear294 said:
Try doing it through Terminal Emulator, see if that helps.
Click to expand...
Click to collapse
Nah, same result using terminal emulator.. what's wrong I wonder?

seamo123 said:
Nah, same result using terminal emulator.. what's wrong I wonder?
Click to expand...
Click to collapse
Android in it's natire has no real rootfs so writing backup to /customdir/ rather than /sdcard/customdir is not gonnw work. If you "remounted" rootfs rw (not sure if you can remount ramdisk) it would still be all in ram.
---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------
Mis012 said:
Android in it's natire has no real rootfs so writing backup to /customdir/ rather than /sdcard/customdir is not gonnw work. If you "remounted" rootfs rw (not sure if you can remount ramdisk) it would still be all in ram.
Click to expand...
Click to collapse
I wonder why people use ADB for shell when they don't have to

Mis012 said:
Android in it's natire has no real rootfs so writing backup to /customdir/ rather than /sdcard/customdir is not gonnw work. If you "remounted" rootfs rw (not sure if you can remount ramdisk) it would still be all in ram.
Click to expand...
Click to collapse
Oh ok, I'll just move the folder to the sdcard and give it a try..

seamo123 said:
Oh ok, I'll just move the folder to the sdcard and give it a try..
Click to expand...
Click to collapse
@Mis012 is right, either move it to a micro SD and make the path /Removable/MicroSD/recoverystuff or put it on the internal storage and make the path /storage/emulated/0/recoverystuff

jerbear294 said:
@Mis012 is right, either move it to a micro SD and make the path /Removable/MicroSD/recoverystuff or put it on the internal storage and make the path /storage/emulated/0/recoverystuff
Click to expand...
Click to collapse
Seemed to work fine, thanks! Boots up perfectly with the 'Intel' image. How does one get into recovery though? The volume up/down press/let go power button shenanigans for this pad always drove me totally up the wall. Anytime I ever got into stock recovery it was always by accident!
What's the key combo?

seamo123 said:
Seemed to work fine, thanks! Boots up perfectly with the 'Intel' image. How does one get into recovery though? The volume up/down press/let go power button shenanigans for this pad always drove me totally up the wall. Anytime I ever got into stock recovery it was always by accident!
What's the key combo?
Click to expand...
Click to collapse
Volume Down + Power, just like on the stock bootloader.
When you see the Intel screen release Power but keep holding Volume Down. You'll see a screen with a generic warning, then options to go to either fastboot or recovery.

Mis012 said:
Becouse the firmware update is for unknown reason always included in the esp.img, then the answer is yes no matter how unlogical it is.
P.S anybody still having 16GB whole emmc dd backup? Some guy from my country who doesn't speak English contacted me on PM, he tried to run some KK to LP update from 4pda.ru while already on lollipop. Now he is stuck in Aptio Setup Utlility (lying to him saying it's BIOS ) and so far this seems to be the only option to help him.
P.P.S I have finaly ordered a Y OTG cable from ebay so next month when I get it I can start debugging my debirf-xkiosk running on kali kernel to find out what's the problem.
*EDIT ilogical maybe?
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
Why your tutorial can be in general and mine was moved to Q&A? It's unfair :'(
Click to expand...
Click to collapse
why just not simply go to dnx mode? then from there make fastboot flash osloader efilinux.efi and then fastboot boot droidboot.img from there it should boot to droidboot and allow to load temp recovery and flash .36(ive already been stuck in uefi for at least 2 times and this method helped me... yesterday i was stuck and its working again)

jerbear294 said:
Volume Down + Power, just like on the stock bootloader.
When you see the Intel screen release Power but keep holding Volume Down. You'll see a screen with a generic warning, then options to go to either fastboot or recovery.
Click to expand...
Click to collapse
That's great, thanks! So does this mean that we're all ready to install a custom ROM when one comes along? Running CM or AOSP on this device would be brilliant, I can finally forget all about that piercing white ASUS ui for a start

seamo123 said:
That's great, thanks! So does this mean that we're all ready to install a custom ROM when one comes along? Running CM or AOSP on this device would be brilliant, I can finally forget all about that piercing white ASUS ui for a start
Click to expand...
Click to collapse
Precisely. A custom ROM is possible with this bootloader.

Ruben Craveiro said:
why just not simply go to dnx mode? then from there make fastboot flash osloader efilinux.efi and then fastboot boot droidboot.img from there it should boot to droidboot and allow to load temp recovery and flash .36(ive already been stuck in uefi for at least 2 times and this method helped me... yesterday i was stuck and its working again)
Click to expand...
Click to collapse
He tried, it complained about some partitions not existing.

Mis012 said:
He tried, it complained about some partitions not existing.
Click to expand...
Click to collapse
he needs to repartition the tablet :
Code:
fastboot oem start_partitioning
fastboot oem partition /system/etc/partition.tbl
fastboot oem format factory
fastboot oem format cache
fastboot oem format system
fastboot oem format config
fastboot oem format logs
fastboot oem format misc
fastboot oem format data
fastboot oem stop_partitioning

Does it work with Build .36?
Hello,
i updated my me176c to the build number WW_V12.10.1.36_20151230 can i use your unlocked bootloader ?

intNERD said:
Hello,
i updated my me176c to the build number WW_V12.10.1.36_20151230 can i use your unlocked bootloader ?
Click to expand...
Click to collapse
you can use the unlocked bootloader on any lollipop version

Ruben Craveiro said:
you can use the unlocked bootloader on any lollipop version
Click to expand...
Click to collapse
Thank You! Great work! Cant wait for a custom rom!

Sd kajad

Ssd

alemarprieto said:
hello i want to repair mi xiaomi mi a1 let me explain what happen . i accidentally used factory reset and mi cell phone got bricked i tried to repair it flashing android 8 (january) but it got reboot and reboot after 1 minute of get into launch app .(i could solve that problem using “dd[/url] if=/sdcard/persist.img of=/dev/block/mmcblk0p27” via TWRP terminal mi cell phone is Working noW but it lost imei and baseband i tried to restore efs using another mi a 1 cellphone (android 7) but it only restored baseband and the first imei is 0 imei sv 00 but second is unknown and unknown , hoW can i fix it?. please:crying:
imei 1 is 867559033212389
imei 2 is 867559033212397
Click to expand...
Click to collapse
flash full stock firmware via mi flash or fastboot

Ahmed.ragab said:
flash full stock firmware via mi flash or fastboot
Click to expand...
Click to collapse
Hello, i did it vía edl and normal flash too ,the same happened but i want to try, please can you give me a link of that filmware to download ? Thancks

Hi , Don't share your IMEI Publicly .
if you face IMEI 0 and SIM 2 IMEI unknown , Use WriteDualIMEI(W+G_eMMC) Tools to rewrite your IMEI (Google the tools as i can't find the link anymore)
To Enable Diag Mode , you need to follow the steps :
1. dial : *#*#717717#*#*
2.Enable USB Debug
3.Connect to the phone
4.Run WriteDualIMEI(W+G_eMMC) as admin
5.Write your ORIGINAL IMEI Note: Change IMEI is illegal
6.Success , Dial *#*#717717#*#* to disable Diag USB PORT
7.Reboot
8.Feedback

alemarprieto said:
hello i want to repair mi xiaomi mi a1 let me explain what happen . i accidentally used factory reset and mi cell phone got bricked i tried to repair it flashing android 8 (january) but it got reboot and reboot after 1 minute of get into launch app .(i could solve that problem using “dd[/url] if=/sdcard/persist.img of=/dev/block/mmcblk0p27” via TWRP terminal mi cell phone is Working noW but it lost imei and baseband i tried to restore efs using another mi a 1 cellphone (android 7) but it only restored baseband and the first imei is 0 imei sv 00 but second is unknown and unknown , hoW can i fix it?. please:crying:
Click to expand...
Click to collapse
Dude don't put your IMEI here it can be misused, here is the link for Official Rom
Link 1 :http://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
Link 2 (Mirror):https://androidfilehost.com/?w=files&flid=240798

Pls hide ur imei, someone could use it.

JoKeRLeE said:
Hi , Don't share your IMEI Publicly .
if you face IMEI 0 and SIM 2 IMEI unknown , Use WriteDualIMEI(W+G_eMMC) Tools to rewrite your IMEI (Google the tools as i can't find the link anymore)
To Enable Diag Mode , you need to follow the steps :
1. dial : *#*#717717#*#*
2.Enable USB Debug
3.Connect to the phone
4.Run WriteDualIMEI(W+G_eMMC) as admin
5.Write your ORIGINAL IMEI Note: Change IMEI is illegal
6.Success , Dial *#*#717717#*#* to disable Diag USB PORT
7.Reboot
8.Feedback
Click to expand...
Click to collapse
thank u so much joker to take the time to read an ansWer , it didn't Work i use the : adb devices
adb shell
su
setprop sys.usb.config diag,adb (becose pc DiDnt recognice the phone using *#*#717717#*#* ) anyai i set it in Diag mode enable , then folloW everithing but didnt Work (of course the program said success) an i disable using (Dial *#*#717717#*#*),after reboot everithing looks the same (imei 1 =0 ,imei sv =00,imei 2 unkno, imei sv unko) baseband is ta.2.3.c1-00544-8953_gen_pak-1

Ahmed.ragab said:
flash full stock firmware via mi flash or fastboot
Click to expand...
Click to collapse
as u can read i already did it ,via edl too

alemarprieto said:
thank u so much joker to take the time to read an ansWer , it didn't Work i use the : adb devices
adb shell
su
setprop sys.usb.config diag,adb (becose pc DiDnt recognice the phone using *#*#717717#*#* ) anyai i set it in Diag mode enable , then folloW everithing but didnt Work (of course the program said success) an i disable using (Dial *#*#717717#*#*),after reboot everithing looks the same (imei 1 =0 ,imei sv =00,imei 2 unkno, imei sv unko) baseband is ta.2.3.c1-00544-8953_gen_pak-1
Click to expand...
Click to collapse
Are you on Oreo ? or Nougat ? I tried all the rom won't work except 7.8.23 Build (first and buggy ROM)
if you tried my method still fail i suggest you to restore using qcn backup , which i personally made for you ( With your IMEI)
but i wont share here but through PM .
You need driver to do this
QPST Setup : https://ia801906.us.archive.org/22/items/QPST.2.7.441/QPST.2.7.441.zip
Qualcomm Driver : http://www.mediafire.com/file/x83c76ektjf2868/QUD.WIN.1.1+Installer-10034.4.zip
*Link taken from :http://en.miui.com/thread-545300-1-1.html
you may follow the guide from there

JoKeRLeE said:
Are you on Oreo ? or Nougat ? I tried all the rom won't work except 7.8.23 Build (first and buggy ROM)
if you tried my method still fail i suggest you to restore using qcn backup , which i personally made for you ( With your IMEI)
but i wont share here but through PM .
You need driver to do this
QPST Setup : https://ia801906.us.archive.org/22/items/QPST.2.7.441/QPST.2.7.441.zip
Qualcomm Driver : http://www.mediafire.com/file/x83c76ektjf2868/QUD.WIN.1.1+Installer-10034.4.zip
*Link taken from :http://en.miui.com/thread-545300-1-1.html
you may follow the guide from there
Click to expand...
Click to collapse
hello jokerlee,
can you make me a qcn with my IMEI too? i will send you a PM

변은주 said:
hello jokerlee,
can you make me a qcn with my IMEI too? i will send you a PM
Click to expand...
Click to collapse
why not

please help, I also run the factory_reset and lost my imei, tried follwing those steps:
Posted by JoKeRLeE
https://www.androidfilehost.com/?fid=673956719939818468
Replace the IMEi with UR Own IMEI . if not it's illegal to use this QCN
Password : testnreport
if you don't know how to change IMEI Using hex editor , try my method . DO NOT use QCN to restore .
(hex and imei provided in order for u to find n replace)
i lost my imei n spent me about 6days n 8 hours per day to find a way to fix it .
actually it's easy to fix the problem .
My own method
1. download the older rom (7.8.23) Link
2. Use flash_all.bat
3.reboot into fastboot mode , erase modemst1 and modemst2 .
fastboot erase modemst1
fastboot erase modemst2
4. reboot
5. go to phone , enter *#*#717717#*#*
6.got to settings enable USB Debugging (ADB)
7. disconnect your phone n connect it back
8.Use WriteDualIMEI(W+G_eMMC) Remember run as administrator , enter your IMEI .
9.if success , go to phone enter *#*#717717#*#* to disable the diag port
10. reboot
Done .
Click to expand...
Click to collapse
the phone freezes upon dialing the *#*#717717#*#* but
can (only) boot to diag mode from fastboot and then "fastboot oem edl". I see the top led blinking in white.
I get stuck in step8 - despite my phone diag port is being recognized in device manage and WriteDualIMEI/QFIL, I get
a big FAIL.
In QFIL I can see the phone is recognized but is not responding to coms.
I tried to change the qualcomm driver to various 9XXX models, com ports, settings etc.
Tried to change fastboot rom versions to 8.XX as well. didn't make a difference.
tried to setprop usb mode to diag from twrp terminal as well.
How did you guys resolve it?

JoKeRLeE said:
Are you on Oreo ? or Nougat ? I tried all the rom won't work except 7.8.23 Build (first and buggy ROM)
if you tried my method still fail i suggest you to restore using qcn backup , which i personally made for you ( With your IMEI)
but i wont share here but through PM .
You need driver to do this
QPST Setup : https://ia801906.us.archive.org/22/items/QPST.2.7.441/QPST.2.7.441.zip
Qualcomm Driver : http://www.mediafire.com/file/x83c76ektjf2868/QUD.WIN.1.1+Installer-10034.4.zip
*Link taken from :http://en.miui.com/thread-545300-1-1.html
you may follow the guide from there
Click to expand...
Click to collapse
it successfully restored my imei thank u so much . you are the best:highfive:

Ok, IMEI is back. Unfortunately, if I update software I loose it again after first reboot. Will all of us have to stick to the very buggy August ROM forever? Anyone found a workaround for this?

JoKeRLeE said:
Are you on Oreo ? or Nougat ? I tried all the rom won't work except 7.8.23 Build (first and buggy ROM)
if you tried my method still fail i suggest you to restore using qcn backup , which i personally made for you ( With your IMEI)
but i wont share here but through PM .
You need driver to do this
QPST Setup : https://ia801906.us.archive.org/22/items/QPST.2.7.441/QPST.2.7.441.zip
Qualcomm Driver : http://www.mediafire.com/file/x83c76ektjf2868/QUD.WIN.1.1+Installer-10034.4.zip
*Link taken from :http://en.miui.com/thread-545300-1-1.html
you may follow the guide from there
Click to expand...
Click to collapse
Hi! Can you do it for me too? I can send my IMEI via inbox. I can't appreciate it enough!

bro i also wan qcn file can you create for me plz....

[Moto G6 Plus] developer option OEM unclock is disabeld (gray, not switchable enable)

Hi,
I have had a MotoG6 plus from a friend, but after upgrade it from 8.0 to 9.0 begans problems. The phone goes on crash and restart many time during usage of lots of Apps. I Tried a factory reset + reinstall alot of app, but nothing changed. The phone crash as well with same frequency. I decide to broke it and i tried to install a LineageOS16_9Pie. Unfortunatly during the Custom install, even if i followed a guide, unloking the bootloader, i really broke it, the bootloader and recovery partition. I have started the image of TWRP via fastboot to obtained a motoG6plus working (even without a proper bootloader) with LineageOS16_9Pie. To do it i've got the code from motorola site, to unlock the G6plus, after eneable USB debug + OEM Unlock from OS. With theLineageOS i have unlocked and locked oem many times using the OS without any problems . I have used the LineageOS for a week, after that, It started agan the same crashs i had with the stock rom 9.
I decided to reinstall the 8.0 version Evert , to remove the boot errors and because with the 8.0 was stable. After i installed the stock rom 8.0 evert i cant' unlock oem again . Into the developer option, the option "OEM unclock" is gray , disabeld not switchable . Even if i tried to unclock again from fastboot command , it say that i have to switch and anable "OEM Unlock" from the OS but i can't.
Is there a way to unclock byassing the OS or re-enable that option?

Try this command in terminal app:
Code:
:/ $ su
:/ # service call oem_lock 1 s16 allowed
The output should be:
Code:
Result: Parcel(00000000 '....')

WoKoschekk said:
Try this command in terminal app:
Code:
:/ $ su
:/ # service call oem_lock 1 s16 allowed
The output should be:
Code:
Result: Parcel(00000000 '....')
Click to expand...
Click to collapse
Thanks WoKoschekk, but i surely ' loaded a wrong rom, because the Moto G6plus don't have Wifi and connectivity via SIMs working, so I can't download any app. I am going to try to copy an app via apk on the SD. The good news is that the bootloader initial stop has disapeared, (but i still do not have any recovery)

Nothing to do with "install app unknown" o similar (sorry, my phone is in Italian). Even if i do have the apk terminal emulator, i Can't install because of the few app in list that i can unable to install unknown sources. In this list there isn't "File manager" .. i still have the error of parsing the package

If you downgrade from Pie to Oreo you will lost all connections. To get them back you must flash a Pie version of any Rom.
First of all flash the right and latest firmware.

I Would like to reburn another rom, but i can't because the option "Unlock OEM" is in "gray" not switchable, so for be is a bit hard. I am stuck..
Thanks anyway for your interest. I appreciated it.

Reggians said:
I Would like to reburn another rom, but i can't because the option "Unlock OEM" is in "gray" not switchable, so for be is a bit hard. I am stuck..
Thanks anyway for your interest. I appreciated it.
Click to expand...
Click to collapse
Flash the latest Magisk.zip to enable OEM unlock option.

WoKoschekk said:
Try this command in terminal app:
Code:
:/ $ su
:/ # service call oem_lock 1 s16 allowed
The output should be:
Code:
Result: Parcel(00000000 '....')
Click to expand...
Click to collapse
Hi
I finally copy a term.apk and installed with success ! (i have no root permissions on the device)
when i give
Code:
evert_n:/ $ su
the answer is:
Code:
/system/bin/sh: su: not found
127|evert_n:/
if send the command with #
Code:
:/ $ # service call oem_lock 1 s16 allowed
i get null
Code:
127|evert_n:/
if i send the command without # (probably it is the cli after su level) like this
Code:
:/ $ service call oem_lock 1 s16 allowed
the answer is
Code:
service: Service oem_lock does not exist

WoKoschekk said:
Flash the latest Magisk.zip to enable OEM unlock option.
Click to expand...
Click to collapse
I have installed Magistik7.3.4.apk via filesystem but, i don't have connectivity and i can't install it via TWRP because i have the device locked so i can't even try to load TWRP via fastboot , so Magistik is not fully working unfortunatly..

Are you able to start the device in fastboot mode?
What is the error message when booting in TWRP?
For the "service oem_lock" command you need super user rights...

if you haven't solved it yet, use this to enable internet connection to your phone and you will be able to unlock the bootloader
https://github.com/Genymobile/gnirehtet

Has anyone solved this? Do I need to wait the 7 days to unlock it again?
I saw a thread where someone said they skipped the 7 days by changing the date of the device and rebooting, but that didn't work for me.