Been scratching my head on this one for a day or two, as while Kinguser/Kingroot works on my phone, it just doesn't cut it in my case and I wouldn't want to put my trust on something that's of dubious repute. Not that I am laying smack on the Kinguser team though, it's that I'm more confident with something the Android community is vouching on for years.
Things needed:
MTK Droid Tools
A working 5038A stock ROM. This image taken off a Smart-locked phone may work.
The latest SuperSU flashable image
Your phone
ADB drivers, and some patience
So what I did was this: Fire up MTK Droid Tools, and click on the Root/Backup/Recovery tab. Click on the Recovery and Boot button, and it'll ask you for a boot image from the stock ROM. Click Yes on the message box that shows up, and if done correctly you'll end up with a fresh recovery image on the recovery folder. Open SP Flash Tool, load up the scatter file from the ROM you just downloaded (or backed up), then load the recovery image you made earlier. You can either flash the whole ROM along with the CWM you did, or just the latter:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once all that's done, boot to recovery by holding Volume+ and Power. Select the SuperSU package from your SD card, then let it do its thing. If done correctly, SuperSU should work properly on your device. Make sure to untick Mount namespace separation on the SuperSU settings menu for Titanium Backup to work correctly (c.f. djranoia).
You can try this image I made just in case; I can't guarantee that it works on any Alcatel OT-5038A out there though.
Code:
http://d-h.st/Ja0x
I don't take credit for all of this, but I'd just like to share this tip in case you feel like doing things the hard way.
Related
Hello,
I need help to recover my phone - Star s9500 after booting into factory mode and going to "Clear eMMC" (I know this was stupid of me but that is another story...). From MTKDroidTools, the phone hardware reads mt6582 and was running 4.2.2.
When the phone powers on, I only get the Android bootup animation and everything stops there.
I managed to install CWM using MTKDroidTools and even tried to flash the ROM using CWM after placing the zipped image on an sdcard. CWM simply aborts after attempting to read the zipped package.
For some reason MTKDroidTools does not show the IMEIs, but I can see the records when I power the phone into factory mode.
I tried to flash the rom using SP Flash tools as indicated in this thread:http://forum.xda-developers.com/showthread.php?t=2458369, but I simply keep waiting with the indicator "EMMC searching" from the tool or the phone itself even after 10 minutes (see attached files).
I am attempting to flash with this rom - http://www.needrom.com/mobile/star-s9500-mt6582-fwvga/ .
I did read somewhere that I have to setup partition information stored in the eMMC for the flashing to be successful. The post on this is here: http://checkrom.com/threads/formatting-emmc-no-no-no.647/ , but I believe I can get this phone up and running again.
Various sources say that I only need to flash the rom. Can someone please point me in the right direction? Why am I unable to flash with SP Flashtools? What alternative flash tools can I try? For pictures please see attached.
I am also now getting a BROM Error from SP Flashtools saying Failed to open COM 8.(see attached)
Thank you in advance!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
S
Hello. Recently I got my hands on this device. Never had experience with flashing Roms/kernels but did my research and got familiar enough to explain the problem.
The phone is very slow and unresponsive. I have checked and it is rooted. So I decided to flash new ROM to it, CM11 ROM + OnePlus One Conversion Kit for Nexus S. However, there is a warning:
"YOU HAVE TO USE CWM Recovery 6.0.4.3 or HIGHER otherwise you will fail during install and other problems will occur!!! You can easily update to latest CWM Recovery by using ROM Manager from Play Store."
So I downloaded ROM Manager to update it and that's where the problems started that I do not know how to deal with, and I don't want to risk bricking. ROM Manager installs fine, but when entering gives following message from first image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So when I tried to ignore that and update it anyway, got a message with error, which resulted in red triangle when booting into recovery. After a while system loads up as usual, phone is working but painfully slow. So if anyone is kind enough to help me restore it to working condition? What to do?
I found it always easier to use the fastboot method. This method it quite primitive and thus might have less problems. Mainly one makes sure that fastboot is installed on the PC (this is ridiculously simple for Linux, but I don't know about and am not interested in Windows), connects the device via USB, boots it to bootloader and issues some commands on the PC to push all parts of the so called "ROM" directly to the device.
And: I used the latest version of TWRP which is similar to CWM, but prettier.
CANNIBAL OPEN TOUCH RECOVERY PORT TO ALCATEL ONE TOUCH POP C2
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM'S have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
READ THIS
First time you boot in recovery will be a touchscreen calibration set up: you have to touch three times the red square. Also, first time you do a backup, it will take a little longer time, because it will be create directory structure and free up the space. After that it will be a joy, is fast, is powerfull, is full of options and is funny. Or if you don't have an sdcard inside your phone, you don't have to go through this
Click to expand...
Click to collapse
How to Install
Download the attached recovery below and place somewhere on the desktop.
Open SP flash tools and choose the scatter file then choose the recovery and flash it.
OR
Use mobile uncle tools to flash it.
Credits:
Project Open Cannibal for this original recovery
carliv for porting this recovery to MTK so that i can port to this device
michfood for his unpack/repack tools
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi
I've downloaded and copied the update firmware files for my D2302, however when I try to create the FTF file it freezes while processing the first file. The decrypted file it creates has no data in it. Any ideas?
My end goal is to be able to have it rooted and if I'm really lucky, have a recovery. However, it doesn't look like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[D230X.properties, in Flashtool data] it even has a recovery (which sounds odd, but I can't get it to go into recovery by power+voldn - it just goes through to system. - I'm now trying to do root with locked bootloader methods.) EDIT: Turns out you have to mash voldn to get into recovery.
Thanks
Biscuit. said:
Hi
I've downloaded and copied the update firmware files for my D2302, however when I try to create the FTF file it freezes while processing the first file. The decrypted file it creates has no data in it. Any ideas?
My end goal is to be able to have it rooted and if I'm really lucky, have a recovery. However, it doesn't look like
[D230X.properties, in Flashtool data] it even has a recovery (which sounds odd, but I can't get it to go into recovery by power+voldn - it just goes through to system. - I'm now trying to do root with locked bootloader methods.) EDIT: Turns out you have to mash voldn to get into recovery.
Thanks
Click to expand...
Click to collapse
If you have an locked bootloader, install philz-twrp multirecovery and take a nandroid backup. I believe it's best to have a nandroid and and ftf (clean) because if you have some mod or problem with your current ROM and an FTF is your only choice it could end badly.
Sent from my D2303 using XDA Free mobile app
So I tried to install TWRP to a Blu Advance 5.0 HD (seems there's not much info on these phones too) and after some bootloops with TWRP (for a failure in the recovery script), I was able to get back into fastboot and flash the stock image from bluroms info website, however now it simply goes to the BLU screen and restarts all the time. I've tried every possible combination with buttons but can't get anywhere, any ideas?
Edit: Upon further searches and realizing I screwed up and flashed boot.img instead of the recovery image from bluroms website, I have also found that I have no way of recovering the device with adb/fastboot, but that I could have a possibility if I use SPFlash tool (Yes, it detects it when plugging it in and whilst it is doing the bootloop) to try and flash the correct file to the device (which currently fails with an error message that doesn't have many details [I do the following things to get the error:
1 - Load the scatter file.
2 - Select recovery to be flashed.
3 - Click download
4 - Plug phone into computer
5 - Wait for download
6 - Error message pops up:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
]).
If there are any ideas on recovering a device from this state without having to buy anything, it'd be appreciated. (And hopefully a good list of instructions on how to use SPFlash tool to recover the device).