Related
I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Beast84 said:
I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Click to expand...
Click to collapse
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
PrizmaticSmoke said:
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
Click to expand...
Click to collapse
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Bumping to see if anyone else can help...
Beast84 said:
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Click to expand...
Click to collapse
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Paramesh96 said:
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Click to expand...
Click to collapse
Ok so that worked to flash cm but will this continue to happen if I try flashing the official lollipop update? I'm trying to return to stock so I can give the tablet to my nephew. I don't want him jumping into recovery or bootloader & wrecking it for good
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
Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Thunderjew said:
Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Click to expand...
Click to collapse
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
kekistaneerefugee said:
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
Click to expand...
Click to collapse
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Thunderjew said:
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Click to expand...
Click to collapse
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
kekistaneerefugee said:
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
Click to expand...
Click to collapse
Thank you very much for helping understand this. I will give it another go at some point, hoping I'll get it to work then. Thanks again.
Hello guys,
sorry for archeology but I got exaclty just the same problem.
Yesterday I decided to flash 34.3.A252 onto my XC. SO the soft itself works fine - later I decided to flash newest twrp for Kugo, 3.2.3-0.
So exactly as Thunderjew has said - after I enter TWRP once I got stuck on Sony logo.
So whats the right order of things here?
I flash stock rom -> then I flash kernel -> and then TWRP?
What about the Encryption - should I apply any? I'd very much like to have my device encrypted. Is it even possible?
But - anyone knows wher I can find working Kernel file for this firmware? Or which version from ggow would work?
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
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
auxillium said:
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
Click to expand...
Click to collapse
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
marvelljones said:
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
Click to expand...
Click to collapse
What do you mean by "hitting the power button and continue to boot"? When I hit the power button on the "Decryption unsuccessful" screen it just locks and unlocks like normal, but stays there.
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
auxillium said:
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
Click to expand...
Click to collapse
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
marvelljones said:
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
Click to expand...
Click to collapse
Will this allow me to install magisk without a factory reset?
auxillium said:
Will this allow me to install magisk without a factory reset?
Click to expand...
Click to collapse
I didn't have to, but I can't guarantee it will work for you. I had previously factory reset my phone but at the time I sideloaded Magisk I had been using the phone for at least a week. Just make a backup of everything first to be safe. *edit* I am using the beta version of Magisk (16.4), not sure if that's making a difference.