[Q] OnePlus One-Ubuntu Help - ONE Q&A, Help & Troubleshooting

Ok guys here is the deal.
Im using ubuntu 14.04lts and Im owner of opo 64gb.
I managed to unlock and root device via cmd on ubuntu and it worked perfect. Problem is that I tried to update modem on opo but it resulted problems. I could boot device but after PIN resolve device ended in reboot, again and again and again.
Now, stupid me I forgot to backup it and I menaged to wipe everything on device hoping somehow that Im gonna flash stock rom again.
But problem started there, as I tried to find solution how to flash stock rom. Now I can do to things, go into fastboot mod manuely, and go into recovery mod TWRP. From there I tried to flash rom but I constantly get message that it cant do it.
I dont know how to sideload zip file from cmd to phone and I tried to flash manuely sys.img, recovery.img and others without result.
Is there anyone here how can guid me step by step and show me how to do it in ubuntu?

mbadboyp said:
Ok guys here is the deal.
Im using ubuntu 14.04lts and Im owner of opo 64gb.
I managed to unlock and root device via cmd on ubuntu and it worked perfect. Problem is that I tried to update modem on opo but it resulted problems. I could boot device but after PIN resolve device ended in reboot, again and again and again.
Now, stupid me I forgot to backup it and I menaged to wipe everything on device hoping somehow that Im gonna flash stock rom again.
But problem started there, as I tried to find solution how to flash stock rom. Now I can do to things, go into fastboot mod manuely, and go into recovery mod TWRP. From there I tried to flash rom but I constantly get message that it cant do it.
I dont know how to sideload zip file from cmd to phone and I tried to flash manuely sys.img, recovery.img and others without result.
Is there anyone here how can guid me step by step and show me how to do it in ubuntu?
Click to expand...
Click to collapse
Have you tried flashing each item of the os individually? Also, i'm using ubuntu 14.04 and can follow mac tutorials well, you might want to search that instead. You will get your phone working again man let me know what you find and how I can help you.
---------- Post added at 07:07 PM ---------- Previous post was at 07:00 PM ----------
check this link out it might be of use. http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541

check this link out it might be of use. http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541

Related

Symlinks Failed .... can't install a ROM

