Related
Can you use flash fire to flash a international rom on the g930t.
kevin527 said:
Can you use flash fire to flash a international rom on the g930t.
Click to expand...
Click to collapse
Hi
Well is a good question , Chainfire said:
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
FlashFire is the most advanced on-device firmware flasher available for rooted Android devices. It can flash full firmware packages from various manufacturers, as well as apply over-the-air (OTA) and ZIP updates - all while maintaining root, and without using a custom recovery.
So in theory you can, but he also said:
https://flashfire.chainfire.eu/
Unlocked bootloader
While an unlocked bootloader is not strictly necessary for many of FlashFire's functionalities, we strongly recommend all root users to run unlocked if possible. With locked bootloaders, there is a much higher chance of a device being unrecoverable if something goes wrong. This is not just true for FlashFire, but for many root apps. The specifics are device dependent.
nevertheless , here in this thread they seem to have used and work
http://forum.xda-developers.com/tmo...-available-t3414146/post67699508#post67699508
I'll test it out and report back.
kevin527 said:
I'll test it out and report back.
Click to expand...
Click to collapse
Please do mate.
good luck.
kevin527 said:
Can you use flash fire to flash a international rom on the g930t.
Click to expand...
Click to collapse
Are you sure you want to flash an exynos rom onto a snapdragon phone?
Hello, i have a big doubt about unlock my Mate 9.
I have read some guides but i'am confused, i will not lose the warranty and i see that with software dc-unlocker is possible relock the bootloader at original status, it is right? there are other softwares that do same job?
Sorry for my bad english.
thanks for help
Khris00 said:
Hello, i have a big doubt about unlock my Mate 9.
I have read some guides but i'am confused, i will not lose the warranty and i see that with software dc-unlocker is possible relock the bootloader at original status, it is right? there are other softwares that do same job?
Sorry for my bad english.
thanks for help
Click to expand...
Click to collapse
There's a difference between lock and relock.
Relock will say 're-locked' in the bootloader, and that's probably voiding warranty.
You can get it to say 'locked' by flashing official firmware, you have a few options here...
1. Firmware Finder
2. Flash update guide
3. Dload method (only for C636B136 and AL00C00B115)
4. FunkyHuawei (paid)
5. Dc unlocked (i think anyway, and paid)
ante0 said:
There's a difference between lock and relock.
Relock will say 're-locked' in the bootloader, and that's probably voiding warranty.
You can get it to say 'locked' by flashing official firmware, you have a few options here...
1. Firmware Finder
2. Flash update guide
3. Dload method (only for C636B136 and AL00C00B115)
4. FunkyHuawei (paid)
5. Dc unlocked (i think anyway, and paid)
Click to expand...
Click to collapse
thanks for answer
So is possible change the status just flashing the stock firmware? is so simple?
i need to do then unlock bootloader>>install modded recovery>>flash modded rom. For return to the stock firmware and bootloader locked what i need to do? i flash the stock firmaware but the twrp remain?
thanks
Khris00 said:
thanks for answer
So is possible change the status just flashing the stock firmware? is so simple?
i need to do then unlock bootloader>>install modded recovery>>flash modded rom. For return to the stock firmware and bootloader locked what i need to do? i flash the stock firmaware but the twrp remain?
thanks
Click to expand...
Click to collapse
No. When you flash stock firmware everything is back to stock. If there was a way to flash a modified update.zip with Twrp as recovery instead of stock recovery it would be possible. But as far as I know we can't yet. I've tried to repack using Huawei Update extractor but it doesn't want to, header mismatch. (this is on all extracted files, not just twrp)
The only reason to get locked bootloader would be if you needed to return the phone because of a software error. If it's hardware it should be replaced anyway.
ante0 said:
There's a difference between lock and relock.
Relock will say 're-locked' in the bootloader, and that's probably voiding warranty.
You can get it to say 'locked' by flashing official firmware, you have a few options here...
1. Firmware Finder
2. Flash update guide
3. Dload method (only for C636B136 and AL00C00B115)
4. FunkyHuawei (paid)
5. Dc unlocked (i think anyway, and paid)
Click to expand...
Click to collapse
ante0 said:
No. When you flash stock firmware everything is back to stock. If there was a way to flash a modified update.zip with Twrp as recovery instead of stock recovery it would be possible. But as far as I know we can't yet. I've tried to repack using Huawei Update extractor but it doesn't want to, header mismatch. (this is on all extracted files, not just twrp)
The only reason to get locked bootloader would be if you needed to return the phone because of a software error. If it's hardware it should be replaced anyway.
Click to expand...
Click to collapse
thanks for help Ante and sorry for my newbie questions, i will just flash one mod rom instead a stock i have now(B182) because i don't like emui, but if is possible when i'll go to sell i can back to stock condition and warranty Ok, i can do that?
thanks
Khris00 said:
thanks for help Ante and sorry for my newbie questions, i will just flash one mod rom instead a stock i have now(B182) because i don't like emui, but if is possible when i'll go to sell i can back to stock condition and warranty Ok, i can do that?
thanks
Click to expand...
Click to collapse
Yep. Flashing stock firmware will do that.
You won't get rid of emui though. We don't have AOSP so emui is always there...
ante0 said:
Yep. Flashing stock firmware will do that.
You won't get rid of emui though. We don't have AOSP so emui is always there...
Click to expand...
Click to collapse
you mean all modded roms are emui based?
Khris00 said:
you mean all modded roms are emui based?
Click to expand...
Click to collapse
Yes.
And there are only 2. RomAur and Ephemeral
ante0 said:
Yep. Flashing stock firmware will do that.
You won't get rid of emui though. We don't have AOSP so emui is always there...
Click to expand...
Click to collapse
ante0 said:
Yes.
And there are only 2. RomAur and Ephemeral
Click to expand...
Click to collapse
thanks again
ante0 said:
There's a difference between lock and relock.
Relock will say 're-locked' in the bootloader, and that's probably voiding warranty.
You can get it to say 'locked' by flashing official firmware, you have a few options here...
1. Firmware Finder
2. Flash update guide
3. Dload method (only for C636B136 and AL00C00B115)
4. FunkyHuawei (paid)
5. Dc unlocked (i think anyway, and paid)
Click to expand...
Click to collapse
sorry for my bad thing. But can i ask you help me this case:
i have Mate 9 Pro LON-L29C636C361 (lastest Oreo ) , but my bootloader is unlocked, and maybe not have stock recovery .
So, which method can flash again full rom C361 (3 file : update.zip, data full, hw...etc) and complete back to stock with locked bootloader???
I read somewhere about method LON-HWOTA, but it fail when flash TWRP step, because i am on Oero, so this method can not use in this my case . Can you show me another way ?
to relock bootloader on Android 8 (MUI8), only works if you have your CORRECT oeminfo.bin. make sure you backup yours before rebranding
1. just flash TWRP
2. make folder folder HWOTA8 on SD card
3. Download HWOTA8 and copy "hwota8_rebrand" to SDcard
4. Copy your oeminfo.bin file to HWOTA8 folder.. Make sure to rename your file to oeminfo.bin
5. Boot into TWRP and install from SDcard hwota8_rebrand
Done bootloader relocked
hi guys i'm brasilian and my english is pretty poor but lets try. i was flash 4.4.4 rom br retail. and i update via ota for lollipop.. and brick .. i search in forums here ... and i go it to put in boot loader without robot.. already try many ways to recovery my boot loader but always get error remote failure.. and already used 6.0.1 stock .. maybe i need to files atualy for this? i'm very sad my maxx is dead .. someone give me light .. help me fix this ... thank you guys
Is your bootloader locked or unlocked?
ChazzMatt said:
Is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked
kenedi jr said:
unlocked
Click to expand...
Click to collapse
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
ChazzMatt said:
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
Click to expand...
Click to collapse
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
kenedi jr said:
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
Click to expand...
Click to collapse
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
So I'm stuck on the bootloader. If I connect charger or pc it will already pro boot loader without the robot. I have already tried to pass stock 4.4.4 and 6.0 and more etc always from the failure remote failure in bootloader appears in the log something with gt bin downgrade
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
kenedi jr said:
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
Click to expand...
Click to collapse
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
I do not have twrp backup and I can not even install the recovery stock
kenedi jr said:
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
Click to expand...
Click to collapse
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that version to repair. Just reflash the entire full firmware.
Click to expand...
Click to collapse
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
thanks bro you saved me
kenedi jr said:
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
Click to expand...
Click to collapse
You can not flash any older gpt.bin files. You have to omit (leave out) that flash command.
Your gpt.bin file is 6.0.1, and you cannot downgrade. Even on 4.4.4, trying to accept the 5.0.2 OTA update is still older gpt.bin file in that OTA than your 6.0.1.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
i don't have link .. i will wanting you so
kenedi jr said:
i don't have link .. i will wanting you so
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=72846593
ChazzMatt said:
https://forum.xda-developers.com/showthread.php?p=72846593
Click to expand...
Click to collapse
I was a bit confused with this link which is the last one? I discovered because I am Brazilian and my English was developed only by playing
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
ChazzMatt said:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Face first you're a myth. I just passed gpt.bin and got the bootloader ... I'm very happy. Do I need to pass the entire rom ??
:good::laugh:
So I have a few questions about the android P beta program. I was wondering if anyone could answer before I opt into it
1) if I opt into I get ota updates which won't be Verizon variants so would I be able to jump back to Oreo?
2)would this allow me to unlock my bootloader possibly?
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Thanks so much for this information I'm gonna opt in for the hell of it
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
daede86 said:
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
Click to expand...
Click to collapse
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
dbrohrer said:
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
Click to expand...
Click to collapse
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
daede86 said:
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
Click to expand...
Click to collapse
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
dbrohrer said:
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
Click to expand...
Click to collapse
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
daede86 said:
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
Click to expand...
Click to collapse
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
dbrohrer said:
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
Click to expand...
Click to collapse
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
daede86 said:
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
Click to expand...
Click to collapse
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
dbrohrer said:
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
Click to expand...
Click to collapse
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
daede86 said:
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
Click to expand...
Click to collapse
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
dbrohrer said:
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
Click to expand...
Click to collapse
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
daede86 said:
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
Click to expand...
Click to collapse
I understand that. I am not sure whats going on then. Sorry.
i've solved the problem!! just to share, i had installed handbrake in my mac to share files via usb and i guess it caused some incompatibility issue.. i've just uninstalled it and i've managed to flash it properly!
So, i have s7 G930F which has bootloader version 4. I'm thinking about flashing some custom roms, but i'm not sure if i should flash older bootloader and modem via twrp.. Is this safe via twrp? Will i brick my device? I'll surely brick it if i flash older bootloader via odin, but what happens with twrp? Thanks in advance.
Dux25 said:
So, i have s7 G930F which has bootloader version 4. I'm thinking about flashing some custom roms, but i'm not sure if i should flash older bootloader and modem via twrp.. Is this safe via twrp? Will i brick my device? I'll surely brick it if i flash older bootloader via odin, but what happens with twrp? Thanks in advance.
Click to expand...
Click to collapse
It is very difficult to downgrade the bootloader and methods which worked in the past have been patched. If you don't know what you're doing leave it alone.
And to answer your question no, you can't just flash an old bl in TWRP and expect a rom to just "work". Your better off installing a custom rom with the version of android you want. Then you don't have to mess about with bootloaders.
cooltt said:
It is very difficult to downgrade the bootloader and methods which worked in the past have been patched. If you don't know what you're doing leave it alone.
And to answer your question no, you can't just flash an old bl in TWRP and expect a rom to just "work". Your better off installing a custom rom with the version of android you want. Then you don't have to mess about with bootloaders.
Click to expand...
Click to collapse
Good to know, thanks dude! So looks like nougat is our best choice in terms of battery life..