Related
Hi!
I have a A2107G and unlocked it, coming from B04.
Everything worked so far, but I have messed around with bootstack/modem and now I am struggling.
I flashed a new ROM with TWRP (different versions) and the ROM (doesn't matter which one) is stuck in booting animation.
What can I do to bring it back to life?
Also another question: After switching on, directly after the ZTE logo coming up, a black sceen with some infos coming up and stay there for 5 secs.
Is there a way to get rid of this
Sui77 said:
Hi!
I have a A2107G and unlocked it, coming from B04.
Everything worked so far, but I have messed around with bootstack/modem and now I am struggling.
I flashed a new ROM with TWRP (different versions) and the ROM (doesn't matter which one) is stuck in booting animation.
What can I do to bring it back to life?
Also another question: After switching on, directly after the ZTE logo coming up, a black sceen with some infos coming up and stay there for 5 secs.
Is there a way to get rid of this
Click to expand...
Click to collapse
Do you have twrp? If yes, flash stock rom.
WesTD said:
Do you have twrp? If yes, flash stock rom.
Click to expand...
Click to collapse
Yes, I have TWRP.
So i should flash a stock image and start over from scratch (with rooting, ...)
Is the posted screen normal?
Sui77 said:
Yes, I have TWRP.
So i should flash a stock image and start over from scratch (with rooting, ...)
Is the posted screen normal?
Click to expand...
Click to collapse
Yes it is normal. It means you've unlocked bootloader.
Flash stock rom zip. There are some guides.
WesTD said:
Yes it is normal. It means you've unlocked bootloader.
Flash stock rom zip. There are some guides.
Click to expand...
Click to collapse
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?
Sui77 said:
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?
Click to expand...
Click to collapse
I use aosp bases.
Sui77 said:
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?
Click to expand...
Click to collapse
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.
Choose an username... said:
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.
Click to expand...
Click to collapse
Hi!
Thanks for your help and the time you spent on my problem.
I have tried all that stuff already, but maybe not in exact that order. Will try it this evening.
In case i will be able to bring it back to life, I have 2 questions, pls:
1: You mentioned the 5sec-screen and a zip to get rid of it.
Where could I find it (not seen yet) and how do i get into fastboot, when I skip this screen?
2: When I setted up my Axon with a Custom Rom and SU and everything was working as it should do, I was not able to write to /system (or deleting something in system/apps)
How do I get rid of this restriction? I think I have found an instruction once, but I failed and afterwards my device was stuck in animation.
orry for bothering, but the Axon really drive me nuts. Never had such a hassle with my Nexus
Sui77 said:
Hi!
Thanks for your help and the time you spent on my problem.
I have tried all that stuff already, but maybe not in exact that order. Will try it this evening.
In case i will be able to bring it back to life, I have 2 questions, pls:
1: You mentioned the 5sec-screen and a zip to get rid of it.
Where could I find it (not seen yet) and how do i get into fastboot, when I skip this screen?
2: When I setted up my Axon with a Custom Rom and SU and everything was working as it should do, I was not able to write to /system (or deleting something in system/apps)
How do I get rid of this restriction? I think I have found an instruction once, but I failed and afterwards my device was stuck in animation.
orry for bothering, but the Axon really drive me nuts. Never had such a hassle with my Nexus
Click to expand...
Click to collapse
Which file manager you are using?
I'm using Root Explorer and no problem. Be sure you allow to root permission
WesTD said:
Which file manager you are using?
I'm using Root Explorer and no problem. Be sure you allow to root permission
Click to expand...
Click to collapse
Also Root Explorer, root granted.
Sui77 said:
Also Root Explorer, root granted.
Click to expand...
Click to collapse
Can you just leave the 5 sec screen alone? You can kill your phone, and there doesn't seem to be anything you can do really.
If you're insistent, you can find it under Themes Apps and Mods, called "We remove the inscription that the bootloader is unlocked" made by NFound1.
And about the restriction to modify the system, connect your phone to a PC with ADB, fire up ADB and configure it (USB debugging, ADB over network if you have the option, permit the connection) and issue 'adb reboot disemmcwp' (disable emmc write protection, that is. Write it just like that or your phone will reboot and you will still have the protection active).
The phone has its difficulties and all but it's easy to work with once you get the hang of it. And, you know, your big cores don't just die all of a sudden, which is a good thing!
Choose an username... said:
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.
Click to expand...
Click to collapse
Tried exactly the steps you descriped, but no luck ---- still stuck in animation
Will try it tomorrow with Magist.
How can I go back to total stock.
Tried anything I found on xda, but no luck.
When I flash the ZTE B05 zip, I don't even get the boot animation.
Sui77 said:
Tried exactly the steps you descriped, but no luck ---- still stuck in animation
Will try it tomorrow with Magist.
How can I go back to total stock.
Tried anything I found on xda, but no luck.
When I flash the ZTE B05 zip, I don't even get the boot animation.
Click to expand...
Click to collapse
How do you flash the B05 zip? Did you try to flash the official zip?? lol
Follow my guide on the Guides section ("back to stock safely" or sth), it works...
Choose an username... said:
How do you flash the B05 zip? Did you try to flash the official zip?? lol
Follow my guide on the Guides section ("back to stock safely" or sth), it works...
Click to expand...
Click to collapse
I tired to flash a B5 an B5 bootstack with TWRP 3.1.1 -> not able to boot
Then i flashed, according to your guide, the stock recovery and now the device seems to be really bricked.
After the ZTE logo a lying robot appears for half a second and after that, the device is dead.
Can't boot into TWRP, can't use adb, EDL, ...
Ok, managed to get back TWRP.
But I really don't know how so solve my issue of how to come back to stock :crying:
Flashed a B05 stock (zip) and B05 bootstack and Magist....stuck in boot animation (AXON picture collage).
Fu....
Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM
Sui77 said:
Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM
Click to expand...
Click to collapse
to go back to stock, download the full zip of any version you want, and download stock recvovery from b08, you have flashed it.
from twrp, format data, and try to boot, if you cannot, reflash b09 recovery from twrp, select image and the recovery you download, then go to stock recovery and update from sdcard. it allways work for me, if you stuck in boot animation again, reboot recovery and wipe data.
after you succesfully boot, reboot edl, and reflash twrp, the version you were using before witn axon7tool, thats all
Sui77 said:
Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM
Click to expand...
Click to collapse
Just follow my guide for that. If you flash the B04 recovery (the one i provided) you shouldn't have any trouble
Managed to flash the B05 and phone is up and running.
Made a backup by using TWRP 3.1.1.0 and flashed CarbonRom, which also worked nicely.
However, I'm not able to flash LOS by using the B05 bootstack.
I'm too dumb for this phone
Sui77 said:
Managed to flash the B05 and phone is up and running.
Made a backup by using TWRP 3.1.1.0 and flashed CarbonRom, which also worked nicely.
However, I'm not able to flash LOS by using the B05 bootstack.
I'm too dumb for this phone
Click to expand...
Click to collapse
What B05 bootstack? You have to use the universal bootstack and the A2017G modem file...
Both are on the LOS thread. It seems weird that carbonROM would even boot without the universal bootstack though
Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:
Pobi123 said:
Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:
Click to expand...
Click to collapse
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?
BlueCyclone said:
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?
Click to expand...
Click to collapse
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping
Pobi123 said:
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping
Click to expand...
Click to collapse
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.
BlueCyclone said:
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.
Click to expand...
Click to collapse
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!
Pobi123 said:
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!
Click to expand...
Click to collapse
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again
BlueCyclone said:
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again
Click to expand...
Click to collapse
Good News! Phone is back in full working order after flashing stock firmware. It was kinda scary though, I had to fix an error in Odin and then the phone wouldn't even boot up! Left it over night, booted it again and it worked fine Thanks a lot for your help, I'll try not to soft brick my device again
Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance
CptUnicorns said:
Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance
Click to expand...
Click to collapse
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear
Striatum_bdr said:
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear
Click to expand...
Click to collapse
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2
CptUnicorns said:
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2
Click to expand...
Click to collapse
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM
Striatum_bdr said:
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM
Click to expand...
Click to collapse
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.
CptUnicorns said:
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.
Click to expand...
Click to collapse
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.
OhioYJ said:
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.
Click to expand...
Click to collapse
That does clear up things for me, I've either mis-read or not read that when on slot A you are actually flashing slot B and Visa versa.
I'll be flashing both my slots to 10.3.1 just so they're fully updated. ( A is my main)
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?
CptUnicorns said:
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?
Click to expand...
Click to collapse
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Great stuff. Thought I understood from how you explained it. I'll check that guide as well and have it to hand just incase.
OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Something didnt want to play when I was flashing... Got to flashing gapps and magisk, gapps flash gave me a error 64 and i got magisk installed, booted, now I've got no twrp and when I use fastboot it just softbricks then restarts after about 5 minutes, I'm gonna try booting from 3.2.3-2 as that was fine and hope I can boot into recovery and just go lineage I think for something new
EDIT
So I used fastboot --set-active=a, managed to get back to twrp so now its flashed on both again. In the process of flashing lineage now, hopefully this wont chuck another error at me for gapps
Hello,
I do have some questions about upgrading LOS from 16 to 17, maybe someone can help me bringing a little light into this upgrading process.
- Is the sideload way the correct way to do this? ( https:// wiki.lineageos.org /devices /fajita /upgrade)
- What´s about the play services, I dont have any installed ( ..."If you did not have Google Apps installed, you must wipe the Data partition (or perform a factory reset) to install them"...) So if later on I want to install e.g. opengapps I have to wipe all my data after upgrading to 17??? (How? TWRP - wipe -advanced wipe - data and cache ???)
and what´s with all may data? I have titanium backup pro (no SD card), so I backup may phone, put it to my PC, upgrade to 17, wipe all data, put the backup back to phone and reboot?
Or do I have to install Magisk.zip and titanium.zip from within TWRP again first
- What do I do if the sideload fails?
- Can I do the upgrad process with TWRP too? (copying and installing from within TWRP?)
- And what about with the A/B slots, no installing twice on both slots?
As you see, I am unsure on how to do things right and I only did this once before as I installed Lineage OS.
(This would be the way I would do this:
- backup all data to PC
- Boot into TWRP
- copy LOS17.zip. Magisk.zip and Titaniumbackup-pro.zip into internal storage
- install LOS17 and boot into TWRP
- wipe data and cache
- install magisk and TB
- copy all data back and restore? (only user data or the system data too??))
Maybe someone can help me with this. Thanks!
My guide for installing Lineage maybe helpful: Guide Installing Lineage
I would recommend a clean install. Most that have tried to follow that wiki have had issues (if you look in the LOS thread). I haven't used. TB zip, but I did use my TB data from the app without issues. If you dont use Gapps, just dont install them. Skip that step. You still have to reboot to recovery to install Magisk though. I dont think I would try a TB zip until after the first boot.
Installing twice is for the intial install to get the same thing on both slots. You dont want Android 9 on one slot and Android 10 on another, or LOS 17 on one and OOS on another. Once you have LOS 17 on both slots and go to update you will just flash once. See my guide about doing an update.
Thank you for your reply,
so if I got your answer right, I should install the LOS17 like the LOS16 before, as a clean,fresh install.
Seems reasonable to me
I will do the same steps as you gave me before https://forum.xda-developers.com/oneplus-6t/help/instructions-installing-lineage-t3949628
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery
- Factory Reset.
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash Gapps
- Flash Magisk
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
Will do the flash on weekend, then I will let you know....
Thanks.
KKF32 said:
Thank you for your reply,
so if I got your answer right, I should install the LOS17 like the LOS16 before, as a clean,fresh install.
Seems reasonable to me
I will do the same steps as you gave me before https://forum.xda-developers.com/oneplus-6t/help/instructions-installing-lineage-t3949628
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery
- Factory Reset.
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash Gapps
- Flash Magisk
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
Will do the flash on weekend, then I will let you know....
Thanks.
Click to expand...
Click to collapse
How did it go?
badpanda said:
How did it go?
Click to expand...
Click to collapse
To put it short: a disaster
What I did:
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Magisk
- Flash TB
- Reboot to System.
What I got was a "Qualcom Crashdump Mode" kind of report
What I used: lineage-17.1-20200418-nightly-fajita-signed / twrp-installer-3.3.1-1-fajita / Magisk-v20.4
So I thought maybe the "no factory reset" at the beginning may caused this problem, so I started the whole flashing again.
Long story short: Being distracted I once forgt to flash TWRP after the LOS and now I am stuck in fastboot.
Cant get anymore into TWRP, "fastboot boot TWRP.img" always throws me into fastboot forever wait
Tried to flash TWRP direct from fastboot "fastboot flash recovery twrp.img", always get a write error.
So, at the moment all I can get in is the bootloader, and I have no clou how to get TWRP up and running again.
Edit: Managed to get into TWRP again, but this double flash + Magisk always gives me this "Qualcomm Crashdump Mode"
Help would very much appreciated!
KKF32 said:
To put it short: a disaster
What I did:
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Magisk
- Flash TB
- Reboot to System.
What I got was a "Qualcom Crashdump Mode" kind of report
What I used: lineage-17.1-20200418-nightly-fajita-signed / twrp-installer-3.3.1-1-fajita / Magisk-v20.4
Click to expand...
Click to collapse
So you tried to go straight to LOS 17, used an old version of TWRP, and never wiped data while going between Android 9 and 10? None of that will work. I think didn't make it clear, you need you need to be on the OOS 10 firmware first. Flash OOS 10 to both slots, at this point using the fastboot ROM would be my suggestion, like my [Guide]Installing Lineage.
Once you have Android 10 in place one both slots, then start your OS 17 install. Note there is a cliff notes version of that guide in the second post, if you don't want all the "wordy" details.
Oh my, I really didn´t understood the step with "get OOS10 on both slots first"
I am often a little sloppy with details, bad habit, will take some time tomorrow and do the reading and the flashing then.
Thanks again.
KKF32 said:
Oh my, I really didn´t understood the step with "get OOS10 on both slots first"
I am often a little sloppy with details, bad habit, will take some time tomorrow and do the reading and the flashing then.
Thanks again.
Click to expand...
Click to collapse
Make sure you use the"unofficial" version of TWRP, linked to in that guide, rather than the outdated official one you used before as well.
OhioYJ said:
Make sure you use the"unofficial" version of TWRP, linked to in that guide, rather than the outdated official one you used before as well.
Click to expand...
Click to collapse
So, LOS17 is up and running, I did it the long way but good to know the fastboot Rom method now. I confess some part of this thread would not have been necessary if had read your installations instruction carefully....
So let me thank you for patience und help, "Reading broadens the mind", I often tell others, will remind myself nexttime
For the past 24+ hours I've been trying to flash a few custom roms on my UNLOCKED BOOTLOADER OP6T, but the phone TURNS OFF a few seconds after the boot sequence/animation.
I've read about the A/B slots and tried the Roms' flashing instructions, along with a few suggestions from others, but I cannot get any Custom Rom on my phone...
Here are the steps I've taken to flash (a few times I tried different things that I'll put in parenthesis). Is there anything ya'll see that I'm doing wrong?:
Starting from OOS 10.3.2 Fastboot Recovery and all required files on an OTG USB Drive
fastboot to TWRP....img
Confirmed I'm on Slot A
Wipe Data/Dalvik
Install OOS...zip (10.3.2)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
(Format Data)
Confirmed I'm on Slot B
Install OOS...zip (10.3.2)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot A
Install Xtended (v8 4/13)
(Wipe Data/Cache)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot B
Install Xtended (v8 4/13)
(Wipe Data/Cache)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot A
Install GAPPS (Arm64 10.0 Nano)
(Format Data)
Reboot System
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
OhioYJ said:
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
Click to expand...
Click to collapse
Thanks for the comment! I just followed your guide, but still seeing the boot animation for a few seconds, then the phone vibrates and turns off.
For kicks, I decided to Format Data and I see the boot animation longer, all the way to the end when it's about to start Android, but then it vibrates and shuts off. Strange.
I'm thinking there is something different about my phone... It's a global, unlocked version and I've rooted/flashed hundreds of roms over the years on various devices, so all of this should be a piece of cake................. Thanks!
oooscasianooo said:
Thanks for the comment! I just followed your guide, but still seeing the boot animation for a few seconds, then the phone vibrates and turns off.
For kicks, I decided to Format Data and I see the boot animation longer, all the way to the end when it's about to start Android, but then it vibrates and shuts off. Strange.
I'm thinking there is something different about my phone... It's a global, unlocked version and I've rooted/flashed hundreds of roms over the years on various devices, so all of this should be a piece of cake................. Thanks!
Click to expand...
Click to collapse
Have you tried without Gapps?
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
onliner said:
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
Click to expand...
Click to collapse
Thanks. I actually gave up and setup stock OOS again, so it took a while to get a TWRP backup, etc. etc.
So after the backup, I installed Xtended + TWRP, reboot to recovery, installed Xtended + TWRP, wiped dalvik, and reboot to system.
Boot animation shut down issue as usual.
Afterwards, I copied the pstore folder (attached zip).
Thanks!
onliner said:
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
Click to expand...
Click to collapse
Anything in the logs I can look for?
This is driving me crazy. I flashed MIUI just fine (because it had the .bat file that does everything for you). Essentially it's doing the same thing as flashing OOS & Rom on A/B, right?
Just tried flashing the newest Xtended Rom (May 11th), same issue. Phone vibrates and completely turns off while the boot animation is running.
OhioYJ said:
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
Click to expand...
Click to collapse
If you have a TMobile 6t I can confirm I have had to manually change the slots during the flashing process to get custom ROMs installed.
mrmcshagbag said:
If you have a TMobile 6t I can confirm I have had to manually change the slots during the flashing process to get custom ROMs installed.
Click to expand...
Click to collapse
I found out that I do have the T-Mobile version that the seller flashed to International Software haha
When I reboot to recovery, I do see that the slots are being changed though.
Would you mind post the exact steps you took to successfully flash a ROM/GAPPS?
oooscasianooo said:
I found out that I do have the T-Mobile version that the seller flashed to International Software haha
When I reboot to recovery, I do see that the slots are being changed though.
Would you mind post the exact steps you took to successfully flash a ROM/GAPPS?
Click to expand...
Click to collapse
Fastboot boot TWRP Marion version
Flash oos
Flash Marion TWRP zip
Check my slot
Reboot recovery
Changed slot since it didn't change
Reboot recovery
Flash oos
Flash Marion TWRP zip
Changed slot
Reboot recovery
Flash custom rom
Flash Marion TWRP zip
Change slot
Reboot recovery
Flash gapps
Flash magisk 20.4
Reboot to system
Those are the steps I had to take before I finally got a custom rom to work. I tried doing the methods posted which would have probably worked if the slots were changing on there own but they weren't for me.
mrmcshagbag said:
Fastboot boot TWRP Marion version
Flash oos
Flash Marion TWRP zip
Check my slot
Reboot recovery
Changed slot since it didn't change
Reboot recovery
Flash oos
Flash Marion TWRP zip
Changed slot
Reboot recovery
Flash custom rom
Flash Marion TWRP zip
Change slot
Reboot recovery
Flash gapps
Flash magisk 20.4
Reboot to system
Those are the steps I had to take before I finally got a custom rom to work. I tried doing the methods posted which would have probably worked if the slots were changing on there own but they weren't for me.
Click to expand...
Click to collapse
Thanks! Do you mean the "mauronofrio" version?
oooscasianooo said:
Thanks! Do you mean the "mauronofrio" version?
Click to expand...
Click to collapse
Yes couldn't remember the exact name but I knew you would be able to find it haha
mrmcshagbag said:
Yes couldn't remember the exact name but I knew you would be able to find it haha
Click to expand...
Click to collapse
hahaha thanks! I was thinking, "is there a T-Mobile version of TWRP?!" haha!