I think I screwed up big time....
I just got my M8 (came from an M7) and I am def S-OFF (checked in bootloader). I have TWRP and when I try to install any ROM, it starts ok first but then it ends with symlinks failed. When I hit reboot, it goes back into recovery. I think I might now the issue and I think it is because I did not delete weaksauce ... I just installed TWRP and rebooted and everything was deleted so I have the custom ROM on the external SD card. I can't even do sideload because it won't find it (when I do adb devices it shows list of devices found but it's empty .. no number like it should be). I fudged up, I know....not sure if it is the weaksauce issue but I'm grateful for any help
UPDATE 1
I have switched to CWM and looks like sideload now works...I'm just installing a ROM and hopefully it'll work. If not, would anybody suggest this...
http://forum.xda-developers.com/showthread.php?t=2727831
the whole RUU flash....either option 1 (if it works) or option 2? If I'm understanding it right, this will wipe everything and go back to stock completely ... then I can do it all over and not screw up...
UPDATE 2
Got it to work....just for those who may have had the same issue. After switching to CWM, sideload did not work. I placed the ROM on an external SD and flashed it as usual and this time it worked (it did not on TWRP for some reason).
?
ghilliek9 said:
I think I screwed up big time....
I just got my M8 (came from an M7) and I am def S-OFF (checked in bootloader). I have TWRP and when I try to install any ROM, it starts ok first but then it ends with symlinks failed. When I hit reboot, it goes back into recovery. I think I might now the issue and I think it is because I did not delete weaksauce ... I just installed TWRP and rebooted and everything was deleted so I have the custom ROM on the external SD card. I can't even do sideload because it won't find it (when I do adb devices it shows list of devices found but it's empty .. no number like it should be). I fudged up, I know....not sure if it is the weaksauce issue but I'm grateful for any help
UPDATE 1
I have switched to CWM and looks like sideload now works...I'm just installing a ROM and hopefully it'll work. If not, would anybody suggest this...
http://forum.xda-developers.com/showthread.php?t=2727831
the whole RUU flash....either option 1 (if it works) or option 2? If I'm understanding it right, this will wipe everything and go back to stock completely ... then I can do it all over and not screw up...
UPDATE 2
Got it to work....just for those who may have had the same issue. After switching to CWM, sideload did not work. I placed the ROM on an external SD and flashed it as usual and this time it worked (it did not on TWRP for some reason).
Click to expand...
Click to collapse
in update 2 how did you flash??
@SidDev said:
in update 2 how did you flash??
Click to expand...
Click to collapse
you will have to download CWM ...put it on your computer in your adb folder....put your phone into fastboot then on your computer you have to fastboot flash recovery (and then the name of the CWM version) and that is it. Now you have CWM ...
oh ok
ghilliek9 said:
you will have to download CWM ...put it on your computer in your adb folder....put your phone into fastboot then on your computer you have to fastboot flash recovery (and then the name of the CWM version) and that is it. Now you have CWM ...
Click to expand...
Click to collapse
I was trying to gain knowledge,
BTW I have moto e with twrp
---------- Post added at 10:42 AM ---------- Previous post was at 10:37 AM ----------
ghilliek9 said:
you will have to download CWM ...put it on your computer in your adb folder....put your phone into fastboot then on your computer you have to fastboot flash recovery (and then the name of the CWM version) and that is it. Now you have CWM ...
Click to expand...
Click to collapse
I was trying to gain knowledge,
BTW I have moto e with twrp

[Q] Stuck @ recovery, reinstalled Skyrocket ADB Drivers still not recognized by PC

Spent 2-3 hours doing the basic troubleshooting in the stickied thread (and checking related threads) before creating this thread.
Currently stuck at recovery, tried installing sultan XDA's CyanogenMod 12 Lollipop ROM wiping data/dalvik/system after having SlimBeam 4.4
Now my phone has Cyanogen Recovery (previously had CWM but I guess CM 12 overwrote it?) and I can't get it to boot into any of the ROMs I have downloaded (PA 5.01 Beta, SlimBeam 4.4.4) and can't use ADB to flash what's on my computer because USB isn't recognized, which I guess is the big problem.
I can still get to ODIN mode, but Odin 1..85 ALSO doesn't recognize my phone. The interesting difference is in CM Recovery, my PC sees the usb device as SGH-I727 but as an unknown device (running an adb sideload command gives 'device not found'), and then in Odin mode my PC sees it as Unknown Device, and yep doesn't show up in Odin.
another interesting note is that CM Recovery finishes the loading bar for applying the Slimebean 4.4.4 update, but then I'm still stuck at recovery. No obvious error message either.
If there's any more information I can provide let me know. Thanks!
Sultan's ROMs come with a custom kernel which may not be compatible with the other ROM's your trying to flash.
If I were you. I would try to install the latest TWRP recovery and try flashing Sultans cm12 again.
cssr said:
Sultan's ROMs come with a custom kernel which may not be compatible with the other ROM's your trying to flash.
If I were you. I would try to install the latest TWRP recovery and try flashing Sultans cm12 again.
Click to expand...
Click to collapse
Ah okay, thanks Zachary! I guess the big issue right now is I'd have to install twrp over ADB/Odin, and my phone isn't recognized even after switching ports/cords
To follow up, the "SAMSUNG Mobile USB CDC Composite Device" and "SAMSUNG Mobile USB Modem" drivers are successfully installed after booting into odin mode, but not recovery mode. Which is weird. Can I use ADB.exe while in Odin mode? Or just in recovery mode?
If you can get a flashable zip on your phone you can do it in recovery and not through Odin.
I think the start of your problem was your recovery was not compatible with a lollipop.
---------- Post added at 10:53 AM ---------- Previous post was at 10:28 AM ----------
I assume when you say Odin mode you mean download mode if you can get into download mode you can install a tar file of twrp recovery
cssr said:
If you can get a flashable zip on your phone you can do it in recovery and not through Odin.
I think the start of your problem was your recovery was not compatible with a lollipop.
---------- Post added at 10:53 AM ---------- Previous post was at 10:28 AM ----------
I assume when you say Odin mode you mean download mode if you can get into download mode you can install a tar file of twrp recovery
Click to expand...
Click to collapse
Yep meant download mode sorry for the confusion. TWRP 2.8.4 is running! Thanks for all your help. To make sure I don't mess this up, I'm going to wipe data, cache, dalvik, and system folders. Then install the cm-12-20150109-Sultan-skyrocket, Sultan-kernel-v1.6.2B-Skyrocket-Lollipop, and pa_gapps-modular-micro-5.0.1-BETA12-20150116-signed zips? Pretty silly question but I want to be sure I'm not missing anything.
That sounds like a good plan hope it works out for you
cssr said:
That sounds like a good plan hope it works out for you
Click to expand...
Click to collapse
Working!! Always feels stupid in hindsight for making a post when everything works out so straightforwardly. Maybe just needed a bit of "rubber duck debugging". I still have NO IDEA where the Cyanogen Recovery came from.
Again, thanks for the help!
FIX: Used multiple USB cords/ports to eventually get download mode working, flashed SGH-I727-UCKJ2-k0nane followed by newest TWRP. After which installed cm-12-20150109-Sultan-skyrocket, Sultan-kernel-v1.6.2B-Skyrocket-Lollipop, and pa_gapps-modular-micro-5.0.1-BETA12-20150116-signed zips
Good glad you got it done.

How To Fix TWRP Bootloop

After attempting root on my replacement phone, I could NOT boot to system. Each time I rebooted to "System", it would boot straight to TWRP over and over. I tried reflashing stock files. No verity patching.. etc.
The Fix:
Download the latest version of TWRP specific to your device here https://build.nethunter.com/test-builds/twrp/lge/
Flash the file and the device should now be able to boot to system. If that doesn't work try another version.
I spoke to @jcadduono about my problems and he believes there may have been something weird going on in the misc partition. Reflashing TWRP will/should fix the problem.
Thanks @jcadduono for all the support.
I had this happen to me after installing TWRP for the first time. It would keep rebooting to TWRP. This was after making sure I flashed SuperSU as well. Eventually in a moment of "might as well see what will happen" I rebooted then held down the power button and volume down. Got to the option if I wanted to factory reset my phone which I did which booted into TWRP. Rebooted to system from there which got me out of the TWRP Bootloop.
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Mrsana said:
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Click to expand...
Click to collapse
Download the deodex rom flash it, then flash no_verity , then format data.
Mastajeff said:
Download the deodex rom flash it, then flash no_verity , then format data.
Click to expand...
Click to collapse
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
frenize said:
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
Click to expand...
Click to collapse
Turn off your phone. Go into TWRP *manually*. That is, press the power off and volume down buttons. Once you see the LG logo, quickly release the power button and press it again. It will ask if you want to do a factory reset. Say "Yes" to both.
Once inside TWRP (*manually*), do a factory reset. You will be rebooted and it will go back to TWRP. Once inside TWRP after the reboot, go to reboot and choose "System". You should know be out of the TWRP bootloop!
It worked for me.
frenize said:
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
Click to expand...
Click to collapse
Decrypt data.
As a general statement : Almost all TWRP bootloops are due to users not backing up their data, and then formatting data.
Hardware encryption is not supported.
Decrypt your data, flash a ROM, and if that ROM doesn't have SuperSU, flash SuperSU.
Go flash my v5 MOD ROM.
Decrypt your data! 95% of TWRP loop cases are due to data not being decrypted, or some other step the user failed to follow.
Good luck.
---------- Post added at 04:28 PM ---------- Previous post was at 04:28 PM ----------
Mrsana said:
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Click to expand...
Click to collapse
This is because you went to Advanced Wipe, and formatted /system.
Make sure you are on the latest TWRP, make sure you're data is decrypted, and then go flash my v5 MOD ROM.
For those that are still having troubles. My guide works: forum.xda-developers.com/v20/how-to/how-fixed-bricked-lg-v20-t3501310
Mastajeff said:
After attempting root on my replacement phone, I could NOT boot to system. Each time I rebooted to "System", it would boot straight to TWRP over and over. I tried reflashing stock files. No verity patching.. etc.
The Fix:
Download the latest version of TWRP specific to your device here https://build.nethunter.com/test-builds/twrp/lge/
Flash the file and the device should now be able to boot to system. If that doesn't work try another version.
I spoke to @jcadduono about my problems and he believes there may have been something weird going on in the misc partition. Reflashing TWRP will/should fix the problem.
Thanks @jcadduono for all the support.
Click to expand...
Click to collapse
is it possible that the phone bootloops without doing anything like root and custom roms?
asking cz i'm looking to get the LG V20 but don't know about the risk of it bootlooping itself, without rooting or anything like that, like it used
to happen on lg g4 and g3.
Thank you
It's been determined that it does this when it finds an update in the fota and or misc folders. The phone downloads updates even when you tell it not to. It just doesn't install them without your permission.
Easy to get out of with the volume down and power button reset procedure which then deletes the files automatically or you can delete the files in twrp to fix it.
Poda_jj said:
is it possible that the phone bootloops without doing anything like root and custom roms?
asking cz i'm looking to get the LG V20 but don't know about the risk of it bootlooping itself, without rooting or anything like that, like it used
to happen on lg g4 and g3.
Thank you
Click to expand...
Click to collapse
All the bootloops for the V20 so far are all due to modifications and rooting. There are some roms that work for everyone but just refuses to work on my phone and will just bootloop. I doubt that the cause of the software bootloop is fully known. I've followed directions 100% on working romss and it would bootloop but installed a different version of the same rom and it worked. None of the bootloop "fixes" did anything for me. Fortunately, the rom that I installed is still awesome and works great.
LS997 BTW
I fought with this for many hours yesterday. I tried everything I could find and got nowhere. Finally ended out holding Volume Up while inserting the cable to computer to put the phone in download mode and was able to use the kdz file to stock restore.
bond32 said:
I fought with this for many hours yesterday. I tried everything I could find and got nowhere. Finally ended out holding Volume Up while inserting the cable to computer to put the phone in download mode and was able to use the kdz file to stock restore.
Click to expand...
Click to collapse
my phone is in twrp bootloop as well, mind going into a bit of details as in how you did the kdz restore?
dangercl0se said:
my phone is in twrp bootloop as well, mind going into a bit of details as in how you did the kdz restore?
Click to expand...
Click to collapse
There's a few guides here on how to do a full restore. Make sure you download the things you need according to your model V20 and make sure you have ADB working and current drivers installed.
http://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903/page7
I've used the kdz file before without any problems but it began the process from my home screen. I had no idea how to get it to start if you're in a TWRP loop which is where the "download mode" came in.
With the phone completely off, hold volume up a d plug it in the computer.
That will put it in download mode which is what mine needed.
The other mistake I made, make sure you use a USB 2.0 port, not 3.0. I've always had issues with USB 3.0 drivers not working correctly but 2.0 seems to be good.
My one is fully back to stock on Verizon 13a now and works well, except I think something is taking up space on my internal storage. It shows a max of around 50 gb with used some and 44 gb available. That seems quite low like something isn't right...
twrp boot loops most deffinately happen due to the update package sitting in your misc folder
use twrp to delete the misc directory as well as the fota directory and reboot.
This hasn't happened to me once since i moved to the latest version for my variant, but happens a ton when using the original build that kept dl the update regardless of me telling it to.
This is a common issue with the LG series and boot-loops. They all do this if there is a expected upate in the misc directory. And has been covered many times over the variants and that deleting misc is the only option. Some of us dont have a kdz, or if youve changed your build.prop the kdz wont restore anything since it will see it as a incompatible device.
before rebooting into twrp on a older build make sure you delete the update package if not this will keep happening. once deleted make sure the updater gets frozen so it wont re-download later.
Team DevDigitel said:
twrp boot loops most deffinately happen due to the update package sitting in your misc folder
use twrp to delete the misc directory as well as the fota directory and reboot.
This hasn't happened to me once since i moved to the latest version for my variant, but happens a ton when using the original build that kept dl the update regardless of me telling it to.
This is a common issue with the LG series and boot-loops. They all do this if there is a expected upate in the misc directory. And has been covered many times over the variants and that deleting misc is the only option. Some of us dont have a kdz, or if youve changed your build.prop the kdz wont restore anything since it will see it as a incompatible device.
before rebooting into twrp on a older build make sure you delete the update package if not this will keep happening. once deleted make sure the updater gets frozen so it wont re-download later.
Click to expand...
Click to collapse
Thanks. I suppose deleting those folders isn't possible without root access?
bond32 said:
Thanks. I suppose deleting those folders isn't possible without root access?
Click to expand...
Click to collapse
yeah MISC and FOTA are protected as read only for the user without root.
Mrsana said:
Turn off your phone. Go into TWRP *manually*. That is, press the power off and volume down buttons. Once you see the LG logo, quickly release the power button and press it again. It will ask if you want to do a factory reset. Say "Yes" to both.
Once inside TWRP (*manually*), do a factory reset. You will be rebooted and it will go back to TWRP. Once inside TWRP after the reboot, go to reboot and choose "System". You should know be out of the TWRP bootloop!
It worked for me.
Click to expand...
Click to collapse
Thank you, This Worked for me.
bond32 said:
There's a few guides here on how to do a full restore. Make sure you download the things you need according to your model V20 and make sure you have ADB working and current drivers installed.
http://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903/page7
I've used the kdz file before without any problems but it began the process from my home screen. I had no idea how to get it to start if you're in a TWRP loop which is where the "download mode" came in.
With the phone completely off, hold volume up a d plug it in the computer.
That will put it in download mode which is what mine needed.
The other mistake I made, make sure you use a USB 2.0 port, not 3.0. I've always had issues with USB 3.0 drivers not working correctly but 2.0 seems to be good.
My one is fully back to stock on Verizon 13a now and works well, except I think something is taking up space on my internal storage. It shows a max of around 50 gb with used some and 44 gb available. That seems quite low like something isn't right...
Click to expand...
Click to collapse
did that, phone works, no more root.... i rooted the phone again, flashed SU and encryption zip. STILL GET INTO TWRP LOOP.
dangercl0se said:
did that, phone works, no more root.... i rooted the phone again, flashed SU and encryption zip. STILL GET INTO TWRP LOOP.
Click to expand...
Click to collapse
Did you try the above where you delete the misc and fota folders?

HELP!! Mate 9 Stuck in ERROR MODE After Reset.

Hello all, this is my first post so I apologize if anything isn't right.
I recently flashed my Mate 9 to stock Nougat B19x through a method I found on this site and then decided I wanted root. Bootloader was already unlocked so I flashed TWRP and then tried to flash a couple different root methods that all failed... So I factory reset through TWRP and tried again but they still failed so on the initial boot everything worked except the screen was blank except for the soft keys. I rebooted and the same again so I put it in fastboot and tried to re-install Nougat through the same method that worked before. It went through the whole process seemingly fine and finished with 'Update should start automatically' but then the phone boot into error mode. I've looked through everything I can find here and done everything I can think of myself but nothing has worked. I can boot into to fasboot but nothing else, not even after flashing any recoveries or stock images extracted from UPDATE.app.
Func no is 14 and error no is 1.
It's a MHA-L09 and I really need to fix it as I can't really afford anything else right now. Any help would be really appreciated and I'm happy to add more info if I've missed anything.
Thanks guys!!!
BUMP
Sorry if it's not very concise, just really need help!
What commands are you using to flash the stock files?
CandyFoxJ said:
What commands are you using to flash the stock files?
Click to expand...
Click to collapse
Standard fastboot flash recovery/system/boot
Not sure if I'm flashing all the right files or if huawei needs different commands.
Follow this guide.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Thanks for your help. That's the one that I used in the first place but everytime I try again, TWRP either doesn't flash even though it says success or I can't get into recovery.
Everytime I try to access recovery using the hardware keys it boots to error mode so is there another way??
I've been looking into this some more and have found it could be a motherboard issue. Is this correct? And if so how much would that kind of repair cost and would it even be possible considering I've unlocked the bootloader?
Thanks again.

cube power m3 tablet TWRP img

Caution!
i have no responsibility if your device bricked
What i read
https://www.techora.net/port-twrp-for-mediatek-64-bit-mt67xx.html
TWRP img based on
https://forum.xda-developers.com/coolpad-note-3/development/note3-t3572794
tools
SPFlash Tool https://spflashtool.com/
Android scatter file and twrp.img
https://goo.gl/CAij4G
1. Download flash tool, scatter file and twrp.img. place them in same folder
2. Load scatter on flashtool and choose recovery. *download only
3. turn off your tablet and connect to pc
4. will be install
I make this img with linked tutorial, and coolpad img file
Choose it cause same cpu model
to install some zips from twrp you need SD card
i dont know why it doesnt read internal storage, adb sideload
Magisk install worked and module looks fine
Didn't try Xposed
I'm not dev
i just one who knows a bit how device work
(with lot bricked devices in my storage)
Might can't answer your questions
I'm not used to on xda forum, so i don't know where to post unlisted device things
https://drive.google.com/open?id=0Bzm7uALjk4svNG0tVjhHSkJFUUZwYW0yQkh6Yk0tTE95djRj
https://drive.google.com/open?id=0Bzm7uALjk4svOURqaUt1ZE9pM0lxS25IQ2NNNTBERGRTVFBn
https://drive.google.com/open?id=0Bzm7uALjk4svOTZ5bWRETmVWaUhDYWJzUV9UTHI5dWpVZy1z
and unlock OEM bootloader with dev option
My Cube Power M3 is now rooted with your twrp file. I just had to use my original scatter file because it didn't worked with yours.
Thank you
... my mistake ... all your files are ok
Good work
mrtee03 said:
... my mistake ... all your files are ok
Good work
Click to expand...
Click to collapse
sometimes work, sometimes not
when try to flash all, or use original boot.img for loading scatter and change it will work
i might have to upload original one later
You're right, that's what I did
chocodesk said:
sometimes work, sometimes not
when try to flash all, or use original boot.img for loading scatter and change it will work
i might have to upload original one later
Click to expand...
Click to collapse
Add some files and flash guide
New link is here
https://goo.gl/CAij4G
It was first time to share my files so i forgot to change link option as public
Sorry for that guys
thank you
Hi guys, I need some help.
I just flashed the TWRP included in Google Drive, everything went fine, the flashing was successful.
I then booted to recovery, TWRP Recovery was installed, I swiped to allow partition modification as asked.
Then I rebooted and was stuck on the Alldocube logo for several minutes.
I tried flashing the original recovery you included back again and same problem, I'm stuck on boot logo :/
Any idea how to deal with this ?
---------- Post added at 11:50 AM ---------- Previous post was at 11:44 AM ----------
I've just tried Wiping Cache and Data / Factory Reset from original Recovery, but still stuck :/
OK guys, I flashed the whole original firmware back in and it's solved the problem.
I guess no TWRP recovery for me :/
PiNgOa said:
OK guys, I flashed the whole original firmware back in and it's solved the problem.
I guess no TWRP recovery for me :/
Click to expand...
Click to collapse
i had same problem and solved with twrp availiable,
but i refund this tablet long ago
i dont remember
sorry for i cant help
worked perfectly to get TWRP, Magisk 16.4 on device running Stock ROM - thank's !
edit
PiNgOa said:
OK guys, I flashed the whole original firmware back in and it's solved the problem.
I guess no TWRP recovery for me :/
Click to expand...
Click to collapse
i think you should flash magsik via twrp
remove system verify
anybody knows how to get lineage 17.1, magisk and twrp on ALLDOCUBE X1 ?

Categories

Resources