Related
Note :- THESE GUIDE IS EXCLUSIVELY FOR ANDROID ONE DEVICE's. & Of course A Rooted Android Device To Flash zip
& EVERY TIME YOU FLASH A ROM ie: Format /System Then IMEI WILL BE GONE SO i MADE FLASHABLE ZIP TO Flash everytime you loose your IMEI [ its better to flash a zip rather than going to "\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001" & Fixing Permissions Manually
You Can Use It Too, On Your Device If Your Partition Is Like This
"\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001"
Here "MP0B_001" Is The IMEI File And Its Corrupt [GENERALLY AFTER FLASHING STOCK ROM]
Then Follow This Guide To Rectify That Problem.
LETS BEGIN
First Download These Files
IMEI MAKER.zip
SCREENSHOT
https://www.dropbox.com/s/9pzf18wxtj7i40l/IMEI MAKER.zip?dl=0
& IMEI REPAIR.zip
SCREENSHOT
https://www.dropbox.com/s/4p2rwoi5oxpth15/IMEI REPAIR.zip?dl=0
So After Downloading The Above Files
Extract IMEI MAKER.ZIP
SCREENSHOT
https://www.dropbox.com/s/o0vs89lob4yf4pv/vlcsnap-2015-01-03-22h23m53s216.png?dl=0
Open IMEI MAKER FOLDER , HOLD "SHIFT & RIGHT CLICK" , Click On "Open Command Window Here"
SCREENSHOT
https://www.dropbox.com/s/lbdzp9ko0t9yons/vlcsnap-2015-01-03-22h24m10s140.png?dl=0
Now In Command prompt (CMD)
-Enter the following text:
imei.exe <15digit_IMEI_1> <15digit_IMEI_2>
(eg: imei.exe 123456789111111 123456789111111)
Then Press ENTER
SCREENSHOT
https://www.dropbox.com/s/j0uss286iv94red/vlcsnap-2015-01-03-22h24m48s31.png?dl=0
NOW YOU WILL SEE A FILE CALLED "MP0B_001_NEW"
Now Rename & Remove "_NEW" From It .
SCREENSHOT
http://www.dropbox.com/s/femtg309chk147v/vlcsnap-2015-01-03-22h25m03s169.png?dl=0
NOW OPEN IMEI REPAIR.ZIP Using Winrar [Software For Pc] [ recommended ]
Inside That Archive Navigate To
data/nvram/md/NVRAM/NVD_IMEI
& DRAG-&-DROP The MP0B_001 File There, Which We Just Created [using IMEI Repair]
Now It Should Look Like This
"/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001"
SCREENSHOTS
https://www.dropbox.com/s/y1ign53lmqrwubs/vlcsnap-2015-01-03-22h26m03s7.png?dl=0
https://www.dropbox.com/s/bsbd0s1jhjt4eww/vlcsnap-2015-01-03-22h26m07s44.png?dl=0
Now Copy The Zip To Your SD CARD [REMEMBER NOT TO PUT IT DEEP INSIDE]
& FLASH IT USING ANY RECOVERY BUT CWM RECOVERY IS RECOMMENDED
& REMEMBER THIS TUTORIAL IS ONLY FOR ANDROID ONE DEVICES AND SIMILAR DEVICES HAVING PARTITION LIKE THIS
/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001
I Uploaded A Video On Youtube For This,
Its only [2:19] Minutes So People Confused Can Watch This Video
http://youtu.be/8DT-32tPbMY
Please Like This Video & Suscribe To My Channel
Share This Video
& Thnx For Watching [If Watched] LOL
DONT PRESS THNX IF I HELPED YOU :laugh:
Sagar Kapasi said:
Note :- THESE GUIDE IS EXCLUSIVELY FOR ANDROID ONE DEVICE's. & Of course A Rooted Android Device To Flash zip
& EVERY TIME YOU FLASH A ROM ie: Format /System Then IMEI WILL BE GONE SO i MADE FLASHABLE ZIP TO Flash everytime you loose your IMEI [ its better to flash a zip rather than going to "\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001" & Fixing Permissions Manually
You Can Use It Too, On Your Device If Your Partition Is Like This
"\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001"
Here "MP0B_001" Is The IMEI File And Its Corrupt [GENERALLY AFTER FLASHING STOCK ROM]
Then Follow This Guide To Rectify That Problem.
LETS BEGIN
First Download These Files
IMEI MAKER.zip
SCREENSHOT
https://www.dropbox.com/s/9pzf18wxtj7i40l/IMEI MAKER.zip?dl=0
& IMEI REPAIR.zip
SCREENSHOT
https://www.dropbox.com/s/4p2rwoi5oxpth15/IMEI REPAIR.zip?dl=0
So After Downloading The Above Files
Extract IMEI MAKER.ZIP
SCREENSHOT
https://www.dropbox.com/s/o0vs89lob4yf4pv/vlcsnap-2015-01-03-22h23m53s216.png?dl=0
Open IMEI MAKER FOLDER , HOLD "SHIFT & RIGHT CLICK" , Click On "Open Command Window Here"
SCREENSHOT
https://www.dropbox.com/s/lbdzp9ko0t9yons/vlcsnap-2015-01-03-22h24m10s140.png?dl=0
Now In Command prompt (CMD)
-Enter the following text:
imei.exe <15digit_IMEI_1> <15digit_IMEI_2>
(eg: imei.exe 123456789111111 123456789111111)
Then Press ENTER
SCREENSHOT
https://www.dropbox.com/s/j0uss286iv94red/vlcsnap-2015-01-03-22h24m48s31.png?dl=0
NOW YOU WILL SEE A FILE CALLED "MP0B_001_NEW"
Now Rename & Remove "_NEW" From It .
SCREENSHOT
http://www.dropbox.com/s/femtg309chk147v/vlcsnap-2015-01-03-22h25m03s169.png?dl=0
NOW OPEN IMEI REPAIR.ZIP Using Winrar [Software For Pc] [ recommended ]
Inside That Archive Navigate To
data/nvram/md/NVRAM/NVD_IMEI
& DRAG-&-DROP The MP0B_001 File There, Which We Just Created [using IMEI Repair]
Now It Should Look Like This
"/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001"
SCREENSHOTS
https://www.dropbox.com/s/y1ign53lmqrwubs/vlcsnap-2015-01-03-22h26m03s7.png?dl=0
https://www.dropbox.com/s/bsbd0s1jhjt4eww/vlcsnap-2015-01-03-22h26m07s44.png?dl=0
Now Copy The Zip To Your SD CARD [REMEMBER NOT TO PUT IT DEEP INSIDE]
& FLASH IT USING ANY RECOVERY BUT CWM RECOVERY IS RECOMMENDED
& REMEMBER THIS TUTORIAL IS ONLY FOR ANDROID ONE DEVICES AND SIMILAR DEVICES HAVING PARTITION LIKE THIS
/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001
I Uploaded A Video On Youtube For This,
Its only [2:19] Minutes So People Confused Can Watch This Video
http://youtu.be/8DT-32tPbMY
Please Like This Video & Suscribe To My Channel
Share This Video
& Thnx For Watching [If Watched] LOL
DONT PRESS THNX IF I HELPED YOU :laugh:
Click to expand...
Click to collapse
didnt help..it didnt work
Wait wait wait... The IMEI is gone?? how can the IMEI be gone? it is how the telecom directorate (Govt.) monitors each phone... thats the reason a couple of years ago all cellular devices without an IMEI (chinese imports mainly) stopped working (they could no longer make calls, but it could be used as a media player).
What You Did
How it didn't helped
Can you say something about it?
-Adarsh- said:
didnt help..it didnt work
Click to expand...
Click to collapse
Here We Are Taking About An Error Which Occurs Mainly After flashing stock Rom On Android One Devices And Yes We Cannot make phone calls in this situation too, So here a Guide to fix it
my imei was also gone that's why this guide
the_prodigal_coder said:
Wait wait wait... The IMEI is gone?? how can the IMEI be gone? it is how the telecom directorate (Govt.) monitors each phone... thats the reason a couple of years ago all cellular devices without an IMEI (chinese imports mainly) stopped working (they could no longer make calls, but it could be used as a media player).
Click to expand...
Click to collapse
Got an error:
set_perm: some changes failed
E:Error in IMEI Repair.zip
(Status 7)
Installation Aborted
the_prodigal_coder said:
Wait wait wait... The IMEI is gone?? how can the IMEI be gone? it is how the telecom directorate (Govt.) monitors each phone... thats the reason a couple of years ago all cellular devices without an IMEI (chinese imports mainly) stopped working (they could no longer make calls, but it could be used as a media player).
Click to expand...
Click to collapse
I accidentally restored the EFS partition from one Nexus 5 to another and ended up with an IMEI of all zeros. It can happen. I was able to repair it with Qualcomm software, but the phone still doesn't see the network. Possibly an antenna issue...
Anyway, it can definitely happen. Also, it is illegal to change your IMEI (in the US at least). I would think it's OK to repair one however. I think the OP should specify that this method should only be used to restore an IMEI to the numbers listed on the device. These can usually be found inside the back cover and on the SIM tray. Check documentation for your model.
Help Needed !! IMEI Fix for Android One not working for me...
I was using CM11 sprout earlier and tried moving back to Stock. I lost my IMEI during this time. I have moved to stock kitkat by doing scatter loading of stock firmware. I have rooted my Android one with CWM recovery. I have used the above tools and generated the MTB_001 and created a zip and installed it with recovery. But, still i have my IMEI as invalid. I even tried replacing the MTB_001 file manually using ES_File explorer and giving permissions 777. Still no luck.
Can someone help me out on how to load proper IMEI as am completely blocked :crying::crying::crying::crying:
Thanks in Advance.
Great Guide! Liked it..Step by Step guide!
But i dont understand why people flash so much..where there is Official Lollipop & CM12 Available for us! Flash Freaking People! :/
You Should Tick All W-R-T All The 9 Then Only It Will Work & Dont Forget To Reboot
SpiceAndroidOne said:
I was using CM11 sprout earlier and tried moving back to Stock. I lost my IMEI during this time. I have moved to stock kitkat by doing scatter loading of stock firmware. I have rooted my Android one with CWM recovery. I have used the above tools and generated the MTB_001 and created a zip and installed it with recovery. But, still i have my IMEI as invalid. I even tried replacing the MTB_001 file manually using ES_File explorer and giving permissions 777. Still no luck.
Can someone help me out on how to load proper IMEI as am completely blocked :crying::crying::crying::crying:
Thanks in Advance.
Click to expand...
Click to collapse
Installation aborted in canvas A1.
When i m flashing the zip file it says installation aborted in canvas A1.:crying::crying::crying::crying::crying:
aryan9090 said:
When i m flashing the zip file it says installation aborted in canvas A1.:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Try to copy paste the IMEI file you just made manually to the directory which is in the main post. It works on my Sparkle V everytime(the copy-paste method).
Does not work for me... please help.....
Sagar Kapasi said:
Note :- THESE GUIDE IS EXCLUSIVELY FOR ANDROID ONE DEVICE's. & Of course A Rooted Android Device To Flash zip
& EVERY TIME YOU FLASH A ROM ie: Format /System Then IMEI WILL BE GONE SO i MADE FLASHABLE ZIP TO Flash everytime you loose your IMEI [ its better to flash a zip rather than going to "\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001" & Fixing Permissions Manually
You Can Use It Too, On Your Device If Your Partition Is Like This
"\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001"
Here "MP0B_001" Is The IMEI File And Its Corrupt [GENERALLY AFTER FLASHING STOCK ROM]
Then Follow This Guide To Rectify That Problem.
LETS BEGIN
First Download These Files
IMEI MAKER.zip
SCREENSHOT
& IMEI REPAIR.zip
SCREENSHOT
So After Downloading The Above Files
Extract IMEI MAKER.ZIP
SCREENSHOT
Open IMEI MAKER FOLDER , HOLD "SHIFT & RIGHT CLICK" , Click On "Open Command Window Here"
SCREENSHOT
Now In Command prompt (CMD)
-Enter the following text:
imei.exe <15digit_IMEI_1> <15digit_IMEI_2>
(eg: imei.exe 123456789111111 123456789111111)
Then Press ENTER
SCREENSHOT
NOW YOU WILL SEE A FILE CALLED "MP0B_001_NEW"
Now Rename & Remove "_NEW" From It .
SCREENSHOT
NOW OPEN IMEI REPAIR.ZIP Using Winrar [Software For Pc] [ recommended ]
Inside That Archive Navigate To
data/nvram/md/NVRAM/NVD_IMEI
& DRAG-&-DROP The MP0B_001 File There, Which We Just Created [using IMEI Repair]
Now It Should Look Like This
"/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001"
SCREENSHOTS
Now Copy The Zip To Your SD CARD [REMEMBER NOT TO PUT IT DEEP INSIDE]
& FLASH IT USING ANY RECOVERY BUT CWM RECOVERY IS RECOMMENDED
& REMEMBER THIS TUTORIAL IS ONLY FOR ANDROID ONE DEVICES AND SIMILAR DEVICES HAVING PARTITION LIKE THIS
/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001
I Uploaded A Video On Youtube For This,
Its only [2:19] Minutes So People Confused Can Watch This Video
Please Like This Video & Suscribe To My Channel
Share This Video
& Thnx For Watching [If Watched] LOL
DONT PRESS THNX IF I HELPED YOU :laugh:
Click to expand...
Click to collapse
I followed complete steps and it got installed successfully but the IMEI is still 0 !! Does this even works on Nexus 5? Please help.
deepak21 said:
I followed complete steps and it got installed successfully but the IMEI is still 0 !! Does this even works on Nexus 5? Please help.
Click to expand...
Click to collapse
did you replace the file and rename it (just asking).
Saurabh K said:
did you replace the file and rename it (just asking).
Click to expand...
Click to collapse
Yes, I did... I followed every step very carefully and there were no error message at all.. everything was successful.
deepak21 said:
Yes, I did... I followed every step very carefully and there were no error message at all.. everything was successful.
Click to expand...
Click to collapse
Is your IMEI back ???? If not.......
try to flash the nvram.img using:
fastboot flash nvram nvram.img
I think that nvram partition may have some problem, just give it a try..and reply
Saurabh K said:
Is your IMEI back ???? If not.......
try to flash the nvram.img using:
fastboot flash nvram nvram.img
I think that nvram partition may have some problem, just give it a try..and reply
Click to expand...
Click to collapse
So far nothing worked, will try anything to get it back. Do I need to clear the cache as well ? Will I lose my data? Just asking
---------- Post added at 08:55 AM ---------- Previous post was at 08:00 AM ----------
Saurabh K said:
Is your IMEI back ???? If not.......
try to flash the nvram.img using:
fastboot flash nvram nvram.img
I think that nvram partition may have some problem, just give it a try..and reply
Click to expand...
Click to collapse
Also, I don't have any nv backup with me... could you please share any nvram image or let me know where can I get it?
deepak21 said:
So far nothing worked, will try anything to get it back. Do I need to clear the cache as well ? Will I lose my data? Just asking
---------- Post added at 08:55 AM ---------- Previous post was at 08:00 AM ----------
Also, I don't have any nv backup with me... could you please share any nvram image or let me know where can I get it?
Click to expand...
Click to collapse
I have the stock KITKAT 4.4.4 nvram image, but I dont know will it work. I will try to extract the image from stock 5.1 and reply soon...
---------- Post added at 09:09 AM ---------- Previous post was at 08:56 AM ----------
deepak21 said:
So far nothing worked, will try anything to get it back. Do I need to clear the cache as well ? Will I lose my data? Just asking
---------- Post added at 08:55 AM ---------- Previous post was at 08:00 AM ----------
Also, I don't have any nv backup with me... could you please share any nvram image or let me know where can I get it?
Click to expand...
Click to collapse
sorry, but i couldn't backup the 5.1 stock nvram but i will send you nvram.img from stock kitkat ROM. Flash and redo the procedure from scratch...and tell your device model also..
First point to note is that only full formatting makes the device lose IMEI,not normal data,system,cache formatting which is required for installing custom roms.When your partition table is messed up you get lots of errors when trying to wipe or mount any partition from custom recoveries,thus leaving you with only option to format before flashing stock rom through sp flash tools.It is after this flash that nvram loses your unique IMEI number.In my case I had backed up my stock rom through cwm recovery,now to restore my IMEI, I just extract the contents of /data/nvram/.....NVD_IMEI from my backup( three files in total) and push it to my to the same directory using adb push command,and it works for me.There is no need to push three cos only one file is relevant .But this is only temporary solution,cos after every reset you will lose your IMEI. It is better to backup the nvram partiton using dd command so that it could be flashed later,which would persist through installs.
tealio said:
I accidentally restored the EFS partition from one Nexus 5 to another and ended up with an IMEI of all zeros. It can happen. I was able to repair it with Qualcomm software, but the phone still doesn't see the network. Possibly an antenna issue...
Anyway, it can definitely happen. Also, it is illegal to change your IMEI (in the US at least). I would think it's OK to repair one however. I think the OP should specify that this method should only be used to restore an IMEI to the numbers listed on the device. These can usually be found inside the back cover and on the SIM tray. Check documentation for your model.
Click to expand...
Click to collapse
please brother how did you "repair it with Qualcomm software to restore an IMEI to the numbers listed on the device. These can usually be found inside the back cover and on the SIM tray"? please can you pm me or email: [email protected] the software and guide pleeeeeeeeeeeeeeeeeeeeaaaaaaasssssssssssseeeeeee
need to fix my htc mytouch 4G and my LG vu II
Thanks
Hi,
I am trying to build a custom boot image to get rid of the immutable files of my P7-L00.
Specifically I haved done this : At a specific point in the boot process the rc scripts execute the set_immutable command with a 1 parameters that sets the immutable bits in all the files mentioned in the set_immutable.list file. If this command is changed to a 0 it clears the immutable bit for all the files. I have buit the custom ramfs necesary for this but when I repack the boot image it will not boot.
I am using the following command for mkbootimg ....
mkbootimg --kernel mykernel.img --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x04000000 --base 0x07000000 --cmdline "k3v2mem k3v2_ion=1 vmalloc=448M maxcpus=4 initcall_debug=n" -o newimg.img
The resulting first page looks ok, it has the same offsets as my original working boot image, but as I mentioned before, it does not boot, but just cycles back to fastboot mode after about 1 minute.
Any help will be appreciated,
Thanks
The most probable that there's a problem with permissions.
Make
Code:
chown 0:0 init.rc
chmod 750 init.rc
before packing ramdisk.
Kostyan_nsk said:
The most probable that there's a problem with permissions.
Make
Code:
chown 0:0 init.rc
chmod 750 init.rc
before packing ramdisk.
Click to expand...
Click to collapse
Thanks a lot ! .... I had not checked the user/groups for the extracted files ...
gguemez said:
Hi,
I am trying to build a custom boot image to get rid of the immutable files of my P7-L00.
Specifically I haved done this : At a specific point in the boot process the rc scripts execute the set_immutable command with a 1 parameters that sets the immutable bits in all the files mentioned in the set_immutable.list file. If this command is changed to a 0 it clears the immutable bit for all the files. I have buit the custom ramfs necesary for this but when I repack the boot image it will not boot.
I am using the following command for mkbootimg ....
mkbootimg --kernel mykernel.img --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x04000000 --base 0x07000000 --cmdline "k3v2mem k3v2_ion=1 vmalloc=448M maxcpus=4 initcall_debug=n" -o newimg.img
The resulting first page looks ok, it has the same offsets as my original working boot image, but as I mentioned before, it does not boot, but just cycles back to fastboot mode after about 1 minute.
Any help will be appreciated,
Thanks
Click to expand...
Click to collapse
I suggest, use kitchen.
gguemez said:
Hi,
I am trying to build a custom boot image to get rid of the immutable files of my P7-L00.
Specifically I haved done this : At a specific point in the boot process the rc scripts execute the set_immutable command with a 1 parameters that sets the immutable bits in all the files mentioned in the set_immutable.list file. If this command is changed to a 0 it clears the immutable bit for all the files. I have buit the custom ramfs necesary for this but when I repack the boot image it will not boot.
I am using the following command for mkbootimg ....
mkbootimg --kernel mykernel.img --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x04000000 --base 0x07000000 --cmdline "k3v2mem k3v2_ion=1 vmalloc=448M maxcpus=4 initcall_debug=n" -o newimg.img
The resulting first page looks ok, it has the same offsets as my original working boot image, but as I mentioned before, it does not boot, but just cycles back to fastboot mode after about 1 minute.
Any help will be appreciated,
Thanks
Click to expand...
Click to collapse
You are correct in saying that modifying the setimmutable binary flag from 1 to 0 in the boot image solves the set_immutable.list problem referred to many times in various posts in this forum..
I have a P7-L07 emui2.3 B125 and a P7-L10 emui3.0 B609. I had no trouble modifying the boot.img for the L07 using
linux-kernelkitchen-0.002 under xubuntu. The L10 is a different story but the main problem is faulty flash memory.
At any rate, you don't really need to worry about the boot.img file at all. A simple and easy work around is to replace the file set_immutable.list with another empty file of the same name. This works quite well on my L10. I used the file manager FX to achieve this. As long as you have root access and can change file permissions correctly this method will work for you.
arthios said:
You are correct in saying that modifying the setimmutable binary flag from 1 to 0 in the boot image solves the set_immutable.list problem referred to many times in various posts in this forum..
I have a P7-L07 emui2.3 B125 and a P7-L10 emui3.0 B609. I had no trouble modifying the boot.img for the L07 using
linux-kernelkitchen-0.002 under xubuntu. The L10 is a different story but the main problem is faulty flash memory.
At any rate, you don't really need to worry about the boot.img file at all. A simple and easy work around is to replace the file set_immutable.list with another empty file of the same name. This works quite well on my L10. I used the file manager FX to achieve this. As long as you have root access and can change file permissions correctly this method will work for you.
Click to expand...
Click to collapse
Thank your for the info. In the P7-L00 with a KingUser Root I could not change the set_immutable.list to anything. Any attempt to modify the file, replace or change the permissions would fail, since the immutable bit was set.
Having fixed the problem I mentioned above I now find myself with the situation that if I change some, I can't say all files, in the system directory the phone reboot immediately. I dont know if this is due to the "partial" root some people say kinguser provides or to some other issue.
I will keep playing around, thanks for the help.
gguemez said:
Thank your for the info. In the P7-L00 with a KingUser Root I could not change the set_immutable.list to anything. Any attempt to modify the file, replace or change the permissions would fail, since the immutable bit was set.
Having fixed the problem I mentioned above I now find myself with the situation that if I change some, I can't say all files, in the system directory the phone reboot immediately. I dont know if this is due to the "partial" root some people say kinguser provides or to some other issue.
I will keep playing around, thanks for the help.
Click to expand...
Click to collapse
changing the 1 to 0 of set_immutable in rc won't work. i already tried that thing. i used 609 boot.img, unpack and repack it successfully but it wont work.
majcomtech said:
changing the 1 to 0 of set_immutable in rc won't work. i already tried that thing. i used 609 boot.img, unpack and repack it successfully but it wont work.
Click to expand...
Click to collapse
Thanks, do you also get the same effect of an immediate reboot when you modify system files? That is what I am really after, since I can't change anything I can't even update the SU or change any files ...
gguemez said:
Thanks, do you also get the same effect of an immediate reboot when you modify system files? That is what I am really after, since I can't change anything I can't even update the SU or change any files ...
Click to expand...
Click to collapse
if you want full root, i already made tut for that. http://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
majcomtech said:
changing the 1 to 0 of set_immutable in rc won't work. i already tried that thing. i used 609 boot.img, unpack and repack it successfully but it wont work.
Click to expand...
Click to collapse
Thanks, I have tried this but in my case it has not worked. Everytime I reboot the phone the files are all back, as if there is a backup partition or something. I an now trying to do this via a UPDATE with CWM...
Thanks again.
gguemez said:
Thanks, I have tried this but in my case it has not worked. Everytime I reboot the phone the files are all back, as if there is a backup partition or something. I an now trying to do this via a UPDATE with CWM...
Thanks again.
Click to expand...
Click to collapse
I expect you are quite fed up by now and I offer my commiserations. There may be however be another solution to your problem. Have you considered downloading a custom ROM for your L00 created (say) by KangVIP or Killprocess, and then extracting the boot image from the zip file and flashing that? These boot images have the set_immutable flag set to 0. As I recall, the ROMs from KangVIP are password protected so a Killprocess ROM or one from someone else might be better. If you do decide to try this out, make sure the build number of the downloaded ROM is similar to yours. The boot images differ between emui2.3 and emui3.0. Good luck!
gguemez said:
Thanks, I have tried this but in my case it has not worked. Everytime I reboot the phone the files are all back, as if there is a backup partition or something.
Click to expand...
Click to collapse
Seems like you have locked bootloader.
Kostyan_nsk said:
Seems like you have locked bootloader.
Click to expand...
Click to collapse
No, the bootloader is unlocked. I can change the boot partition at will, I have many times letf it unbootable and restored it with no problem. I will try to do something via the recovery parition but, the only one I have found that worked in my phone, always gives me errors when running my scripts (so I am obviously doing something wrong).
I got to the point of sending a script that says ... ui_print ("Hello World"); ... but that gives me an error too!
I will keep trying to figure this out, thanks for your help.
Guillermo
What value has "fblock=" parameter in "/proc/cmdline"?
Hi,
Seeing if anyone has stock images (system & boot) for the Urbane. I have hours of searching in online and came up empty. I flashed a system file that didn't belong and am now stuck on the splash screen. Does anyone have or has anyone seen the stock images??
Thanks in advance.
You sound like you know more about this stuff than me, but can you use the OTA update and recovery in the development forum? Would a factory reset overwrite system changes?
I was able to find a TWRP backup that was submitted on the forum for a LGWR development that worked perfectly. I will say I put my self through a lot of trouble as the rom I flashed messed with partitions and write permissions. I ended up doing a wipe in TWRP followed by individually wiping each partition. Then I was able to load the backup through adb and restore.
Thanks!
rwade434 said:
Hi,
Seeing if anyone has stock images (system & boot) for the Urbane. I have hours of searching in online and came up empty. I flashed a system file that didn't belong and am now stuck on the splash screen. Does anyone have or has anyone seen the stock images??
Thanks in advance.
Click to expand...
Click to collapse
Hi @rwade434,
Were you able to find a way to recover? I have got myself (stupid me!) into trouble by flashing the wrong ROM (damn!) and now I am stuck into fastboot menu!
Any idea how and where to get the original LJZ13E or LDZ22D image back to our Urbane?
Thanks a lot.
Ok, I have got myself out of misery by following the nice thread at http://forum.xda-developers.com/watch-urbane/general/twrp-2-8-6-0-test-build-t3122005. There was the TWRP recovery and the 5.1.1. image backup. Thanks for the tips.
It certainly wasn't easy for me to find, it doesn't seem the the Urbane is really owned by anyone out there.
Were you able to find any ROMS for the Urbane?
This works to get the watch back to the last firmware version, but it seems that the system remains modified and unable to take the newest 1.3 firmware (Status 7 error). If anyone has the true, factory images (non-TWRP), I sure would appreciate them being posted (as I am sure others would too). Worst case scenario, a TWRP backup of the latest 1.3 image would work, too. Thanks!
meatlocker said:
This works to get the watch back to the last firmware version, but it seems that the system remains modified and unable to take the newest 1.3 firmware (Status 7 error). If anyone has the true, factory images (non-TWRP), I sure would appreciate them being posted (as I am sure others would too). Worst case scenario, a TWRP backup of the latest 1.3 image would work, too. Thanks!
Click to expand...
Click to collapse
Follow the step (copy from www reddit com/r/AndroidWear/comments/3hsmkq/ota_downloads/), it can fix the problem.
-----------------------------------------
The first thing that I did was relocked my bootloader, then unlocked it again, which wipes everything (again). Next, I used the adb shell command, and typed "su" to gain Super User. Then, I mounted the file system to r/w, using the following command: mount -o remount,rw /system Next, I cd'd to system/bin. In system/bin, I used the mv command to rename the app_process32_original file to app_process32. That looks like: mv app_process32_original app_process32. Then, I renamed the install-recovery_original.sh file to install-recovery.sh (using the same mv command as above).
-----------------------------------------
And then reboot into recovery mode and sideload the new ota.
Hahaha, that's a first for me. You quoted my own comment from Reddit. I hope my solution helps someone else. Have a 'thanks' for offering to help someone, Alex.
@rwade
rwade434 said:
I was able to find a TWRP backup that was submitted on the forum for a LGWR development that worked perfectly. I will say I put my self through a lot of trouble as the rom I flashed messed with partitions and write permissions. I ended up doing a wipe in TWRP followed by individually wiping each partition. Then I was able to load the backup through adb and restore.
Thanks!
Click to expand...
Click to collapse
Could you tell me what folder did you use to store the backup.zip? I've been trying to bring my Urbane back to life. It's driving me crazy.
mseck said:
Could you tell me what folder did you use to store the backup.zip? I've been trying to bring my Urbane back to life. It's driving me crazy.
Click to expand...
Click to collapse
https://mega.nz/#!0N0SiCrK!NEHqeolukz7jkuazn3V3eHSzVMC2hcEDbk4P3-cU7mY
Copy the folder of the zip into TWRP/BACKUP/505KPZK0107693/ and restore backup
potaturrias said:
https://mega.nz/#!0N0SiCrK!NEHqeolukz7jkuazn3V3eHSzVMC2hcEDbk4P3-cU7mY
Copy the folder of the zip into TWRP/BACKUP/505KPZK0107693/ and restore backup
Click to expand...
Click to collapse
Do i live the file as RAR or change it to ZIP? or unzip and move the folder itself?
@rwade434
Thank you for the TRWP back up, I had a couple issue creating directories so i created them manual. and Copy/paste each file.
I've been without my watch for 4 Days. Thank you much!
Factory reset, like new
Note:
This is not bootanimation, this is the splash screen (the 'Huawei' boot logo which is displayed when device is switched ON)
This is for Huawei P8 Lite 2017 Only.. (Resolution 1080x1920)
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Huawei P8 Lite 2017 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
Use this tool and instructions:
Huawei OEM_logo Changer
Note: Use a 1080x1920 pic, as .bmp file (in rgb565 format as specified in that post)
Old method:
STEPS to create boot logo:
1. Download & Extract this in computer: Huawei_P8_Lite_2017_Logo_Maker.zip
2. Make sure you have a picture in BMP format with resolution exactly 1080x1920px. (Can be of any format)
3. Now rename your picture as logo.bmp & replace it inside "pics" folder of the extracted folder. (Or directly edit the 'logo.bmp' file)
4. Finally, run the 'CREATE_LOGO.bat' to create oeminfo.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash boot logo:
Steps to backup your oeminfo.img:
Open Terminal Emulator, type the following command to save your stock oeminfo.img to your Internal Storage:
Code:
su
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo_stock.img
Now, choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_logo.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the oeminfo.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/oeminfo.img of=/dev/block/platform/hi_mci.0/by-name/oeminfo
c. To flash from Fastboot mode:
Code:
fastboot flash oeminfo oeminfo.img
Finally, Reboot and check if the bootlogo has changed!!
Note:
Incase something goes wrong or device doesn't bootup, just flash the stock oemlogo.img from custom recovery or fastboot.
Credits:
1. @CrimsonBloodfang who provided the stock oemlogo.img of P8 Lite 2017 (PRA-LX2)..
2. @GokulNC (myself ) who wrote this script
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Is that working with all variants of the p8lite 2017? I rebranded mine to the Chinese Honor Version.
Doesn't work for me., same logo as before.
rebranded mine too
---------- Post added at 09:07 PM ---------- Previous post was at 09:05 PM ----------
https://imgur.com/a/XAup4
just made this btw, it's already in the right format.
GokulNC said:
TESTING:
@CrimsonBloodfang
1. Can you please check if this tool is working??
2. Please check if flashing the zip from custom recovery works.
3. Please attach your 'oeminfo' partition backup. I guess it might have the logo inside it (if the above procedure doesn't work)
4. Are there different variants of P8 Lite like P8lite 2017 , etc. ?
Click to expand...
Click to collapse
1. I am able to create a new "oemlogo.mbn" and a "flashable_logo.zip" through your tool but unfortunately the stock boot logo of Huawei still shows up in every reboot, after using the two files.
2. The zip file works in TWRP Recovery and was flashed without errors but the stock boot logo still shows upon reboot then after rebooting, I checked /product/etc/logo/ and the stock oemlogo.mbn was not replaced with the new one.
3. Here is the oeminfo.img backup, by using this command in a terminal emulator
Code:
su
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo.img
and this one is the raw file itself. I only used two out of three methods of backing up the oeminfo partition based from this thread because I was unsure as to where in TWRP Recovery should I find the backup for oeminfo partition since it only has the options Boot, Cache, Data, System and Vendor for backup. Maybe in the "Vendor" partition, but the backup size is 394 MB.
4. I'm not sure for the variants of Huawei P8 Lite, maybe only Huawei P8 Lite (2017) and the ones on the "download section" in this link? If you meant the Huawei P8 Lite (2017) variants, the ones I know are Huawei P8 Lite (2017) PRA-LX1, PRA-LX2, PRA-LX3, PRA-LA1 and PRA-TL00. I'm using the Huawei P8 Lite (2017) PRA-LX2.
I've also tried copy pasting the new oemlogo.mbn then changed it to the correct permissions (-rw-r--r--). I even tried renaming it to "oemlogo.mbn.bak" to see if there's any change but it seems that this file is not in control of the boot logo. We also have the boot warning logo too by the way, the one that is caused by unlocking the bootloader.
Here is my own logo.bmp boot logo, 1080x1920 resolution, edited through Gimp 2 and exported as .bmp file format.
Edit: Does anyone know where is the exact location for our boot logo files? I've also found the same oemlogo.mbn file on some folders in /product/hw_oem
@CrimsonBloodfang
The oeminfo.img file had the pictures as I guessed.
I have updated the OP with the new tool. Please check if it's working
Also, I think the files in the '/product/hw_oem/whatever' directory are created from the oemlogo partition while booting (not sure though).
So maybe using the old tool, setting the permissions for oemlogo.bin as -r--r--r-- might have worked (since write access is denied).
Edit:
As specified in GSMArena website, is it true that P8 Lite (2017) is also called Huawei P9 Lite (2017), Huawei Honor 8 Lite, Huawei Nova Lite, Huawei GR3 (2017) ???
If yes, this tool MIGHT work for those devices too.
Thanks! I will be testing it now.
GokulNC said:
@CrimsonBloodfang
Edit:
As specified in GSMArena website, is it true that P8 Lite (2017) is also called Huawei P9 Lite (2017), Huawei Honor 8 Lite, Huawei Nova Lite, Huawei GR3 (2017) ???
If yes, this tool MIGHT work for those devices too.
Click to expand...
Click to collapse
Yes, it is called with different names from different countries and they are more or less, just the same devices.
In the Philippines, this phone is called the Huawei GR3 (2017).
Edit:
Maybe the users need to backup their own "oeminfo.img" first before using the tool and can you add it on OP? They might use my device's oeminfo.img if they forgot to backup and it might change their device's region settings then their stock updates would be based from my country.
I haven't rebranded my phone, just went straight to LineageOS 14.1 so I'm not sure about the consequences of flashing other oeminfo.
still not working for me. Now it's just booting into eRecovery and the logo was changed to the original one
@GokulNC
It also didn't work for me. I've tested it six or more times with both the Terminal Emulator and the TWRP Recovery flash method.
Edit:
The logo file in "pics" folder of the tool has a logo.png and not anymore a logo.bmp, so I tried both file formats just in case. I've tried replacing it with logo.bmp, I've tried replacing it with logo.png and I've tried placing both logo.bmp and logo.png together on the "pics" folder. Then flashed the six different files of oeminfo.img and flashable_logo.zip with Terminal Emulator and TWRP Recovery, but on every reboot, the boot logo is still at stock.
The only locations left I can guess as to where the boot logo files for Huawei P8 Lite (2017) are maybe in the Boot partition or it's embedded in the Kernel.
@CrimsonBloodfang
Actually there were many .bmp pics inside the oeminfo.img
I didn't look at that properly.
When I extracted them, I saw 2 bootlogo images.
So I've modified the tool to change them both.
Try the new tool that I've uploaded now and see if it's working
It should contain 2 files named logo1.png and logo2.png
CrimsonBloodfang said:
The only locations left I can guess as to where the boot logo files for Huawei P8 Lite (2017) are maybe in the Boot partition or it's embedded in the Kernel.
Click to expand...
Click to collapse
Nope, I don't think so..
MIcHiJK said:
Is that working with all variants of the p8lite 2017? I rebranded mine to the Chinese Honor Version.
Click to expand...
Click to collapse
I'm not sure if the oeminfo partition is same across all the different firmwares.
I guess they all must be the same. If you can attach your stock 'oemlogo.img', I'll take a look at it.
CrimsonBloodfang said:
The logo file in "pics" folder of the tool has a logo.png and not anymore a logo.bmp, so I tried both file formats just in case. I've tried replacing it with logo.bmp, I've tried replacing it with logo.png and I've tried placing both logo.bmp and logo.png together on the "pics" folder.
Click to expand...
Click to collapse
My tool automatically converts everything to .bmp format, so it doesn't matter
Striike said:
still not working for me. Now it's just booting into eRecovery and the logo was changed to the original one
Click to expand...
Click to collapse
I'm not sure about the rebranded device. Can you please attach your 'oeminfo' file?
I'll check that out.
GokulNC said:
@CrimsonBloodfang
Actually there were many .bmp pics inside the oeminfo.img
I didn't look at that properly.
When I extracted them, I saw 2 bootlogo images.
So I've modified the tool to change them both.
Try the new tool that I've uploaded now and see if it's working
It should contain 2 files named logo1.png and logo2.png
Click to expand...
Click to collapse
Ok, I've flashed the flashable_logo.zip using the new tool and it seems to work. Boot logo is not anymore the stock one but instead, it's replaced by a "glitched image" with a color green background and two rectangles with colors pink and blue, not the boot logo I made. Boot warning sign is still there afterwards though.
It may be a wrong procedure on my part because I just placed my logo.bmp together with the logo1.png and logo2.png but I will continue tinkering and testing it or have a lower file sized image to see if I can finally get the desired boot logo.
---------- Post added at 11:04 PM ---------- Previous post was at 10:52 PM ----------
Also flashed my backup oeminfo.img through Terminal Emulator or TWRP Recovery and everything went back to normal.
@GokulNC
Tested it many times, boot logo always end up with the "glitched image" as attached below.
This is not the original image. Just an edited image through Gimp 2, for reference.
CrimsonBloodfang said:
@GokulNC
Tested it many times, boot logo always end up with the "glitched image" as attached below.
This is not the original image. Just an edited image through Gimp 2, for reference.
Click to expand...
Click to collapse
Does this arise after changing the logo2.png (or logo2.bmp)??
Is that the same output no matter what the logo2 is?
I mean, even for the default one that I've placed in pics folder or what you replaced with, is the output the same weird image??
FYI, ensure there are only 2 images in the pics folder while creating the oemlogo.img, ie, logo1.<whatever_format> and logo2.<whatever_format>
GokulNC said:
Does this arise after changing the logo2.png (or logo2.bmp)??
Is that the same output no matter what the logo2 is?
I mean, even for the default one that I've placed in pics folder or what you replaced with, is the output the same weird image??
FYI, ensure there are only 2 images in the pics folder while creating the oemlogo.img, ie, logo1.<whatever_format> and logo2.<whatever_format>
Click to expand...
Click to collapse
Yes, I've already tried different ways like replacing only the logo2.png or replace both images and also ensured there are two images in the pics folder.
I also tried using only the "default images" and did not replace anything in the pics folder, then flashed the newly created files and the resulting boot logo is still the glitched image.
Edit:
The image in this post is what the glitched image of the boot logo, actually looks like.
GokulNC said:
Note:
This is not bootanimation, this is the splash screen (the 'Lenovo' boot logo which is displayed when device is switched ON)
This is for Huawei P8 Lite 2017 Only.. (Resolution 1080x1920)
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Huawei P8 Lite 2017 (any ROM)
2. Optional:Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create boot logo:
1. Download & Extract this in computer: Huawei_P8_Lite_2017_Logo_Maker.zip
2. Make sure you have a picture in BMP format with resolution exactly1080x1920px. (Can be of any format)
3. Now rename your picture as logo.bmp & replace it inside "pics" folder of the extracted folder. (Or directly edit the 'logo.bmp' file)
4. Finally, run the 'CREATE_LOGO.bat' to create oeminfo.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash boot logo:
Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_logo.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the oeminfo.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
c. To flash from Fastboot mode:
Finally, Reboot and check if the bootlogo has changed!!
Note:
Incase something goes wrong or device doesn't bootup, just flash the stock oemlogo.img from custom recovery or fastboot.
Credits:
1. @CrimsonBloodfang who provided the stock oemlogo.img of P8 Lite 2017 (PRA-LX2)..
[email protected] (myself ) who wrote this script
Hit the Thanks:good: button if it worked for you
You're welcome to post the splash images that you created..
Click to expand...
Click to collapse
Thanks bro
Very useful guide
CrimsonBloodfang said:
Yes, I've already tried different ways like replacing only the logo2.png or replace both images and also ensured there are two images in the pics folder.
I also tried using only the "default images" and did not replace anything in the pics folder, then flashed the newly created files and the resulting boot logo is still the glitched image.
Edit:
The image in this post is what the glitched image of the boot logo, actually looks like.
Click to expand...
Click to collapse
Hi, sorry for my late reply. Got stuck up with something lately.
I have attached a new tool, with little changes.
Please check if it's working.
If it doesn't, I'm not sure what else to do.
honorfan said:
Thanks bro
Very useful guide
Click to expand...
Click to collapse
Hi, did this work for you?
Thanks, I will be testing it later. I've also found out from another user that changing the boot logo using the tool, has stopped working in Nougat and Oreo.
Here is what he said, and this thread is also changing their Huawei device using the oeminfo partition.
Maybe you already know these?
@GokulNC
Tested it twice, it's still showing the glitched image.
My first attempt was replacing the logo2.png with another image as logo2.bmp. Flashed the files through TWRP Recovery, rebooted and the result is still the glitched image.
Second attempt was to not replace anything in the "pics" folder. Created the files, flashed them in TWRP Recovery, rebooted and the result is still the same.
I've been searching around xda forums for information about editing Huawei's oeminfo for its boot logo image and I noticed that their tutorials needs to follow a "specific RGB format" when editing the images to be used as a boot logo. (Bitmap file with color depth not less than 16 bit, supported color schemes: RGB555, RGB565, RGB888, RGB8888)
Although, I'm uncertain that this might be the cause of the problems and I haven't tried it yet.
- Follow any of the RGB formats to fix the problem.
I've only tried "RGB565" and "RGB888 with color depth of 24 bits".
On the other hand, seeing the "glitched image" as a boot logo, might just only be an indication of a corrupted oeminfo, when it's not properly recompiled or reconstructed?
Just to be sure, I'll place the links of the threads and posts, that I think might be useful for reference.
You might have already read these threads before.
- How To Change The Splash Screen or Boot Logo In Huawei Honor 7 at post #2
- Scroll down to Part VII - How To Change The Splash Screen
- Solution by Kostyan_nsk
- [HOW TO] Replace initial splash screen (logo) on Huawei P7
- [GUIDE] Changing boot splash image on the Huawei Y6
I will try changing the RGB formats for the image that I'll be editing, to see if it makes a difference.
--- Please don't quote this entire post ---
I have, with the help of two people who's XDA I don't know, just unlocked an Honor 9 Lite without an unlock code!:angel: The method follows:
Initial revision
0. Prepare adb and fastboot. On windows, change all
Code:
fastboot
commands to
Code:
.\fastboot
and similarly for
Code:
adb
(skip to step 2 if you have the June 2018 patch or earlier)
1a. Downgrade firmware to 8.0.0.xxx (June patch) via androidhost.ru - search for your device, get a C432 version.
1b. Downgrade, instructions are in the 'ReleaseDoc' folder. Use the forced install method
(do not reboot the phone until step 3a is complete)
2a. Enter
Code:
fastboot
2b. Enter powershell or terminal and type:
Code:
fastboot oem hwdog certify begin;fastboot oem get-product-model
2c. Send the result to @huaweihax telegram group or in this thread (telegram will have faster response times)
2d. We will send you your slock when we gets a chance. Please be patient, we have real lives. Download it on the same pc as you have fastboot on.
2e. Copy the slock to your working directory
2f. Type in your shell:
Code:
fastboot flash slock <slock_filename>
(Download twrp on the pc that has fastboot, copy to working directory)
3a.
Code:
fastboot flash erecovery_ramdisk <twrp filename>
3b. Read step 3c and 3d
3c.
Code:
fastboot reboot
3d. Hold volume up AFTER the phone vibrates
3e. Twrp should boot up. If not, reboot it and try 3d again
(Each reboot until step 4 is complete, you will restart step 4)
4a. Connect usb
4b.
Code:
adb shell dd if=/dev/block/bootdevice/by-name/nvme of=/tmp/nvme
4c.
Code:
adb pull /tmp/nvme
You may now reboot the device, if you want.
5a. Open the nvme file in a hex editor. Find 'FBLOCK' in the file. There should be '8' shortly before the fblock. Move down exactly one line from '8' and you will see 01. Change that to 00 and repeat for all instances of fblock in the file. Save the file.
5c.
Code:
adb push nvme /tmp/nvme
5d.
Code:
adb shell dd if=/tmp/nvme of=/dev/block/bootdevice/by-name/nvme
6. Reboot!
CONGRATS! YOUR DEVICE IS NOW UNLOCKED!
Latest revision:
0. Prepare adb and fastboot. On windows, change all fastboot commands to ./fastboot and similarly for adb
Skip to step 2 if you have the June 2018 patch or earlier
1a. Downgrade firmware to June patch via androidhost.ru - search for your device, any C number should work.
1b. Downgrade, instructions are in the 'ReleaseDoc' folder. Use the forced install method
2a. Enter fastboot
2b. DO NOT REBOOT THE PHONE UNTIL STEP 3a is complete!!! Failing to follow this will result in anger!
2c. Enter powershell or terminal and type:
Code:
fastboot oem hwdog certify begin;fastboot oem get-product-model;fastboot oem get-build-number
2c. Send the result in the telegram group @huaweiHax (link to the public group is at the start of the channel), or, if that's entirely impossible, PM @OldDroid on XDA.
2d. A nice guy will send you your slock. Please be patient, they have real lives. Download it on the same pc as you have fastboot on.
2e. Copy the slock to your working directory
2f.
Code:
fastboot flash slock <slock_filename>
(Download twrp on the pc that has fastboot, copy to working directory)
3a.
Code:
fastboot flash erecovery_ramdisk <twrp filename>
3b. Read step 3c and 3d
3c.
Code:
fastboot reboot
3d. Hold volume up AFTER the phone vibrates
3e. Twrp should boot up. If not, reboot it and try 3d again
4a. Connect usb
4b.
Code:
adb shell dd if=/dev/block/bootdevice/by-name/nvme of=/tmp/nvme
4c.
Code:
adb pull /tmp/nvme
WARNING: FOLLOW THESE STEPS VERY CAREFULLY AND DOUBLE-CHECK EVERYTHING!
5a. Open the nvme file with a hex editor. Repeat step 5b until you have done all the instances of FBLOCK.
5b. Search the file for FBLOCK. For each instance, you should see the character 8 shortly before. Go down exactly one line from the 8. Select the .. You should see 01 become highlighted in the hex area. Change the 01 to 00 and repeat 6 more times (7 in total). Save the file as nvmepatched
5c.
Code:
adb push nvmepatched /tmp/nvme
5d.
Code:
adb shell dd if=/tmp/nvme of=/dev/block/bootdevice/by-name/nvme
6. Reboot!
CONGRATS! YOUR DEVICE IS NOW UNLOCKED!
----------------------------------------------------------------
Files you might find useful:
nvme.zip: a twrp flashable zip that automates step 5 of the instructions. I have tested it and it works fine for me. If TWRP crashes and restarts, that's fine, but idk why it happens. If it happens to you, please send /tmp/recovery.log to me in pm or here, or in telegram
autoroot.zip: a zip file containing a python script and related files to automatically unlock Huawei's. To use it, put a twrp file called 'twrp-kirin.img' in the 'files' subfolder. I cannot upload that file due to XDA file size restrictions.
https://www.androidfilehost.com/?w=files&flid=285583: thanks to @mrmazak, this is a windows batch tool version of autoroot.zip
In the attached photos you will see correct and incorrect converted "slock files"
When you follow the guide from above. Between 2-C and 2-D.
If the you get just a long string of letters and numbers (512 characters to be exact). That string of numbers it that state is "text" it needs to be "HEX". , to do this there are command line tools to do it. But it can be done in a user friendly way in a hex editor program. But this needs to done as hex and not text. The photos show both examples.
In the correct edited photo the long string is written to the left side (the hex area)
In the incorrect edited photo the long string is written to the right side (the text area).
SLOCK CONVERSION
FOR command line use
Copy the long string of text as regular txt file NO EXTRA SPACES -- for this example name it slock.txt
Command line code for linux: Needs "XDD" It should already be installed on most systems.(inside VIM)
Code:
cat slock.txt | xxd -r -p > binary-slock.bin
Command line code for Windows: Needs "XDD.exe" It canbe found inside VIM http://www.vim.org/
Code:
type slock.txt | xxd.exe -r -p > binary-slock.bin
NVME EDITS
Linux terminal
Code:
sed 's/\x46 \x42 \x4C \x4F \x43 \x4B \x00 \x00 \x01 \x00 \x00 \x00 \x01/\x46 \x42 \x4C \x4F \x43 \x4B \x00 \x00 \x01 \x00 \x00 \x00 \x00/g' nvme > temp
Windows cmd version needs GNU-SED
OR
reg-expression-tool LIKE "jrepl.bat" (one of my favorite little tools)
Code:
files\JREPL.BAT "\x46\x42\x4C\x4F\x43\x4B\x00\x00\x01\x00\x00\x00\x01" "\x46\x42\x4C\x4F\x43\x4B\x00\x00\x01\x00\x00\x00\x00" /m /x /f modified-nvme /o -
Scripted method
Windows batch file tool
Use newest version in the folder. And allow tool to update, when first ran.
.
.
mrmazak said:
this sounds like great news for continuing custom roms on Huawei.
Just want to ask about the above section.
Are you saying just the sending of data will be rolled into an app, or the whole thing will be self contained in an app?
Click to expand...
Click to collapse
Just the second stage of sending data, olddroid is 'thinking' about making them both automated, but right now, neither is.
hackintosh5 said:
Just the second stage of sending data, olddroid is 'thinking' about making them both automated, but right now, neither is.
Click to expand...
Click to collapse
It'd be really helpful if he did that. And by the way thanks for sharing.
Hi my phone version is c185 what should i do?
moonknight01 said:
Hi my phone version is c185 what should i do?
Click to expand...
Click to collapse
Try to use the c00 firmware, it may or may not dload. If it fails, theres not much you can do.
hackintosh5 said:
Try to use the c00 firmware, it may or may not dload. If it fails, theres not much you can do.
Click to expand...
Click to collapse
In c185 wouldnt work?
Sent from my LLD-L21 using Tapatalk
moonknight01 said:
In c185 wouldnt work?
Click to expand...
Click to collapse
There's no c185 dloadfirmware, so try c432. It may fail the install, it might not. I just don't know.
Honor 9 lite c636
Can C636 work?
aldinista said:
Can C636 work?
Click to expand...
Click to collapse
Again, try another firmware like c432 or c00, but it all depends on whether the dload works or not. If it doesn't install, you'll have to find one that does. If it installs you'll be ok. Just flash the correct model firmware after completing the exploit
hackintosh5 said:
Again, try another firmware like c432 or c00, but it all depends on whether the dload works or not. If it doesn't install, you'll have to find one that does. If it installs you'll be ok. Just flash the correct model firmware after completing the exploit
Click to expand...
Click to collapse
Oke i try.. ?
Hehehe, sorry because I'm not yet so familiar.
I'm still a beginner ??
@hackintosh5
My LLD-L21 (C636) bricked with Bootloader is Relocked & FRP Locked, but has been solved now with the help of your tutorial.
Thanks you so much sir. :good::good::good:
Wait but how can you flash something from fastboot if the bootloader is locked?
Fredin_ said:
Wait but how can you flash something from fastboot if the bootloader is unlocked?
Click to expand...
Click to collapse
Please unquote the entire post... Then I'll respond.
It beggars belief sometimes..........I mean its the very FIRST line in the bloody post.........???
What more can you do, even it was in BIG RED CAPITALS it would still happen.
Sparkrite said:
It beggars belief sometimes..........I mean its the very FIRST line in the bloody post.........???
What more can you do, even it was in BIG RED CAPITALS it would still happen.
Click to expand...
Click to collapse
Dude chill......... was a mistake sorry ?
---------- Post added at 06:12 PM ---------- Previous post was at 06:12 PM ----------
hackintosh5 said:
Please unquote the entire post... Then I'll respond.
Click to expand...
Click to collapse
Sorry forgot that part ?
Fredin_ said:
Dude chill......... was a mistake sorry ?
---------- Post added at 06:12 PM ---------- Previous post was at 06:12 PM ----------
Sorry forgot that part ?
Click to expand...
Click to collapse
Okay
Fredin_ said:
Wait but how can you flash something from fastboot if the bootloader is locked?
Click to expand...
Click to collapse
Slock and rescue_recovery can be flashed without unlocking. Don't ask me why, ask Wavei.
hackintosh5 said:
Slock and rescue_recovery can be flashed without unlocking. Don't ask me why, ask Wavei.
Click to expand...
Click to collapse
K thanks man?
SeenThings said:
@hackintosh5
My LLD-L21 (C636) bricked with Bootloader is Relocked & FRP Locked, but has been solved now with the help of your tutorial.
Thanks you so much sir. :good::good::good:
Click to expand...
Click to collapse
Hi bro did you get unlock boot loader?
Sent from my LLD-L21 using Tapatalk