Related
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
MH928 said:
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
Click to expand...
Click to collapse
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
paleszgergo said:
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
Click to expand...
Click to collapse
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
MH928 said:
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
Click to expand...
Click to collapse
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Justatechie said:
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Click to expand...
Click to collapse
Yeah, thats what i mean!
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Sirocco.ukr.lviv said:
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Click to expand...
Click to collapse
Is your Bootloader unlocked?
Justatechie said:
Is your Bootloader unlocked?
Click to expand...
Click to collapse
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Sirocco.ukr.lviv said:
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Click to expand...
Click to collapse
To find out, you have to put your phone into fastboot.
To do that power down your phone, then hold volume up and power button at the same time. There, the asus logo will pop up like normal and hang on that screen to show that you are in fastboot mode.
Open up command prompt and verify your device is connected, by typing in fastboot devices.
If it shows up good then all you have to do is type in fastboot oem device-info.
If it says device unlocked: true that means your BL is unlocked.
If its not, you have to download crowlock from the cm12 thread and flash it.
It works better with cwm but since you are stuck its worth a shot to flash it under old twrp.
Then check the BL status again, if its good great.
You could restore your device from some backups posted or if you could find a boot.img from the stock image, you could use the new version of twrp to flash the boot image under image flashing.
This is the adb/fastboot driver I use http://forum.xda-developers.com/showthread.php?t=2588979
Justatechie you are only one who help. i appreciate it. god bless you!
i've done it. unlocked already. i watched bootloop so i wiped everything. what rom to install?
del
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Justatechie said:
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Click to expand...
Click to collapse
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Sirocco.ukr.lviv said:
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Click to expand...
Click to collapse
Dont worry about the asus_toon, it will turn back into padfone x when you are finally able to restore to the at&t factory rom
What is very strange,is that you cannot wipe certain things, I guess It may be due to a tampered bootloader. (something must have tripped it up)
My bootloader is unlocked but not tampered.
But the reason why it says ASUS_T00N is because you installed cm or miui and it changed build prop and the partitions. (all of quarx roms are built from the pfs source but work on the pfx too) its not a big deal don't worry.
Have you tried any other recoveries, perhaps the older version of twrp Here
Try booting them through fastboot using the fastboot boot filename.img (of the recovery file that should be located inside a folder containg fastboot/adb files)
See if they can wipe cache data(no media) and system. Remember, booting from fastboot is just temporary
Then try flashing a rom, doesnt matter what it has to be but it should work after its done. Maybe flash without gapps, it could sometimes cause a random problem and besides you can always install it later.
I never had to use fastboot to wipe cache either because well I could do that in recovery, plus its safer
hey guy i have a big problem with my redmi 3, i unlocked the bootloader and then flashed twrp recovery, but it don't work properly, during the operation of flashing rom or nandroidbackup it reboot always, i've tried to reflash the recovery via adb and fastboot but the problem is not solved, can you help me?thank you sorry for bad english
SOLVED:i downgraded to 7.1.3 version via fastboot and then flash cofface version of twrp
robonudo said:
hey guy i have a big problem with my redmi 3, i unlocked the bootloader and then flashed twrp recovery, but it don't work properly, during the operation of flashing rom or nandroidbackup it reboot always, i've tried to reflash the recovery via adb and fastboot but the problem is not solved, can you help me?thank you sorry for bad english
Click to expand...
Click to collapse
No one has a solution? Advance some idea of problem if you want
robonudo said:
No one has a solution? Advance some idea of problem if you want
Click to expand...
Click to collapse
for me, you only have flash incorrect version of twrp.
i have got same problem.. then i have change twrp version (download coffage twrp) and i have solve it..
only one problem i have now: i must boot coffage twrp from pc.
Kayl88 said:
for me, you only have flash incorrect version of twrp.
i have got same problem.. then i have change twrp version (download coffage twrp) and i have solve it..
only one problem i have now: i must boot coffage twrp from pc.
Click to expand...
Click to collapse
Thank you for the help, but I tried such as 4 type of twrp but the result was the same, can you send me a PM with link of the version that work for you? For your problem has you press volume + and - power button for several second?
Kayl88 said:
for me, you only have flash incorrect version of twrp.
i have got same problem.. then i have change twrp version (download coffage twrp) and i have solve it..
only one problem i have now: i must boot coffage twrp from pc.
Click to expand...
Click to collapse
have you tried booting your phone with vol up + vol down + power buttons?
robonudo said:
Thank you for the help, but I tried such as 4 type of twrp but the result was the same, can you send me a PM with link of the version that work for you? For your problem has you press volume + and - power button for several second?
Click to expand...
Click to collapse
i'm back. in a minute i contact you via pm.
usblaidas said:
have you tried booting your phone with vol up + vol down + power buttons?
Click to expand...
Click to collapse
the problem is not enter into recovery.
the first time i have flash wrong twrp. when i enter in recovery, by hardware procedure, in the bottom of screen i read version of twrp.. and is version twrp 3.0.0r2. this is a wrong version!
then.. i do flash from pc, flash operation success.. and ONLY with command "fastboot boot XXXXX.img" , where xxxx.img is name of recovery i have flash before, i can enter in correct twrp.
i don't know why, but i think i can't flash and fix the correct version of twrp. bhooooooooooo!
edit:
problem solved..
i have rename twrp img file in "recovery.img" and i have flash it in fastboot mode by pc..
i have try to enter in recovery with adbo command (adb reboot recovery) and phone reboot in correct twrp version;
then i have try to enter in recovery with hardware procedure (poweroff, volume up + power and release power when appear Mi logo, tap on "recovery") and it work;
and, in the end, i have try to nter in recovery mode by app "updater"
all works perfectly now!
Kayl88 said:
i'm back. in a minute i contact you via pm.
the problem is not enter into recovery.
the first time i have flash wrong twrp. when i enter in recovery, by hardware procedure, in the bottom of screen i read version of twrp.. and is version twrp 3.0.0r2. this is a wrong version!
then.. i do flash from pc, flash operation success.. and ONLY with command "fastboot boot XXXXX.img" , where xxxx.img is name of recovery i have flash before, i can enter in correct twrp.
i don't know why, but i think i can't flash and fix the correct version of twrp. bhooooooooooo!
edit:
problem solved..
i have rename twrp img file in "recovery.img" and i have flash it in fastboot mode by pc..
i have try to enter in recovery with adbo command (adb reboot recovery) and phone reboot in correct twrp version;
then i have try to enter in recovery with hardware procedure (poweroff, volume up + power and release power when appear Mi logo, tap on "recovery") and it work;
and, in the end, i have try to nter in recovery mode by app "updater"
all works perfectly now!
Click to expand...
Click to collapse
Hi,, i've successfully unlocked my redmi 3 bootloader, and now there's root permission option in security app. I tapped it and confirmation prompt to get root acces appear, i click ok, then my device download something (my assume its root file), and reboot by it self after. Now i have rooted redmi 3 with unlocked bootloader but no superSU installed.
I want to install twrp recovery which is official now for redmi 3, i've read about dm-verity thing in our redmi 3 and still confused about it.
Can i just install twrp recovery thru twrp manager app from play store? If yes, can i go into twrp recovery via updater app.?
Thanks in advance.
you can install twrp by fastboot!
and then yes, you can enter in twrp by updater app
bucks_26 said:
Hi,, i've successfully unlocked my redmi 3 bootloader, and now there's root permission option in security app. I tapped it and confirmation prompt to get root acces appear, i click ok, then my device download something (my assume its root file), and reboot by it self after. Now i have rooted redmi 3 with unlocked bootloader but no superSU installed.
I want to install twrp recovery which is official now for redmi 3, i've read about dm-verity thing in our redmi 3 and still confused about it.
Can i just install twrp recovery thru twrp manager app from play store? If yes, can i go into twrp recovery via updater app.?
Thanks in advance.
Click to expand...
Click to collapse
Congratulations you just followed the official method of getting root access successfully, root access is not from SuperSU but from MIUI itself, it's in the Security app.
You can, but the phone won't boot anymore then, because of the dm-verity thingy. So in another word, you have to disable it by flashing a modified boot image, I'm not sure but some custom ROM might have come with the modified image already, but MIUI ROM definitely doesn't, it is certain you'd get a boot loop after flashed TWRP and try to boot into Android again. That's the simple explanation. And yes you can go to TWRP from updater app, it's the same thing as writing 'reboot recovery'.
Dikirim dari Redmi 3 saya menggunakan Tapatalk
Hi,
I unlocked my Honor 9 bootloader using the "fastboot oem unlock 'unlock key'" method.
After that it did low level reset or something of the sort and booted to Android.
After that I wanted to install TWRP using fastboot, the problem is that every time I do "adb reboot bootloader" I get a message the device cannot be trusted (see pic) and it boots to android.
I tried pressing power button, up button (this gets me to the recovery), but it always gets back to Android and not to fastboot.
What can I do???
Thank you
Return fully stock, then try again
PalakMi said:
Return fully stock, then try again
Click to expand...
Click to collapse
How do I do that, use the original recovery?
OK, I managed to get to the bootloader by turning off the phone, pressing the volume down button and connecting the USB cable.
I flashed twrp and somehow booted to the recovery I wanted to flash the supersu.zip but all the folders and file names in the sdcard were gibberish.
I rebooted and everything was ok (not gibberish) but instead of having twrp I got the original recovery back.
Since then even if I flash using fastboot the twrp recovery I keep getting the original recovery.
In the fastboot screen there's a message "Android reboot reason: bootloader NA reboot_enter_fastboot_common_func" is it normal? (see pic)
And one last question, should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
UPDATE:
I managed to get twrp working.
I did fastboot oem relock, and then unlocked the bootloader again, and it booted to twrp (without re-flashing twrp).
When I tried to flash supersu all the files were gibberish (see pic), what am I missing?
If I wipe data it seems fine, but then I boot to system to copy the supersu file and once I load twrp it is gibberish again.
Also should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
Appreciate any help I can get.
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Midhon58 said:
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Click to expand...
Click to collapse
yeah I figured as much.
Didn't think of using external SD, thanks, was about to try adb sideload, I assume it would have worked too.
Many thanks, the external sd did the trick
The Fastboot installation process goes all fine but device boots into Mi-Recovery by default. Currently Using Miui 9 Dev Rom (7.12.21 | Beta). This happened after I flashed the stock Dev rom after accidentally bricking my phone while unrooting through SuperSu's Full Unroot Option.
Bootloader is unlocked. Help asap plz.
Using The 4Gb 64Gb variant.
Hi,
if you flash Global Developer rom using Fastboot method, you will always flash a stock recovery with it.
There is a great manual how to unlock your device on official CZ and SK webpage created by local admins.
Just go to miuios.cz (translate it to ENG using browser like chrome or others) create an account to be able see the links.
Then on the main page scroll down to Redmi note 4 and check
[NÁVODY] - základné /Bootloader/TWRP/MIUI/ROOT
there is everything you need to unlock device with software you need.
All credits to miuios team.
Crys2perk said:
The Fastboot installation process goes all fine but device boots into Mi-Recovery by default. Currently Using Miui 9 Dev Rom (7.12.21 | Beta). This happened after I flashed the stock Dev rom after accidentally bricking my phone while unrooting through SuperSu's Full Unroot Option.
Bootloader is unlocked. Help asap plz.
Using The 4Gb 64Gb variant.
Click to expand...
Click to collapse
I think is a problem about installation process (I had the same problem with another phone), but you can still access twrp with your computer. Just use this command: Fastboot boot "twrp.img".
Update "twpr.img" with your own twrp´s file name.
Wait untill phone´s reboot (more than 15s.)
Then use it as usual
Good luck
XiaomiRedUser said:
I think is a problem about installation process (I had the same problem with another phone), but you can still access twrp with your computer. Just use this command: Fastboot boot "twrp.img".
Update "twpr.img" with your own twrp´s file name.
Wait untill phone´s reboot (more than 15s.)
Then use it as usual
Good luck
Click to expand...
Click to collapse
I ran into the same problem after unlocking the bootlader:
TWRP would not install -> [Vol+] + [Power] started only the MIUI recovery.
But after some search, I found that you have to:
enter in a terminal "fastboot flash recovery twrp-x.x.x-x-mido.img"
enter after that "fastboot boot twrp-x.x.x-x-mido.img"
My Note 4 then started in TWRP.
EDIT:
Corrected step 2
Crys2perk said:
The Fastboot installation process goes all fine but device boots into Mi-Recovery by default. Currently Using Miui 9 Dev Rom (7.12.21 | Beta). This happened after I flashed the stock Dev rom after accidentally bricking my phone while unrooting through SuperSu's Full Unroot Option.
Bootloader is unlocked. Help asap plz.
Using The 4Gb 64Gb variant.
Click to expand...
Click to collapse
After flashing twrp, directly from terminal boot to twrp and flash super su along with lazyflasher, after that reboot, when rebooted install official twrp app and super su app, and using the twrp app once again install twrp. That shld do.
MyNameIsRage said:
After flashing twrp, directly from terminal boot to twrp and flash super su along with lazyflasher, after that reboot, when rebooted install official twrp app and super su app, and using the twrp app once again install twrp. That shld do.
Click to expand...
Click to collapse
Tried This Still Not Working.
I directly booted from fastboot to TWRP
I Magisk Rooted then , which works fine now.
tinaeire said:
I ran into the same problem after unlocking the bootlader:
TWRP would not install -> [Vol+] + [Power] started only the MIUI recovery.
But after some search, I found that you have to:
enter in a terminal "fastboot flash recovery twrp-x.x.x-x-mido.img"
enter after that "adb reboot recovery"
My Note 4 then started in TWRP.
Click to expand...
Click to collapse
How did you get ADB commands to work in Fastboot? Having the same TWRP problem right now.
dancress said:
How did you get ADB commands to work in Fastboot? Having the same TWRP problem right now.
Click to expand...
Click to collapse
From a terminal from your PC. With a Windows open "cmd.exe".
tinaeire said:
From a terminal from your PC. With a Windows open "cmd.exe".
Click to expand...
Click to collapse
ADB doesn't work in Fastboot... fastboot.exe does. And that can only boot into itself (the bootloader), not the recovery.
Anyway, I solved the problem. Mine is a 4X not a Note 4X. Damn you Xiaomi... they are exactly alike!
dancress said:
ADB doesn't work in Fastboot... fastboot.exe does. And that can only boot into itself (the bootloader), not the recovery.
Anyway, I solved the problem. Mine is a 4X not a Note 4X. Damn you Xiaomi... they are exactly alike!
Click to expand...
Click to collapse
You are right, my mistake.
adb does not work and I mixed it up.
But I did test 'fastboot boot twrp-x.x.x-x-mido.img' in fastboot mode and it worked on my Note 4.
tinaeire said:
I ran into the same problem after unlocking the bootlader:
TWRP would not install -> [Vol+] + [Power] started only the MIUI recovery.
But after some search, I found that you have to:
enter in a terminal "fastboot flash recovery twrp-x.x.x-x-mido.img"
enter after that "fastboot boot twrp-x.x.x-x-mido.img"
Click to expand...
Click to collapse
As others have reported, I had the same issue too. I was able to boot to TWRP with the fastboot boot command above, but it looks like after you boot to the stock ROM (mine was MIUI V9.2.1.0.NCFMIEK as far as I remember), the TWRP recovery gets replaced by the stock one. After flashing LineageOS (official lineage-14.1-20180331-nightly-mido-signed.zip), I can now properly reboot to TWRP with Vol+ & Power.
Thanks for the tip @tinaeire :good:
Why aren't devs mentioning this in the instructions right after the recovery flash command? I'll never understand. I guess it's more MIUI's fault for being so weird about the bootloader.
TWRP boots stable
Press VOLUME-UP and POWER together, when you feel the vibration release the buttons.
-> boots into TWRP
If you hold the two buttons until you see the TWRP logo flash up and release them at that moment -> boots to MIUI.
Did that with phone mentioned below, TWRP 3.2.1, and MIUI Global 9.2 Stable.
I am also facing the same problem, please someone guide me thoroughly how to root my xiaomi redmi note 4 snapdragon global stable version. i have successfully unlocked my phone but i can't start it up in twrp recovery mode. please tell me all the steps and files necessary.
habib_561 said:
I am also facing the same problem, please someone guide me thoroughly how to root my xiaomi redmi note 4 snapdragon global stable version. i have successfully unlocked my phone but i can't start it up in twrp recovery mode. please tell me all the steps and files necessary.
Click to expand...
Click to collapse
Once you flash TWRP via fastboot then use command fastboot boot xxx.img
So, you'll be able to boot to TWRP, next flash magisk for MIUI, install lazyflasher.zip and reboot and check if TWRP sticks.
i have the same issue after flash the twrp and it reboot back to mi recovery instead. However i am using redmi K20.
Found out that the issue is the twrp.img file that you flash must be a correct one that your download for your device.
If it is not the correct file ( my case is using redmi k20 pro instead of redmi k20 twrp.img), i will always failed and stay at mi recovery.
Hi everybody i need your help,
I got an honor 9 STF-L09. I got bricked and I want to install the stock firmware because my phone doesnt on again. I have Twrp installed and unlocked bootloader but when i try to boot into system it says "Func NO: 10 (boot image)".
I tried to flash firmware from thi guide https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892 but nothing to do.
I tried to flash using twrp but the ionstallation fail everytime.
Is there someone that can help me with a stock firmware or even other firmwares that makes my H9 on againg.
Please help me I'am DESPERATE
Did you take a look here ?
http://droidvendor.com/download-8-0-0-360-c432-official-oreo-for-honor-9-stf-l09/
sorry, I'm not expert on this topic, it's the only help i can give you
What rom did you have before? EMUI 8 or 5.1?
JBolho said:
What rom did you have before? EMUI 8 or 5.1?
Click to expand...
Click to collapse
I had emui 8
leocap33 said:
I had emui 8
Click to expand...
Click to collapse
I will provide you with the files that (hopefully) will bring your device back to life. Just need to upload the first, i'll update this post with the link and instructions, hang on a second.
JBolho said:
I will provide you with the files that (hopefully) will bring your device back to life. Just need to upload the first, i'll update this post with the link and instructions, hang on a second.
Click to expand...
Click to collapse
thank you man
leocap33 said:
thank you man
Click to expand...
Click to collapse
In the link you will find Stock EMUI 8 Ramdisk, Recovery and System, as well as TWRP and a Kernel that fixes the possibility of losing the capacitive buttons. Download them into a folder on the root of your PC (for example C:\Temp)
https://www.dropbox.com/sh/88l72rypm6u1u94/AADtPyvsIFhyBl1mcJ5raTBZa?dl=0
I don't know what caused your boot to disappear, mine disappeared when i tried to unroot it from within SuperSU app (Big Mistake), but let's not be drastic just yet. You need Fastboot and ADB on your PC, turn off your phone, hold Volume - and connect the USB cable from the PC to the device. You should enter Fastboot mode. I hope your device is FRP unlocked as well.
Open a command line and input "fastboot devices" to make sure your device is connected
First let's try restoring Ramdisk, TWRP and Kernel:
Run "fastboot flash ramdisk STF-L09_ramdisk.img", then "fastboot flash recovery_ramdisk stf_twrp_oreo.img" and finally "fastboot flash kernel B360_fix_kernel.img"
After that just run "fastboot reboot" and see if it boots or not... This should take care of your problem, if not, let's go drastic:
Turn off the device and plug it in fastboot mode again onto your PC.
On the command line run "fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img" (this will flash stock recovery), and "fastboot flash system SYSTEM.img" (this will flash your system partition, in small bathes at a time, fresh.)
After that, just "fastboot reboot" and it should boot to your system (and without a factory reset!) If it bootloops for some reason, turn off the device, boot into stock recovery and wipe cache (or do a full factory reset, but that should not be necessary i think...)
Hope all this helps!
JBolho said:
In the link you will find Stock EMUI 8 Ramdisk, Recovery and System, as well as TWRP and a Kernel that fixes the possibility of losing the capacitive buttons. Download them into a folder on the root of your PC (for example C:\Temp)
https://www.dropbox.com/sh/88l72rypm6u1u94/AADtPyvsIFhyBl1mcJ5raTBZa?dl=0
I don't know what caused your boot to disappear, mine disappeared when i tried to unroot it from within SuperSU app (Big Mistake), but let's not be drastic just yet. You need Fastboot and ADB on your PC, turn off your phone, hold Volume - and connect the USB cable from the PC to the device. You should enter Fastboot mode. I hope your device is FRP unlocked as well.
Open a command line and input "fastboot devices" to make sure your device is connected
First let's try restoring Ramdisk, TWRP and Kernel:
Run "fastboot flash ramdisk STF-L09_ramdisk.img", then "fastboot flash recovery_ramdisk stf_twrp_oreo.img" and finally "fastboot flash kernel B360_fix_kernel.img"
After that just run "fastboot reboot" and see if it boots or not... This should take care of your problem, if not, let's go drastic:
Turn off the device and plug it in fastboot mode again onto your PC.
On the command line run "fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img" (this will flash stock recovery), and "fastboot flash system SYSTEM.img" (this will flash your system partition, in small bathes at a time, fresh.)
After that, just "fastboot reboot" and it should boot to your system (and without a factory reset!) If it bootloops for some reason, turn off the device, boot into stock recovery and wipe cache (or do a full factory reset, but that should not be necessary i think...)
Hope all this helps!
Click to expand...
Click to collapse
thank you a lot, u give me hope. When I return home I'll try everything
JBolho said:
In the link you will find Stock EMUI 8 Ramdisk, Recovery and System, as well as TWRP and a Kernel that fixes the possibility of losing the capacitive buttons. Download them into a folder on the root of your PC (for example C:\Temp)
https://www.dropbox.com/sh/88l72rypm6u1u94/AADtPyvsIFhyBl1mcJ5raTBZa?dl=0
I don't know what caused your boot to disappear, mine disappeared when i tried to unroot it from within SuperSU app (Big Mistake), but let's not be drastic just yet. You need Fastboot and ADB on your PC, turn off your phone, hold Volume - and connect the USB cable from the PC to the device. You should enter Fastboot mode. I hope your device is FRP unlocked as well.
Open a command line and input "fastboot devices" to make sure your device is connected
First let's try restoring Ramdisk, TWRP and Kernel:
Run "fastboot flash ramdisk STF-L09_ramdisk.img", then "fastboot flash recovery_ramdisk stf_twrp_oreo.img" and finally "fastboot flash kernel B360_fix_kernel.img"
After that just run "fastboot reboot" and see if it boots or not... This should take care of your problem, if not, let's go drastic:
Turn off the device and plug it in fastboot mode again onto your PC.
On the command line run "fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img" (this will flash stock recovery), and "fastboot flash system SYSTEM.img" (this will flash your system partition, in small bathes at a time, fresh.)
After that, just "fastboot reboot" and it should boot to your system (and without a factory reset!) If it bootloops for some reason, turn off the device, boot into stock recovery and wipe cache (or do a full factory reset, but that should not be necessary i think...)
Hope all this helps!
Click to expand...
Click to collapse
Hi sir I tried, everything flashes ok but when I reboot it continue bootloops until it enter into erecovery. I tried to wipe data but when I press the button to wipe cache after it displays a red '!' into the circle and the same for the wiping data.
sorry for my English, how can I solve ..? FRP was written "FRP unlock"
leocap33 said:
Hi sir I tried, everything flashes ok but when I reboot it continue bootloops until it enter into erecovery. I tried to wipe data but when I press the button to wipe cache after it displays a red '!' into the circle and the same for the wiping data.
sorry for my English, how can I solve ..? FRP was written "FRP unlock"
Click to expand...
Click to collapse
Everything flashes ok, no errors? What did you flash? Everything?
eRecovery is to rescue the device, that won't work with Oreo (at least not for me). The stock recovery you enter it by keeping the Vol + pressed and power up the device (just as TWRP), you can enter it? And it gives error when wiping the cache?
JBolho said:
Everything flashes ok, no errors? What did you flash? Everything?
eRecovery is to rescue the device, that won't work with Oreo (at least not for me). The stock recovery you enter it by keeping the Vol + pressed and power up the device (just as TWRP), you can enter it? And it gives error when wiping the cache?
Click to expand...
Click to collapse
yes it gives me an error while I wipe cache or factory data. I enter normally into recovery with vol+.
leocap33 said:
yes it gives me an error while I wipe cache or factory data. I enter normally into recovery with vol+.
Click to expand...
Click to collapse
What ROM exactly were you using? OldDroid's B360? Or some other?
I were using the stock emui8 I don't know the build number because I can't get it. My region is italy
leocap33 said:
I were using the stock emui8 I don't know the build number because I can't get it. My region is italy
Click to expand...
Click to collapse
The only explanation i see is that the EMUI8 you were using has something different from the one in OldDroid's thread... On mine i did exactly what i told you, those files are the ones i used on mine as well.
Right now you have everything stock right? Can you try to flash one of the Treble Roms? Either AOSP or RR-O?
You just have to download them (they're a system.img file) and run the "fastboot flash system system.img" command, go to recovery and factory reset. Your device should boot.
If everything fails, the only hope i see if to go to OldDroid's thread - https://forum.xda-developers.com/honor-9/how-to/stf-l09c432-how-to-install-oreo-h9-t3707729 and download the files, and follow the instructions on the OP to rollback to Nougat.
sonneper said:
Did you take a look here ?
http://droidvendor.com/download-8-0-0-360-c432-official-oreo-for-honor-9-stf-l09/
sorry, I'm not expert on this topic, it's the only help i can give you
Click to expand...
Click to collapse
I think the link you probided is a fake bull$hiting guide :
1) it states european C432 but provided two of the three files of a russian C10 firmware.
2) almost sure. the file provided won't flash the dload way as stated in guide.
leocap33 said:
Hi everybody I got an honor 9 STF-L09, my region is italy. I got bricked and I want to install the stock firmware because my phone doesnt on again. I have Twrp installed and unlocked bootloader but when i try to boot into system it says "Func NO: 10 (boot image)".
I tried to flash firmware from thi guide https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892 but nothing to do.
I tried to flash using twrp but the ionstallation fail everytime.
Is there someone that can help me with a stock firmware or even other firmwares that makes my H9 on againg.
Please help me I'am DESPERATE
Click to expand...
Click to collapse
OK, so you were on oreo, and now the nougat's service repair dload firmware are not working.
I'll start by asking:
-how do you get bricked, what did you do just before ?
Try this tool for honor 9:
https://forum.xda-developers.com/newreply.php?do=newreply&p=75084955
(xda link to russian tool)
https://forum.xda-developers.com/newreply.php?do=newreply&p=75661658
(xda link to english translated scripts)
http://4pda.ru/forum/index.php?showtopic=833645&st=2400#entry69940847
(pda link to russian tool)
Same here, I just have access to eRecovery and fastboot mode
I was on the last version (oreo) and I wanted root my phone so I have unlock bootloader and install twrp but after twrp install in the wipe my internal stockage was empty and when I wanted install supersu I have some error like failed to mount: data, failed to mount: cache, ect..
but I still had access to my phone
Except that I had to go through the eRecovery every time so I tried to look at the side of my errors mount and I tried unbrick with the software Huawei Multi Tool and images of a rom stock publish on the forum except that I had even more access to my phone but I no longer have the errors mount.. With Huawei Multi Tool I have try the recovery option but nothing, now I don't know what make
Hi everyone I tried all the tools given into this thread but no success, it seems like a big lost challenge
Tell us more..
so you were on oreo or nougat before brick ?
and now the nougat's service repair dload firmware are not working ?
how do you get bricked, what did you do just before ?
Yeah never see a sht like that, I guess we have to send our phones to a huawei repair center..
Ok you were on oreo emui8.