Hello,
some of us who have bought a Hero locked to Orange can't seem to get it unlocked (http://forum.xda-developers.com/showthread.php?t=555424).
For those have you who have managed to successfully unlock an Hero on Orange please can you advise on your experience- did you have to do something differently? And who you used to get the code? I have used Unlock Now (www.unlock-now.com) but the code they have supplied didn't work (they refunded me).
I have never had a problem unlocking a HTC phone until now and I find it hard to believe that Orange Heros can't be unlocked.
Please help if you can.
*********************************************************
[Update 16/10/09]
I am glad this thread has been of use to people.
I thought I would add and update to the first page so people don't have to wade through the whole thread.
If you are experiencing this issue you have two choices:
1)CID unlock your Hero (http://forum.xda-developers.com/showthread.php?t=559806).
2)Use a Rebel II Sim.
OK there are three choices.
3) Use your Hero on an Orange contract for about three months then ring up Orange and ask them for a unlock code. They will charge about £20 for it and you may have to wait up to two weeks for em to send it.
C'est tout.
*********************************************************
[Update 24/10/09]
OK, after discussions and PM's on this thread I was advised to use the code I had previously bought with a different rom (when I first got my Hero tried it I was using the Orange stock rom then Modacos 2.3).
I just tested it now, took out my rebel sim put in the code and it works! I am currently using Modaco's 2.8.
Hope this helps.
I used http://hero.unlock-now.com/sim-unlock-HTC-Hero/ and the code worked for me. I did get my Hero within a few days of release. My work collegue also did the same with no problems.
What network do you use your hero on now?
hi i bought one locked to orange uk and unlocked it here
http://www.simunlock-htchero.com/buy.html
i received the code in 2 minutes and it worked, i use now Optimus in Portugal
Got my second one (for the wife) off eBay a week or two back. Poster claimed it was days old. Unlocked through htcunlock fine. Three sim seems to work better with Orange radio than the tmobile hero I purchased earlier.
Zuber
RetroFlux: I'm now on o2 after my unlock.
i'm getting the same thing with my orange locked hero, I have even tried a foreign sim as suggested. But does not seem to unlock with the correct unlock code. Is there a cable method for unlocking?
I have the same problem.
First case:
Turn on the phone with orange SIM card - everything works fine.
Turn on the phone with any other SIM card (I actually tried 3 other SIM card from 3 different providers). It asks unlock code. Enter unlock code I bought (actually any code containing 8 digits) it says "Network unlock successful." But after that it allow only emergency calls and if I try to make a call I see "Not registered in network" message. After reboot it asks unlock code again.
Second case:
If I do "restore to factory defaults" and turn it on the first time with my (no orange) SIM card, it asks unlock code I enter correct unlock code (salesman gave me one, and after that I also bought the same code in the Internet )
it hangs with phrase "Unlocking SIM card...". (Actually "turn off menu" works, I even can make an emergency call, but that is all I can get from it)
Also I noticed that in the first case there is strange line on the bottom of the screen (of the size of the notification bar).
I have tried different ROMS (original, rooted, latest, modacos) all the same. I also tried to downgrade radio firmware. I even tried all SIM cards I can obtain, the problem is obviously doesn't caused by SIM/Network incompatibility. Btw, my SIM card works OK in another HTC Hero (which was bought with my one).
I think it is problem with unlock procedure itself, not with code correctness. If wrong code entered it must say something like "wrong code", but for any 8 digit code it says "Network unlock successful". Is is the symptom! )
I do not know what to do further
I got a (UK) Orange Hero about 3 weeks ago from dial-a-phone. Unlocked it without a problem about a week later from:
http://hero.unlock-now.com/sim-unlock-HTC-Hero/
Took about 20 mins and worked 1st time. Now running with an UK O2 sim. Sorry!
As I mentioned above, while first boot with my local SIM card it hangs with "Unlocking SIM card..." message. At this time I see the following processes running.
Code:
# ps wwwwwww
PID USER VSZ STAT COMMAND
1 0 292 S /init
2 0 0 SW< [kthreadd]
3 0 0 SW< [ksoftirqd/0]
4 0 0 SW< [watchdog/0]
5 0 0 SW< [events/0]
6 0 0 SW< [khelper]
7 0 0 SW< [suspend]
8 0 0 SW< [early_suspend]
9 0 0 SW< [kblockd/0]
10 0 0 SW< [kmmcd]
11 0 0 SW< [btaddconn]
12 0 0 SW< [btdelconn]
13 0 0 SW< [kondemand/0]
14 0 0 SW< [qmi]
15 0 0 DW< [rpcrouter]
16 0 0 SW< [detection/0]
17 0 0 SW< [krpcserversd]
18 0 0 SW [pdflush]
19 0 0 SW [pdflush]
20 0 0 SW< [kswapd0]
21 0 0 SW< [aio/0]
22 0 0 SW< [panel_on/0]
23 0 0 SW< [cabc_work_q]
24 0 0 SW< [mtdblockd]
25 0 0 SW< [kadspd]
26 0 0 SW< [USB mass_storag]
27 0 0 SW< [synaptics_wq]
29 0 0 SW< [kstriped]
30 0 0 SW< [krfcommd]
31 0 0 SW< [mmcqd]
33 0 3328 S /sbin/adbd
50 1000 808 S /system/bin/servicemanager
51 0 852 S /system/bin/vold
52 0 668 S /system/bin/debuggerd
53 1001 11064 S /system/bin/rild
54 0 73504 S zygote /bin/app_process -Xzygote /system/bin --zygote --start-system-server
55 1013 30172 S /system/bin/mediaserver
57 1002 1180 S /system/bin/dbus-daemon --system --nofork
59 0 800 S /system/bin/installd
61 1008 1196 S /system/bin/akm8973
73 0 0 DW< [snd_rpc]
77 1000 173m S system_server
140 9998 159m S android.process.acore
142 1001 132m S com.android.phone
144 1000 96660 S com.htc.android.htcsetupwizard
166 10002 111m S com.google.process.gapps
179 0 0 DW< [ksdiorqd]
180 0 0 SW< [tiwlan_wifi_wq]
186 10004 96600 S com.htc.android.worldclock
193 10005 101m S com.htc.provider
207 1010 3160 S /system/bin/wpa_supplicant -Dtiwlan0 -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf
237 10031 121m S com.htc.android.htcime
244 9999 140m S com.htc.launcher
253 10016 98640 S com.htc.android.psclient
265 10017 107m S com.android.mms
285 10019 97736 S android.process.media
296 10020 106m S com.google.android.apps.maps:FriendService
307 10022 99016 S com.esmertec.android.jbed
322 10036 97.6m S com.google.android.partnersetup
332 10042 100m S com.htc.calendar
346 1000 100m S com.android.settings
356 10029 98612 S com.htc.android.footprints
366 10013 98012 S com.android.setupwizard
430 0 740 S /system/bin/sh -
468 0 2072 R ps wwwwwww
Im having the same issue, I got a new HTC Hero on Orange today, and it wont unlock. I used Unlock-now, so I have sent them a message asking for my money back, will that suffice. Has anyone been able to get there Orange UK, branded and locked phones unlocked.
nintendolinky, what is your ROM version ? There may be a possibility you have the latest firmware build... maybe...
i'm in the same boat! bought the code but no joy. it say's unlocked but could not register my voda sim. Anyone?
I tried to contact Orange today to buy an unlock code from them directly, after been passed about I eventually got through to someone bureaucratic wench who was completely unhelpful and I ended up telling them to F off and hung up. Kind of shot myself in the foot there.
I know this doesn't help our situation but I am still looking into it.
joemax said:
nintendolinky, what is your ROM version ? There may be a possibility you have the latest firmware build... maybe...
Click to expand...
Click to collapse
So are you saying there is an issue with the new firmware? When you say firmware do you mean ROM? As I have already flashed Modacos latest ROM and my Three/Vodafone/O2 sim still won't work.
I don't have my Hero with me at the moment but will post back my firmware number later, if other people (who are having the same issue) can post theirs maybe we can find a common firmware at fault.
nintendolinky said:
I used Unlock-now, so I have sent them a message asking for my money back, will that suffice.
Click to expand...
Click to collapse
I used Unlock-Now, they did refund me after your usual basic diagnostics.
joemax said:
nintendolinky, what is your ROM version ? There may be a possibility you have the latest firmware build... maybe...
Click to expand...
Click to collapse
Ok, here are my firmware details:
Firmware version: 1.5
Baseband Version: 63.18.55.06EU_6.35.06.18
Kernel Version: 2.6.27-8dd6deee [email protected]
Build Number: 2.73.405.5 146733 CL#61267 MCR2.2c release keys
Software Version: 1.0.0.A6288
Someone out there must be able to help fix this, pros/cooks/anyone can you shed anylight on this?
I've tried oldest/newes/custom ROMs, it looks like unlocking procedure doesn't depend on ROM at all.
is there a way to unlock this via cable? what about flashing the rom?
my build number is
Build Number: 1.76.61.3 whats the difference with this and Build Number: 2.73.405.5?
Here is my info:
Firmware version: 1.5
Baseband Version: 63.18.55.06EU_6.35.06.18
Kernel Version: 2.6.27-8dd6deee [email protected]
Build Number: 2.73.405.5 146733 CL#61267 MCR2.2e release keys
Software Version: 1.0.0.A6288
My build number is different, to the one listed here.
Hi all,
Is it normal for wifi to drain 1% every 5-10 mins on standby? Where as when I'm on 2g mobile data I get 40-45mins for every 1%. I've investigated this for 6 hours and it consistently shows the same result.
My setup:
Same Apps and setup. Wifi Cisco E3000 and 20 feet away from my room.
I also placed my phone 6feet away and still get the same batt drain.
I get a 120-190mah as per batterymonitor app on wifi and only 20-30mah on 2g
Thouhts?
My battery consumption on a 2.3.4 XXKG3 rooted S2, without Samsung crap:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check your running services, you will know rightaway what is killing your battery.
Yes, that is possible. It all depends on your situation. For some people mobile data drains more battery then wifi. And for some wifi drains more then mobile data.
Nothing to worry about.
yqed said:
My battery consumption on a 2.3.4 XXKG3 rooted S2, without Samsung crap:
Check your running services, you will know rightaway what is killing your battery.
Click to expand...
Click to collapse
How the heck can your battery last that long? I barely touched my phone and its down to 50 in hours. Does it matter if I'm on KH3? I live in Nz but imported my phone I think from Taiwan or hk. Will I be able to use KG3?
WiFi drains battery if it is continually searching for a signal when non is present i find .
jje
I prefer to use wifi when possible just because the battery consumption is less than 3G.. i remember one time I forgot the phone at night with wifi turned on and connected, after 7-8 hours i had lost only 2%
I leave wifi and data both turned on, all the time. That way it just uses whatever's available and I don't have to worry about it. With very minimal use (only a few calls and a handful of SMS) I can get 4 days out of my phone. I have a tablet and am usually in front of a PC, so the phone rarely gets used as anything more than a phone!
Anyway, wifi is not your issue. Have you looked into freezing the wifi sharing app? (You don't have to actually be sharing wifi for this to be a relevant thing to do!)
JJEgan said:
WiFi drains battery if it is continually searching for a signal when non is present i find .
jje
Click to expand...
Click to collapse
this is correct, if you have a good Wi-Fi signal the battery drain should be les than 3G but if not then it's gonna be worse.
thanks for the rep guys. I notice that my wifi scans continuously eventhough its using my home network. It's like scanning every 20 secs or so. Ss that normal?
With regards to Apps, and I've frozen everything I can think of that might cause a drain like beautiful widget, setting all my snyc to manual except my google account. I don't receive too much push email. I've frozen the usual culprits like wifi sharing/manager, all samsung Apps, disable fast dormancy, disable auto backup by google.
3 hours ago I frozen juicedefender and when I checked batt still drained 1% 5-15mins.!!! I'm now trying viber frozen.
I'm running out of Apps to freeze!
Is it possible that my phone drains more batt by using wifi N? Btw, as my first post says I already tried to put my phone closer to my router and I still get the same drain. Damn!!!
---------- Post added at 11:40 PM ---------- Previous post was at 11:35 PM ----------
Does having kh3 have anything to do with it? If I change modems will I benefit from it? Could it be rom related - I remember when I first rooted I was on lp and I think the batt was better. I'm now on cog1. 5.1. But I'd imagine it's more of the kernel
Edit: I forgot to mention that I'm getting 60-80% Android OS
Kepster said:
thanks for the rep guys. I notice that my wifi scans continuously eventhough its using my home network. It's like scanning every 20 secs or so. Ss that normal?
With regards to Apps, and I've frozen everything I can think of that might cause a drain like beautiful widget, setting all my snyc to manual except my google account. I don't receive too much push email. I've frozen the usual culprits like wifi sharing/manager, all samsung Apps, disable fast dormancy, disable auto backup by google.
3 hours ago I frozen juicedefender and when I checked batt still drained 1% 5-15mins.!!! I'm now trying viber frozen.
I'm running out of Apps to freeze!
Is it possible that my phone drains more batt by using wifi N? Btw, as my first post says I already tried to put my phone closer to my router and I still get the same drain. Damn!!!
---------- Post added at 11:40 PM ---------- Previous post was at 11:35 PM ----------
Does having kh3 have anything to do with it? If I change modems will I benefit from it? Could it be rom related - I remember when I first rooted I was on lp and I think the batt was better. I'm now on cog1. 5.1. But I'd imagine it's more of the kernel
Edit: I forgot to mention that I'm getting 60-80% Android OS
Click to expand...
Click to collapse
Personally, I kept it short and simple. I flashed the XXKG3 generic ROM that is compatible with my Bell distributor then I installed CF-Root and started to uninstall the apps, not "freezing" them (no idea why is called freeze, as the command is "# pm disable PACKAGE").
I use Wifi N with a Cisco E4200 DD-WRT (phone at 20") as well Beautiful Widgets and I never disabled any of the system services you mentioned in your post, you should NOT play with them. You are trying blindly to see if you improve your battery when in fact you are hurting it by killing processes that are needed by system apps (there is your drain). And Juice Defender saves you a bit of battery than use it on its app... not a big advantage. Just start from fresh with a stock ROM and clean your way up, the right way... don't just disable/uninstall what you "think" it might help. And stop installing "optimization" apps, how do you know they actually help if you do not monitor them? Get your system cleaned first, then start installing one app at the time while checking the stats available in your OS, not some fancy app. DocRambone posted a very good list, related to safe applications to be removed. Did you looked at that list? Personally, I uninstalled only half of them.
These are my running services:
Code:
PID USER VSZ STAT COMMAND
1 root 508 S /init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [migration/0]
5 root 0 SW [watchdog/0]
9 root 0 SW [events/0]
11 root 0 SW [khelper]
15 root 0 SW [async/mgr]
16 root 0 SW [pm]
19 root 0 SW [suspend]
20 root 0 SW [sync_system_wor]
151 root 0 SW [s5p-tmu]
337 root 0 SW [sync_supers]
339 root 0 SW [bdi-default]
341 root 0 SW [kblockd/0]
356 root 0 SW [khubd]
359 root 0 SW [kseriod]
394 root 0 SW [irq/331-max8997]
434 root 0 SW [kmmcd]
527 root 0 SW [kondemand/0]
540 root 0 SW [pet_watchdog/0]
549 root 0 SW [khungtaskd]
550 root 0 SW [kswapd0]
599 root 0 SW [aio/0]
612 root 0 SW [crypto/0]
1237 root 0 SW [sec_jack_wq]
1240 root 0 SW [irq/350-sec_hea]
1245 root 0 SW [spi_gpio.3]
1262 root 0 SW [svnet_txq]
1274 root 0 SW [file-storage]
1300 root 0 SW [irq/328-mxt224_]
1306 root 0 SW [irq/325-k3g]
1312 root 0 SW [irq/326-proximi]
1315 root 0 SW [cm3663_light_wq]
1316 root 0 SW [cm3663_prox_wq]
1366 root 0 SW [mali_dvfs]
1369 root 0 SW [mali-pmm-wq]
1378 root 0 SW [sii9234_wq]
1379 root 0 SW [irq/481-mhl_int]
1380 root 0 SW [irq/496-mhl_wak]
1383 root 0 SW [irq/343-max1704]
1394 root 0 SW [kstriped]
1396 root 0 SW [kmpathd/0]
1398 root 0 SW [kmpath_handlerd]
1399 root 0 SW [ksnapd]
1400 root 0 SW [kconservative/0]
1414 root 0 SW [ktflash_requlat]
1429 root 0 SW [usbhid_resumer]
1432 root 0 SW [binder]
1441 root 0 SW [irq/333-IPC_HOS]
1452 root 0 SW [mmcqd]
1481 root 0 SW [l2cap]
1482 root 0 SW< [krfcommd]
1488 root 0 SW [dynamic hotplug]
1501 root 0 SW [melfas_touchkey]
1506 root 0 SW [fimc0_iqr_wq_na]
1509 root 0 SW [fimc1_iqr_wq_na]
1512 root 0 SW [fimc2_iqr_wq_na]
1515 root 0 SW [fimc3_iqr_wq_na]
1518 root 0 SW [hdcp work]
1529 root 0 SW [tvout resume wo]
1535 root 0 SW [sec-battery]
1538 root 384 S /sbin/ueventd
1761 root 0 SW [Si4709_wq]
1782 root 0 SW [jbd2/mmcblk0p9-]
1784 root 0 SW [ext4-dio-unwrit]
2563 root 0 SW [jbd2/mmcblk0p7-]
2564 root 0 SW [ext4-dio-unwrit]
2566 root 0 SW [jbd2/mmcblk0p1-]
2567 root 0 SW [ext4-dio-unwrit]
2570 root 0 SW [jbd2/mmcblk0p10]
2571 root 0 SW [ext4-dio-unwrit]
2579 system 868 S /system/bin/servicemanager
2580 root 6616 S /system/bin/vold
2581 system 1972 S /system/bin/notified_event
2583 root 732 S /system/bin/debuggerd
2584 radio 9512 S /system/bin/rild
2585 system 4624 S /system/bin/npsmobex
2586 system 8476 S /system/bin/drexe
2590 bluetoot 1372 S /system/bin/dbus-daemon --system --nofork
2591 root 932 S /system/bin/installd
2592 keystore 1804 S /system/bin/keystore /data/misc/keystore
2594 system 14192 S /system/bin/tvoutserver
2595 shell 800 S /system/bin/sh /system/bin/rtc_log.sh
2612 shell 780 S /system/bin/immvibed
2907 wifi 2644 S /system/bin/wpa_supplicant -Dwext -ieth0 -c/data/wifi/bcm_su
3374 media 56536 S < /system/bin/mediaserver
3375 root 15472 S /system/bin/netd
3376 root 126m S zygote /bin/app_process -Xzygote /system/bin --zygote --star
3391 system 276m S system_server
3496 root 0 SW [iscan_sysioc]
3497 root 0 SW [dhd_watchdog]
3498 root 0 SW [dhd_dpc]
3499 root 0 SW [dhd_sysioc]
3502 system 152m S com.android.systemui
3511 app_99 168m S com.sec.android.inputmethod.axt9
3521 radio 155m S com.android.phone
3522 app_66 148m S android.process.media
3528 app_53 134m S com.sec.pcw.device
3532 system 134m S com.samsung.bt.avrcp
3536 bluetoot 134m S com.broadcom.bt.app.system
3544 app_12 176m S com.sec.android.app.twlauncher
3604 app_54 173m S com.google.process.gapps
3631 app_12 148m S android.process.acore
3688 app_84 135m S com.sec.android.app.FileTransferManager
3777 app_36 137m S com.sec.android.widgetapp.weatherclock
3927 app_38 136m S com.sec.android.widgetapp.apnews
4193 app_91 137m S com.sec.android.app.clockpackage
4220 app_16 137m S com.android.providers.calendar
4234 app_100 134m S com.sec.android.daemonapp.accuweather
4255 app_78 159m S com.google.android.gm
4333 app_81 174m S com.cooliris.media
4366 app_119 144m S com.google.android.apps.reader
4376 app_103 170m S com.levelup.beautifulwidgets
4435 app_37 138m S com.sec.android.widgetapp.stockclock
4453 app_16 138m S com.android.calendar
4476 system 156m S com.android.settings
4486 app_112 177m S com.google.android.music
4633 app_82 137m S com.sec.android.app.fm
4752 app_40 135m S com.sec.android.app.samsungapps.una
6623 app_68 185m S < com.google.android.apps.maps
9014 dhcp 916 S /system/bin/dhcpcd -ABK eth0
10732 graphics 139m S com.sec.android.app.screencapture
11958 system 138m S com.wssyncmldm
11989 system 135m S com.sec.android.providers.drm
11997 app_1 139m S com.smlds
12037 app_102 139m S com.skype.raider
13094 app_5 141m S jackpal.androidterm
13136 app_115 135m S com.noshufou.android.su
13170 app_68 149m S com.google.android.apps.maps:NetworkLocationService
13180 app_68 144m S com.google.android.apps.maps:FriendService
13503 app_83 141m S com.sec.android.app.FileTransferServer
13579 root 0 SW [flush-179:0]
13646 shell 1684 S /sbin/ext/busybox sh /sbin/sleep 3600
13651 shell 1676 S /sbin/ext/busybox /sbin/sleep 3600
13707 app_68 154m S com.google.android.apps.maps:HotpotService
13788 system 135m S com.android.MtpApplication
13825 app_5 796 S /system/bin/sh -
13858 root 796 S sh -
13966 root 1684 S /sbin/ext/busybox sh /sbin/ps
13971 root 1716 R /sbin/ext/busybox /sbin/ps
Compare it with yours and see what is running extra. Here are the visual running services and my battery after 29hrs (just for reference, the proper way is to look into a terminal):
I will do what you said bro and start from scratch! Never thought I'm actually causing more drain by disabling some Apps! One more question bro. Which Apps did you remove from the list?
Thanks again!
Certain routers are known to drain battery life on our SGS2s. I'm fairly certain some D-Link routers are known offenders in this regard. I can't be certain about you're router, but if you have access to different wifi connections, you should do a little testing.
Fiddling about in your router settings and upgrading your router firmware may help.
I'd link the threads where I came across the info, but I can't seem to find them atm.
Kepster said:
I will do what you said bro and start from scratch! Never thought I'm actually causing more drain by disabling some Apps! One more question bro. Which Apps did you remove from the list?
Thanks again!
Click to expand...
Click to collapse
DocRambone's list is very helpful. Technically, you can remove all that list and it won't cause any issues to your phone. However, I wanted to keep some of the apps like the NDLA, Analog Clock (for alarms), Memo, etc. Just go with your usage and uninstall what you think you will never use. Is always easier to remove it later, instead of putting it back. I don't remember exactly which apps I uninstalled (not disabled), I did it the hard way through terminal.
Many people recommended Titanium but I feel much more comfortable to see what is going on. SystemApp Remover is very good alternative to Terminal, IMO.
Here it is a list of the package manager commands:
Code:
# pm
usage: pm [list|path|install|uninstall]
pm list packages [-f] [-d] [-e] [-u] [FILTER]
pm list permission-groups
pm list permissions [-g] [-f] [-d] [-u] [GROUP]
pm list instrumentation [-f] [TARGET-PACKAGE]
pm list features
pm list libraries
pm path PACKAGE
pm install [-l] [-r] [-t] [-i INSTALLER_PACKAGE_NAME] [-s] [-f] PATH
pm uninstall [-k] PACKAGE
pm clear PACKAGE
pm enable PACKAGE_OR_COMPONENT
pm disable PACKAGE_OR_COMPONENT
pm setInstallLocation [0/auto] [1/internal] [2/external]
The list packages command prints all packages, optionally only
those whose package name contains the text in FILTER. Options:
-f: see their associated file.
-d: filter to include disbled packages.
-e: filter to include enabled packages.
-u: also include uninstalled packages.
The list permission-groups command prints all known
permission groups.
The list permissions command prints all known
permissions, optionally only those in GROUP. Options:
-g: organize by group.
-f: print all information.
-s: short summary.
-d: only list dangerous permissions.
-u: list only the permissions users will see.
The list instrumentation command prints all instrumentations,
or only those that target a specified package. Options:
-f: see their associated file.
The list features command prints all features of the system.
The path command prints the path to the .apk of a package.
The install command installs a package to the system. Options:
-l: install the package with FORWARD_LOCK.
-r: reinstall an exisiting app, keeping its data.
-t: allow test .apks to be installed.
-i: specify the installer package name.
-s: install package on sdcard.
-f: install package on internal flash.
The uninstall command removes a package from the system. Options:
-k: keep the data and cache directories around.
after the package removal.
The clear command deletes all data associated with a package.
The enable and disable commands change the enabled state of
a given package or component (written as "package/class").
The getInstallLocation command gets the current install location
0 [auto]: Let system decide the best location
1 [internal]: Install on internal device storage
2 [external]: Install on external media
The setInstallLocation command changes the default install location
0 [auto]: Let system decide the best location
1 [internal]: Install on internal device storage
2 [external]: Install on external media
For some reason I couldn't upload screen capture photos of my usage our lack thereof but basically with minimal apps installed I still get a drain from 100 to 76% in 6 hours over wifi-with 2 signal bars. Android os 91%, display 8%, cell standby 5%, idle 3%.
Checked running apps and saw fotaclient, fb, drm, Settings, maps, viber, setcpu, go launcher, syncimds, google services, voice command. I'm assuming this are normal background apps. I've got a strong feeling that my router doesn't like my phone. I will try to keep my pyotr idle but this time on data connection
Sent from my GT-I9100 using XDA App
Problem solved! It was indeed my e3000 that's causing the excessive drain! I just separated my 2.4 and 5ghz signal and voila! After 8 hours out only drained 8%! Woohoo!
Sent from my GT-I9100 using XDA App
Some users had reported wifi drain for KH3 radio. When i was on stock 2.3.3, freezing wifi sharing, wifi sharing manager and switching to KG5 modem did the trick. KH3 also caused higher battery temp when compared to Kg5...
Kepster said:
Problem solved! It was indeed my e3000 that's causing the excessive drain! I just separated my 2.4 and 5ghz signal and voila! After 8 hours out only drained 8%! Woohoo!
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Just to add, I see you are on 2Degrees, I get higher drain on my 2Degrees than my Vodafone...whilst I suspect that 2Degrees have weak reception in my area, and usually runs on 2G, I presume the phone is still searching for 3G network...hence uses more power. Just out of curiousity did you buy your SGS2 from Vodafone or Telecom? Chur.
droidphile said:
Some users had reported wifi drain for KH3 radio. When i was on stock 2.3.3, freezing wifi sharing, wifi sharing manager and switching to KG5 modem did the trick. KH3 also caused higher battery temp when compared to Kg5...
Click to expand...
Click to collapse
I confirm that XXKH3 drains faster the battery compared to XXKG3, but look at the GPS gains... whoaaa, pinpoint location in less than 3 seconds with a 5meters accuracy. Really happy to finally use my GPS properly, it is worth the increased battery drain. From my tests, the new firmware decreased the battery life by about 4 hours... I can live with that, in exchange of a great GPS.
Yeah GPS locking was brilliant in KH3... But i use wifi and data connection more, than GPS. KH3 drained more battery on standby also. May be it's causing more wakelocks...
Can some one please guide how to root Iball slide tablet. Iball Tab information is given below
OS
Browser UserAgent : Mozilla/5.0 (Linux; U; Android 2.3; en-gb; iBall Slide i7011 Build/GINGERBREAD) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1
Android ID : acbc4627cc4a9253
Uptime : 0 days, 1 hours, 53 minutes, 26 seconds
Uptime (without sleeps) : 0 days, 1 hours, 53 minutes, 26 seconds
BuildInfos
Android version : 2.3
Release Codename : REL
API LEVEL : 9
CPU ABI : armeabi-v7a
Manufacturer : unknown
Bootloader : unknown
CPU ABI2 : armeabi
Hardware : smdkv210
Radio : unknown
Board : smdkv210
Brand : generic
Device : smdkv210
Display : MID Serials 2.3 GINGERBREAD 20110830.164011
Fingerprint : generic/full_smdkv210/smdkv210:2.3/GINGERBREAD/20110830.164011:eng/test-keys
Host : urbetter-linux01
ID : GINGERBREAD
Model : iBall Slide i7011
Product : full_smdkv210
Tags : test-keys
Type : eng
User : raymanfeng
Battery
Not charging...
Level : 50 %
Technology : Li-ion
Temperature : 20.0 °C (68.0°F)
Voltage : 7626 mV
Memory
Download Cache Max: 100MB/ Free: 86.45MB
data Max: 488MB/ Free: 367MB
External storage Max: 6.55GB/ Free: 6.26GB
Total RAM: 361MB
Free RAM: 159MB
Threshold RAM: 24.00MB
Low Memory Killer Levels
FOREGROUND_APP:__ 8.00MB
VISIBLE_APP:_________ 12.00MB
SECONDARY_SERVER: 16.00MB
HIDDEN_APP:________ 24.00MB
CONTENT_PROVIDER: 28.00MB
EMPTY_APP:__________ 32.00MB
Telephony
Data Activity: DATA_ACTIVITY_NONE
Data State: DATA_DISCONNECTED
IMEI(or MEID): null
IMEI/SoftVer: null
MSISDN: null
Registered MCC:
Registered MCC MNC:
Registered Operator Name:
Network Type: NETWORK_TYPE_UNKNOWN
Phone Type: PHONE_TYPE_GSM
SIM Country Code: us
SIM MCC MNC: 310004
SIM Operator Name: Verizon
SIM Serial Number: null
SIM State: SIM_STATE_UNKNOWN
Subscriber ID(IMSI): null
VoiceMail number:
Roaming: false
No Cell detected
Networks
Background Data Usage: true
type mobile[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type WIFI[]
state CONNECTED/CONNECTED
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable true
type mobile_mms[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type mobile_supl[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type mobile_hipri[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type Network3gDataStateTracker[]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type NetworkEthDataStateTracker[]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
Wifi
State: WIFI_STATE_ENABLED
CPU
Processor ARMv7 Processor rev 2 (v7l)
BogoMIPS 998.15
Features swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer 0x41
CPU architecture 7
CPU variant 0x2
CPU part 0xc08
CPU revision 2
Hardware SMDKV210
Revision 0000
Serial 0000000000000000
Frequency Stats (time):
Screen
Resolution: 800 x 480
Refresh Rate: 68.0
X factor for DIP: 1.25
Density: 200 dpi
Pixel per inch X: 144.0 dpi Y: 144.0 dpi
OpenGL
As retreiving opengl infos can crash some device, it is not enabled by default. If you wish to, go in settings menu.
Sensors
mma7660-accel: 0.2 mA by urbetter
Gravity Sensor: 0.2 mA by Google Inc.
Linear Acceleration Sensor: 0.2 mA by Google Inc.
Rotation Vector Sensor: 0.2 mA by Google Inc.
Environment
Root Directory: /system
Data Directory: /data
Download Cache Directory: /cache
External Storage State: mounted
External Storage Directory: /mnt/sdcard
Medias Directories
Alarms: /mnt/sdcard/Alarms
DCIM: /mnt/sdcard/DCIM
Downloads: /mnt/sdcard/Download
Movies: /mnt/sdcard/Movies
Music: /mnt/sdcard/Music
Notifications: /mnt/sdcard/Notifications
Pictures: /mnt/sdcard/Pictures
Podcasts: /mnt/sdcard/Podcasts
Ringtones: /mnt/sdcard/Ringtones
Features
android.hardware.location.network
android.hardware.wifi
android.hardware.nfc
com.google.android.feature.GOOGLE_BUILD
android.hardware.location
android.hardware.sensor.gyroscope
android.hardware.bluetooth
android.hardware.touchscreen.multitouch.distinct
android.hardware.microphone
android.hardware.sensor.light
android.software.live_wallpaper
android.hardware.telephony
android.hardware.touchscreen.multitouch.jazzhand
android.hardware.sensor.barometer
android.software.sip
android.hardware.touchscreen.multitouch
android.hardware.sensor.compass
android.hardware.camera
android.software.sip.voip
android.hardware.sensor.proximity
android.hardware.location.gps
android.hardware.telephony.gsm
android.hardware.telephony.cdma
android.hardware.camera.front
android.hardware.sensor.accelerometer
android.hardware.touchscreen
glEsVers=2.0
JavaProperties
java.vendor.
java.class.path: .
java.class.version: 46.0
os.version: 2.6.35.7
java.vendor: The Android Project
user.dir: /
user.timezone: null
path.separator: :
os.name: Linux
os.arch: armv7l
line.separator:
file.separator: /
user.name:
java.version: 0
java.home: /system
Mount points
MountPoint
Name Type Options
- /
rootfs rootfs rw
- /
ubi0:rootfs ubifs rw,relatime
- /dev
tmpfs tmpfs rw,relatime,mode=755
- /dev/pts
devpts devpts rw,relatime,mode=600
- /proc
proc proc rw,relatime
- /sys
sysfs sysfs rw,relatime
- /acct
none cgroup rw,relatime,cpuacct
- /mnt/asec
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /proc/bus/usb
none usbfs rw,relatime,devmode=666
- /mnt/obb
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /dev/cpuctl
none cgroup rw,relatime,cpu
- /data
/dev/block/mmcblk0p3 ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
- /cache
/dev/block/mmcblk0p2 ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
- /sys/kernel/debug
/sys/kernel/debug debugfs rw,relatime
- /mnt/sdcard
/dev/block/vold/179:1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/secure/asec
/dev/block/vold/179:1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/sdcard/.android_secure
tmpfs tmpfs ro,relatime,size=0k,mode=000
- /mnt/extsd
/dev/block/vold/179:8 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.UCMobile.intl-1
/dev/block/dm-0 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.skype.raider-1
/dev/block/dm-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.opera.mini.android-1
/dev/block/dm-2 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.eamobile.nfsshift_na_wf-1
/dev/block/dm-3 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.guidedways.iQuranPro-1
/dev/block/dm-4 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.dolphin.browser-1
/dev/block/dm-5 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/kz.mek.DialerOne-1
/dev/block/dm-6 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.adobe.reader-1
/dev/block/dm-7 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.google.earth-1
/dev/block/dm-8 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.electricsheep.asi-1
/dev/block/dm-9 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.joeykrim.rootcheck-1
/dev/block/dm-10 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
I tried ginger break but of no use superuser is install but not working, Here is the feedback from root Checker
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.6 is installed!
System Environment PATH: /system/busybox/bin /system/busybox/sbin /system/busybox/usr/bin /system/busybox/usr/sbin /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
-rwsr-sr-x 1 2000 2000 22228 Feb 28 2008 /system/bin/su
Standard su binary location: ls -l /system/xbin/su:
ls: /system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
ls: /sbin/su: No such file or directory
Alternate su type binary location: ls -l /system/xbin/sudo:
ls: /system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your iBall Slide i7011 device by Root Checker version 3.9 from joeykrim in the Android Market
Please guide
Thanks in advance
any help from anyone regarding rooting iball slide i7011 android 2.3 tab. I have tried gingerbreak and also tried superoneclick as per guide but of no use.
both of them reports that the tab is rooted but when i try su command superuser wont give permission. its a mess up right now. and when i try to remove superuser its not done saying its a system app. and when i go to /system/apps/superuser its mounted as r/o.
can anyone help this ?????
I have tried almost all process from single click app to rooting via adb, bt failed. So I have changed its firmware, which includes a custom ROM...So using my iball slide with much more functions..
Bt there is one problem..The camera is not working..may be the device driver is not working, I am trying to develop this issue, and will be back when I will debug that..
Rooting Iball Slide tab
DISCLAMER you do all this on your own risk if you break your tab don’t blame me. You may want to backup some files before messing around...
1. Full charge your slide, as we required to on/off it many times
2. Download Gingerbrak.apk , saved it to the root of you SD card
3. Make sure Unknown source and USB debugging is enable
4. One file manager and install gingerbreak.apk
5. One Gingerbreak.apk, wait until your device is off
6. Press power button, let the devices start, go to application if you see Superuser Icon there, you half work is done
7. If Superuser is not install, manually install it from market
8. Connect tab to your computer with OTG, wait until driver are installing
9. To check if deriver is install or not
Right click computer > Manage>Devices Management
And check for ADB Interface and android Composite ADB Interface if it is there that means your tab is ready for next step
10. Again on your tab click gingerbreak application, wait until your mobile is off, let it be in off for now
11. Type CMD in search, Click and run as administrator
12. Type CD.. until you reach to C:\
13. Then type [space cd space platform-tools] , without bracket
14. Power on your device, wait until you see slide boot screen than
15. type [space adb devices] enter it will show you message and List of devices attached, don’t worry even if it doesn’t shows serial no of your devices , if message come as “device not found” than you need to install OTG driver manually
16. Now enter [space adb space shell]
17. Wait for few second and type [ cd/system/bin], now you would see $ sign
18. Wait till device is completely started, unlock screen
19. And type [ ./su] that is DOT /SU
20. Now check the screen, Superuser application should ask you for permission , Click allow
21. Type [rm/system/busybox/bin/su].
22. Type exit , Exit again, Wala now you are rooted
Download root check application to check whether is rooted or not
If it doesn’t happened repeat the process again, if you have any question, just put in comment, I would love to answer it
ffarhan.s said:
Rooting Iball Slide tab
DISCLAMER you do all this on your own risk if you break your tab don’t blame me. You may want to backup some files before messing around...
1. Full charge your slide, as we required to on/off it many times
2. Download Gingerbrak.apk , saved it to the root of you SD card
3. Make sure Unknown source and USB debugging is enable
4. One file manager and install gingerbreak.apk
5. One Gingerbreak.apk, wait until your device is off
6. Press power button, let the devices start, go to application if you see Superuser Icon there, you half work is done
7. If Superuser is not install, manually install it from market
8. Connect tab to your computer with OTG, wait until driver are installing
9. To check if deriver is install or not
Right click computer > Manage>Devices Management
And check for ADB Interface and android Composite ADB Interface if it is there that means your tab is ready for next step
10. Again on your tab click gingerbreak application, wait until your mobile is off, let it be in off for now
11. Type CMD in search, Click and run as administrator
12. Type CD.. until you reach to C:\
13. Then type [space cd space platform-tools] , without bracket
14. Power on your device, wait until you see slide boot screen than
15. type [space adb devices] enter it will show you message and List of devices attached, don’t worry even if it doesn’t shows serial no of your devices , if message come as “device not found” than you need to install OTG driver manually
16. Now enter [space adb space shell]
17. Wait for few second and type [ cd/system/bin], now you would see $ sign
18. Wait till device is completely started, unlock screen
19. And type [ ./su] that is DOT /SU
20. Now check the screen, Superuser application should ask you for permission , Click allow
21. Type [rm/system/busybox/bin/su].
22. Type exit , Exit again, Wala now you are rooted
Download root check application to check whether is rooted or not
If it doesn’t happened repeat the process again, if you have any question, just put in comment, I would love to answer it
Click to expand...
Click to collapse
first of all a big thanks to ffarhan.s.... thanks bro ur guide was fantastic and worked like charm. i rooted my tab without any glitch. thanks a lot buddy.
but something more to say for the newbies,
1. download gingerbreak.apk and save it in ur tab's sd card(which means internal 8gb memory)
2. ADB composite device may not show up in device manager so dont worry. but android adb interface must be shown in the path computer > Manage>device manager>android phones>android adb interface (its very necessary)
3. .. as ffarhan wrote > Then type [space cd space platform-tools] , without bracket.. its actually the path of your android sdk folder. assuming u have downloaded the sdk folder under c:\
so the path will be c:\android-sdk\platform-tools
then type adb devices press enter. the result may show like this :
List of devices attached
MID_serials devices
.... below this blank.dont worry its fine.
the main part is point 16 - 22. these should work as ffarhan wrote otherwise repeat the process from start.
anywyz, once again thanks ffarhan.s for the entire process. take care bro.
have a nice day
I have done this, bt for my case it was a temporary root..I think it has to be made permanent...
will "root explorer" go ?my i7011 is ok(Root Explorer 2.17).
it can mount / or other partitions as ro or rw?
btw, can u mail me the file "/system/bin/wpa_supplicant" , thanks a lot, [email protected]
ffarhan.s said:
8.Connect tab to your computer with OTG, wait until driver are installing
9.To check if deriver is install or not
Right click computer > Manage>Devices Management
And check for ADB Interface and android Composite ADB Interface if it is there that means your tab is ready for next step
10. Again on your tab click gingerbreak application, wait until your mobile is off, let it be in off for now
Click to expand...
Click to collapse
the device manager on my computer does show any ADB interface or android Composite ADB interface. What am i doing wrong ?
New problem !!
ffarhan.s said:
16. Now enter [space adb space shell]
17. Wait for few second and type [ cd/system/bin], now you would see $ sign
18. Wait till device is completely started, unlock screen
19. And type [ ./su] that is DOT /SU
20. Now check the screen, Superuser application should ask you for permission , Click allow
21. Type [rm/system/busybox/bin/su].
22. Type exit , Exit again, Wala now you are rooted
Download root check application to check whether is rooted or not
If it doesn’t happened repeat the process again, if you have any question, just put in comment, I would love to answer it
Click to expand...
Click to collapse
on performing step 16, the $ sign pops up immediately and for the remaining steps i keep getting 'cannot find'. plz help me out.:fingers-crossed:
vivdutta said:
on performing step 16, the $ sign pops up immediately and for the remaining steps i keep getting 'cannot find'. plz help me out.:fingers-crossed:
Click to expand...
Click to collapse
That's not a bring problem . And the correction in 21st step that it is rm system not rm/system. Hope u get it
ffarhan.s said:
Rooting Iball Slide tab
DISCLAMER you do all this on your own risk if you break your tab don’t blame me. You may want to backup some files before messing around...
1. Full charge your slide, as we required to on/off it many times
2. Download Gingerbrak.apk , saved it to the root of you SD card
3. Make sure Unknown source and USB debugging is enable
4. One file manager and install gingerbreak.apk
5. One Gingerbreak.apk, wait until your device is off
6. Press power button, let the devices start, go to application if you see Superuser Icon there, you half work is done
7. If Superuser is not install, manually install it from market
8. Connect tab to your computer with OTG, wait until driver are installing
9. To check if deriver is install or not
Right click computer > Manage>Devices Management
And check for ADB Interface and android Composite ADB Interface if it is there that means your tab is ready for next step
10. Again on your tab click gingerbreak application, wait until your mobile is off, let it be in off for now
11. Type CMD in search, Click and run as administrator
12. Type CD.. until you reach to C:\
13. Then type [space cd space platform-tools] , without bracket
14. Power on your device, wait until you see slide boot screen than
15. type [space adb devices] enter it will show you message and List of devices attached, don’t worry even if it doesn’t shows serial no of your devices , if message come as “device not found” than you need to install OTG driver manually
16. Now enter [space adb space shell]
17. Wait for few second and type [ cd/system/bin], now you would see $ sign
18. Wait till device is completely started, unlock screen
19. And type [ ./su] that is DOT /SU
20. Now check the screen, Superuser application should ask you for permission , Click allow
21. Type [rm/system/busybox/bin/su].
22. Type exit , Exit again, Wala now you are rooted
Download root check application to check whether is rooted or not
If it doesn’t happened repeat the process again, if you have any question, just put in comment, I would love to answer it
Click to expand...
Click to collapse
well i have a few problems...i have ADB interface...that means the the drivers are installed right?but when i open gingerbreak..it does the process...but my tab shuts off...i switch it on and superuser is also there...then i connect with OTG and i guess my drivers are installed...then i dont understand what you mean by Type CD.. until you reach to C:\...what exactly am i supposed to do??can u please post screenshots...or even better...if it is not too much trouble a video on how u did it!! i really want to root my tab...but i just cant get through to it!! :|
how to root iball slide with jelly bean (6309r)
can anybody please help me and tell how to root iball slide with jelly bean (6309r):crying:
This Procedure Works for every Iball Slide Tablets
http://forum.xda-developers.com/showthread.php?p=43037172#post43037172