OK so I put the BAMF Cubed Kernel on my phone and now I can't flash other kernels.
Many of us are having this problem, and I am having trouble installing new kernels when I try new ROMs.
Would someone please tell me step by step how to do this?
My understanding is that the boot.img file should be placed in the same folder on my PC as adb.exe, Fastboot, etc...
Is this correct? If so, what is the command line I should use to push the kernel to the phone?
Example: I want to try the new RezROM ICS from lllboredlll.
I downloaded the ROM, and have the zip on my phone's SD card. I also have it on my PC.
When I open it, I see a folder called Kernel. In that folder, there is a boot image. Also in that folder is a PH98IMG file containing a second boot image.
Which one is the correct kernel file to push via PC?
The way I understand it and have been doing it. Open up the zipped rom and you will see a boot image , extract or copy it to the folder that you have fastboot in . Then in Hboot..pull up a CMD box.. and either change location or if you have abd in your path.. the instructions are fastboot flash boot boot.img
then that should flash the kernel .. then boot to recovery ..wipe data/factory reset and then flash the rom .
BBEgo said:
OK so I put the BAMF Cubed Kernel on my phone and now I can't flash other kernels.
Many of us are having this problem, and I am having trouble installing new kernels when I try new ROMs.
Would someone please tell me step by step how to do this?
My understanding is that the boot.img file should be placed in the same folder on my PC as adb.exe, Fastboot, etc...
Is this correct? If so, what is the command line I should use to push the kernel to the phone?
Click to expand...
Click to collapse
Boot the phone into fastboot. Plug in the USB cable, open a CMD window on your computer. Set the current directory to the folder with adb.exe, fastboot.exe, and your new boot.img file.
enter the command:
fastboot flash boot boot.img
How come no one sets up their path to include the android-SDK folder with adv, fastboot...etc? I did and makes life so much easier since you never have to cd to anything to run those commands.
Sent from my ADR6425LVW using Tapatalk
I keep getting an error when trying to run fastboot. Any idea's?
c:Android>fastboot oem get_indentifier_token
'fastboot' is not recognized as an internal or external command, operable program or batch file.
Do you have adb and fastboot in the c:\android folder?
Yep they are both there. In my tools folder it says that he adb tool has moved to platform-tools/
If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"
Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.
Would this have any effect?
Yes. So you would have to point to the platform-tools folder or move adb into your android folder. Easier to just put it in your android folder so you don't have to navigate to it with the cmd prompt. Or do the PATH thing which I don't know how to do.
All you need in there is:
adb
AdbWinApi.dll
fastboot
Then after you get your Unlock_code.bin emailed to you copy that into there too.
I just keep all that as is and then anything I want to flash later I just copy in and then delete after I'm done flashing it. Except for the Amon Ra recovery, I've been keeping the current version of that in there too.
Can this be done? fastboot flash system system.ext4 or system.sin? i have tried with numerous and upto date fastboot executables but always receive fail with error FAILED (remote: Unknown chunk type). I have created sparse image chunks and even those won't flash with same error about chunk type. Am i doing something wrong or is fastboot no longer a good way to flash system images on newer S1 bootloaders? I understand that i can do this via custom recovery but for a project of mine i need fastboot to work. Any ideas gentlemen?
While In TWRP recovery you could try adb shell > su then dd the system.ext4.img.
I am not 100% but I don't think the system.ext4 that is produced by FlashTool from the .sin is a sparsed .img but is a normal .img. I think fastboot may need sparse.img's
Backup as always of course
Example:
Code:
adb shell
Code:
su
(su Probably not needed in TWRP)
Code:
dd if=/sdcard/system.ext4.img of=/dev/block/platform/mtk-msdc.0/by-name/system
EDIT: Sorry should of read your post better that will teach me for speed reading :laugh:
Still think it requires a proper sparse .img not sure what method you used.
PS: I assume you tried to rename it with the ext4 removed eg: just system.img
i am installing arter97 collection.
i use powershell-cmd but i cant flash kernel because can't find file.
But Filename is correct
What is the problem?
powershell pointed to same directory as file location?
i implement powershell in adb and fastboot folder
All file placed in adb and fastboot folder
strange - didnt have any issues flashing...
have you tried with cmd.exe? what error did you get? - no such file or directory?
Please Help!
I did something very stupid today.
Unlocked my RMX2170, got into fastboot.
Tried to flash PBRP as recovery, and some vbmeta.img image as vbmeta of my phone.
Disaster! My phone got stuck in a bootloop of just repeatedly booting into fastboot.
No recovery, nothing.
From there, I installed SHRP using the fasboot flash recovery command, and now I have SHRP.
SHRP, however, cannot flash ANYTHING as a result of an error that it "failed to mount /system_root and /vendor"
The phone can effectively boot into Qualcomm EDL and fastboot.
I've tried countless tools and software to get back to stock. Nothing works. MSM requires a login to function, so it won't work.
Anyone at all, please, can you tell me how to get back to FULL stock?
Through sheer trial and error,
Procedure:
1. Downloaded A37 ofp file from www.gsmmafia.com/realme-7-pro-rmx2170-flash-file/ (or mediafire download)
2. Extracted it using bkerler/oppo_decrypt's ofp_qc_extract.py into a folder:
Code:
py -3 -m pip install -r requirements.txt
py -3 ofp_qc_extract.py a37_ofp_file.ofp .\extracted
3. Rebooted the phone into fastboot, ready for flashing (Power + Volume Down for me)
5. Ran:
Code:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
(keep in mind these .img files came from the extracted ofp's folder!)
6. Rebooted into system using the fastboot menu (START)
7. I'm pretty sure my phone ran A41 before today... so I gave the phone an update from inside Android, that seemed to work fine.
As a bonus, my bootloader seems to have remained unlocked? Nice!
Also interesting: holding volume up does not boot into recovery. This is an issue for another day lads.
Can you explain me step 2? I have bootloped phone and I don't understand how to use oppo decrypt
Domac5 said:
Can you explain me step 2? I have bootloped phone and I don't understand how to use oppo decrypt
Click to expand...
Click to collapse
1. Download and install Python on your computer.
2. Press Windows + R, then type cmd, hit enter to access a terminal.
3. Make sure Python works by trying py -3 in the terminal. (Type exit() to exit the Python shell)
4. Download oppo_decrypt's repository zip and extract it in a folder anywhere.
5. Use cd in the terminal to navigate to the extracted folder.
6. Run this command to install the dependencies of oppo_decrypt:
Bash:
py -3 -m pip install -r requirements.txt
7. You should have already downloaded the ofp file for the phone. If not, get it from here.
8. You need to run the Python script in order to extract the images you need, so, you should copy it to the folder where your ofp file is.
Bash:
cp ofp_qc_decrypt.py /where/the/ofp/file/is/ofp_qc_decrypt.py
9. Go into the directory with the script and ofp file, and extract it.
Bash:
py -3 ofp_qc_extract.py the_ofp_file.ofp .\extracted
The extracted images you need, if you were on Android 10, should be in the extracted folder in the terminal's working directory.
Best of luck, although I can't really help you step-by-step for everything, so I suggest you visit r/realme's Discord.
Go to the Discord for more help!
Codian said:
1. Download and install Python on your computer.
2. Press Windows + R, then type cmd, hit enter to access a terminal.
3. Make sure Python works by trying py -3 in the terminal. (Type exit() to exit the Python shell)
4. Download oppo_decrypt's repository zip and extract it in a folder anywhere.
5. Use cd in the terminal to navigate to the extracted folder.
6. Run this command to install the dependencies of oppo_decrypt:
Bash:
py -3 -m pip install -r requirements.txt
7. You should have already downloaded the ofp file for the phone. If not, get it from here.
8. You need to run the Python script in order to extract the images you need, so, you should copy it to the folder where your ofp file is.
Bash:
cp ofp_qc_decrypt.py /where/the/ofp/file/is/ofp_qc_decrypt.py
9. Go into the directory with the script and ofp file, and extract it.
Bash:
py -3 ofp_qc_extract.py the_ofp_file.ofp .\extracted
The extracted images you need, if you were on Android 10, should be in the extracted folder in the terminal's working directory.
Best of luck, although I can't really help you step-by-step for everything, so I suggest you visit r/realme's Discord.
Go to the Discord for more help!
Click to expand...
Click to collapse
Step 8 not working for me
Do you have original recovery.img file,please send me? I just can't extract it from ofp file, 2 days trying and just can't
Domac5 said:
Step 8 not working for me
Click to expand...
Click to collapse
Sorry, instead of "cp" the command is "copy", my mistake.
Domac5 said:
Do you have original recovery.img file,please send me? I just can't extract it from ofp file, 2 days trying and just can't
Click to expand...
Click to collapse
You can't flash recovery.img. It won't work, I tried. You need to re-flash all of the system partitions like in my post.
I don't have the files anymore, as I did this a while ago. Sorry.
Codian said:
Sorry, instead of "cp" the command is "copy", my mistake.
Click to expand...
Click to collapse
Still doesnt work
I did it, problem was in python3 comand, that one should be typed without number 3 because that doesn't work in windows. Now it's extracting
did you had these problem?