I'm new to rooting and all of this type of thing, i figured I would first start with my HTC Flyer. I successfully unlocked the bootloader, and installed SuperUser, upon installing greenify and i tried to install the Xposed Framework, and my device now is stuck in a boot loop.
When enter the bootloader and do a factory reset or try to enter factory it completely freezes, and when i try to connect it to my PC via fastboot the PC says that the USB device that is connected cannot be recognized and fastboot will not work. Did i completely fry this device? Also if you have time I couldnt figure out a proper way to flash a custom rom so if anyone has a guide for that I would appreciate a link to that as well.
Thank you so much!!
Hello guys,
I tried to update my phone to marshmellow, it got stuck at 95% and after it it entered a bootloop, I thought on just installing a custom recovery and take it from there but when I use fastboot it gives me a Remote: command not allowed error, I have my bootloader unlocked, I am thinking this has to do with not having USB debugging enabled, I can´t access the phone to activate it though. I have also tried to flash lots of stock roms through sd putting them on dload folder on Sds root but it fails right away at 5% it says update install failed, at this point Im not sure what to do... Any ideas?
thanks
Hi,
I'm new here, so please excuse me if I am posting in the wrong category.
So I tried to root my Doogee F7 (not the pro version) using fastboot and TWRP, and it resulted in a sort of bootloop where it says:
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then it restarts and gives the same message again. This loop has been going on for some time and I can't stop it because the phone has a non-removable battery and I have tried every possible combination of buttons (i.e. Power + Volume Down + Volume Up).
The process I used in my attempt to root was as following:
1. I used
Code:
adb reboot bootloader
to go into fastboot. (I already set up everything like USB debugging and OEM unlocking in the developer options)
2. I then used
Code:
fastboot oem unlock
and pressed Volume Up to unlock the bootloader. All was successful.
3. I then tried to flash TWRP to recovery and I believe this is where everything went wrong. I flashed it using
Code:
fastboot flash recovery recovery.img
and it was successful, according to the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\Users\momen\Downloads\recovery (1).img"
target reported max download size of 134217728 bytes
sending 'recovery' (12832 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.779s
4. After it finished I used
Code:
fastboot reboot
to reboot the phone and that's when it got stuck.
At the moment I am just letting my battery run out, as I have no other way of turning off the phone, and neither adb nor fastboot is working.
I don't really know if my device was even supported, but I followed the instructions on various websites stating that I should first unlock my bootloader, then flash TWRP, then flash superSU onto it, and my phone would be rooted. I used the latest TWRP image, and I think that was where I went wrong. Is there anything I can do to get my phone to work again?
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
solartediego said:
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
Click to expand...
Click to collapse
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Hello there. I suggest that you use "fastboot boot recovery.img" than using "fastboot flash" if you are not sure if the custom recovery works (or if you just want to test/try it). In this way, you'll just boot the custom recovery temporarily (and your stock recovery is still in tacked).
For rooting your device, first you'll need a working custom recovery for your device (you used TWRP, very first if it works or compatible with your device).
Insyder28 said:
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Click to expand...
Click to collapse
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
ciubsy2004 said:
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
Click to expand...
Click to collapse
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
TheBidan said:
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
Click to expand...
Click to collapse
I have managed to get the flash tool recognizing my phone.Had to keep pressed volume up,if i recall properly(or try volume down) before connecting usb cable to phone with flash tool opened and . It was a while ago though and i can't remember exactly which key was for sure. Hope this helps
Hello there. I have an Elephone P9000 Lite, which required a re-flash. Fair enough. After I formatted everything then flashed the stock ROM... I tried booting it up, but the boot animation won't show up, instead, it's all just a black screen. It went on like that for 10 minutes, before I decided to stop trying. It got bricked. Now, I decided to try and flash CM13 (I found a ROM on this forum), but I can't flash it using SP Flash Tool (what I used to flash stock) because it's an .img file, so it doesn't have a scatter. I came to the conclusion that I can use:
a) Recovery, which I can't access due to the device being bricked
or
b) ADB, which requires USB debugging to be enabled, but I can't enable it due to my device being bricked.
Can anyone help me?
(I have quite some experience with flashing and stuff, but I have no idea how to flash .img using a PC without having to access the phone's OS)
So, I have quite a problem, and having a country-native device isn't really helping.
I have a Cherry Mobile J2s in 6.0 with bootloader access allowed.
I seemed to have failed in rooting my phone by doing 'fastboot recovery twrp-3.2.1-0-cherry.img' it seemed to have been added properly but it said something like 'recovery' partition successfully made. I'm not sure if that's something wrong but I placed it in just in case. Because of this, my phone showed the Encryption Unsuccessful.
Here's the bad part. It doesn't seem to be able to reset itself. It just stays on the opening screen that says Flare J2s. It doesn't seem to open up the reset screen which I see from other tutorials. I believe it's because I failed to install the recovery img correctly, most especially since I had nothing like a boot img to use. I have tried opening recovery mode but to no avail. I seem to not have a way with connecting my phone to my pc so I can't use adb to fix itself.
Does anyone know how to fix this problem? Thanks in advance. ^^
Pink Panther Bumps
Bu-bump. Bu-bump.
Bu-buh, bu-buh, bu-buh, bu-buh-
Bu-buuuuuump. Bu-bu-bu-bump.
thatguy396 said:
So, I have quite a problem, and having a country-native device isn't really helping.
I have a Cherry Mobile J2s in 6.0 with bootloader access allowed.
I seemed to have failed in rooting my phone by doing 'fastboot recovery twrp-3.2.1-0-cherry.img' it seemed to have been added properly but it said something like 'recovery' partition successfully made. I'm not sure if that's something wrong but I placed it in just in case. Because of this, my phone showed the Encryption Unsuccessful.
Here's the bad part. It doesn't seem to be able to reset itself. It just stays on the opening screen that says Flare J2s. It doesn't seem to open up the reset screen which I see from other tutorials. I believe it's because I failed to install the recovery img correctly, most especially since I had nothing like a boot img to use. I have tried opening recovery mode but to no avail. I seem to not have a way with connecting my phone to my pc so I can't use adb to fix itself.
Does anyone know how to fix this problem? Thanks in advance. ^^
Click to expand...
Click to collapse
The proper command should have been fastboot flash recovery twrp-3.2.1-0-cherry.img . I am not to familiar with the device you are using, but can you put it in download mode? If that's an option, try to reflash the same firmware you are using to recover your phone.
Bump
Bump.
I think first you need to unlock bootloader before flashing that custom recovery .
Similar problem and Fix you can find here:
https://forum.xda-developers.com/showthread.php?t=2453849
Good Luck .