Is the any of LG_IME.apk that works on "Joestone's Gingerbread 2.3.2".
I've had extracted LG_IME form "Lavero Burgos's data2system mod of AOSP Joestone Gingerbread" ROM and have installed it to "Joestone's Gingerbread 2.3.2"
The problem is, it says force close.
Thanks
use this http://gt540.co.cc/index.php?dir=&file=LG_IME_2.3.zip
I don't know what went wrong, I've installed the zip package via recovery but it seems that the problem remains.
When I select LG IME as the input method, It does still says force close.
But thanks anyway
heres what to do with my file:
TUTORIAL #7
- Dowload LG_IME_data2system and unzip in desktop
- Open System folder and copy the 3 folders: app, lib2 and usr folders to C:\*SDK\platform-tools\
- Plug your phone to the computer
- Open a CMD terminal and type:
Code:
cd C:\*SDK\platform-tools
adb devices
adb remount
adb push app /system/app
adb push lib2 /system/lib
adb push usr /system/usr
adb kill-server
exit
- Unplug your phone
- Go to ROM Manager application and run Fix Permissions (DO NOT avoid this step, so you dont get FC's)
DONE!
Veronica
Sent from my GT540 using XDA App
It works, thanks Veronica
I've followed your tutorial step by step and it works without any problem. No more FC ...
Thanks Veronica
Nearly There. . .
Followed your guide right through. Only problem I have is the T9 (predictive) won't work, the little T9 button is disabled..... no FC's though. Any thoughts ??
lavero.burgos said:
heres what to do with my file:
TUTORIAL #7
- Dowload and unzip in desktop
- Open System folder and copy the 3 folders: app, lib2 and usr folders to C:\*SDK\platform-tools\
- Plug your phone to the computer
- Open a CMD terminal and type:
Code:
cd C:\*SDK\platform-tools
adb devices
adb remount
adb push app /system/app
adb push lib2 /system/lib
adb push usr /system/usr
adb kill-server
exit
- Unplug your phone
- Go to ROM Manager application and run Fix Permissions (DO NOT avoid this step, so you dont get FC's)
DONE!
Veronica
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
can someone tell me why this method is not working for me ?? i've followed the instructions but.. FC's...
Related
Mod Edit: Unstickied, placed link in wiki:http://forum.xda-developers.com/wiki/index.php?title=Nexus_One Thanks
This is an alternative approach of rooting the Nexus without touching the bootloader.
-no downgrade neccessary
-no battery modification neccessary
-no messing around with SD card slot
-you don't even have to open your phone...
Working and confirmed for ALL ROMs, including European Vodafone EPF30/FRF91, Korean FRF91, AT&T/T-Mo Stock including FRF91
-------
Credits:
-------
- The Android Exploid Crew:
http://c-skills.blogspot.com/2010/07/android-trickery.html
- Amon_RA
- cyanogen
-------
Notes:
-------
- The exploit wasn't found by me (see credits), I just implemented it as a proof of concept for the Nexus One
- Basically this method should work on all currently known ROM versions.
- I tested it on EPF30, Korean FRF91, Vodafone FRF91, US Stock FRF91.
- As usual when doing this kind of stuff: DO THIS AT YOUR OWN RISK.
- It could even work on other Android devices as long as their system partition is at
/dev/block/mtdblock3/ with yaffs2 file system and there is still some space left on the system partition (without any changes).
-------
Prerequisites:
-------
- Locked Nexus One
- Latest Android SDK incl. USB drivers
- Working ADB
- The file "freenexus.zip"
edit:
get it here:
http://multiupload.com/MVT98F5HBY
or
http://dl.dropbox.com/u/1327667/freenexus.zip
MD5: 947C20222056D7C070733E7FCF85CF15
-------
Step-by-step guide:
-------
1. install android sdk & USB drivers
2. extract the content of the zip file into the tools directory of SDK (i.e. \android-sdk-windows\tools)
-> For all Newbies: Take care that you extract the files directly to the tools folder and don't create a new subdirectory freenexus within tools!!! If you did, delete the folder and extract again!!! Check twice that there is no FOLDER freenexus in your tools directory before you continue!!!
3. open a command prompt (Windows: Start, Run, "cmd", OK; Linux: Terminal)
4. change to SDK tools directory (i.e. cd \android-sdk-windows\tools)
5. connect Nexus to USB and check if debugging mode is activated
(Settings/Application/Development/USB Debugging)
6. run "adb devices" in shell and see if there is a device listed. if not back to step 5 or reinstall USB-drivers
7a. for Windows: run "freenexus.bat" in command shell (this copies the neccessary files to /data/local/tmp)
7b. for Linux or manual installation: run the following commands
Code:
adb push freenexus /data/local/tmp/freenexus
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb shell chmod 755 /data/local/tmp/freenexus
adb shell chmod 755 /data/local/tmp/busybox
8. run the following commands:
Code:
adb shell
(you should see a "$" prompt now)
cd /data/local/tmp
9. on your phone go to a screen where you can easily toggle wifi (widget or settings/wireless)
10. be prepared to toggle wifi immediately after you execute the next step
11. run
Code:
./freenexus
12. toggle wifi on
13. you should see something like that:
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by ak for HTC Nexus One
[+] Using basedir=/sqlite_stmt_journals, path=/data/local/tmp/freenexus
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
13b) if you get "permission denied" error, you have most likely not followed the big red newbie hint after point 2. check this by entering "ls -l", if you see a "drwxr-xr-x" and not "-rwxr-xr-x" in front of the line where freenexus is listed you did not follow properly. Search the posts in the thread on how to correct this.
14. run
Code:
rootshell
15. if you succeeded you will be asked for a password, if not try again from step 10
16. enter the password "freenexus"
17. now you should see a "#" as a prompt -> you are root now
18. run the following commands:
Code:
./busybox cp busybox /system/bin
chmod 4755 /system/bin/busybox
busybox cp Superuser.apk /system/app
busybox cp su /system/bin
chmod 4755 /system/bin/su
rm /system/bin/rootshell
exit
exit
19. Check if you keep root rights:
Code:
adb shell
su
20. after you executed the su command the Superuser app on your device should ask you for allowance
21. you should see the "#" prompt again, if you didn't get that try su again
22. done
-------
Comments:
-------
- General
If you are not planning to wipe your data partition (what you probably will do when installing CM6 first time) you should think about deleting all the temp files still lying in /data/local/tmp (for safety reasons and to have more space on /data):
Code:
adb shell
cd /data/local/tmp
rm busybox
rm su
rm Superuser.apk
rm freenexus
rm flash_image (will only exist if you executed the steps below in recovery section)
- Installation of Custom Recovery
If you only want root rights you are done here. If you want to install custom ROMs you have to install
a custom recovery first. Easiest way would be to download "ROM Manager" from the market. There are plenty of tutorials on how to install custom recovery/ROM at xda.
Edit: It is safer to install the recovery manually. In this case or for those of you running into problems with installing custom recovery with ROM Manager (doesn't stick) you can continue with
these steps (without remount of system partition, now tested successfully):
1) Download recovery-RA-nexus-v1.7.0.1.img to the root directory of your SD-Card
- Note: UnMount your SD-Card after copying these files, but keep your phone plugged in
- or don't mount SD-Card at all and push the file via adb to /sdcard
2) Save file "flash_image" to sdk tools directory:
3) In your terminal run
Code:
adb push flash_image /data/local/tmp/flash_image
adb shell
su
- At this point, it will hang until you choose "Allow" on your phone with the SuperUser app pop-up
- $ should now be replaced with #
5) run the following commands:
Code:
[COLOR="Red"]mount -o rw,remount /dev/block/mtdblock3 /system[/COLOR]
cd /data/local/tmp
chmod 755 flash_image
[COLOR="Red"]./flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img[/COLOR]
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
(and if everything worked fine:)
rm flash_image
Alternatively you can continue with step 9 and then steps 16-24 from the old rooting method tutorial
to manually install Amon_RA's recovery. You will also need the file flash_image for that (link taken from HBOOT thread).
- HBOOT
If you rooted from a Korean Rom or have installed the latest Vodafone Rom via PASSIMG you probably have
HBOOT 0.35 which makes it currently difficult to install Cyanogenmod (there is an assertion failure in the install script, at least with CM6 RC1/2. Maybe future versions of CM6 will include HBOOT 0.35 in the script) or other custom ROMs. (You are still on 0.33 if you just installed the Vodafone OTA Update)
There is a tutorial to revert HBOOT here:
http://forum.xda-developers.com/showthread.php?t=726258
Instead of using the EPF30 image you can also use any other PASSIMG file (at least if it has HBOOT 0.33,
otherwise this step wouldn't make sense...)
Note that when flashing a PASSIMG with a different HBOOT version there is a reboot after the HBOOT has been flashed, then after reboot the PASSIMG will be loaded again and the rest of the image will be flashed.
To check HBOOT and Radio version: press and hold trackball while turning on the phone. To exit select Reboot with Vol+/- and press Power button.
Caution:
After you have reverted your HBOOT, you have lost your root rights and you are back on stock recovery.
But you can (or have to) repeat the above procedure to get root rights back.
Edit:
The downgrading also downgrades your radio!!! Before installing CM6 you have to flash a Froyo Radio!
Latest one can be found here:
http://forum.xda-developers.com/showthread.php?t=723839
-------
Troubleshooting:
-------
After trying to flash a custom ROM with ROM Manager one user wasn't able to boot the phone normally and also no longer able to boot to recovery. In this rare case try to download a compatible PASSIMG file:
For example EPF30 (Europe Vodafone 2.1)
http://shipped-roms.com/shipped/Pas...ogle_WWE_1.14.1700.1_EPF30_release_signed.zip
or FRF91 (Europe Vodafone 2.2):
http://shipped-roms.com/shipped/Pas...on_VF_2.15.151.5_R_FRF91_MFG_Shipment_ROM.zip (<-this one is currently a zip in zip. You have to extract it once to get the working PASSIMG.zip)
(Appropriate US-PASSIMGs can also be found on shipped-roms.com, most likely EPE76)
Rename the file to PASSIMG.zip (case sensitive, Windows users take care that the file isn't called PASSIMG.zip.zip hidden extension)
Copy it to main folder of SD card.
Boot phone into Bootloader mode (press and hold trackball when turning on the phone, until fastboot mode starts)
Select Bootloader mode by pressing power button.
The bootloader should then start to analyse the PASSIMG.zip and ask you afterwards to install it.
You're phone (not your SD) will be completely wiped after the procedure but should work again (and can be rooted again...)
sweet!! been waiting for this! will try it tomorrow as soon as i wake up! will report back then!
edit: i cant download freenexus.zip maybe use another hoster?
file section edited.
Great tutorial ! Waiting for some feedbacks
(file link doesn't work)
dolomiti7 said:
file section edited.
Click to expand...
Click to collapse
On the left I can see just an empty folder named "SmartDrive"
link doesn't work
dolomiti7 said:
-> after clicking on "Smartdrive Gastzugang starten" you might get an error message, but after klicking ok on the error message
you should be able to access the folder "nexus" on the left side of the window anyway
Click to expand...
Click to collapse
No way! Can't do anything even after i press ok on the error message
if you click on that there should be a subfolder "nexus" that should be clickable too. at least it works here... anyway. someone wants to upload the file to a hoster? rapidshare... contact me
for the early adaptors (will only work 10 times):
rapidshare.com/files/409266634/freenexus.zip
MD5: 947C20222056D7C070733E7FCF85CF15
multiple download sites!:
http://www.multiupload.com/MVT98F5HBY
or here:
http://dl.dropbox.com/u/1327667/freenexus.zip
thank you. added the link.
This worked flawlessly.
Massive thanks.
Hi, I have a Italian Vodafone Nexus One with FRF91, i have followed all the steps and now in my apps there is Superuser Permission with green light. It means that i have root rights? Can I install Cyanogen Mod now? Thanks, excuse my English.
Worked perfectly on a stock AT&T N1 with FRF91. Thanks!
Excellent tutorial step by step...great work!
Can i change the password at the end?
So once gaining root, I can flash a custom recovery with rom manager without braking/unlocking the boot loader?
@fc_themaster:
if the superuser app popped up at step 19/20 then you have root rights. you can try to install ROM Manager from the market and install a custom recovery with that porgram. it also needs root rights so superuser should pop up again at that point.
@PSeeCO: you don't need to change a password. the password was only used for the temporary rootshell which you (hopefully) deletetd with the command "rm /system/bin/rootshell" in step 18. From that point on root rights are controlled via the Superuser app. If you install an already rooted custom ROM it is obsolete anyway.
@jivemaster: yes, we can! just use ROM Manager from the market to install custom recovery.
dolomiti7 said:
@PSeeCO: you don't need to change a password. the password was only used for the temporary rootshell which you (hopefully) deletetd with the command "rm /system/bin/rootshell" in step 18. From that point on root rights are controlled via the Superuser app. If you install an already rooted custom ROM it is obsolete anyway.
Click to expand...
Click to collapse
Perfect, thank you so much!
I created script to change framework-res.apk
--New-- Script with safer operation uploaded.
Requirements
-rooted
-busybox installed
1-copy framework-res.apk that you want to replace to the root of your sdcard (make sure it's in root)
2-extract reframe.zip(attachment) to root of your sdcard
in adb shell, use this command:
Code:
su
cd /sdcard
sh reframe.sh
your phone will reboot. and done! your framework-res.apk replaced safely.
Original framework-res.apk backed up as framework-res.apk.orig in /sdcard
Is there any method to get back original framework from SDCard, and paste it to /system, when my phone doesn't want to boot?
hugerth said:
Is there any method to get back original framework from SDCard, and paste it to /system, when my phone doesn't want to boot?
Click to expand...
Click to collapse
Use xrecovery..
Sent from my E15i using XDA App
Can't install... ok... I reflash 1.6 and root it again, install 2.1 and xRecovery for the future...
hugerth said:
Can't install... ok... I reflash 1.6 and root it again, install 2.1 and xRecovery for the future...
Click to expand...
Click to collapse
ops.if you have working rootshell, you can replace it using rootshell. but, since you've go back to 1.6, it doesn't matter. just install xrecovery in the future, quite useful.
Now I have system back (after about 2h) with working xRecovery and... God!.. why I haven't noticed it before...
i wanna ask how to recover the framework-res.apk from the xrecovery??
mount /system and use adb push
edit: new script. revised operation
D:\adb>adb remount
remount failed: Operation not permitted
any help here? I need to replace the framework
nm, forgot to chmod 06777 /system/framework
Thank you for you work. I hope to see this work Just rebooted my phone after applying your script.
propc said:
I created script to change framework-res.apk
--New-- Script with safer operation uploaded.
Requirements
-rooted
-busybox installed
1-copy framework-res.apk that you want to replace to the root of your sdcard (make sure it's in root)
2-extract reframe.zip(attachment) to root of your sdcard
in adb shell, use this command:
Code:
su
cd /sdcard
sh reframe.sh
your phone will reboot. and done! your framework-res.apk replaced safely.
Original framework-res.apk backed up as framework-res.apk.orig in /sdcard
Click to expand...
Click to collapse
Can u tell me where to find the adb shell
Sent from my E15i using XDA App
Use Super One Click, it comes with adb. Copy cmd.exe to SOC folder. Now start cmd, now type 'adb shell' (click enter) and then the other commands.
Sent from my E15i using Tapatalk
you can always change a framework by installer from available theme
mzmz83 said:
Use Super One Click, it comes with adb. Copy cmd.exe to SOC folder. Now start cmd, now type 'adb shell' (click enter) and then the other commands.
Sent from my E15i using Tapatalk
Click to expand...
Click to collapse
This is what I see when I open superoneclick t shows Root, shell Root, Unroot, allow non market apps....
Now in superoneclick folder that it comes in when u open it this is what u see
Superuser.apk
Superoneclick
Su
Sqlite3
Regeagainsttecage
Bushels
Addbwinusbapi
Adbwinapi
Ashland
Adblinux
Adb. Application
But when I try to open adb app it does not open a screen comes up then it closes so there is where am stuck at:-( :-( can u help me out from there??????
Sent from my E15i using XDA App
adb won't stay open if you click it, it will just flash out on the screen.
it was supposed to be somekind of a "bridge" for the cmd and the phone...
correct me if i'm wrong please...
You have to copy cmd.exe to the SuperOneClick folder, then you have to open the cmd.exe, not the superonecklick.exe.
I'm trying to replace framework and when I type in shell I got:
cd /sdcard
#
sh reframe.sh
sh: Can't open reframe.sh
#
oubsty, Thanks you
Boshe said:
I'm trying to replace framework and when I type in shell I got:
cd /sdcard
#
sh reframe.sh
sh: Can't open reframe.sh
#
Click to expand...
Click to collapse
I think it works if your phone is charged by your laptop/computer only. You do not allow it to connect. I mean you can not reach SDCard through Total Commander, etc. only charging.
Help
# sh reframe.sh
sh reframe.sh
sh: Cannot open reframe.sh
#
any ideas
got SuperOneClick 1.5.5 ( busybox )
root explorer ( only thing in superuser )
SE's PC companion running in background [ keeps asking for mount, but is ignored ]
got Android full SDK installed - drivers, ADB, 'the works'
root'd succesfully -(( WORLD-1-8_2.0.1.A.0.47 )) White-DarkBlue / Pink
4Gb Kingston HC4 sdc4/4gb 18 - un partitioned.
I wish to remove some bloat, and change to a custom theme.
{EDIT} - how to access recovery mode?, got customization = home-back-back-home-back-home-home-back
Dalvik Debug Monitor won't run, adb error2
thanks in advance.
Hi guys,
I take no credit for this, as this method was already described in this forum:
http://forum.androidcentral.com/bar...ow-download-install-honeycomb-nook-color.html
The only thing I did was apply this to regular APK installs and they've been working well thus far.
Here's what you do (windows users):
1. Make sure the NC has ADB access, check the Honeycomb thread for more on this
2. Have the APK you want to install readily available.
3. Open a command prompt, Start -> Run -> "CMD" (No quotations) (Make sure you're admin when doing this)
4. cd into your android-sdk file by typing in the file directory, mine looks like this:
cd..
cd..
cd android-sdk\tools
Click to expand...
Click to collapse
This is because my android-sdk is in C:\android-sdk
5. Now type in the following commands:
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb push [YOUR APK HERE] /system/app
Click to expand...
Click to collapse
Where [YOUR APK HERE] is the file name of the APK you want to install. I've found the easiest way to do this is to type in "adb push" then drag and drop the file into the command prompt for easy access.
6. Finally, type in
adb reboot
Click to expand...
Click to collapse
7. Enjoy your APKs! I can't guarantee how well they'll work, so far Pulse reader is working well for me
I also have to point out, that for many apps, the "adb install "program.apk" works well - its how i installed my copy of quadrant and dolphin HD.
Divine_Madcat said:
I also have to point out, that for many apps, the "adb install "program.apk" works well - its how i installed my copy of quadrant and dolphin HD.
Click to expand...
Click to collapse
This is true, for that all you have to do is:
adb install [YOUR APK HERE]
Click to expand...
Click to collapse
Thanks, Divine_Medcat!
newer versions of the SDK moved the adb to /platform-tools/ folder
Where are the APKs on the NC to pull them from?
nm: read the post more thoroughly. It's /system/app
Hi friends. I have bought a HCL me U1 tab : 7" display, 512 mb ram, running android 4.0.3 ICS on it. But it does not supports Google play on it and I am pretty upset. Tried to root it with z4root, gingerbreak but nothing works.. Please help.
yup, Im stuck with this tab too, its good tab though.
IT lacks gapps and has few bugs, I hope we get a way to root it soon, or a custom rom will be much better
somebody ..help us
Have you tried SuperOneClick and/or Unlock Root? Both tools are capable of rooting a vast number of devices, so it's worth a shot.
One click ==> yes, will try another one soon. One click doesnt seem to work though. Any help here would be much appreciated
---------- Post added at 01:58 PM ---------- Previous post was at 01:31 PM ----------
ok unlock root gets stuck on 'try to get shell root permissions'. It recognizes the device and all, but gets stuck here
This tablet can be rooted.
Follow this link
http://crazyfreakgamers.com/hclme/viewtopic.php?f=2&t=60
follow below steps to root your HCL Tab U!
********* i am not responsible for any mess with your device do this on your own risk *****************
-Install android SDK and set up under program files (the path will be like C:\Program files/android/android-sdk/platform-tools/adb
-open SDK manager (under android-SDK Folder)
-WHen the list appear, scroll down and download Google USB driver and install it. Then scroll above and download Android 4.0.3 repositories
__-Now turn USB debugging ON in settings
-Download Superuser file from "downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip" then extract the zip file to desktop and you will see 2 folder as "System" and "Meta-INF"
-Connect your Tab via USB
-Open CMD with administrator rights (search CMD then right click on it and select run as administrator)
-Type the following line of code
>cd..
>cd..
>cd..
>cd program files
>cd android
>cd android-sdk
>cd platform-tools
>adb
-While tab is connected to PC, Restart tablet into recovery mode by pressing start and vol+ button at the same time
>adb devices
>adb shell
>adb root (you will see a message "adb is already running as a root")
-Restart the tablet
-Wait till system opens till its home screen appears
>adb devices (you should see your device number)
>adb shell getprop ro.secure (output should be 0)
>adb shell mount -oremount,rw /dev/block/system /system
>adb push c:\users/"username"/desktop/system/bin/su /system/bin/
>adb push c:\users/"username"/desktop/system/bin/su /system/_install/bin/
>adb shell chmod 4777 /system/bin/su
>adb shell mount -oremount,ro /dev/block/system /system
-Download superuser app from market or anyother site and install it. Just open it once
-Download Yaffs explorer from market or anyother site and install it.
-Open the app and Click the drag down button on top and select "/".
-open the 2nd option which will be bin> /system/_install/bin
-Scroll down to and search for SU and you should be able to see that
-Click and hold and it will open up a pop up menu so in that select execute, then tick "As root" option and click Go button
-Superuser dialog box will open adn you have to accept it and you will be permitted to root level access.
-Now download any app which require root permission and use it and you will get a dialog box telleing you "this app requires Superuser permission" then click Yes. Now you should have definatly been granted SU permission.
Enjoy
originally by
Milen Balchandra
Superb_user said:
********* i am not responsible for any mess with your device do this on your own risk *****************
-Install android SDK and set up under program files (the path will be like C:\Program files/android/android-sdk/platform-tools/adb
-open SDK manager (under android-SDK Folder)
-WHen the list appear, scroll down and download Google USB driver and install it. Then scroll above and download Android 4.0.3 repositories
__-Now turn USB debugging ON in settings
-Download Superuser file from "downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip" then extract the zip file to desktop and you will see 2 folder as "System" and "Meta-INF"
-Connect your Tab via USB
-Open CMD with administrator rights (search CMD then right click on it and select run as administrator)
-Type the following line of code
>cd..
>cd..
>cd..
>cd program files
>cd android
>cd android-sdk
>cd platform-tools
>adb
-While tab is connected to PC, Restart tablet into recovery mode by pressing start and vol+ button at the same time
>adb devices
>adb shell
>adb root (you will see a message "adb is already running as a root")
-Restart the tablet
-Wait till system opens till its home screen appears
>adb devices (you should see your device number)
>adb shell getprop ro.secure (output should be 0)
>adb shell mount -oremount,rw /dev/block/system /system
>adb push c:\users/"username"/desktop/system/bin/su /system/bin/
>adb push c:\users/"username"/desktop/system/bin/su /system/_install/bin/
>adb shell chmod 4777 /system/bin/su
>adb shell mount -oremount,ro /dev/block/system /system
-Download superuser app from market or anyother site and install it. Just open it once
-Download Yaffs explorer from market or anyother site and install it.
-Open the app and Click the drag down button on top and select "/".
-open the 2nd option which will be bin> /system/_install/bin
-Scroll down to and search for SU and you should be able to see that
-Click and hold and it will open up a pop up menu so in that select execute, then tick "As root" option and click Go button
-Superuser dialog box will open adn you have to accept it and you will be permitted to root level access.
-Now download any app which require root permission and use it and you will get a dialog box telleing you "this app requires Superuser permission" then click Yes. Now you should have definatly been granted SU permission.
Enjoy
originally by
Milen Balchandra
Click to expand...
Click to collapse
after doing the whole process
when i try to execute su as root (YAFFS EXPLORER)
Super user not asks to allow root access
Nothing happens when i select to run su as root pls help
Can any make cwmflashable zip for dhis tab??? Pleeeesssssee
Sent from my GT-S5360 using xda premium
HCL U1 Help
Anybody having the stock rom of HCL u1 .ftf file???? I desperately need the original stock files...please...atleast gimme the link for it...
Can't find superuser and yaffs explorer
Superb_user said:
********* i am not responsible for any mess with your device do this on your own risk *****************
-Install android SDK and set up under program files (the path will be like C:\Program files/android/android-sdk/platform-tools/adb
-open SDK manager (under android-SDK Folder)
-WHen the list appear, scroll down and download Google USB driver and install it. Then scroll above and download Android 4.0.3 repositories
__-Now turn USB debugging ON in settings
-Download Superuser file from "downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip" then extract the zip file to desktop and you will see 2 folder as "System" and "Meta-INF"
-Connect your Tab via USB
-Open CMD with administrator rights (search CMD then right click on it and select run as administrator)
-Type the following line of code
>cd..
>cd..
>cd..
>cd program files
>cd android
>cd android-sdk
>cd platform-tools
>adb
-While tab is connected to PC, Restart tablet into recovery mode by pressing start and vol+ button at the same time
>adb devices
>adb shell
>adb root (you will see a message "adb is already running as a root")
-Restart the tablet
-Wait till system opens till its home screen appears
>adb devices (you should see your device number)
>adb shell getprop ro.secure (output should be 0)
>adb shell mount -oremount,rw /dev/block/system /system
>adb push c:\users/"username"/desktop/system/bin/su /system/bin/
>adb push c:\users/"username"/desktop/system/bin/su /system/_install/bin/
>adb shell chmod 4777 /system/bin/su
>adb shell mount -oremount,ro /dev/block/system /system
-Download superuser app from market or anyother site and install it. Just open it once
-Download Yaffs explorer from market or anyother site and install it.
-Open the app and Click the drag down button on top and select "/".
-open the 2nd option which will be bin> /system/_install/bin
-Scroll down to and search for SU and you should be able to see that
-Click and hold and it will open up a pop up menu so in that select execute, then tick "As root" option and click Go button
-Superuser dialog box will open adn you have to accept it and you will be permitted to root level access.
-Now download any app which require root permission and use it and you will get a dialog box telleing you "this app requires Superuser permission" then click Yes. Now you should have definatly been granted SU permission.
Enjoy
originally by
Milen Balchandra
Click to expand...
Click to collapse
Where do I download the Superuser app from? Do I have to download it in my PC and then somehow install it into my U1? Or Do I download and install it directly into my U1??
I'm stuck at the superuser app part... And couldn't find yaffs explorer in the HCL ME market... There's no other Market in my tablet yet!
I'm pretty new to such things, It would be great if you help me out!
Thanks!
Rooted HCL ME U1
KingTodi said:
Where do I download the Superuser app from? Do I have to download it in my PC and then somehow install it into my U1? Or Do I download and install it directly into my U1??
I'm stuck at the superuser app part... And couldn't find yaffs explorer in the HCL ME market... There's no other Market in my tablet yet!
I'm pretty new to such things, It would be great if you help me out!
Thanks!
Click to expand...
Click to collapse
This guide is successfully tested by me.
1. You need a 32 bit OS. (I have used 7 Pro x86).
2. Turn USB debugging ‘ON’ in settings of the tablet.
3. Download Superuser hear
Then extract the zip file to desktop:\ & you will see 2 folders as
“System” and “Meta-INF”.
4. Download the drivers. Then connect the tablet & install the drivers
using device manager.
5. Download SuperOneClick!. Extract the archive, go to the folder
named ADB. Open an elevated command prompt download that first
6. CONTINUE WITH THE FOLLOWING COMMANDS.
>adb root (you will see a message “adb is already running as a root”)
>adb devices (you should see your device number)
>adb shell (adb shell will run and daemon tool will also run if this message is not see then close elevated command prompt and restart tablet and continue with following commands)
7. NOW RESTART THE TABLET AND WAIT TILL THE HOME SCREEN APPEARS.NOW
CONTINUE WITH FOLLOWING COMMANDS.
>adb shell getprop ro.secure (output should be 0)
>adb shell mount -oremount,rw /dev/block/system /system
>adb push c:\users/”username”/desktop/system/bin/su /system/bin/
>adb push c:\users/”username”/desktop/system/bin/su /system/_install/bin/
>adb shell chmod 4777 /system/bin/su
>adb shell mount -oremount,ro /dev/block/system /system
8. install busybox first and then check root status with root checker
superuser app,Yaffs explorer,Root Checker can be downloaded from any other site.
Custom Rom HCL ME U1 Tablet
Try this link to Install CWM recovery on HCl ME U1 and also Root The HCl ME U1 tablet
Link: http://tabletkinghcl007.blogspot.in/
jjv007 said:
This guide is successfully tested by me.
1. You need a 32 bit OS. (I have used 7 Pro x86).
2. Turn USB debugging ‘ON’ in settings of the tablet.
3. Download Superuser hear
Then extract the zip file to desktop:\ & you will see 2 folders as
“System” and “Meta-INF”.
4. Download the drivers. Then connect the tablet & install the drivers
using device manager.
5. Download SuperOneClick!. Extract the archive, go to the folder
named ADB. Open an elevated command prompt download that first
6. CONTINUE WITH THE FOLLOWING COMMANDS.
>adb root (you will see a message “adb is already running as a root”)
>adb devices (you should see your device number)
>adb shell (adb shell will run and daemon tool will also run if this message is not see then close elevated command prompt and restart tablet and continue with following commands)
7. NOW RESTART THE TABLET AND WAIT TILL THE HOME SCREEN APPEARS.NOW
CONTINUE WITH FOLLOWING COMMANDS.
>adb shell getprop ro.secure (output should be 0)
>adb shell mount -oremount,rw /dev/block/system /system
>adb push c:\users/”username”/desktop/system/bin/su /system/bin/
>adb push c:\users/”username”/desktop/system/bin/su /system/_install/bin/
>adb shell chmod 4777 /system/bin/su
>adb shell mount -oremount,ro /dev/block/system /system
8. install busybox first and then check root status with root checker
superuser app,Yaffs explorer,Root Checker can be downloaded from any other site.
Click to expand...
Click to collapse
hey can i use 64 bit os?? any other method for 64 bit os??
Hi, I have been using Rom toolbox Lite for a while now and never had a problem, untill I got the "not so great" idea to change the heapsize in build.prop - after reboot the tablet is stuck on Loading - screenshot http://imageshack.com/a/img924/2306/BJbCT1.png
I have tried to reset, reset to factory default, to push back an old build.prop by ADB from prompt, tried the same from QtADB(0.8.0(newer 32bit not availble) - seems I have full access to all folders), even tried modifying the build.prop as root and start QtADB as root then copy it back - nothing has helped.
I have a complete backup(rom dump) made with uberizer, but since I'm not using windows anymore but instead Peach OSI(heavily modified Xubuntu). I'm not really sure what to do now.
My Minami M-750 DualCore A20(allwinner) tablets info is uploaded at specdevice long time ago as I were trying to find others with the same tablet:
http://specdevice.com/showspec.php?id=e5ba-9ce5-0033-c58700000000
It doesn't have custom Rom or custom recovery, but do have an option in recovery to update from external storage(where I can access internal sdcard and external sd) - update from ADB - update from cache.
Anyone have any suggestions?
With kind regards
JBJ
EDIT: Thanks to this article below the problem is now solved.
Note: Step 1 . instead of Eclipse ADT download SDK command line tools https://dl.google.com/android/android-sdk_r24.4.1-linux.tgz
Follow this guide on how to install the SDK: https://androidonlinux.wordpress.com/2013/05/12/setting-up-adb-on-linux/
Step 3. Open a Terminal and shoot this command: —–Note: The “Android” in the command is the folder in which we extracted the SDK in.
cd ~/Android/sdk/platform-tools/
Edit build.prop using ADB
by Louis Matthijssen · July 26, 2014
There are many reasons why you may like to edit your build.prop file. I always edit it in order to lower my DPI, resulting in a bigger looking screen.
You can edit it on the device itself using a file manager or a build.prop editor but it may be more convenient to edit the file using a PC.
Please note that your device has to be rooted to edit the build.prop file.
Download and unzip the Eclipse ADT
Make sure your device has USB debugging enabled
Open a command prompt or terminal and cd to the platform-tools directory:
cd C:\adt-bundle-windows\sdk\platform-tools
Check if your device is recognized:
If it’s not you may install the Google USB driver and try again
adb devices
The device may ask you if the computer is trusted, choose yes
Restart ADB as root:
adb root
Remount /system as rw (read-write):
adb remount
Download build.prop to your pc:
adb pull /system/build.prop
Now you can edit build.prop using your favorite editor
Important: use a plain text editor! I recommend Notepad++ for Windows and Geany for Linux
Upload build.prop to your device:
adb push build.prop /system/build.prop
Fix permissions:
adb shell chmod 644 /system/build.prop
Reboot your device:
adb reboot