Hi,
Recently ive been trying to root my OnePLus nord 2t CPH2399 (256gb version) using this guide: https://forum.xda-developers.com/t/...3-7-0_12-0-for-oneplus-nord-2t-karen.4503617/
though i failed with the 3rd step as no boot.img will appear when i click install. Every time i try to boot out of TWRP it puts me right back in it, is there a way to escape this bootloop?
thanks
You probably should have asked this question on the relevant thread rather than opening up a new topic.
Did you download the boot.img you need to flash after flashing twrp?
oh, i didnt realize i had to download that, it said nothing about it so i assumed that i find it there, might you be able to send a link to where i can download this?
thanks
Ok so ive continued the guide, using the appropriate boot.img but is still cant get out of the twrp bootloop, anything i try just reboots into either twrp or fastboot and then into twrp, is there any way to fix this?
Related
Ive been trying to fix this for two days. This post is a last resort. Ive searched the forum and tried what little I found.
Ive trashed phones and had to fix them but never seen this.
I finally got root on this thing and was flashing CM10 but kept seeing "failed" using TWRP so decided id flash
CWM and give it a try. Once,still TWRP Twice,still TWRP. Third, Black recovery screen then skip to normal boot.
Fourth try it read "error: cannot load 'openrecovery-twrp-2.3.1.0-evita'" and has since with both recoveries.
No access with volume/power method. No access from command prompt. No access through Quick Boot , Rom Toolbox,
etc.
If I posted this wrong Im sorry. I can usually fix these things myself but Im waving the white flag on this one.
I tried adb help but everything I tried said failed. Any help would be greatly appreciated.
ksflat43 said:
Ive been trying to fix this for two days. This post is a last resort. Ive searched the forum and tried what little I found.
Ive trashed phones and had to fix them but never seen this.
I finally got root on this thing and was flashing CM10 but kept seeing "failed" using TWRP so decided id flash
CWM and give it a try. Once,still TWRP Twice,still TWRP. Third, Black recovery screen then skip to normal boot.
Fourth try it read "error: cannot load 'openrecovery-twrp-2.3.1.0-evita'" and has since with both recoveries.
No access with volume/power method. No access from command prompt. No access through Quick Boot , Rom Toolbox,
etc.
If I posted this wrong Im sorry. I can usually fix these things myself but Im waving the white flag on this one.
I tried adb help but everything I tried said failed. Any help would be greatly appreciated.
Click to expand...
Click to collapse
First off stick with twrp cwm is not officially supported on our device and can blank your SD card...can you link me to the cm ROM you were trying to flash it was for our phone not the international one x right?
tactical kitten said:
First off stick with twrp cwm is not officially supported on our device and can blank your SD card...can you link me to the cm ROM you were trying to flash it was for our phone not the international one x right?
Click to expand...
Click to collapse
Thanks for the reply. Ive got the link. first thing I see wrong is it says endeavoru and mine says evita I believe. The CM10 wouldnt install so I
tried flashing CWM recovery and here we are. Heres the link.
Thanks again.
Well, I cant send you the link. It says new users cant post outside links. Sorry. Its from the CM website. Dated 2012-01-07
ksflat43 said:
Thanks for the reply. Ive got the link. first thing I see wrong is it says endeavoru and mine says evita I believe. The CM10 wouldnt install so I
tried flashing CWM recovery and here we are. Heres the link.
Thanks again.
Well, I cant send you the link. It says new users cant post outside links. Sorry. Its from the CM website. Dated 2012-01-07
Click to expand...
Click to collapse
Ok so corrct me if im wrong the cm10 you're trying to install says endeavoru? That's the intl one x not ours....we have the evita like you stated so you're lucky the build prop check is there or if it successfully flashed you'd be bricked...stay in our forum and you'll be fine...now here are your stepsinstall twrp through fastboot
Move the Rom of you're choice onto your phone(mount in twrp)
If you're on hboot 1.14 you have to flash boot.omg seperately
Wipe data system and cache install Rom enjoy...
You may have to format your sd if cwm corrupted it
tactical kitten said:
Ok so corrct me if im wrong the cm10 you're trying to install says endeavoru? That's the intl one x not ours....we have the evita like you stated so you're lucky the build prop check is there or if it successfully flashed you'd be bricked...stay in our forum and you'll be fine...now here are your stepsinstall twrp through fastboot
Move the Rom of you're choice onto your phone(mount in twrp)
If you're on hboot 1.14 you have to flash boot.omg seperately
Wipe data system and cache install Rom enjoy...
You may have to format your sd if cwm corrupted it
Click to expand...
Click to collapse
I cant install through fastboot. I get the "error cant load" message i talked about in the first post. It wont let me near recovery
if u can get in to fastboot but not in to twrp youll probly have to relock your bootloader and ruu back to stock
Reflash twrp 2.3.3.1 for evita in fastboot, also run fastboot erase cache. If your nandroid was made with cwm it wont work with twrp.
Please help...I recieved my OPO today. It was a chinese version that was supposed ot ship with CM 11s but instead had just regular cm11. I was trying to flash it with twrp recovery first...but could not see a zip file that would flash correctly on the CM OPO page. I ended up trying to use ADB but ended up bricking my phone. I can get into Fastboot mode but that's all. What can I do now to get it workign again...can't even seem to get into recovery anymore. Please help.
acheney1990 said:
Please help...I recieved my OPO today. It was a chinese version that was supposed ot ship with CM 11s but instead had just regular cm11. I was trying to flash it with twrp recovery first...but could not see a zip file that would flash correctly on the CM OPO page. I ended up trying to use ADB but ended up bricking my phone. I can get into Fastboot mode but that's all. What can I do now to get it workign again...can't even seem to get into recovery anymore. Please help.
Click to expand...
Click to collapse
Try flashing a stock image.. follow the instructions on this page: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
extract the image into your adb/fastboot folder and then Run flash-all.bat (if your bootloader is unlocked, if not make sure you unlock it using one of the toolkits available then run flash-all.bat)
Hope this helps.
acheney1990 said:
Please help...I recieved my OPO today. It was a chinese version that was supposed ot ship with CM 11s but instead had just regular cm11. I was trying to flash it with twrp recovery first...but could not see a zip file that would flash correctly on the CM OPO page. I ended up trying to use ADB but ended up bricking my phone. I can get into Fastboot mode but that's all. What can I do now to get it workign again...can't even seem to get into recovery anymore. Please help.
Click to expand...
Click to collapse
I'm assuming your bootloader is unlocked? All you need to do is flash TWRP recovery from here.
Code:
fastboot flash recovery <filename>.img
And then grab one of the recovery flashable versions of CM11S from this thread and flash it. That's your easiest solution.
Transmitted via Bacon
I got it everyone. Thanks though.
Can a moderator please delete those thread.
acheney1990 said:
Can a moderator please delete those thread.
Click to expand...
Click to collapse
No they won't delete it, plus it's good that it remains because the information is now readily available for anyone else who gets into the same situation.
Transmitted via Bacon
Hi Everyone!
Because of having issues i can´t fix on my OnePlus, i´m finally asking for some professional help here, as it´s getting more and more complicated and i don´t want to ruin my phone.
What was my plan?
Installing CM11S 44S on my OPO, which had the 05Q Version as factory setting.
Also i wanted to install a franco kernel.
I hoped, if i do both steps successfully, my OPO will have a good battery life (44S seemed to be the most efficient version, according to some forums).
What did i do so far?
First i set up an adb backup for my data, but not for the OS. However, i installed SDK plus tools and drivers.
Next step was installing a new recovery, which is able to flash a new version of CM11S, so i set up TWRP with fastboot, which means my device is "unlocked" now.
Everything worked well so far, i also made an backup in TWRP.
The problem:
I wanted to reboot my OPO at some point and TWRP asked me for rooting my device. Accidentally i swiped over so it started rooting process, but i didn´t want to root it, so i immediately shut the device down.
By now TWRP recovery/fastboot is working, but my OS 05Q is lost and i can´t install a new ROM because im getting the Report:
--
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
Error flashing zip /<path to .zip file>
--
Can anyone help me to get 05Q back or the 44S with the franco kernel?
I know there might be some other threads that deal with similar problems, but actually none of them helped me so far. For example: do i need a fastboot image or signed flashable zips (which i have)? In which order do i install the kernel and the ROM?
Some Information:
I can access my device via fastboot and my OPO is also shown as a adb device on my MAC.
When starting in TWRP, i can also access the device in USB Mode, transfering files is also possible.
I´m not really competent with android modding or programming, so i will need some noob-friendly answers, but i bet you guys know how to help me out here.
Thank you very much for your help, i really don´t know what to do anymore.
EDIT:
I found out how to place a md5 file to the referring version, but it still sais: MD5 does not match.
I´m so done with it right now that i wish i had my OPO back as it was few days ago.
Well, i cant really help here as i have not face this problem but ur mistake was that u Immediately shut the device down the moment it was installing root. It may have corrupted the partitions of the phone and left it at that state, so maybe restoring the partitions of that section may help. Like i said im not knowledgeable about this
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Thyrix said:
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Click to expand...
Click to collapse
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Heisenberg said:
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Click to expand...
Click to collapse
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Thyrix said:
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Click to expand...
Click to collapse
You need the fastboot images.
Heisenberg said:
You need the fastboot images.
Click to expand...
Click to collapse
Got stuck at step 2: It Terminal said error: cannot determine image filename for sbl1.mbn - although the name is correct and the file is in the correct folder :/
EDIT:
Fixed it, forgot to type sbl1 2 times, im sorry
And it worked, thank you sooooo much!!!
Hey Guys,
I know there are some older threads but im getting a bit confused and a bit desperate. My op6 arrived a few days back and I decided to flash a custom rom today. Got twrp and magisk installed. Tried to flash omnirom and I also flashed twrp again (got confused at the time). Now my phone only boots into fastboot. If anyone could help I would greatly appreciated it, panicking ever so slightly about this. I was on Android oos 9.0 when i tried to flash omnirom 9.0.
I tried to fastboot boot into twrp via the cmd but its giving me an error of (Failed to load/authenticate boot image: load error)
Thanks in advance.
Did you have pie on both slots? And also, if you know there is threads regarding this, why don't you read the sulotions provided?
whizeguy said:
Did you have pie on both slots? And also, if you know there is threads regarding this, why don't you read the sulotions provided?
Click to expand...
Click to collapse
Hey thanks for the quick reply. I looked through some of the other threads and most of them seem to assume that the person does not have an unlocked bootloader and such. Atm im reading through this thread and trying to understand exactly what to do. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/page61
Came from a oneplus 5 so not used to the whole slot system.
But yeah couldnt find a thread that fits my situation for android 9.0
Edited:
From what I understand it should be a pi setup on both if they are both populated.
Edit2:
So good news. Got the phone working again. Used an unbrick tool over on the oneplus forums. If anyone ever finds themselves in the same situation look for the Mega unbrick guide on the oneplus forums.
I'm having the same issue. After watching multiple videos, reading multiple XDA threads, I'm still confused as to what to do. Here is everything that I have done, and continue to have the same issue (reboots into bootloader)
1. Installed latest Oxygen OS via OTA.
2. OEM unlocked.
3. Installed TWRP (Blu Spark 3.2.3)
4. Wiped System, Caches and Data
5. Installed Lineage 16.0 on both slots via TWRP
6. Flashed TWRP.zip
Upon rebooting the phone, it boots straight into the bootloader. Am I doing something wrong or missing something?
Also coming from Nexus 6P and unfamiliar with the slot system...
Edit: 'Unbricked' device by using the method found in this thread...
Hi all,
So i've previously unlocked my Poco X4 Pro 5g and rooted it. All was fine until yesterday where i'm now stuck in the booting screen.
I have installed every OTA update and i'm running global Xiaomi ROM. I noticed the phone was getting buggy and since it hadn't been restarted in some time, I did so in the hopes the bugs would go.
Upon restarting which took a VERY long time, everything was un-rooted(?) following the reboot. I think this is happening because i had to hide Magisk previously for certain apps.
Anyway i tried to re-root by using Magisk by using fastboot to flash my boot.img that Magisk patches from my original install from previous updates back which is where i think the problem lies. Since numerous updates later, the boot.img may have changed hence now why i'm stuck in the boot screen.
What can i do since i can't find a download link the the very latest ROM. Using the original boot.img also causes boot screen freeze so now i'm out of ideas
Any ideas?
stevey88 said:
Hi all,
So i've previously unlocked my Poco X4 Pro 5g and rooted it. All was fine until yesterday where i'm now stuck in the booting screen.
I have installed every OTA update and i'm running global Xiaomi ROM. I noticed the phone was getting buggy and since it hadn't been restarted in some time, I did so in the hopes the bugs would go.
Upon restarting which took a VERY long time, everything was un-rooted(?) following the reboot. I think this is happening because i had to hide Magisk previously for certain apps.
Anyway i tried to re-root by using Magisk by using fastboot to flash my boot.img that Magisk patches from my original install from previous updates back which is where i think the problem lies. Since numerous updates later, the boot.img may have changed hence now why i'm stuck in the boot screen.
What can i do since i can't find a download link the the very latest ROM. Using the original boot.img also causes boot screen freeze so now i'm out of ideas
Any ideas?
Click to expand...
Click to collapse
Use this tool
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Thanks for your reply, could you tell me what has gone wrong with the phone and what i need to do?
I've followed the link, the flash tool wont install the drivers and crashes (i have created a log folder which seems to be a common issue but doesn't fix). I've attempted to flash but i receive the error:Antirollback check error.
I'm not sure what, if anything has happened but now im stuck in fastboot mode!
Looking at the images in the link, it looks like following this guide will wipe my phone?
I'd like to attempt to recover it first if possible, could you tell me what your link is intending me to do?
stevey88 said:
Thanks for your reply, could you tell me what has gone wrong with the phone and what i need to do?
I've followed the link, the flash tool wont install the drivers and crashes (i have created a log folder which seems to be a common issue but doesn't fix). I've attempted to flash but i receive the error:Antirollback check error.
I'm not sure what, if anything has happened but now im stuck in fastboot mode!
Looking at the images in the link, it looks like following this guide will wipe my phone?
I'd like to attempt to recover it first if possible, could you tell me what your link is intending me to do?
Click to expand...
Click to collapse
The root seems to be the source of the problem.
ARB problem: install a more recent rom or delete the lines concerning ARB from the rom script or use the script directly from the rom folder without going through Miflash or trying an older version of Miflash.
Indeed the flash will delete your data, if you have access to Twrp try to save, without guarantee that the backup or restore will work.
Miflash will allow you to recover your phone.
stevey88 said:
Thanks for your reply, could you tell me what has gone wrong with the phone and what i need to do?
I've followed the link, the flash tool wont install the drivers and crashes (i have created a log folder which seems to be a common issue but doesn't fix). I've attempted to flash but i receive the error:Antirollback check error.
I'm not sure what, if anything has happened but now im stuck in fastboot mode!
Looking at the images in the link, it looks like following this guide will wipe my phone?
I'd like to attempt to recover it first if possible, could you tell me what your link is intending me to do?
Click to expand...
Click to collapse
Hey, i had to use miflash tool today, and also got the antirollback error on my first attempt. Turned out, in my case it was caused by spaces in the path to the rom folder.
Might not be the case for you, but worth checking, eh?
Also, make sure to double-tripple check the "clean"/"clean and lock" flag in the miflash tool before flashing it. Wouldn't want to accidentally lock it again
JustRay76 said:
Hey, i had to use miflash tool today, and also got the antirollback error on my first attempt. Turned out, in my case it was caused by spaces in the path to the rom folder.
Might not be the case for you, but worth checking, eh?
Also, make sure to double-tripple check the "clean"/"clean and lock" flag in the miflash tool before flashing it. Wouldn't want to accidentally lock it again
Click to expand...
Click to collapse
I was able to miflash working by commenting out the anti rollback checks in the batch scripts. I had other issues due to long folder names. I was able to reflash and recover, thanks again to NOSS8
I really regret not backing stuff up before restarting although i should've before loading a boot.img
I'm attempting to patch the latest boot.img using Magisk, hopefully all will go well this time. At least I've got nothing to loose now!
Hello bro I understood your problem that was caused by magisk i also faced this issue and understood that it is making problem while patching the boot.img thats why I reccomend to not patch the image because it ends with a bootloop just rename the Magisk.apk to Magisk.zip and flash it normally with a custom recovery now al done you can use magisk without bootloop but dont forget to flash bootloop saver magisk module to be safe from other magisk module issues