Related
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
Chapter 1: The Foolishness of the User
Hi, I have the korean version of the optimus one(KU3700). It was on gingerbread(2.3.4) stock. I was trying to root it by downgrading it. I entered "adb reboot recovery" and I'm stuck. I tried to reflash it by going to emergency mode with the button combinations using the KDZ updater with this
"csmg. lgmobile. com:9002/swdata/WEBSW/LGKU3700/AKTFBK/KU370040_00/KU370040_00.kdz"
and it worked without any errors but when it when it came up it was still on recovery mode. Is there any way I can change the phone mode to the regular mode
Chapter 2: Journey to Salvation
For anyone who has this korean optimus one, after days of searching, I've found a web site that gave me hints to solve the problem. I just needed a different kdz file and I got it here:
h t t p://sirospace.tistory.com/category/Android%E2%97%86
popped it in google translate because I'm Filipino and can't read korean.
Downloaded the froyo kdz and flashed. I hope this can help other people stupid enough to play with their phones by typing random commands without knowing what it does, like me, LOL...so happy, now it's time to root
Chapter 3: False Hope
OK so I have successfully unbricked and rooted my KU3700, now The problem I have is installing a custom recovery on this phone, none of the images I try work.
Recovery images I have tried are as follows:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
Every time it finishes and reboots, it gets stuck at the LG logo.
Chapter 4: Wisdom Within
Found the problem. The images above are for the P500.Even if the KU3700 hardware is similar to the P500, flashing firmwares made for the other model will result in errors. The same holds true for custom recoveries.
Chapter 5: The Plea to the Gods
I've contacted drellisdee and submitted the files needed for custom recovery creation for the KU3700.
Just waiting for the flash image now. Thank you everyone
Chapter 6: The Forgotten
It seems drellisdee is busy right now. I'm a windows user and knows nothing about programing. So if anybody can help I'm sure the KU3700 community would be greatful. I've attached the files I think are needed to make a custom recovery.
Chapter 7: Quest for the Custom Recovery
I got tired of waiting. So as a windows user with no experience in programming, I did a lot of copying and pasting, I managed to port clockwork mod using virtualbox following this website:
h t t p://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
So I have got a bootable and flashable custom recovery but nothing works yet. I still need to configure it according to the device.
I have uploaded the image and the build files. Please help me configure it and tell me what's wrong. I really don't know that I'm doing
PS: you can try flashing the custom recovery by doing "fastboot flash recovery /Path to/recovery.img and you can go to recovery by using android terminal and type "boot recovery". It will boot, but that's that LOL. Take out the battery to boot to normal mode.
Chapter 8: The Holy Grail
LOL, I found the answer again. I was so frustrated that I kept squishing the phone in recovery and found out that it was just a button configuration problem. A bit of research and I found out that I can toggle it by pressing volume up and volume down at the same time. WOOHOO!!! Custom Recovery at last
Chapter 9: Invasion of the ROMS
And here at last, the user is retired. But the adventure is far from over. It is foretold that the creation of the Custom Recovery will begin a new era. The key to open the gate has been found. So our hero will await the invasion of the ROMS<background music...> END
you can see at
tinhte.vn/threads/908874
Thank you for the reply but as I said, I can flash fine without errors it's getting back to regular mode I have a problem with. Rebooting and reflashing does not take me out of the recovery screen(it's just a opened box with an orange arrow and the android logo).
vidgen13 said:
Thank you for the reply but as I said, I can flash fine without errors it's getting back to regular mode I have a problem with. Rebooting and reflashing does not take me out of the recovery screen(it's just a opened box with an orange arrow and the android logo).
Click to expand...
Click to collapse
yes i see.but i'm newer android.i only send you link to fix
i hope have a pro android to fix your brick
This is just a shot in the dark because i didn't understand what you did entirely : have you used the combination to actually recover the stock rom after you flashed with KDZ ? (Home+VolDown+Power)
Yes already did. The computer can see the phone whenever I connect it except that I can't access adb. I may have to take this back to the store
vidgen13 said:
Yes already did. The computer can see the phone whenever I connect it except that I can't access adb. I may have to take this back to the store
Click to expand...
Click to collapse
Are you sure you flashed the right rom for your phone? There's an application that downloads the required rom for your phone according to your IMEI/SN, but i don't know if it works with the korean version.
Yes it's the KDZ file, unfortunately it's the only KDZ file out there for ku3700. Shouldn't have settled for this korean version
why you wanna downgrade the latest version?
Dude I have the same Korean edition as you.
Actually why you wanna downgrade the latest version.?
My phone had 2.2.2 and I did upgrade it into 2.3.4 I did it officially and I can tell you How to re-install 2.3.4 if you want.
asmOne said:
Dude I have the same Korean edition as you.
Actually why you wanna downgrade the latest version.?
My phone had 2.2.2 and I did upgrade it into 2.3.4 I did it officially and I can tell you How to re-install 2.3.4 if you want.
Click to expand...
Click to collapse
Thanks for the reply. I wanted to downgrade it to root it. And now I'm rooted. My only problem now is installing a custom recovery. I've already tried several custom recoveries:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
but I get stuck at the LG logo when it reboots. I think it's because it's for the p500. So if you have a custom recovery for the ku3700 please help
I dont get it ,p504,p505,p506 are versions of p500??? And why some of our roms work on those phones?? So by logic this stock work on p500???
Sent from my LG-P500 using XDA Premium App
vidgen13 said:
Thanks for the reply. I wanted to downgrade it to root it. And now I'm rooted. My only problem now is installing a custom recovery. I've already tried several custom recoveries:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
but I get stuck at the LG logo when it reboots. I think it's because it's for the p500. So if you have a custom recovery for the ku3700 please help
Click to expand...
Click to collapse
this method worked for my working KU3700 when I'm using my 1st KU3700 I also was struck as you and finely I realized there are No custom roms for Optimus one Korean edition (KU3700/SU370) and I had to connect my phone to an Octopus box (lg softwere box) via software box installed the official firmware. if this method not working you have to connect to a software box.
connect to the internet your PC and 1st install Driver and 2nd install the LG update tool. after installation connect your phone to computer and wait a five seconds for comport installation. after install your phone Run LG Update application.
it is connect to the server automatically indicating red line and after search for latest firmware.
if you can Update your phone it is shows Update butten.
Driver
http://www.4shared.com/file/C3BSNx9P/lgunitedmobiledriver_s4981man3.html
LG Update Tool
http://www.softpedia.com/get/Mobile-Phone-Tools/Others/LGMobile-Support-Tool.shtml
Thank you all for the quick answers, but I already have a rooted ku3700. All I need now is a working custom recovery. If someone has the same phone, please tell me which image is compatible
you can appear the emergency mood with android logo.
it means you have an Empty phone. your Os was been erased. You have to connect your phone to Octopus software box and box server has you original Os for your IMEI. this is the only solution. if you will able to solve this problem without a Software box please inform me. we can open a New Thread for Korean edition.
(ku3700/su370)
I already got out of the emergency mode without an octobus box. It's really simple, you just need to use a different kdz file. The hard part was looking for the kdz file. I have 3 kdz files. KU370017(froyo), KU370033(gingerbread-rootable), KU370040(latest one from LG, gingerbread-unable to root). Just flash with the KDZ updater. I'm on the second firmware because I can't root the latest firmware. To root it, I used super one click(latest version, use zerg rush option). Now I'm just waiting for a custom recovery from drellisdee so I can use custom roms. When I get it, I'll ask him if I can post it so we all can have uber phones LOL
Updated the thread. Can somebody help?
vidgen13 said:
Updated the thread. Can somebody help?
Click to expand...
Click to collapse
If you have flashed a working clockworkmod you can enter into clockworkmod via ROMManager (search in google play aka market). In ROMManager you have "reboot to recovery" option in case you want to go to recovery to flash something. Also you can try to flash from ROMManager a custom recovery (5.0.2.0 for oldBB or 5.0.2.7 for newBB), try to choose to phone model LGP500 oldBB, try and test if it's working. Wish you luck.
Thanks but I already have a working recovery. I just need some ROM makers now
vidgen13 said:
Thanks but I already have a working recovery. I just need some ROM makers now
Click to expand...
Click to collapse
Have you tried CM7.2? if your phone is very similar with Optimus One i doubt it isn't compatible with your phone.
If your phone use 2.6.35.10 or 2.6.35.14 kernel you can give a shot to try CM7.2 on your phone, but before try this make a backup first.
Check this thread Post Your CyanogenMod 7.2.0-RC1 Nightly Questions HERE!! for CM7 custom rom.
yep, it doesn't work. Is there a tutorial for building cyanogen for unsupported devices? All I can find are tutorials for supported devices. I've already got the source code from LG. The problem is just incorporating it in the cyanogen mod. I wish this phone had more users LOL
Just bought PAP 5044. Fantastic phone. Anyone have any ideas for rooting this phone, installing cwm???
Use Framaroot 1.6 (Boromir exploit) for rooting. It's pretty much "one click" stuff and works like a charm. Now, as for cwm, I still haven't found the solution. I just managed to boot to the stock recovery but none of the commands are working so no use there.
arsenique said:
Use Framaroot 1.6 ...stock recovery ...
Click to expand...
Click to collapse
Yeah framaroot works awesome. Stock recovery works too. Commands are little funny. Entering everything ith volume up, volume down is for down
Finally got CWM working. The procedure of installing is fairly simple but I had to browse through few czech and russian forums to get the recovery.img.
This procedure doesn't need PC at all. Everything is done on your phone. Just follow these few simple steps.
1. First of all, you should be rooted. If not, use Framaroot to do that (fairly simple to do and pretty much "one click" stuff)
2. Next, install MobileUncle MTK Tools (available here )
3. Now, download the attached recovery.img and transfer it to the root of your SD card.
4. Open MobileUncle and grant root permission if asked.
5. Once it is open, choose "recovery update" on the main screen.
6. You should be able to see your recovery.img first on the list. Below are some other recovery images found online but DO NOT chose those.
7. When tapped your recovery.img it will ask "use recovery file: recovery.img (5620Kb)?" - tap Yes.
8. Within seconds, it is flashed and it will ask if you want to reboot to recovery... choose Yes.
9. That's it. You have fully functional CWM
Now, if you want to backup your device in CWM please note that the backup folder may grow pretty large if you are using SD Ext (which is pretty much a must with this device) so make sure that you have enough space on your SD card before you perform backup.
P.S. browsing through the czech and russian forums, I've found couple of pretty functional ROMs (there are few MIUI ports and one Xperia C port). I'm going to test those in the next couple of days and if it works, I'll share it here.
Cheers.
Disclaimer: I am NOT a developer! I am NOT responsible if you brick your device or if anything goes wrong!
Any new custom roms for this device? Cant find anything out there about custom roms for this phone...
Puritanicall said:
Any new custom roms for this device? Cant find anything out there about custom roms for this phone...
Click to expand...
Click to collapse
Okay so i found this xperia ported miui rom for Prestigio 5044 and it works great . I would send a link but it's my first post here and I can't post outside links, just search google for "COLLECTION OF MIUI PORTED ROMS FOR VARIOUS DEVICES" and the first one should be it.
Then scroll down until you see prestigio 5044 and download.
I would like to know if anyone has got some other roms for this device.
unusualphone said:
Okay so i found this xperia ported miui rom for Prestigio 5044 and it works great . I would send a link but it's my first post here and I can't post outside links, just search google for "COLLECTION OF MIUI PORTED ROMS FOR VARIOUS DEVICES" and the first one should be it.
Then scroll down until you see prestigio 5044 and download.
I would like to know if anyone has got some other roms for this device.
Click to expand...
Click to collapse
Dont wanna risk with flashin' roms for now. I installed xPosed framework and changed everything i could
any custom rom for prestigio 5044 great phine
Sent from my PAP5044DUO using xda app-developers app
Check thread about Lava Iris 504q development, its a same phone..
Prestigio 5044DUO Development
Prestigio 5044DUO Development ( many roms )
androidpro.info/main/androidinsertion/prestigio5044/
pizzonia said:
Check thread about Lava Iris 504q development, its a same phone..
Click to expand...
Click to collapse
Too bad we can't flash their roms.. Prestigio done something to the bootloader so we can't boot their kernel properly. Probably by flashing Lava's uboot, we could do it. Effort oz for otg support that prestigio disabled
Sent from my PAP5044DUO using Tapatalk
Dear
Can you help me find original recovery image for Prestigio 5044 DUO? I would like to go back to original ROM but I can’t because I have CWM recovery instaled.
THX, BR
lolerpro8 said:
Too bad we can't flash their roms.. Prestigio done something to the bootloader so we can't boot their kernel properly. Probably by flashing Lava's uboot, we could do it. Effort oz for otg support that prestigio disabled
Sent from my PAP5044DUO using Tapatalk
Click to expand...
Click to collapse
hi to all,
i just fuond this thread and i hope that someone can help me.. Pleasee!
My first post and it's already a mess.
I explain my situation shortly:
I download framaroot and installed the boromir expansion, by the way everything until i made a mess. I deliberately deleted the browser that is a core application. The result is that the phone is blocked. I didn't done anything else. Now my pc won't recognize the phone, or to be more specific is still recognized but only in recovery mode, and activating "install from adb". The pc recognizes it like an htc dream.. Thanks to adb, i've tried to install the firmware version, in hoping to come back to the stock version and undo, but the installlation is completed but the phone still not workin.
When i turn on the device it starts with boot animation logos and then SOME it's not working and the phone is blocked.
Can someone save me?
thanks to all for reading me, and losing your time. I made a mess.
villo88 said:
hi to all,
i just fuond this thread and i hope that someone can help me.. Pleasee!
My first post and it's already a mess.
I explain my situation shortly:
I download framaroot and installed the boromir expansion, by the way everything until i made a mess. I deliberately deleted the browser that is a core application. The result is that the phone is blocked. I didn't done anything else. Now my pc won't recognize the phone, or to be more specific is still recognized but only in recovery mode, and activating "install from adb". The pc recognizes it like an htc dream.. Thanks to adb, i've tried to install the firmware version, in hoping to come back to the stock version and undo, but the installlation is completed but the phone still not workin.
When i turn on the device it starts with boot animation logos and then SOME it's not working and the phone is blocked.
Can someone save me?
thanks to all for reading me, and losing your time. I made a mess.
Click to expand...
Click to collapse
Flash custom recovery trough spft then flash some modified rom
lolerpro8 said:
Flash custom recovery trough spft then flash some modified rom
Click to expand...
Click to collapse
where i can find custom recovery and custom firmware?
can u please suggest me somenthing?
I also found driver so that spft can recognize my phone, but i don't know which one is correct and working properly.
By experience, the driver is called "mtk usb vcom port" or "usb preloader 65xx"???
Then i don't know how to use spft, it's my first time, and custom rom don't know what to choose
villo88 said:
where i can find custom recovery and custom firmware?
can u please suggest me somenthing?
I also found driver so that spft can recognize my phone, but i don't know which one is correct and working properly.
By experience, the driver is called "mtk usb vcom port" or "usb preloader 65xx"???
Then i don't know how to use spft, it's my first time, and custom rom don't know what to choose
Click to expand...
Click to collapse
Everything you need can be found here http://androidpro.info/main/androidinsertion/prestigio5044/ . To get to meta mode you need to compliantly turn off your device and connect it to the computer( with battery still inside)
lolerpro8 said:
Everything you need can be found here . To get to meta mode you need to compliantly turn off your device and connect it to the computer( with battery still inside)
Click to expand...
Click to collapse
I tried different version without flashing them, only by installing the zip, and i would like to install the last prestigio version, or a clean version with just root..
Is it possibile?
By the way everything seems to work with these custom roms, but not the phone itself, i have the broadband and imei, but it doesn't recognize the sim cards, to be more specific the IMSI number.
villo88 said:
I tried different version without flashing them, only by installing the zip, and i would like to install the last prestigio version, or a clean version with just root..
Is it possibile?
By the way everything seems to work with these custom roms, but not the phone itself, i have the broadband and imei, but it doesn't recognize the sim cards, to be more specific the IMSI number.
Click to expand...
Click to collapse
All the stock versions from the site are down. You need to get some othernrom. I prefer either miui or coloros. As for the other thing, if it doesnt work after flash its hardware related
lolerpro8 said:
All the stock versions from the site are down. You need to get some othernrom. I prefer either miui or coloros. As for the other thing, if it doesnt work after flash its hardware related
Click to expand...
Click to collapse
Yep indeed, infact i put again imei and now it's working, but the only thing i don't know which value to set in at for second sim. It's always hard! To me is a factory problem.
I've installed the bean version instead. It's working, i love it but i don't know exactly how to install\update xposed framework and gravity box tools. When u install, it magically appears on ur sd card a folder called "xposed disabled". It's still not working.
I would like to change columns in UI system.
villo88 said:
Yep indeed, infact i put again imei and now it's working, but the only thing i don't know which value to set in at for second sim. It's always hard! To me is a factory problem.
I've installed the bean version instead. It's working, i love it but i don't know exactly how to install\update xposed framework and gravity box tools. When u install, it magically appears on ur sd card a folder called "xposed disabled". It's still not working.
I would like to change columns in UI system.
Click to expand...
Click to collapse
Dude i cant help you with everything search before posting.
ASUS MeMO Pad 8 (K011) ME181C Recovery Guide
The following is a list of what we can currently do with this tablet. It assumes firmware versions with the WW prefix (WW-3.1.23.1xx).
Root Status: Obtained
Bootloader: Locked
CWM Recovery Possible: Yes (Tethered)
Custom ROMS: None
The following information is for recovering your tablet and obtaining root only. The bootloader is locked on the device at this time.
Tethered CWM recovery
This is a temporary solution to unsigned loading. The bootloader on the device is currently locked, so after rebooting, it will revert back to standard recovery. Use this to restore to a stock firmware or to install SuperSU.
Download the official firmware and extract it.
Rename UL-K011-WW-3.1.23.172-user.zip to user.zip.
Copy user.zip to the root of your SD card.
Enable USB debugging on your tablet.
Run Launcher.bat.
Type ACCEPT.
Choose option T3.
This will reboot in to the Tethered Recovery.
Choose Install Zip from external SD card.
Choose user.zip
Reboot once finished.
Bootable Image for Recovery
This file is to be used if your system will not get past the Asus or Intel logo. Boot the system using Volume Up and Power. Once the logo appears, let go of power. Once in DroidBoot, use fast boot to flash the boot and system images. This is provided in case signature verification fails on the official images.
fastboot flash system system.img
fastboot flash boot boot.img
This file also contains adb and fastboot. If your tablet is not detected, try the Asus drivers.
Reboot the system and use the CWM tethered recovery to reinstall the official firmware.
OTA Updates
If you’ve recovered from the official firmware on the Asus site, you’re probably sitting at version WW-3.1.23.172. Here are the OTA updates to bring your system up to the current version of WW-3.1.23.189. There are two different OTA updates available here, so the process will need to be completed twice. Update 172 to 183 and Update 183 to 189.
Boot in to recovery, press the volume keys several times and install from ADB.
Extract the RAR file and rename the files update.zip.
On your PC, open a command prompt and change to the directory containing the update file
Assuming ADB is installed on the system, type: adb sideload update.zip
Once the process completes, reboot your system and update apps as needed.
Repeat this process for any additional update files.
Recovery image
This is the default recovery for the tablet. If you get adventurous and try to flash another one, this may come in handy.
can you explain
RemmyLee said:
All thanks to vampirefo for his work on this.
FB Tethered Recovery Launcher
Kind of curious if this method will work with the other versions of the tablet to allow SuperSU to be installed. Anyone want to try it?
Long story short, I screwed this thing messing with the framework. For some reason, the official firmware from the Asus site was failing signature verification when trying to reinstall. Someone managed to grab a stripped system image that at least gave me a launcher and USB debugging. This beauty allowed me to get the firmware installed and everything back to normal, as well as installing SuperSU.
If you have any trouble getting the tablet to show up in Windows, the Asus distributed drivers work like a charm.
Click to expand...
Click to collapse
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
1. https://cloud.mail.ru/public/2b47381cb37c/ADB.rar - This contains adb and fastboot if you don't already have them installed. This also contains the system image that we're going to use temporarily to get this thing restored.
2. Hook it up to your computer and load up Fastboot on the tablet (Volume+ and Power while booting. Let go of power after the logo shows up).
3. Flash the System image ( fastboot flash system system.img) followed by the boot image (fastboot flash boot boot.img)
4. Reboot.
5. https://www.androidfilehost.com/?fid=95857557620392052 - Next, we're going to use a temp version of CWM-Recovery to reinstall firmware. Enable USB debugging, run launcher.bat, type "ACCEPT" and choose T3.
6. You'll auto reboot into CWM-Recovery. Grab the official firmware from the Asus site and install the zip from SD. Once complete, you'll need to reroot the device most likely. If you have a SuperSU zip, install it after you've restored the system.
You're done. This also opens us up for just about anything. Go play with your system. As long as you don't mess up your boot loader, this should save you.
Sent from my K011 using XDA Free mobile app
Asus MeMo Pad 8 - Pro 7 Entertainment Pad
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
OTA update 172 to 183
OTA update 183 to 189
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
shadow2483 said:
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
Click to expand...
Click to collapse
If you need any more help than whats above, let me know.
fulishone said:
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
Click to expand...
Click to collapse
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
RemmyLee said:
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
Click to expand...
Click to collapse
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
fulishone said:
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
Click to expand...
Click to collapse
Yep. That'll get you updated to the current firmware. I contacted ASUS yesterday and sadly, there are no plans on bringing Lollipop to this thing, nor are they interested in giving us an unlocked bootloader.
As for the Intel Tether, where the bootloader is locked, we can use a tethering method to access CWM recovery, but once we reboot, it reverts back to the standard recovery. This prevents us from using custom roms at this time. When it reboots, it checks signatures. The official firmware was not installing using the standard methods, so I used CWM to reinstall. That's why I included it above.
BBY builds
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
et1ssgmiller said:
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
Click to expand...
Click to collapse
I'm curious to know if the tethered method would allow a temporary CWM session to install SuperSU on the BBY line. I haven't seen anyone try it yet. If USB debugging is enabled, the tethered restore should try to automagically do everything for you. If you boot in to recovery, can you do a fastboot devices?
Can´t mount external sd card anymore
After using CWM tethered recovery to backup my rom, i cant mount my external sd card anymore. Any ideas?
Updates
RemmyLee said:
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
URLS removed to post
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
tperki said:
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
Click to expand...
Click to collapse
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Success
RemmyLee said:
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Click to expand...
Click to collapse
Yeah, strange that it won't update over the air. But thanks to your assistance I am running build 189. It may just be wishful thinking, but the device does seem a bit peppier. Thank you RemmyLee!!!!
[Update] Since updating to build 189, the device is much more stable and snappier. This was definitely worth doing. I don't understand why ASUS would not be pushing this out to everyone with this device.
Just wanna say thanks to the OP. Got my tablet back from the service center and was wondering why some apps were missing. Sure enough I was on WW...179. Nice to have updates and recoveries in one place. Great work!
Thank you so much bro, I have been googling a lot trying to find a root method and just discovered that I can easily have recovery and flash supersu zip thanks to you!!
Me181c not working...
Hi guys, I was using SoftKeyZ for about 2 weeks, I wanted to set my navigation buttons to it's default, so I tried using Backup of the SoftKeyZ, but when it rebooted the tablet, I lost my navigation buttons and indeed my notification and status bar. It rebooted again automatically, and this time when it started, I got an error which says: "Unfortunately, KeyguardTestActivity haas stopped", the error prevents me from unlocking the tablet and using it, so I cannot use it at all. I don't know how to go to recovery mode on my tablet, I used the button tips but it didn't work for me. I've downloaded the official rom from asus.com . Pleeeeeeeeeeeeeeeeeeeeeease, I need your help guys, you're my last chance...
should I do a complete wipe ?
Hi,
Thanks for the help in this thread.
I followed the instructions and successfully flashed the update firmware file. I was expecting for the tablet to be reset to original factory condition but found that all my apps ect were still there. I guess the user.zip is an update rather that a full ROM or should I have wiped everything first ?
I am have problems with the tablet such as Bluetooth has stopped working and wifi will only connect to very strong signal, (as in touching the router) which is why I wanted to completely wipe the device a start fresh.
f I wipe everything will the firmware file be able to restore the system fully?
Is there a complete firmware image file that can be downloaded any where ?
Thanks in advance for any advice
update : so fed up with no Bluetooth so I took the chance and did a full factory wipe and the system restored ok with the firmware file. Bluetooth problem solved, (Wifi did not, probably Hardware issue)
Thanks again
Signature failure
Thanks to your instructions, I've successfully managed to update my device to build WW-3.1.23.172, however, when trying to install 172 to 183 update I get a signature verification failure message.
Any ideas why this is happening?!
Hello!
First post here!
I just revived a Cubot Note S and am pretty happy with the performance.
I've searched around for a while and am unable to root the device, I've seen one other post on XDA regarding a successful Root on 5.1 but am unable to find any information on how this is achieved.
I've tried Kingo, King and Root Genius with USB Debugging an OEM Unlock enabled.
If someone could point me in the right direction, that would be great,
Thank you
Sorry, don't have any kind of solution but I just wanted to say I'm in the exact same boat as you. Been trying to root my Cubot for days.
Good News!
Aftee alot of digging and flashing several recoveries I have successfully rooted the Cubot Note S.
Ill put a simple guide here to help:
Its your responsibility what happens to your phone, Mine works flawlessly, but be careful out there!
Requirements:
Cubot note S on 5.1 Lollipop
Smart Phone Flash Tool & MTK Scatter file (for the cubot) & Super SU.zip
buzztechnica.com/2016/03/how-to-root-and-install-twrp-recovery.html?m=
In the first paragraph is a download link. Download the rar and extract it. All you need is the Smart Phone Flash tool and the MT scatter.txt. THE RECOVERY IN THIS DOES NOT WORK!
Modified TWRP recovery (there is omly one that works!
android-hilfe.de/thema/root-und-twrp-fuer-cubot-note-s.753414/page-2 << Post number 37 has the Mega link to the working recovery.img file
MTK VCOM drivers
spflashtool.com
Look for link that says "Download MediaTek VCOM Drivers" get the self installer package.
About recoveries,
Make sure you use the Modified one and not any other. The bundled one in the FlashTool and the other 3 floating in the internet do not work as they do not register touches. These are useless.
Okay, so now you have the files i would create a new folder with everything you need. So thats the Flash tool, scatter file and the modified TWRP recovery and phone drivers.
Before you start. Copy the SuperSU zip to your phone somewhere. Also enable USB Debugging in the developer options. Finally TURN OFF YOUR PHONE. i.e hold power, power off. Dont plug your phone into the computer yet
On your computer install the VCOM drivers first. Now to get the drivers installed I had to modify the batch file to work on Win10. If your on Win10. Right click the install batch file and edit. Remove all the lines regarding the OS check and save and run the installer. A command window will notify of the install success
open the Flash tool. Now, the second box asks you to select a scatter file. Select the one you have.
Ensure the dropdown box is selected to Dowload Only.
Ensure that ONLY recovery is ticked, you dont wanna flash anything else accidently!
To summarise... now, you should have super su.zip on your phone. Smart phone flash tool setup with the scatter file and custom recovery loaded. Your ready to flash!
Before plugging your phone in click Download. Now plug your phone in. And you will see it will flash. Should take a few seconds youll see a bar going along the screen. A box will pop up saying download OK!
Now, apparantly your phone is meant to boot without any assistance. Mine did not. So in this case. Unplug from PC. Remove phone battery. Put back in and tey to enter recovery (Pwr + Vol Up) <<< tip, dont hold them in too long as my phone just kept resetting. Hold about half a second while the screen is on then let go
You should now be in twrp recovery. Swipe the notification and proceed to flash the super su zip. Once complete, remove your battery and DONT press restart. It wont work and your phone will freeze.
Put your battery back in and boot normally, you now have custom recovery and Root!!
Enjoy!
Sorry about the links. Im new here. Modify the links and paste in browser
.... or you simply navigate to needrom.com and seek for "Cubot Note S". Then you'll find a working TWRP-recovery for Android 5.1 and even 6.0, a beta ROM for Marshmallow (6.0) and the not yet published ROM from 11-07/2016 for Lollipop (5.1). To flash with SP-Flash-Tool from your Computer.
Cheers!
frankonia said:
.... or you simply navigate to needrom.com and seek for "Cubot Note S". Then you'll find a working TWRP-recovery for Android 5.1 and even 6.0, a beta ROM for Marshmallow (6.0) and the not yet published ROM from 11-07/2016 for Lollipop (5.1). To flash with SP-Flash-Tool from your Computer.
Click to expand...
Click to collapse
I tried these, but as stated, all those Recorives did not work due to not recognising the touches. plus, the 5.1 stock ROM is stable, where as the 6.0 is still beta. I'd rather stick with a stable ROM.
6.0 ROM and the 6.0 TWRP may work, but its untested for me. hence why I've targeted 5.1 in my tut
Thanks for the detailed walk through Sparky. I may give it a go but I'm very new to all this so I don't want to get myself into something where I'm not really sure what I'm doing. Either way, thanks for the help
hiiiiYA said:
Thanks for the detailed walk through Sparky. I may give it a go but I'm very new to all this so I don't want to get myself into something where I'm not really sure what I'm doing. Either way, thanks for the help
Click to expand...
Click to collapse
No problem, Its actually quite straight forward once you've found the working files. At least now there is a tutorial on the internet for this phone which is complete and tested
moha u are awesome actually, how the hell did u find out that?
It took me days, i rooted with iroot - woorked, then it unrooted itself, did again, didnt work I Tried millions of different Recovery.img nothing.
Tried urs - works perfektly with 5.1. Does not with 6.0.
But thank u a lot <3 Edit 2: 6.0 works with the img of: http://www.needrom.com/download/cobot-note-s-6-0/
Hi, anyone with success on v.6 / Marshmallow ?
SparkyTheAlbino said:
Hello!
First post here!
I just revived a Cubot Note S and am pretty happy with the performance.
I've searched around for a while and am unable to root the device, I've seen one other post on XDA regarding a successful Root on 5.1 but am unable to find any information on how this is achieved.
I've tried Kingo, King and Root Genius with USB Debugging an OEM Unlock enabled.
If someone could point me in the right direction, that would be great,
Thank you
Click to expand...
Click to collapse
Kingroot works