[Technical Support] Can't boot into recovery mode - OnePlus X Q&A, Help & Troubleshooting

Hi there,
I'm pretty new to zip flashing, but after the installation I regretted and wanted it removed. Before that I had made an entire backup, which I then restored and since then my phone has not been able to boot.
I've tried to boot into recovery mode but without any luck. It's stuck on the OnePlus logo.
I can get it in Fastboot though but that's about it and the normal power on results in bootloop.
I've been reading many topics about this but in all cases it's crucial that you've enabled USB Debugging which is quite the task since I'm not able to boot it up.
Hope you guys can help me since I don't have any spare phone at the moment.
P.S. I'm on OP X with OxygenOS.
EDIT: Solved

MattBooze said:
Hi there,
I'm pretty new to zip flashing, but after the installation I regretted and wanted it removed. Before that I had made an entire backup, which I then restored and since then my phone has not been able to boot.
I've tried to boot into recovery mode but without any luck. It's stuck on the OnePlus logo.
I can get it in Fastboot though but that's about it and the normal power on results in bootloop.
I've been reading many topics about this but in all cases it's crucial that you've enabled USB Debugging which is quite the task since I'm not able to boot it up.
Hope you guys can help me since I don't have any spare phone at the moment.
P.S. I'm on OP X with OxygenOS.
EDIT: Solved
Click to expand...
Click to collapse
Hi there, can u help me solve this problem..i have the same problem as yours..Now i dont know what to do..i have tried the mega unbrick but no luck at all still the same issues stuck at the boot logo and reboot itself..i need your help fast..contact me at [email protected] Email me there..please

Basically this is how it goes: You have to have an unlocked bootloader or else it will more than likely not boot into a tampered system. Unlocking the bootloader is simple on this phone and does not void the warranty, but to do so you have to have enabled "OEM unlock" in the developer settings which from the sounds of it you didn't. I'm going to cut and paste some of my response I've sent to other people here:
The first thing you're going to need to do is to flash the stock Recovery from OnePlus. Ypu will flash it the same way you flashed TWRP (if you did) with Fastboot. If you haven't done that and need me to explain it I will, I'll be here all day. Download the recovery here: https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
Next, the recovery will normally only flash the stock ROM as provided by OnePlus. You can download that file from here: http://downloads.oneplus.net/2016-04-02/opx/OnePlus_X_OxygenOS_2.2.1/ . Flash that with the stock recovery and then do a Factory Data Reset. You will not lose pictures, music, whatever. You won't lose the backup you made either. We just need it to boot into OOS so you can turn on the unlock option.
Reboot the phone. It might take a while. Once you're into the device everything should be working as normal. Go to Settings -> About Phone. Scroll down and tap the "Build Number" until it says you've enabled Developer settings. Go to Settings -> Developer and turn on OEM Unlock. Now you can boot back into Fastboot, and from your computer use the command "fastboot oem unlock" as simple as that and it will unlock the bootloader. Now if you'd like you can safely reflash the TWRP recovery and you should be able to restore your backup.
---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------
husandroid said:
Hi there, can u help me solve this problem..i have the same problem as yours..Now i dont know what to do..i have tried the mega unbrick but no luck at all still the same issues stuck at the boot logo and reboot itself..i need your help fast..contact me at [email protected] Email me there..please
Click to expand...
Click to collapse
I'm not using email but you can read my reply above if you're having the same problem.

I get;
FAILED (remote: dtb not found) when I try to boot, any suggestions?

o.maille said:
I get;
FAILED (remote: dtb not found) when I try to boot, any suggestions?
Click to expand...
Click to collapse
Just reboot manually dude.

o.maille said:
I get;
FAILED (remote: dtb not found) when I try to boot, any suggestions?
Click to expand...
Click to collapse
Which version of oos u were in? If u were in oos 3.1.x u should flash marshmellow stock recovery... Thn u ll nvr never get dtb not found issue

Im having the same issue, but when i try to flash the recovery, it just says "cannot load (filename)". How do i fix this?
Edit: Fixed!

Related

[Q] HTC Amaze not booting

