Pretty inexperienced with Andriod after taking the leap from IOS.
Rooted my honor 7 using Kingoroot everything worked fine then I let me phones battery die whilst at work came home to charge it up and now it's stuck in a boot loop/honor screen.
So far I have tried to let it automatically download the ROM using the EMUI recovery that fails completely.
I tried using HiSuite to recover that gets to 90% then gets stuck.
Finally I have tried every single honor 7 ROM i can find in an attempt to install via SD card every time I have it tells me version check fail.
Only had the phone couple of months anything I can do to recover it/repair?
Many thanks
Markus
did you unlock bootloader before rooting? you could use adb to flash stock rom....
next time dont follow youtube guides titled "how to root any android phone", on android theres way bigger change to bootloop or brick your device while messing with root, custom recovery and custom roms than on iOS. in this thread you will have all info beginner needs about honor 7 rooting, fixing and customizing: https://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
thelous said:
did you unlock bootloader before rooting? you could use adb to flash stock rom....
next time dont follow youtube guides titled "how to root any android phone", on android theres way bigger change to bootloop or brick your device while messing with root, custom recovery and custom roms than on iOS. in this thread you will have all info beginner needs about honor 7 rooting, fixing and customizing: https://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
Click to expand...
Click to collapse
Thanks for the reply and no I did not as I wasn't aware it needed to be done however in fastboot it says Phone Unlocked and the fastboot oem get-bootinfo also says (bootloader) unlocked.
Yet I am still unable to to flash as Command not allowed is appearing when I try.
I have tried following the guide to aquire my unlock password from the huawei site how ever it tells me my details i.e serial number and imei are incorrect.
Really appreciate the help , thank you
Markus
markuswhiteus said:
Thanks for the reply and no I did not as I wasn't aware it needed to be done however in fastboot it says Phone Unlocked and the fastboot oem get-bootinfo also says (bootloader) unlocked.
Yet I am still unable to to flash as Command not allowed is appearing when I try.
I have tried following the guide to aquire my unlock password from the huawei site how ever it tells me my details i.e serial number and imei are incorrect.
Really appreciate the help , thank you
Markus
Click to expand...
Click to collapse
i think rooting app unlocked it wrong(caused bootloop) and messed something up....
Get the B380 update from Honor site and do a forced update ( if you've already been on B380).
It should work after that.
Sebster97 said:
Get the B380 update from Honor site and do a forced update ( if you've already been on B380).
It should work after that.
Click to expand...
Click to collapse
Tried that get a version check fail.
btw did you install xposed? it doesnt work on emui... just bootloops
What version are you current on? B380?
I assume that this KingoRoot thing messed up your SYSTEM Partition and thats why it bootloops. To fix this do this:
If you're on B380, go and get the B380 full update from the official Honor site and extract it so that you can see the UPDATE.APP file.
Then get the Huawei Update extractor from here : https://forum.xda-developers.com/showthread.php?t=2433454
Open it and extract the SYSTEM.img and the BOOT.img
If you are familiar with adb do this: (if not, ask what to do)
copy SYSTEM.img to your adb folder. Connect your phone in fastboot mode, and enter in cmd: "fastboot flash boot boot.img"
and after its done:
"fastboot flash system SYSTEM.img" (everything without quotation marks obviously)
It will take some time, be patient. If it's done just write: fastboot reboot
and lets hope it works for you !
Sebster97 said:
What version are you current on? B380?
I assume that this KingoRoot thing messed up your SYSTEM Partition and thats why it bootloops. To fix this do this:
If you're on B380, go and get the B380 full update from the official Honor site and extract it so that you can see the UPDATE.APP file.
Then get the Huawei Update extractor from here : https://forum.xda-developers.com/showthread.php?t=2433454
Open it and extract the SYSTEM.img and the BOOT.img
If you are familiar with adb do this: (if not, ask what to do)
copy SYSTEM.img to your adb folder. Connect your phone in fastboot mode, and enter in cmd: "fastboot flash boot boot.img"
and after its done:
"fastboot flash system SYSTEM.img" (everything without quotation marks obviously)
It will take some time, be patient. If it's done just write: fastboot reboot
and lets hope it works for you !
Click to expand...
Click to collapse
Tried that gota wait for the unlock code to flash the ROM on and no I never used xposed
Related
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
also to note....you dont have to install linux to get s-off....if you follow my guide you can do it straight from a live disk rather than installing it....so it wont erase or mess up your windows partition at all
Solved!
Thank you, Mjones, I finally got it! I knew it was much easier than I was making it out to be. I was missing the kernel! Yeah, a crucial part in the process, I know
I first ran CWM and flashed the ROM over and ran the .zip through recovery (which I couldn't understand at first as I could never find it in the directory) but the installer would only go 50% and would fail... makes sense why now lol
I later flashed TWRP and backed up again after recovering from the fail. I flashed over the kernel and voila! So simple... Had to slap myself.
Thanks again! Case solved.
REV3NT3CH, that is sweet!! I have been hoping there is a way to gain s-off with Windows. I have 7 at work and 8.1 (which I can't get anything to work on) at home. I actually have to focus on work today haha so I'll look into the method and try it out tomorrow if I can. Thanks for all of the help.
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Sorry, don't know anything about that phone.
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Did you try this first? (Right from Moto's site)
Perform a factory reset using external keys
1. Power off the phone, press and hold volume down button, press power button
2. Screen will come up with "Fastboot", press Vol down key to cycle through choices until you get "Android Recovery", then press Vol up key
3. Wait for the "triangle ! / Android" screen then go on to step 4
4. Press both Vol up and Vol down key simultaneously. A menu will come up
5. Tap on Vol down key until "wipe data/factory reset" is highlighted, and tap Power key. Another Confirmation screen will come. Tap on Vol down key until coming to Yes and tap Power key
6. After userdata is cleared, the "reboot system now" option will be highlighted by Default. Tap Power key
7. Phone will reboot to initial setup screen.
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
not working
hariom.gupta11 said:
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
Click to expand...
Click to collapse
not working on my 4c. write successful but when reboot is completed it goes to previous state.
"the user data partition can no longer be used"
zb602kl_x00tdb
L0RDZ3RO said:
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
Click to expand...
Click to collapse
I have same problem on asus zenfone max pro m1 I bought it online said used and now working
can't boot into recovery.
can't boot into system.
Only EDL Mode and Fastboot Mode, but fastboot is Locked whic I cant unlock because I cannot boot into system to toggle USB Debugging and allow OEM unlocking
Qualcomm is harder to flash than MTK that can use SP FlashTool.
on this I use QFIL but keeps "sahara error". I tried searching and try moving firmware file to bin but no Luck. I'm currently trying different version of QFIL Tool.
If it FAILS my only HOPE is to use MUT-QCfire which will Require a "SmartCardReader" Which is a bit pricey and I don't even know if it will work on my device.
I screwed up my phone lol, when I was updating it to oreo, I didn't know that the update.zip file was corrupted.
Now I'm stuck on
Error!
Func NO : 9 (hifi image)
Error NO : 1 (security image failed)
My version was...
STF-L09C185B170
What i tried to install that failed is...
STF-L09C185B361 (8.0.0.361)
I can still go to fastboot with everything unlocked, I can also flash a twrp recovery, but only by typing flash recovery_ramdisk(instead "recovery"), and when I try to do the update method by pressing vol up, vol down, and power, it doesnt take me to the update section, it just show me a crashed screen, then goes back to error message.
I also tried volup and power, I can't seem to go to twrp(I think booting to twrp and flashing zip files can be one of the only ways to fix this). Is there a way to go to twrp recovery using fastboot?
I've also tried flashing extracted files from update.app manually, it doesn't work. Some files can be flashed, while some can't.
Please I'm begging u guys, pls halp :crying:
also I guess the lesson here is: double check if your file is corrupted before installing/flashing
First, what is the way you took triying to update ?
(When done from system UI, official or FF, there is an integrity check of downloaded files.)
It seems you got oreo partition scheme during your failed update.
First see this guide:
https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
Try to restore using erecovery. (download and update firmware via wifi)
If not working you could use HWOTA8.
For launching recovery (stock or twrp) from bootloader type "fastboot reboot recovery".
oslo83 said:
First, what is the way you took triying to update ?
(When done from system UI, official or FF, there is an integrity check of downloaded files.)
It seems you got oreo partition scheme during your failed update.
First see this guide:
https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
Try to restore using erecovery. (download and update firmware via wifi)
If not working you could use HWOTA8.
For launching recovery (stock or twrp) from bootloader type "fastboot reboot recovery".
Click to expand...
Click to collapse
I downloaded the oreo file using a browser and installed it with HWOTA, everything got inserted into my device, but the update failed and it gave me the error when I reboot. Also I can't get to erecovery or upgrade mode(that's the crashed screen), and "fastboot reboot recovery" doesn't work, it just show me a list of commands(which I assume happens if the command is invalid).
Ok I'll try HWOTA8, but I need to configure it so it recognizes my device, only my adb recognizes it.
Do 'fastboot devices work'?
Try english hwota8.
oslo83 said:
Do 'fastboot devices work'?
Try english hwota8.
Click to expand...
Click to collapse
Nah, I figured it out, I backed up my adb folder and just merged hwota8 with it. Yes, it does work.
Btw how do I fully turn off the device? it just keeps bootlooping if i hold down the volup and power key, maybe this is the reason why I can't get into twrp recovery.
My only hope is that I can flash something on fastboot that will let me go to update mode(or erecovery) or twrp.
Like.. anything, even boot.img fails when I try to flash it. It must be stuck on oreo partition.
Also I did considered dc phoenix, but I don't have the money to pay for an account. Man, why is unbricking not free on huawei devices? That guy prolly made a fortune by now(for holding everyone with unbrick leverage lel), and it's a huge mistake for me to fiddle with a huawei device, it has so many problems with twrp and root.
If anyone can find a way to do unbrick it, like anything, that would be great.
So you didn't manage to use honor9's hwota8 ?
oslo83 said:
So you didn't manage to use honor9's hwota8 ?
Click to expand...
Click to collapse
I used it but it didn't worked, I need to be either booted in the phone's os or inside twrp recovery bec. all of the commands executed by hwota8 are adb shell, not fastboot. Like I said, I only have access to fastboot, but I'll try again tomorrow. This is taking a lot of my time and I'm having panic attacks that I may not be able to fix this lol. Oh yeah, thanks for helping out.
Note: Since Oreo, partitions names have changed ; "recovery" changed to "recovery_ramdisk" now.
Use this command to flash recovery: fastboot flash recovery_ramdisk YourStockOrTwrpRecovery.img
Use oreo stock recovery or oreo twrp.
But I thought with hwotas available for honor 9 you started from bootloader...
oslo83 said:
Note: Since Oreo, partitions names have changed ; "recovery" changed to "recovery_ramdisk" now.
Use this command to flash recovery: fastboot flash recovery_ramdisk YourStockOrTwrpRecovery.img
Use oreo stock recovery or oreo twrp.
But I thought with hwotas available for honor 9 you started from bootloader...
Click to expand...
Click to collapse
I already did that, read the OP. Like I said, I can't boot into any recovery, not twrp not stock, not even upgrade mode, nothing.
As for hwota8, nope, it doesnt start from the bootloader, it's already trying to use the adb shell commands.
Anyway I'm taking all chances, I'm trying to research oreo's partitions names, and I'm also trying to find out how to bypass this message "FAILED (remote: Command not allowed)" bec. it might be the only way I can salvage this phone.
edit: ok im trying hwota8 again, maybe i missed something, and yes it has fastboot, sorry i was rushing but im trying again now, i'll post my progress later
I'm trying to flash twrp.I have gone step by step I can't think of anything that I forgot to do, I did everything that was mentioned here and other places even my device is detected in both adb & fastboot.but I can't flash twrp
I tried these:
1-adb devices
returned a serial number
2-rebooted to bootloader using:
adb reboot bootloader
3-fastboot devices
returned device id(I think)
4-fastboot flash recovery.img
returned error
5-fastboot flash recovery recovery.img
returned error either "command not allowed" or "Operation is not permited"
6-Different combinations of above commands plus flashing command
What is flashing .... in fastboot.It doesn't work. It acts like an unknown command. Does anyone know how to use it correctly? Help of fastboot didn't help
(Attached screenshots=CMD:Command Line in Windows,SCL-U31:My phone screen in fastboot mode)
See it for yourself in screenshot please
Thanks in advance!
P.S I read a lot of other threads,I Couldn't Find anything that helped me solving the problem,So,Any further idea?
No luck still
Guys I'm tryings to flash an stupid twrp recovery or at least get back to original recovery(All firmware packages are in UPDATE.app format and I can't flash it since It says "recovery image verification failed) . System needs its original recovery to do factory reset,right?
Tell me where to go!!!
Any luck? At least please tell me where to go!! I even mentioned it in a lot of other related xda threads they simply tell me it's a stupid OFF Topic replay or thread. I might be a junior member in xda but it's been years that I worked with a lot of phones and now I'm pretty experienced. Bad luck of mine I damaged my note 3 and got this stupid Y6. It was hard to root unlocking bootloader and now I can't flash twrp in fastboot or whatever. Wishing there was a proper tool like odin for devices like this so it was easy to flash twrp. Anyway.
HELP ME PLEASE!!
flightover588 said:
Any luck? At least please tell me where to go!! I even mentioned it in a lot of other related xda threads they simply tell me it's a stupid OFF Topic replay or thread. I might be a junior member in xda but it's been years that I worked with a lot of phones and now I'm pretty experienced. Bad luck of mine I damaged my note 3 and got this stupid Y6. It was hard to root unlocking bootloader and now I can't flash twrp in fastboot or whatever. Wishing there was a proper tool like odin for devices like this so it was easy to flash twrp. Anyway.
HELP ME PLEASE!!
Click to expand...
Click to collapse
What error gave you when you tried to do this command "fastboot flash recovery twrp.img"
Be sure to have usb debugging enabled.
Thespartann said:
What error gave you when you tried to do this command "fastboot flash recovery twrp.img"
Be sure to have usb debugging enabled.
Click to expand...
Click to collapse
Of course I did. And also device is being detected in both adb and fastboot.
As I already mentioned I used flash recovery recovery.img(or twrp.img I have two versions of recovery that I can flash)
The error is=remote operation is not allowed or sometimes operation is not permitted(which seems to have same meaning )
flightover588 said:
Of course I did. And also device is being detected in both adb and fastboot.
As I already mentioned I used flash recovery recovery.img(or twrp.img I have two versions of recovery that I can flash)
The error is=remote operation is not allowed or sometimes operation is not permitted(which seems to have same meaning )
Click to expand...
Click to collapse
OK then.
You can root your device with kingroot/kingoroot, it worked in the past for Huawei Y6, after you rooted your device install flashify and press on "Recovery image" after you granted root access to the app.After that click on select file, download this recovery for y6: https://www.androidfilehost.com/?fid=962187416754472815 and flash the recovery with Flashify.
Done!
I am not responsible for Bricked devices!
After you done all of that you can flash an custom ROM and I recommend to root with magisk. Always make an backup when flashing a ROM!
If I helped a Thanks is appreciated
Thespartann said:
OK then.
You can root your device with kingroot/kingoroot, it worked in the past for Huawei Y6, after you rooted your device install flashify and press on "Recovery image" after you granted root access to the app.After that click on select file, download this recovery for y6: https://www.androidfilehost.com/?fid=962187416754472815 and flash the recovery with Flashify.
Done!
I am not responsible for Bricked devices!
After you done all of that you can flash an custom ROM and I recommend to root with magisk. Always make an backup when flashing a ROM!
If I helped a Thanks is appreciated
Click to expand...
Click to collapse
You uploaded a twrp recovery on AFH just for me? Thank you,man!I appreciate your help. I really do! But Believe it or not I already tried flashify,Rashr and flashfire. These three cause same thing,when I reboot to recovery it says "recovery image verification failed"Then quickly goes to fastboot&rescue mode where I can't still flash twrp using flash command. Referring to firstb post
flightover588 said:
You uploaded a twrp recovery on AFH just for me? Thank you,man!I appreciate your help. I really do! But Believe it or not I already tried flashify,Rashr and flashfire. These three cause same thing,when I reboot to recovery it says "recovery image verification failed"Then quickly goes to fastboot&rescue mode where I can't still flash twrp using flash command. Referring to firstb post
Click to expand...
Click to collapse
Not nice to hear that.
What you could try to do is:
Factory reset/Install an update.app made for SCL-U31 from recovery
Enable Usb debugging again
Reinstall usb drivers (HiSuite)
Lock&Unlock your bootloader again
Try to flash TWRP
Im happy if this worked and i am sorry if i wasted your time, sometimes this happens if you don't have HiSuite installed.
You could try this too:
adb reboot bootloader
adb kill-server
fastboot flash recovery recovery.img
fastboot reboot
Attention, install HiSuite to your PC, Connect the Phone to the PC with the cable, make sure You have usb debbuing is enabled and accept any dialogs that show in your home screen(They do not show on lockscreen) wait so HiSuite installs on the phone(An dialog should show up on the PC) and try flashing TWRP again.
Good luck
flightover588 said:
Guys I'm tryings to flash an stupid twrp recovery or at least get back to original recovery(All firmware packages are in UPDATE.app format and I can't flash it since It says "recovery image verification failed) . System needs its original recovery to do factory reset,right?
Click to expand...
Click to collapse
Is your boatloader unlocked?
You can find about by typing
fastboot oem devices-info
MANUALLY INSTALLING FULL NOUGAT 7.11 FIRMWARE 2018/03/15(security_patch 2018-02-05) (RECOVERY, BOOT, SYSTEM) Even If Its Soft Bricked Because You Messed Up Somewhere. Files Here Are For Asus Zenfone 3 Zoom ZE553KL Z01HD WW Sku .
Its The Last Nougat Update Before Oreo Was Released.
MORE FIRWARES HERE
Story Time:
As I Remember It.....Condensed Version, This Was Over A Few Days Of Trial And Error, Mainly Because Adb SideLoad Refused To Flash Asus's Stock Firmware Zip Files.
I Messed Up My Friends Asus Zenfone 3 Zoom, ZE553KL.
He Bought Used, He Quickly Updated To Oreo From Within The Phones Update But Was Having Missed Texts And Slow Lte(4g) Speeds, He Wasnt Sure If It Happened On Nougat Which The Phone Was On Originally.
Downgraded To 6.01, Installed Twrp, Magisk, Still Having Same Issues, Flashing An Update Zip W/a Modded Updater Script Via Twrp Caused A Soft Bricked Phone, It Never Completed The Flash, Twrp Backup Didnt Work, Factory Reset A No Go, Couldn't Manually Flash Stock Rom As Adb Sideload Always Gave Errors, Fastboot System images Didnt Help For One Reason Or Another, Phone Was Just Bootlooping Back To The Unlocked Bootloader Menu.
Down Loaded Alot Of Stuff, Read Countless Pages, And Somehow Got The Right Firmware Files(recovery, boot, system img files) That Was Flashable Via Fastboot Extracted From A Zip, My Fix Is Below. These Are Not My Files But I Cant Remember Where I Got Them From As I Dl-ed Alot Of Stuff Trying To Get This Phone To A Running State. No I Havent Tried Oreo Yet, He Has His Phone Back Now And Not Sure When He'll Let Me Play With It Again, Lol.
UPDATE TO THIS STORY
HOWTO FLASH
PREREQUISITES:
Make A Nandroid Backup
If Bootable Remove/Signout Of Google Account
(Might Work With Locked Bootloader, IDK)
Ze553kl(Zenfone3 Zoom) Phone With Unlocked Bootloader(used unlocker apk from asus website when phone was in running state)
Unlocking Bootloader App Available From Asus - was for upto nougat 7.11
Usb Asus Drivers
Usb Debugging Enabled On Phone, Maybe Not But Wont Hurt To Try
Adb Fastboot Program(Included)
Recovery, Boot, And System Img Files Of Nougat 7.11(Included)
Computer Running Windows
Usb Data Cable For Phone
ON PHONE-
If Bootable Enable Usb Debugging, Uncheck Verify Apps Via Usb, Install From Unknown Sources, Remove Google Account
Backup Internal Sdcard - Most Def
Remove Sdcard, Just In Case
Put Phone Into Fast Boot Mode- Unplugged, Phone Powered Off - Vol Up + Power Button Pressed, Hold Both Until Screen Comes On.
Plug Usb In Cable To Phone From Pc.
ON COMPUTER-
From The Download Section Below Dl ADB_FASTBOOT_1.4.1.ZIP File And Extract It Into A New Empty Folder.
Download And Copy The Three .Img Files From The Download Section Below Into This New Adb Folder
HOW TO RUN ADB VIA COMMAND PROMPT? -
From Within Adb-fastboot Folder You Created, Nothing Selected, Hold Down The Shift Key Then Use The Right Mouse Button To Click In Empty Space In The Adb-fastboot Folder, Select "Open Command Window Here" From The Menu That Pops Up.
From Within Command Prompt Type-
Adb Devices
It Should Output A Device With A String Of Letters And Numbers, Thats Your Phone.
Next Steps Will Install Nougat 7.11 And Consequently Wipe Your Phone
Run These 5 "fastboot" Commands One At A Time.
When Each Step Is Completed Run The Next Command, You Can Copy And Paste These Five (5) Fastboot Commands Into The Command Prompt Window
----------------------------------------------------------------------
1.
Code:
fastboot flash recovery recovery-zoom-7.11.img
2.
Code:
fastboot flash boot boot-zoom-7.11.img
3.
this one @ ~4gb will take awhile to initialize and complete, patience needed
CAN REDO THIS SYSTEM FLASH NOW TO MAKE SURE IT "STICKS"
Code:
fastboot flash system system-zoom-7.11.img
4.
wipes internal sdcard
Code:
fastboot format userdata
5.
Code:
fastboot reboot
-------------------------------------------------------------------------------------------
if you were successfull it will boot into 7.11, takes about 3-5 mins to boot.
IF DID NOT FLASH PROPERLY OR ODD BEHAVIOR AFTER REBOOT THEN REDO STEPS AGAIN....ELSE KEEP READING!
------------------------------------------------------------------------
IF STILL BRICKED OR ODD BEHAVIOR BUT CAN BOOT TO BOOTLOADER/FASTBOOT THEN DO THESE COMMANDS WHEN IN FASTBOOT MODE
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
THEN RE-BOOT BACK INTO BOOTLOADER AND DO THE FLASH FOR 7.11 FIRMWARE
STILL HAVING ISSUES, RESTORE USING TECH FW THAT REFLASHES ALL MDMS, RADIOS, DRIVERS ETC FROM HERE
[FW] 7.1.1 & 6.0.1 Service Tech Firmwares - Debrick - Upgrade - Downgrade
- -------------------------------------------------------------------------------------
disclaimer im not responsible for yours or anyone elses devices, do at your own risk
DOWNLOADS
PHONE FILES ARE FROM A Asus Zenfone 3 Zoom ZE553KL WW SKU FIRMWARE Version WW-71.60.139.30 2018/03/15
RECOVERY-ZOOM-7.11.IMG
md5 03d8358e1341a73b5a492c12e3dbe39e
BOOT-ZOOM-7.11.IMG
md5 1ad55f9852d56b79a95654173af5649a
SYSTEM-ZOOM-7.11.IMG
md5 7217f778701c988271739ab18fb0fb30
ADB_FASTBOOT_1.4.1.ZIP
..
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Deleted. Double post
Naman Vashishth said:
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Click to expand...
Click to collapse
What do u mean by raw. In what format is it in.
I've converted oreo stock firmware .dat files to .img files but I can't test them as I don't have the phone. My friend seems happy on nougat and I don't think he'll let me flash it on his phone.
I haven't tried dl-ing official stock and seeing if phone will see it as an update to manually self install via nougat recovery or maybe to try adb sideload again.
Naman Vashishth said:
I can provide you latest system,boot, recovery.img files if you want...
Click to expand...
Click to collapse
Please do - I could sure use them.
Work very well !
ciao
God bless you! You made my quite dead phone, live again!
Thank you
I can't update to Oreo via ota... do you know why?
the op here. lol, my friend dropped the phone and now its dead screen, no display/no touch but phone still works.
he doesnt want to get a screen for it as it will cost almost as much as he paid for it.......so its mine now.
been flashing stuff to it, gave it a very hard soft brick, still dealing with that.
my goal was to run it remotely but get adb/usb debugging enabled and get pc trusted by phone. i thought he wanted to sell it as is but decided to give to me to do whatever i want to it
got out of the hard soft brick, installed twrp, use twrp cli, twrp backups and restore, rooted w/magisk, installed 6.0.1 (fluked it), 7.11 using my method above with the extra erase commands, removed frp, got adb /usb debugging enabled and device adb authorized by hacking , got vysor, a remote control mirroring app running, all without a working screen.
i'll write up a tut for any1 else that needs help. fyi, weak screen if dropped even short distance, but he had no cover, but pretty to hard to brick it, imo, ymmv
So can i downgrade my phone from android 8 to 7.1.1 following this process.
kingairtel08 said:
So can i downgrade my phone from android 8 to 7.1.1 following this process.
Click to expand...
Click to collapse
yes, i went from 8.0 to 7.11 then to 6.01
more fw here https://forum.xda-developers.com/ze...fw-7-11-6-0-1-service-tech-firmwares-t3850000
Bro i am on 8.0 and want to unlock bootloader and root it n enable cam2api in it, as unlocker nt working in android 8.0 so i want to back to 7.1.1. thank u bro,i will try it tonight.
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
kingairtel08 said:
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
Click to expand...
Click to collapse
after flashing did u, in stock recovery, do a factory reset and wipe caches aka wipe user data in fastboot.
else do a complete wipe as outlined in op
yes bro i m on stock recovery ,did wipe cache etc.
kingairtel08 said:
yes bro i m on stock recovery ,did wipe cache etc.
Click to expand...
Click to collapse
does etc mean factory reset?
did u do the extra procedure to completely erase everything as posted in op in the section of when still having issues
yes bro. i followed all steps .
kingairtel08 said:
yes bro.
Click to expand...
Click to collapse
yes to which
this?
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
if yes then do a full restore of radio, mdm etc from here using method 1 or 2
https://forum.xda-developers.com/att-s7-edge/how-to/fw-7-11-6-0-1-service-tech-firmwares-t3850000
i did all this steps then flash firmware img.
kingairtel08 said:
i did all this steps then flash firmware img.
Click to expand...
Click to collapse
which method did u use from the link i posted
bro i dnt have the 7.1..1 zip file ,i used ur 7.1.1.img file,used method 2.
i will try once again ,wil reply within 2hours.
bro i want to unlock my phone whats why i downgrade,but after downgrading checked official unlock tool gives the same network error that gives on android 8.0.is there any way to unlock it on this 7.1.1 firmware?
I recently bought an unlocked Moto G Play 2021 with the intent of learning how to flash custom rom's etc. The steps I've done so far are below.
Went to Motorola's site and got the code to unlock the bootloader
Waited for the "OEM Unlock" button to be available in the Developer Options menu.
Followed the directions Here to try to get an unofficial version of TWRP installed.
when I type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img Using the vbmeta.img from the link above, I get some kind of anti-rollback error and can't boot to recovery.img
So far, what I've found says I need to be on Android 10 for this to work but I can't find a stock rom of Android 10 for this device. Electimon posts AOSP builds for this phone Here so I assume there's a way to get this to work, I just don't know what it is and I've gone through these threads a few times now and can't piece it together. Any assistance would be greatly appreciated.
Additionally, thanks Electimon for doing those AOSP builds.
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Luiz Vinicius said:
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Click to expand...
Click to collapse
I'm not sure entirely what happened, but after I used the TWRP app my phone bricked and I had to use the Lenovo rescue app on my pc to factory reset it.
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
svoc said:
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
Click to expand...
Click to collapse
Thank you for the response!
I made sure my phone was on wi-fi and checked for updates. I then rebooted to fastboot and flashed recovery to the MotoGuamnaFixed2.img. I still got a blank screen when I tried to reboot to recovery. I then rebooted to fastboot manually and did
fastboot flash recovery_a MotoGuamnaFixed2.img
fastboot flash recovery_b MotoGuamnaFixed2.img
It said ok both times, and when I try to reboot to recovery, I get a blank screen that I can't interact with. Pressing the power and volume buttons does nothing. Rebooting and letting the phone go through the boot process, to include waiting for the warning about the unlocked bootloader to go away results in a blank screen.
I also tried booting to fastboot and selecting "Recovery Mode" from the fastboot menu. Same result. That being said, I followed the instructions in the second link anyway, which are
fastboot -w
fastboot update (filename).zip
Now my phone has a blank screen I cannot interact with, but when I type "adb devices" I see the phone. Typing "adb shell ls -l" shows there is definitely a file structure there.
Just download the rom for the version that your device is unzip it and manual flash each one to the correct spot except recovery flash the twrp and then reboot and let me know look at flash file.xml to see where to flash each IMG and bin to make shur you download your rom and not another one for the same device but different carrier what it sounds like to me is happening is you downloaded the wrong ROM when you tried to do a force update
Send me a screenshot of your about device screen please I might need to make a change to a few things to get it working
I'm stuck in a boot loop right now. WIll the output from fastboot getvar work?
What carrier do you have
Download your rom first then follow my last post to get it back out of a bootloop
svoc said:
What carrier do you have
Click to expand...
Click to collapse
It's an unlocked phone, no carrier, no SIM. I did the factory reset with the Lenovo rescue tool and sent you the screen shot of the device info page.
Update - svoc has spent a crap ton of his personal time trying to help me with this. I've learned a bunch and wanted to publicly acknowledge his willingness to go way above and beyond trying to get this working.
I don't understand why I can't get twrp to boot I'm not for shut what the problem is if any one has any idea please let me and I will try
Big thanks to svoc for all the phone calls and troubleshooting my device, that is apparently possessed by at least 3 demons and a donkey. There are two links below. The first is the link to the intstructions that worked.
The second is to the compressed file that gave me a degoogled android. It's really, really basic and you'll have to side load the app store of your choice onto the device but it works.
*NOTE* I have not used a sim card or tested the cellular capability. If you do the things below and it doesn't work, reboot to bootloader and flash the radio.img with the one from your stock rom, which can be obtained from lolinet.
Any custom ROMs out there for Moto g play 2021 (guamna)?
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
forum.xda-developers.com
https://github.com/phhusson/treble_experimentations/releases/download/v412/system-squeak-arm64-ab-vanilla.img.xz