I had previously ( and successfully ) used this http://forum.xda-developers.com/showthread.php?t=2168413 to install Rataplan's ROM. For some reason, I lost interest in the 710 and put it away for a couple years. Now when trying to turn it on the screen is dead. The battery has a full charge.
I thought that I could retrace the steps in that thread I followed earlier to fix this problem. However, neither NSS 0.48 or 0.51 recognize the phone as Nokia Phone Connectivity. All I get is NAND Disk Drive.
The Qualcomm CDMA Technologies MSM drivers keep failing to install. I followed the steps in this thread : http://forum.xda-developers.com/showthread.php?t=1669498 thinking it would succeed. It doesn't.
Now I am trying to locate that " one click downloader " mentioned in the instructions.
Does anybody know where I might find that program ???????
Any other suggestions will be most appreciated.
Related
Hi All,
Yes I searched, could not find a helpful post that I could understand (unfortunately a lot of not-so-good english on these forums!).
I used the file 'windowsmobile2003se.exe' here;
http://forum.xda-developers.com/showthread.php?t=230279
It started loading fine, then when it came up with the progress bar to start updating, my device rebooted and is now stuck in bootloader.
When I try himaupgradeut.exe, it gives me a ERROR 101: Connection Error. USB is disabled in ActiveSync and I can see the device as "Microsoft USB Sync".
The USB still works (I can use mtty and xda2unlock in Windows XP and they both work fine). Is the device still recoverable?
I have hard reset (Power + Reset), removed and re-inserted battery and tried a normal reset, none of these work.
Can I please have some step-by-step instructions on how to recover the phone? The bootloader version is 1.06
Thanks.
can you get some pics?
Have you tryed leaving the battery out for 1 day or over night. Because that fixed some problems for me.
try it
flyboy
Yeah I've left the battery out overnight (about 12 hours to make sure the backup battery ran flat). It's still stuck on the boatloader.
It's just got the normal bootloader screen (Serial up top and 1.06 down the bottom) and this changes to USB when in the cradle, so the device seems to be fine.
Any ideas?
Solution found!
I HAVE FOUND A SOLUTION FOR RECOVERING FROM BOOTLOADER!
Full props and thanks go to utak3r of buzzdev.net
Please go to this thread.
http://buzzdev.net/viewtopic.php?f=8&t=36437&start=0
MODS: Please sticky this. Please.
Hi All,
I have made a script that people can use to easily flash their Himalaya without performing all the above steps manually.
My extreme and eternal thanks go to utak3r (from BuzzDev), xda-developers.com and buzzdev.net for building such great communities and for providing so much help and information (even if it is a little hard to follow sometimes!).
You can download it from;
http://members.iinet.net.au/~nomicakes/MakeSDBoot.zip
http://www.clonnyserver.com/uploads/tools/himalaya/MakeSDBoot.zip
The zip file contains the script and the tools neccesary to do this.
As above, if you aren't familar with flashing devices and the possible outcomes, DO NOT USE THIS TOOL.
Hi there,
Yesterday I tried to upgrade my Qtek 2020 to the last rom available but something went wrong and now my PPC only shows the bootloader screen.
After hours of researching on Google I found this forum and this topic. I tried to do what is in utak3r tutorial but I can't connect to my PPC using mtty (usb port can't open) and I don't know why. :\
When I try himaupgradeut.exe, it gives me a ERROR 101: Connection Error too...
And finally when I run this script made by Clontarf it fails on the last step on writing to the SD card. It gives me a Error - Access Denied.
I don't know how to solve this. Would you please help me?
Problem solved!
I bricked my Desire 310 when i tried to replace the stock recovery.
Rooted it successfully, read a lot of threads regarding MTK-based phones and thought i might be able to get more out of it, as i wasn't completely fine with 4.2.2 installed on a brand new phone.
However, i ended up with trying to install a custom recovery as described [here(would be a link if i were allowed to post them)]. The whole process gave no error, everything looked fine, ending with a "success!"-message, followed by a reboot, showing just the HTC splash... and a reboot... and a reboot... and.. well i guess you know what happened next.
Based on a whole lot of different threads, this might not be the end of my phone, as i can still see the [preloader(would be a picture if i were allowed to link it)] in my device manager, which basically means "hi, i'm not completely dead and you might find a way to recover me".
The question is: how?
I tried out SP Flash tool and MTK Flash tool so far. both programs find the phone when i get it ready to download my previously made backup (hey. i might not exactly know what i'm doing there, but at least i saved everything before i wrecked it! ).
The problem is: I just get an[error message(look above)] about some failed download to SRAM sorcery, which sounds cool and important but doesn't give me a clue about what i'm doing wrong or how to fix it. (cable ok tested 3 different cables, including the one the device was shipped with, also tested it on my PC running win 8.1 x64 and another one running win 7 x86)
Does anyone have an idea how i could get at least a working bootloader/recovery back to my device?
Tell me if you need any extra information
I also link an attachment including the log file created by SP Flash Tool.
View attachment 2772794
Well. That's it. Thanks in advance for anything that may be posted in here
Two Pictures related to this:
View attachment 2772803
View attachment 2772804
Need your help
Reebee87 said:
I bricked my Desire 310 when i tried to replace the stock recovery.
Rooted it successfully, read a lot of threads regarding MTK-based phones and thought i might be able to get more out of it, as i wasn't completely fine with 4.2.2 installed on a brand new phone.
However, i ended up with trying to install a custom recovery as described [here(would be a link if i were allowed to post them)]. The whole process gave no error, everything looked fine, ending with a "success!"-message, followed by a reboot, showing just the HTC splash... and a reboot... and a reboot... and.. well i guess you know what happened next.
Based on a whole lot of different threads, this might not be the end of my phone, as i can still see the [preloader(would be a picture if i were allowed to link it)] in my device manager, which basically means "hi, i'm not completely dead and you might find a way to recover me".
The question is: how?
I tried out SP Flash tool and MTK Flash tool so far. both programs find the phone when i get it ready to download my previously made backup (hey. i might not exactly know what i'm doing there, but at least i saved everything before i wrecked it! ).
The problem is: I just get an[error message(look above)] about some failed download to SRAM sorcery, which sounds cool and important but doesn't give me a clue about what i'm doing wrong or how to fix it. (cable ok tested 3 different cables, including the one the device was shipped with, also tested it on my PC running win 8.1 x64 and another one running win 7 x86)
Does anyone have an idea how i could get at least a working bootloader/recovery back to my device?
Tell me if you need any extra information
I also link an attachment including the log file created by SP Flash Tool.
View attachment 2772794
Well. That's it. Thanks in advance for anything that may be posted in here
Two Pictures related to this:
View attachment 2772803
View attachment 2772804
Click to expand...
Click to collapse
Hi ! saw your thread and required your help
1) can u proveide me information about how exactly did you root your device !!
And secondly if u remember your phone's build number can u plzz tel me because I also have aproblem with my desire 310 its single sim and 1gb ram version I eceived a software update and after the installation the phone keeps rebooting after every 2 mins if I use it or plug it in for charging and stays awake if I put it in ecovery or factory mode so I needed your roms backup so that I can fix my phone Unless if your phone was of the same specks as mine
I will be waiting for your soon response thanks
It happend the same for me! U can try recovery mode but it is not gonna work.
I have the same problem (
i have this phone and after update that i have no problem with that. my phone is rooted by vroot app
Reebee87 said:
I bricked my Desire 310 when i tried to replace the stock recovery.
Rooted it successfully, read a lot of threads regarding MTK-based phones and thought i might be able to get more out of it, as i wasn't completely fine with 4.2.2 installed on a brand new phone.
However, i ended up with trying to install a custom recovery as described [here(would be a link if i were allowed to post them)]. The whole process gave no error, everything looked fine, ending with a "success!"-message, followed by a reboot, showing just the HTC splash... and a reboot... and a reboot... and.. well i guess you know what happened next.
Based on a whole lot of different threads, this might not be the end of my phone, as i can still see the [preloader(would be a picture if i were allowed to link it)] in my device manager, which basically means "hi, i'm not completely dead and you might find a way to recover me".
The question is: how?
I tried out SP Flash tool and MTK Flash tool so far. both programs find the phone when i get it ready to download my previously made backup (hey. i might not exactly know what i'm doing there, but at least i saved everything before i wrecked it! ).
The problem is: I just get an[error message(look above)] about some failed download to SRAM sorcery, which sounds cool and important but doesn't give me a clue about what i'm doing wrong or how to fix it. (cable ok tested 3 different cables, including the one the device was shipped with, also tested it on my PC running win 8.1 x64 and another one running win 7 x86)
Does anyone have an idea how i could get at least a working bootloader/recovery back to my device?
Tell me if you need any extra information
I also link an attachment including the log file created by SP Flash Tool.
View attachment 2772794
Well. That's it. Thanks in advance for anything that may be posted in here
Two Pictures related to this:
View attachment 2772803
View attachment 2772804
Click to expand...
Click to collapse
Select DA_SWSEC.bin as Download-Agent...
Hi! I really head your help!! I looked a lot around and followed lots of guides on how to revive my phone, but i've some big issue with it and i really hope that someone here may help me...
The Hard Brick (it won't turn on, it won't charge, it seems like he's totally dead) occurred the other day, i was trying to open googlemaps and the SP was really slow, so i turned it off, and then i wasn't able to turn it on again, at first it was stucked at the screen with the logo (before the splash animation, the logo that you can't normally change) then i managed to turn it on after 2 or 3 times taking off the SD card, but i got a corrupted homescreen, i turned it off again and then, after 2 or 3 times, i got the Hard Brick!!
Probably in my last attempts i created a bounch of errors in the rom that bricked my phone.
Here's what i've done to revive it:
- SPFlashTool 1332.0.187
- official drivers, recovery, rom, etc, from the jiayu.es website.
- removed the battery, manually installed the drivers.
- with spft i loaded the scatter file of the official rom and started the format:
the phone is recognised as Mediatek USB VCOM (Android) (COM3)
i always got the error: S_COM_PORT_OPEN_FAIL (1013)/B] (with every option available)
I tryied to download only the preloader.bin and the recovery.img but i recive the same error.
- someone give me an advice: to remove every old driver for the phone and leave the SPFlashTool to recognise the phone forcing the installation of the drivers. And i really don't get how to do it, the windows update automatically detect the device, if i stop the windows update i simply get an unknown device, the SPFT don't have a chance to recognise it and force the installation of the drivers.
Does anyone of you have a solution, a similar problem, a way to revive my cellphone?
I really can't effort another one XD
FenriX` said:
Hi! I really head your help!! I looked a lot around and followed lots of guides on how to revive my phone, but i've some big issue with it and i really hope that someone here may help me...
The Hard Brick (it won't turn on, it won't charge, it seems like he's totally dead) occurred the other day, i was trying to open googlemaps and the SP was really slow, so i turned it off, and then i wasn't able to turn it on again, at first it was stucked at the screen with the logo (before the splash animation, the logo that you can't normally change) then i managed to turn it on after 2 or 3 times taking off the SD card, but i got a corrupted homescreen, i turned it off again and then, after 2 or 3 times, i got the Hard Brick!!
Probably in my last attempts i created a bounch of errors in the rom that bricked my phone.
Here's what i've done to revive it:
- SPFlashTool 1332.0.187
- official drivers, recovery, rom, etc, from the jiayu.es website.
- removed the battery, manually installed the drivers.
- with spft i loaded the scatter file of the official rom and started the format:
the phone is recognised as Mediatek USB VCOM (Android) (COM3)
i always got the error: S_COM_PORT_OPEN_FAIL (1013)/B] (with every option available)
I tryied to download only the preloader.bin and the recovery.img but i recive the same error.
- someone give me an advice: to remove every old driver for the phone and leave the SPFlashTool to recognise the phone forcing the installation of the drivers. And i really don't get how to do it, the windows update automatically detect the device, if i stop the windows update i simply get an unknown device, the SPFT don't have a chance to recognise it and force the installation of the drivers.
Does anyone of you have a solution, a similar problem, a way to revive my cellphone?
I really can't effort another one XD
Click to expand...
Click to collapse
There is a guide right here
I already tryied to revive my phone with this guide, but with no success...
I was thinking that maybe someone can show me the right driver (with all the package of driver that i find i always have no idea which one i've to install)
And maybe someone already tryied to revive a jiayu g4a and know the name of the right preloader, 'cause apparently what i need to do is to download into the SP the right preloader to revive it...
I bought a " Figo Atrium 5.5 ". The Figo website has instructions to flash the device to 6.0 Marshmallow instead of Lollipop. I believe these instructions are incomplete. Here is the link, I'll detail for you what I've tried using their recommended software SPFlash https://support.figoglobal.com/support/solutions/articles/16000047848-android-6-0-atrium-5-5
I downloaded and extracted both files on Windows 8 64 bit desktop, the SPFlash tool and the other the Atrium ROM itself. The very first instruction is installing the drivers which I do using the install.bat file from the "Driver_Auto_Installer_v1.352.00" folder. I believe my install fails at this point. Opening the Flash_Tool exe after installing the drivers (the tool does say they installed properly) I never get any information in the Chip Info in the Flash_Tool. It appears those drivers are not installed properly.
Researching this, I came across videos that suggest the drivers were not being installed properly because the drivers are Not digitally signed. I followed the instructions to fix the problem by booting to Advanced StartUp options then choosing to run the OS with digital signing checking disabled. Now on installing the drivers I get the popup asking me if I am sure I want to install the drivers I choose Install Anyway. The driver install tool just sits there for a couple of minutes doing nothing, then the popup message comes back asking again, am I sure I want to install the drivers. This is an endless loop, the application never attempts to install the drivers. The phone is plugged into the the PC at this point because I assume it must be for windows to see the phone. Note, at no time except the End of the instructions does it tell me to have the phone plugged in. This confuses me greatly. I don't know if the phone should be plugged into the pc at this point or not. Can someone who if used to doing these kinda flash jobs look over these instructions and help me figure out what I'm doing wrong. Thank you. I will do my best to answer back with more info, I'll be home all day watching this thread.
( btw, the forum on that site is moderated. I have tried over two weeks ago to post forum messages about my issues, but the moderators never posted any of my messages - it seems customer service is non existent)
Please mark this as Solved. I fixed my problem with a bit more research. Figo gives incomplete and also incorrect information on upgrading the Rom ( as you can see) Nowhere do they tell you in the instructions that you need USB Debugging Enabled or how to do it. This is a critical step or the drivers will never see the phone. The drivers did correctly install the first time as I suggested. That was the incomplete information. The incorrect information is this: They tell you to take the battery out to flash the device - which will never work because the phone needs power for the drivers to flash the device. What you have to do while the phone is On and Connected to PC is remove the battery then put it back in - then the phone will flash. This is critical step 2 they were wrong about. I suspect it has something to do with a bad Chinese translation.
Hi everyone. As I said on a former post, I have an Alcatel 1t 7 tablet; I need its stock recovery image, but even stock firmware is getting impossible to find. I mean, apparently there are firmware for that reference of tablet, but what happens, is that there are several models that share the same physical appearance, but have different hardware, so, they have different firmware, and by that reason, their firmware don't work for my tablet. Anyway...
The fact is, looking that its original firmware is not available on the internet, at least publicly; I'm trying to reflash my tablet by using alcatel's tool called "Alcatel Mobile Upgrade", a tool that I don't guess, would be unknown for many of you. So as I said, I'm trying to reflash it with it (and in the process, restore stock recovery, I hope). So I installed MTK drivers, installed the version recommended for this tablet, followed program's instructions, but when I reach step 2 of 4, the program warns me saying this: "Read terminal information failed. Unplug device, remove the device battery and plug it again - Repeat step 2 and try again".
The issue is, that its battery is internal, not removable; even, is soldered to the board. And I must add, that at first, when I bought this tablet and began to "experiment" with it, I was using SP flash tool, and it was giving me almost the same warning that Alcatel mobile upgrade, but later I discovered what that was a fail of the used sp flash tool version. On a webpage, someone recommended a specific version of sp flash tool to fix that issue; I mean, that I could download firmware to the device without having to "unplug battery"; and It worked.
So first ¿How can upgrade my tablet by using that program?¿What am I doing wrong?¿ Which device must appear under device manager, to it can work?¿mtk usb port, Mediatek DA usb VCOM, Android preloader, or which one? And second, ¿Could be this problem, due to alcatel's mobile upgrade version?
let battery drain to make sure device is powered off. you only have preloader mode for a second - within this time pick up in device manager and install preloader drivers.
if drivers installed correctly, first start flashing, then connect phone. flash tool will keep device in preloader mode for the flashing time period
aIecxs said:
let battery drain to make sure device is powered off. you only have preloader mode for a second - within this time pick up in device manager and install preloader drivers.
if drivers installed correctly, first start flashing, then connect phone. flash tool will keep device in preloader mode for the flashing time period
Click to expand...
Click to collapse
Thank you for replying. Definitely using Alcatel mobile upgrade is not an option, at least to me. I mean, I couldn't make it work in any way. "Fortunately", after an exhaustive search, I could find a post on internet, that recommended for a similar issue, to use Sugar MTK; the publisher shared this program and its credentials, for can use it . So I downloaded and used it, and I could restore my original stock. Now my issue is to port it to TWRP, but now I'm gonna to write a new post about it.
link me to the sugarmtk