bobo65:


put Ur phone off
press volume down then insert Ur phone to Ur lappy via USB...if u get a pop up that Ur device is successfully installed, then Ur device should work with sp flash tool, if u don't..download the drivers for Ur phone.. save them on Ur desktop then c connect Ur phone to Ur lappy via USB while pressing volume down then goto device manager and start installing the drivers that have question marks on them.. let Ur default search folder be Ur desktop

NeonDee:
Gyrados, you're good to go. Hope you choose LASU as most preferred? Also, aim 60+ in the p.UTME.
Lumiere91, you're good to go.

Karmanaut:
cc 4llerbuntu, saibinc They might be able to help.

donhils:
What is this one saying?

Gyrados:
I use an Alps s313 device,which some of you might know as HTC s313 and after trying to find support for my phone,I found out that there was no forum for an alps device: xda, etc..and it came to me that as there is no custom recovery or rom support,what would happen if we got a bootloop or bricked our devices...So come in and state your request,problems or contribution.....

Gyrados:
Alright....My phone is a cloned mtk device.Cpu Z says the manufacturer is Alps and the model is s313 but at the back of the phone,there is no manufacturer's name but the model is s51,the phone is a 5",4.2.3 ubifs mt6572 smartphone.I've googled both names and it appears that Alps never made such phone but searching on "s313" alone brought out my device although "s51" is the accurate spec of the device....Because of the lack of a known manufacturer,I guessed that the phone isn't widely used and for that it has no support or forum concerning it....When my dad first got the phone I had connected it to many PCs with no hassle but the USB port had begun to disconnect from the motherboard due to the thick cord he was using....He tried taking it for repairs but to no avail...He later passed the phone yo me and the first thing I tried doing was to make a cwm recovery with mtk droid tools so that I could tweak or flash a non laggy new rom but that's when I started getting the "unknown device" notification telling me that there was no drivers installed .I downloaded different drivers only to get that "the specified file does not contain information about your hardware"..Because of this,I could not back up my device or do anything related to PCs...Desperate to tweak the laggy ROM that I was based on,I Flashed v wrong twrp and cwm recovery and I end up losing my stock recovery... Although I had made a backup with flashify before doing so,flashify refuse to let me restore my stock recovery...So without success, I continued using my phone a normal user..I was checking on some build.prop tweaks when I was called and my friend took my phone and thinking that I was planning on doing so changed build.prop value and rebooted the phone which resulted in a soft brick...Since I didn't have a working recovery I couldn't wipe data...so I got the USB port fixed although I lost my volume keys in the process...Thinking I had solved the problem I went back to my PC but still.....I have adb,mtk droid tools and sp flash tools present the missing piece is the connection between the PC and the phone. Now my questions are
1)How do I get this device to be seen by a PC ?
2)I would be taking the phone to computer village next week and although I doubt it,can the phone be flashed?

Karmanaut:



He didn't mention the model.
I suggested that since he had a backup of the build.prop he should

adb push

it to his device, but he says his device is not detected.
He has the stock ROM,
He wants to flash it but SP tool is not recognising it.

Karmanaut:

cc 4llerbuntu, saibinc
They might be able to help.

Karmanaut:

Without USB debugging turned on, ADB can't find your device.
Does SP flash tool recognize it?


Since you've installed ADB, go to C://adb
That is the adb folder in your PC.
Open the folder, hold the Shift button on your keyboard then right click, then select "open command window here"
Connect your device to the pc, turn it on (either factory mode or normal boot)
type

adb devices

thenpress enter
See your device shows up

Karmanaut:

Congratulations.

You need SP flash tool for that, and the stock ROM to be flashed.
Tutorial on how to use SP flash tool:
http://forum.xda-developers.com/showthread.php?t=1982587

Karmanaut:

No problem.
Flashing your device will solve your problem instantly but you'll lose your data, which is why you have to go through this method to replace the build.prop which you say is the cause of the boot loop.
If you have no qualms about losing your data you can flash it.

Karmanaut:

Do it on a friend or colleague's PC.
Or go to a cyber café.

Karmanaut:

Did you follow the steps in the XDA thread?
If it didn't recognise your device, then download the MTK drivers from here:
https://m.box.com/shared_item/https%3A%2F%2Fwww.box.com%2Fs%2Fqavnkekndjy38xp0zne1

Karmanaut:

XP?
You need to activate the hidden administrator account.
Right-click "my computer" and select "manage". Expand "local users and groups". Select "users". Now right-click on the administrator account and select properties. You can enable it in there.
Or you can Upgrade to Windows 7.

Karmanaut:

Yes you can, but It'll be the modified one that's causing your device to bootloop, if you know the changes you made to the build.prop you can pull it from your device via ADB, edit it, then push it back to your device.

Karmanaut:

From another phone that's the same mode as yours.

http://forum.xda-developers.com/showthread.php?t=2588979
Get the ADB drivers from there.

Karmanaut:

Was USB debugging turned on beforehand?
If so boot into factory mode, connect your device to a PC with ADB installed and push the new build.prop to your device via ADB.

Karmanaut:

If you can boot to recovery your problem is half solved.
Just get a PC with ADB installed.
Then

adb push

the build.prop file from the same model of phone to your phone.