Related
This is based on my experience with two UNis..one Exec and other JASJAR..both had same problem...this is how I solved :
-Put yr device in bootloader Mode
-Disable USB in Active Sync
-Now connect woth USB cable and open mtty utility
-Select the "WESUSB... " port
-You shall see a blank white screen..press Enter to get "USB>"
-Then type ( as BUzz has informed) set 14 0
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
-Then I ran the ROM Upgrade directly(After enbabling the USB)
-I then followed the procedure as informed on the COngratulations Screen that is hold the two "-" buttons and soft reset and then pressed 0
-I got them back to normal..
I hope this helps to all my friends...Pls feel free..pls do not trouble our Buzz..he might be busy in inventing something more to our devices
could you please clarify this statement
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
in particular the bit "for two three times"
ta
I meant that after typing set 14 0 did not help so in frsutration I thoight of typing something more like set 14 10, set 14 9 set 14 20 also...then I did the flashing again...I got the success...
my msn : [email protected] pls add me...I am normally on line 07.30 to 09.30 IST and 22.00 onwards IST(Indian Std Time).I can help u out
great info. I suggest the following as well:
- If after upgrading and reset, still see Serial 1.0, UpGRADE THE RADIO, and reset again (for mor info search for "MDA PRO is alive"). It will work.
- And, as Dherrero said to me, Dont' worry! there is almost always a solution for your problem (99%).
Same problem, still can't get Jasjar working
Hi -
My Jasjar is now sitting endlessly at the blue imate boot screen, showing the new ROM version numbers. Help!
I've tried "hdubli"s suggestions, but to no avail (although i still have no idea what "set 14 0" was meant to do, or what i was meant to see on screen afterwards!) I also tried "set 14 10", "set 14 9", "set 14 20"...
I've tried reflashing down to the older ROM version, then back to the latest ROM(several times now).
I've tried the following update: http://forum.xda-developers.com/viewtopic.php?t=42992&highlight=bootloader
I'm re-applying the imate official rom now, as i don't know what the above version one is.
But it's still hanging at the blue startup screen...
- It seems to be ROM version independent
- what else is there that i can flash? could the bootloader be corrupt or something?
- iMate online support walked me through reapplying from bootloader, and removing the battery, but that was all they could offer. THen referred me to a 'local service agent'.... but that could take days...
Can anyone help?
/Mark
Re: Same problem, still can't get Jasjar working
mcackay said:
Hi -
My Jasjar is now sitting endlessly at the blue imate boot screen, showing the new ROM version numbers. Help!
I've tried "hdubli"s suggestions, but to no avail (although i still have no idea what "set 14 0" was meant to do, or what i was meant to see on screen afterwards!) I also tried "set 14 10", "set 14 9", "set 14 20"...
I've tried reflashing down to the older ROM version, then back to the latest ROM(several times now).
I've tried the following update: http://forum.xda-developers.com/viewtopic.php?t=42992&highlight=bootloader
I'm re-applying the imate official rom now, as i don't know what the above version one is.
But it's still hanging at the blue startup screen...
- It seems to be ROM version independent
- what else is there that i can flash? could the bootloader be corrupt or something?
- iMate online support walked me through reapplying from bootloader, and removing the battery, but that was all they could offer. THen referred me to a 'local service agent'.... but that could take days...
Can anyone help?
/Mark
Click to expand...
Click to collapse
Hi all,
I have been following almost every thread of this forum for the past week or so, && this is the first time i have come across another person who is suffering from the same problem... Hi Mcackay... I have the EXACT same problem... I have been given some suggestions which i shall try soon... If anything atall works i shall let you know bro... && please inform me if you find any solution...
mOrph
May be this will help further
If one has tried to update Atom/Wizard ROm...will certainly notice that the upgrade process doesn't start unless the battery is >50%..so this is the biggest clue.
Those who want to upgrade make sure that their battery is more than 50%..no one will face the problem.
So those huys who are already in problems...shd try to get their friend's battery which is fully charged and then do the ROM Update..
This will certainly solve their problems.
I installed the new ROM but every time it just said 'congratulations all done etc.....' and I could not get out of bootloader mode.
I did a hard reset to get the white screen and then had the choice of X or 0, but both put me back at the grey screen (where it is just possible to read USB and serial 1.0).
After doing this 5 or 6 times, I found the old radio 1.06 upgrade and ran that, and on completion it allowed the universal to start up AND the ROM files that I had sucessfully installed (see above) were there.
Only problem is I now have 1.06 radio and not 1.09, but i can do an upgrade for just that later.
steve
i cannot make it start i have tried to write in mtty set 14 0 , set 14 9, set 14 20 but nothing.also i ave triedto install almost all rom but everytime stucks in the blue i mate image,any ideas please???
angeln20 said:
i cannot make it start i have tried to write in mtty set 14 0 , set 14 9, set 14 20 but nothing.also i ave triedto install almost all rom but everytime stucks in the blue i mate image,any ideas please???
Click to expand...
Click to collapse
Hi buddy... Am facing the same problem for the past 15 days... My JASJAR has been stuck on the blue imate splashscreen mode... I too have tried flashing the device with all possible ROMS but to no use... One thing that we can conclude is that the problem is ROM independent... Lets work on this together.. There are other 2-3 people on this forum who are facing this same problem... Lets put our heads together && work out a solution... If there is any success at my end, i will update you asap.. PLEASE do the same...
Regards,
mOrph
Almost the same problem I have
Almost the same problem I have with MDA Compact II Now the device is dead the screen blinks. somebody told me that there is a software that works on dos mode and reset all to bring it boot loader & and so there is a bottun inside the device to to clear every thing. But I don't know how???
I also have the same problem stuck on 2nd splash screen
This all started when I used the official imate Jasjar ROM upgrade from the clubimate site (since I have an imate Jasjar). I've come a long way in understanding how to manually upgrade the ROM and have tried numerous ROMs, radios, etc. and still won't go past the splash screen. I'm hoping I we can figure it out today.
no luck yet.i cannot to something and i am afraid that the battery will empty.....
I'm hopefull - I'm online with imate support
I keep on getting disonnected from their support, but so far they said "its just and error but i will help you to fix it so please me the IMEI number" so I gave him my IMEI number and he's supposed to email me the fix. We'll see ..... I'm keeping my fingers crossed.
morphosin said:
angeln20 said:
i cannot make it start i have tried to write in mtty set 14 0 , set 14 9, set 14 20 but nothing.also i ave triedto install almost all rom but everytime stucks in the blue i mate image,any ideas please???
Click to expand...
Click to collapse
Hi buddy... Am facing the same problem for the past 15 days... My JASJAR has been stuck on the blue imate splashscreen mode... I too have tried flashing the device with all possible ROMS but to no use... One thing that we can conclude is that the problem is ROM independent... Lets work on this together.. There are other 2-3 people on this forum who are facing this same problem... Lets put our heads together && work out a solution... If there is any success at my end, i will update you asap.. PLEASE do the same...
Regards,
mOrph
Click to expand...
Click to collapse
i agree this, i also got problem with my exec,
some of thread told us use mtty set 14 0, or just falsh single rom such llike radio rom or nk.nbf, tied many time, tried may ways of reset, boot options, other version and kinds of roms, still no work for me,
I did solve the problem with 3 Unis by what I hv explained above...I think it is Flash Chip related issue...after upgrade it is just not getting a kind of trigger to load the OS..This time I am really struggling with morphosin's JASJAR...it is lying at my place for past 2 days...but no luck so far.
I hv also tried following mtty commands and the results are as explained
task 28
DOC_format failed
task 0
task 7 0/1
made the Uni hang...it did not lock/unlock the ROM
rtask 0/1/3/4
In all these cases it did reset the radio...also had the Radio ROM run but still no effect on booting
May be buzz can help now as increasing number of people are getting this
problem..
I also think of some kind of Super CID in new ROMs which need to be unlocked before doing the upgrade..
@hdubli
thanks but many of my friends are helped by your post,too.
Also one of my friend, receovered by useing command with PlatformBuilder from PC, he reported me like that.
Asukal said:
@hdubli
thanks but many of my friends are helped by your post,too.
Also one of my friend, receovered by useing command with PlatformBuilder from PC, he reported me like that.
Click to expand...
Click to collapse
Hi Asukal...
Can you please elaborate the "platform builder recovery method"... I think thats the only thing left to do now...
Thanks...
FYI ... still working with imate technical support
I've made some progress with imate technical support, but still no solution. So far it's the standard bootloader - USB - Load the ROM response. I'm hoping they'll email me back today with a real answer. I'll keep you all posted.
hdubli said:
This is based on my experience with two UNis..one Exec and other JASJAR..both had same problem...this is how I solved :
-Put yr device in bootloader Mode
-Disable USB in Active Sync
-Now connect woth USB cable and open mtty utility
-Select the "WESUSB... " port
-You shall see a blank white screen..press Enter to get "USB>"
-Then type ( as BUzz has informed) set 14 0
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
-Then I ran the ROM Upgrade directly(After enbabling the USB)
-I then followed the procedure as informed on the COngratulations Screen that is hold the two "-" buttons and soft reset and then pressed 0
-I got them back to normal..
I hope this helps to all my friends...Pls feel free..pls do not trouble our Buzz..he might be busy in inventing something more to our devices
Click to expand...
Click to collapse
I also have been stuck in bootloader mode for days, but by following the above it sorts it every time.
I am using mtty v1.42 and simply select USB get the USB> prompt then type SET 14 0 then return. I then see HTCUSB> and close the program
I then cold boot and I am back in business. This is 100% repaeatable
Hope this helps
Stu
Hi XDA geeks , pros and fans !
I'd like to start this new threadline concerning the freshly-appeared TCT MOVE handheld device marketed for the budget segment.As i understand it appeared in march or later this year and has quite good specs for the approx. 100 euro category.
Some details can be found on
http://alcatelonetouch.com/products/smartphones/move
Contrarily to some beliefs IT IS NOT a branded OT-908 ,rather a cosmetized one .It comes in black or silver / white , a bit heavy for it's size , and higher specs than the OT-908.
Concerning the hardware specs, i'll be coming back later with some accurate chipset and sensor details.For now
OS is Android Froyo v2.2.2.Looks like there will be official ROM updates,at the time being there is the OneTouch Upgrade v1.2 ,which downloads about 540 Mb chunked firmware files, and exits with error.
Memory is 512 Mb RAM , for user space is available about 300 Mb
512 Mb ROM flash, available to user about 160Mb.
SD card slot supports up to 32Gb MicroSD, the phone comes with a 2Gb one.
Camera is a 2.1Mpixel one.There is no secondary one,but the main camera is available for video calls,with Yahoo! Messenger i tested it myself.How to use it this way i will explain later.
GPS is amazing , if assistance software is used , the lock-on takes only seconds.
Sensors - linear acceleration sensor
- 3 axis orientation sensor
- 3 channel magnetic field sensor (digital compass)
- light sensor for illuminance detection
- optical proximity sensor , it seems not in use by operating system(or rather poorly)
Processor - 600 MHz Qualcomm ARMv6 compatible, min frequency is 122 Mhz, and deep sleep capability.Qualcomm MSM 7627 chipset
rooting ?
hi djada80.i should like to ask if you managed to root your phone ?
Yeah , it's quite simple.There are in the Android Market some free apps , i think the best which i also use is the one named Ginger Break.Just download and install it.Detailed usage info can be found here
http://forum.xda-developers.com/showthread.php?t=1044765
firmware upgrade
it seems that the branded ones somehow cannot be upgraded ! at this point i need assistance , so PLEASE , if there is anybody experienced in debranding Acatel smartphones, then YOU ARE MOST WELCOME !.I saw guys having problem with debranding T-Mobile Move , so let's DO IT !
cannot sync with windows
i cannot sync my tmobile move with windows.have a toshiba satellite c665 with win 7 .pls help !
connect phone to computer,enable usb tethering.install alcatel android manager on computer. Can be found here
alcatelonetouch.com/contents/download/T-Mobile_AndroidManager_2.2.1108.1645.rar
This should work,instead of Android Sync Manager WiFi ,the last has some issues with this phone ,do not use it.
Yahoo! messenger front camera
Contrarily to some beliefs THERE IS POSSIBLE TO MAKE VIDEO CALLS with front camera only on Froyo 2.2.It is quite simple:
1.) if you have any version of yahoo apps , remove them all
2.) install Y!Messenger v1.3.2 , the afferent audio and video plugin and
optionally Y!Mail v1.3.2
Nothing fancy with it , just works.Remember, DO NOT UPDATE from Market.
Might also check this,if it doesn't work
http://forum.xda-developers.com/showthread.php?t=1087769
remove bundled apps ?
Hi !
Is there a way to remove some of the unnecessary factory shipped apps ?
RE
Yes , there is. So the smart method vould be to remove them from phone memory , and eventually install it on SD Card , if they are (and they are) UNMOVABLE.
Or just leave them ,anyway a factory reset will restore all the shipped applications.
1.) [optional] install Android SDK with platform 2.2 , sdk tools and eventually drivers.Enable USB debugging on device.On PC launch command prompt and change directory to \Android\android-sdk\platform-tools\.Run command
adb shell pm setInstallLocation 2
This enables SDCARD installation by default.Prerequisits to have ROOT ACCESS.
2.) with RootExplorer simply delete unwanted applications from \custpack\apps\ on device.Optionally you can make backups.
3.) if you made backups , the backed-up apk can be used to be reinstalled , NOW ON SD CARD
Good luck.
RE again
A reboot of the device is required to cleanup the junk after a forced delete.Or it can be done manually , BUT USE CAUTION.
i have an alcatel move branded Cosmote Move, i like this phone very much but i`ve managed to brick it the second time, first time i bricked and took it to waranty, they reinstall the software free of charge, now it has the same simptoms (pass the carrier logo and get stuck to carrier animation) and i need to send it to waranty again. i dont manage to get it unbricked. i`ve root it with gingerbreak but this phone doesnt go to recovery mode. i`ve searched the internet and google it for hours, but nothing.
if anyone knows how to do it please tell me, in the user manual says hard reset vol - and power, get stuck whit touch buttons light up and screen black!!
thanks in advance
re Themaster
it's not a brick yet i suppose , though you didn't specify how you managed to "brick" your phone.a nice clean reflash would solve the problem , probably you deleted some system files while in root mode.again did you use root explorer or something similar ?
try a factory reset as it follows:
1.) turn off the phone
2.) press vol up and the power on and hold the buttons pressed for about 1 minute
3.) the phone boots up , android logo appears and then an animation with some sort of thrashcan or whatever
4.)wait until it finishes , then the phone shuts down automatically.power on the phone and it will be restored
Beware ,battery must be at least 70 % charged or kept in charger , NOT USB connected to PC.
This restores phone to factory state , but not all the applications from /custpack/apps
Best regards !
Useful Key Combinations
These keypress modes apply on a shut down phone
Hard Reset - reinstalls android core system from ROM , deletes user data and misconfig
key combo : vol up + power on long pressed until trashcan animation appears
Flash Mode - used for ROM update , useless momentarily
key combo: vol down + power on long pressed , black screen appears and touch buttons lit up
Root access , mount filesystem with root access ,DANGEROUS !
key combo : home + power on long pressed until boot
build environment under Ubuntu
Lately, there has been some problems setting up an Android build environment under Lucid Lynx, as i've seen many have been complained for the missing java5 jdk.
For Romanian users: seems to be a problem with the Romtelecom DNS servers , when adding Jaunty or Dapper repositories to Lucid.
Use Google DNS as alternatives 8.8.8.8 and 8.8.4.4.This works.
From what I've been able to determine. The move and 908(s) are the same hardware with with only cosmetic differences. Something is different in software, I've been unable to root my 908s with ANY tools I've found.
I was also unable to use ADB under windows. The handset apparently requires four drivers, I was only able to find three of them. I got the Alcatel tools to work, as well as tethering, but no ADB. i didn't have any such issues under Ubuntu, but without root it isn't helpful.
I could not locate a stock rom or source anywhere on the Alcatel sites, so I sent a GPL request, i'm waiting to hear back.
UPDATE
After a long night I managed to root my 908s. I'll write out the jist of it, but I was flying by the seat of my pants, fueled by caffeine and sleep depervation. DON'T consider this a HOWTO.
First off, to the best of my knowlage there is no one click solution as of yet. As I said before still missing the driver that makes ADB work in windows, and handset based solutions didn't pan out. A little reasearch showed that the OT-990 has the same chip/ram and ROM space as ours. The screen is bigger, and I don't know what board is in it, but on a hunch I figured it was close enough. So I went here: http://forum.xda-developers.com/showthread.php?t=1164391 in the hopes that some sort of combined effort in future ROM development would be possible.
Yes that's right folks its a guide to MANUALLY root you handset with ADB. So not for the faint of heart. I didn't have high hopes, as issuing ls -l on either the sqlite folder or data threw a permission denied. So blindly I tried to push psneuter, busybox and su to /data/local. I almost fell off my chair when it worked! from there I used psneuter to get ADB into root, and managed to get the su binary to /system/xbin, and Superuser into /system/app. Superuser was installed, but still no root. So I checked out Root Checker to see what was going on. There are three places that su typically lives; /system/xbin, /system/bin, and /sbin. So I tried to put su in those folders. I got it into /system/bin but sbin is mounted read-only. I did not remount any directories, as the instructions are lacking syntax (I'm a little rusty with advanced mounting commands). I think things are mapped a little differently anyway. I still did not have root on the handset, so I then fired up Superuser to see what it could see. It saw the su binary, even though it wasn't working right. Then I thought well if it can see it, then maybe it can update and fix it. Sure enough after running the update to su in Superuser, (drumroll please...) I had working root.
So that's my story so far, I'm gonna give Alcatel a week or so to reply to my request. Then we'll take it from there. (Hey it worked on Huewei right?)
If a real dev should come across this, feel free to jump in. Its a solid little phone and has the potential to work on a range of handsets.
Gratitude
Thanks snkiz for your attention ! I am pleased that someone 'heavy' noticed my efforts of dedicating this threadline to the newcomer ! Indeed a small little phone with potential , maybe in time we get it gingerbread , cupcake ( or whatever ),even wm6.5 or 7 ...
As of ADB drivers , i had ADB from the first by these steps:
1.) http://www.alcatelonetouch.com/contents/download/move upgrade 1.2 Setup.rar , package contains the drivers
Now i noticed that when i try firmware upgrade , the utility downloads about half a giga of *.bin files and then exits with 'download failed error'.
2.) installed Android SDK , platform tools and Google drivers (i am not sure if necessary), the 2.2 platform (api 8)
Under Win7 cmd in platform tools , adb shell , su and on device pops up 'unknown has been granted superuser rights' and voila! in cmd shell i have '#'.Previously installed Gingerbreak.
My device is a Cosmote Move.
Ya, no I got that file too. I think they are "consumer drivers" because like I said I got all the Alcatel tools running but on my win 7 one driver was still missing, and I have pretty good googlefu. effin hate windows, this is why. I'm by no means a "heavy" but I am comfortable in a Linux environment, that helps alot. As to you being able to get gingerbreak to work, i'd bet that comes down to carrier firmware.
---------- Post added at 06:53 PM ---------- Previous post was at 06:39 PM ----------
djada, seeing as your the op could you please re-tag the thread with the model numbers to make it easier to find? cosmote, 908, 908s, and qualcom should do.
perhaps a mod could move this thread to the android hacking forum where it can get the proper attention please?
ADB driver
Driver files are from WHATEVER.\android-sdk\extras\google\usb_driver\ , if does not install automatically , can be forced.Anyway Win$ux 7 detects ADB interface , installs some sh.t from windows update server , and you'll have an ADB interface in Device Manager (working or not).Try to force the google drivers.
On the other hand ,i'm sorry but dunno how to move the thread , maybe i should start a new one in
http://forum.xda-developers.com/forumdisplay.php?f=565&order=desc&page=552
Just looked at it and they don't have Alcatel
Mod
Just started workin on a Cyanogen build , if i manage to build at least a kernal img , maybe i can lure in the Koush guy from github.We are in need of flash , backup , recovery tools.Not as lucky as the Samsung or HTC guys ...
Hey Guys Let me start from the beginning: I got my tablet a year ago and about 5 months ago. (so its out of warranty) anyways about 8 months ago i had to send it in for a broken back camera. after a month they sent me back a new tablet and i was happy. after it came out of warranty i decided to go and root my tablet. that went fine with no problems. i wanted to see what else i could do with my tablet and i found unlocking it would open up the world of custom rom's. intrigued i looked it up and decided to unlock my tablet. after downloading the unlocker i tried to unlock it and it wouldn't unlock. after looking around at possible solutions i found out that my device had an unknown serial number. I tried using ratchet to fix it but it kept giving me the error of "device not found". when type adb devices it shows up there as connected but when i try to push the file its not. ive read it might be caused because my system directory dosen't have write permissions. any help would be greatly appreciated.
Asus transformer Prime
Android 4.1.1
kernel:3.1.10-00004-gc770ddc
Build:JRO03C.US_epad-10.4.2.17-20121018
ADB
Have you added your VID to your adb_usb.ini? This should be in the %HOME%\..android directory. My example:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x071b
0x0e79
0x18d1
0x2207
Note, ignore the first line. I.E. for VID_18D1, I added 0x18d1.
bnborg said:
Have you added your VID to your adb_usb.ini? This should be in the %HOME%\..android directory. My example:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x071b
0x0e79
0x18d1
0x2207
Note, ignore the first line. I.E. for VID_18D1, I added 0x18d1.
Click to expand...
Click to collapse
could you please explain step-by-step on how to do that im a novice at this stuff and i dont know what im doing.
I know that it was foolish of me to not fully research this set of commands I have copied the before and after of tit all from the command line. I was attempting to mess around with my phone with QPST. I know, I can REALLY REALLY make things hideous if I don't tread carefully with QPST, but I am willing to take the risk in order to learn, even if I do get burned because my phone bursts into flames.
Any who here is the output from my commandline which I ran because using *#0808# and switching to either RNDIS+DM+MODEM or DM+MODEM+ADB didn't make my phone visible for QPST. And I also tried while in recovery, download mode, and all the other settings in the *#0808# menu, plus variations of the menu and then booting into recovery, normal boot, and download mode. All to no avail, then in frustration I tried the following and it's gotten to the point I can't see my phone via adb anymore. So could someone please give me the undo set of commands for typing into my phones terminal as I can't type them via my computer due to adb not seeing it anymore? Thanks
C:\Users\xxxxx>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\xxxxx>adb shell
$ echo MODEM USB > /sys/class/sec/switch/usb_sel
echo MODEM USB > /sys/class/sec/switch/usb_sel
cannot create /sys/class/sec/switch/usb_sel: permission denied
$ su
su
# echo MODEM USB > /sys/class/sec/switch/usb_sel
C:\Users\xxxxx>adb shell
error: device not found
Oh!, and if anyone can explain either what the commands did or better yet where I can go read about such commands and what they do that would be great too. Thanks
Not sure how relevant this is or if it will help you but this man seems to be in kinda the same boat, why don't you take a look at this thread particularly post #2 http://forum.slimroms.net/topic/2008-broken-usbuart-path-causing-loss-of-adb/
Sent from my Nexus 7 2013 using Tapatalk
crazymonkey05 said:
Not sure how relevant this is or if it will help you but this man seems to be in kinda the same boat, why don't you take a look at this thread particularly post #2 http://forum.slimroms.net/topic/2008-broken-usbuart-path-causing-loss-of-adb/
Sent from my Nexus 7 2013 using Tapatalk
Click to expand...
Click to collapse
Thank you for the link I haven't tried anything based on the information yet, actually haven't read it all yet. Very complex stuff just lets me know how far I have to go. Odd thing is that I now for some reason have ADB working again. I did a factory reset recently and the other day I reinstalled/refreshed my computer. My computer was infected by a bunch of viruses and malware the phone was just sluggish and I had way more apps I wanted rid of than to keep. Anyway, I don't know if the virus on my system had anything to do with the malfunction or if it was the command I used but for now it is back to working.
I was working on a friends HTC Desire and was having a hell of a time getting fastboot commands to work. I got hboot USB working but when giving a command it would generate a "device connected toi USB has malfunctioned" also the USB ports would shut off untill reboot too intermittantly and even my wifi three or four days ago became disabled and I reset the adapter fine for 5mins then it went a level deeper and deeper till I reinstalled the driver. That being said it is more likely that it was the virus and or the person messing with my system that was causing all the grief. They even triggered email alerts on a couple of my accounts that passwords were input wrong 5 times in a row and that some security settings were being changed. Hopefully I have dealt with that if not I'll have to wait till they get bored. Sorry if that was a little off topic it sort of conencts to my recent problems.
Hello i have N7100 with Cyanogenmod 11
I want to autoboot my phone when he starts charging battery
Not working:
Apps like autoboot on charge
Something like this: yt watch?v=Zp9G6A6EFlA
sebeknr2 said:
Hello i have N7100 with Cyanogenmod 11
I want to autoboot my phone when he starts charging battery
Not working:
Apps like autoboot on charge
Something like this: yt watch?v=Zp9G6A6EFlA
Click to expand...
Click to collapse
what you are looking for in custom roms
it is a kind of bug in kernel (offline charging bug )
devs are doing their best to dispose of it:laugh::laugh:
any idea, i'm stiil lookung for solved to this: autoboot when charge
sebeknr2 said:
any idea, i'm still looking for solved to this: auto-boot when charge
Click to expand...
Click to collapse
@sebeknr2
i don't have an apk to do that , and i DON'T HAVE cm11 on my phone
but the most important thing I donot know your ability in modding
any way there is a solution , so if you insist you can try it on your risk only ( maybe your phone became unstable / or may be you will brick your phone)
with (totalcommander app or any root apk...) go to
system /bin
search for a file in *bin , such as lpm , or playlpm ....
back up it first ( copy it to other place or rename it ....)
then open it , and delete all the line in, then put this code
#!/system/bin/sh
/system/bin/reboot
save it ( Be sure to set the ownership and permissions the same as the old playlpm especially execute permission
then turn off your phone and try to plug in charger
at last i did not try this thing by my self ( because I don't interest to such as..)
so this guide maybe wrong And there is another easy way
I don't know
good luck