Flashed magisk patched boot.img, wifi and recovery mode no longer working - OnePlus 7T Questions & Answers

Hi guys,
I tried patching and flashing my boot.img, which lead to a CrashDump. I reflashed the stock boot.img, but now I can't boot into recovery mode (just brings me back to the language select menu) and I can't turn on WiFi. Anyone know of a way to flash stock without recovery?
EDIT: Fixed by following https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213

Related

Flashing OTA failed. I need help to restore my phone.

Hi,
My phone is rooted and the DPI was customized. I tried to manually flash the OTA but the installation got stuck so I cannot boot into Android anymore. I tried those restore tutorials but when I try to flash using fastboot I get a "FAILED (remote: Permission denied). I tried to clear the cache in the recovery and then it got also stuck and now I can't access recovery.
This is what I can read in the bootloader
---------------------------
FASTBOOT MODE
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
HW_VERSION -
BOOTLOADER VERSION - unknown
IFWI - 0094.0177
SERIAL NUMBER - Xxxxx....
SIGNING - ?
SECURE_BOOT - ?
continue fastboot process
-----------------------------
I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!
manlord said:
I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!
Click to expand...
Click to collapse
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....
ultramag69 said:
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....
Click to expand...
Click to collapse
Thanks for your help. I did that earlier with the latest pre-rooted OTA and now it gets stuck on the splashscreen. I tried going to recovery (stock now) and doing a factory reset after flashing system.img and it still the splashscreen after I reboot. I know the 1st boot after flahing a ROM can be long, but now it's been an hour and I'm still on the splash screen...
The only other thing I can recommend is to flash a RAW rom image. As I have never needed to do this I can't say how this works but if you do a search you should find out the procedure...
This may relock your bootloader so just be aware....

[SOLVED] HELP! i'm stuck in a boot loop! :(

my flashing history:
i was on audax (oos based nougat rom) with blu spark kernel before, then went to official ob1, then back to audax, then back to stock oos nougat and now i flashed audax and after clean flashing it, it just wont boot up.
when i try to boot up i see the 1+ logo but then it reboots to recovery. i also tried flashing stock nougat again and also flashed stock kernel manually but it also doesnt work.
i always do:
1. wipe system/dalvic/cache/data
2. install ROM
3. wipe dalvik/cache
4. flash magisk (also tried without flashing magisk)
5. reboot
i've been looking on the interwebs all day but nothing worked.. help pls :/
EDIT: problem was blu spark twrp. Maybe installing Oreo ****ed it up. I flashed codeworkx newest twrp universal build and now Im able to boot again!! Btw: I also found that magisk 15.0 prohibits a proper boot up and results in a boot loop. version 15.2, however, does the trick!
when it auto reboot to recovery, formate data
When s**t happens, it is wise to start everything from scratch:
-boot in fastboot mode and flash stock recovery with "fastboot flash recovery recovery.img" (rename recovery.img with your recovery filename), then reboot recovery and select english, advanced, adb sideload;
-flash stock OS with "adb sideload rom.zip" (rename rom.zip with your Oxygen OS filename).
Procedure will require some minute because of the large file size. Remember to save all your data on internal storage first!
I advice you to flash original recovery because often sideloading in TWRP leads to some error.
Your phone will boot again... after that you may reflash TWRP, Magisk etc
I had the same issue. Bootloop and jumb into recovery by itself. You have to flash magisk 15.2 via recovery and will be boot.
redatak said:
I had the same issue. Bootloop and jumb into recovery by itself. You have to flash magisk 15.2 via recovery and will be boot.
Click to expand...
Click to collapse
He says that it occurs even without Magisk... I had a similar trouble once, and the only way to solve it was the procedure I wrote above...
I dont know if you can boot it w/o root
redatak said:
I dont know if you can boot it w/o root
Click to expand...
Click to collapse
Why not? Stock OS is not rooted.
jonsat said:
Why not? Stock OS is not rooted.
Click to expand...
Click to collapse
He said audrax not stock oos
SOLVED! TWRP was the only variable left that I didn't think of. See initial post for solution. thx for help!

