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
Related
Hi guys,
At the beggining sorry if I asked my question in wrong topic.
My phone is gt-s7562 galaxy s duos and I flashed a Rom via Odin but it failed,the Rom was downloaded correctly and drivers was installedin my pc
After that my phone stayed on boot,and it just booted in downloading mode which didn't have product name
I flashed a recovery file via Odin which was passed in Odin and after that I could go to recovery mode and I did full wipe and then reboot. my rom was booted successfuly, but I don't have product name yet!
So what should I do to solve this issue?
I can root my device by flashing a .zip file via recovery and then install a custom rom, but I don't know that this work can solve my issue or not?
Please help me, what should I do now?
{
"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"
}
Previous error in Odin by flashing rom :
And I can't backup my efs folder and I can't make a call, my phone goes to emergency calls only when i try to dial a number!
I tried to flash 1file and 3file ROM and with .Pit file via Odin but all of them have failed
I can install custom recovery and root my device.
What do you think aboat installing custom ROM via recovery? Can I repair my product and making a call?
What should I do to solve this issue?
Where should I ask my question? :crying:
Please help me
Perhaps flash original firmware?
And used odin 3?
Sent from my GT-S7562 using xda app-developers app
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
Hi, updating my Nexus 5 to marshmellow has left it stuck at the boot animation. I can get into recovery and have flashed factory 5.1.1 and 4.4.4 images but all that changes is the device loops with older boot animations. Kwongger's NEXUS 5 Toolkit v2.2 completed successfully but didn't improve anything. Trying to flash Cyanogenmod I run into adb "unauthorised". The device had usb debugging enabled and the RSA key of the PC was accepted but after multiple factory resets it appears to be gone.
Is there anyone out there with the experience to help me fix my phone? THANKS!!
How did you flash the image!! the google site for factory images isnt giving me all the files just one file once extracted...missing all the flash scripts...and win bat file...i downloaded lmw48b and 48m both the same sceanario....what file did you flash??
AcquiredIntellect said:
How did you flash the image!! the google site for factory images isnt giving me all the files just one file once extracted...missing all the flash scripts...and win bat file...i downloaded lmw48b and 48m both the same sceanario....what file did you flash??
Click to expand...
Click to collapse
Are you grabbing the images from here?
https://developers.google.com/android/nexus/images?hl=en
After unzipping e.g. 6.0.0 (MRA58K) I have the following: (check your AV if you have missing files)
{
"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"
}
Here's a good guide to flashing factory images:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Does no one have any advice for my bootloop issue???
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.
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).