Ok I've got my opx, unlocked the bootloader and installed twrp, don't know how I forgot to make a backup before flashing supersu and now my phone can only enter twrp, nothing else. Can someone please make a nandroid backup and share it with me, I'm trying to restore it that way. Or can I do anything else? Any help will be appreciated, thanks!
Sent from my XT1033 using Tapatalk
demolatorul said:
Ok I've got my opx, unlocked the bootloader and installed twrp, don't know how I forgot to make a backup before flashing supersu and now my phone can only enter twrp, nothing else. Can someone please make a nandroid backup and share it with me, I'm trying to restore it that way. Or can I do anything else? Any help will be appreciated, thanks!
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Stock rom link:
http://forum.xda-developers.com/onep...-dump-t3244996
Stock recovery:-https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing
2. Now boot into twrp recovery
3. Mount you storage in twrp mount option.
4. Copy the rom and stock recovery...unmount.
5.. Boot into TWRP. Install -> Select Images -> Select the recovery.img -> Proceed. Scrn shts added
6.Now Do not reboot from TWRP, your oneplus would freeze instantly. Do a "adb reboot recovery" from terminal/command-prompt instead. This will reboot to stock recovery.(if you havr installed new 2.8.7.0 there is no bug like freeze)
7. After having boot into Stock recovery, Flash full system Dump
Hit thanks if helped
Thanks, all I needed was the stock rom to flash it, thanks man!
Sent from my XT1033 using Tapatalk
i have a big problem
C:\adb\cm11s>fastboot flash recovery stock_recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.515s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
when i type fastboot oem unlock my oneplus x boot end`s in Bootloop
sorry for bad english i am German :crying:
bj82xx said:
i have a big problem
C:\adb\cm11s>fastboot flash recovery stock_recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.515s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
when i type fastboot oem unlock my oneplus x boot end`s in Bootloop
sorry for bad english i am German :crying:
Click to expand...
Click to collapse
Same here! Bit stuck on what to do? Any ideas?
Solved IT
dagstar said:
Same here! Bit stuck on what to do? Any ideas?
Click to expand...
Click to collapse
- Unbrick it http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
- Update the Bootloader with the latest one : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
-Thats it
THANKS
mohammedtabish said:
Stock rom link:
http://forum.xda-developers.com/onep...-dump-t3244996
Stock recovery:-https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing
2. Now boot into twrp recovery
3. Mount you storage in twrp mount option.
4. Copy the rom and stock recovery...unmount.
5.. Boot into TWRP. Install -> Select Images -> Select the recovery.img -> Proceed. Scrn shts added
6.Now Do not reboot from TWRP, your oneplus would freeze instantly. Do a "adb reboot recovery" from terminal/command-prompt instead. This will reboot to stock recovery.(if you havr installed new 2.8.7.0 there is no bug like freeze)
7. After having boot into Stock recovery, Flash full system Dump
Hit thanks if helped
Click to expand...
Click to collapse
Onyx was soft bricked, when booting, the bottom text disappeared, so boot loop. This method help me to restore everything as default, and worked perfectly! Thanks so much!!!!
Related
Here is my issue, will try to explain as much as I can:
So I got the phone only booting to the LG logo and no further. So I read a couple threads which were mentioning about the LG Flash tool that I could try to use to restore the device, that did not work. So I tried to do Fastboot to see if that would help in any way. After trying, I was able to get Fastboot using @Lelus method ,now I cant get back the S/W upgrade mode, trying everything i could think of and still no progress. Would really love to fix this device and appreciate any help I can get.
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
mechen said:
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
Click to expand...
Click to collapse
Already tried all that. Phone does not boot or nothing. I can only access fastboot. I cant even flash the ICS u and x boot. When I try it says remote: partition doesn't exist.
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
trumpiks said:
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
Click to expand...
Click to collapse
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Liger878 said:
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Click to expand...
Click to collapse
Ok now thats strange, you have all the drivers? ADB, OMAP, FASTBOOT
Yeah, everything is installed and installed properly.
Sent from my SGH-T959 using XDA Free mobile app
Hi, all.
I was messing around with Android Tweaker 2, zipaligning my apps, performing vague system tweaks and the like, when I rebooted my phone for the changes to take effect; however, the phone booted up, finished the booting animation, and where the home screen should be showing up only showed a black screen. From there I can only reboot again, reboot into STOCK recovery, or reboot into fastboot, which has limited function in an Asus device (inability to flash unsigned custom recovery images, inability to flash rom images, stock firmware images are unavailable ANYWHERE, etc.) My device WAS rooted, however, I did a factory reset from the stock recovery in hopes that the problem would be resolved, so I'm not sure if root access was retained. I've tried a lot of things, but what I need is access to adb to push some files, or just figure out what the hell happened to the device.
Any ideas? Thanks in advance.
Details:
Asus Padfone X [4.4.2 stock rom]
WAS rooted
LOCKED bootloader
STOCK recovery
Fastboot is basically useless, given the "safeguards" Asus has implemented
Read the CM12.1 for instructions on unlocking bootloader , there are instructions on booting from custom recovery using fastboot from there you can adb push the files to your phone as posted in the Nandroid Stock backup thread and install using TWRP.
daggorlad said:
Read the CM12.1 for instructions on unlocking bootloader , there are instructions on booting from custom recovery using fastboot from there you can adb push the files to your phone as posted in the Nandroid Stock backup thread and install using TWRP.
Click to expand...
Click to collapse
Thanks for the advice.
I have consulted the CM12.1 thread, and I see the instructions, the first step of which is to "boot into CWM, CMRecovery, or TWRP." However, I do not have any of these custom recoveries flashed on my Padfone X. Is there a way I can boot custom recovery off an external microsd or something?
Note: upon attempting the "fastboot flash recovery CMrecovery.img" command, the cmd window returns the following:
Code:
target reported max download size of 1879048192 bytes
sending 'recovery' <11220 KB>...
OKAY [ 0.438s ]
writing 'recovery'...
FAILED <remote: can't flash unsigned image>
finished. total time: 0.444s
EDIT: Problem has been resolved, used
Code:
fastboot boot twrp.img
and restored stock.
shattered519 said:
Thanks for the advice.
I have consulted the CM12.1 thread, and I see the instructions, the first step of which is to "boot into CWM, CMRecovery, or TWRP." However, I do not have any of these custom recoveries flashed on my Padfone X. Is there a way I can boot custom recovery off an external microsd or something?
Note: upon attempting the "fastboot flash recovery CMrecovery.img" command, the cmd window returns the following:
Code:
target reported max download size of 1879048192 bytes
sending 'recovery' <11220 KB>...
OKAY [ 0.438s ]
writing 'recovery'...
FAILED <remote: can't flash unsigned image>
finished. total time: 0.444s
EDIT: Problem has been resolved, used
Code:
fastboot boot twrp.img
and restored stock.
Click to expand...
Click to collapse
Glad I was able to point you into the right direction.
Hi,
I tried to install TWRP on my Honor 5X KIW-UL00, but its seems to fail..
I successfully got my unlock code and unlock the bootloader. (Somes stranges chineses signs are appearing under the boot logo )
I flash TWRP using the command
Code:
fastboot flash recovery twrp-3.0.2-0-kiwi.img
I get the response:
Code:
C:\adb>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.466s]
writing 'recovery'...
OKAY [ 0.704s]
finished. total time: 2.171s
BUT ! When I reboot to recovery mode (Power + Volume Up) I get the "Huawei eRecovery" and not TWRP...
Any ideas ?
What am I missing ?
Thanks
Ok, it seems solved.
I tried it 2 times again and it happens something differently at the reboot (There was a "Optimizing" screen).
I try recovery mode again and tatatata ! it worked !
bmerklen said:
Ok, it seems solved.
I tried it 2 times again and it happens something differently at the reboot (There was a "Optimizing" screen).
I try recovery mode again and tatatata ! it worked !
Click to expand...
Click to collapse
Glad you fixed it mate.
bmerklen said:
Ok, it seems solved.
I tried it 2 times again and it happens something differently at the reboot (There was a "Optimizing" screen).
I try recovery mode again and tatatata ! it worked !
Click to expand...
Click to collapse
Are there more details to this solution? I'm stuck with this issue and I've tried a tad bit more than 2 times haha.
For me the secret was the reboot after the flash. You need to reboot peacefully at least 1 time before accessing the recovery.
bmerklen said:
For me the secret was the reboot after the flash. You need to reboot peacefully at least 1 time before accessing the recovery.
Click to expand...
Click to collapse
To clarify, your way that fixed it is:
- Flash the Recovery
- Reboot Normally
- Reboot to Recovery
instead of
- Flash the Recovery
- Reboot to Recovery
Alright, I'll try this when I am home. Will Update!
Update: Didn't work, unfortunately D:
fastboot boot kiwi_twrp_3-21_recovery.img
Yes, that's the key, after flashing recovery, I always do a system reboot rather than recovery
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
Hi,
Last week I got my phone stuck in a bootloop which led to me making a lot of mistakes, I flashed a boot.img as a kernel, I deleted my entire software, and I lost a lot of files. I currently have my phone in an error mode, it says I have to update the system again. I have access to fastboot but I do not have access to twrp (flashing the recovery doesn't work).
Can anyone help me with this problem?
pim8181 said:
Hi,
Last week I got my phone stuck in a bootloop which led to me making a lot of mistakes, I flashed a boot.img as a kernel, I deleted my entire software, and I lost a lot of files. I currently have my phone in an error mode, it says I have to update the system again. I have access to fastboot but I do not have access to twrp (flashing the recovery doesn't work).
Can anyone help me with this problem?
Click to expand...
Click to collapse
Is a really fastboot mode or error mode?
If it is fastboot what you see, Phone unlocked and FRP unlock?
kilroystyx said:
Is a really fastboot mode or error mode?
If it is fastboot what you see, Phone unlocked and FRP unlock?
Click to expand...
Click to collapse
I can get in both fastboot and error mode, I think fastboot is the most useful. It says PHONE Unlocked and FRP unlocked.
pim8181 said:
I can get in both fastboot and error mode, I think fastboot is the most useful. It says PHONE Unlocked and FRP unlocked.
Click to expand...
Click to collapse
-Do you know exactly which files or partitions did you mess?
-What is your region code and build number?
If you don’t know run this command is fastboot mode => fastboot oem get-build-number
-Do you have a TWRP backup from your device?
kilroystyx said:
-Do you know exactly which files or partitions did you mess?
-What is your region code and build number?
If you don’t know run this command is fastboot mode => fastboot oem get-build-number
-Do you have a TWRP backup from your device?
Click to expand...
Click to collapse
I don't know for sure which parts I messed up, but I do know these thing: I don't have an OS installed, and my kernel is a boot.img.
I don't know my region number for sure, but according to this post: https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473 it should be C432.
My build number is ANE-LX1 8.0.0.126 (C432) and I should have a TWRP backup on my sd card from the moment my phone was only bootlooping.
pim8181 said:
I don't know for sure which parts I messed up, but I do know these thing: I don't have an OS installed, and my kernel is a boot.img.
I don't know my region number for sure, but according to this post: https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473 it should be C432.
My build number is ANE-LX1 8.0.0.126 (C432) and I should have a TWRP backup on my sd card from the moment my phone was only bootlooping.
Click to expand...
Click to collapse
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
kilroystyx said:
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
Click to expand...
Click to collapse
I can't install TWRP, I currently install it by flashing the file as a recovery_ramdisk.
After it is flashed I execute the command fastboot reboot and hold volume up whilst disconnecting my phone from my PC.
Do you have any tips?
pim8181 said:
I can't install TWRP, I currently install it by flashing the file as a recovery_ramdisk.
After it is flashed I execute the command fastboot reboot and hold volume up whilst disconnecting my phone from my PC.
Do you have any tips?
Click to expand...
Click to collapse
No, you are doing right. Can you post the output from fastboot during the installation?
kilroystyx said:
No, you are doing right. Can you post the output from fastboot during the installation?
Click to expand...
Click to collapse
Code:
fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
gives:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.122s]
finished. total time: 0.811s
Since I can't boot in TWRP by holding down the volume up button when rebooting I tried to use the boot command:
Code:
fastboot boot TWRP_3.2.1-0_ANE-LX1_Full_01.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.695s
pim8181 said:
Code:
fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
gives:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.122s]
finished. total time: 0.811s
Since I can't boot in TWRP by holding down the volume up button when rebooting I tried to use the boot command:
Code:
fastboot boot TWRP_3.2.1-0_ANE-LX1_Full_01.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.695s
Click to expand...
Click to collapse
I don't believe that fastboot boot can work...
That is strange...
Can you flash TWRP one more time?
After successful flash don't use the command fastboot reboot
Unplug the USB cable and press ON/OFF and VOL+ and stay pressings until you see TWRP screen.
kilroystyx said:
I don't believe that fastboot boot can work...
That is strange...
Can you flash TWRP one more time?
After successful flash don't use the command fastboot reboot
Unplug the USB cable and press ON/OFF and VOL+ and stay pressings until you see TWRP screen.
Click to expand...
Click to collapse
It didn't work , maybe I can flash the stock system image from fastboot?
pim8181 said:
It didn't work , maybe I can flash the stock system image from fastboot?
Click to expand...
Click to collapse
Yes, system, cust, recovery_ramdisk.... all partions that might be mess by you.
kilroystyx said:
Yes, system, cust, recovery_ramdisk.... all partions that might be mess by you.
Click to expand...
Click to collapse
I don't know how to get these ones can you explain it to me?
pim8181 said:
I don't know how to get these ones can you explain it to me?
Click to expand...
Click to collapse
Check this thread, this applies to recovery_ramdisk but for all other partitions is the same.
kilroystyx said:
Check this thread, this applies to recovery_ramdisk but for all other partitions is the same.
Click to expand...
Click to collapse
It worked, many thanks for your help!
For those that have issues with the programme, I had to uncheck the verify header checksum button in the settings file in order for it to work properly.
kilroystyx said:
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
Click to expand...
Click to collapse
I guess I spoke too soon, I can get my phone in TWRP but it continues to bootloop.
pim8181 said:
I guess I spoke too soon, I can get my phone in TWRP but it continues to bootloop.
Click to expand...
Click to collapse
Did you do wipes?
If didn't work use your TWRP backup or use HuRUpdater
kilroystyx said:
Did you do wipes?
If didn't work use your TWRP backup or use HuRUpdater
Click to expand...
Click to collapse
My TWRP is completely lost and the tool doesn't seem to work, I wiped data cache and dalvik.
When you flash a rom aren't you just supposed to flash the rom itself, when I bricked my phone by installing Xposed I just reflashed the rom it's sytem image and a boot image. How should I do it?