in need of assistance on android 9.0 kernel & rooting issue

I flashed twrp recovery then i did not reboot i flashed a kernel witch is 9.0 compatiable then flashed magisk now I am stuck on a white screen with the Google G with a loading bar any help would be great
WoZzYDoesitbest said:
I flashed twrp recovery then i did not reboot i flashed a kernel witch is 9.0 compatiable then flashed magisk now I am stuck on a white screen with the Google G with a loading bar any help would be great
Click to expand...
Click to collapse
Just extract and fastboot flash the original boot.img from the factory image. You'll have to open the nested zipfile in the image file to get to it. Once you flash it, you should be back where you started and able to boot system. Retrace your steps and found out what you did wrong. Which kernel? As a side note, you should first fastboot boot the TWRP.img file and then while you are in TWRP, you flash the TWRP zip file. You can also use TWRP (boot) to queue up TWRP, Kernel, and Magisk and they will all flash in that sequence saving some time. There are also sticky guides on how to do this.
v12xke said:
Just extract and fastboot flash the original boot.img from the factory image. You'll have to open the nested zipfile in the image file to get to it. Once you flash it, you should be back where you started and able to boot system. Retrace your steps and found out what you did wrong. Which kernel? As a side note, you should first fastboot boot the TWRP.img file and then while you are in TWRP, you flash the TWRP zip file. You can also use TWRP (boot) to queue up TWRP, Kernel, and Magisk and they will all flash in that sequence saving some time. There are also sticky guides on how to do this.
Click to expand...
Click to collapse
Yeah appreciate it i figured it out last night this phone drives me nuts

Semi-bricked XA1, possible recovery?

So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Darth343 said:
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Click to expand...
Click to collapse
OK use the boot.img and recovery.img made by @janjan HERE. Under the heading ¨Downloads¨ see ¨Xperia XA1¨ and download the KERNEL + RECOVERY the boot.img and recovery.img are compatible with the G3121-G3112-G3125-G3116-G3123 devices on the applicable firmware.
Flash BOTH using fastboot. The boot.img is patched to allow TWRP to boot which it will never do using the stock boot.
If you wish to go back to stock then simply use FlashTool to flash the stock fotakernel.sin and boot.sin contained in the firmware for your device.
Does it works becouse I boot my g3116 from flashtool camand was
Fastboot boot boot.img and then also it's stuck into bootloader

{GUIDE} - fix for being stuck at samsung boot screen due to rollback protection

