Hello..
i have flashed the [SuperSU-v2.78-201609011115.zip] from this thread , but when i rebooted my OPX i've ended with bootloop.
tried to wipe cache partition and dalvik, but no results.
I do know how to recover from a simple bootloop , but i still need root.
Any thoughts or ideas or solutions will be appreciated.
device Info:
Oneplus X
Android 6.0.1 OxygenOs 3.1.4
with unofficial twrp recovery from this thread
thanks.
Mr.3bood said:
Hello..
i have flashed the [SuperSU-v2.78-201609011115.zip] from this thread , but when i rebooted my OPX i've ended with bootloop.
tried to wipe cache partition and dalvik, but no results.
I do know how to recover from a simple bootloop , but i still need root.
Any thoughts or ideas or solutions will be appreciated.
device Info:
Oneplus X
Android 6.0.1 OxygenOs 3.1.4
with unofficial twrp recovery from this thread
thanks.
Click to expand...
Click to collapse
Use modified supersu for oos 3.x.x
cva_kabil said:
Use modified supersu for oos 3.x.x
Click to expand...
Click to collapse
I've Googled it and found it here ,
scroll down in the replies until you see "modded superSU 2.78 for OOS 3"
Thanks a lot and thanks button was hit.
thread closed
Mr.3bood said:
Hello..
i have flashed the [SuperSU-v2.78-201609011115.zip] from this thread , but when i rebooted my OPX i've ended with bootloop.
tried to wipe cache partition and dalvik, but no results.
I do know how to recover from a simple bootloop , but i still need root.
Any thoughts or ideas or solutions will be appreciated.
device Info:
Oneplus X
Android 6.0.1 OxygenOs 3.1.4
with unofficial twrp recovery from this thread
thanks.
Click to expand...
Click to collapse
Try http://forum.xda-developers.com/attachment.php?attachmentid=3939651&d=1479393635
Mr.3bood said:
I've Googled it and found it here ,
scroll down in the replies until you see "modded superSU 2.78 for OOS 3"
Thanks a lot and thanks button was hit.
thread closed
Click to expand...
Click to collapse
haha u r welcome
godai74 said:
Try http://forum.xda-developers.com/attachment.php?attachmentid=3939651&d=1479393635
Click to expand...
Click to collapse
Thanks man! It amazingly worked.
Related
I'm trying to flash my GNote and have a custom recovery. However when I try to flash a custom rom, CM10 in particular, I get an error that says Status 7. I have searched here and google and cannot find a fix or explanation of what is wrong. Any takers? Thanks for the help. :good:
cdanford said:
I'm trying to flash my GNote and have a custom recovery. However when I try to flash a custom rom, CM10 in particular, I get an error that says Status 7. I have searched here and google and cannot find a fix or explanation of what is wrong. Any takers? Thanks for the help. :good:
Click to expand...
Click to collapse
Update to the lastest cwm or use twrp. I recommend twrp.
just_visiting said:
Update to the lastest cwm or use twrp. I recommend twrp.
Click to expand...
Click to collapse
What version of twrp do you have?
cdanford said:
What version of twrp do you have?
Click to expand...
Click to collapse
Version 2.3.1.1
The link is in the Original Android Development forum.
http://forum.xda-developers.com/showthread.php?t=1647575
I got TWRP installed and flashed CM10 but it is stuck in the boot screen. I wiped cache, dalvik, and factory settings and flashing again. Any idea?
Got it working just fine. THanks for the support guys!
cdanford said:
Got it working just fine. THanks for the support guys!
Click to expand...
Click to collapse
Mind sharing how? I'm on the latest TWRP and CWM, and both cause a bootloop no matter what I do.
derArzt12 said:
Mind sharing how? I'm on the latest TWRP and CWM, and both cause a bootloop no matter what I do.
Click to expand...
Click to collapse
He had an error. Not a bootloop. You're doing something wrong.
Sent from my GT-N7005 using xda premium
joe3681 said:
He had an error. Not a bootloop. You're doing something wrong.
Sent from my GT-N7005 using xda premium
Click to expand...
Click to collapse
cdanford said:
I got TWRP installed and flashed CM10 but it is stuck in the boot screen. I wiped cache, dalvik, and factory settings and flashing again. Any idea?
Click to expand...
Click to collapse
I have the same error, which causes a bootloop. And in his comment it says he's stuck in one.
status 7 error message:radio
kindly check your radio base band and update xxlf1 using thread and try the update again
Hi guys I was on official mm then I came back to lollipop , installed twrp wiped data to install ROM then I booted into the ROM I stuck at 1 plus logo. My recovery (twrp) was working(thank God) , Now I am only able to install OOS please help me out.
9888 said:
Hi guys I was on official mm then I came back to lollipop , installed twrp wiped data to install ROM then I booted into the ROM I stuck at 1 plus logo. My recovery (twrp) was working(thank God) , Now I am only able to install OOS please help me out.
Click to expand...
Click to collapse
Can't use the twrp you used on OS 3 for ROMs that don have updated bootloader (currently Ashwins CM13, CM14 do.) For the rest you have to use original twrp. You can just flash it in your current recovery by pressing IMG button bottom right.
Exodusche said:
Can't use the twrp you used on OS 3 for ROMs that don have updated bootloader (currently Ashwins CM13, CM14 do.) For the rest you have to use original twrp. You can just flash it in your current recovery by pressing IMG button bottom right.
Click to expand...
Click to collapse
Bro I am using original twrp IMG
9888 said:
Bro I am using original twrp IMG
Click to expand...
Click to collapse
Sorry I was just guessing so many people having issues lol. What ROM and are you flashing anything after ROM like root etc?
Exodusche said:
Can't use the twrp you used on OS 3 for ROMs that don have updated bootloader (currently Ashwins CM13, CM14 do.) For the rest you have to use original twrp. You can just flash it in your current recovery by pressing IMG button bottom right.
Click to expand...
Click to collapse
Exodusche said:
Sorry I was just guessing so many people having issues lol. What ROM and are you flashing anything after ROM like root etc?
Click to expand...
Click to collapse
It's not time to guess please help me
9888 said:
It's not time to guess please help me
Click to expand...
Click to collapse
Did you install OS 2 before you flashed original twrp?
You have tou use the correct corresponding twrp for each Android version. Official 3.0.20 and unofficial oos 3 twrp version don't work both ways.
Omicron Technics
Fastboot install old OnePlus recovery, then flash OOS 2.2.3.
Then fastboot flash Official TWRP.
Exodusche said:
Did you install OS 2 before you flashed original twrp?
Click to expand...
Click to collapse
yes
Kéno40 said:
Fastboot install old OnePlus recovery, then flash OOS 2.2.3.
Then fastboot flash Official TWRP.
Click to expand...
Click to collapse
ok
I somehow uninstalled my OS tonight when I was trying to flash AOSP's Oreo ROM. The flashing was unsuccessful (Error: 7) but I've noticed that no ROMs will flash at all.
I'm getting the same error for all ROMs despite them being suitable for my device:
Updater Process ended with ERROR: 7 Error Installing Zip File "ROM xx.x.x..."
Click to expand...
Click to collapse
Things I've done:
I've tried wiping the cache before I flash ROMS
I am on the most updated version of TWRP available for my device (3.0.2)
I've tried changing the updater-script as someone pointed out in another thread but it did not help
At this point, I just want a stable OS that will run on the phone.... Can someone help me? I just want to understand the error and what's causing it and install a ROM that would work...
Look for Mega Unbrick Guide to install a OS.
Sent from my Pixel 2 XL using Tapatalk
That's odd, because Error 7 is usually related to Updater-Script. Have you modified your model name in Updater-Script or just removed the line from it?
jklh said:
[*]I am on the most updated version of TWRP available for my device (3.0.2)
.
Click to expand...
Click to collapse
TWRP version is 3.1.1-1 now so you're not on the last.
Beside that, the question is what was on your device before :
- Did you already installed OOS 3.1.4 at one point?
- Didi you use the BLUpdater method to update the bootloader (logic ) ?
If no to the 2 questions above, that is the problem. So , you'll have to use the mega unbrick guide !
Kéno40 said:
TWRP version is 3.1.1-1 now so you're not on the last.
Beside that, the question is what was on your device before :
- Did you already installed OOS 3.1.4 at one point?
- Didi you use the BLUpdater method to update the bootloader (logic ) ?
If no to the 2 questions above, that is the problem. So , you'll have to use the mega unbrick guide !
Click to expand...
Click to collapse
I actually haven't done both. I tried flashing the OOS 3.1.4 full ROM but it did not work. I will update my TWRP to 3.1.1-1 and I'll try it again. I do have an update though, I am able to flash an old version of Android M OOS using "OnePlusOxygen_14_OTA_003_all_201510241934". If I am able to install this, maybe this isn't a bricked device? Any advice would be super useful, thanks in advance.
jklh said:
I actually haven't done both. I tried flashing the OOS 3.1.4 full ROM but it did not work. I will update my TWRP to 3.1.1-1 and I'll try it again. I do have an update though, I am able to flash an old version of Android M OOS using "OnePlusOxygen_14_OTA_003_all_201510241934". If I am able to install this, maybe this isn't a bricked device? Any advice would be super useful, thanks in advance.
Click to expand...
Click to collapse
If you haven't done any of the 2 things listed, then you tried to flash a "new Bootloader rom", you have no choice :
=> MEGA UNBRICK GUIDE
Hi guys , i just flashed lieange 15.1 and i even flashed otp encrypter and super sub but whenever i try to launch supersu it says root undetected, can you help please ? Thx in advance .
thewall95678 said:
Hi guys , i just flashed lieange 15.1 and i even flashed otp encrypter and super sub but whenever i try to launch supersu it says root undetected, can you help please ? Thx in advance .
Click to expand...
Click to collapse
Dont use supersu, it's outdated. Use Magisk.
k3lcior said:
Dont use supersu, it's outdated. Use Magisk.
Click to expand...
Click to collapse
So i just need to flash magisk and thats it ?
thewall95678 said:
So i just need to flash magisk and thats it ?
Click to expand...
Click to collapse
Yes, flash magisk from 1st post in Lineage 15.1 thread, you need Treble TWRP homever - https://androidfilehost.com/?fid=890278863836285248
k3lcior said:
Dont use supersu, it's outdated. Use Magisk.
Click to expand...
Click to collapse
Just tried to flash magisk , it says updater process ended with error : 1
Tried to reflash the rom , now i dont have root nor twrp , what can i do ?
thewall95678 said:
Tried to reflash the rom , now i dont have root nor twrp , what can i do ?
Click to expand...
Click to collapse
What about reading what i've said? You didn't flash Treble TWRP that's why u got error 1 while trying to flash Magisk.
Reboot to recovery with Power & VOL+, flash TWRP linked by me, flash magisk from 1st post of LOS 15.1 thread.
k3lcior said:
What about reading what i've said? You didn't flash Treble TWRP that's why u got error 1 while trying to flash Magisk.
Click to expand...
Click to collapse
I hadnt read your post yet and i tried to reflash
Hi,
I tried to install Magisk by first unlocking the bootloader, installing a custom recovery (TWRP) and later flashing Magisk. Unfortunately during the installation of TWRP I got hit with boot loop and used Sony's flash tool to get the stock ROM and get booted. But the ROM offered by flash tool is 6.01 (Marshmallow). Then I tried to install the latest Magisk 20.4 both by using TWRP and by using Magisk manager. But both resulted in the 'Unsupported/Unknown image format' error. These are the logs I see are:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
Basically I want to:
1) Install Magisk
2) Upgrade from Marshmallow to the latest Android stock.
Any guidance is highly appreciated.
Thanks,
Karthik
Karthik.V.M said:
Hi,
I tried to install Magisk by first unlocking the bootloader, installing a custom recovery (TWRP) and later flashing Magisk. Unfortunately during the installation of TWRP I got hit with boot loop and used Sony's flash tool to get the stock ROM and get booted. But the ROM offered by flash tool is 6.01 (Marshmallow). Then I tried to install the latest Magisk 20.4 both by using TWRP and by using Magisk manager. But both resulted in the 'Unsupported/Unknown image format' error. These are the logs I see are:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
Basically I want to:
1) Install Magisk
2) Upgrade from Marshmallow to the latest Android stock.
Any guidance is highly appreciated.
Thanks,
Karthik
Click to expand...
Click to collapse
Hi, first install the latest stock android rom and then flash magisk with twrp. Also you can try the stable versions, not canary.
Good luck, zaqm
zaqm said:
Hi, first install the latest stock android rom and then flash magisk with twrp. Also you can try the stable versions, not canary.
Good luck, zaqm
Click to expand...
Click to collapse
Hi Zaqm,
Thanks for your reply. I am a newbie in this whole process. Can you point me where can I get the latest stock android rom? Also should I use TWRP to install it? Your help is much appreciated. :good:
Regards,
Karthik
Karthik.V.M said:
Hi Zaqm,
Thanks for your reply. I am a newbie in this whole process. Can you point me where can I get the latest stock android rom? Also should I use TWRP to install it? Your help is much appreciated. :good:
Regards,
Karthik
Click to expand...
Click to collapse
Hi Zaqm,
I have managed to flash the latest stock android (8.0) using flashtool and xperifirm tool. When I tried to install magisk using TWRP on the latest stock android, I still get the same error message 'Unsupported/Unknown image format'. Any pointers are welcome.
Thanks,
Karthik
Karthik.V.M said:
Hi Zaqm,
I have managed to flash the latest stock android (8.0) using flashtool and xperifirm tool. When I tried to install magisk using TWRP on the latest stock android, I still get the same error message 'Unsupported/Unknown image format'. Any pointers are welcome.
Thanks,
Karthik
Click to expand...
Click to collapse
Hi, sorry for the late reply. Which magisk version did you try to flash? You can try v18 or 18.1 which I think are compatible with Android 8.
Good luck, zaqm
zaqm said:
Hi, sorry for the late reply. Which magisk version did you try to flash? You can try v18 or 18.1 which I think are compatible with Android 8.
Good luck, zaqm
Click to expand...
Click to collapse
HI Zaqm,
I tried the latest Magisk 20.4 and few other previous versions but I don't remember giving v18 or v18.1 a try. I will do that.
Also, I would like to share that I did not allow TWRP to modify the system partition. I opted to keep the system partition 'Read Only'. The reason I did this is that whenever I allow TWRP to modify the system partition, I get stuck at the SONY boot logo and my phone would not boot and I need to reflash the stock ROM again.
I also came to know that I need to flash a rooted kernel to avoid the bootloop or I should flash the drm fix if I want to keep the stock kernel. Can you comment on that?
Thanks,
Karthik
Karthik.V.M said:
HI Zaqm,
I tried the latest Magisk 20.4 and few other previous versions but I don't remember giving v18 or v18.1 a try. I will do that.
Also, I would like to share that I did not allow TWRP to modify the system partition. I opted to keep the system partition 'Read Only'. The reason I did this is that whenever I allow TWRP to modify the system partition, I get stuck at the SONY boot logo and my phone would not boot and I need to reflash the stock ROM again.
I also came to know that I need to flash a rooted kernel to avoid the bootloop or I should flash the drm fix if I want to keep the stock kernel. Can you comment on that?
Thanks,
Karthik
Click to expand...
Click to collapse
Hi, I'm sorry but I don't own myself a Xperia X and can't tell such specific things related to it. Let someone else answer these questions.
Good luck, zaqm
zaqm said:
Hi, I'm sorry but I don't own myself a Xperia X and can't tell such specific things related to it. Let someone else answer these questions.
Good luck, zaqm
Click to expand...
Click to collapse
Hi Zaqm,
Sorry for my delayed reply. I appreciate your pointers. I will update this thread with my findings. Will keep you posted.
Thanks,
Karthik
Karthik.V.M said:
Hi Zaqm,
Sorry for my delayed reply. I appreciate your pointers. I will update this thread with my findings. Will keep you posted.
Thanks,
Karthik
Click to expand...
Click to collapse
Hi, did you solve the error? i face the exactly same problem but mine is xperia sp.
same problem without solve