After shutting down and turning on my phone again this morning, it will not boot up and instead freezes on the white splash screen with the green HTC logo. I have tried waiting it out, clearing the caches, flashing the kernel, and just tried a hard reset, all to no avail.
Also, if I plug my phone into the charger, the orange light comes on. However, it remains on when I unplug it from the wall and the only way to get the light off is to take out the battery.
I was using a custom ROM, the Amazing QuikSense 2.1.2, for the past 4 months without any problems. I haven't installed any new applications in awhile. I don't know what caused this. What can I do to get my phone working again?
Can you get into recovery? Try taking battery out, put back in, hold volume down and power at same time and see if you can get into recovery. If so, reflash the rom.
yes, i can get into recovery and to ClockworkMod
i have already tried flashing the ROM again but it is still freezing when booting
eudemonics said:
i have already tried flashing the ROM again but it is still freezing when booting
Click to expand...
Click to collapse
How are you flashing the kernel? Fastboot or ADB? ADB may not work on a soft brick... Maybe try fastboot?
OR
Did your battery die and that's what triggered this? If your battery is dead and you are on a CWM that doesn't have charging while off, you could be screwed until u get a fresh battery. Does the phone turn off after hanging on splash screen?
Sent from my HTC_Amaze_4G using Tapatalk 2 Beta-5
i tried flashing the kernel using this utility, in ClockworkMod:
http://forum.xda-developers.com/showthread.php?t=1552889
eudemonics said:
i tried flashing the kernel using this utility, in ClockworkMod:
http://forum.xda-developers.com/showthread.php?t=1552889
Click to expand...
Click to collapse
Theres ur problem, u need to use ekf
Idk if there is still a thread with ekf, but u can just download fauxs kernel from his thread, extract the zip on your computer, put your fone in fastboot and connect the phone to the computer via usb. Open the folder u extracted the zip to and open the file that says flash.bat and it will do the rest
Sent from my NRGized Amaze...
via xda premium
i have EKF but i am using a Mac now and can't get into my PC. i used the utility because i was unable to figure out how to flash it in terminal
i have tried flashing the kernel through ADB and flashing the ROM and it is still freezing on the HTC startup screen.. i don't know what to do next.. please help
it says:
fastboot flash boot Kernel-Here/boot.img
sending 'boot' <2876 KB>... FAILED <status malformed <1 bytes>>
the boot.img file is fine - why is it failing?
im also having this problem, my phone keeps freezing at the startup screen when the htc logo pops up. i dont know much about this kind of stuff so i would really appreciated if anyone could guide me to what to do
the way that my phone froze like that was that i tried to flash a kernel for the Energy rom, i did installed the rom itself
http://forum.xda-developers.com/showthread.php?t=1362759 this is the rom that i wanted to use
and i flashed the kernel that was provided in the 4th post, i downloaded that file, extracted and ran the .bat file and thats how it happened
i would appreciate if anyone could help me with this
Urgent help me
I am using htc amaze wind
i used hasoon `s tool , i just clicked on flash your kernels and my phone is not started up. It shows me only htc screen ...
Please help me out
---------- Post added 1st November 2012 at 12:00 AM ---------- Previous post was 31st October 2012 at 11:45 PM ----------
i am new in this .. my phone is not starting up. what should i do ? when i went to team recoveries project and try to restore it shows like no os installed ..
please help me
suratimehul said:
I am using htc amaze wind
i used hasoon `s tool , i just clicked on flash your kernels and my phone is not started up. It shows me only htc screen ...
Please help me out
---------- Post added 1st November 2012 at 12:00 AM ---------- Previous post was 31st October 2012 at 11:45 PM ----------
i am new in this .. my phone is not starting up. what should i do ? when i went to team recoveries project and try to restore it shows like no os installed ..
please help me
Click to expand...
Click to collapse
I'm not sure if I can help you but other could and will if you provided more specific infos about your phone
1. What kernel did you tried to flash, using hansoon's toolkit?
2. What is your phone status before trying to flashed kernel? I.e are you rooted? Unlocked bootloader? S-Off? Running custom Rom or stock, ect and ect ...
3. When using toolkit to flash kernel, did you put ANY kernel in the "Kernels" folder at all???
antiquezip said:
I'm not sure if I can help you but other could and will if you provided more specific infos about your phone
1. What kernel did you tried to flash, using hansoon's toolkit?
2. What is your phone status before trying to flashed kernel? I.e are you rooted? Unlocked bootloader? S-Off? Running custom Rom or stock, ect and ect ...
3. When using toolkit to flash kernel, did you put ANY kernel in the "Kernels" folder at all???
Click to expand...
Click to collapse
Amaze_All-In-One_Kit_V4.0 . I UNLOCKED BOOT LOADER THAN I FLASH RECOVERY TWRP 2.3.1.0 AND I FLASHED KERNEL WITH FLASH KERNEL .. THATS ALL THAN MY PHONE DOSENT START ..
AFTER THAT I REMOVED MY BATTERY AND TRY TO PUT IN BOOTLOADER AND RUN RECOVERY , TRY TO RECOVER BUT IS SHOWS LIKE NO OS INSTALLED ??????
actually i wipe all data in recovery mode i used TWRP AND WIPE ALL SYSTEM DATA AND PHONE STORAGE .. PLEASE SOMEBODY HELP ME
---------- Post added at 02:01 PM ---------- Previous post was at 01:28 PM ----------
This will flash TWRP.
If it says "Waiting For Device"
Go to Settings -> Develop Option
and enable USB Debugging.
Press a button to continue.
C:\Users\Mehul\Desktop\Amaze_All-In-One_Kit_V4.0\data>pause
Press any key to continue . . .
C:\Users\Mehul\Desktop\Amaze_All-In-One_Kit_V4.0\data>adb kill-server
* server not running *
C:\Users\Mehul\Desktop\Amaze_All-In-One_Kit_V4.0\data>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Mehul\Desktop\Amaze_All-In-One_Kit_V4.0\data>fastboot flash recovery Re
coveries/TWRP.img
< waiting for device >
sending 'recovery' (6246 KB)... OKAY [ 1.540s]
writing 'recovery'... OKAY [ 4.535s]
finished. total time: 6.075s
C:\Users\Mehul\Desktop\Amaze_All-In-One_Kit_V4.0\data>fastboot reboot
rebooting...
finished. total time: 1.934s
C:\Users\Mehul\Desktop\Amaze_All-In-One_Kit_V4.0\data>pause
Press any key to continue . . .
You wiped all of your data and system, so it's basically means that you have nothing on your phone, no OS, nada, that's why the phone would not boot up.
I suggest you to read more before doing anything to your phone next time :fingers-crossed:
At least you still have recovery on your phone. I'm not sure if TWRP would allow your phone to be charge while off, if it's not, then you better stop doing any further and try to look around to see if you have a wall-charger to charge your battery. Make sure it's full before proceed any further.
These next steps would be
1. Read this thread
2, Flashing 4EXT recovery would be your best bet since it allow your phone to be charged while off - this will be a life saver.
3. Flash an RUU to get back to stock. Note: You will need to re-lock your bootloader in order to do this
Good luck
antiquezip said:
You wiped all of your data and system, so it's basically means that you have nothing on your phone, no OS, nada, that's why the phone would not boot up.
I suggest you to read more before doing anything to your phone next time :fingers-crossed:
At least you still have recovery on your phone. I'm not sure if TWRP would allow your phone to be charge while off, if it's not, then you better stop doing any further and try to look around to see if you have a wall-charger to charge your battery. Make sure it's full before proceed any further.
These next steps would be
1. Read this thread
2, Flashing 4EXT recovery would be your best bet since it allow your phone to be charged while off - this will be a life saver.
3. Flash an RUU to get back to stock. Note: You will need to re-lock your bootloader in order to do this
Good luck
Click to expand...
Click to collapse
thank you very much , but what should i do first i am afraid to do... please suggest me first step and be easy on me !!
You still be able to boot into your recovery, right? I don't use TWRP so I'm not sure but you will need to know how much juice you still have before going further. In 4EXT recovery, it tell you that information inside recovery though ...
Next, I would flash 4EXT recovery to make sure you can charge your phone while it's off ... using Hansoon's toolkit. Don't try to flash kernel again for you don't needed it as yet
The rest is very much already told. You will try to go back to stock by reading the link that I've provided.
PS: DON'T be affraid. DONT Panic. Just read through the Amaze Bible to gain more knowledge and confident. You'll be okay. Just take your time to read. It's not that hard as you though while in panic mode
antiquezip said:
You still be able to boot into your recovery, right? I don't use TWRP so I'm not sure but you will need to know how much juice you still have before going further. In 4EXT recovery, it tell you that information inside recovery though ...
Next, I would flash 4EXT recovery to make sure you can charge your phone while it's off ... using Hansoon's toolkit. Don't try to flash kernel again for you don't needed it as yet
The rest is very much already told. You will try to go back to stock by reading the link that I've provided.
PS: DON'T be affraid. DONT Panic. Just read through the Amaze Bible to gain more knowledge and confident. You'll be okay. Just take your time to read. It's not that hard as you though while in panic mode
Click to expand...
Click to collapse
thank you very much . yes i am still able to boot in recovery- (4EXT TOUCH ) let me go through the reading but i don't have external sd card ..IS IT FINE ??
---------- Post added at 10:05 PM ---------- Previous post was at 09:54 PM ----------
Now to the steps.
1. Download the stock ruu from here
2. Lock your bootloader by using the fastboot command "fastboot oem lock"
3. Reboot to system
4. Flash the stock RUU you downloaded by placing it in the root of your external sd card and renaming it PH85IMG.zip and rebooting to bootloader.
5. Once you have the stock rom reinstalled, set the security lock by using fastboot command " fastboot oem writesecureflag 3"
6. Profit?
I DOWNLOADED STOCK RUU ,AND I LOCKED BOOTLOADER . I REBOOT THE SYSTEM AND IT RELOCKED . NOW MOVING TO (4) STEP I DIDNT GET WHAT TO DO ???
suratimehul said:
thank you very much . yes i am still able to boot in recovery- (4EXT TOUCH ) let me go through the reading but i don't have external sd card ..IS IT FINE ??
---------- Post added at 10:05 PM ---------- Previous post was at 09:54 PM ----------
Now to the steps.
1. Download the stock ruu from here
2. Lock your bootloader by using the fastboot command "fastboot oem lock"
3. Reboot to system
4. Flash the stock RUU you downloaded by placing it in the root of your external sd card and renaming it PH85IMG.zip and rebooting to bootloader.
5. Once you have the stock rom reinstalled, set the security lock by using fastboot command " fastboot oem writesecureflag 3"
6. Profit?
I DOWNLOADED STOCK RUU ,AND I LOCKED BOOTLOADER . I REBOOT THE SYSTEM AND IT RELOCKED . NOW MOVING TO (4) STEP I DIDNT GET WHAT TO DO ???
Click to expand...
Click to collapse
Writesecurityflag??? Its been a while for me but that doesnt sound right. If s=off u want... u need the wire trick... After step 4 (which is accurate btw) u need to put the recovery.img of your choice (4ext highly recommended) in the same folder as your fastboot.exe program on pc. I recommend renaming it "recovery.img" and then you type "fastboot flash recovery recovery.img" to flash ur custom recovery of choice. From there, reboot into recovery and flash superuser.zip. then u r rooted stock
Sent from my Wicked Galaxy S III

