Greetings
I followed these procedures, and pushed the boot.img with Odin, but the phone goes into download mode stating: "Could not do normal boot." Can anyone see what I am doing wrong? How can I troubleshoot the issue? Is there some way I can look at some logs somewhere? I did save my recovery.log file from twrp to the sdcard before I loaded the backedup files and rebooted the phone. I put them here is there anything else I can do?
I tried the same thing with boot.img and I got the following:
Code:
[email protected]:~/xiaolu/mkbootimg_tools$ ./mkboot boot.img ksumag
Unpack & decompress boot.img to ksumag
kernel : zImage
ramdisk : ramdisk
page size : 2048
kernel size : 8262680
ramdisk size : 1064985
dtb size : 1300480
base : 0x00000000
kernel offset : 0x00008000
ramdisk offset : 0x02000000
second_offset : 0x00f00000
tags offset : 0x01e00000
dtb img : dt.img
cmd line : console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3
ramdisk is gzip format.
Unpack completed.
[email protected]:~/xiaolu/mkbootimg_tools$ cd ksumag/
[email protected]:~/xiaolu/mkbootimg_tools/ksumag$ ls
dt.img img_info ramdisk ramdisk.gz zImage
[email protected]:~/xiaolu/mkbootimg_tools/ksumag$
I put the scsi_wait.ko ( name? ) file in ramdisk /dev folder, and replaced the zImage and dt.img file with the ones I made, and packed them into my own boot.img file.
Here is the output:
Code:
[email protected]:~/xiaolu/mkbootimg_tools$ ./mkboot ksumag/ boot.img
mkbootimg from ksumag//img_info.
kernel : zImage
ramdisk : new_ramdisk.gz
page size : 2048
kernel size : 8262680
ramdisk size : 1082259
dtb size : 1300480
base : 0x00000000
kernel offset : 0x00008000
ramdisk offset : 0x02000000
tags offset : 0x01e00000
dtb img : dt.img
cmd line : console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3
Kernel size: 8262680, new ramdisk size: 1082259, boot.img: 10893312.
boot.img has been created.
...
Then I put all files in a tar file. I did make a couple of mistakes with files names, which I hope did not damage the boot.img file.
Code:
[email protected]:~/xiaolu/mkbootimg_tools$ tar -H ustar -c boot.img >> boot.img
tar: boot.img: file is the archive; not dumped
[email protected]:~/xiaolu/mkbootimg_tools$ ls
ARM dtbToolCM ksumag mkbootimg recovery.img
boot.img dtbtool.txt lz4 MyKernel.tar.md5 recovery.tar.md5
commands dtc mkboot oldfiles shahin
dtbTool ksuamg mkbootfs README.md sm-n900p-test1
[email protected]:~/xiaolu/mkbootimg_tools$ tar -H ustar -c boot.img > boot.img
tar: boot.img: file is the archive; not dumped
[email protected]:~/xiaolu/mkbootimg_tools$ tar -H ustar -c boot.img > boot.tar
[email protected]:~/xiaolu/mkbootimg_tools$
Then I took the hash of the entire thing:
Code:
[email protected]:~/xiaolu/mkbootimg_tools$ md5sum -t boot.tar >> boot.tar
[email protected]:~/xiaolu/mkbootimg_tools$ mv boot.tar boot.tar.md5
[email protected]:~/xiaolu/mkbootimg_tools$
What are you trying to get
kenny1991 said:
What are you trying to get
Click to expand...
Click to collapse
I am trying to get a flashable image. The file I get from the above procedure goes on my phone, but the kernel does not seem to be loaded. I am still learning about the boot process, and I do not know if my phone just has a bootloader or a bootstrap also; regardless it seems to not load the kernel since it goes into download mode. The recovery.log does not show anything either. I posted in pastebin. I can put link to it here if you think it would help. My goal is to flash my phone with a copy of the kernel which I built myself.
Oh you need a developer to respond for that.
kenny1991 said:
Oh you need a developer to respond for that.
Click to expand...
Click to collapse
Do you know if I can move this thread myself or perhaps request it from one of the admins? I do not know how effective it would be if I put a link to this discussion in the developer forum.
You may ask as you can't move it. You should move it to developers discussion forum
I have a fresh unconnected BLU R1 HD. I want to do the following to it:
1. Unlock the Bootloader. The Device appears to run V6.1 of the firmware.
2. Install TWRP Recovery.
3. Install LineageOS
4. Install GAPPS
5. Install SuperSU.
I will do these tasks in whatever order is required to achieve the result of a Rooted Phone, running LineageOS and F-Droid, with no ADUPS. I do not wish to have simply a rooted Stock Rom, as eventually, I want to move to LineageOS 14, and get Nougat.
I will be using a Mageia Linux PC for this task. I have downloaded LineageOS 13.0 R1 HD V3.8. If I should need a newer port, say so. In addition, I have DirtyCow For Linux V3. Please, instruct me further.
zombie_ryushu said:
I have a fresh unconnected BLU R1 HD. I want to do the following to it:
1. Unlock the Bootloader. The Device appears to run V6.1 of the firmware.
2. Install TWRP Recovery.
3. Install LineageOS
4. Install GAPPS
5. Install SuperSU.
I will do these tasks in whatever order is required to achieve the result of a Rooted Phone, running LineageOS and F-Droid, with no ADUPS. I do not wish to have simply a rooted Stock Rom, as eventually, I want to move to LineageOS 14, and get Nougat.
I will be using a Mageia Linux PC for this task. I have downloaded LineageOS 13.0 R1 HD V3.8. If I should need a newer port, say so. In addition, I have DirtyCow For Linux V3. Please, instruct me further.
Click to expand...
Click to collapse
Few notes for you.
Use newest port build, not the one you mentioned. Many bugs on that version.
No need for superSU , Root is built into rom. In developer options menu
The tool has the directions and instructions for you. No need for another step by step here.
mrmazak said:
Few notes for you.
Use newest port build, not the one you mentioned. Many bugs on that version.
No need for super super. Root is built into room. In developer options menu
The tool has the directions and instructions for you. No need for another step by step here.
Click to expand...
Click to collapse
Alright in response to that, I have downloaded port V5.2. Is that the latest version?
Additionally, my distribution renames fastboot fastboot-android because there is another command called fastboot that has nothing to do with Android. (so I did a find and replace in your script to rename all instances of fastboot to fastboot-android.)
The file I downloaded seems to be a zip file, not an image file of any sort. Is that fine?
The step-by-step for dirty-cow seems to be about removing adups, installing TWRP, removing the Ads.
Additionally. The version of adb-tools I have is 4.4.2
zombie_ryushu said:
Alright in response to that, I have downloaded port V5.2. Is that the latest version?
Additionally, my distribution renames fastboot fastboot-android because there is another command called fastboot that has nothing to do with Android. (so I did a find and replace in your script to rename all instances of fastboot to fastboot-android.)
The file I downloaded seems to be a zip file, not an image file of any sort. Is that fine?
The step-by-step for dirty-cow seems to be about removing adups, installing TWRP, removing the Ads.
Click to expand...
Click to collapse
Yes 5.2 is right.
I believe I included fastboot binary in the tool and call that binary from the script, so you must verify your changes are correct.
The step-by-step , (that I wrote) has nothing to do with adups.
The tool is just collection of batch file (she'll script) and a replacement from.bin file, dirty-cow binary, and modified system file with a root shell built in. This is all done simply to force the ability to unlock bootloader.
mrmazak said:
Yes 5.2 is right.
I believe I included fastboot binary in the tool and call that binary from the script, so you must verify your changes are correct.
The step-by-step , (that I wrote) has nothing to do with adups.
The tool is just collection of batch file (she'll script) and a replacement from.bin file, dirty-cow binary, and modified system file with a root shell built in. This is all done simply to force the ability to unlock bootloader.
Click to expand...
Click to collapse
The fastboot binary is not inthe Zip I have for Linux. (DirtyCow-R1_HD-V6-Linux-V3.zip) Is this too old a version?
Do you use IRC by any chance?
zombie_ryushu said:
The fastboot binary is not inthe Zip I have for Linux. (DirtyCow-R1_HD-V6-Linux-V3.zip) Is this too old a version?
Do you use IRC by any chance?
Click to expand...
Click to collapse
there are too more updated version of the linux script.
this one is latest. It has not been "universal" and may have bugs based on version of linux you use.
DirtyCow-R1_HD-TOOL-V9+linux.zip : https://forum.xda-developers.com/devdb/project/dl/?id=23649
mrmazak said:
there are too more updated version of the linux script.
this one is latest. It has not been "universal" and may have bugs based on version of linux you use.
DirtyCow-R1_HD-TOOL-V9+linux.zip : https://forum.xda-developers.com/devdb/project/dl/?id=23649[/QUO
Due to my Anxiety on the issue, I accidentally adbed up the version I had, but I did not run the dirtycow exploit yet, should I start over, or keep going with what I have? (this is very Nerve Racking.)
Only Step 1 has been carried out.
Click to expand...
Click to collapse
zombie_ryushu said:
mrmazak said:
there are too more updated version of the linux script.
this one is latest. It has not been "universal" and may have bugs based on version of linux you use.
DirtyCow-R1_HD-TOOL-V9+linux.zip : https://forum.xda-developers.com/devdb/project/dl/?id=23649[/QUO
Due to my Anxiety on the issue, I accidentally adbed up the version I had, but I did not run the dirtycow exploit yet, should I start over, or keep going with what I have? (this is very Nerve Racking.)
Only Step 1 has been carried out.
Click to expand...
Click to collapse
you should be fine. The newer versions realy just add additional checks along the way in hopes of preventing trouble, and a way to find the cause of that trouble.
Click to expand...
Click to collapse
mrmazak said:
zombie_ryushu said:
you should be fine. The newer versions realy just add additional checks along the way in hopes of preventing trouble, and a way to find the cause of that trouble.
Click to expand...
Click to collapse
Alright. I will proceed with what I have. I downloaded your updated version and all of your Linux Binaries are x86_32 while my Distribution is x86_64.
Click to expand...
Click to collapse
#exit
> > > > > > > > > > > > > > > > Waiting 5 seconds...
[*] COPYING UNLOCK.IMG OVER TOP OF COPIED FRP IN /data/local/test NOT AS ROOT WITH DIRTYCOW
[*]
cowing. Start: 0, size: 102400
cowing. Start: 102400, size: 102400
cowing. Start: 204800, size: 102400
cowing. Start: 307200, size: 102400
cowing. Start: 409600, size: 102400
cowing. Start: 512000, size: 102400
cowing. Start: 614400, size: 102400
cowing. Start: 716800, size: 102400
cowing. Start: 819200, size: 102400
cowing. Start: 921600, size: 102400
cowing. Start: 1024000, size: 24576
checking md5 of new frp before copying to mmcblk0p17
unlock file does not match
Something Went Wrong Restarting phone and try again
press enter to exit
Does SP Flash Tool work on this version of the Blu ROM? If so, I found Colton's non-scripted procedure posted here easy to follow and it worked great on my Fedora Linux system when I did both of my phones. There are Linux versions of the flash tool: https://spflashtool.com/ Sorry, I am not familiar with the "dirty cow" stuff as SP Flash Tool worked well for me as detailed in this thread: https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
yaconsult said:
Does SP Flash Tool work on this version of the Blu ROM? If so, I found Colton's non-scripted procedure posted here easy to follow and it worked great on my Fedora Linux system when I did both of my phones. There are Linux versions of the flash tool: https://spflashtool.com/ Sorry, I am not familiar with the "dirty cow" stuff as SP Flash Tool worked well for me as detailed in this thread: https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
Click to expand...
Click to collapse
I don't know yet. I'm just sort of following the instructions.
zombie_ryushu said:
#exit
> > > > > > > > > > > > > > > > Waiting 5 seconds...
[*] COPYING UNLOCK.IMG OVER TOP OF COPIED FRP IN /data/local/test NOT AS ROOT WITH DIRTYCOW
[*]
cowing. Start: 0, size: 102400
cowing. Start: 102400, size: 102400
cowing. Start: 204800, size: 102400
cowing. Start: 307200, size: 102400
cowing. Start: 409600, size: 102400
cowing. Start: 512000, size: 102400
cowing. Start: 614400, size: 102400
cowing. Start: 716800, size: 102400
cowing. Start: 819200, size: 102400
cowing. Start: 921600, size: 102400
cowing. Start: 1024000, size: 24576
checking md5 of new frp before copying to mmcblk0p17
unlock file does not match
Something Went Wrong Restarting phone and try again
press enter to exit
Click to expand...
Click to collapse
please check if the file "working/new_frp_md5.txt" was created on you pc. Should have been in the folder "working" created in the tool folder
mrmazak said:
please check if the file "working/new_frp_md5.txt" was created on you pc. Should have been in the folder "working" created in the tool folder
Click to expand...
Click to collapse
It has not been. The folder mentioned is empty.
I can retry from Step 1 is thats required, but I really wish I had a more immediate way to respond to you.
zombie_ryushu said:
It has not been. The folder mentioned is empty.
I can retry from Step 1 is thats required, but I really wish I had a more immediate way to respond to you.
Click to expand...
Click to collapse
That seems odd. The earlier section of the script does the same md5 check , of the files pushed with adb in order to do the dirty-caw part. And it saves to same folder. And if folder is empty , that does not add up.
***unless you did an exit from the tool #7****
during exit by #7 the working folder is emptied.
So please start over and before exiting check the folder "working" for the new_frp_md5.txt file
#pwd
/
#exit
> > > > > > > > > > > > > > > > Waiting 5 seconds...
[*] COPYING UNLOCK.IMG OVER TOP OF COPIED FRP IN /data/local/test NOT AS ROOT WITH DIRTYCOW
[*]
cowing. Start: 0, size: 102400
cowing. Start: 102400, size: 102400
cowing. Start: 204800, size: 102400
cowing. Start: 307200, size: 102400
cowing. Start: 409600, size: 102400
cowing. Start: 512000, size: 102400
cowing. Start: 614400, size: 102400
cowing. Start: 716800, size: 102400
cowing. Start: 819200, size: 102400
cowing. Start: 921600, size: 102400
cowing. Start: 1024000, size: 24576
checking md5 of new frp before copying to mmcblk0p17
new FRP matches md5
[*] WAITING 5 SECONDS BEFORE WRITING FRP TO EMMC
[*] DD COPY THE NEW (UNLOCK.IMG) FROM /data/local/test/frp TO PARTITION mmcblk0p17
ciao
#dd if=/data/local/test/frp of=/dev/block/mmcblk0p17
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.109 secs (9619963 bytes/sec)
#exit
> > > > Waiting 5 seconds...
coping new frp is done phone will now reboot and script will return to start screen
press enter to exit
R1-HD-TOOL.sh: line 222: kill-server: command not found
It worked this time, I think.
Its rebooted into Fastboot mode. trying to look up the next step.
The Phone is in Fastboot Mode, but not doing much else. fastboot-android says there are no fastboot devices connected. Your script does not kill the adb server correctly. Do I need to kill it myself by doing control+Z and then adb kill-server?
$ fastboot-android devices
QCUCORS8PFMV85KN fastboot
zombie_ryushu said:
Its rebooted into Fastboot mode. trying to look up the next step.
The Phone is in Fastboot Mode, but not doing much else. fastboot-android says there are no fastboot devices connected. Your script does not kill the adb server correctly. Do I need to kill it myself by doing control+Z and then adb kill-server?
Click to expand...
Click to collapse
dont think that the kill-server was nescisary.
cant help with the fastboot-android part.
once you can use fastboot. next step is to check again that phone is unlockable
Code:
fastboot flashing get_unlock_ability
if result of that command is a number larger than 1 , continue with
Code:
fastboot oem unlock
then
Code:
fastboot reboot
this should make phone reboot and it will do factory reset. (needed when bootloader is unlocked)
mrmazak said:
dont think that the kill-server was nescisary.
cant help with the fastboot-android part.
once you can use fastboot. next step is to check again that phone is unlockable
Code:
fastboot flashing get_unlock_ability
if result of that command is a number larger than 1 , continue with
Code:
fastboot oem unlock
then
Code:
fastboot reboot
this should make phone reboot and it will do factory reset. (needed when bootloader is unlocked)
Click to expand...
Click to collapse
The fastboot-android nor your fastbootlinux binary included with your tool does not understand the
Code:
fastboot flashing get_unlock_ability
command.
(bootloader) Start unlock flow
OKAY [ 44.663s]
finished. total time: 44.663s
was the result of fastboot oem unlock
zombie_ryushu said:
The fastboot-android nor your fastbootlinux binary included with your tool does not understand the
Code:
fastboot flashing get_unlock_ability
command.
(bootloader) Start unlock flow
OKAY [ 44.663s]
finished. total time: 44.663s
was the result of fastboot oem unlock
Click to expand...
Click to collapse
ok so it looks like it worked.
you need to do the reboot and allow the reset before flashing anything.
Hello. At some point, the phone turned off and then when you press the power button, the phone booted up to the moment with the logo prowered by android -> Asus and turned off.
If you put your phone on charge: battery logo -> powered by android -> Asus.
When using keyboard shortcuts, fastboot works.
There were attempts to flash through the fastboot to the v16 firmware and the factory one, but everything is useless, everything is going well through cmd, until the partition table is updated.
I hope for help in resuscitation.
Code:
==========================================
ZE620KL raw flashing program
Version 20180129
==========================================
erase cmd: -f
need_wipe_data: 1
Please connect device to host.
This is ZE620KL device!
This is FUSED device!
This is SDM636 CPU!
Device support check CID !!
Device's CID is ASUS!
RAW file found: OPEN_ZE620KL_15.0501.1711.46_M1.2.2.P8_Factory_Phone-userdebug.raw
file size is: 2236165676 bytes(2183755 Kbytes)
This is ZE620KL RAW file for ZE620KL device.
Folder is not exsit
Get return message:
aft_support: yes
finished. total time: 0.001s
Support AFT security.
fastboot device serial: J8AXB765A124HL4
fastboot device serial len: 15
target reported max download size of 536870912 bytes
sending 'aft' (0 KB)...
OKAY [ 0.008s]
writing 'aft'...
OKAY [ 0.003s]
finished. total time: 0.013s
Start process RAW file: OPEN_ZE620KL_15.0501.1711.46_M1.2.2.P8_Factory_Phone-userdebug.raw
file size is: 2236165676 bytes(2183755 Kbytes)
This is ZE620KL RAW file for ZE620KL device.
=================================================================================
Process File for partition label: partition, size: 262144bytes
#=================================================================================
Process File for partition label: xbl, size: 2883584bytes
#=================================================================================
Process File for partition label: abl, size: 262144bytes
#=================================================================================
Process File for partition label: pmic, size: 262144bytes
#=================================================================================
Process File for partition label: rpm, size: 262144bytes
#=================================================================================
Process File for partition label: tz, size: 2097152bytes
#=================================================================================
Process File for partition label: hyp, size: 524288bytes
#=================================================================================
Process File for partition label: devcfg, size: 262144bytes
#=================================================================================
Process File for partition label: cmnlib, size: 262144bytes
#=================================================================================
Process File for partition label: cmnlib64, size: 524288bytes
#=================================================================================
Process File for partition label: keymaster, size: 524288bytes
#=================================================================================
Process File for partition label: xblbak, size: 2883584bytes
#=================================================================================
Process File for partition label: ablbak, size: 262144bytes
#=================================================================================
Process File for partition label: pmicbak, size: 262144bytes
#=================================================================================
Process File for partition label: rpmbak, size: 262144bytes
#=================================================================================
Process File for partition label: tzbak, size: 2097152bytes
#=================================================================================
Process File for partition label: hypbak, size: 524288bytes
#=================================================================================
Process File for partition label: devcfgbak, size: 262144bytes
#=================================================================================
Process File for partition label: cmnlibbak, size: 262144bytes
#=================================================================================
Process File for partition label: cmnlib64bak, size: 524288bytes
#=================================================================================
Process File for partition label: keymasterbak, size: 524288bytes
#=================================================================================
Process File for partition label: dsp, size: 16777216bytes
#=================================================================================
Process File for partition label: modem, size: 106430464bytes
#=================================================================================
Process File for partition label: logfs, size: 16384bytes
#=================================================================================
Process File for partition label: bluetooth, size: 536576bytes
#=================================================================================
Process File for partition label: boot, size: 18087936bytes
#=================================================================================
Process File for partition label: recovery, size: 21495808bytes
#=================================================================================
Process File for partition label: asusfw, size: 67108864bytes
#=================================================================================
Process File for partition label: system, size: 1281728448bytes
###=================================================================================
Process File for partition label: vendor, size: 707982956bytes
##
========================================
Flashing gpt_both0.bin for partition begin
========================================
target reported max download size of 536870912 bytes
sending 'CRC' (0 KB)...
OKAY [ 0.009s]
writing 'CRC'...
OKAY [ 0.008s]
finished. total time: 0.019s
target reported max download size of 536870912 bytes
sending 'partition' (256 KB)...
OKAY [ 0.014s]
writing 'partition'...
FAILED (remote: Error Updating partition Table
)
finished. total time: 0.033s
!!!ERROR to flash!!!
ERROR: Flashing files!
errorlevel="1"