Related
well, im pretty new at this, this is the first time i root and flash something in my htc vivid, i was trying to install the de-sensed rom and i followed a guide on this forum for the htc vivid, now just before installing the rom, i was told to enter recovery mode and wipe this and that and then install, but before i could i wasnt able to enter recovery mode. Im in HBOOT just as before and when i click recovery a white htc logo appears and i am redirected to fastboot, i dont know what to do, if it helps when i enter bootloader it kinda looks for some images or something like that and doesnt find any, it did that before but i could access recovery
Did you try and reflash the recovery ?
Bigtjmc said:
Did you try and reflash the recovery ?
Click to expand...
Click to collapse
ill look that up and try it, ill post results, thanks for your answer!
do you know by any chance where i can get the stock recovery for htc vivid? or do i have to use a different one? if so which one ?
you can get tool kit and it makes life easy and you can flash recovery in a second .
---------- Post added at 10:20 PM ---------- Previous post was at 09:58 PM ----------
K first off u need to have the boot loader unlocked and then you need a custom recovery prog.
Then you van flash the boot IMG in flash boot cmd via pc then install the rest of the Rom on the ph in recovery , or to make life easy get the ph to s off then no pc is needed just flag the Rom ..
THANKS
Bigtjmc said:
you can get tool kit and it makes life easy and you can flash recovery in a second .
---------- Post added at 10:20 PM ---------- Previous post was at 09:58 PM ----------
K first off u need to have the boot loader unlocked and then you need a custom recovery prog.
Then you van flash the boot IMG in flash boot cmd via pc then install the rest of the Rom on the ph in recovery , or to make life easy get the ph to s off then no pc is needed just flag the Rom ..
Click to expand...
Click to collapse
it worked!
i downloaded the 2.2 toolkit, hit install cwm and boom im in thank you!
Good job , if ya need more help let us know .
Hello, I am using a rooted kindle fire 5th gen on 5.3.1 OS. Recently, I attempted to install a custom recovery to no avail. My problem now, however, is I have messed up the ability to access kindle's default recovery mode. I have attempted to use the button method on startup, reboot in recovery with apps such as titanium backup, rom manger, quick reboot, and I have tried using commands in terminal emulator app. Every time however my fire gets stuck at the white amazon logo on start up. I left it there for nearly 24 hours and still never booted into recovery. Each time I am forced to manually power down and turn back on for regular startup. The kindle doesn't give me any problems other than I cant access recovery mode! I would I would welcome any suggestions and greatly appreciate some help. Thank you and Happy New Year!!
DJ
I had the same problem unfortunately you can't really install custom recoveries on the fire OS 5 please tell me you made a backup of your old recovery
---------- Post added at 07:24 AM ---------- Previous post was at 07:19 AM ----------
You can use flash fire to install custom roms but don't do it until you have your recovery fix if you mess up you brick your device forever if you don't have your recovery back
---------- Post added at 07:47 AM ---------- Previous post was at 07:24 AM ----------
Here is the recovery you need to flash if you didn't back up
https://drive.google.com/file/d/0B5pfjMkNO_nMZFJjWWl2QmpFT3M/view?usp=drivesdk
Thanks!
ANDROID2468 said:
I had the same problem unfortunately you can't really install custom recoveries on the fire OS 5 please tell me you made a backup of your old recovery
---------- Post added at 07:24 AM ---------- Previous post was at 07:19 AM ----------
You can use flash fire to install custom roms but don't do it until you have your recovery fix if you mess up you brick your device forever if you don't have your recovery back
---------- Post added at 07:47 AM ---------- Previous post was at 07:24 AM ----------
Here is the recovery you need to flash if you didn't back up
Thank you for helping me! I attempted to the recovery on with a command window in fastboot mode. I used the command: "fastboot flash recovery" then drug the image to the command line. Upon hitting enter it says my disc image is corrupt. How can I flash this image?
Click to expand...
Click to collapse
The bootloader is locked so that probably why you have that error try going to the play store and bownload an app called rashr and flash it that way
Problem Solved
ANDROID2468 said:
The bootloader is locked so that probably why you have that error try going to the play store and bownload an app called rashr and flash it that way
Click to expand...
Click to collapse
You my friend are a godsend. I got recovery back and I've backed up this time lol. I shouldn't have been messing around with custom recoveries too much being new at this and all, but hey trial and error. Thanks for your help!!
Your welcome and Here is a link on how to install slim ROM using flash fire
Hello guys,
this is my first thread and I have a serious problem:
First, I unlock the bootloader and flash TWRP on it. It seems working, because every time it's booting there comes a message, that I can't trust this device, cause it's unlocked.
The problem is, when i go in fastboot mode, it says "FRP locked") and in the dev-options I can't change the setting (oem unlock). Now when its connected with PC (fastboot Mode), and I try everytime to flash Data there is this error: "FAILED (remote: Command not allowed)"
So...I format all data with TWRP (no OS anymore). Now I know there is no custom ROM for this device out. I was totally fckd up.
I download the update.zip (Stock Rom update) from another Thread and unpack boot.img, recovery.img and system.img from update.app (cause I don't know how to flash it otherwise).
I tried to flash every 3 img. data with TWRP - only the boot.img and recovery.img was installed. Now my device is Bricked because of Im stupid.
So I can only try to flash data with holding vol+ and vol- and power. I also tried eRecovery, but everytime, I tells me that there was a problem by downloading the package.
The fastboot mode is useless, cause there is this bug (read above).
Can you tell me, is there a method to flash update.zip, or another way, or is this device totally broken?
Thanks!!:crying:
Which firmware you had before brick?
MobileTechArena said:
Which firmware you had before brick?
Click to expand...
Click to collapse
I think it was the EMUI 5.0.1 Version (newest) with Android 7.0
70X1C said:
I think it was the EMUI 5.0.1 Version (newest) with Android 7.0
Click to expand...
Click to collapse
PRA-LX1?
MobileTechArena said:
PRA-LX1?
Click to expand...
Click to collapse
Exacly
70X1C said:
Exacly
Click to expand...
Click to collapse
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
MobileTechArena said:
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
Click to expand...
Click to collapse
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
70X1C said:
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
Click to expand...
Click to collapse
Then try to put UPDATE.APP into dload and do Force update.
70X1C said:
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
Click to expand...
Click to collapse
Is you FRP locked? Try to unlock bootloader again, fastboot oem unlock "your unlock code". Then try to flash TWRP again. Don't bother with Dload and forced update as that doesn't work.
MobileTechArena said:
Is you FRP locked? Try to unlock bootloader again, fastboot oem unlock "your unlock code". Then try to flash TWRP again. Don't bother with Dload and forced update as that doesn't work.
Click to expand...
Click to collapse
I have no idea of the cause, but dload never worked for me too.
This only works if you can boot to Android and Developer Options menu opens for you (if they don't you'll end up with bricked device).
Boot into the Fastboot mode and relock your device (Command: "fastboot oem relock (unlock code)" ).
Then you'll be able to unlock the OEM Lock from the Developer Options menu. (And after it you can go back to Fastboot and unlock the bootloader again to reinstall the TWRP).
You still need help?
MobileTechArena said:
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
Click to expand...
Click to collapse
Where exactly is the rescue system file? I can't seem to find it
theholycutu said:
Where exactly is the rescue system file? I can't seem to find it
Click to expand...
Click to collapse
Looks like they removed it from that site. If i find it somewhere i will share it.
.
MobileTechArena said:
Looks like they removed it from that site. If i find it somewhere i will share it.
.
Click to expand...
Click to collapse
Thanks a lot
theholycutu said:
Where exactly is the rescue system file? I can't seem to find it
Click to expand...
Click to collapse
https://mega.nz/#!k0MzQL5T!yHj-2n9DuGvb-ZdsemOgw4k3vQTMy7CJXIGFAhJlplo
Sorry I have seen the thread just before.
Please let me know when you downloaded it. I'll take it out again.
ChinHon said:
https://mega.nz/#!k0MzQL5T!yHj-2n9DuGvb-ZdsemOgw4k3vQTMy7CJXIGFAhJlplo
Sorry I have seen the thread just before.
Please let me know when you downloaded it. I'll take it out again.
Click to expand...
Click to collapse
I downloaded it thanks a lot
:good:
please help me. i also have a bricked p8 lite 2017. but i can boot into. TWRP,fastboot,system upgrade
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
man i also have a bricked p8 lite 2017, did you solve your problem? help me please
EXE bahotin said:
please help me. i also have a bricked p8 lite 2017. but i can boot into. TWRP,fastboot,system upgrade
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
man i also have a bricked p8 lite 2017, did you solve your problem? help me please
Click to expand...
Click to collapse
I get ERROR: 255 and I have tried a lot of options and still haven't got to any solutions.. still attempting to solve it, too
Hi guys, muy English is not so good, but here we go:
I had a problem after rooting my P10, my phone is a VTR-L09c605 and I rebranded it to VTR-L29c432 successfully and after that I updated it to Oreo (b360) using the hwota.bat successfully again.
I flashed twrp for oreo and I installed magisk v16 without problems, it worked so fine until I decided to debloat a bit the phone, I remember that I uninstaled all the Gapps (using a Fx file explorer directly from system partition) and other app that I can't remember, after that I rebooted the phone and was stuck at bootloop, I saw the huawei bootanimation normarly (the bubbles with blue background) and the phone restarted again and again... In that moment I rebooted into twrp and wipe cache partition, I flashed this stock ramdisk https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482 and no luck (I don't know why I did it).
After that, I tried to flash the full ota using the hwota.bat but i was stuck at "your device has been unlocked and cannot be trusted, the phone is booting now" that message appears always when I tried to enter into twrp or erecovery but now it was stuck in that message and I rebooted it manually into fastboot, maybe the problem was that whem I tried to flash again the oreo full ota, I used the same files (contained in the recovery folder (twrp and recovery nocheck) from nougat.
Please guys, help me, I still can boot into fastboot, but can't boot into twrp(even flashing it via fastboot recovery_ramdisk) or erecovery, maybe the hwota.bat needs to be edited, but I don't know what lines I need to change, if someone knows how to repair the phone, please, help me.
Thanks in advanced
If you deleted some system app or system file by mistake it wont probably boot, try to flash ramdisk, original recovery_ramdisk, original kernel, and original system.img to see if it boots again, I would just try the first ramdisk(to get rid of root) recocery_ramdisk and original kernel.
Sent from my [device_name] using XDA-Developers Legacy app
lil_kujo said:
If you deleted some system app or system file by mistake it wont probably boot, try to flash ramdisk, original recovery_ramdisk, original kernel, and original system.img to see if it boots again, I would just try the first ramdisk(to get rid of root) recocery_ramdisk and original kernel.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I flashed some of them using fastboot, I extract them from the update.zip from the oreo's full ota (update.app) and using the huawei extractor, but there's a lot of recovery files, how to know which is the correct?
You just need recovery_ramdis.img it's written wrong in there and also ramdisk.img you also need kernel.img try with those only I have those file on my PC but I'm not home I could upload them and share you the link but it would be later.
Sent from my [device_name] using XDA-Developers Legacy app
lil_kujo said:
You just need recovery_ramdis.img it's written wrong in there and also ramdisk.img you also need kernel.img try with those only I have those file on my PC but I'm not home I could upload them and share you the link but it would be later.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
No success my friend, I'm still getting the error mode: please update system again, and can't boot into recpvery (I flashed it)
The files that tou have are for oreo? I'm on L29c432b360
I'm a bit desperate, hope it can be fixed :/
Yes I have that same build and model, done worry u had the same issue before and it took me awhile to recover it , for sure it has a fix. Remember i flashed some other file last time but don't remember which since they are in my PC, do you have frp unlocked and phone unlocked ? Do you have access to you unlocked key? I would try to relock now that you are on the stock recovery and try to factory reset once it enters erecovery after it gets lock it performs a factory wipe
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
Also try to press the volume up and down at the same time to enter update mode
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
sfoot13 said:
No success my friend, I'm still getting the error mode: please update system again, and can't boot into recpvery (I flashed it)
The files that tou have are for oreo? I'm on L29c432b360
I'm a bit desperate, hope it can be fixed :/
Click to expand...
Click to collapse
Yes I had a similar issues same thing try to relock it and just make sure to be in stock recovery and ramdisk also and stock kernel. Once you relocked it I should do a factory reset try if that works.
Sent from my [device_name] using XDA-Developers Legacy app
lil_kujo said:
Yes I have that same build and model, done worry u had the same issue before and it took me awhile to recover it , for sure it has a fix. Remember i flashed some other file last time but don't remember which since they are in my PC, do you have frp unlocked and phone unlocked ? Do you have access to you unlocked key? I would try to relock now that you are on the stock recovery and try to factory reset once it enters erecovery after it gets lock it performs a factory wipe
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
Also try to press the volume up and down at the same time to enter update mode
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Yes I had a similar issues same thing try to relock it and just make sure to be in stock recovery and ramdisk also and stock kernel. Once you relocked it I should do a factory reset try if that works.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, I have frp and phone unlocked and I have my unlock key (saved as screenshot and .txt file).
So, if I relock my bootloader, it will do a low level format but actually I can't access to erecovery and update mode, because it fails to enter in that mode and I always get the error mode message.
But, there's a possibility to lock the bootloader and doing that, that action unlocks the access to erecovery? (sounds like a mess )
I'm not at home now, I'll try what you said me, and I'll wait until you can upload the files
Thank you so much for your help, I really appreciate it
Any success? I have the same problem. Im about ready to cough up 20 euros but im hopefully waiting for a solution.
I have same problem... Did you fix your phone? Some metohds for other guys work but not for me
We need a good tuto on that...Im stuck too now after trying some mods in build.prop
whats the adb command to flash erecovery-kernel/ramdisk ect.
---------- Post added at 03:32 PM ---------- Previous post was at 03:16 PM ----------
Cant extract Update.app in huawei update extractor...got error
Recovery_ramdisk.img Invalid header crc - Expected:22935 got 52610
really need help here hehehe
here are the results.. same as other guy,on that 432..
first of all.huawei update extractor wont open the update.pp from the HWOTA_VTRC432B360-Oreo package giving ramdisk error.....
have access to fastboot..
unlocked frp/bootloader
on stock recovery and cant flash any recovery---- twrp..it give some some partition error
successfully flashed :
kernel with erecovery_kernel_a.img
kernel with kernel_a.img
ramdisk with ramdisk_a.img
FAILED to flash:
erecovery_ramdisk_a with fastboot flash ramdisk erecovery_ramdisk_a.img (is it the good command ? )
recovery_ramdisk_a.img with fastboot flash ramdisk and recovery
so,whats next
please
all that cuz of frikkin build.prop MODIF.
i did re lock with low level reset...
i re unlock for another low level reset...
just wont boot anymore
when booting normally it takes me directly to firmware dload screen and fail to dload of course....
virusdunil said:
here are the results.. same as other guy,on that 432..
first of all.huawei update extractor wont open the update.pp from the HWOTA_VTRC432B360-Oreo package giving ramdisk error.....
have access to fastboot..
unlocked frp/bootloader
on stock recovery and cant flash any recovery---- twrp..it give some some partition error
successfully flashed :
kernel with erecovery_kernel_a.img
kernel with kernel_a.img
ramdisk with ramdisk_a.img
FAILED to flash:
erecovery_ramdisk_a with fastboot flash ramdisk erecovery_ramdisk_a.img (is it the good command ? )
recovery_ramdisk_a.img with fastboot flash ramdisk and recovery
so,whats next
please
all that cuz of frikkin build.prop MODIF.
i did re lock with low level reset...
i re unlock for another low level reset...
just wont boot anymore
when booting normally it takes me directly to firmware dload screen and fail to dload of course....
Click to expand...
Click to collapse
Same to me. Also i can flash CUST and some TWRPs but doesnt want to boot in recovery
I have fixed mine this morning by extracting KERNEL.img from update.app
fastboot flash kernel KERNEL.img
my p10 got back to life after trying all flashable things for maybe 6 hours yesterday
:silly:
I was stuck in error mode and managed to get out of it. I reached this gloriously by trying to flash Magisk V15.4 zip and then the oreoupgrade (from Jannomag), which failed..
First I tried the Multi-Tool method. Didn't work for me. Flashing was succesful, but no change in boot status.
So I slept over it and today I tried DC Phoenix. Selected the UPDATE.APP from update.zip and the UPDATE.APP from update_full_hw.zip. I cross my fingers and waited. It took a long time^^ When finished, it didn't reboot automatically. So I removed the cable and shut it down by pressing Power Button for some seconds. It booted then into eRecovery and I was confused.. It tried to download firmware via WiFi etc, but failed then with some ID error or smth, idk. I rebooted ....
aaaaaand voila: Booted without problems, all data still there!! :victory:
I sent it to tech service, tomorrow I'll know if they fixed my phone.
I think that I hard bricked it, because I relocked the bootloader, so the phone stuck at huawei's logo, no fastboot mode, no recovery, nothing, so guys, NEVER RELOCK THE BOOTLOADER if you get an error like that, it's the worst IDEA that you can have.
I'm a bit confused with this phone, looks like the system is very sensitive if you make modifications, like debloating or add or remove some lines in build.prop, things like tha.
Sadly, there's no much development for this phone :/
@Fenryl93 Happy to know that you fixed your phone bro!
@virusdunil you were using Oreo or Nougat? I was on Oreo, so I think that I'll not install Oreo until it becomes official :/
..
sfoot13 said:
@virusdunil you were using Oreo or Nougat? I was on Oreo, so I think that I'll not install Oreo until it becomes official :/
Click to expand...
Click to collapse
I was on nougat....VTR-L09 then rebranded it
Finally, the tech service repaired my phone, they changed the electronic board, well, that's what they wrote in the report.
So, I have my phone back, I'll try to be more careful this time.
I am new and I don't have much experience in custom rom, recovery, kernel etc. and I think I was wrong in some procedure.
I have a problem with my Moto E5 XT1944-3, I wanted to install the TWRP by following these steps:
https://forum.xda-developers.com/moto-e5/development/recovery-twrp-3-2-3-x-moto-e5-plus-t3912189
(I have the bootloader unlocked)
The inconvenience came when I restarted in recovery mode and the touch did not work (only in recovery mode), which led me to flash again twrp-x.x.x.x.img but still the same. What I ventured on the Internet to find solutions and simplifying, I ended up flashing the recovery img as follows: fastboot flash boot twrp-x.x.x.x.img (I guess the problems started there)
*The E5 did not turn on with the logo and did not start the OS, I tried to use the Lenovo tool to restore the E5 and it says that it is not compatible (maybe because of the unlocked bootloader) although it allowed you the option to search for it within the "compatible" smartphones . I tried from the fastboot tool to try to revive the E5 but it does not start the system. Nor does he let me use: fastboot erase system / data / recovery; to try to make a clean installation.
* The last thing I try is to reinstall the TWRP and try to use the USB-OTG with the mause, but, although it has electricity, the mause does not appear and if the screen is turned off and then on again it remains blank forcing me to a forced restart.
* Oh and download an AOSPEXTENDED ROM and install the img with fastboot and it didn't load the logo but the boot animation but it was just a loop
* Any idea what to do?
* I think that if the recovery worked correctly, I could solve this.
Greetings from Argentina using the google translator :dedos cruzados:
Did you flash the correct recovery? Your phone is the Moto E5 Nora variant
---------- Post added at 07:08 PM ---------- Previous post was at 07:04 PM ----------
And the command is like this:. fastboot flash recovery xxxxxc.bin
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
Dont use fastboot flash boot or you will overwrite the bootloader
loco72 said:
Dont use fastboot flash boot or you will overwrite the bootloader
Click to expand...
Click to collapse
And fastboot flash bootloader... did you forgot? And remember, NEVER EVER use fastboot erase bootloader, as it will brick your device.