I recently picked up a Chinese variant (STF-AL10) Honor 9 and wen through the process of unlocking the bootloader, rooting and re-branding to the European variant (STF-L09). All good. Was able to flash the latest ROM (STF-L09C432B378) using HURUpdater. All good except the 2 capacitive keys not working. Saw that there was a potential fix with an updated Kernel for build 366. So.... I tried flashing STF-L09C432B366 with HURUpdater. The flash appeared to be successful (no error messages except for the a couple that are expected apparently). But the phone was dead right after I tried rebooting from TWRP. Absolutely none of the reboot button combinations work.
Has anyone experienced this before? The seller is promising to fix or replace the phone so I've sent it back. But I'm still interested in finding out what went wrong. Are there any pitfalls when downgrading -- I only went from 378 to 366. My impression was that HURUpdater was fairly reliable. I'm wondering if the the B666 ROM was corrupted. I'm still surprised that I ended up with a hard-bricked phone.
Thanks.
SirShnike said:
I recently picked up a Chinese variant (STF-AL10) Honor 9 and wen through the process of unlocking the bootloader, rooting and re-branding to the European variant (STF-L09). All good. Was able to flash the latest ROM (STF-L09C432B378) using HURUpdater. All good except the 2 capacitive keys not working. Saw that there was a potential fix with an updated Kernel for build 366. So.... I tried flashing STF-L09C432B366 with HURUpdater. The flash appeared to be successful (no error messages except for the a couple that are expected apparently). But the phone was dead right after I tried rebooting from TWRP. Absolutely none of the reboot button combinations work.
Has anyone experienced this before? The seller is promising to fix or replace the phone so I've sent it back. But I'm still interested in finding out what went wrong. Are there any pitfalls when downgrading -- I only went from 378 to 366. My impression was that HURUpdater was fairly reliable. I'm wondering if the the B666 ROM was corrupted. I'm still surprised that I ended up with a hard-bricked phone.
Thanks.
Click to expand...
Click to collapse
Hello, for me happend quite the same thing, I tried to downgrade my original STF-L09 from b378 to b368 with HURUpdater and right after rebooting from TWRP, where I chose reboot to recovery, the phone died. Because it is in warranty I sent it to service last week. So I'm looking forward to what they'll say to me
Regards.
You can not lower the firmware version if your firmware is gt Turbo
Your phone will fall into the state of usb ser
You can restore it but it costs money
I reconstructed my phone from this brick myself
gaguga said:
You can not lower the firmware version if your firmware is gt Turbo
Your phone will fall into the state of usb ser
You can restore it but it costs money
I reconstructed my phone from this brick myself
Click to expand...
Click to collapse
What was the first firmware with gt Turbo? b377? Previously I successfully downgrade from b376 to b368.
btw your post is very useful!
Yeah, that explains a lot. What's been the best fix so far for the capacitive buttons problem? The one route I've seen is flashing the kernel file in fastboot mode from one of the patched builds (366, etc.) Any other ways that work?
gaguga said:
You can not lower the firmware version if your firmware is gt Turbo
Your phone will fall into the state of usb ser
You can restore it but it costs money
I reconstructed my phone from this brick myself
Click to expand...
Click to collapse
How did you do that? Dc phoenix?
Midhon58 said:
How did you do that? Dc phoenix?
Click to expand...
Click to collapse
no, not phoenix
gaguga said:
no, not phoenix
Click to expand...
Click to collapse
IDT?
oslo83 said:
IDT?
Click to expand...
Click to collapse
Yes
gaguga said:
Yes
Click to expand...
Click to collapse
What does it mean IDT?
Thanks.
modest.young said:
What does it mean IDT?
Thanks.
Click to expand...
Click to collapse
Special program
gaguga said:
Yes
Click to expand...
Click to collapse
gaguga said:
You can not lower the firmware version if your firmware is gt Turbo
Your phone will fall into the state of usb ser
You can restore it but it costs money
I reconstructed my phone from this brick myself
Click to expand...
Click to collapse
My phone came back from service center after bricking it during downgrading from b378 to b368 with changed motherboard. So unlocking the bootloader via HCU client was needed. Unlocking succeeded, so now I'm going to flash new treble ROMs.
modest.young said:
My phone came back from service center after bricking it during downgrading from b378 to b368 with changed motherboard. So unlocking the bootloader via HCU client was needed. Unlocking succeeded, so now I'm going to flash new treble ROMs.
Click to expand...
Click to collapse
And I like you))))
https://forum.xda-developers.com/showpost.php?p=78564317&postcount=1081
cioce said:
I try to flash B376 (already flashed some months ago) over B378 and now it's HARDBRICKED
like this https://forum.xda-developers.com/honor-9/how-to/revive-dead-honor-9-hardbrick-connect-t3846500
I don't wanna to spend money on dc-unlocker, so I will give the phone to Honor service, hoping they pass it in warranty. :fingers-crossed:
Click to expand...
Click to collapse
fuc*** GPU turbo
yz8_1337 said:
Hello, do you mind telling me how exactly you fixed your phone?
I'd highly appreciate it
Click to expand...
Click to collapse
1 Transfer the phone to USB com
2 we sew a board firmware
3 in Hsu prescribe imei
4 flashing firmware
This is briefly
Sorry for my English
Related
please help me solved this problem
i upgraded my g925f from lollipop to marshmallow
since i bought it from Philippines i installed ph stock rom 6.0.1
but then i dont have any signals so i tried other region and installed united arab emirates
but the problem is i want to downgrade my g925f from 6.0.1 to 5.1.1
i tried already many stock roms but still failed and giving a msg. sw rev check fails device: (number) binarynumber)
i also tried flashing bootloader and modem first but still the same result
please help me to fix my g925f thanks.
christianesquejo12 said:
please help me solved this problem
i upgraded my g925f from lollipop to marshmallow
since i bought it from Philippines i installed ph stock rom 6.0.1
but then i dont have any signals so i tried other region and installed united arab emirates
but the problem is i want to downgrade my g925f from 6.0.1 to 5.1.1
i tried already many stock roms but still failed and giving a msg. sw rev check fails device: (number) binarynumber)
i also tried flashing bootloader and modem first but still the same result
please help me to fix my g925f thanks.
Click to expand...
Click to collapse
have u tried samsung smart switch
if ur device isnt carrier locked
samsung smart switch will fix it
osman34 said:
have u tried samsung smart switch
if ur device isnt carrier locked
samsung smart switch will fix it
Click to expand...
Click to collapse
i tried but smartswitch says that my s/n is invalid
christianesquejo12 said:
i tried but smartswitch says that my s/n is invalid
Click to expand...
Click to collapse
Did you try to just reset network settings? Is your phone stuck in a boot loop?
callumbr1 said:
Did you try to just reset network settings? Is your phone stuck in a boot loop?
Click to expand...
Click to collapse
i already did that but nothing happen , and everytime i was stucked on a bootloop i flash again the 6.0.1 rom in order to remove the bootloop
Have you tried a Rom with same number in it as original (file name 9th position states "2' or "3", etc and probably is the same as the error device number)?
christianesquejo12 said:
i already did that but nothing happen , and everytime i was stucked on a bootloop i flash again the 6.0.1 rom in order to remove the bootloop
Click to expand...
Click to collapse
Yeah. You cant downgrade from MM back to 5.1.1 unfortunately
callumbr1 said:
Yeah. You cant downgrade from MM back to 5.1.1 unfortunately
Click to expand...
Click to collapse
Well that's not true, i did it last week, so perfectly possible (not when you have locked bootloader). But you have to use the correct stock firmware version...
Dr_IT said:
Well that's not true, i did it last week, so perfectly possible (not when you have locked bootloader). But you have to use the correct stock firmware version...
Click to expand...
Click to collapse
You can only downgrade if you have unlocked bootloader and your fw is 3xxxx or lower... (the first few mm builds)
callumbr1 said:
You can only downgrade if you have unlocked bootloader and your fw is 3xxxx or lower... (the first few mm builds)
Click to expand...
Click to collapse
So you confirm you can downgrade? Haven't tried the new 4xxx firmware yet, so that maybe true or not. But 4xxx is very new and 3xxx or lower are a lot of firmwares, so not a few...
Dr_IT said:
So you confirm you can downgrade? Haven't tried the new 4xxx firmware yet, so that maybe true or not. But 4xxx is very new and 3xxx or lower are a lot of firmwares, so not a few...
Click to expand...
Click to collapse
Well i personally haven't managed to downgrade my device and im on 3xxx. There are few reports on here that once you flash 4xxx you cannot go back. Infact im yet to find somebody who has succesfully downgraded on here.
callumbr1 said:
Well i personally haven't managed to downgrade my device and im on 3xxx. There are few reports on here that once you flash 4xxx you cannot go back. Infact im yet to find somebody who has succesfully downgraded on here.
Click to expand...
Click to collapse
Yeah i've read those posts too. But as i also almost gave up on downgrading from 3xxx because it was mentioned here a lot it couldn't be done while this was not true, i'm not taking that as 100% true anymore...
Dr_IT said:
Yeah i've read those posts too. But as i also almost gave up on downgrading from 3xxx because it was mentioned here a lot it couldn't be done while this was not true, i'm not taking that as 100% true anymore...
Click to expand...
Click to collapse
What mm firmware did you downgrade from? What build was it?
callumbr1 said:
What mm firmware did you downgrade from? What build was it?
Click to expand...
Click to collapse
Downgraded from G925FXXS3DPB2 to G925FXXS3COK5...
Hi All,
So after searching all the threads and forums I have created this thread to address this issue and to get possible solutions.
I have a Redmi Note 4 - Snapdragon/Qualcomm variant 4GB/64GB version.
Bootloader Status: Unlocked.
OS Version: MIUI 8, 7.4.20 Developer Version.
So sometime back I tried to upgrade to the latest Version of MIUI9 7.9.15. When the system got updated and rebooted my phone got softbricked. SS below. I was on one of the Custom ROMs AEX and tried updating the firmware of MIUI9 and faced the same issue. However am able to come out of the brick using MiFlash tool am still not sure what's causing the issue.
NOTE: Even after reverting back I see the weird lines on screen unless I flash the previous firmware version again.
Would appreciate your thoughts and inputs. Thanks!
Images: Adding Soon!
Alexis Gordon said:
Hi All,
So after searching all the threads and forums I have created this thread to address this issue and to get possible solutions.
I have a Redmi Note 4 - Snapdragon/Qualcomm variant 4GB/64GB version.
Bootloader Status: Unlocked.
OS Version: MIUI 8, 7.4.20 Developer Version.
So sometime back I tried to upgrade to the latest Version of MIUI9 7.9.15. When the system got updated and rebooted my phone got softbricked. SS below. I was on one of the Custom ROMs AEX and tried updating the firmware of MIUI9 and faced the same issue. However am able to come out of the brick using MiFlash tool am still not sure what's causing the issue.
NOTE: Even after reverting back I see the weird lines on screen unless I flash the previous firmware version again.
Would appreciate your thoughts and inputs. Thanks!
Images: Adding Soon!
Click to expand...
Click to collapse
What about fastboot mode?
Have you tried a full wipe and fresh install of the developer ROM, if that's the one you want?
sachin n said:
What about fastboot mode?
Click to expand...
Click to collapse
Apologies not able to add the Screens onto the OP for some reason stating I need to post some 10 posts or so.
Everything fastboot,recovery,boot screen shows a display which is messed up and shows scrambled screen.
Jimmyrinse said:
Have you tried a full wipe and fresh install of the developer ROM, if that's the one you want?
Click to expand...
Click to collapse
Did a full wipe and flashed Dev ROM latest build through MiFlash also the latest stable build causes the same issue. Not able to see anything the display gets messed up showing only some scramble red and black vertical lines.
Not able to attach the screens. Will do attach them as soon as am able to.
Alexis Gordon said:
Apologies not able to add the Screens onto the OP for some reason stating I need to post some 10 posts or so.
Everything fastboot,recovery,boot screen shows a display which is messed up and shows scrambled screen.
Click to expand...
Click to collapse
Visit a nearby service centre?
And act like a noob in front of em', that's gonna work. They'll fix it for ya.
sachin n said:
Visit a nearby service centre?
Click to expand...
Click to collapse
Need to but still using this as my daily driver. Got a A1 just yesterday once everything is setup on that will walk-in to a SVC. Thanks!
sachin n said:
Visit a nearby service centre?
And act like a noob in front of em', that's gonna work. They'll fix it for ya.
Click to expand...
Click to collapse
You mean to say I shouldn't sound like a geek say I have unlocked the bootloader and was trying to just update the firmware to that of MIUI9 got "softbricked" reverted using MiFlash and stuff..
Alexis Gordon said:
You mean to say I shouldn't sound like a geek say I have unlocked the bootloader and was trying to just update the firmware to that of MIUI9 got "softbricked" reverted using MiFlash and stuff..
Click to expand...
Click to collapse
Yeah, that. Tell em' I dunno why, was updating my phone using about phone system update, it went like this. Please fix this! :angel:
Alexis Gordon said:
Did a full wipe and flashed Dev ROM latest build through MiFlash also the latest stable build causes the same issue. Not able to see anything the display gets messed up showing only some scramble red and black vertical lines.
Not able to attach the screens. Will do attach them as soon as am able to.
Click to expand...
Click to collapse
Can you boot to recovery or is screen scrambled in that too?
Stock or using twrp
sachin n said:
Yeah, that. Tell em' I dunno why, was updating my phone using about phone system update, it went like this. Please fix this! :angel:
Click to expand...
Click to collapse
My MIUI Forum post. The screens are there in the post if you are curious.
Not sure if XDA rules allow me to post an external link..
http://en.miui.com/thread-854626-1-1.html
Jimmyrinse said:
Can you boot to recovery or is screen scrambled in that too?
Stock or using twrp
Click to expand...
Click to collapse
Yeah that too. Gosh! wish XDA allowed me to attach some SS.
Everything goes Haywire, I would have to flash the old Dev build through MiFlasher again and flash the TWRP .IMG file through fastboot. It such a pain good thing I have my bootloader unlocked else would be lost.
Alexis Gordon said:
My MIUI Forum post. The screens are there in the post if you are curious.
Not sure if XDA rules allow me to post an external link..
http://en.miui.com/thread-854626-1-1.html
Click to expand...
Click to collapse
Ow, that was seriously serious, visit nearby centre ASAP and get it fixed. Good luck.
sachin n said:
Ow, that was seriously serious, visit nearby centre ASAP and get it fixed. Good luck.
Click to expand...
Click to collapse
Was it? OMG! I didnt make put a big deal of it as I was always able to revert back and run Custom ROMs somehow. Will visit a SVC asap. Thanks again.:angel:
Strange how previous version is ok....
Which version can you use that works
Alexis Gordon said:
Was it? OMG! I didnt make put a big deal of it as I was always able to revert back and run Custom ROMs somehow. Will visit a SVC asap. Thanks again.:angel:
Click to expand...
Click to collapse
Why not try flashing stable version through mi flash tool?
Venkatesh said:
Why not try flashing stable version through mi flash tool?
Click to expand...
Click to collapse
Thanks for the suggestion but like I mentioned few posts earlier I did try flashing the Stable build fastboot version - v 8.5.4.0 and the same thing happened. So got me thinking issue seems not to be confined with MIUI9 but something which am not able to figure out.
Alexis Gordon said:
Thanks for the suggestion but like I mentioned few posts earlier I did try flashing the Stable build fastboot version - v 8.5.4.0 and the same thing happened. So got me thinking issue seems not to be confined with MIUI9 but something which am not able to figure out.
Click to expand...
Click to collapse
firmware?
If the recovery does the same then its not the rom as this loads before the rom
Jimmyrinse said:
firmware?
If the recovery does the same then its not the rom as this loads before the rom
Click to expand...
Click to collapse
Pretty sure firmware is closely associated to Bootloader, Boot and Recovery much more than the ROM itself. Then the Signal reception, radio and stuff. But I may be wrong.
Ok I took the chance in flashing my SM-N950U to the U1 firmware using Prince Odin and it worked. Be sure that both firmwares are bootloader v3 or you WILL BRICK also as a safe precaution i deleted my google accounts and any that controls the FRP so that it would be off.
BigHussle said:
Ok I took the chance in flashing my SM-N950U to the U1 firmware using Prince Odin and it worked. Be sure that both firmwares are bootloader v3 or you WILL BRICK
Click to expand...
Click to collapse
Which U1 firmware did you flash? And what firmware were you previously on?
So does that mean this whole "you can't cross flash between U and U1" thing has been debunked? It was just an issue with people trying to flash a lower level bootloader?
Edit: looks like it: https://forum.xda-developers.com/ga...block-carrier-switching-t3742409/post75423088
andrewNY said:
So does that mean this whole "you can't cross flash between U and U1" thing has been debunked? It was just an issue with people trying to flash a lower level bootloader?
Edit: looks like it: https://forum.xda-developers.com/ga...block-carrier-switching-t3742409/post75423088
Click to expand...
Click to collapse
Yes, just stick to BL 3 if you are on it and you are good.
Gus194 said:
Which U1 firmware did you flash? And what firmware were you previously on?
Click to expand...
Click to collapse
I was on AT&T 3BRA8 on a Note 8 I got from AT&T I deleted my google accounts from the device before doing the flash.
confirming. went from 3CRAE(oreo) to 3BRA5(U1) using prince odin.
guaneet said:
confirming. went from 3CRAE(oreo) to 3BRA5(U1) using prince odin.
Click to expand...
Click to collapse
Were you nervous watching it install. I was sweatin the whole time
BigHussle said:
Were you nervous watching it install. I was sweatin the whole time
Click to expand...
Click to collapse
Yeah. Funny thing is, I was doing this on my laptop which died halfway through the Odin. I just rebooted back into download mode and reflashed. I was almost in tears
What is the difference between u and u1?
guaneet said:
Yeah. Funny thing is, I was doing this on my laptop which died halfway through the Odin. I just rebooted back into download mode and reflashed. I was almost in tears
Click to expand...
Click to collapse
That happened to me once. But I have a spare phone now
Jay5583 said:
What is the difference between u and u1?
Click to expand...
Click to collapse
U is for the US carrier branded phones (950U) and has the carrier bloat added on top of what is downloaded during setup. The U1 (950U1) is for the US unlocked unbranded phones sold at Best Buy and others. That has no carrier bloat added and what is automatically downloaded depending on what sim you have can be uninstalled instead of disabled. The downside to U1 is you will be missing some carrier specific enhancements like VVM for Verizon and other features. But with that said there are some apps and features that are not hidden on the U1. I have a U1 and prefer the cleaner software it has.
Jay5583 said:
What is the difference between u and u1?
Click to expand...
Click to collapse
U is all US carrier
U1 is unlocked
Nevermind, figured it out!
Close thread
Is there one for the S7 Active?
ThunderingLight said:
Is there one for the S7 Active?
Click to expand...
Click to collapse
Hasn't been found yet
Ok can you update the post once it has been found?
So, anyone flash this yet? I'm tempted but won't be back home to a PC (in case something goes wrong) until tonight. Just looking for some general impressions.
So, I did this. Pretty impressed with the overall device feel now, SE9 is nice . No hang ups other thank it took a long friggin' time, also remember this will WIPE all the data, so make sure to do a backup prior to. The initial/first phone setup is very iPhone-ish, imo.
bobloblaw1 said:
So, anyone flash this yet? I'm tempted but won't be back home to a PC (in case something goes wrong) until tonight. Just looking for some general impressions.
Click to expand...
Click to collapse
Be warned; this update is ONLY for SM-G930A firmware - it has a second-stage updater that blocks all other versions (including SM-G930T, which I myself tried). In other words, it is a carrier-specific update, folks.
PGHammer said:
Be warned; this update is ONLY for SM-G930A firmware - it has a second-stage updater that blocks all other versions (including SM-G930T, which I myself tried). In other words, it is a carrier-specific update, folks.
Click to expand...
Click to collapse
Will it work for sm-g930u at&t ????
mhdsweidan said:
Will it work for sm-g930u at&t ????
Click to expand...
Click to collapse
HIGHLY doubtful - not with a specific firmware check in place.
mhdsweidan said:
Will it work for sm-g930u at&t ????
Click to expand...
Click to collapse
You could try flashing G930A firmware in Odin and updating that way.
(Not sure it'll work though)
Sent from my SM-G955U using Tapatalk
If switching from u firmware back to att ql1 what version is capable of flashing att haven't been on carrier firmware since mm , wanna try Oreo
miko12312 said:
If switching from u firmware back to att ql1 what version is capable of flashing att haven't been on carrier firmware since mm , wanna try Oreo
Click to expand...
Click to collapse
What's your bootloader version? (5th from last letter in build number)
Sent from my SM-G955U using Tapatalk
FatalONEM8 said:
You could try flashing G930A firmware in Odin and updating that way.
(Not sure it'll work though)
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
If it weren't for this being a daily driver, I'd consider it. However, because it is, that's not an option. So I'll have to wait for either a neutral version or one that will work with the SM-G930T.
I am currently testing it out, I was on the latest U firmware and downloaded the latest ATT firmware, will update on how it goes
**EDIT
I am getting a model mismatch trying to flash G930AUCS4BRA1 (full odin file) on to a G930UUES4BRA1 firmware
micallan_17 said:
I am currently testing it out, I was on the latest U firmware and downloaded the latest ATT firmware, will update on how it goes
**EDIT
I am getting a model mismatch trying to flash G930AUCS4BRA1 (full odin file) on to a G930UUES4BRA1 firmware
Click to expand...
Click to collapse
Try using PrinceComsy Odin
Sent from my SM-G955U using Tapatalk
oreo otas
Goodnight friends, I started to update my phone to version 8.0 but it has more than 30 min in the option of patchin system files is normal or my step to better life is my s7.
Excuse me for my English since it is not my native language.
spend the fright of my life but finally install now approve to see how it works on android 8.0
Just flashed updateon my s7 and now mywifi is not working anyone else having this issue?
Has anyone been able to successfully downgrade back to RA1 after sideloading 8.0?
chewis559 said:
Just flashed updateon my s7 and now mywifi is not working anyone else having this issue?
Click to expand...
Click to collapse
Just reboot in recovery mode and wipe cache
chewis559 said:
Just flashed updateon my s7 and now mywifi is not working anyone else having this issue?
Click to expand...
Click to collapse
I had the same issue. The recommendation of rebooting into recovery and wiping Cache works.
:good:
I have a moto edge+ 2022 boost mobile and I wonder if it can be installed retusa firmware I need flash instructions and by the way should I unlock the bootloader?
EddiePR said:
I have a moto edge+ 2022 boost mobile and I wonder if it can be installed retusa firmware I need flash instructions and by the way should I unlock the bootloader?
Click to expand...
Click to collapse
I unlocked my bootloader. As long as you are fine with your warranty being void I don't wee what it could hurt to do so. I am trying to figure out if different firmware can be installed also
BariB523 said:
I unlocked my bootloader. As long as you are fine with your warranty being void I don't wee what it could hurt to do so. I am trying to figure out if different firmware can be installed also
Click to expand...
Click to collapse
ooh! to unlock the bootloader is the same process as always or something new? I haven't had a moto for a long time, I don't remember anymore and I'm really interested is possible to flash another firmware? Do you know the codename of this model to look for the firmware on the web since I still don't have a laptop... so I can see for myself
BariB523 said:
I unlocked my bootloader. As long as you are fine with your warranty being void I don't wee what it could hurt to do so. I am trying to figure out if different firmware can be installed also
Click to expand...
Click to collapse
I really don't care about warranty.. I got it for $199. I'm going to use it without a case / screen protector, that's how I am!
EddiePR said:
ooh! to unlock the bootloader is the same process as always or something new? I haven't had a moto for a long time, I don't remember anymore and I'm really interested is possible to flash another firmware? Do you know the codename of this model to look for the firmware on the web since I still don't have a laptop... so I can see for myself
Click to expand...
Click to collapse
How To Unlock Bootloader On Any Motorola Moto Phones
In this comprehensive tutorial, we will show you the steps to unlock the bootloader on any Motorola device. The journey of this OEM has been quite an
www.getdroidtips.com
These instructions are spot on. This is what I followed and the codename is HIPHI. I used the firmwares here HIPHI firmwares. I flashed the Android 13 file located in the RETUS folder in the Official folder. I used Rescue and Smart Assistant app to initiate a rescue and once the rom files were downloaded I switched the files with the files from the lolinet rom
EddiePR said:
I really don't care about warranty.. I got it for $199. I'm going to use it without a case / screen protector, that's how I am!
Click to expand...
Click to collapse
Lol! I want this phone to last a while even with the price. It was too good of a deal lol
BariB523 said:
How To Unlock Bootloader On Any Motorola Moto Phones
In this comprehensive tutorial, we will show you the steps to unlock the bootloader on any Motorola device. The journey of this OEM has been quite an
www.getdroidtips.com
These instructions are spot on. This is what I followed and the codename is HIPHI. I used the firmwares here HIPHI firmwares. I flashed the Android 13 file located in the RETUS folder in the Official folder. I used Rescue and Smart Assistant app to initiate a rescue and once the rom files were downloaded I switched the files with the files from the lolinet rom
Click to expand...
Click to collapse
I installed the retus Android 12 rom but it doesn't grab ota and it stays on the dish software channel but the android 13 drains the battery in less than 30 minutes the battery ran out didn't something similar happen to you?
BariB523 said:
How To Unlock Bootloader On Any Motorola Moto Phones
In this comprehensive tutorial, we will show you the steps to unlock the bootloader on any Motorola device. The journey of this OEM has been quite an
www.getdroidtips.com
These instructions are spot on. This is what I followed and the codename is HIPHI. I used the firmwares here HIPHI firmwares. I flashed the Android 13 file located in the RETUS folder in the Official folder. I used Rescue and Smart Assistant app to initiate a rescue and once the rom files were downloaded I switched the files with the files from the lolinet rom
Click to expand...
Click to collapse
Wait how you can change firmware in smart assistant after download or begin proccess ? I never used that app
EddiePR said:
Wait how you can change firmware in smart assistant after download or begin proccess ? I never used that app
Click to expand...
Click to collapse
Were you ever able to figure this out?
EddiePR said:
I installed the retus Android 12 rom but it doesn't grab ota and it stays on the dish software channel but the android 13 drains the battery in less than 30 minutes the battery ran out didn't something similar happen to you?
Click to expand...
Click to collapse
I haven't had the same issue unfortunately
I'm also trying to change the software channel.
Is there a way to change the ro.carrier value?