I have Alcatel OT-910, but i cant find anything about root & rom for this model here on xda-developers forum. I found threads for other Alcatel models (OT-908, OT-980, OT-990) and i was wondering is anyone working on this particular model? Is it possibile to have root access? stock ROM for OT-910? Thanks.
Alcatel OT-910
CPU 600 MHz
OS Android OS, v2.2 (Froyo)
Keyboard QWERTY
root
i have tried to root my OT-910 with SuperOneClick 2.3.3, but it doesn't work.
Keeps stuck at Step #7 Waiting for Device.
also tried to unplug and replug it at this part, but no chance.
any other ideas how to get root? Some of the installed apps are useless for me and eat up my memory, want to get rid of them
rooting problem
I've got OT910 too, tried several ways to root with steps, provided for other Alcatel android phones - no luck.
Try with different versions os superoneclick. Aso you should install Pdanet on your phone and your computer to and try again with superoneclick.
Sent from my ALCATEL one touch 990
No luck still
I tried all SuperOneClick releases, z4root, GingerBreak - nothing really works. The phone is hardly operable without root - too much garbage preinstalled.
Hey, i have an Alcatel OT-909a (which is the same as Alcatel OT-910 but with a lower px camera) and i also am unable to get root access, i already know that there is a stock busybox, and have seen some files of the internal memory but still not having luck, i also flashed some CWM and RA recoveries but i just got stuck while trying to access recovery, so i have to get back to stock recovery, i think there must be a way to do at least a nandroid backup and try to root the backup and flash again, but i dont know, the CWM recovery just boot the android logo, after there is nothing in the screen, but the QWERTY keys are on like if the phone was in recovery, i had tried Super One Click 1.9.2 and 2.3.3 and got stuck in step #7 too, zergRush and GingerBreak doesnt work also, something extrange for me is that the last time i try CWM, it didnt boot into recovery but into fastboot, as far as i know internal memory is read-only except for the installation of apps and some folders (or somehow i push GingerBreak and zergRush to the internal memory isn't?), i can't push su to the xbin or bin folders, but i already saw what is inside xbin an bin (as i said memory is read-only and there are some folders that requires permissions to access), there must be a way to push su to xbin folder (or at least maybe access su in another location?) but i still seeing how?
PD: sorry for my possible bad english speaking
PD2: yes i'm a noob and i hate myself but please some of you that know of this, help us?
Edit: just curious i just push su to "/data/local/tmp" then i just tipe ./su and it appeared on the phone "shell has been granted superuser permissions"
Alcatel_OT_909a /909s /910
OS: Android Gingerbread 2.3.4 / 6180
Kernel: 2.6.35.7-perf [email protected] #3
Here an idea: Custom Rom
hey guys, if some of you (someone, anyone who might wanna help?) are still maybe reading this thread, i wonder, i have played with the phone a little (unluckly i really messed up breaking the cellphone and luckily for me, the motherboard was replaced at service center), and i have been able to pull out most of the system partition, custpack and others, (except for the recovery partition) and i was wondering if maybe there is a way to create a custom rom with those files?, maybe we could create our custom rom and flash it, after seeing around the files, i got that 909a it's using what it's looks like at least the same kernel than ot910, (actually some information is from the ot910, in the manual it refers to ot909a-s ot910 as same cellphone but with different px in camera), so maybe we could create a custom GB rom based on the files from the stock system partition, and as alcatel has relased the kernel sourcecode maybe we could even do a custom kernel?, i was just wondering if someone can try to do a custom rom with those files, as i have tried flashing some GB roms replacing files and the phone doesn't boot up to android, but in recovery you get su access and pull the other files, but when replacing files, there is a moment when the system lose adb shell access, so maybe someone with more knowleadge (as i'm new to both android and linux) can help?
Rooting -- any news?
Has anyone succeeded in rooting the device in the meantime? I had no luck with either psneuter, zergrush, or gingerbreak ...
OT-910 successfully rooted!
Hi,
thank's to the great work of giantpune over at Phandroid, the Alcatel OT-910 has been successfully rooted (see the attached screenshot)!
For instructions, cf. the thread "Optimus Elite root with an apk" at Phandroid's LG Optimus Elite forum. Put in a nutshell, you have to install the following two APK's:
1. the Poot-debug.apk tailor-made for this phone, and
2. Ministro II.apk.
Both files are linked at the end of giantpune's original post at the LG Optimus Elite forum.
Note that Superuser, but not SuperSU, will grant root access on the OT-910.
Have fun!
Any Rom for OT 910
nolda said:
Hi,
thank's to the great work of giantpune over at Phandroid, the Alcatel OT-910 has been successfully rooted (see the attached screenshot)!
For instructions, cf. the thread "Optimus Elite root with an apk" at Phandroid's LG Optimus Elite forum. Put in a nutshell, you have to install the following two APK's:
1. the Poot-debug.apk tailor-made for this phone, and
2. Ministro II.apk.
Both files are linked at the end of giantpune's original post at the LG Optimus Elite forum.
Note that Superuser, but not SuperSU, will grant root access on the OT-910.
Have fun!
Click to expand...
Click to collapse
Can you please suggest any ROM for OT 910.
Help need...
Hi guys,
I need your help man, I had just rooted successfully and I don't know what have I done now it is just stuck at TCL logo and restarting.
please please please help...
May be flashing it solve the problem I have sent email to alcatel but they didn't have the rom so some one help me and also I had flash recovery but didn't back up original one so also give me that or any working CWM recovery.
plzzzzzzzzzzzzzzzz
my last hope is xda...
smkamranqadri said:
Hi guys,
I need your help man, I had just rooted successfully and I don't know what have I done now it is just stuck at TCL logo and restarting.
please please please help...
May be flashing it solve the problem I have sent email to alcatel but they didn't have the rom so some one help me and also I had flash recovery but didn't back up original one so also give me that or any working CWM recovery.
plzzzzzzzzzzzzzzzz
my last hope is xda...
Click to expand...
Click to collapse
If your last hope is xda... then maybe you will not have that much luck, if you're stuck at TCL logo, maybe you could try using the "OTU Upgrade Tool" (by means "OTU = Alcatel/TCL Flasher") and maybe that will do the trick and then you get your phone back to stock, if not (or if you already did that), then you're a little out of luck, as far as I know, there is no stock recovery around, and also as far as I know, there is no CWM recovery, now, in case you did use OTU Tool, and failed flashing the phone, then is almost sure that your nand is bricked, if you used OTU Tool and that didn't get your phone back, then you should see if you can still flash Android Images (more accurately 2.3.3 (since 2.3.4 did brick my phone twice)), at least with a non-functional 2.3.3 image, maybe you could flash from there with OTU again, or try to modify 2.3.3 system to work with your phone, if nothing of that did result for you, then you're out of luck, because I'm almost sure that would mean that you are in a nand brick, and the only way to solve it, is sending it to Service Repair (at least for now)
now, for using OTU Upgrade Tool, you can download it from TCL/Alcatel website ( www2.alcatelonetouch.com/global-en/support/download.html ) in the download section, select your phone model, and from there download the OTU Upgrade Tool, after downloading, install it and follow the instructions for getting the phone in "Download Mode" (in OT910 = (pressing "Q" key with the phone totally off, and after pressing the "Q" key for 30sec. or a minute, then (still pressing the "Q" key) connect it to the pc and follow the onscreen steps (that means, choosing your mobile and getting in to look for the firmware and download it)
I have a kind of "backup" of the system (I mean, every file that is in /system) but sadly, it doesn't have the properly permissions set, and so, it gives also a boot loop (also I bricked my phone once again and for worse, when it was out of warranty), so if you still in warranty maybe you should send it to service :/
that's the sad of life when your mobile is not the one that is being developed by expert developers (not even a beginner one )
Hope you can fix your phone
thanks for help
thanks man you are my captain...
I recheck the upgrade tool it just say that you have latest software.
So if you have 2.3.3 then please give me that i will update it via adb shell as i can still access it as su.
smkamranqadri said:
thanks man you are my captain...
I recheck the upgrade tool it just say that you have latest software.
So if you have 2.3.3 then please give me that i will update it via adb shell as i can still access it as su.
Click to expand...
Click to collapse
I will, but before, what version of upgrade tool are you using? (mine has a kind of strange bug that the rom is never ever able to get the last update (as always download saying there is a new update (it's a fake but anyway)), that would be kind of a problem since maybe after you flash 2.3.3 the upgrade tool will state that you're still in latest firmware (even through upgrade tool is supposed to be a service tool, funny isn't?), anyway, since you have nothing to lose (since apparently you flashed a custom recovery that didn't work for you), but, there are this two things you should try before, first (and pretty much the must obvious one) if you have warranty (as long as you're in warranty and never tried to see what's inside the phone), and two, there is a little possibility that maybe you can access adb via the recovery you flashed, even, when the tcl logo appears, try to do "adb shell" or "adb devices", so maybe you can recover your phone without the need of flashing android 2.3.3.
now, if nothing of that worked, then there is nothing to loose, if you have the android sdk, from there you can download a 2.3.3 image, that will boot, but display nothing in the screen (still you can do adb shell with su, and try to properly install libraries maybe?), if not, then i'll check if I can do one system image for you, and see what it does
by the way, if somehow you can access adb , try to do "adb pull" and pull the " /system" partition
it's really sad that we can't (at least not me) figure out, how to use the files that the upgrade tool uses ( 570mb of 10 - 520kb files)
Help me... alcatel 909
Azuruw said:
I will, but before, what version of upgrade tool are you using? (mine has a kind of strange bug that the rom is never ever able to get the last update (as always download saying there is a new update (it's a fake but anyway)), that would be kind of a problem since maybe after you flash 2.3.3 the upgrade tool will state that you're still in latest firmware (even through upgrade tool is supposed to be a service tool, funny isn't?), anyway, since you have nothing to lose (since apparently you flashed a custom recovery that didn't work for you), but, there are this two things you should try before, first (and pretty much the must obvious one) if you have warranty (as long as you're in warranty and never tried to see what's inside the phone), and two, there is a little possibility that maybe you can access adb via the recovery you flashed, even, when the tcl logo appears, try to do "adb shell" or "adb devices", so maybe you can recover your phone without the need of flashing android 2.3.3.
now, if nothing of that worked, then there is nothing to loose, if you have the android sdk, from there you can download a 2.3.3 image, that will boot, but display nothing in the screen (still you can do adb shell with su, and try to properly install libraries maybe?), if not, then i'll check if I can do one system image for you, and see what it does
by the way, if somehow you can access adb , try to do "adb pull" and pull the " /system" partition
it's really sad that we can't (at least not me) figure out, how to use the files that the upgrade tool uses ( 570mb of 10 - 520kb files)
Click to expand...
Click to collapse
First of all my update tool version is 1.2.0.10.
Second i got second hand set from local market at karachi, pakistan so no warranty where i exchange some email from alcatel support for rom but said that they didn't have.
third i can access adb shell with couple of reentering su i got super user so what to do to recover.
i will pull system partition and give you the link soon also downloading sdk for image.
thanks alot...
may we could chat live for better working. find me smkamranqadri at any platform except google kami.genius.
Got ROM/ RECOVERY
smkamranqadri said:
First of all my update tool version is 1.2.0.10.
Second i got second hand set from local market at karachi, pakistan so no warranty where i exchange some email from alcatel support for rom but said that they didn't have.
third i can access adb shell with couple of reentering su i got super user so what to do to recover.
i will pull system partition and give you the link soon also downloading sdk for image.
thanks alot...
may we could chat live for better working. find me smkamranqadri at any platform except google kami.genius.
Click to expand...
Click to collapse
I had got rom & recovery and every partions so any one need have do chat with me at fb - Muhammad Kamran qadri
Hi Guys,
Long-time listener, first-time caller..
I have a feeling I’ve broken my HTC One X+ [enrc2b] (UK Vodafone running CM10.2) due to a bad upgrade.
I had Cyanogen 10.2 installed and have been happily using and updating it via the built in CM update tool.
I went from stable to nightly a couple months ago and have never found any major issues so continued to use nightlies.
On Sunday (12th Jan) a new CM update was made available and I went through the usual process without really looking closely at the update. The update was for CM11. (Shouldn't matter? I've flashed new boot.img's before when required).
The update downloaded so the phone rebooted and went to flash, but failed halfway through due to a corrupt download.
I’m not sure if it was the file on the CM servers or if the download simply corrupted but I’ve never seen a similar issue and didn’t interrupt the update so I’m guessing it was a bad file uploaded for the update.
This is where it gets messy.
I had removed the previous update files so there are none available in the /cmupdate/ folder other than the CM11 version. If I had kept just one I wouldn't be in this situation (lesson learnt!).
My phone DOES NOT have USB debugging turned on, therefore I am not able to use ADB to push files to the device. Is there anyway to send files to the phone without using ADB. I'm pretty familiar with fastboot but can only flash recovery/boot using fastboot (?).
I’ve tried flashing the stock recovery so I can use the RUU for Vodafone UK but the RUU flsah fails. I’ve re-locked the bootloader and have the stock recovery but I get an error when using the RUU.
The RUU is v1.14 and my phone has v1.17 (from CM) so I suspect this is the problem as the version needs to be greater than the current?
The error from the RUU is related to the bootloader (error 140). I’ve tried a couple different versions of RUU such as a Europe one with v1.17 but it throws the wrong region code error when trying to flash.
I don’t have a nandriod back up. I thought I had done when I originally unlocked and rooted the phone. Turns out that it didn’t work.
I have downloaded a couple nandriods that I think would work but because I don’t have ADB working I can’t push the files to the device anyway.
I have CWM recovery installed again now, after the failed RUU update, and a version of hboot (that’ll check when I get home). I think it’s 1.400?
So, is my phone save-able, or is it now a paperweight. Any and all help appreciated.
A lot of the posts relating to fixing similar issues assume you have ADB/USB debug available, and I don’t! I have done a lot of reading over the past couple of days but am no closer to resolving this.
In case it helps, I can grab the zips from the RUU temp folder but wouldn't know how to flash them (does it need ADB?).
Can anyone help?
max3o6 said:
Hi Guys,
Long-time listener, first-time caller..
I have a feeling I’ve broken my HTC One X+ [enrc2b] (UK Vodafone running CM10.2) due to a bad upgrade.
I had Cyanogen 10.2 installed and have been happily using and updating it via the built in CM update tool.
I went from stable to nightly a couple months ago and have never found any major issues so continued to use nightlies.
On Sunday (12th Jan) a new CM update was made available and I went through the usual process without really looking closely at the update. The update was for CM11. (Shouldn't matter? I've flashed new boot.img's before when required).
The update downloaded so the phone rebooted and went to flash, but failed halfway through due to a corrupt download.
I’m not sure if it was the file on the CM servers or if the download simply corrupted but I’ve never seen a similar issue and didn’t interrupt the update so I’m guessing it was a bad file uploaded for the update.
This is where it gets messy.
I had removed the previous update files so there are none available in the /cmupdate/ folder other than the CM11 version. If I had kept just one I wouldn't be in this situation (lesson learnt!).
My phone DOES NOT have USB debugging turned on, therefore I am not able to use ADB to push files to the device. Is there anyway to send files to the phone without using ADB. I'm pretty familiar with fastboot but can only flash recovery/boot using fastboot (?).
I’ve tried flashing the stock recovery so I can use the RUU for Vodafone UK but the RUU flsah fails. I’ve re-locked the bootloader and have the stock recovery but I get an error when using the RUU.
The RUU is v1.14 and my phone has v1.17 (from CM) so I suspect this is the problem as the version needs to be greater than the current?
The error from the RUU is related to the bootloader (error 140). I’ve tried a couple different versions of RUU such as a Europe one with v1.17 but it throws the wrong region code error when trying to flash.
I don’t have a nandriod back up. I thought I had done when I originally unlocked and rooted the phone. Turns out that it didn’t work.
I have downloaded a couple nandriods that I think would work but because I don’t have ADB working I can’t push the files to the device anyway.
I have CWM recovery installed again now, after the failed RUU update, and a version of hboot (that’ll check when I get home). I think it’s 1.400?
So, is my phone save-able, or is it now a paperweight. Any and all help appreciated.
A lot of the posts relating to fixing similar issues assume you have ADB/USB debug available, and I don’t! I have done a lot of reading over the past couple of days but am no closer to resolving this.
In case it helps, I can grab the zips from the RUU temp folder but wouldn't know how to flash them (does it need ADB?).
Can anyone help?
Click to expand...
Click to collapse
the phone when on recovery doesn't need the USB debugging to be turned on....
if u had installed the proper drivers u will be able to see ur phone as on recovery.....
[email protected] said:
the phone when on recovery doesn't need the USB debugging to be turned on....
if u had installed the proper drivers u will be able to see ur phone as on recovery.....
Click to expand...
Click to collapse
Hmm, ok thanks. Maybe I need to reinstall ADB drivers. The HTC USB drivers work ok (fastboot usb is fine) and I do have ADB installed but having meddled with it (reinstalled ADB) I should try pushing again I guess.
Thanks, will try when when home! :good:
ADB without USB debugging turn on
Now sorted!
ADB works when the phone is in recovery, not in hboot. Dur.
Thanks!
hi still looking for help with my avoca android tablet. it doesnt boot up into android operating system just stuck on boot screen but can go into recovery mode with things like reboot now, update rkimage and so on.
i have tried to root it with an app called kingo root and says its rooted but i have tried to install a custom rom but nothing happens says aborted. is there anything i can do bare in mind i cannot access the tablet to turn usb debugging on and nothing else. if there is a thread here that will help and get things working again then id be really grateful or if someone can tell me what to do any help will be appreciated.
Well first off root will not allow you to flash a custom rom. You need an unlocked bootloader as well as a custom recovery. Your best bet would be find the stock image and flash that to get it running again and then take a week and do some reading and learn what your doing
I no what I'm doing I just can't find the things I need as the company no longer exist and I've searched hi and lo for a copy of their stock rom but nothing if I had that I no il be ok. But not sure how to unlock bootloader as I've used adb and fastboot but it don't work says waiting for device. Any pointers please
spampocket said:
I no what I'm doing I just can't find the things I need as the company no longer exist and I've searched hi and lo for a copy of their stock rom but nothing if I had that I no il be ok. But not sure how to unlock bootloader as I've used adb and fastboot but it don't work says waiting for device. Any pointers please
Click to expand...
Click to collapse
That is one of the biggest issues with cheap devices like this. You will most likely never find drivers or the stock rom for it. The best thing you might be able to pull off is porting a rom from a similar device.
Thanks yeah I think it's my only hope all I got to go by really is that this model of tablet uses jelly bean 4.2 as stock, so may see if can flash a stock rom from googles dev site as they have different model stock rims and just hope that one works. Il try nexus stock one first see if get lucky if not just work done the list. What do you recommend I do first shall I unlock bootloader first even though the command doesn't work in fastboot says device null or waiting when I type fastboot oem unlock. Or am I better starting off with a stock rom using adb? Also what recovery do you recommend I've used twrp and clockwork. Thanks
I'm trying to side load twrp using adb and all I get is opening update package, verifying update package, then installation failed do you no what I'm doing wrong