I've seen alot of guys here who are encountering problems while flashing custom roms.Make sure you have backed up all your data before starting the procedure.
This method is also valid for those who are coming straight from the Stock rom.
Prerequisites :
•Unlocked Bootloader
•ADB and Fastboot Files
•Desired Custom Rom
•Copypartitions file
•TWRP image
•TWRP installer - Download and move it to Internal Storage
•A USB C-Type Cable and some Brain.
•Magisk [Optional]
•Fresh Gapps ARM64 (I'd recommend Mini)
Installation :
#1. Back up all your data or simply move everything to your PC.
#2.Boot your phone into Bootloader Mode [Power button + Volume Down] or Enable Debugging mode,And run this Command ''adb devices''- To ensure that the device is connected,then ''adb reboot bootloader''.
#3.Move the ''twrp.img'' file to the ''adb" folder of your PC.
#4.You'll see 3-4 files along with twrp.img file you just copied there[adb folder], Simply Click Shift+Right Click anywhere in that blank space,then click on Open Powershell Window here or Open Command Prompt Window.
#5.Attach your phone to the PC,you'll hear a sound,yet run this Command "fastboot devices" to ensure that the device is connected properly [Device ID will appear]
#6.Now you're supposed to temporarily boot TWRP in order to permanently flash the Custom Recovery.So to do this ,Run this Command while the device is connected to the PC in fastboot mode > "fastboot boot twrp.img '' [After Typing fastboot boot, simply drag twrp.img file into the PowerShell or Command prompt window to Complete the Command ''fastboot boot twrp.img'',it may look like ''fastboot boot C://adb/twrp.img''.
#7.After Booting Temporarily into TWRP,Swipe for Modifications,Locate and install TWRPinstaller.zip,this will permanently install TWRP as your Recovery.
#8.After installing TWRP,Return to the home screen of TWRP and Reboot into Recovery from there.[Permanently Flashing incase you don't need hassles with computer flashing]
#9.After booting again into TWRP,Click on Wipe>Format User Data>Type Yes>Go to Home screen Reboot into Recovery.
#10.After booting again into TWRP,Click on Wipe>Advanced Wipe> [Tick on Dalvik/Art Cache,Cache, System,Data] > Wipe it off.
#11.Go back to the Home Screen of the TWRP,Reboot into Recovery.
#12.Now Push copypartitions.zip file to your phone from your PC,then flash it via TWRP,then again,Reboot your phone to Recovery.
#13.Now Push the Desired Custom rom you would want to install on your G7 river from the PC> Install it> After the Installation Finishes,Reboot your phone to the Bootloader mode from TWRP [As the the Recovery will be replaced by the Custom Rom's Recovery,hence, TWRP will be removed].
#14.Once in the Fastboot Mode,run the command in PowerShell or CMD, "fastboot boot twrp.img"
#15.After booting again into TWRP,Push Gapps File into your phone and install it Accordingly,After the installation Finishes,Wipe Dalvik Cache,Come back to the Home screen of TWRP,Reboot > Power Off in TWRP,then manually Power it On,After powering it On,the rom may prompt you for a factory reset,that's it. You've successfully installed Custom Rom along with the Google Apps without Messing with the partitions.
#16.Now, Finally Boot your phone into Bootloader mode, run the command "fastboot boot twrp.img" and install TWRPinstaller.zip,this will again permanently install TWRP as your recovery.
#17.You may root your phone by installing Magisk or Flash any other zip without the need of temporarily booting TWRP,as you've flashed it permanently. Simply Reboot to Bootloader then Boot into Recovery.
Errors and Fixes:
#1.If you encounter any problem while flashing zips from the internal storage, simply move all the zips to the MicroSD or USB OTG and flash it from there.
#2.If your TWRP isn't reading the internal storage properly or isn't responding well,simply reboot your phone again to the Bootloader mode,again boot twrp.img and try again,this should do the thing.
#1.copy-partitions-AB.zip
#2.twrp-3.3.1-0-river.img
#3.twrp-installer-3.3.1-2-river.zip
Find these files on the internet or XDA forums as I can't Post links yet,Happy to help!
Simplify and Clarify
Thanks @deathcruizer for the your procedure. It rescued me in a jam. The critical items for me that you noted were that the Custom ROM replaced TWRP with its own Recovery and that a Factory Reset was required.
I wanted to simplify and clarify your key points for those already setup with fastboot and familiar with TWRP. Generic filenames mentioned should be replaced by the actual full name; eg, twrp-3.3.1-2-river.img.
1. Backup partitions in TWRP just in case for a restore. And Data will be needed later.
2. Move all zip files needed (ROM, Gapps, copy-partitions, twrp-installer, Magisk, etc.) to internal storage or USB OTG. Move twrp.img on PC to a convenient location for fastboot.
3. Enter fastboot boot twrp.img to temporarily use TWRP.
4. Flash copy-partitions.zip, reboot, and flash custom ROM.zip.
5. In TWRP, choose Reboot to the Bootloader mode, not Recovery. TWRP has been removed and replaced by the custom ROM's Recovery.
6. Enter fastboot boot twrp.img to temporarily use TWRP again. Install Gapps.zip, wipe caches, and then Power Off.
7. Manually Power On to the Custom ROM. Accept its Factory Data Reset option.
8. Boot into Bootloader Mode, enter fastboot boot twrp.img again, and use this temporary TWRP to install TWRP permanently using twrp-installer.zip.
9. Reboot and begin a minimum setup of the Custom ROM.
10. Reboot to TWRP and restore the Data partition.
11. G7 River is back with its apps, desktop layout, settings, icons, etc., on the new Custom ROM.
Hey guys, your tutorial is great and very informative. I do however have a recurring problem with installing any custom rom. No matter which one I choose, I have no LTE and occasionally the phone randomly reboot if I unplug my phone. Has anyone encountered this? I've followed all applicable steps for properly installing a custom rom, and am pretty use to it as I've always flashed roms on as many phones as I could. Any help or guidance would be appreciated. Thanks in advance
What model phone, to be clear?
Moto g7, xt19621. I tried to flash lineage again today to no avail. Twrp then copy. Zip. Reboot. Lineage. Wipe dalvic. Reboot. Previously tried wiping system and starting from scratch. Copy. Zip and start from scratch. Clean flash. Dirty flash. I've been able to get it to work properly maybe 2 or three times since having the phone and trying different roms. Basically always having to revert back to stock after a multitude of attempts. I've never had this much trouble flashing with a phone.
---------- Post added at 12:45 AM ---------- Previous post was at 12:27 AM ----------
Do I need to flash stock to the 9eiginal firmware or something? I tried the stock room from August 2019, and kind 9f same issues. Device kinda bugged out.
If you're going to do a full article, always be sure to check and double check your process before sharing. The A/B slots on this device CAN cause mucho mucho errors if the user is unfamiliar or does not alternate correctly (TWRP can select boot slot, yes, but doesnt always work the right way), they can end up with a bricked device. I am excited to see a full guide be posted but for other people's sake, I recommend maybe clarifying the A/B details. I, personally, have yet to find a good A/B tutorial, and how they work during installs, online but if there is one and someone wants to share the link I'd sure appreciate it! Thanks and goodluck!
---------- Post added at 02:02 AM ---------- Previous post was at 01:49 AM ----------
trentag1988 said:
Moto g7, xt19621. I tried to flash lineage again today to no avail. Twrp then copy. Zip. Reboot. Lineage. Wipe dalvic. Reboot. Previously tried wiping system and starting from scratch. Copy. Zip and start from scratch. Clean flash. Dirty flash. I've been able to get it to work properly maybe 2 or three times since having the phone and trying different roms. Basically always having to revert back to stock after a multitude of attempts. I've never had this much trouble flashing with a phone.
---------- Post added at 12:45 AM ---------- Previous post was at 12:27 AM ----------
Do I need to flash stock to the 9eiginal firmware or something? I tried the stock room from August 2019, and kind 9f same issues. Device kinda bugged out.
Click to expand...
Click to collapse
back up phone if you have third party backup application
(not absolutely necessary BUT, I always remove my security and google account before going into fastboot)
reboot to fastboot or power off phone and boot to fastboot by holding down the volume down+power
"fastboot set_active b"
"fastboot boot (drag your twrp img file from it's location to the command window) so that it reads sort of like "fastboot boot c:\path-to-twrp.img"
1. now install copy-partitions.zip
2. "Format, Advanced", type "yes" then back to TWRP main screen
3. install ROM of your choice (if installing Lineage, skip step 4)
4. install twrp-installer.zip (make sure you're using the zip format, not img)
5. "adb reboot bootloader"
"fastboot set_active a" (because when you installed the ROM, the device installed it to the inactive slot, in this instance that slot would be "a"
ADV: you may get a message indicating you're already on slot a, which is fine. 9 out of 10 times the device changes slot automatically after you reboot
post-ROM-install
6. from TWRP home choose "Advanced, ADB Sideload", check the two boxes and"adb sideload c:\path-to-gapps" (you'll need ARM64 gapps for this device)
7. IF you want magisk, from TWRP home choose "Advanced, ADB Sideload", check the two boxes and "adb sideload c:\path-to-magisk.zip"
8. "adb reboot bootloader"
9. "fastboot -w"
10. For whatever reason, magisk never stays on my device but I just install the apk and install it from the app.
Hope this doesn't annoy anyone and proves helpful.
@clinton I am definitely going to try this particular method. Setting B as active first is the one thing I have not done. I would like to point out that I am about to do fastboot boot twrp.img , however when installing the provided zip, my phone makes a weird noise on every screen tap. Like odd feedback from the speaker. If I use just lineage recovery that installs from the rom, it doesn't do that. Another thing that happens now - every lineage install goes fine until first boot. As soon as I sign on to WiFi and it tries to activate the radio, device just shuts down. Has anyone had this happen to them?
I am still experiencing the same issues. flashed back to original firmware and had no LTE. didn't resolve when flashing a custom rom. Flashed to latest stock rom and everything went through properly (LTE, no random reboot after unplugging), attempted rigmarole for flashing custom rom, same issues. x over signal bar and reboot as soon as I unplug the device. I have basically given up at this point, going to have a go at it again when stock android 10 update happens Thank you, guys, for all the help and tutorials. Big hugs, take care
Related
Hello,
I saw that the OTA update to Lollipop was available on my phone today, so I went ahead and let it download. Upon completion of the download, it restarted and applied patches, then restarted again and has been stuck in boot loop for about an hour. After reading several other threads on how to try to reset the phone, I'm stuck. When I try power + volume up or down, the LED status indicator flashes red and I never get to any kind of other screen. Am I completely screwed? I previously had stock 4.4.2 with no modifications.
Finally was able to get to the bootloader menu. Apparently having the phone plugged into the charger was preventing me from getting there for some reason. I ended up having to wipe the phone to get it to boot
so you can get into clock recovery right? download nexus 4 toolkit..that might save your phone. I suggest you to unroot and flash everything to stock and then unlock again and start everything from scratch. good luck.
Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?
Sportfreunde said:
Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?
Click to expand...
Click to collapse
I guess TWRP Recovery has option to enable MTP and you can access the internal SD card by connecting mobile with computer using usb cable.
---------- Post added at 06:37 PM ---------- Previous post was at 05:37 PM ----------
Sportfreunde said:
Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?
Click to expand...
Click to collapse
Flash TWRP Recovery using fastboot.
1. If you have otg y cable, connect it and use file manager to copy all the files.
2. OTG method is failed then select “Mount”, then select only “Data” and connect your Nexus 4 to your computer and Enable MTP in TWRP. now you can use adb pull and push commands.
I ended up going the factory reset route, which wasn't really a bad thing. My photos had been backed up in dropbox and the play store remembered all the apps and were able to reload them. The only things I really had to do was reload some music onto the phone and re-enter passwords for apps.
Same story here: sideloaded the OTA zip file, then had bootloop. Tried a few approaches, but none worked. In the end only wiping the data was the solution for me. Lost some userdata in a few important Apps...
I went through this yesterday. The only way to get it to boot is a Factory Reset from Recovery. It works like magic, but sucks you lose the data.
Got the OTA yesterday and also got a bootloop(stuck in boot screen animation). I couldnt afford losing my photos/videos as i had no backup , so i figured out a super easy to get it to boot without wiping data .
I was unrooted with stock recovery running stock 4.4.2, bootloader was unlocked. I flashed CWM recovery through fastboot and wiped chache+ Dalvik from there then simply rebooted the phone .
I had already tried wiping cache from the stock Android recovery,needless to say that didnt work for me.
If anyone else is having the same problem please try the method above and report back, cheers!
I post this on Google Product Forum 2 days ago. Hope it helps
https://productforums.google.com/for...Q/wDzRUm4b2UsJ
(updated 29/11/2014)[not perfect but it is a SOLUTION]
The idea of this is to downgrade your nexus 4 without wiping your data, which means stuff you will need includes:
1. adb and fastboot on your computer (I am using mac but you can find it on windows as well. There are tones of website and forums telling you the latest method of getting it onto your computer)
2. factory image of nexus 4(I use 4.4.4, since that's what it was. I don't have the time and energy to try to do the same thing with lollipop. you can try can leave a comment).
update: do NOT try to flash 5.0 rom using this method. You will be stuck at boot loop again
3. usb cable
4. nexus 4 with unlocked bootloader(the process of unlocking bootloader will wipe your device)
5. computer
steps
1. unzip the factory image (something.tgz)
2. for me, after unzipping the .tgz, I still find another .zip inside. unzip that too.
3. hold vol+, vol-, and power button simultaneously to enter fastboot mode
4. open terminal(mac)(it would probably be cmd for windows)
5. connect your nexus 4(in fastboot)
6. to make sure it connect successfully, type "fastboot devices". if something like "005040c0d54bb291 fastboot" appears, you are good. Otherwise, try reconnect your device/boot to fastboot again/use another usb cable
7.now we need to tell the terminal to navigate to the location of the unzipped factory image. to do that, i suggest you put the unzipped folder to somewhere easy to find, like desktop. these are some commands to help you navigate:
"ls" allows you to look at whats inside the current directory of the terminal. For example, this is the output after typing "ls" for me:
some folder Photos
nexus4image.tgz how many folders do you have
5.zip occam-ktu84p
more folder occam-ktu84p.zip
after knowing where you are, use "cd" (below) to go to your folder
"cd" means change directory. For example. "cd Photos" will brings me to the "Photos" folder. And then if I type ls, I will see a whole bunch of photos in my photos. If you go to the wrong folder, type "cd ..", and it will bring you back to the previous folder.
8. flash bootloader.
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash bootloader bootloader-mako-makoz30d.img
9. reboot bootloader. just copy and paste
fastboot reboot-bootloader
10. flash radio
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
11. reboot bootloader. just copy and paste
fastboot reboot-bootloader
12. flash system
system.img is located inside the zip, use ls to help you navigate. This steps takes the longest time, total time on this step is 87 seconds while the others are less then 1 second
fastboot flash system system.img
13. flash boot
boot.img is located inside the zip, use ls to help you navigate.
fastboot flash boot boot.img
14. flash recovery
fastboot.img is located inside the zip, use ls to help you navigate.
fastboot flash recovery recovery.img
15. format cache(not the memory, so everything should be fine)
fastboot format cache
16. reboot and wait
this will reboot your device. You probably have to wait for a while to initialise all the apps. after than you are good to go!
fastboot reboot
credit: my friend for giving me this idea + http://forum.xda-developers.com/nexu...image-t2010312 + HelpMyNexus
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections, ligma,
* thermonuclear war, or your mom getting upset with you for being on the computer all day
Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/
THIS GUIDE APPLIES TO JETER AND ALJETER DEVICES
FOR ALJETER DEVICE OWNERS ONLY.
there are ALOT of different variants of the aljeter so please before beginning this root method go to settings, system, about phone. look for either sw version or software channel verison and either remember what it says or write it down. me or anyone else will need this to help troubleshoot which aljeter variant you have. this will also be important to know incase you mess up and need to reflash stock firmware which those instructions are at the bottom of this guide.
The following devices have been confirmed to work on devices with Android 8 (Oreo)
XT1922-4 Model
XT1922-5 Brazilian Model
XT1922-7 Boost Mobile/ Virgin Mobile
XT1922-9 Motorola Retail
The following devices have been confirmed to work with Android 9 (pie)
XT1922-7 (Jeter) boost Mobile/ Virgin Mobile.
XT1922-3 (Aljeter)
XT1922-5 (Aljeter retbr)
Please make backups using TWRP IN CASE OF FAILURE.
Original stock firmware FOR JETER can be found here. https://mirrors.lolinet.com/firmware/moto/jeter/official/ and here FOR ALJETER https://mirrors.lolinet.com/firmware/moto/aljeter/official/
The steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first.
Prerequisite:
Unlocked bootloader.
FOR LINUX USERS. If you're using a linux distro then congrats this is all you should have to run. open command prompt and run this. "sudo apt-get install adb" without quotation marks. then follow Motorolas bootloader guide in provided link. continue to step 1 after.
FOR WINDOWS USERS.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio...platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.
Minimal adb/fastboot v1.4.3 installer can be found here. https://androidfilehost.com/?fid=746010030569952951
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
DECRYPTION AND BACKUP.
NOTICE
IF YOU YOU ARE USING THE 32GB MODEL OR THE 16GB MODEL AND ARE ON ANDROID 9 (PIE) PLEASE USE THE ANDROID 9 (PIE) MODEL TWRP. USERS WITH THE 16GB MODEL AND THE 32GB MODEL ON ANDROID 8 (OREO) WILL STILL NEED TO USE SEPERATE TWRPS
MAKE SURE TO SWIPE RIGHT IN TWRP TO ALLOW SYSTEM MODIFICATIONS.
Step 1.) Download and extract twrp image to the ADB/Fastboot folder on your computer.
FOR ANDROID 8 (OREO)
16gb model twrp: https://www.androidfilehost.com/?fid=6006931924117921836
32gb model twrp: https://www.androidfilehost.com/?fid=6006931924117927211
FOR ANDROID 9 (PIE)
https://www.androidfilehost.com/?fid=6006931924117921849
Step 2.) Reboot to your bootloader. You can do this by turning on your device and holding the power button and volume down button at the same time.
Step 3.) Once the device reboots to the bootloader type the following from your computer with your phone connected via USB.
Code:
fastboot boot twrp.img
Step 4.) Once TWRP boots from your computer type (it may take a bit to boot because it is trying to decrypt your userdata, but it will fail and prompt for a password. Just click cancel)
Step 5.) time to backup your stock recovery and stock boot. use these commands one at a time.
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
This will backup your stock boot and recovery images if you need to revert to stock later.
Step 6.) time to decrypt which will also format your data so make sure to make a backup. while still booted in twrp touch the "wipe" button then touch "format data", type yes and after its all done reboot to bootloader use this command.
Code:
adb reboot bootloader
CONGRATS! if you read this correctly and or didnt skim then you have successfully decrypted your device and backed up your stock recovery and stock boot.img. proceed below for root process.
ROOT PROCESS.
Step 1.) Run the following command from your computer to install the TWRP image to your device.
Code:
fastboot flash recovery twrp.img
Step 2.) Use the volume keys on the device to select boot to recovery and TWRP will boot up again. swipe right to allow modifications. IT SHOULD NOT ASK YOU FOR A PASSWORD THIS TIME IF IT DOES YOU MESSED UP DURING THE DECRYPT PROCESS
Step 3.) Follow this link to the creators site to download the disabler zip. https://zackptg5.com/android.php#disverfe download it to your ADB/Fastboot folder.
Step 4.) Download the Magisk Beta v20.0 and or the latest zip file from https://github.com/topjohnwu/Magisk/releases to your ADB/Fastboot folder. (I personally use beta so I use beta in this guide but you don't have to)
Step 5.) Run the following command to push the dm_verity force encrypt disabler and magisk zip to your device
Code:
adb push Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip /tmp
adb push Magisk-v20.0.zip /tmp
This will push the Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip and Magisk-v20.0.zip to your /tmp folder
Step 6.) Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 7.) Flash Magisk-v20.0.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 8.) Reboot your device
Step 9.) Just wait for the device to boot up. might take a bit and it might seem its in a bootloop but if you followed this guide exactly as is just wait it out it took about 5-10 minutes before i got to the "lets get started" screen after updating to pie (android 9)
Step 10.) Verify Magisk Manager is installed and the root functionality works. sometimes the manager apk wont be installed so download the magisk manager apk from the provide links. click advanced to see if the boxes are unchecked. (2022 edit) If you see magisk app and magisk needs updated you can do it but I can't confirm if it's safe and what works and doesnt after
CONGRATS! IF YOU DIDNT SKIM MY GUIDE YOU SHOULD HAVE A SUCCESSFULLY ROOTED AND ENCRYPTION DISABLED DEVICE, HAVE FUN.
IF YOU MESSED UP, DIDNT PUT A COMMAND IN CORRECTLY, SKIMMED, OR ARE INA GENUINE BOOTLOOP/BRICK THIS SECTION IS FOR YOU
Step 1.) DOWNLOAD STOCK FIRMWARE HERE FOR JETER AND CERTAIN ALJETER DEVICES (from what i can tell usa variant aljeter devices are consided jeter) https://mirrors.lolinet.com/firmware/moto/jeter/official/ IF YOU REMEMBER OR WROTE DOWN YOUR SW CHANNEL VERSION THEN DOWNLOAD STOCK FIRMWARE FOR BASICALLY EVERY OTHER ALJETER DEVICE HERE. https://mirrors.lolinet.com/firmware/moto/aljeter/official/ UNZIP STOCK FIRMWARE TO YOUR ADB/FASTBOOT FOLDER TO FLASH IT. TO REVERT BACK TO STOCK YOU HAVE TO REFLASH STOCK FIRMWARE FROM THE BOOTLOADER if your device is bootlooped or bricked or not working right you have to reflash the stock firmware your device came with. PLEASE INPUT THESE COMMANDS ONE AT A TIME DO NOT DO THEM ALL AT ONCE. I KNOW ITS A HASSLE BUT IT GUARANTEES A SUCCESSFUL REFLASH. I CANNOT EMPHASIZE THIS ENOUGH
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastbot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
Credits: @kwiksi1ver for making the original guide. @topjohnwu for magisk. @shimp208 for minimal adb/fastboot. @Spaceminer for providing the new twrps for 16gb and 32 gb devices, and @Zackptg5 for making the Universal DM-Verity, ForceEncrypt, Disk Quota Disablers.
QUICK NOTE/EDIT: SINCE I DO NOT OWN THIS DEVICE ANYMORE I CANNOT CONFIRM IT BUT YOU SHOULD BE ABLE TO UPDATE TO THE LATEST MAGISK 24.3 FROM THE MAGISK APP AFTER YOU INSTALL V20, AGAIN I AM NOT ABLE CONFIRM IF IT WORKS, CAUSES BOOTLOOPS, OR ANYTHING SO KEEP THAT IN MIND, but hopefully it does work for yall I've also updated the ADB commands for the disabler to reflect its latest version and I've updated the magisk link to topjohnwus GitHub as that's where all updates happen/ go first
RESERVED
In order to update the confirmed working models for this guide, if anyone that has this device with a unlocked bootloader and does root and decrypt successfully using my guide and it's not on the confirmed device list. PLEASE JUST PM ME and let me know. Please include device model number, name, and if on aljeter your software channel version.( For example. Xt1922-5 aljeter, sw channel: retbr)
following the instructions exactly gets me into a really weird bootloop where my phone boots twrp, shows some log and then reboots and does the same thing over and over
blowingoff said:
following the instructions exactly gets me into a really weird bootloop where my phone boots twrp, shows some log and then reboots and does the same thing over and over
Click to expand...
Click to collapse
I have the same issue. I used the recovery steps to go back to stock but every time i re-attempt to root/install twrp the bootloop comes back:
Also, it's failing to mount /data after Resurrection Remix wouldn't boot and it keeps giving me the unable to mount /data (invalid argument) problem. I need help badly. Can you help? Is it the TWRP's fault?
Kuntitled said:
I have the same issue. I used the recovery steps to go back to stock but every time i re-attempt to root/install twrp the bootloop comes back:
Also, it's failing to mount /data after Resurrection Remix wouldn't boot and it keeps giving me the unable to mount /data (invalid argument) problem. I need help badly. Can you help? Is it the TWRP's fault?
Click to expand...
Click to collapse
Are you encrypted? Because twrp will do that if you are. You have to use the wipe > format > type "yes" to continue method to remove encryption. Then reboot from twrp, directly back into twrp. Then it can mount /data properly, at which point you need to flash the encryption disabler. If you don't disable encryption you'll keep running into the same problem. You only have to do that once. After that you can use the regular wipe option. If you ever flash the stock vendor.img you'll need to do it again.
Also, please make sure twrp has been flashed to recovery. I don't think it'll work if you just boot through fastboot. If you followed all these instructions and magisk still refuses to install, or gives you a bootloop, then it's a ROM problem and not TWRP. Should that happen, let me know and I'll flash Resurrection remix and see if I can figure out what's going on. I've had ROMs refuse to be rooted before. Descendant ROM had this problem on some older builds.
Spaceminer said:
Are you encrypted? Because twrp will do that if you are. You have to use the wipe > format > type "yes" to continue method to remove encryption. Then reboot from twrp, directly back into twrp. Then it can mount /data properly, at which point you need to flash the encryption disabler. If you don't disable encryption you'll keep running into the same problem. You only have to do that once. After that you can use the regular wipe option. If you ever flash the stock vendor.img you'll need to do it again.
Also, please make sure twrp has been flashed to recovery. I don't think it'll work if you just boot through fastboot. If you followed all these instructions and magisk still refuses to install, or gives you a bootloop, then it's a ROM problem and not TWRP. Should that happen, let me know and I'll flash Resurrection remix and see if I can figure out what's going on. I've had ROMs refuse to be rooted before. Descendant ROM had this problem on some older builds.
Click to expand...
Click to collapse
as for me: I followed the instructions which tell us to only boot twrp during the data format and only then actually flash twrp.
but my problem is no magisk, as I always root my phone whenever i revert back to stock. it's just that decryption is not working on my xt1922-5
blowingoff said:
as for me: I followed the instructions which tell us to only boot twrp during the data format and only then actually flash twrp.
but my problem is no magisk, as I always root my phone whenever i revert back to stock. it's just that decryption is not working on my xt1922-5
Click to expand...
Click to collapse
Do it like this.
1. fastboot flash recovery twrp.img
2. Use the volume keys while still in fastboot to select "recovery" then hit the power button.
3. Hit cancel at the decryption screen when twrp boots up.
4. In TWRP select wipe > format > type "yes" to continue. Do not reboot the phone yet.
5. In twrp select reboot > recovery.
6. Once twrp boots up again, select mount and check the boxes for /data, /system, /vendor, /cache.
7. Now flash the universal encryption disabler.
8. Let it boot once, then go back into recovery and flash Magisk.
This should solve your problem.
Spaceminer said:
Do it like this.
1. fastboot flash recovery twrp.img
2. Use the volume keys while still in fastboot to select "recovery" then hit the power button.
3. Hit cancel at the decryption screen when twrp boots up.
4. In TWRP select wipe > format > type "yes"no to continue. Do not reboot the phone yet.
5. In twrp select reboot > recovery.
6. Once twrp boots up again, select mount and check the boxes for /data, /system, /vendor, /cache.
7. Now flash the universal encryption disabler.
8. Let it boot once, then go back into recovery and flash Magisk.
This should solve your problem.
Click to expand...
Click to collapse
My issue is as follows:
I had rooted my g6play months ago, back when pie came out on Ota for it. The guide I followed didn't have me disable encryption, which at the time wasn't a real big deal, with my only loss being the inability to do nandroid backups. But fast forward to now, when Resurrection Remix GSI came out, I was immediately interested as I think that rom could be a great experience.
So I decided to come here in this guide because I might as well disable encryption, right? So I flashed the new twrp and did get it to wipe and disable the encryption (in the option that has you type in yes) and proceeded to flash RR, it booted to the boot anima9and there it stayed for a good 30 minutes before I decided to try the older GSI image, maybe that one would work.
But nope, I immediately got the unable to mount /data bootloop and successfully flashed my stock rom and tried again, this time flashing the new twrp right off the bat. No avail. Now everytime i go into a freshly flashed twrp, i get no password prompt, and when i try to access the internal storage, it comes up as 0mb. Even my Linux complains that it couldn't mount my Internal storage as only the SD card shows up (weirdly enough I was able to successfully push dm verity and magisk to /temp no problem but they fail upon flashing)
Edit: gotta mention that after the first time I did the pull adb command to get the backups, the command refuses to work anymore. And also that I still have an old twrp backup stored (did that today before trying this)
Kuntitled said:
My issue is as follows:
I had rooted my g6play months ago, back when pie came out on Ota for it. The guide I followed didn't have me disable encryption, which at the time wasn't a real big deal, with my only loss being the inability to do nandroid backups. But fast forward to now, when Resurrection Remix GSI came out, I was immediately interested as I think that rom could be a great experience.
So I decided to come here in this guide because I might as well disable encryption, right? So I flashed the new twrp and did get it to wipe and disable the encryption (in the option that has you type in yes) and proceeded to flash RR, it booted to the boot anima9and there it stayed for a good 30 minutes before I decided to try the older GSI image, maybe that one would work.
But nope, I immediately got the unable to mount /data bootloop and successfully flashed my stock rom and tried again, this time flashing the new twrp right off the bat. No avail. Now everytime i go into a freshly flashed twrp, i get no password prompt, and when i try to access the internal storage, it comes up as 0mb. Even my Linux complains that it couldn't mount my Internal storage as only the SD card shows up (weirdly enough I was able to successfully push dm verity and magisk to /temp no problem but they fail upon flashing)
Edit: gotta mention that after the first time I did the pull adb command to get the backups, the command refuses to work anymore. And also that I still have an old twrp backup stored (did that today before trying this)
Click to expand...
Click to collapse
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
---------- Post added at 11:58 AM ---------- Previous post was at 11:42 AM ----------
blowingoff said:
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
Click to expand...
Click to collapse
Edit: i can not mount data, twrp says argument invalid. followed your instructions anyway and my phone still gets me to a bootloop to a "running OpenRecoveryScript" again.
blowingoff said:
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
---------- Post added at 11:58 AM ---------- Previous post was at 11:42 AM ----------
Edit: i can not mount data, twrp says argument invalid. followed your instructions anyway and my phone still gets me to a bootloop to a "running OpenRecoveryScript" again.
Click to expand...
Click to collapse
Go into the wipe menu, advanced wipe, check data and hit change file system. change data back to f2fs. When you guys format and don't immediately reboot straight to recovery, data sets to Auto and freaks out
Starkiller2 said:
Go into the wipe menu, advanced wipe, check data and hit change file system. change data back to f2fs. When you guys format and don't immediately reboot straight to recovery, data sets to Auto and freaks out
Click to expand...
Click to collapse
the multiple times i checked, the file system was always f2fs, but sometimes ext4
and also: Do you mean we should do that after we try to format with the format data (typing yes) option? If so, it doesn't work as the internal storage won't mount. Won't even show up on my computer
Kuntitled said:
the multiple times i checked, the file system was always f2fs, but sometimes ext4
and also: Do you mean we should do that after we try to format with the format data (typing yes) option? If so, it doesn't work as the internal storage won't mount. Won't even show up on my computer
Click to expand...
Click to collapse
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Starkiller2 said:
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Click to expand...
Click to collapse
Alright, let me work through this.
I'm currently on a stock firmware and it's working fine.
Right now i have to:
1. boot into recovery twrp
2. change the filesystem of data
3. flash recovery and boot into it
4. format data(yes option)
5.check and change the file system again
6.reboot straight back into twrp recovery from recovery
7.flash dm verity zip
8.flash magisk
9.boot
Is this correct? and as for attempting to install a GSI image again, should i attempt to flash it before the verity zip and magisk? (i'll also be flashing micro gapps) or do i let it boot into system once and then i do it? (by wiping data/dalvik/cache/system)
Kuntitled said:
Alright, let me work through this.
I'm currently on a stock firmware and it's working fine.
Right now i have to:
1. boot into recovery twrp
2. change the filesystem of data
3. flash recovery and boot into it
4. format data(yes option)
5.check and change the file system again
6.reboot straight back into twrp recovery from recovery
7.flash dm verity zip
8.flash magisk
9.boot
Is this correct? and as for attempting to install a GSI image again, should i attempt to flash it before the verity zip and magisk? (i'll also be flashing micro gapps) or do i let it boot into system once and then i do it? (by wiping data/dalvik/cache/system)
Click to expand...
Click to collapse
Let's simplify. If everything is working,
go to fastboot
Flash recovery (boot doesn't seem to be working here)
Fastboot flash recovery twrp image
Select recovery, when the decrypt menu comes up, hit cancel
Wipe menu,
Swipe to factory reset
Go back to wipe
format data, yes,
Reboot recovery
Flash disabler
Flash magisk
And yes. Boot system then GSI flash, then factory reset before magisk
---------- Post added at 01:44 PM ---------- Previous post was at 01:36 PM ----------
We'll get it figured out
Starkiller2 said:
Let's simplify. If everything is working,
go to fastboot
Flash recovery (boot doesn't seem to be working here)
Fastboot flash recovery twrp image
Select recovery, when the decrypt menu comes up, hit cancel
Wipe menu,
Swipe to factory reset
Go back to wipe
format data, yes,
Reboot recovery
Flash disabler
Flash magisk
And yes. Boot system then GSI flash, then factory reset before magisk
---------- Post added at 01:44 PM ---------- Previous post was at 01:36 PM ----------
We'll get it figured out
Click to expand...
Click to collapse
Do i check the file system for data at any point?
Kuntitled said:
Do i check the file system for data at any point?
Click to expand...
Click to collapse
Only if it won't mount
Starkiller2 said:
Only if it won't mount
Click to expand...
Click to collapse
does it matter where i flash disabler, magisk and GSI from? I've been doing it from my SD card
Kuntitled said:
does it matter where i flash disabler, magisk and GSI from? I've been doing it from my SD card
Click to expand...
Click to collapse
No that's fine
Starkiller2 said:
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Click to expand...
Click to collapse
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues and it mounts sucessfully with ext4 but won't let me format data
I get the mkfs.f2fs -t 0 /dev/block/mmcblk0p56 error 1, unable to mount data whenever i try to change to f2fs. Has my previous failed attempt at installing GSI **** with my filesys?
Kuntitled said:
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues
Click to expand...
Click to collapse
But data won't work as ext4, hence the boot loop
Try going to fastboot and typing
Fastboot -w
Then boot to recovery
---------- Post added at 02:10 PM ---------- Previous post was at 02:07 PM ----------
Kuntitled said:
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues and it mounts sucessfully with ext4 but won't let me format data
I get the mkfs.f2fs -t 0 /dev/block/mmcblk0p56 error 1, unable to mount data whenever i try to change to f2fs. Has my previous failed attempt at installing GSI **** with my filesys?
Click to expand...
Click to collapse
I honestly don't see how, especially if stock is working
Help me guys. I deleted my Oneplus 6T SystemUI.apk. Bootloop. Please teach me how to fix it.
Maybe this thread could be useful
https://forum.xda-developers.com/showthread.php?t=1637847
Is your bootloader unlocked? If so, you can just boot TWRP via fastboot (boot the img, not installing the zip) and dirty flash the latest OTA.
If nothing works, boot into EDL mode and use msmdownloadtool as last resort, but you will lose ALL your data in the process. Don't mess with the cable when msmdownloadtool is working or your phone is going to be permanently bricked. You should only use msmdownloadtool if you've tried everything and nothing is working, or you entered Qualcomm crash dump mode and fastboot/recovery isn't working.
I don't understand
komodo_1 said:
Maybe this thread could be useful
https://forum.xda-developers.com/showthread.php?t=1637847
Click to expand...
Click to collapse
I don't understand this
Then
adb shell
su
rm system/app/SystemUI.apk
exit
basedtobeh said:
Is your bootloader unlocked? If so, you can just boot TWRP via fastboot (boot the img, not installing the zip) and dirty flash the latest OTA.
If nothing works, boot into EDL mode and use msmdownloadtool as last resort, but you will lose ALL your data in the process. Don't mess with the cable when msmdownloadtool is working or your phone is going to be permanently bricked. You should only use msmdownloadtool if you've tried everything and nothing is working, or you entered Qualcomm crash dump mode and fastboot/recovery isn't working.
Click to expand...
Click to collapse
My 6t bootloader unlocked and i don't have boot img
undrahbayar said:
My 6t bootloader unlocked and i don't have boot img
Click to expand...
Click to collapse
Since you uninstalled SystemUI.apk, I'm going to assume you have Magisk and adb/fastboot installed on your PC.
Do you have TWRP installed? If so, just boot into it and dirty flash the latest OTA.
If not, download twrp-3.2.3-2-fajita.img here https://dl.twrp.me/fajita/ and boot into it via fastboot.
On your PC, download the latest OxygenOS from OnePlus website. move the .img you downloaded earlier to your fastboot folder, hold Vol Up + Power until you enter fastboot, back to PC - type into the search bar "cmd" then press enter, type fastboot boot "twrp-3.2.3-2-fajita.img" and press enter. Your phone should boot into TWRP, now copy the OTA file into your phone and install it into both slots (just to be sure).
You're going to lose Magisk if you do this, but you can just reinstall it and it's much better than having a $600 paperweight
Remember that you need to have a working adb and fastboot on your PC to do this.
Some tip: You can backup your data while you're in TWRP via USB mass storage, it's a good idea to do it now just in case your phone is bricked even worse than before.
basedtobeh said:
Since you uninstalled SystemUI.apk, I'm going to assume you have Magisk and adb/fastboot installed on your PC.
Do you have TWRP installed? If so, just boot into it and dirty flash the latest OTA.
If not, download twrp-3.2.3-2-fajita.img here https://dl.twrp.me/fajita/ and boot into it via fastboot.
On your PC, download the latest OxygenOS from OnePlus website. move the .img you downloaded earlier to your fastboot folder, hold Vol Up + Power until you enter fastboot, back to PC - type into the search bar "cmd" then press enter, type fastboot boot "twrp-3.2.3-2-fajita.img" and press enter. Your phone should boot into TWRP, now copy the OTA file into your phone and install it into both slots (just to be sure).
You're going to lose Magisk if you do this, but you can just reinstall it and it's much better than having a $600 paperweight
Remember that you need to have a working adb and fastboot on your PC to do this.
Some tip: You can backup your data while you're in TWRP via USB mass storage, it's a good idea to do it now just in case your phone is bricked even worse than before.
Click to expand...
Click to collapse
i don't want lost my data. my phone twrp installed. https://l.facebook.com/l.php?u=http...v2tKWpgjtH1uNa9qGkEpux3yPIjNDUTQIEPCPb_dVJD7U i don't understand it
He had to delete the wrong systemui apk first, with the commands you quoted
then comes those for apk installation
Code:
adb push SystemUI.apk system/app/SystemUI.apk
reboot
i never tried something like that so I dunno if it would work on all devices, or just on rooted or on no one @ all.
undrahbayar said:
I don't understand this
Then
adb shell
su
rm system/app/SystemUI.apk
exit
Click to expand...
Click to collapse
undrahbayar said:
i don't want lost my data. my phone twrp installed. https://l.facebook.com/l.php?u=http...v2tKWpgjtH1uNa9qGkEpux3yPIjNDUTQIEPCPb_dVJD7U i don't understand it
Click to expand...
Click to collapse
Dirty flashing doesn't wipe your data, but you should definitely back up your data in case something goes wrong.
If you have TWRP installed, just do what I typed on my previous reply. To make it clearer:
1. Download the latest OxygenOS for OnePlus 6T here https://www.oneplus.com/support/softwareupgrade/details?code=9
2. Boot into TWRP (Vol Up + power/Vol down + power, I don't remember which one is for recovery). If it asks for password, enter your PIN number
3. USB mass storage should now be available, you can copy/move files from your phone to PC while in this mode. It's a good idea to backup your data now if you haven't.
4. Copy the OTA file you downloaded into your phone
5. Press Install on TWRP, and select the file you downloaded earlier. It's going to take a while, don't panic.
6. When it has finished, DON'T reboot into system. Instead, go back to TWRP.
7. Press Reboot and choose the other slot (opposite of current slot, so if your current slot is B, press A. if it's A, press B)
8. Install the OTA again (This flashes stock OOS into both slot)
9. Again, DON'T reboot into system, go back to TWRP.
10. Press Reboot in TWRP and choose your previous slot.
11. Boot into system
You're not going to lose data if you do this correctly. But, you're going to lose Magisk if you do this (or maybe TWRP too). Just install Magisk again.
Don't permanently install TWRP on OP 6T because it's going to conflict with Magisk. If you need TWRP, just boot into TWRP.img via fastboot instead of permanently installing it.
I don't exactly know how to flash ROMs on A/B partition devices, but this is what I do and it works everytime. Some steps might be unnecessary, though.
basedtobeh said:
Dirty flashing doesn't wipe your data, but you should definitely back up your data in case something goes wrong.
If you have TWRP installed, just do what I typed on my previous reply. To make it clearer:
1. Download the latest OxygenOS for OnePlus 6T here https://www.oneplus.com/support/softwareupgrade/details?code=9
2. Boot into TWRP (Vol Up + power/Vol down + power, I don't remember which one is for recovery). If it asks for password, enter your PIN number
3. USB mass storage should now be available, you can copy/move files from your phone to PC while in this mode. It's a good idea to backup your data now if you haven't.
4. Copy the OTA file you downloaded into your phone
5. Press Install on TWRP, and select the file you downloaded earlier. It's going to take a while, don't panic.
6. When it has finished, DON'T reboot into system. Instead, go back to TWRP.
7. Press Reboot and choose the other slot (opposite of current slot, so if your current slot is B, press A. if it's A, press B)
8. Install the OTA again (This flashes stock OOS into both slot)
9. Again, DON'T reboot into system, go back to TWRP.
10. Press Reboot in TWRP and choose your previous slot.
11. Boot into system
You're not going to lose data if you do this correctly. But, you're going to lose Magisk if you do this (or maybe TWRP too). Just install Magisk again.
Don't permanently install TWRP on OP 6T because it's going to conflict with Magisk. If you need TWRP, just boot into TWRP.img via fastboot instead of permanently installing it.
I don't exactly know how to flash ROMs on A/B partition devices, but this is what I do and it works everytime. Some steps might be unnecessary, though.
Click to expand...
Click to collapse
i don't fix it. don't work it.
Hello everyone,
I have recently unlocked the bootloader on my Nokia 6.1 plus, and rooted it. I then went ahead and installed TWRP ( App install method - found in the twrp website ). However after I rebooted my phone has been stuck on the TWRP splash screen , I Tried going to download mode , and that just got me back to the twrp splash screen. I turned off the phone and powered it on again , same result . Whatever I do it just keeps going back to the TWRP splash screen .. What is even worse is that my device can not be recognized by my pc while stuck on the splash screen , thus I can not use ADB or Fastboot ...
I am feeling really hopeless and stuck , Help would be much appreciated!! Thanks
Now, dissemble the device and enter edl mode
Sent from my Nokia 6.1 using Tapatalk
MaxTurner771 said:
Hello everyone,
I have recently unlocked the bootloader on my Nokia 6.1 plus, and rooted it. I then went ahead and installed TWRP ( App install method - found in the twrp website ). However after I rebooted my phone has been stuck on the TWRP splash screen , I Tried going to download mode , and that just got me back to the twrp splash screen. I turned off the phone and powered it on again , same result . Whatever I do it just keeps going back to the TWRP splash screen .. What is even worse is that my device can not be recognized by my pc while stuck on the splash screen , thus I can not use ADB or Fastboot ...
I am feeling really hopeless and stuck , Help would be much appreciated!! Thanks
Click to expand...
Click to collapse
You shouldn't have installed TWRP on a A/B device let alone install it via the app. It's okay, We're here to help.
If you have OSTLA in your PC, Just open it up and load all files and select to flash the stock ROM. Select Normal Download/Erase User Data options and if the option to Chech AP status is enabled, Disable it. Select on start or the option to flash stock ROM.
Power off your phone completely. If you can't, Then press the volume+ button and power button. Once the screen goes off, Immediately connect phone to PC.
Phone should now reboot into download mode and stock rom should start flashing. Then it's just a matter of waiting for it to flash and reboot.
CarbonGTR said:
You shouldn't have installed TWRP on a A/B device let alone install it via the app. It's okay, We're here to help.
If you have OSTLA in your PC, Just open it up and load all files and select to flash the stock ROM. Select Normal Download/Erase User Data options and if the option to Chech AP status is enabled, Disable it. Select on start or the option to flash stock ROM.
Power off your phone completely. If you can't, Then press the volume+ button and power button. Once the screen goes off, Immediately connect phone to PC.
Phone should now reboot into download mode and stock rom should start flashing. Then it's just a matter of waiting for it to flash and reboot.
Click to expand...
Click to collapse
I had a problem in that my device would never be recognized by my pc even when i finally manage to put in download mode, However after many days trying I was finally able to do it , and to use OSTL.... so thank you!!
I am wondering now how I will do the thing i wanted from the start which is to flash a kernel if i shouldn't use twrp?
MaxTurner771 said:
I had a problem in that my device would never be recognized by my pc even when i finally manage to put in download mode, However after many days trying I was finally able to do it , and to use OSTL.... so thank you!!
I am wondering now how I will do the thing i wanted from the start which is to flash a kernel if i shouldn't use twrp?
Click to expand...
Click to collapse
So to my understanding what you want to achieve is flash a custom kernel on stock rom. And after you messed up your stock recovery by installing twrp, if you have flashed stock rom using ostla then follow these steps.
First without tampering anything finish an ongoing/pending ota/sp update cause after you install custom kernel you phone won't be able to install OTAs. The last sp is of june so install that.
Now coming to installing the kernel-
*Place your twrp and kernel zip file into your adb folder*
1. Setup usb debugging and connect your device normally to your pc, check if the device is communicating with pc type in "adb devices" and allow on your phone for authorisation.
It should reply with your serial on cmd window.
2. Type in "adb reboot bootloader" that should put your device in download mode.
3. Type in "fastboot boot twrp.img" (replace twrp.img with whatever your twrp image file name is)
4. Go to advanced and select adb sideload, swipe to start.
5. Now move to your cmd window and type in "adb sideload kernel.zip" (replace kernel.zip with whatever your kernel zip file name is)
Wait for the process to finish
Now press home go to wipe>advanced wipe select dalvik cache and swipe to wipe
again press home and select reboot, select system
Now final important step
6. don't swipe, select "do not install twrp"
D-Mi said:
So to my understanding what you want to achieve is flash a custom kernel on stock rom. And after you messed up your stock recovery by installing twrp, if you have flashed stock rom using ostla then follow these steps.
First without tampering anything finish an ongoing/pending ota/sp update cause after you install custom kernel you phone won't be able to install OTAs. The last sp is of june so install that.
Now coming to installing the kernel-
*Place your twrp and kernel zip file into your adb folder*
1. Setup usb debugging and connect your device normally to your pc, check if the device is communicating with pc type in "adb devices" and allow on your phone for authorisation.
It should reply with your serial on cmd window.
2. Type in "adb reboot bootloader" that should put your device in download mode.
3. Type in "fastboot boot twrp.img" (replace twrp.img with whatever your twrp image file name is)
4. Go to advanced and select adb sideload, swipe to start.
5. Now move to your cmd window and type in "adb sideload kernel.zip" (replace kernel.zip with whatever your kernel zip file name is)
Wait for the process to finish
Now press home go to wipe>advanced wipe select dalvik cache and swipe to wipe
again press home and select reboot, select system
Now final important step
6. don't swipe, select "do not install twrp"
Click to expand...
Click to collapse
This might sound like a stupid question but I am a major newbie when it comes to this,
Right now i managed to compile a custom kernel and I have a boot image along with the kernel, so to get the kernel.zip do I just zip up all these files? also I read that I could simply flash the image by rebooting to my bootloader and then using " fastboot flash boot boot.img " would this work , and if so does this mean i don't need twrp...
Thanks again for the help , it is much appreciated
MaxTurner771 said:
This might sound like a stupid question but I am a major newbie when it comes to this,
Right now i managed to compile a custom kernel and I have a boot image along with the kernel, so to get the kernel.zip do I just zip up all these files? also I read that I could simply flash the image by rebooting to my bootloader and then using " fastboot flash boot boot.img " would this work , and if so does this mean i don't need twrp...
Thanks again for the help , it is much appreciated
Click to expand...
Click to collapse
If you just want to flash your custom kernel there's no need to flash a boot.img if you've a running rom installed. You can flash the kernel.zip it via twrp or adb sideload via twrp.
Sorry for the late reply, if you have a bootloader-unlocked 6.1 Plus you should join Nokia 6.1 Plus community on telegram you'll get much faster response from the community regarding your device ?
First of all, I must note that this is my first time flashing a phone, so don't rely too much on my knowledge on the subject, please!
So...
I started by unlocking the OEM and USB debugging from the developer menu, then downloading and extracting ADB tools to my PC. I unlocked my A1 just fine. I then proceeded to install twrp on my phone by using the "fastboot flash boot twrp.img" (as it was named in my ADB folder) and "fastboot reboot" commands. It should be noted that the "fastboot flash recovery twrp.img" did NOT work in the previous step so I have to use the "boot" command instead. TWRP was working perfectly, and I wiped the data from my system and data slots from twrp (there was no cache option in the menu except dalvik which I also wiped).
After that, I added tissot's evolution_tissot-ota-td1a.221105.001-11121815-unsigned.zip and ProjectElixir_3.2_tissot-13.0-20221102-0447-BETA-OFFICIAL.zip to my phone via fastboot after download. Both were flashed successfully (I didn't try to do them both at the same time, of course. One didn't work and stuck on the boot screen for project elixir, so I tried the other after wiping the older one). Both were stuck on the boot screen for their respective teams.
EDIT: Tried it with the stock version PKQ1.180917.001.V10.0.18.0.PDHMIXM.zip, and it worked! Any idea what the issue is here?
If anyone needs more info, I would be glad to provide it. A little help goes a long way!
Cheers