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 .
Related
could anyone help with a seemingly bricked tab speed 6, attempted to root using kingoroot and it failed causing connection issues to google so i was unable to add a account, after hard reset and booting in to recovery i have wiped the cache and reset to factory, however now the tablet is stuck on checking connection and doesn't go any further with or without sim card.
after searching and searching i have come up with nothing apart from this threadhttp://forum.xda-developers.com/general/xda-assist/stock-rom-vodafone-speed-tab-6-vf-1397-t3329343
it looks as though he is having the same problem.
assuming kingoroot has corrupted the rom and i need to reflash to repair it,
i don't know if it is a generic tablet it appears to be made by alcatel but im unsure.
i also do not know if i could use a firmware from another device or even custom rom, anything will do as long as it doesn't end up in the bin
i also have another which hasnt been messed with and was wondering if it would be possible to back up the rom from it and reflash it to the bricked one, if so could anyone steer me in the right direction
could anyone help me locate as rom and flashing tool that will help
thanks in advance, apologies if this is posted in the wrong place.
You said you had a second one, you don't have to root it, just follow this tutorial and hopefully you should be good to go.
no bootloader
hi thanks for your reply however upon backing up the other tablet, it had still not solved the problem does that tutorial back up the Rom or just system files I created the backup.ab and used adb recovery to no avail...., however, I gave up on this method and was going to use a custom recovery on the the working tablet to back up the rom, however when I tell adb to reboot to the downloader it just reboots the tablet there seams to be no downloader on either tablet, so even if I had the rom it appears I could not flash it via the downloader as I can't get to it, nor sd card as there is no option to flash it, it's really bugging me now as it's obviously only soft bricked, any more help would be greatly appreciated thanks in advance also to add fastboot lists the device but when I tell it write the recovery it says waiting for device
inexperience
thanks for the help I am quiet inexperienced but determined so any help pointing me in the right direction would help thanks
facerolla said:
hi thanks for your reply however upon backing up the other tablet, it had still not solved the problem does that tutorial back up the Rom or just system files I created the backup.ab and used adb recovery to no avail...., however, I gave up on this method and was going to use a custom recovery on the the working tablet to back up the rom, however when I tell adb to reboot to the downloader it just reboots the tablet there seams to be no downloader on either tablet, so even if I had the rom it appears I could not flash it via the downloader as I can't get to it, nor sd card as there is no option to flash it, it's really bugging me now as it's obviously only soft bricked, any more help would be greatly appreciated thanks in advance also to add fastboot lists the device but when I tell it write the recovery it says waiting for device
Click to expand...
Click to collapse
What command do you do to tell adb to reboot to download? What command to you give fastboot to flash the recovery?
hi thanks for the quick reply im ujsing adb reboot-bootloader , it reboots the tablet and then greats me with the vodafone start up logo then asks me which country im in, as for attempting to flash with fastboot ive tried fastboot oem unlock to unlock the bootloader ( says waiting for device) ive also tried adb push c:\adb\backup.ab ( doesnt seam to recognise the psush command as it cycles through all available commands , and attempted to flash recovery with fastboot flash recvovery cwm.zip ( says waiting for device) adb reboot sideload just reboots the tablet same as adb reboot bootloader, thanks for all your help.., ikt is really bugging me i appreciate your time.
I don't know if download mode is accessed differently I've found this post that seems to Suggest hold volume up and down then connect until battery charging appears http://forum.gsmhosting.com/vbb/f272/vf-1397-a-2047715/ this is for unlocking it seems, but don't seam to be able to get it to work, earlier I removed root with kingoroot from kingoroot app, also to no avail and rooted again both root removal and rooting were successful but still tablet stays on the checking connection screen when rebooted, I was hoping the removal may of fixed the issue but no...., I was thinking if I could get back custom recovery on it I could do the same to the working one I have begrudgingly so I could back up the working ones rom and use it to flash the bricked one, but I don't really want to risk bricking that one either, but was considering finding another rom from another model the same chipset and flash it with that but obviously no download mode means I can't do it..
if it's any help The recovery mode states android system recovery <3e>
LMY47V release keys
reboot system now
wipe data/factory reset
wipe cache partition
power down
enable adb
they are the only options,
again thanks for all your time and effort
facerolla said:
hi thanks for the quick reply im ujsing adb reboot-bootloader , it reboots the tablet and then greats me with the vodafone start up logo then asks me which country im in, as for attempting to flash with fastboot ive tried fastboot oem unlock to unlock the bootloader ( says waiting for device) ive also tried adb push c:\adb\backup.ab ( doesnt seam to recognise the psush command as it cycles through all available commands , and attempted to flash recovery with fastboot flash recvovery cwm.zip ( says waiting for device) adb reboot sideload just reboots the tablet same as adb reboot bootloader, thanks for all your help.., ikt is really bugging me i appreciate your time.
Click to expand...
Click to collapse
You can't always unlock the bootloader via that command and you'll need to have the bootloader unlocked to flash a custom recovery, if you can find stock images on the web you can flash them via fastboot.
---------- Post added at 12:44 PM ---------- Previous post was at 12:36 PM ----------
Also to restore an adb backup you do "adb restore filename".
unfortunately there is no stock image anywhere on the Web, is there a good app I could use to save the rom from the working tablet without rooting, really don't want to risk rooting the working tablet
facerolla said:
unfortunately there is no stock image anywhere on the Web, is there a good app I could use to save the rom from the working tablet without rooting, really don't want to risk rooting the working tablet
Click to expand...
Click to collapse
Hello! Remember this?
Also to restore an adb backup you do "adb restore filename".
Click to expand...
Click to collapse
Did it work? I see you left a "thanks" so I assume something happened.
hi, I give up on the tablet, I've been asked to see if I can give it another go, but don't know where to start, I still have a working one but no idea how to get the rom from the working one to the bricked one. thanks for the help you gave me to begin with.
facerolla said:
hi, I give up on the tablet, I've been asked to see if I can give it another go, but don't know where to start, I still have a working one but no idea how to get the rom from the working one to the bricked one. thanks for the help you gave me to begin with.
Click to expand...
Click to collapse
I have a couple tricks up my sleeve and that is, you know how you said when you ran adb reboot bootloader? Run adb shell instead and it should give you a command explorer, from there, type "su" and report results, you should see either a root request on the device or a hash sign in the coommand shell.
Just a quick question
Did you ever manage to get it working if so how did you go about doing it as i attempted to install a custom boot animation and it appears to be stuck in a constant boot loop as such i'm not really sure what to do with it or if it is savable. Any response would be helpful. 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
Hey,
I'm quite new with all this stuff and I just got into some problem. I wiped everything in recovery mode using twrp, cache and internal memory etc (dont ask me why). Anyway, my phone seem to be stuck on a booting loop since I can't enter recovery because twrp fail to load up correctly. You can see where it gets stuck in the image I attached.
Someone know what's wrong and if it's possible to fix somehow?
Thanks :fingers-crossed:
Okay, it seems like I managed to fix it myself. I used adb and fastboot to install everything as stock.
https://developers.google.com/android/images
However I'm not sure about the USB debugging part, how do I enable that if there is no os installed? Do I even need it enabled when I use fastboot?
Can I do that? My device won't boot into recovery, despite flashing it through fastboot several times. Also tried "fastboot boot twrp.img" and it doesn't boot. Can I flash original OxygenOS or any other rom through fastboot? If so, how?
Also my device cannot be seen @"adb devices", I believe usb debugging is off, any way I can turn it on using fastboot? Googled for a while and couldn't find any information.
Just google "Mega Unbrick Guide" or search here !
Thanks for the suggestion, I did follow that process successfully but the phone is still stuck in a bootloop. The bootloader locked in the process as well and now I cannot flash any recovery through fastboot. The phone will get into recovery though but trying to sideload anything will result in a "protocol fault(no status)" error.
As a sidenote, the internal storage seems "faulty" to say the least now. It is not recognized at any time as MTP device but rather shows 3 unformated partitions of 1.00MBs, 155MBs and 2.5GB respectively. Moreover trying to "Install from Local" @recovery menu renders no response, just a short vibration, sometimes.
Anyone else encountered this problem? Is there any chance it is a hardware problem afterall? I'm really clueless right now.
While trying to set up a new boot animation, I came across an error which prevented my phone form booting up into the OS and instead showed me the Fastboot screen every time. I tried reflashing twrp, as well as flashing another boot animation into it. While reflashing TWRP for the third time (I didn't really know what to do so I just hoped it would work eventually), it seems like it corrupted some of my phone data, meaning preloader and I believe some other stuff. The phone now won't boot at all, and also isn't getting recognized by SPFlashTool. While plugging it into my PC I can still hear the "connected" and "disconnected" sound though.
Any ideas on what I could do?
I know its kinda late but
Have you tried using adb or fastboot and check if your device is recognized with the adb devices command?
noah_bfn said:
Have you tried using adb or fastboot and check if your device is recognized with the adb devices command?
Click to expand...
Click to collapse
I don't know how to do it But I'm having the same problem the screen is black , can you guys help me ?
Your phone sounds like it is soft bricked.
emersonsamuel said:
I don't know how to do it But I'm having the same problem the screen is black , can you guys help me ?
Click to expand...
Click to collapse
Your phone sounds as though it is soft bricked. It can be brought back to life.
Follow here to un-brick your device:
https://forum.xda-developers.com/android/general/ulefone-power-5-twrp-root-project-treble-t3943714
Loyal_Guardian said:
While trying to set up a new boot animation, I came across an error which prevented my phone form booting up into the OS and instead showed me the Fastboot screen every time. I tried reflashing twrp, as well as flashing another boot animation into it. While reflashing TWRP for the third time (I didn't really know what to do so I just hoped it would work eventually), it seems like it corrupted some of my phone data, meaning preloader and I believe some other stuff. The phone now won't boot at all, and also isn't getting recognized by SPFlashTool. While plugging it into my PC I can still hear the "connected" and "disconnected" sound though.
Any ideas on what I could do?
Click to expand...
Click to collapse
Just use the spflashtool. Try multiple times and try my updated guide. Make sure you installed the drivers properly AND USE A GOOD CABLE. I had some hard times flashing with spflashtool, but it was just the cable.