hi all,
i have a rooted vivo air lte with supersu.
i wanted to install magisk with the manager 8.0.3 (the boot.img from stock rom i extracted to downloads folder) by choosing direct install.
now the phone hangs on the bootlogo.
i can boot into recovery and choose "apply update from adb"
i installed fastboot and adb on the pc.
in the terminal command "adb devices" i see "devicenr sideload".
when i enter fastboot devices, there is no device shown.
im not sure if i have unlocked the bootloader when i rooted the phone a year ago..
so what do i have to do now to get it booting again?
thanks for the help!
schlunk said:
in the terminal command "adb devices" i see "devicenr sideload".
Click to expand...
Click to collapse
Device is configured to get booted in "Sideload" mode what is a variant of ADB mode.
Try this
Code:
adb devices
adb reboot
to return to "Normal" mode.
no, this is what i have chosen in the recovery, otherwise i dont get any device listed in the terminal..
@schlunk
Once being in the Android Recovery Mode and you select option Reboot system the Android device simply gets restarted: the actually configured ADB mode herewith doesn't get changed / reset.
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
schlunk said:
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
Click to expand...
Click to collapse
QFIL is the answer.
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
schlunk said:
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
Click to expand...
Click to collapse
https://firmwarefile.com/blu-vivo-air-lte-v0010uu
https://www.youtube.com/watch?v=MdknZvaTwl4
thats exactly the file i downloaded to extract the boot.img and see what happend
i dont want to flash the complete stock firmware again with the risk that my phone is bricked after that.
there must be some easier solution for this??
cant i just flash what magisk messed up?
schlunk said:
there must be some easier solution for this??
cant i just flash what magisk messed up?
Click to expand...
Click to collapse
Nope, I don't think there is.
Depends if that boot is same that was in your device. See the video
and the thread too: https://forum.hovatek.com/thread-31476.html
The boot should be the same, the firmware is exactly the same like in the phone regarding the label.
So with this linked method, flashing a single partition means, the boot.img can be flashed solo, without the need of flashing the whole firmware?
And when that doesnt work, i still could flash the whole firmware then as last resort?
That what I would do... Good luck!
Related
[[ SOLVED ]]
I was trying to flash a rom and I did wrong.
The phone got stuck on the white HTC screen.
I'm trying to get it back, the problem is that when I connect to the pc is not recognized. I installed SDK Tools, adb, drivers and all.
All In One Toolkit run and try to flash the boot.img but it says "error: device not found"
I run adb commands but it says the same thing, "error: device not found"
I tried it with Venom Flasher but I can not solve.
I uninstalled and went back to install the drivers, but I still have the same result, I run out of options.
When I turn the phone enters fastboot, I can access the recovery, but the phone at this time does not rom, dead.
By mistake I went to lock the bootloader but today I unlock it again with the All In One Toolkit and the bin file, so do not understand why if the file could flasher to unlock the bootloader again, but when trying to flash the boot.img or execute commands like: adb devices, adb reboot bootloader throws the error "device not found"
I appreciate it can help me ...
rikrdoVe said:
I was trying to flash a rom and I did wrong.
The phone got stuck on the white HTC screen.
I'm trying to get it back, the problem is that when I connect to the pc is not recognized. I installed SDK Tools, adb, drivers and all.
All In One Toolkit run and try to flash the boot.img but it says "error: device not found"
I run adb commands but it says the same thing, "error: device not found"
I tried it with Venom Flasher but I can not solve.
I uninstalled and went back to install the drivers, but I still have the same result, I run out of options.
When I turn the phone enters fastboot, I can access the recovery, but the phone at this time does not rom, dead.
By mistake I went to lock the bootloader but today I unlock it again with the All In One Toolkit and the bin file, so do not understand why if the file could flasher to unlock the bootloader again, but when trying to flash the boot.img or execute commands like: adb devices, adb reboot bootloader throws the error "device not found"
I appreciate it can help me ...
Click to expand...
Click to collapse
ADB commands are only recognized in recovery or when system is running. re-unlock your bootloader first. you can reboot into bootloader by pressing and holding power & volume-down button. navigate using volume buttons and enter fastboot by pressing power button. Now you can flash boot.img with "fastboot flash boot boot.img" or using any One X+ compatible toolkit. If it doesn't work, try installing latest HTC sync on your computer to get latest drivers. you can uninstall htc sync later again, the drivers will remain installed.
Here's a guide how you can setup adb/fastboot on cour computer, also contains useful information for beginners: http://forum.xda-developers.com/showthread.php?t=2213910
reaper90 said:
ADB commands are only recognized in recovery or when system is running. re-unlock your bootloader first. you can reboot into bootloader by pressing and holding power & volume-down button. navigate using volume buttons and enter fastboot by pressing power button. Now you can flash boot.img with "fastboot flash boot boot.img" or using any One X+ compatible toolkit. If it doesn't work, try installing latest HTC sync on your computer to get latest drivers. you can uninstall htc sync later again, the drivers will remain installed.
Here's a guide how you can setup adb/fastboot on cour computer, also contains useful information for beginners: http://forum.xda-developers.com/showthread.php?t=2213910
Click to expand...
Click to collapse
Yeah, try doing that. I locked boot loader again but still had no results. What I did right now was "fastboot flash boot boot.img" says ok, but just gets stuck on the white screen. The phone right now has no information, nothing. I have in my pc folder with the rom that was installed (zip with boot.img) I have the latest version of clockworkmode.
rikrdoVe said:
Yeah, try doing that. I locked boot loader again but still had no results. What I did right now was "fastboot flash boot boot.img" says ok, but just gets stuck on the white screen. The phone right now has no information, nothing. I have in my pc folder with the rom that was installed (zip with boot.img) I have the latest version of clockworkmode.
Click to expand...
Click to collapse
Some more information please. What rom did you flash and what recovery did you use? also do you have international version of this phone or AT&T/Telus version?
reaper90 said:
Some more information please. What rom did you flash and what recovery did you use? also do you have international version of this phone or AT&T/Telus version?
Click to expand...
Click to collapse
1. Carbon ROM: http://forum.xda-developers.com/showthread.php?t=2447870&page=33
2. CWM 6.0.4.6
3. Yes, international version.
rikrdoVe said:
1. Carbon ROM: http://forum.xda-developers.com/showthread.php?t=2447870&page=33
2. CWM 6.0.4.6
3. Yes, international version.
Click to expand...
Click to collapse
Did you use the right version of CWM for android 4.4+?
reaper90 said:
Did you use the right version of CWM for android 4.4+?
Click to expand...
Click to collapse
Correct, as said in the post "Note: For KK 4.4.x necessary CWM recovery from Lloir's thread."
rikrdoVe said:
Correct, as said in the post "Note: For KK 4.4.x necessary CWM recovery from Lloir's thread."
Click to expand...
Click to collapse
Did you do a wipe in before flashing the new rom?
Anyway you can copy a new rom.zip onto your phone using "adb sideload rom.zip" or "adb push rom.zip /data/media/0" while you're in recovery. Then do a full wipe first, flash rom and don't forget to flash boot.img.
reaper90 said:
Did you do a wipe in before flashing the new rom?
Anyway you can copy a new rom.zip onto your phone using "adb sideload rom.zip" or "adb push rom.zip /data/media/0" while you're in recovery. Then do a full wipe first, flash rom and don't forget to flash boot.img.
Click to expand...
Click to collapse
Thanks for your help...
I cant flash zip file, its says "error: device not found".
I put the zip file in adb folder, then "adb sideload filename.zip"
Do not know if I'm doing well, I turn on the phone in recovery mode, then with the volume keys I go to "install zip" option then "install zip from sideload" then run the command I get the error.
rikrdoVe said:
Thanks for your help...
I cant flash zip file, its says "error: device not found".
I put the zip file in adb folder, then "adb sideload filename.zip"
Do not know if I'm doing well, I turn on the phone in recovery mode, then with the volume keys I go to "install zip" option then "install zip from sideload" then run the command I get the error.
Click to expand...
Click to collapse
ADB may take some time to recognize your device in recovery. Try "adb devices" first and if it isn't listed as in recovery or sideload, wait some minutes and try again. Shouldn't take more than 5 minutes though.
But you have installed latest drivers?
reaper90 said:
ADB may take some time to recognize your device in recovery. Try "adb devices" first and if it isn't listed as in recovery or sideload, wait some minutes and try again. Shouldn't take more than 5 minutes though.
But you have installed latest drivers?
Click to expand...
Click to collapse
Hey, i tried that, and says:
List of devices attached:
FA31ZW100713 recovery
And then, i write "adb sideload filename.zip"
Error: Closed >>
I waited 6 minutes and the same result.....
And yes, i have the latest drivers and HTC Sync Manager.
rikrdoVe said:
Hey, i tried that, and says:
List of devices attached:
FA31ZW100713 recovery
And then, i write "adb sideload filename.zip"
Error: Closed >>
I waited 6 minutes and the same result.....
And yes, i have the latest drivers and HTC Sync Manager.
Click to expand...
Click to collapse
Your phone needs to be in recognized as in sideload mode in order to use adb sideload. when recognized in recovery, try "adb push rom.zip /data/media/0", this will copy your rom onto your phones internal memory. Depending on rom size, this may take some minutes and there's no progress bar/display, so give it some time, 10 min should be enough.
reaper90 said:
Your phone needs to be in recognized as in sideload mode in order to use adb sideload. when recognized in recovery, try "adb push rom.zip /data/media/0", this will copy your rom onto your phones internal memory. Depending on rom size, this may take some minutes and there's no progress bar/display, so give it some time, 10 min should be enough.
Click to expand...
Click to collapse
A month without phone and thanks to you it works again!
Thank you so much, I could not pass the zip in any way but with "adb push rom.zip / data/media/0 /" if it happened and I could flash ...
I Repeat .... THANK YOU!
have the same problem with my HTC One X.
Can you gave me an answer?
Hi all. Before i start i want to say, i read a lot of threaths and comments before i started to booting recovery and i followed Tutorial that you can find somewhere here on XDA for MotoE.
I unlocked Bootloader correctly and everything was right. Then i downloaded latest version of TWRP and CWM if something will be wrong.
So i booted into bootloader, connected to PC (windows 8.1) and using adb i installed TWRP (by command window). After instalation was complete, i used comand: "fastboot reboot" to get my mobile start normally. Everything worked fine so i started last step. Turned off mobile, booted into bootloader(or maybe fastboot? idk...) and by volumebuttons i choosed "Recovery" . Then a black screen for a minute. After that mobile stuck on screen that i attached down below. So i tried this but with CWM (same process way). But nothing new... Someone said me i had to try "Minimal ADB and Fastboot" but again, nothing happend.
Can you help me guys?
The recovery isn't installed! Reinstall the recovery and follow correct steps!
I tried it one more time. I´m attaching image that is from command window showing that .img was booted ... Strange is, immediately after booting was completed, mobile restarted... and after i turned off mobile again, still i can´t reach recovery. Isn´t that problem in .img file? maybe it´s broken, isn´t it?
Tried once again
Ok last try didnt worked. So i complettly followed this guide http://forum.xda-developers.com/moto-e/general/guide-one-moto-e-beginners-guide-t2807891 STEP-BY STEP!
Command window screen attached, Fastboot screen attached.
After reboot, turn off i tried to open recovery and again that image that i posted in first coment. (android figure with words: no command)
By that guide i downloaded recovery from here: https://goo.im/devs/OpenRecovery/condor/
and i downloaded just "openrecovery-twrp-2.7.1.0-condor.img" as i have to do it (written in guide)
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
neo.ank said:
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
Click to expand...
Click to collapse
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Mondop said:
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Click to expand...
Click to collapse
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
neo.ank said:
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
Click to expand...
Click to collapse
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Mondop said:
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Click to expand...
Click to collapse
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
neo.ank said:
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
Click to expand...
Click to collapse
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Mondop said:
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Click to expand...
Click to collapse
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
neo.ank said:
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
Click to expand...
Click to collapse
Okay, can you give me link with tutorial? i found just this one which restores whole system (and its 4.4.3 and i have now 4.4.4, i mean this will be maybe problem, wouldn´t it?)
i mean this one (tutorial how to restore moto E)
http://forum.xda-developers.com/showthread.php?t=2759495
did you try updating / reinstalling USB-driver on your computer?
magicw said:
did you try updating / reinstalling USB-driver on your computer?
Click to expand...
Click to collapse
no i didnt, think you it will help? i mean if i can connect my mobile into pc without any problem in normal mode and in fastboot too... i will unninstal drivers, intall them again and them i will try unninstal motorola device manager and then again intall him.
(i had newest drivers i can update them)
LOL?
OK im in recovery i already flashed superSU...
What did i do?
As you said, i reinstalled all drivers...
then i downloaded same TWRP again (but with mirror source)
I downloaded attached md5 file ( still dont know what should i do with it )
moved recovery and .md5 files into minimal adb and fastboot (both files i renamed to "recovery")
turned off devices
started fastboot
connected to PC
started command window and entered command "fastboot flash recovery recovery.img"
then i didnt wrote sommand "fastboot reboot" as i done before
i just unpluged usb and navigate to recovery button and launched it
and VUALA im in recovery
hurraaa
just installed superSU and then rebooted.
everything works (superSU too)
i have one more question...
i downloaded twrp manager from google play
first start: asked for root permission a allowed it
then message appeard:
"The only compatible version of busybox we support is Stericson. All other cause havoc on all operations in this app. Please click yes to install Stericson busybox"
what the heck is busybox?
+Should i download it or not?
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
ok then
magicw said:
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
Click to expand...
Click to collapse
i have no reason to want twrp manager, i just wanted to look at this app, and i found that busybox there so i wanted to ask here
thx for answer, now i undertand
I kinda messed up about a month ago, I was wanting to root my HTC One so I could try some custom ROMS and experience other cool stuff
However, Me, feeling nervous decided to go the Cyanogenmod Installer route (You know this isn't gonna end well). And so I plugged in my device and everything was good and fine until It was unlocking my bootloader, it seemed to do the HTCDev one, I got the option to unlock it or lock it, and as soon as the device restarted the phone disconnected.
Some apps went missing, however I recently had a talk to a friend who said that is normal, and he recommended me to come here to get some help.
I can boot into the bootloader where you can go into fastboot and stuff, I can factory reset through the Android OS once its booted, however when I enter recovery in the bootloader, the screen goes black and a red exclamation mark shows up for about 5-10 minutes and then the device reboots into Android.
The same thing happens when I try to get Over the air updates, I can still get OTA updates, they just don't install.
So what I'm looking for is, can I relock my device and get it back to how it was before I ran Cyanogenmod installer and then maybe I can try root it manually and have more control over the situation.
I hope you guys can help me and I hope I can find a place on this forum
Thanks in advance guys!
First of all, it seems you shouldn't have started to mess with this at all...
now to fix this...
Download the latest recovery of your choice e.a. twrp. @ http://techerrata.com/browse/twrp2/m7 the normal one is the m7 i suppose? else go to the right section...
save it to your /sdcard directly or move it there. than for the eaz just rename it to twrp.img
open an terminal if installed on your device and type
su
than
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 (note command for the m7)
if you however don't have the capability to install an app because of missing gapps... which sounds like it...
install adb/fastboot on your pc with the htc drivers..
download the recovery image with your pc and rename it to twrp.img and put it at your fastboot file
turn off your device
keep holding volume down until a menu shows up
select fastboot from the menu
attach the device to your pc
open cmd and type fastboot devices (to see if you actually installed the right driver... and that it's recognizing it)
if it does
type:
fastboot flash recovery twrp.img
if that all succeeded, you can download gapps for the android version your using or flash something else with the working recovery..
goodluck!
Hawkysoft said:
First of all, it seems you shouldn't have started to mess with this at all...
now to fix this...
Download the latest recovery of your choice e.a. twrp. @ (It prevented me posting links) the normal one is the m7 i suppose? else go to the right section...
save it to your /sdcard directly or move it there. than for the eaz just rename it to twrp.img
open an terminal if installed on your device and type
su
than
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 (note command for the m7)
if you however don't have the capability to install an app because of missing gapps... which sounds like it...
install adb/fastboot on your pc with the htc drivers..
download the recovery image with your pc and rename it to twrp.img and put it at your fastboot file
turn off your device
keep holding volume down until a menu shows up
select fastboot from the menu
attach the device to your pc
open cmd and type fastboot devices (to see if you actually installed the right driver... and that it's recognizing it)
if it does
type:
fastboot flash recovery twrp.img
if that all succeeded, you can download gapps for the android version your using or flash something else with the working recovery..
goodluck!
Click to expand...
Click to collapse
Thank you! Will there be a risk in ruining my device?
And thank you once again! I definitley shouldn't have messed with this, but you gotta start somewhere right?
If I never took the risk of building my own computer then I never could have done it Its how we learn.
Anyways, I'm not sure about the terminal bit, I don't run linux and I don't have a mac? So, how would I have access to the terminal. Unless I somehow got it on my device (I don't know how to do that).
And one more question, once I've done the things you've told me to do I can just put Cyanogenmod on it?
Thanks once again
Oh, and I have got Gapps, if my Gapps you mean Google Apps, yes I have I've got Google play services, Google play, hangouts etc.
Thank you! Will there be a risk in ruining my device?
Click to expand...
Click to collapse
Further than now? i highly doubt it... unless you totally put in a wrong recovery which magically wud fk up the partitions?
And thank you once again! I definitley shouldn't have messed with this, but you gotta start somewhere right?
Click to expand...
Click to collapse
True, but babysteps mate...
Anyways, I'm not sure about the terminal bit, I don't run linux and I don't have a mac? So, how would I have access to the terminal. Unless I somehow got it on my device (I don't know how to do that).
Click to expand...
Click to collapse
Terminal should be on the phone, if not use command prompt in windows... u need to do a little research on the m7 forums which driver you need they probably have an m7 toolkit again if the one is the m7, as far as i knew it is.. than you could put the recovery.img in the folder of fastboot.exe and go there with command prompt and do what i've written before
And one more question, once I've done the things you've told me to do I can just put Cyanogenmod on it?
Click to expand...
Click to collapse
erhm ofcourse you can, however just download the rom instead of an installer...
p.s. you got gapps.. install an emulator oh... better solution... install flashify download the latest twrp and install it with that if u have proper root that is!
Hawkysoft said:
Further than now? i highly doubt it... unless you totally put in a wrong recovery which magically wud fk up the partitions?
True, but babysteps mate...
Terminal should be on the phone, if not use command prompt in windows... u need to do a little research on the m7 forums which driver you need they probably have an m7 toolkit again if the one is the m7, as far as i knew it is.. than you could put the recovery.img in the folder of fastboot.exe and go there with command prompt and do what i've written before
erhm ofcourse you can, however just download the rom instead of an installer...
p.s. you got gapps.. install an emulator oh... better solution... install flashify download the latest twrp and install it with that if u have proper root that is!
Click to expand...
Click to collapse
Thanks I don't have root, I've run rootchecker, and it says I don't have root.
And what if I do Cyanogenmod but I want to go back to HTC Sense (Doubt it though)
Will instlaling the recovery root my device? If not, how will I root it?
Oh and, how do I get fastboot and ADB?
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
I recently found my old HTC desire 526g and I decided to flash a custom ROM, but its volume buttons aren't working so I had to use adb, I am not really an good in these types of things. I tried to flash TWRP on my htc using adb (Followed a YouTube tut) but this is coming up.
I have attached a screenshot below.
After unlocking bootloader (probably would have done it earlier) did you allow the usb debugging.
2) try installing adb+fastboot, platform tools and your htc drivers and keep your recovery file in the platform tools and open cmd there use the appropriate command to flash it
Rajveer chauhan said:
After unlocking bootloader (probably would have done it earlier) did you allow the usb debugging.
2) try installing adb+fastboot, platform tools and your htc drivers and keep your recovery file in the platform tools and open cmd there use the appropriate command to flash it
Click to expand...
Click to collapse
Hello, Thanks for replying! I think I have done everything in correct manner, but still coming thiss error, I have rooted my phone too. BTW, is there any way you can navigate through system recovery without using volume buttons (as they are not working) I mean any commands, to navigate in recovery mode using adb
YourLocalClown69 said:
Hello, Thanks for replying! I think I have done everything in correct manner, but still coming thiss error, I have rooted my phone too. BTW, is there any way you can navigate through system recovery without using volume buttons (as they are not working) I mean any commands, to navigate in recovery mode using adb
Click to expand...
Click to collapse
So if you're rooted so you can flash recovery via twrp app on playstore, or if magisk installer for twrp exists for your phone or by flashfire if you have your working recovery
'adb reboot bootloader' will bring you fastboot mode.
'fastboot flash recovery recovery.img' (while TWRP image or CWM image is renamed recovery.img and placed into the fastboot folder)will bring you TWRP/CWM.
'fastboot reboot recovery' will bring you into TWRP or CWM installed.
'fastboot reboot' will reboot you phone in case you are stuck.
LR7875 said:
'adb reboot bootloader' will bring you fastboot mode.
'fastboot flash recovery recovery.img' (while TWRP image or CWM image is renamed recovery.img and placed into the fastboot folder)will bring you TWRP/CWM.
'fastboot reboot recovery' will bring you into TWRP or CWM installed.
'fastboot reboot' will reboot you phone in case you are stuck.
Click to expand...
Click to collapse
This comes later now lol, Due to my lack of knowledge and not enough patience, I tried to flash custom recovery through TWRP app, and I didn't found my phone model on device list, SO i just selected random htc model phone and now it is restarting over and over again, Is there any fix to this? I am obviously a complete noob in this field.
If possible find stock recovery of that firmware version (be serious abt version) and flash it by fastboot
2) find how to unbrick htc by downloading stock rom this will make you lose all data
Rajveer chauhan said:
If possible find stock recovery of that firmware version (be serious abt version) and flash it by fastboot
2) find how to unbrick htc by downloading stock rom this will make you lose all data
Click to expand...
Click to collapse
Even If I find the this whatever you said, how am I supposed to fix it, as I mentioned,Volume buttons aren;t working and its stuck in bootloop, it won't past its manufacturers logo, so adb is no help in it, Only way to fix it would be to fix sound buttons. sad me, Well, R.I.P. HTC Desire 526g dual sim 2015-2021
I hope that this phone is not your primary driver
YourLocalClown69 said:
I recently found my old HTC desire 526g
Click to expand...
Click to collapse
Rajveer chauhan said:
I hope that this phone is not your primary driver
Click to expand...
Click to collapse
He unearthed his phone from some drawer, so this is not his daily driver.