Related
Okay here's my situation my phone was rooted, bootloader unlocked I was on stock rooted lollipop my phone turned off on its own it got stuck in a boot loop . I was going to flash lollipop again notice recovery didn't load so I went to fastboot and tried to flash twrp-2.8.7.0 it loaded but then it froze at start up of twrp tried again and the same. So I tried a newer recovery twrp 2.8.70 this one didn't load all the way neither same for twrp3.0.0.0 so after all that I just said screw it I'm going stock. So I booted to download mode and use lgup lollipop .kdz method everything loaded up fine. I noticed my boot loader got locked Rom loaded up and before I can finish the initial setup phone rebooted again. Now I'm stuck in a boot loop,no download mode it just reboots when launched and locked bootloader. Can't unlock it in fastboot any suggestions on what to do?
Sorry for being so long been on it for two days. HELP HELP HELP HELP PLZ PLZ
*UPDATE*
okay by the grace of god for some reason it was stuck on boot start up"lg screen left it for about an hour and nothing so i did a pull battery and the phone was hot to the touch so i just gave up on it and put the battery back in and for some dam reason it booted up long enough for me to get to the developers option check unlock oem and usb debugging snd after 30 minutes of working just fine i noticed it had MM6.0??? dont know how that wa'Ys done???? confused on that??? but any hoo the dam phone rebooted after the play store tried to update. and this time i got a "Your device Software cant be checked for corruption??? but i am able to boot to download mode and fastboot mode and unlocked bootloader but still cant flash twrp????
There is no legit kdz for LP I know of for H901 devices. The one I know of bricks phones.
Sent from my LG-H901 using XDA-Developers mobile app
holy crap did i just survive a brick????
sabresfan said:
There is no legit kdz for LP I know of for H901 devices. The one I know of bricks phones.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
killa57 said:
holy crap did i just survive a brick????
Click to expand...
Click to collapse
Your phone probably tried to update by itself. You should probably use lgup to return to stock since you can get to download mode now. Follow this thread to root. http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
MudaTrucka said:
Your phone probably tried to update by itself. You should probably use lgup to return to stock since you can get to download mode now. Follow this thread to root. http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
Click to expand...
Click to collapse
okay i have tried it the ROM did not stick the recovery loads but then freezes after it loads I have no download mode no more and it shows im unlocked in fastboot mode but when I try anything like flash recovery or erase system it’ll say okay but then it will say ......# fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 1.458s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.475s
killa57 said:
okay i have tried it the ROM did not stick the recovery loads but then freezes after it loads I have no download mode no more and it shows im unlocked in fastboot mode but when I try anything like flash recovery or erase system it’ll say okay but then it will say ......# fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 1.458s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.475s
Click to expand...
Click to collapse
Update does everything look okay?
Flashing via fastboot, even with an unlocked bootloader, in MM is known broken.
Sent from my LG-H901 using Tapatalk
toastido said:
Flashing via fastboot, even with an unlocked bootloader, in MM is known broken.
Click to expand...
Click to collapse
So I'm basically out of options then hummm!!!!
killa57 said:
okay i have tried it the ROM did not stick the recovery loads but then freezes after it loads I have no download mode no more and it shows im unlocked in fastboot mode but when I try anything like flash recovery or erase system it’ll say okay but then it will say ......# fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 1.458s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.475s
Click to expand...
Click to collapse
Hold volume up and plug in the USB at same time while the phone is off to get to download mode. And did you follow all directions for rooting on marshmallow?
EDIT: I prefer this thread as it describes more. http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
MudaTrucka said:
Hold volume up and plug in the USB at same time while the phone is off to get to download mode. And did you follow all directions for rooting on marshmallow?
EDIT: I prefer this thread as it describes more. http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
Click to expand...
Click to collapse
Okay I have pin pointed the problem it's hardware issue it only boots up if the phone is hot What do I do now? As long as the phone is hot it works that's why I couldn't boot recovery download mode. Cause the phone would stop working freeze all the time.:good:
killa57 said:
Okay I have pin pointed the problem it's hardware issue it only boots up if the phone is hot What do I do now? As long as the phone is hot it works that's why I couldn't boot recovery download mode. Cause the phone would stop working freeze all the time.:good:
Click to expand...
Click to collapse
Do you have insurance on it? I think the only thing you can do is replace it since it's a hardware issue.
MudaTrucka said:
Do you have insurance on it? I think the only thing you can do is replace it since it's a hardware issue.
Click to expand...
Click to collapse
Do I remove the bootloader lock or will insurance cover it that way?
killa57 said:
Do I remove the bootloader lock or will insurance cover it that way?
Click to expand...
Click to collapse
Keeping the bootloader locked would probably be best
After fumbling with install twrp in order to change over to CM13 from stock, I somehow managed to install the original recovery wrong as well as completely boning the OS. Because of this, on boot, all that shows is the honor screen continuously. Of course the obvious answer to this is to reinstall twrp and restore one of my recovery files. Unfortunately trying to flash twrp through fastboot results in an "FAILED (data transfer failure (Unknown error))". Any suggestions? I can't access the phones internal storage nor the SD card either when I plug it into my PC.
Only one solution, flash a stock firmware using a PC.
PalakMi said:
Only one solution, flash a stock firmware using a PC.
Click to expand...
Click to collapse
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Dueter1um said:
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
Click to expand...
Click to collapse
I don't think only fastboot is enough, but take a look at the link provided by JT-on
JT-on said:
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Click to expand...
Click to collapse
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Dueter1um said:
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Click to expand...
Click to collapse
Happy for you, next time be careful
I got this same error, had to use different USB cable and different USB port.
Hello,
I have rooted my Honor7 with Kingoroot. Now I want to unroot it to do OTA Updates.
Unroot with Kingoroot is failing and the Support is not answering.
I tried with Honor Multi Tool and flashing stock recovery (.IMG) , but as soon as I want to flash Recovery this is printed out: FAILED (remote: Command not allowed)
I have already checked bootloader and there is written "Phone unlocked"
So what's the Problem?
Regards,
Christian
Qhris said:
Hello,
I have rooted my Honor7 with Kingoroot. Now I want to unroot it to do OTA Updates.
Unroot with Kingoroot is failing and the Support is not answering.
I tried with Honor Multi Tool and flashing stock recovery (.IMG) , but as soon as I want to flash Recovery this is printed out: FAILED (remote: Command not allowed)
I have already checked bootloader and there is written "Phone unlocked"
So what's the Problem?
Regards,
Christian
Click to expand...
Click to collapse
There´s an option inside Kingroot to uninstall. I can't remember the steps to get there, but you can't just uninstall the app.
The other options would be flash system.img or factory reset after backing up the relevant data with Huawei backup native app.
I was struggling a bit with Kingroot unroot too, but after I restarted Honor it just worked out. Just use option in menu of Kingroot to uninstall. First time during unroot I got error or it just froze for a moment and nothing hapenned.
And just FYI even you remove Kingroot, you have to reflash completely your FW by local update otherwise OTA won´t work because system partition was changed by Kingroot.
Go to Settings>Root Authorization Settings>Remove Root permission. Select OK for the next screens (it will take some time) and check if app was uninstalled. If not, do it.
Reboot the phone and you´re done.
Ing.King said:
I was struggling a bit with Kingroot unroot too, but after I restarted Honor it just worked out. Just use option in menu of Kingroot to uninstall. First time during unroot I got error or it just froze for a moment and nothing hapenned.
And just FYI even you remove Kingroot, you have to reflash completely your FW by local update otherwise OTA won´t work because system partition was changed by Kingroot.
Click to expand...
Click to collapse
I have restarted the device many times. Everytime the unroot with the computer software is failing...
One question regarding kingroot. I am not able to remember, that I need to unlock the bootloader over huawei. Is this possible?
zinko_pt said:
Go to Settings>Root Authorization Settings>Remove Root permission. Select OK for the next screens (it will take some time) and check if app was uninstalled. If not, do it.
Reboot the phone and you´re done.
Click to expand...
Click to collapse
What APP do you mean? There is an app named "Kingo Link", but this app does not have any Settings.
The other was SuperSU#. I have done there the unroot option and deinstalled the app, but the device is still rooted. (Checked with Root Checker Basic)
I suppose you used kingroot installed in your phone.
Ah ok. No I used the pc program (https://www.kingoapp.com/)
If you didn't modified your system other than rooting it, I suggest you to flash system.img from Stock Firmware you were using previously.
DigiGoon said:
If you didn't modified your system other than rooting it, I suggest you to flash system.img from Stock Firmware you were using previously.
Click to expand...
Click to collapse
Already tried....
"I tried with Honor Multi Tool and flashing stock recovery (.IMG) , but as soon as I want to flash Recovery this is printed out: FAILED (remote: Command not allowed)"
Is it possible to do the update without removing the root?
Qhris said:
Already tried....
"I tried with Honor Multi Tool and flashing stock recovery (.IMG) , but as soon as I want to flash Recovery this is printed out: FAILED (remote: Command not allowed)"
Is it possible to do the update without removing the root?
Click to expand...
Click to collapse
Nope, the install will fail everytime if the system is modified, but in some cases it is reported that, by doing this process multiplte times it actually passes through regardless the rooted system.
So keep trying, and that error occurs when you have a Locked Bootloader, did you checked if its not in any way relocked?
Qhris said:
Already tried....
"I tried with Honor Multi Tool and flashing stock recovery (.IMG) , but as soon as I want to flash Recovery this is printed out: FAILED (remote: Command not allowed)"
Is it possible to do the update without removing the root?
Click to expand...
Click to collapse
Modified partition, so no.
I would go with the PC app side and try a uninstall.
If it doesn't work, then a manual fastboot flash of the boot.img, recovery.img, system.img, by this order. If not with current Bxxx version, go back to B100.
As a rule of thumb I never use Kingroot as it sticks like a chewed bubble gum.
DigiGoon said:
Nope, the install will fail everytime if the system is modified, but in some cases it is reported that, by doing this process multiplte times it actually passes through regardless the rooted system.
So keep trying, and that error occurs when you have a Locked Bootloader, did you checked if its not in any way relocked?
Click to expand...
Click to collapse
How i could check, if my bootloader is relocked? The multi tool check says it's unlocked...
To boot into bootloader mode follow these steps:
Switch off your device.
Press and hold Vol DOWN button.
While pressing and holding it, connect your device to PC.
Once in bootloader mode you'll get text on the screen like:
Phone Locked - If your bootloader is locked.
Phone Unlocked - If your bootloader is unlocked.
Phone Relocked - If your bootloader is relocked after once doing an unlock.
Report back after checking.
Good News. I removed root with the king app, but flashing is not working:
C:\Users\Chris\Desktop\HONOR_MultiTool\Files>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (459682 KB)...
OKAY [ 10.279s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 10.283s
C:\Users\Chris\Desktop\HONOR_MultiTool\Files>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (459682 KB)...
OKAY [ 10.244s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 10.247s
I have checked bootloader like DigiGoon said and there is written "Phone Unlocked"... Wtf? ..
Qhris said:
Good News. I removed root with the king app, but flashing is not working:
C:\Users\Chris\Desktop\HONOR_MultiTool\Files>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (459682 KB)...
OKAY [ 10.279s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 10.283s
C:\Users\Chris\Desktop\HONOR_MultiTool\Files>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (459682 KB)...
OKAY [ 10.244s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 10.247s
I have checked bootloader like DigiGoon said and there is written "Phone Unlocked"... Wtf? ..
Click to expand...
Click to collapse
Have you tried with B100?
zinko_pt said:
Have you tried with B100?
Click to expand...
Click to collapse
Yes, this was system.img from "PLK-L01C432B100 Upgrade Software UK"
zinko_pt said:
Have you tried with B100?
Click to expand...
Click to collapse
No, flash the boot.img from current Bxxx version.
zinko_pt said:
No, flash the boot.img from current Bxxx version.
Click to expand...
Click to collapse
It must be the current boot.img? I am not able to find any for B180...
Qhris said:
It must be the current boot.img? I am not able to find any for B180...
Click to expand...
Click to collapse
Yes, use this full B180 https://www.androidfilehost.com/?w=files&flid=102830
@Qhris Try to update your ADB & Fastboot drivers, it seems like the drivers are outdated.
Use the latest SDK from Google.
Hello everyone!
I tried to install CM13 nightly on my brand new Honor 5X. Followed the process, installed TWRP 3.0.2 bootloader and then the CM13 and Google Apps zips. When I booted the phone I saw the blue face for CM, but the phone never booted and kept rebooting! I tried to launch in TRWP recovery mode, but the swipe is locked and I can not go back to the install menu. TWRP is completely unresponsive no matter how i swipe or press the volume/power button. Why is TWRP like that?
Model: KIW-UL00
hrstoyanov said:
Hello everyone!
I tried to install CM13 nightly on my brand new Honor 5X. Followed the process, installed TWRP 3.0.2 bootloader and then the CM13 and Google Apps zips. When I booted the phone I saw the blue face for CM, but the phone never booted and kept rebooting! I tried to launch in TRWP recovery mode, but the swipe is locked and I can not go back to the install menu. TWRP is completely unresponsive no matter how i swipe or press the volume/power button. Why is TWRP like that?
Click to expand...
Click to collapse
U are mistaken , issue is u do installed Cm13 over b418 or b420++ ..
If iam right ur device wasn't bricked .I can help u here .raise the discussion with your thoughts and I will end it up with success
Sent from my KIW-L22 using Tapatalk
if u still can recognize the phone with fast-boot then u can go back to stock ( only latest to get match build version or upgraded one ) downgraded build will fail .
hrstoyanov said:
Hello everyone!
I tried to install CM13 nightly on my brand new Honor 5X. Followed the process, installed TWRP 3.0.2 bootloader and then the CM13 and Google Apps zips. When I booted the phone I saw the blue face for CM, but the phone never booted and kept rebooting! I tried to launch in TRWP recovery mode, but the swipe is locked and I can not go back to the install menu. TWRP is completely unresponsive no matter how i swipe or press the volume/power button. Why is TWRP like that?
Model: KIW-UL00
Click to expand...
Click to collapse
Havnt u made a twrp backup ?
Sent from my KIW-L22 using Tapatalk
hrstoyanov said:
Hello everyone!
I tried to install CM13 nightly on my brand new Honor 5X. Followed the process, installed TWRP 3.0.2 bootloader and then the CM13 and Google Apps zips. When I booted the phone I saw the blue face for CM, but the phone never booted and kept rebooting! I tried to launch in TRWP recovery mode, but the swipe is locked and I can not go back to the install menu. TWRP is completely unresponsive no matter how i swipe or press the volume/power button. Why is TWRP like that?
Model: KIW-UL00
Click to expand...
Click to collapse
When the twrp boots up, let the phone alone until the screen turns off. Press power and see if it starts working.
This usually does the trick for me.
muradulislam said:
When the twrp boots up, let the phone alone until the screen turns off. Press power and see if it starts working.
This usually does the trick for me.
Click to expand...
Click to collapse
Oh wait . I had the solution
Sent from my KIW-L22 using Tapatalk
---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------
hrstoyanov said:
Hello everyone!
I tried to install CM13 nightly on my brand new Honor 5X. Followed the process, installed TWRP 3.0.2 bootloader and then the CM13 and Google Apps zips. When I booted the phone I saw the blue face for CM, but the phone never booted and kept rebooting! I tried to launch in TRWP recovery mode, but the swipe is locked and I can not go back to the install menu. TWRP is completely unresponsive no matter how i swipe or press the volume/power button. Why is TWRP like that?
Model: KIW-UL00
Click to expand...
Click to collapse
I think am the only one who can solve ur issue .. If u are online now , quote me. I will help u for sure .trust me ur touch screen works in recovery after doing what I said
Sent from my KIW-L22 using Tapatalk
gopinaidu77 said:
Oh wait . I had the solution
Sent from my KIW-L22 using Tapatalk
---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------
I think am the only one who can solve ur issue .. If u are online now , quote me. I will help u for sure .trust me ur touch screen works in recovery after doing what I said
Click to expand...
Click to collapse
Be civil and stop doing that please...
muradulislam said:
Be civil and stop doing that please...
Click to expand...
Click to collapse
Ohh .. I was just saying ! Don't take it soo serious .
Sent from my KIW-L22 using Tapatalk
---------- Post added at 08:02 PM ---------- Previous post was at 07:56 PM ----------
muradulislam said:
Be civil and stop doing that please...
Click to expand...
Click to collapse
I had faced this multiple times . I used get a jerk in my body if touch dint won't on twrp . almost phone in dead state and we still had to ability to access fastboot but twrp never work and even other recoveries .
So my solution is just soo easy .
Twrp touch failure is caused due to the kernal in Cyanogenmod .
So , just flash the stock boot.IMG and tadaaa .
Reboot to twrp and that's it .
And I may not be the only one ,but am just boosting the OP's anxiety and confidence levels making him aware that his phone is still alive .
Take it easy my frn . Am not a god to know everything , and I always try to live civil.thanks for your advice and I will take it sportive .
And +1 for you
gopinaidu77 said:
Ohh .. I was just saying ! Don't take it soo serious .
Click to expand...
Click to collapse
Well, what can I say, you said it and I did take it seriously but let's forget all that.
And the trick I said, I used it with honor 6 and 7 and it worked, we are all here to help so I tried that too.
muradulislam said:
Well, what can I say, you said it and I did take it seriously but let's forget all that.
And the trick I said, I used it with honor 6 and 7 and it worked, we are all here to help so I tried that too.
Click to expand...
Click to collapse
But that thing dint work on 5x . if that do , I could have kept silent with your post . but your answer is obvious .thanks
Sent from my KIW-L22 using Tapatalk
gopinaidu77 said:
But that thing dint work on 5x . if that do , I could have kept silent with your post . but your answer is obvious .thanks
Click to expand...
Click to collapse
Then just point it out to me straight using the words "You are wrong" with the explanation, why do you think so...
It will make me learn that my approach is wrong and will make me learn something new.
Using a direct and honest approach is much better than a sarcastic one. IMHO.
muradulislam said:
Then just point it out to me straight using the words "You are wrong" with the explanation, why do you think so...
It will make me learn that my approach is wrong and will make me learn something new.
Using a direct and honest approach is much better than a sarcastic one. IMHO.
Click to expand...
Click to collapse
Ha ha , well said . I would have done that ! But when I said that , I dint pointed u actually . still thanks for your great words . will remember till I last in xda
gopinaidu77 said:
But that thing dint work on 5x . if that do , I could have kept silent with your post . but your answer is obvious .thanks
Sent from my KIW-L22 using Tapatalk
Click to expand...
Click to collapse
Guys,
Thanks, I will keep trying with your recommendations, here is where I left yesterday:
My issue is that TWRP does not recognize any touch event and I cannot swipe to unlock it and go to the menus. Not sure how it happened, but it used to work initially.
Out of desperation, I downloaded the US stock firmware from Huawei, placed the UPADTE.APPP under /sdcard/dload/update.zip
When I boot now (power+ volume up) I see a circle EMUI initial screen and some menus in Chinese (which I don't understand). With the volume, I am able to switch to the next menu where it discovers all wireless networks around me. But, I cannot select mine network with touching the screen, and the EMUI recovery does not work with the volume.
At this point my concern is that somehow I broke the phone as it is not responding to screen touch events. Could that be the reason why I cannot unlock TWRP?
I can install CM13 recovery image or TWRP any time, but that's about it - I cannot run CM13 (rebooted all the time and now TWRP is toast) or put back the stock firmware (blocked swipe on the screen items).
hrstoyanov said:
Guys,
Thanks, I will keep trying with your recommendations, here is where I left yesterday:
My issue is that TWRP does not recognize any touch event and I cannot swipe to unlock it and go to the menus. Not sure how it happened, but it used to work initially.
Out of desperation, I downloaded the US stock firmware from Huawei, placed the UPADTE.APPP under /sdcard/dload/update.zip
When I boot now (power+ volume up) I see a circle EMUI initial screen and some menus in Chinese (which I don't understand). With the volume, I am able to switch to the next menu where it discovers all wireless networks around me. But, I cannot select mine network as with touching the screen, and the EMUI recovery does not work with the volume.
At this point my concern is that somehow I broke the phone as it is not responding to screen touch events. Could that be the reason why I cannot unlock TWRP?
I can install CM13 recovery image or TWRP at will, but that's about it - i cannot run CM13 (reboots all the time) or put back the stock firmware (blocked swipe)
Click to expand...
Click to collapse
If u have twrp backup ..
Open the backup
Rename boot.ext4.win to boot.img
(U can also extract any marshmallow boot.IMG from update.app)
Put it in fastboot folder
Then put ur phone in fastboot mode
Type this command
Fastboot flash boot boot.img
Later type this command .
Fastboot reboot
And come back up to recovery.
Tada. It will work now.
Sent from my KIW-L22 using Tapatalk
gopinaidu77 said:
If u have twrp backup ..
Open the backup
Rename boot.ext4.win to boot.img
(U can also extract any marshmallow boot.IMG from update.app)
Put it in fastboot folder
Then put ur phone in fastboot mode
Type this command
Fastboot flash boot boot.img
Later type this command .
Fastboot reboot
And come back up to recovery.
Tada. It will work now.
Sent from my KIW-L22 using Tapatalk
Click to expand...
Click to collapse
he says that touch is not working with TWRP .
Romiui said:
he says that touch is not working with TWRP .
Click to expand...
Click to collapse
Yes .. The solution is for that
Sent from my KIW-L22 using Tapatalk
gopinaidu77 said:
If u have twrp backup ..
Open the backup
Rename boot.ext4.win to boot.img
(U can also extract any marshmallow boot.IMG from update.app)
Put it in fastboot folder
Then put ur phone in fastboot mode
Type this command
Fastboot flash boot boot.img
Later type this command .
Fastboot reboot
And come back up to recovery.
Tada. It will work now.
Sent from my KIW-L22 using Tapatalk
Click to expand...
Click to collapse
...Tried to follow your instructions, but no luck
1. I don't have TWRP backup. So, I downloaded the latest HUAWEI Honor 5x stock: (KIW-L24, Android 6.0.1,EMUI 4.0,C567D003,United States)
2. Extracted UPDATE.APP first, and then extracted boot.IMG from it.
3. Deployed the boot.img:
? platform-tools ./fastboot flash boot ~/Downloads/BOOT.img
target reported max download size of 266338304 bytes
sending 'boot' (44266 KB)...
OKAY [ 1.407s]
writing 'boot'...
OKAY [ 0.698s]
finished. total time: 2.105s
4. Deployed TWRP recovery:
? platform-tools ./fastboot flash recovery ~/Downloads/twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.438s]
writing 'recovery'...
OKAY [ 0.713s]
finished. total time: 2.151s
5. Rebooted the phone - it keeps rebooting endlessly :
? platform-tools ./fastboot reboot
rebooting...
finished. total time: 0.002s
5. Reboot the phone in recovery mode (power+Vol Up+Vol Down)
TWRP comes with the lock on the screen. No touch events, swipe as before. Dead as a door nail again!
6. Desperate, I also tried to deploy the CM13 recovery:
? platform-tools ./fastboot flash recovery ~/Downloads/cm-13.0-20161216-NIGHTLY-kiwi-recovery.img
target reported max download size of 266338304 bytes
sending 'recovery' (48114 KB)...
OKAY [ 1.517s]
writing 'recovery'...
OKAY [ 0.751s]
finished. total time: 2.268s
This works - I am able to boot in CM recovery now, but the CM recovery tools is pretty useless and limited. Well, at least it does not rely on the touch screen and one can access the items ...
... So I am even more frustrated now with the whole experience. This process was not supposed to be such a descent into a black hole .
My thinking is that my Honor 5x lost its touch screen permanently due to this CM endeavors.
Also, is there any problem that it is a Chinese model (KIW-UL00) and I used US stock image in step 1 ?
Any other ideas?
i can say that u flashed US version which might have wrong display driver ! .. u need to go back to the stock as same what came with the phone
use full software dload or flash it throw fastboot after extracting update.app .
this link might help u . just make account and download the latest update .
Honor 5X KIW-UL00 - B239
hrstoyanov said:
...Tried to follow your instructions, but no luck
1. I don't have TWRP backup. So, I downloaded the latest HUAWEI Honor 5x stock: (KIW-L24, Android 6.0.1,EMUI 4.0,C567D003,United States)
2. Extracted UPDATE.APP first, and then extracted boot.IMG from it.
3. Deployed the boot.img:
? platform-tools ./fastboot flash boot ~/Downloads/BOOT.img
target reported max download size of 266338304 bytes
sending 'boot' (44266 KB)...
OKAY [ 1.407s]
writing 'boot'...
OKAY [ 0.698s]
finished. total time: 2.105s
4. Deployed TWRP recovery:
? platform-tools ./fastboot flash recovery ~/Downloads/twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.438s]
writing 'recovery'...
OKAY [ 0.713s]
finished. total time: 2.151s
5. Rebooted the phone - it keeps rebooting endlessly :
? platform-tools ./fastboot reboot
rebooting...
finished. total time: 0.002s
5. Reboot the phone in recovery mode (power+Vol Up+Vol Down)
TWRP comes with the lock on the screen. No touch events, swipe as before. Dead as a door nail again!
6. Desperate, I also tried to deploy the CM13 recovery:
? platform-tools ./fastboot flash recovery ~/Downloads/cm-13.0-20161216-NIGHTLY-kiwi-recovery.img
target reported max download size of 266338304 bytes
sending 'recovery' (48114 KB)...
OKAY [ 1.517s]
writing 'recovery'...
OKAY [ 0.751s]
finished. total time: 2.268s
This works - I am able to boot in CM recovery now, but the CM recovery tools is pretty useless and limited. Well, at least it does not rely on the touch screen and one can access the items ...
... So I am even more frustrated now with the whole experience. This process was not supposed to be such a descent into a black hole .
My thinking is that my Honor 5x lost its touch screen permanently due to this CM endeavors.
Also, is there any problem that it is a Chinese model (KIW-UL00) and I used US stock image in step 1 ?
Any other ideas?
Click to expand...
Click to collapse
Bro , please flash boot.img of stock ROM in boot partition n
And keep twrp in recovery partition and reboot to recovery will fix
Don't flash cm recovery .
Do this way.
Flash stock ROM boot.img in to boot partition first .
Now reboot to recovery . touch will work then
gopinaidu77 said:
Bro , please flash boot.img of stock ROM in boot partition n
And keep twrp in recovery partition and reboot to recovery will fix
Don't flash cm recovery .
Do this way.
Flash stock ROM boot.img in to boot partition first .
Now reboot to recovery . touch will work then
Click to expand...
Click to collapse
... but this is exactly what I did? And after rebooting nothing improves!
➜ platform-tools ./fastboot flash boot ~/Downloads/BOOT.img
target reported max download size of 266338304 bytes
sending 'boot' (44266 KB)...
OKAY [ 1.393s]
writing 'boot'...
OKAY [ 0.690s]
finished. total time: 2.082s
➜ platform-tools ./fastboot flash recovery ~/Downloads/twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.429s]
writing 'recovery'...
OKAY [ 0.710s]
finished. total time: 2.139s
Apologies if I should have searched harder. My understanding is that touch screen issues like this happen when the firmware you flash isn't quite compatible with your device. I've triple checked the stuff I downloaded, and I'm not seeing how it could be that. Maybe I did something else stupid? This is my first time rooting anything.
Product/Variant (as seen in bootloader): sofia XT2041-4 64GB PVT
The boot.img I downloaded: lolinet's firmware/moto/sofia/official/RETUS/ (the august 31 one. Currently trying with the earlier one, but the download is taking forever)
Magisk version: 7.5.1
I only have a linux laptop, so the rescue and smart assistant appears to be off the table
Here's what I did:
Downloaded the boot.img from lolinet
patched it using magisk
flashed it using fastboot
How I flashed it:
Code:
~/Downloads$ fastboot flash boot magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_b' (12136 KB)...
OKAY [ 0.376s]
writing 'boot_b'...
OKAY [ 0.069s]
finished. total time: 0.446s
I booted up after this, and I couldn't use the touchscreen. Then I noticed the boot_b thing, so I did the following to do both partitions (although I have no idea if this is what you're supposed to do):
Code:
~/Downloads$ fastboot flash boot_a magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_a' (12136 KB)...
OKAY [ 0.350s]
writing 'boot_a'...
OKAY [ 0.076s]
finished. total time: 0.425s
~/Downloads$ fastboot flash boot_b magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_b' (12136 KB)...
OKAY [ 0.370s]
writing 'boot_b'...
OKAY [ 0.214s]
finished. total time: 0.584s
No dice..
Next, I tried to just use the unpatched boot.img to restore things.
Code:
~/Downloads$ fastboot flash boot_a XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img
target reported max download size of 805259264 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.908s]
writing 'boot_a'...
OKAY [ 0.696s]
finished. total time: 2.604s
~/Downloads$ fastboot flash boot_b XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img
target reported max download size of 805259264 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.949s]
writing 'boot_b'...
OKAY [ 0.525s]
finished. total time: 2.474s
once again, no dice..this time I didn't even get to the lockscreen. Just stuck on the moto logo
Any idea what I've done wrong? Would really appreciate some help with this.
Update: I tried with the other boot.img from lolinet, doesn't get to lockscreen. Then I tried a factory reset with twrp, and flashing the earlier boot.img and I got to the setup screen, but still no touch.
Update 2: I managed to get omnirom flashed, and that's working so far! I am still curious to know why the touch screen issues popped up..will be useful next time I want to flash stock
check the forums for the g7 play, I've found topics about that kind of issue.
There's a few touchscreen vendors used for the same device, and they use different drivers basically.
Got a link by any chance? The ones I've seen are twrp related or because of the wrong firmware.
Any idea how to figure out which set is right for my phone?
Here is solution: get full ROM through LMSA and flash components through bootloader and fastbootd
* boot, recovery, dtbo, vbmeta, super flashed in fastbootd (adb reboot fastboot)
* All other actions done in bootloader (adb reboot bootloader)
mingkee said:
Here is solution: get full ROM through LMSA and flash components through bootloader and fastbootd
* boot, recovery, dtbo, vbmeta, super flashed in fastbootd (adb reboot fastboot)
* All other actions done in bootloader (adb reboot bootloader)
Click to expand...
Click to collapse
Can this be done without fastbootd? i stupidly flashed twrp (which doesnt work). so I dont have stock recovery to get into fastbootd. Can this be done using regular fastboot?
Or any way to flash a stock rom using just fastboot? the rom i have does not have 'flash all' so im not sure what to do from here.
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
cnoevl21 said:
Can this be done without fastbootd? i stupidly flashed twrp (which doesnt work). so I dont have stock recovery to get into fastbootd. Can this be done using regular fastboot?
Or any way to flash a stock rom using just fastboot? the rom i have does not have 'flash all' so im not sure what to do from here.
Click to expand...
Click to collapse
Solution:
Flash everything ***except*** those flashed in fastbootd
fastboot reboot bootloader
fastboot reboot fastboot
The last resort: use LMSA rescue, but your phone will be wiped
mingkee said:
Solution:
Flash everything ***except*** those flashed in fastbootd
fastboot reboot bootloader
fastboot reboot fastboot
The last resort: use LMSA rescue, but your phone will be wiped
Click to expand...
Click to collapse
when you say flash everything. is it just flashing the .img files? or literally everything?
Sorry, ive never had to manually flash before.
---------- Post added at 09:17 PM ---------- Previous post was at 09:15 PM ----------
nero075 said:
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
Click to expand...
Click to collapse
ill have to try this. thanks. Ive tried to just boot the boot.img and it hasnt done anything. so ill do this to try and get into fastbootd.
nero075 said:
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
Click to expand...
Click to collapse
Ok. ive gotten into fastbootd but have no idea what to do now. I assumed it was like flashing with regular fastboot. but when i type commands like fastboot flash boot boot.img i get a failed result no such file or directory
Hello friend,
Did you ever resolve your issue with the touchscreen?
I've just down the same thing using Magisk. Everything was fine until I flashed the magisk.patched.img. The device booted up but the touchscreen doesn’t work no matter what.
Please let me know of your solution.
Thank you kindly.
PamelaGirl said:
Hello friend,
Did you ever resolve your issue with the touchscreen?
I've just down the same thing using Magisk. Everything was fine until I flashed the magisk.patched.img. The device booted up but the touchscreen doesn’t work no matter what.
Please let me know of your solution.
Thank you kindly.
Click to expand...
Click to collapse
hey did you fix it or something? i got the same problem, and idk what to do, can you help?
I never solved it.
In the end I was able to get a Moto G8 Plus that I was able to unlock the bootloader and root using Magisk.
PamelaGirl said:
I never solved it.
In the end I was able to get a Moto G8 Plus that I was able to unlock the bootloader and root using Magisk.
Click to expand...
Click to collapse
sadly the phone i tried to root is the only phone that i have
I understand the frustration my friend. I tried and tried but it just doesn’t work with Moto G Power.
PamelaGirl said:
I understand the frustration my friend. I tried and tried but it just doesn’t work with Moto G Power.
Click to expand...
Click to collapse
i think i got how to do it, u need to use LENOVO MOTOROLA SMART ASSISTANT and it works i think, i am going to try it, there is a tutorial in this forum, sadly only works if u have windows, but i manage to go to a place that has windows pc https://forum.xda-developers.com/t/moto-g-power-flashing-guide.4159301/
klninja said:
i think i got how to do it, u need to use LENOVO MOTOROLA SMART ASSISTANT and it works i think, i am going to try it, there is a tutorial in this forum, sadly only works if u have windows, but i manage to go to a place that has windows pc https://forum.xda-developers.com/t/moto-g-power-flashing-guide.4159301/
Click to expand...
Click to collapse
That’s a good find. Please report back with your success so I stand corrected.
PamelaGirl said:
That’s a good find. Please report back with your success so I stand corrected.
Click to expand...
Click to collapse
a person already did this
That’s good news!
Now its your turn.
PamelaGirl said:
That’s good news!
Now its your turn.
Click to expand...
Click to collapse
i would like to ask a question, when ur g8 wasnt working did the phone charge or not? cus mine dont show how much battery i have
Sorry I honestly cannot recall. I was so frustrated at that time, blinded to get the root to work that I did not notice.