Hi all I have been tinkering away and destrying my setup left right and centre to sort this process out but if you're unable to run the latest TWRP for your note from Ian and get stuck at SAMSUNG screen on boot then this process will fix that if followed correctly. This is due to the device's roll back protection.
This process will reset everything back to current date and get everything working on the new Oneui 2.1 base
Process for getting round SAMSUNG screen issue - please read through first and get the files you need before starting. I did this on my N976B but in theory it should work for other 10-range devices, notes indeed!
UNLESS YOUR RUNNING CRUEL KERNEL OR A SPIN OFF, YOU'LL NEED VOL UP AND POWER TO ACTIVATE MAGISK ON EACH BOOT
Needed:
Stock firnware
Magisk app
Twrp image
Pc and odin also patience and a brain lol
-Return to stock by flashing AP/BL/CP&CSC in odin
-Reboot and confirm oem unlocking greyed out, install magisk app and patch twrp image from Ian, also patch your ap file.
-reboot to download, meanwhile get the magisk_patched.tar and insert TWRP renamed as recovery.img in place of the stock patched recovery (keep this one for later)
-In download mode and with auto reboot off in odin, flash BL, Magisk_patched.tar(with the TWRP from Ian in), CP & HOMECSC.
-When flashing is complete exit download mode and immediately hold power and vol up and hold until on TWRP slider screen. swipe to allow modifications, format internal storage and flash multidisabler.
-Reboot TWRP and backup your current patched stock rom. FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER AND THEN FLASH MULTIDISABLER (THIS IS IMPORTANT AS YOU WILL THEN BE ABLE TO INSTALL TWRP VIA THE APP WITHOUT HAVING TO REFORMAT INTERNAL)
-Reboot straight to stock recovery (reboot from TWRP and hold Vol up and power until in stock recovery) and factory reset then reboot.
-You should now boot up as normal, setup your device, in particular have TWRP app and Magisk set up and running.
-Flash the Unpatched TWRP for your device in the TWRP app - reboot TWRP and check the box to kill that annoying swipe to allow modifications and then you are good to flash whatever rom or kernel you want for your device!
Flash the stock patch recovery as boot??
orbital_71 said:
Flash the stock patch recovery as boot??
Click to expand...
Click to collapse
yes then immediately flash multidisabler before you reboot to set up
i have just helped someone through this on TG so it defo works :good::good::good:
It can also confirm this is working. Just followed this guide on my Note 10+ (N975F with CTD1) and happy flashing now.
drexxie1962 said:
It can also confirm this is working. Just followed this guide on my Note 10+ and happy flashing now.
Click to expand...
Click to collapse
Excellent, thanks for testing!!!!!!!
@askmydas
you may find this useful - follow this to get your sec date reset then follow the process spelt out in the thread of the rom you want to use as you may need a different TWRP depending on what sec date the chef of your chosen rom uses.
Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?
KiwiNote+ said:
Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?
Click to expand...
Click to collapse
I worked it out, I was trying to install "recovery.img" to boot partition, "recovery.img" needs to be installed to RECOVERY partition. Silly me. Fixed it now, but have a new issue:
After I flash unpatched twrp image through the app, now my phone will only boot into TWRP. I don't even boot with recovery button presses, but it will still boot into TWRP only. Any ideas?
I know this is an old thread, but it may be that my solution could help someone who is locked on the outside of the device (softbrick)
TD,DR: If you have softbrick and you can't boot the device at all, try flashing via Odin the BL, CP, CSC from a stock rom and the AP of another completely different stock rom.
I had an IMEI 0000 issue on my Galaxy Note 8 (SM-N950F), using Hades Rom (custom), and I needed to install the stock rom. As I was on the F(15) binary, there were only two roms (SamMobile and Stockrom.net) available for my country (Brazil) with this binary:
N950FXXUFDUD6_N950FOXMFDUD6_ZTO
stockrom.net_N950FXXUFDUG5_N950FOXMFDUG4_ZTO
And a via Frija:
SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And no Combination Rom for that binary
After flashing these roms several times, I was always stuck on the “Powered by Google” screen, even doing cache wipe and factory reset through stock recovery several times. So I flashed the N950FOXMFDUD6, flashed the CF-Auto-Root and was able to boot the device. Once inside I noticed that it didn't solve the problem of IMEI 0000. I tried a few more procedures, ended up restarting to install TWRP, and the OEM is closed!!! (OEM OFF, Prenormal). I start getting the message “only official binaries are allowed to be flashed(recovery)”. I flash the stock rom, but it gets stuck on “Powered by Google” again. I tryed to install CF-Auto-Root and I get the message “only official binaries…” I can't log into the device anymore. So after four days of desperation, trying every technique possible, trying to create the Combination Rom by unzipping the AP file from the stock Rom and modifying the files inside, without success, I finally try a procedure I haven't seen anywhere else: I go to the modified Odin: Odin3_v3.14.1_3B_PatcheD, I selected the BL, CP, CSC files from the N950FOXMFDUD6 rom and the AP file from the rom SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And it worked! I can boot the device

Categories

Resources