[HTC PHONES][UNBRICK] How to unbrick all htc phones

Ok, so i have seen many people on xda saying there htc phone is bricked blah blah...
this is to explain what brick you have, what is causing it, if it can be fixed, how it can be fixed, and what to do if it is completely bricked!
BEFORE WE GO ANY FURTHER, I WOULD LIKE YOU AFTER YOU FINISH READING THIS FIX TO STOP AND CONSIDER HITTING THE THANKS BUTTON AS IT WILL HELP ME AS MUCH AS THIS GUIDE POSSIBLY HELPED YOU
also i am open to ANY questions, help or anything needed by the community! so if you need something, be sure to comment!
first i will explain the definitions of a brick-
HARD BRICK
a hard brick (also knows as a hardware brick) is when your phone doesnt turn on and when adb and fastboot dont pick up your device as you have damaged hardware on your device
Click to expand...
Click to collapse
SOFT BRICK
a soft brick (also knows as a software brick) is when your device turns on but gets stuck at bootloader, recovery, htc logo, bootlogo etc...
Click to expand...
Click to collapse
OPTIONS FOR A HARD BRICK-
there are a few options here.
1ST OPTION- riffbox jtag repair, this is a repair by manually pumping firmware into your phone with a riffbox connected to a jtag connected to your phones motherboard
method for this is a difficult, yet money saving process, but may not work all the time.
HOW TO RIFF
1. buy a riffbox and the required jtag for your device
2. install the firmware that comes with the riffbox
3. extract the motherboard from your device
4. connect in the following way (<computer><riff cable><riffbox><jtag cable><jtag><motherboard>)
5. run the software that came with the riffbox
6 follow prompted instructions by riff firmware
7.DONE!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
2ND OPTION-
1. buy a new motherboard
2. replace the motherboard
HOW TO REPLACE MOTHERBOARD
1. open your device and extract the motherboard(chances are you can find it on youtube)
2. replace it with the new motherboard
3. DONE
Click to expand...
Click to collapse
Click to expand...
Click to collapse
3RD OPTION(ONLY IF OPTION 1 AND 2 DO NOT WORK)-
buy a new phone
or buy a motherboard, and a new lcd screen as you have fore then likely overclocked your processor, and over volted your lcd screen and blown it.
Click to expand...
Click to collapse
OPTIONS FOR A SOFT BRICK
a softbrick is 99% repairable with a htc phone, as htc has a more then simple way of operating
it needs the following to run
1st you need a hboot
2nd you need a system image, data image and boot image. ( i say all three of these because your phone wont boot unless you have all three)
3rd applications
so now we identify your problem!
if your phone turns on and goes straight to recovery or bootloader, even after you have tried rebooting into system this is what you do!
the problem is cause by not having a system and data image.
1. download a rom for your device
2. put the rom on your sd card(if you dont have an sd boot into recovery and push the file to your phone using my adb guide HERE
3. put your sd card in your phone and reboot into recovery
4. flash the rom.
5.DONE
Click to expand...
Click to collapse
if your phone turns on and is stuck at the htc logo then this is a problem with the boot.img, heres what to do.
1. download the rom you have and open the .zip file on your computer, then extract the boot.img from the file and put it somewhere on your computer
2. connect phone to computer
3. read HERE to learn how to flash the boot.img
4.DONE
Click to expand...
Click to collapse
if your phone turns on and goes straight to bootloader and you cant get into recovery then this is caused by not having no image files flashed, and heres how to fix it.
1. boot into bootloader
2. select fastboot in the bootoader menu
3. connect phone to your computer
4. download a recovery for your phone and read HERE how to flash it
5. boot into recovery
6. download a rom for your device
7. put the rom on your sd card(if you dont have an sd boot into recovery and push the file to your phone using my adb guide HERE
8. put your sd card in your phone and reboot into recovery
9. flash the rom.
10. DONE
Click to expand...
Click to collapse
if none of those work then you might want to consider flashing an RUU file (FIXES ALMOST ALL ERRORS)
1. download the RUU for your device and CID
2. flash it
3. DONE
Click to expand...
Click to collapse
if not even that works, consider it a hard brick
HOPE THIS HELPED! AND REMEMBER TO HIT THANKS!
hey bro nice guide. My friend's htc incredible 2 is softbricked he can boot into fastboot but cannot boot into recovery (tried flashing new one and also using fastboot boot recovery.img ) his bootloader is unlocked but he is still s-on can he flash a rom via fastboot?? Also an ruu is out of question since there is none for the latest version
ArslanQureshi said:
hey bro nice guide. My friend's htc incredible 2 is softbricked he can boot into fastboot but cannot boot into recovery (tried flashing new one and also using fastboot boot recovery.img ) his bootloader is unlocked but he is still s-on can he flash a rom via fastboot?? Also an ruu is out of question since there is none for the latest version
Click to expand...
Click to collapse
i believe the problem is you!
try flashing a recovery image to the recovery partition by
fastboot flash recovery /PATH/TO/FILE/recovery.image
if you need help pm me, i love helping the community and im happy to help out! also 99% of the time i fix the problem i also have a support thread!
ricky310711 said:
i believe the problem is you!
try flashing a recovery image to the recovery partition by
fastboot flash recovery /PATH/TO/FILE/recovery.image
if you need help pm me, i love helping the community and im happy to help out! also 99% of the time i fix the problem i also have a support thread!
Click to expand...
Click to collapse
already flashed recovery but it still wont boot so I told him to force boot it using fastboot boot recovery.img but it still didn't work and I sent you a pm
ArslanQureshi said:
already flashed recovery but it still wont boot so I told him to force boot it using fastboot boot recovery.img but it still didn't work and I sent you a pm
Click to expand...
Click to collapse
also its fastboot reboot-recovery or fastboot reboot recovery
Soft/Hard brick combined
Hi, I have an HTC Thunderbolt that is not being detected by ADB or Fastboot but it starts up and is in a bootloop. Unfortunately I have not backed it up and I have stock recovery. I do have an SD card so if there is a way that I can probably put a fix on it and apply it through the recovery I would. Awesome guide BTW.
iLeoable said:
Hi, I have an HTC Thunderbolt that is not being detected by ADB or Fastboot but it starts up and is in a bootloop. Unfortunately I have not backed it up and I have stock recovery. I do have an SD card so if there is a way that I can probably put a fix on it and apply it through the recovery I would. Awesome guide BTW.
Click to expand...
Click to collapse
is the bootloader unlocked? also does it boot into bootloader?
PM me!
First of all Thanks IN Advance!!
I installed this rom [http://forum.xda-developers.com/show...php?t=2519414] and was working fine with no problems then i by mistakenly installed a wrong rom which was for on screen nav bar i installed it when i booted it up it got stuck in the htc white screen so i removed the battery and booted it again still no luck, so i went too recovery and wiped cache and dalvik cache but still no luck then i got panicked and by mistakenly wiped my whole sd card "Yikes!!" now when i go in recovery it got stuck on the loading screen so i installed another recovery which is cwm through fastboot and was now able to gain access to it so then i went on and tried to install a rom, after it was installed i booted up the boot, then the boot animation of the vivokat(which i installed) showed up and it was spinning but its was not smooth it was lagging so i waited and waited nothing happened then i tried to install it through fast boot but still gives me an error . please help!!!!
I AM:
***UNLOCKED***
VIVO PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.18.00_M
---------- Post added at 02:43 PM ---------- Previous post was at 02:37 PM ----------
bobsteranian said:
First of all Thanks IN Advance!!
I installed this rom [http://forum.xda-developers.com/show...php?t=2519414] and was working fine with no problems then i by mistakenly installed a wrong rom which was for on screen nav bar i installed it when i booted it up it got stuck in the htc white screen so i removed the battery and booted it again still no luck, so i went too recovery and wiped cache and dalvik cache but still no luck then i got panicked and by mistakenly wiped my whole sd card "Yikes!!" now when i go in recovery it got stuck on the loading screen so i installed another recovery which is cwm through fastboot and was now able to gain access to it so then i went on and tried to install a rom, after it was installed i booted up the boot, then the boot animation of the vivokat(which i installed) showed up and it was spinning but its was not smooth it was lagging so i waited and waited nothing happened then i tried to install it through fast boot but still gives me an error . please help!!!!
I AM:
***UNLOCKED***
VIVO PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.18.00_M
Click to expand...
Click to collapse
but bow after giving the cellphone to the shop keeper for fixing it(but he failed)now the cellphone does not even boot in recovery and it also gets stuck on HTC splash screen
please help me i don't understand what to do
complete details of my mobile in following link
http://forum.xda-developers.com/android/help/htc-826-os-please-help-t3187369
Hi!
My phone keeps staying on the startup animation.
I actually had a recovery installed, and in the memory there's a rom's zip ready to get installed... but I can't get into the bootloader.
Even if I press volume down+power button it goes on startup animation until the battery is totally drained.
I could even flash the RUU, but I actually can't select the fastboot mode...
Any suggestion?
Thanks!
hello, Have rant into a problem. my htc m8 has a soft brick and it is frozen loading. I tryied to connect the phone to a computer but its not recognised. I dont know how to recover it. I have bricked it by flashing a wrong unistall of xposed framework I think. I please help me to find a solution
rozetnikas said:
hello, Have rant into a problem. my htc m8 has a soft brick and it is frozen loading. I tryied to connect the phone to a computer but its not recognised. I dont know how to recover it. I have bricked it by flashing a wrong unistall of xposed framework I think. I please help me to find a solution
Click to expand...
Click to collapse
install the stock RUU
Hello I have a problem with my HTC sensation XE - phone does't boot but when I plug charger to the phone HTC logo(with vibration) appears every 15 minutes and lasts for a minute or so.
When phone is charging red diode is flashing but I can't boot the phone. Is it Hardware bricked? what to do?
witkacz said:
Hello I have a problem with my HTC sensation XE - phone does't boot but when I plug charger to the phone HTC logo(with vibration) appears every 15 minutes and lasts for a minute or so.
When phone is charging red diode is flashing but I can't boot the phone. Is it Hardware bricked? what to do?
Click to expand...
Click to collapse
try booting into bootloader
Ricky Divjakovski said:
try booting into bootloader
Click to expand...
Click to collapse
I have tired - doesn't work
witkacz said:
I have tired - doesn't work
Click to expand...
Click to collapse
are you pressing the buttons properly? and are all buttons functioning?
if so its more then likely hard bricked
Thanks
Thanks, is this transferable onto any android (Samsungs?)
[email protected] said:
Thanks, is this transferable onto any android (Samsungs?)
Click to expand...
Click to collapse
Similiar method for samsungs, although you use ODIN, there is no fastboot
hello sir i have HTC D728x flash with RUU files, my PC get hang up, so force me to reboot the PC while in the midst of flashing...
after reboot take out phone power off.. then when i turn on the phone it did not give me any response (so means i'm in a HARD BRICK situation) the PC won't detect my PHONE..
is there any ways to recover my phone? if there is can you give me the link or procedure thanks in advance....
and i believe my HTC D728x is MTK chipset...
Soft-bricked Phone
Hi
i am new to all these stuff, as u said earlier my phone is stuck on the htc logo so it needs to flash boot.img
my phone is htc m8 eye where can i find the stock rom to proceed from
the question might be silly but thanks anyway

Bricked Nexus 9

Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
nexus 9
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
MoooN said:
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
Click to expand...
Click to collapse
I don't have a Linux system and looking through thread seems too advance for me. I can't relate it to the N9. However, there seems to be something wrong partition, because I can't mount storage.
matt4787 said:
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
Click to expand...
Click to collapse
I can flash custom recovery, but I can't push files or adb sideload, therefore I can't do anything in recovery anyway.
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Does the Google Logo flash for a second or so before it goes to bootloader?
nexus 9
Try to get into bootloader by holding power and volume down.
MoooN said:
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
Click to expand...
Click to collapse
I will look in to it, thank you.
jd1639 said:
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I already tried one version of the image, which didn't work, will try to flash the others.
scrosler said:
Does the Google Logo flash for a second or so before it goes to bootloader?
Click to expand...
Click to collapse
restart - sometimes yes and sometimes no, if plug into computer - no, if not plugged - yes,
matt4787 said:
Try to get into bootloader by holding power and volume down.
Click to expand...
Click to collapse
you mean power + volume up, but yes, no problem getting there, also adb is working
thanks for all your help, I will try different factory image and flashing from OTG
The problem is your kernel is not loading or mismatched to the operating system. I have experienced this a lot on HTC devices when I screw something up... I mean "experiment"
You need to flash the boot system and vendor image from the latest factory ROM.
You need to do it manually...
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot to recovery and wipe data. Not factory rest but actually wipe all of /data partition.
That should get you back. If not post back results.
If you are not familiar with fastboot then state so and I will help you.
Yes! I got it booting again, thank you everyone for helping. Apparently, the problem was, I think, wiping manually, that is, system, cache, recovery, boot, user data, and vendor didn't erase everything. What did the trick was [fastboot -w], I did this instead of erasing one by one. Thank you so much guys!
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
bynarie said:
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
Click to expand...
Click to collapse
Um, he's got it fixed.
Sent from my Nexus 5 using XDA Free mobile app
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Thanks for paying it forward.
I have a similar problem my nexus 9 wont turn on and would freeze in the optimizing apps screen after going past the nexus logo but i can get to the fastboot and recovery. But i cannot flash the factory image because my bootloader is locked and i didn't enable developer options prior to the problem. I'm thinking about sideloading the latest ota would that help me ? And is there anyway to unlock bootloader if i can't boot the device?
---------- Post added at 10:10 PM ---------- Previous post was at 10:07 PM ----------
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Can you please explain to me what fastboot w- command means ?
It erases userdata and cache. Often needed if you run into bootloops. But it does wipe your data so backup off your device first.
Bricked N9
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
emi.guego said:
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
Click to expand...
Click to collapse
I had the same problem... I had to manually flash each image through fastboot starting with the recovery img
Sent from my HTC One M9 using XDA Free mobile app
But how can I do it if I can't enable USB debugging?
Enviado desde mi Moto MAXX mediante Tapatalk

One Plus X - cannot enter in recovery mode [help]

hi friends,
i was trying to root my phone before but my was briked.
then i flashed boot.img and recovery.img and then phone started.
but now i am trying to update new OS released. its not updating.
i tried to enter in recovery mode but it only shows icon.
i think its problem with recovery.img ?
can anyone provide link for orignal recovery.img for oneplus x ??
What root method did you use?
CafeKampuchia said:
What root method did you use?
Click to expand...
Click to collapse
i just following this link on forum and steps
http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
Good, at least your bootloader is unlocked. Can you get it into fastboot mode?
CafeKampuchia said:
Good, at least your bootloader is unlocked. Can you get it into fastboot mode?
Click to expand...
Click to collapse
yes i can go in fastboot mode. but my phone is not rooted.
what shall i do ?
Rooting has nothing to do with flashing. Put it in bootloader mode and flash a recovery. Then try doing a factory reset. If that doesn't work, re-flash the ROM.
CafeKampuchia said:
Rooting has nothing to do with flashing. Put it in bootloader mode and flash a recovery. Then try doing a factory reset. If that doesn't work, re-flash the ROM.
Click to expand...
Click to collapse
Put it in bootloader mode and flash a recovery ??
i will enter in bootloader mode and then how to flash recovery? can you explain little? Thanks
It's all in step 5 of the guide you used to root the device on the first place. No need to re-write it here.
CafeKampuchia said:
It's all in the guide you used to root the device on the first place. No need to re-write it here.
Click to expand...
Click to collapse
actually i didn't understand which recovery to flash? twrp or stock ??
No offence, but you need to do more research and know how this stuff works before flashing things.
I can't answer your question because I don't know what you are trying to flash. Ask in the thread where you found it. If it's a custom ROM, TWRP Will work. If stock, stock recovery is best.
I'm signing off for a while. Good luck.
CafeKampuchia said:
No offence, but you need to do more research and know how this stuff works before flashing things.
I can't answer your question because I don't know what you are trying to flash. Ask in the thread where you found it. If it's a custom ROM, TWRP Will work. If stock, stock recovery is best.
I'm signing off for a while. Good luck.
Click to expand...
Click to collapse
i have flashed stock_recovery.img and now i can go to recovery mode.
but when i am trying to update to new OS, its failed. [ i tried from Settings -> check updates -> it download and go to recovery mode and says: installation failed.] also [ i directly go to recovery mode and maually install from Local and choose OnePlusOxygen_14_OTA_003-004_patch_201511031712.zip and still it says: failed to update.
help???
rahulcool said:
i have flashed stock_recovery.img and now i can go to recovery mode.
but when i am trying to update to new OS, its failed. [ i tried from Settings -> check updates -> it download and go to recovery mode and says: installation failed.] also [ i directly go to recovery mode and maually install from Local and choose OnePlusOxygen_14_OTA_003-004_patch_201511031712.zip and still it says: failed to update.
help???
Click to expand...
Click to collapse
Right, because the device is rooted. The first section of the routing guide tells you the problem (modified system position) and there are threads here to solve it.
CafeKampuchia said:
Right, because the device is rooted. The first section of the routing guide tells you the problem (modified system position) and there are threads here to solve it.
Click to expand...
Click to collapse
yes it was problem due to some incorrect rooting.
i flashed stock recovery.img and then i downloaded full rom and flashed it with help of memory card. and now the phone is working fine.
Thanks for all ur helps and post.
rahulcool said:
yes it was problem due to some incorrect rooting.
i flashed stock recovery.img and then i downloaded full rom and flashed it with help of memory card. and now the phone is working fine.
Thanks for all ur helps and post.
Click to expand...
Click to collapse
No prob, glad I could help. What rooting method did you originally use?
CafeKampuchia said:
No prob, glad I could help. What rooting method did you originally use?
Click to expand...
Click to collapse
http://www.android.gs/install-twrp-recovery-root-oneplus-x/
thats the method in above link , its same posted in this forum too.
i can't root my mobile, its showing error.
i will make new thread and post screenshot there,please check.
I bricked my one x its white and it wont boot trying to flash stock recovery but keeps complaing that device not unlocked i try fastboot oem unlock does it but phone wont boot just stuck at a oneplus sigh help would be appreciated to get my phone booting again.
jutley said:
I bricked my one x its white and it wont boot trying to flash stock recovery but keeps complaing that device not unlocked i try fastboot oem unlock does it but phone wont boot just stuck at a oneplus sigh help would be appreciated to get my phone booting again.
Click to expand...
Click to collapse
well that's why you need to unlock bootloader first before attempting to root your phone. and know what you are doing (flashing). With all that said if you can still boot to Recovery then flash this Full ROM (save this on an SD card) that should stop the bootloop and have a working ROM
https://www.androidfilehost.com/?fid=24269982087013219
If you can't boot to recovery or even bootloader this is your guide
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
jutley said:
I bricked my one x its white and it wont boot trying to flash stock recovery but keeps complaing that device not unlocked i try fastboot oem unlock does it but phone wont boot just stuck at a oneplus sigh help would be appreciated to get my phone booting again.
Click to expand...
Click to collapse
maybe try this?
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
jutley said:
I bricked my one x its white and it wont boot trying to flash stock recovery but keeps complaing that device not unlocked i try fastboot oem unlock does it but phone wont boot just stuck at a oneplus sigh help would be appreciated to get my phone booting again.
Click to expand...
Click to collapse
if you can still access bootloader then simply just boot TWRP from it, first download this full rom and save it on your SD card
https://www.androidfilehost.com/?fid=24269982087013219
then go to bootloader if you can still access it and boot TWRP
fastboot boot [whatever your twrp name is].img
you can download modified twrp here
http://forum.xda-developers.com/devdb/project/dl/?id=16464
then once inside TWRP just install the FULL ROM that was downloaded and saved in the SD card/
My phone boots into fastboot ok but there is no recovery wont boot. I try to flash recovery and it says it cant because not unlocked tried unlocking bootloader says its sucesfull but phone wont get bast boot logo.

Umx u673c root?

The phone has unlockable bootloader and I only have low mobile data and was wondering if there's a way to rip the stock recovery to port twrp over.
When I get wifi tomorrow, I'll try using PC king root while the phone is in fastboot mode.
Kingoroot will get to 100 but fail, kingroot pc version would just give me Chinese letters and do nothing.
Can anyone list anyother root exploits I might I can try on this phone? I tried the Android version of kingroot , but that just gives me the request device and I can't bypass it.
Root u673c
... has anyone been able to root the U673C version 6.0.1, if so, guide me through it, thanks!
we need to somehow extract the stock recovery.img to port twrp over.
Rooted boot image for u673c
I have finally rooted this phone. Here is the rooted boot.img uploaded to MediaFire.
https://www.mediafire.com/download/r6hs4x6mju18j01
Its rooted with Magisk 17.1
Unlock bootloader rename file to boot.img and flash with fastboot.
tdawgg777 said:
I have finally rooted this phone. Here is the rooted boot.img uploaded to MediaFire.
https://www.mediafire.com/download/r6hs4x6mju18j01
Its rooted with Magisk 17.1
Unlock bootloader rename file to boot.img and flash with fastboot.
Click to expand...
Click to collapse
Awesome! SO is it possible to get more detailed instructions. It's been a few years since i've dont this stuff. My old brain's memory isn't so good.
DB225 said:
Awesome! SO is it possible to get more detailed instructions. It's been a few years since i've dont this stuff. My old brain's memory isn't so good.
Click to expand...
Click to collapse
Some instructions would be nice, Does not work I can get boot.img to install but it will only boot into stock recovery
In developer options click allow OEM unlocking then boot to fastboot mode and use fastboot to unlock bootloader and flash the rooted kernel.
Rename file to boot.img
Unlock bootloader: fastboot oem unlock
Flash kernel: fastboot flash boot boot.img
twrp is not included...
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
Here is the twrp that I used and so far seems to work fine.
https://forum.xda-developers.com/showpost.php?p=78089109&postcount=283
Thank Rortiz2 for building it.
---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------
If you are having trouble booting system after installing twrp try wiping data and cache.
The no verity zip should not be needed since kernel was patched with magisk... but if still Having issues booting system try flashing the no verity zip... you can search for it here on xda
Thank you !
I just wanted to thank you, I am disabled and dont have alot of income, This phone is my lefeline, I now have it rooted running Magisk 18.0 and TWRP is installed and seems to be working fine, However I would like to ask this. There is an pain in the ass app that seems to be part of the last firmware update this phone had, ( io.appservice.module ) ( Found in data/appi.service.module-1/base.apk
This Kunt sorry for the language, If you uninstall it it is back with every reboot ?
I can disable it to solve the problem but I would like it gone, Any thoughts ?
does anyone have twrp backup or copy firmware.I wipe internel by accident cant flash u673c no os,thanks sean
---------- Post added at 04:40 AM ---------- Previous post was at 04:32 AM ----------
does anyone have backup or copy firmware u673c cause screwed up wiped internel memory,sean
derwoodbones said:
I just wanted to thank you, I am disabled and dont have alot of income, This phone is my lefeline, I now have it rooted running Magisk 18.0 and TWRP is installed and seems to be working fine, However I would like to ask this. There is an pain in the ass app that seems to be part of the last firmware update this phone had, ( io.appservice.module ) ( Found in data/appi.service.module-1/base.apk
This Kunt sorry for the language, If you uninstall it it is back with every reboot ?
I can disable it to solve the problem but I would like it gone, Any thoughts ?
Click to expand...
Click to collapse
I would just disable the app... just in case there is an update for the phone in future... if you remove the app the update will fail but if its disabled you can just enable it take update and then disable it again... also disable the stock gallery and install a third party one from the playstore... the stock gallery app will through all sorts of ads at you full screen ads as well.
I used titainium backup to disable all apps I didn't want... bit you can use what ever app you want. You can disable most apps in the apps info but not all apps.
I just use the phone as a backup and don't know where it is right now but when I come accross it I'll post all the apps I disabled here.
I healthfully thank you
---------- Post added at 04:00 AM ---------- Previous post was at 03:59 AM ----------
I fully thank you
Thanks for the info!
In your post, you wrote, "then boot to fastboot mode".
Kindly explain how that is done on this phone. After spending hours, I can't figure it out.
Thanks again!
tdawgg777 said:
In developer options click allow OEM unlocking then boot to fastboot mode and use fastboot to unlock bootloader and flash the rooted kernel.
Rename file to boot.img
Unlock bootloader: fastboot oem unlock
Flash kernel: fastboot flash boot boot.img
twrp is not included...
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
Here is the twrp that I used and so far seems to work fine.
https://forum.xda-developers.com/showpost.php?p=78089109&postcount=283
Thank Rortiz2 for building it.
---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------
If you are having trouble booting system after installing twrp try wiping data and cache.
The no verity zip should not be needed since kernel was patched with magisk... but if still Having issues booting system try flashing the no verity zip... you can search for it here on xda
Click to expand...
Click to collapse
smuskat said:
Thanks for the info!
In your post, you wrote, "then boot to fastboot mode".
Kindly explain how that is done on this phone. After spending hours, I can't figure it out.
Thanks again!
Click to expand...
Click to collapse
I'm sorry I can remember the button combo... From phone off press and hold vol down and power release power and keep holding vol down... I think fast boot mode is an all black screen or it just has umx logo, can't remember exactly... when you have a fast hooky cmd window open type fastboot devices to see if your phone is connected... if it is not try holding vol up instead of vol down when turning phone on... if vol up don't work try holding both vol buttons. Before this can be done make sure usb debugging is enabled in developer options and authorize your pc when prompted... alternately after you have adb authorized you could use adb cmd "adb reboot bootloader"
If you ned help with adb/fastboot do a quick google search you will find plenty of info and instructions
I appreciate your reply.
But I need some more assistance, please:
I've rooted many devices, flashed custom ROM's, Custom recoveries, etc, but I'm completely stuck now with this phone.
I tried "Power and Vol Down"....nothing.
I tried "Power and Vol Up"...and for a split second I see the Android robot on its back...but after that split second, I'm in the stock recovery menu.
One of the stock recovery menu choices is to reboot into Bootloader. When I try that, the phone reboots; but to the best of my knowledge, does not get into Bootloader mode.
I have installed ADB on my PC. When I type "ADB devices", I see my phone listed. But when I type "adb reboot bootloader", it reboots, but not into Bootloader.
I have USB debugging enabled, I have authorized my PC, and in Developer options, I have enabled the "Unlock Bootloader" option.
My Googling results have not yielded useful info.
I'm stuck.....
I hope that someone with experience with this particular device can please tell me what I'm doing wrong.
Thank you!
tdawgg777 said:
I'm sorry I can remember the button combo... From phone off press and hold vol down and power release power and keep holding vol down... I think fast boot mode is an all black screen or it just has umx logo, can't remember exactly... when you have a fast hooky cmd window open type fastboot devices to see if your phone is connected... if it is not try holding vol up instead of vol down when turning phone on... if vol up don't work try holding both vol buttons. Before this can be done make sure usb debugging is enabled in developer options and authorize your pc when prompted... alternately after you have adb authorized you could use adb cmd "adb reboot bootloader"
If you ned help with adb/fastboot do a quick google search you will find plenty of info and instructions
Click to expand...
Click to collapse
hope it helps
for me command "Fastboot Continue" would make it continue to load, it did take a while....
if it continues the loop then something went wrong. as i got the infinite bootscreen 1st try.
i just reinstalled the boot image a 2nd time and it worked here's the CRC-32 Hash "a483081b"
Not sure what you mean. You wrote " command "Fastboot Continue" would make it continue to load" Do you mean from the PC command prompt? Do you mean from the phone's recovery menu?
You also wrote " i got the infinite bootscreen 1st try"
I don't know what you mean by "infinite bootscreen"......
Sorry I'm having trouble....ty!
Liberator Elite said:
for me command "Fastboot Continue" would make it continue to load, it did take a while....
if it continues the loop then something went wrong. as i got the infinite bootscreen 1st try.
i just reinstalled the boot image a 2nd time and it worked here's the CRC-32 Hash "a483081b"
Click to expand...
Click to collapse
More Info
smuskat said:
Not sure what you mean. You wrote " command "Fastboot Continue" would make it continue to load" Do you mean from the PC command prompt? Do you mean from the phone's recovery menu?
You also wrote " i got the infinite bootscreen 1st try"
I don't know what you mean by "infinite bootscreen"......
Sorry I'm having trouble....ty!
Click to expand...
Click to collapse
Sent ya PM
Smuskat
Hope That Helps.
I Got Magisk, Xposed & Even A Custom Bootscreen With Sound on Mine.
Okay. Got it all done, mostly thanks to Liberator Elite. And just so that no one else should ever be as stuck as I was, please allow me to clarify what actually worked:
I kept on attempting to put the phone into Fastboot mode or Bootloader mode. I could enter the stock recovery, choose to boot into Bootloader, but it wasn't working--or so I thought. All I would see upon reboot was a screen that was black, with the words "UMX" (Ultimate Mobile Xperience??? or whatever...)
However, Liberator Elite called to my attention that that screen WAS THE BOOTLOADER screen. I typed "Fastboot Devices" from the command prompt, and there was my phone! I then was able to flash over the boot.img file, and the TWRP posted here, and from TWRP, I was able to install Magisk.
For some of you, this is all simple--thanks for not laughing.
And to the entire community, thanks for being such a great resource! All done--thanks to you guys. Much appreciated!!!

Categories

Resources