Related
Hi experts!
Is there an available factory image of the latest firmware for griffin xt1650-03 for download? I unlocked my boot loader and tried to flash custom firmware now I am stuck in boot loop. My phone was nougat and updated via OTA last week before I decided to unlock boot loader. I tried loading the latest image I got from firmware.center but I am getting Downgrade version and verification failed when flashing stock partition and not loader. Please help
Note: I did this my wifi became unusable after my last OTA (mac 02:00:00:00) and thought using custom firmware would help
And I did not make a back up
Get it in fastboot mode, flash TWRP and root it. That might work.
I am in exactly the same position as OP, although I have successfully installed TWRP and have open bootloader from which I can boot into TWRP no probs. I didnt do a backup (will never again make this error!!)
The problem arises when I try to flash (any) files over to device I get the "Downgrade version and verification failed" like OP when flashing stock Telus rom (telus phone) or any other rom/files.
Rebooting brings me back to the moto unlocked bootloader page (horrible!) and the only way out is to get key combo or fastboot into bootloader/recovery etc.
Tried flashing multiple images as whole or bit by bit, always get the same bad validation message. Finding it hard to believe this 700dollar phone is a brick after literally following MotoS own 'unlock your bootloader' instructions. Never had issues like this on OPO, S6, S7, LG etc.
PC shows android device connected, nothing in the two empty folders that appear. TWRP confirms I have no OS installed and throws me back to bootloader.Wondering if locking bootloader again will allow me to install 'stock' ROM or at least recovery? I have reached my android knowledge limit and am not sure where to go from here, any help much appreciated!
OK. This happened to me. The way that I solved it was by flashing the RETUS NPL86.25.15 and then flashing the OTA 25.17-3-3 through twrp. Although I think I could've saved the headache if the original instructions included flashing the OEM.bin but anyways. That's what I did. Hope it helps.
Thanks. I did try flashing the oem.bin but got partition name error.
Can you link to the files you mention I think it's a kernel and then an OTA image? Thanks again in advance.
What I mean is that when I first started flashing the RETUS rom the instructions skipped that part so I ended up flashing most of the file system without something so it would never boot but it wouldn't loop it'd just hang. So basically you flash everything and then include the OEM.bin after you do the system chunks
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Meranico said:
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Click to expand...
Click to collapse
If you can boot to "downloader" use rebranding SW, it will fix everything
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
Thank you so much! My mobile phone is working again! :victory:
Edit: Small problem persists: I cannot use the buttons left and right of the scanner. They do not react.
Edit2: Could fix this. I flashed B120 and the buttons worked again.
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
whats rebranding sw and hoe do i do it as i have the smae problem please help
corey568brown said:
whats rebranding sw and hoe do i do it as i have the smae problem please help
Click to expand...
Click to collapse
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Meranico said:
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Click to expand...
Click to collapse
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
corey568brown said:
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
Click to expand...
Click to collapse
Good to know!
As I had the same problem as you do know: I flashed B120, which does not seem to have the bug with the buttons and upgraded via Firmware Finder to B130 and then to B150.
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work
Hello.
My honor 9 (stf al00) cant boot. It stuck on huawei erecovery.
I've tried hard reset, wipe cache & wipe data but still stuck.
And also I dont have the driver.
Can anyone please help me.
What happened before ?
You were on nougat or oreo ? which build ?
Which region ? C00 ? or rebranded C432 or else ?
oslo83 said:
What happened before ?
You were on nougat or oreo ? which build ?
Which region ? C00 ? or rebranded C432 or else ?
Click to expand...
Click to collapse
I dont know what happend, give my brother use for awhile, suddenly he return to me with this problem.
its on nougat. sorry what build, i dont know.
Region China?. i dont know about the C00 or rebranded and c432 that you said. really have no idea.
OK.
So your Honor9 is STF-AL00 and was on nougat.
But:
-you don't know on which firmware region it was and you don't know if it was rebranded to STF-L09
-i guess your brother could also have updated it to oreo, or rebranded it before bricking it...
If you did not have any chinese app stock installed like QQ, Weibo or Tancent News then you could be probably on region C432 (or C10 or C185) ;
If so use this with an exfat external micro sdcard or usb-otg EXFAT formatted:
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
First try with C432B130, read the instructions inside, do it, then report.
thanks.. i will try it tonight,
i've done try update with sd card before, but not with those file inside the link you give.
and also not with EXFAT fromat sd card, but it said Software Update Failed.
i will try this and update here again..
thanks
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work
ruigarcia said:
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work
Click to expand...
Click to collapse
Are you with nougat or oreo partitionni'g scheme ?-> are you actually booting on a nougat twrp or on a oreo twrp ?
Which region your phone were on on ?
original chinese C00 ?
or rebranded C432, C10 or else?[/QUOTE]
oslo83 said:
Are you with nougat or oreo partitionni'g scheme ?-> are you actually booting on a nougat twrp or on a oreo twrp ?
Which region your phone were on on ?
original chinese C00 ?
or rebranded C432, C10 or else?
Click to expand...
Click to collapse
[/QUOTE]
right now with oreo partitions, never rebranded the phone, and i was running update b362 so i assume im still on c00, otherwise i dont think i would have worked.
twrp is 3.1.1.1 open kirin edition
right now with oreo partitions, never rebranded the phone, and i was running update b362 so i assume im still on c00, otherwise i dont think i would have worked.
twrp is 3.1.1.1 open kirin edition[/QUOTE]
OK so, the facts :
1) B362 firmware are mostly european (C432) or russian (C10) and could be japanese (C635).
So your phone was previously rebranded from chinese to one of these region.
It's not a problem if not done wrong, maybe your case...
2)'twrp 3.1.1.1 open kirin edition' is a custom recovery for NOUGAT and not for oreo.
And then some more questions:
-Can you boot your phone to normal mode ?
-You were on nougat before brick ?
-You were one oreo B362 before brick ?
-The brick happens after it upgraded from mogat to oreo B362 ? If so, how did you update ? normal OTA ? forced OTA with android app Firmware Finder ?
i can only boot the phone in recovery mode (twrp and erecovery) and fastboot
i installed b360 through forced ota and then when i was in the system i updated again to b362 throught settings\system update
i was on oreo b362 before brick, and i remember now that my navigations buttons were not working so i flashed a custom kernel to fix it, but
that prevented me from booting to the system again. (Proto Kernel)
edit: used that tool you gave me and i managed to flash STF-L09_C432B360.
ruigarcia said:
i installed b360 through forced ota and then when i was in the system i updated again to b362 throught settings\system update
Click to expand...
Click to collapse
So your phone was correctly rebranded in the past and we can deduce you are now on region C432 or C10.
ruigarcia said:
i was on oreo b362 before brick, and i remember now that my navigations buttons were not working so i flashed a custom kernel to fix it, but
that prevented me from booting to the system again. (Proto Kernel)
Click to expand...
Click to collapse
You flashed a custom B360 kernel over your B362 : It was why your phone bootlooped just after !!
Flashing a stock B362 kernel would have solve the bootloop.
ruigarcia said:
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
Click to expand...
Click to collapse
You said you had flashed boot, kernel and recovery from an update.app.... Which build number and region this update.app was from ?
You could flash back B362 stock boot, kernel and recovery and it should boot if you did not messed something else...
So, the best for you will be to:
1) use HuRUpdater to flash C432B360 or C10B360 firmware (depending of your actual phone region)
2)then flash the B360 kernel fix
3)then update via OTA or huRUpdater.
oslo83 said:
So your phone was correctly rebranded in the past and we can deduce you are now on region C432 or C10.
You flashed a custom B360 kernel over your B362 : It was why your phone bootlooped just after !!
Flashing a stock B362 kernel would have solve the bootloop.
You said you had flashed boot, kernel and recovery from an update.app.... Which build number and region this update.app was from ?
You could flash back B362 stock boot, kernel and recovery and it should boot if you did not messed something else...
So, the best for you will be to:
1) use HuRUpdater to flash C432B360 or C10B360 firmware (depending of your actual phone region)
2)then flash the B360 kernel fix
3)then update via OTA or huRUpdater.
Click to expand...
Click to collapse
i flashed many update.app, i messed up with that, cant remember the last one.
just flashed twrp for oreo now, went to terminal and i can see "ro.hw.vendor: (hw)
does this tell me my phone region?
with this twrp for oreo i also get another error when flashing a rom zip "failed to mount "\system" (permission denied)
Stop messing with random dload folder and update.app ; From what i seen only special one called 'service repair' will work.
No. It does not.
Stop messing trying to flash random zip when on twrp ; From what i heard only special one called 'FullOTA-MF-PV' will work this way with twrp.
Be bold and try HuRUpdater witj C432B360 following my latter post.
oslo83 said:
Stop messing with random dload folder and update.app ; From what i seen only special one called 'service repair' will work.
No. It does not.
Stop messing trying to flash random zip when on twrp ; From what i heard only special one called 'FullOTA-MF-PV' will work this way with twrp.
Be bold and try HuRUpdater witj C432B360 following my latter post.
Click to expand...
Click to collapse
i used HuRUpdater and worked. thank you! cant update to b362 through settings tho
C432 is maybe the wrong region if you don't get ota update notification to b362/b364 when checking for update in settings :
1) What's your build number version on Settings/System/about ?
2) What's the country shown when you dial**#*#2846579#*#**- on the dial pad, then go to 'Network Information Query' and then to 'Vendor Country Info' ?
---------- Post added at 19:44 ---------- Previous post was at 19:42 ----------
Dial**#*#2846579#*#*
---------- Post added at 19:46 ---------- Previous post was at 19:44 ----------
sorry typos.
So dial:
Code:
*#*#2846579#*#*
im so sorry, i cant access my pc right now.
i will update soon i can get access to my pc.
oslo83 said:
C432 is maybe the wrong region if you don't get ota update notification to b362/b364 when checking for update in settings :
1) What's your build number version on Settings/System/about ?
2) What's the country shown when you dial**#*#2846579#*#**- on the dial pad, then go to 'Network Information Query' and then to 'Vendor Country Info' ?
---------- Post added at 19:44 ---------- Previous post was at 19:42 ----------
Dial**#*#2846579#*#*
---------- Post added at 19:46 ---------- Previous post was at 19:44 ----------
sorry typos.
So dial:
Code:
*#*#2846579#*#*
Click to expand...
Click to collapse
vendor:hw
country:eu
build number:stf-l09 8.0.0.360(c432)~
reflashed b360 and now i get update to b364 on settings. still no capacity buttons..
So, you're fine on C432.
Just flash the B360 kernel fix while you're still on B360 https://forum.xda-developers.com/showpost.php?p=75772700 ;
This will fix your buttons.
You can then do a normal update via settings
ok so i tried to update using vol up + vol down + power button, again it said software install failed
inside those rar file got 2 file, 1 is UPDATE.APP which is 4gb++ and another one is update_STF-L09_hw_eu.app size around 1.4gb.
try update with 4gb file, appear 5% loading and then appear software install failed, same with 1.4gb file...
the only option i got is reboot system now when the error come out..
already did wipe cache & data before i do the update..
any idea? am i doing wrong step?
I have the same problem...When the installation begins, it stops at 5%
My phone is turned off. I tried to install recovery but got nothing
any idea please
Mate 10. So, I tried to install the latest EMUI version using HuRUpdater - bad idea. Now, my phone will not boot. I can enter EMUI Recovery Mode but when I try to receive download package, it says it can't be retrieved. I can also enter Fastboot Mode but the problem with that is that under Device Manager, it only gets recognized as, "Android Bootloader Interface."
Please, any help would be greatly appreciated.
edit: So, fastboot DOES work. What files from what version do I flash to return to stock recovery? I don't even know if Pie was actually written to the device or not before the device rebooted and wouldn't boot.
edit again: I have just successfully installed TWRP via fastboot but it hangs at startup screen - is this because it's not compatible with Pi?
So I've tried flashing ramdisk_recovery.img, kernel.img and system.img from the Pi version but I still can't factory reset the phone. It boots back to the white screen with the android dude and says, "Please update system again."
Any help would be appreciated...
Using Multi-Tool, it detects my device in Fastboot mode as still 8.0.0.143. So, I'm trying to flash System, Ramdisk, Cust, Recovery_Ramdisk and Userdata......all succeed, except one - Ramdisk.img. When I manually try to flash Ramdisk.img in command prompt, it also fails, "FAILED (remote: partition length get error)". In Multi-tool, the error is, "the size or path does not match the file system markup."
Please, does anyone have any other suggestions? I've been at this for nearly 12 hours straight.
I assume u have unlocked bootloader and frb unlocked too if both yes u can search in xda for zip file beta downy 0.4
It will help you to downgrade emui 9 to. Emui 8
If u have unlocked bootloader only I guess u need funky huawei to restore ur devise
I hope I did helped u
Thanks for the reply.
My bootloader is unlocked but how do I know if I have unlocked FRP?
And downy tool requires ADB but I can only access Fastboot.
edit: I just checked and my FRP is also unlocked. What now?
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
essen212 said:
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
Click to expand...
Click to collapse
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Pretoriano80 said:
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Click to expand...
Click to collapse
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
essen212 said:
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
Click to expand...
Click to collapse
Try with EMUI 9 first, then, if it fails, try Oreo. The most important part is finding a DLOAD firmware for your cust/region.
I've fixed it!
Funky emailed me back and I ended up using a different method on their site which worked like a charm. I couldn't recommend them enough.
Hi, good to hear you got it sorted! Would you mind sharing the details on what you had to do differently with FHC? I'm in the same boat here with a mate 10 pro that died on emui9 and I'm not sure if I should go the FHC way or not...
Thx - David
Hello,
i got today a Chinese XT1605-05. I flashed the firmware and gapps with twrp from this thread.
The firmware and gapps were installed successfully. But after reboot only the boot animation stucked for around 5 minutes than the smartphone restarts into twrp. Gladly i can copy firmware files to system folder and flash again. So the smartphone isn’t bricked.
Than i tried an older lineage 16.0 firmware => same problem.
And a firmware [URL="https://forum.xda-developers.com/moto-z/development/rom-omnirom-t3881462“] from here[/URL] => same problem.
Now i have nothing running. I have no idea where i could get the right firmware file for this Chinese Version.
And the original (stock image from lenovo) firmware is only available from sources which could be infected. Not a good idea to flash this garbage.
Best regards
TUKF98
Edit:
Ok, here ist the default firmware:
https://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837
But it would be better to get android 9.0 working.
Sorry, for double post. It was created by a mistake.
Edit 2:
This stock firmware does not work. Wrong zip file.
Edit 3:
It works now, the lineage version .
I watched this video. And did all steps.
Edit 4:
Now its not working anymore. Its a joke. I installed a new version of lineageOS with the same procedure it worked first.
And now it wont work. The old firmware doesnt work also. WTF. I dont know what is wrong with this thing. Its now again stucking in boot sequence with the "ball moving on the line".
Edit:
Have flashed stock firmware back via fastboot commands. What a crap phone . 100 Euros are cheap, but not as cheap that i would take this ..... .
Now i have installed the original China firmware with trojans.
You cant block this **** from recording every input. But the european firmware does not run on my phone. After flash its hanging in bootloop.