Smartphone Pomp P8 - Android General

Hi everybody!
I'm looking for a cheap phone and I have just found this: Pomp P8
http://www.aliexpress.com/store/pro...-TV-entertainment-Cheap/101027_812064010.html
I have been searching for rooting this phone and I haven't found anything!!
I would like to know if it's possible to root this phone.
Thank you very much.
Edit: How to root it, solve problems with Google Play, GPS, dictionary...
Here

vAlmaraz said:
Hi everybody!
I'm looking for a cheap phone and I have just found this: Pomp P8
http://www.aliexpress.com/store/pro...-TV-entertainment-Cheap/101027_812064010.html
I have been searching for rooting this phone and I haven't found anything!!
I would like to know if it's possible to root this phone.
Thank you very much.
Click to expand...
Click to collapse
I'm also looking for this phone, have you found a root way? You have it right now?

Brokn.Down said:
I'm also looking for this phone, have you found a root way? You have it right now?
Click to expand...
Click to collapse
Yes, I have wrotten a thread in HTCManía, an important forum in Spain:
http://www.htcmania.com/showthread.php?p=8312819#post8312819
We are investigating more ways and improvements for this phone.
Now, we have a root method and a gps solution.
Also check this forum:
http://www.forocoches.com/foro/showthread.php?t=3212170
Sorry for my english.

vAlmaraz said:
Yes, I have wrotten a thread in HTCManía, an important forum in Spain:
http://www.htcmania.com/showthread.php?p=8312819#post8312819
We are investigating more ways and improvements for this phone.
Now, we have a root method and a gps solution.
Also check this forum:
http://www.forocoches.com/foro/showthread.php?t=3212170
Sorry for my english.
Click to expand...
Click to collapse
Yep, i view it, is good you speak spanish as i'm also speak spanish, wait for my pm

Already have the phone, myself and there is no need to root the phone. It's already rooted and comes with 'su' installed.
As as said 'su' is there, but you should update 'su' to a newer version as Superuser.apk doesn't work well with the version included in the phone.
Go to androidsu.com/superuser (download latest su and Superuser.apk)
run:
# adb push su /sdcard/
# adb push Superuser.apk /sdcard/
# adb shell
in the shell:
# su
# mount -o rw,remount /system
# cat /sdcard/su /system/bin/su
# chmod 06755 /system/bin/su
# cat /sdcard/Superuser.apk /system/app/Superuser.apk
# logout
# adb reboot
As for the recovery mode, using Power Btn and Volume Down Btn, you can go into recovery mode, no need to re-flash recovery, but you can if you wanna

thejinx said:
Already have the phone, myself and there is no need to root the phone. It's already rooted and comes with 'su' installed.
As as said 'su' is there, but you should update 'su' to a newer version as Superuser.apk doesn't work well with the version included in the phone.
Go to androidsu.com/superuser (download latest su and Superuser.apk)
run:
# adb push su /sdcard/
# adb push Superuser.apk /sdcard/
# adb shell
in the shell:
# su
# mount -o rw,remount /system
# cat /sdcard/su /system/bin/su
# chmod 06755 /system/bin/su
# cat /sdcard/Superuser.apk /system/app/Superuser.apk
# logout
# adb reboot
As for the recovery mode, using Power Btn and Volume Down Btn, you can go into recovery mode, no need to re-flash recovery, but you can if you wanna
Click to expand...
Click to collapse
Thank you very much!
I'll try it!

thejinx said:
Already have the phone, myself and there is no need to root the phone. It's already rooted and comes with 'su' installed.
As as said 'su' is there, but you should update 'su' to a newer version as Superuser.apk doesn't work well with the version included in the phone.
Go to androidsu.com/superuser (download latest su and Superuser.apk)
run:
# adb push su /sdcard/
# adb push Superuser.apk /sdcard/
# adb shell
in the shell:
# su
# mount -o rw,remount /system
# cat /sdcard/su /system/bin/su
# chmod 06755 /system/bin/su
# cat /sdcard/Superuser.apk /system/app/Superuser.apk
# logout
# adb reboot
As for the recovery mode, using Power Btn and Volume Down Btn, you can go into recovery mode, no need to re-flash recovery, but you can if you wanna
Click to expand...
Click to collapse
Thanks, when mine arrive i'll try it
Also wait for a new clean cm9.1 rom for this phone that i'll make

cypress maptur
Sorry, I made a mistake. When using 'cat' you need to use the redirect:
cat /sdcard/su > /system/bin/su
cat /sdcard/Superuser.apk > /system/app/Superuser.apk

Brokn.Down said:
Thanks, when mine arrive i'll try it
Also wait for a new clean cm9.1 rom for this phone that i'll make
Click to expand...
Click to collapse
I prefer a cm10.1 rom

vAlmaraz said:
I prefer a cm10.1 rom
Click to expand...
Click to collapse
Some links for some custom ROMs?

thejinx said:
Some links for some custom ROMs?
Click to expand...
Click to collapse
Unfortunately, I don't know how to build a custom rom, for now.
I can help posting the nexus 4 System dump:
http://dl.atftas.us/OEM/Nexus/Nexus_4/Nexus4_System_Dump.zip

vAlmaraz said:
I prefer a cm10.1 rom
Click to expand...
Click to collapse
Me too but there is not sources for the kernel and is hard to port it

Brokn.Down said:
Me too but there is not sources for the kernel and is hard to port it
Click to expand...
Click to collapse
I don't believe that using CM will work on this phone.

thejinx said:
I don't believe that using CM will work on this phone.
Click to expand...
Click to collapse
Is the best way as the aosp source are incomplete for compile cm10.1 for a generic kernel

BTW, does anybody have problem with the GPS? I've tried Sygic and Google Maps and not getting any satellites, or at least no very fast.
I've tried the how-to for the GPS from htcmania.com, but doesn't really help. Also tried FasterGPS app and nothing.
Please let me know if you know a good fix.
Also, does anybody know how to unlock the bootloader? Recovery can't be re-written if the bootloader is not unlocked (or at least thats what I believe).

Hello.
Sent from my SCH-I605 using Xparent BlueTapatalk 2

thejinx said:
BTW, does anybody have problem with the GPS? I've tried Sygic and Google Maps and not getting any satellites, or at least no very fast.
I've tried the how-to for the GPS from htcmania.com, but doesn't really help. Also tried FasterGPS app and nothing.
Please let me know if you know a good fix.
Also, does anybody know how to unlock the bootloader? Recovery can't be re-written if the bootloader is not unlocked (or at least thats what I believe).
Click to expand...
Click to collapse
Recovery: maybe this could help:
http://bm-smartphone-reviews.blogspot.com.es/2012/05/mt6575-flashing-tutorial.html
http://bm-smartphone-reviews.blogspot.com.es/2012/02/complete-guide-to-clockworkmod-recovery.html

vAlmaraz said:
Recovery: maybe this could help:
http://bm-smartphone-reviews.blogspot.com.es/2012/05/mt6575-flashing-tutorial.html
http://bm-smartphone-reviews.blogspot.com.es/2012/02/complete-guide-to-clockworkmod-recovery.html
Click to expand...
Click to collapse
Yeah, I knew this, but what about the GPS? Can't get it to work.

thejinx said:
Yeah, I knew this, but what about the GPS? Can't get it to work.
Click to expand...
Click to collapse
Sorry, I haven't tried GPS yet. Maybe this week I could have some free time and I can try it.

vAlmaraz said:
Sorry, I haven't tried GPS yet. Maybe this week I could have some free time and I can try it.
Click to expand...
Click to collapse
Would it be possible to dump the ROM from your phone and uploaded someplace? I'm thinking is the ROM, but don't have the original one.

Related

Rooting the Eris

Has anyone been able to root thier Erie yet? If so how did you do it? Or can anyone point me in the right direction to get started. Thanks for the help.
I think it'll be at least a few weeks. Someone needs to get the recovery image and mod it as they did with the Hero. I think.
so is anyone working on this? if you give me instuctions i will dump my phone and post it, if that will help? i would really just like to be able to tether over wifi when needed without having to pay out the ear for it.
Is it that different from the Sprint's Hero? Try the current method...
herzzreh said:
Is it that different from the Sprint's Hero? Try the current method...
Click to expand...
Click to collapse
I'm concerned that the image from the Hero will cause problems since it's different carrier etc
The method used to root isn't carrier dependent. You probably won't want to load MoDaCo's current ROM as it is Sprint specific, but assuming the kernel build is the same you may be able to gain root with the asroot2 script.
To clarify, 'rooting' is not the same as loading a custom ROM. One begets the other, but loading a custom ROM isn't a requirement, just a door that gets opened when you gain root access to your phone.
Assuming everything else is the same on the phone, the Amon_Ra recovery bootloader should work as well.
If asroot2 works then we can flash a new recovery image, you can dump your ROM, and I can do a MCR version.
P
would i still use the recovery image that is posted for the hero? or would i stop at that step when rooting?
binny1007 said:
would i still use the recovery image that is posted for the hero? or would i stop at that step when rooting?
Click to expand...
Click to collapse
If you use the recovery image for the hero and it doesn't work, it's not usually a big deal.
Just pull out the battery to restart your phone normally. Since the recovery image is separate from the rom, replacing the first does not affect the latter.
binny1007 said:
would i still use the recovery image that is posted for the hero? or would i stop at that step when rooting?
Click to expand...
Click to collapse
Follow the rooting instructions to the letter, all the way through. Just don't flash a new rom if successful.
You can use the recovery image posted for the Hero.
ok i am following the instructions and this is what i am getting? what is going wrong?
C:\AndroidSDK\tools>adb shell
$ chmod 0755 /data/local/asroot2
chmod 0755 /data/local/asroot2
$ /data/local/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
[1] Killed /data/local/asro
$ mount -o remount,rw -t yaffs2 /dev/block/mtd
mount -o remount,rw -t yaffs2 /dev/block/mtdbl
mount: Operation not permitted
$ cd /system/bin
cd /system/bin
$ cat sh > su
cat sh > su
cannot create su: read-only file system
$ chmod 4755 su
chmod 4755 su
Unable to chmod su: No such file or directory
The eris and droid can't use that exploit unfortunately, you'll have to wait until there's another way in
binny1007 said:
ok i am following the instructions and this is what i am getting? what is going wrong?
C:\AndroidSDK\tools>adb shell
$ chmod 0755 /data/local/asroot2
chmod 0755 /data/local/asroot2
$ /data/local/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
[1] Killed /data/local/asro
$ mount -o remount,rw -t yaffs2 /dev/block/mtd
mount -o remount,rw -t yaffs2 /dev/block/mtdbl
mount: Operation not permitted
$ cd /system/bin
cd /system/bin
$ cat sh > su
cat sh > su
cannot create su: read-only file system
$ chmod 4755 su
chmod 4755 su
Unable to chmod su: No such file or directory
Click to expand...
Click to collapse
You guys and Bell South...sounds like Sprint had the only vulnerable CDMA version.
You guys will have to wait for a new "asroot" type file...a new exploit to get you guys access.
well that sucks, so there is no other way around this right now? Or if anyone needs a ginnie pig i am more than happy to help.
thecodemonk said:
You guys and Bell South...sounds like Sprint had the only vulnerable CDMA version.
You guys will have to wait for a new "asroot" type file...a new exploit to get you guys access.
Click to expand...
Click to collapse
That's what I thought. Hopefully since the hardware is so similar it wont take long.
Unfortunately hardware is barely a glimmer in this equation - the expliots used to gain root are software, usually kernel bugs.
Something will turn up soon.hopefully.
binny1007 said:
well that sucks, so there is no other way around this right now? Or if anyone needs a ginnie pig i am more than happy to help.
Click to expand...
Click to collapse
Just remember, while it's unlikely, any of these actions could theoretically brick your phone...be aware of the risks!
Have you attempted the flashrec method?
Drop the Recovery Image from here onto your sd card
http://forum.xda-developers.com/showthread.php?t=581521
Download the apk from here and install it on your phone:
http://zenthought.org/content/project/flashrec (download it from your phone's webbrowser and open the file...if that doesn't work, download astro file explorer from the market and try again).
Once you open flashrec, click on the "backup" link and then type in the path to your recovery image (most likely: /sdcard/recovery-RA-heroc-v1.2.3.img)
Then flash and try to reboot into recovery mode (power off, then either home+power, volume down+power, or camera+power...depends on who you ask, one of those should get you into the recovery image where you'll see an option for nandroid, that's how you'll know it was a success).
If you reboot and it doesn't work or it freezes, pop out the battery and boot normally...shouldn't hurt anything (though if you want to be more safe, I'd wait until we got the RUU for whatever carrier you're on (Verizon/Telus/etc)). Currently the Sprint RUU is the "get out of jail" card that's saved a bunch of people.
Just remember, while it's unlikely, any of these actions could theoretically brick your phone...be aware of the risks!
thecodemonk said:
You guys and Bell South...sounds like Sprint had the only vulnerable CDMA version.
Click to expand...
Click to collapse
Cellular South
thecodemonk said:
Have you attempted the flashrec method?
Click to expand...
Click to collapse
It doesn't use the same exploit as asroot2?
markachee said:
Cellular South
It doesn't use the same exploit as asroot2?
Click to expand...
Click to collapse
Sorry, Cell South, Bell south...(can you tell I'm not from around there? )
I have no idea if it does...but I figured it can't hurt to try eh? Because if it works, wouldn't that be awesome?

How to root the Droid 2

All credit for the binary goes to Sebastian Krahmer at http://c-skills.blogspot.com/. Please see fit to donate via Paypal to [email protected]
If you want a simpler 'one-click' process, go to this thread: Easier 1-2-3 Droid 2 Root for Windows / Linux / Mac
***NOTE: Proceed at your own risk. I and the providers of this code are not responsible for anything you do to your phone!***
Setup:
- Install adb (here) and Motorola drivers for windows(32-bit or 64-bit)
- Download attached archive
- Extract to a directory, I used c:\Droid2Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open command prompt
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- cd c:/Droid2Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two) to c:/Droid2Root
- cd c:/wherever-your-sdk-tools-folder-is
- adb kill-server
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
- exit
I'm sure there are certain steps that could be streamlined or eliminated, so please feel free to make a suggestion and I'll edit the post.
Additional thanks to @rainabba and AllDroid.org for their excellent Droid X rooting tutorial, which assisted me greatly in this process.
waiting for a recovery, glad to see its rooted
Android n00b here, I can remove the Verizon crapware with this right? And tether?
thelolotov said:
Android n00b here, I can remove the Verizon crapware with this right? And tether?
Click to expand...
Click to collapse
yes and yes
thelolotov said:
Android n00b here, I can remove the Verizon crapware with this right? And tether?
Click to expand...
Click to collapse
I wouldn't remove anything yet since we don't have a sbf file to recover from partial bricks. However, tethering and any other apps that require root can be used now.
I'm new to doing this all the adb way.
When you say extract to a directory what do you mean to extract. After it downloads the achive files its done.....
i understand the rest of the commands but im lost there
Hmm, alright, that's still worth it, will I lose my data/have to hard reset to root?
Right click the downloaded archive and "extract files". You need to do this so adb can push them to the phone.
thelolotov said:
Hmm, alright, that's still worth it, will I lose my data/have to hard reset to root?
Click to expand...
Click to collapse
Nope, it just gives you access. Nothing deleted.
I'm retarded i didnt realize it was attached to the post, i thought it was what adb downloaded when i first opened it cause it called them archives.
cannot access
I got as far as pushing super user su and busy box onto my phone but it says that system in read only.. how do i fix this?
Anybody actually try this?
Hello,
I am following your directions and when I get to the "adb push Superuser.apk" step I receive the following error:
"failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system"
I get this same error for the other adb push steps that follow.
Edit: To verify, I get a # shell.
Edit 2: I tried pushing the Superuser.apk to /data/local/tmp then cp to /system/app/, this also popped up a read-only file system error.
I'm currently trying it.
I have a 64 bit driver on my computer that i used to use for my D1 but it doesn't recognize my D2 when doing adb devices and i cant install the 32 bit driver
GSletta said:
I got as far as pushing super user su and busy box onto my phone but it says that system in read only.. how do i fix this?
Click to expand...
Click to collapse
Did you verify you have the # prompt three steps before that?
Yeah i get the # but it wont let me push superuser su and busybox
GSletta said:
Yeah i get the # but it wont let me push superuser su and busybox
Click to expand...
Click to collapse
Weird.. I didn't need to mount the system manually, but let me if there's a step I left out.
and some more screens (feel free to use in first post):
http://i.imgur.com/nPllt.jpg
http://i.imgur.com/COTEA.jpg
http://i.imgur.com/open3.jpg
djh816 said:
and some more screens (feel free to use in first post):
http://i.imgur.com/nPllt.jpg
http://i.imgur.com/COTEA.jpg
http://i.imgur.com/open3.jpg
Click to expand...
Click to collapse
Did you add any steps to mount the system? I don't believe I did, but it seems others are finding it to be read-only.
jerseyh22accord said:
I'm currently trying it.
I have a 64 bit driver on my computer that i used to use for my D1 but it doesn't recognize my D2 when doing adb devices and i cant install the 32 bit driver
Click to expand...
Click to collapse
Don't know if it will help you, but if it's anything like the DInc, you could just use the SDK's drivers and add a few device identifier lines to the INF file before installing them.

Samsung sidekick 4G

Has anyone begun working on rooting and customizing roms yet? I know the device isn't out for a week or so but I would figure I would ask. My vibrant I so much better rooted and I wanted the same experience on this sidekick.
Sent from my SGH-T839 using XDA App
Wreximus said:
Has anyone begun working on rooting and customizing roms yet? I know the device isn't out for a week or so but I would figure I would ask. My vibrant I so much better rooted and I wanted the same experience on this sidekick.
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
i wish i knew how to do this, but if i can't figure it out, i'm sure others will soon.
Just got mine last night. The usual Samsung trick with rageagainstthecage-arm5.bin works great.
abliss said:
Just got mine last night. The usual Samsung trick with rageagainstthecage-arm5.bin works great.
Click to expand...
Click to collapse
Oh really? Cool. So far all I've used is one-click root for the Samsung Epic.... is this similar? I'll check it out, thanks!
Has anyone tried using SuperOneClick yet?? I will probably try in a bit and post back with my results..
Ok... well I didn't try SuperOneClick, but I did root it via the rageagainstthecage exploit...
Want to help me do the exploit on my SK4G to root it man ?
Give me instructions ?!
I got it working on mine too. The basic steps were
1) enable debug USB mode on your phone
2) install Samsung drivers for the phone - right now Samsung's site seems to not have a choice for the Sidekick 4G's model (SGH-T839), but I grabbed the drivers for the Vibrant (at www .samsung.com/us/support/downloads/SGH-T959ZKDTMB) and they worked.
3) get adb shell working on your PC (Google it)
4) download the rageagainstthecage-arm5.bin and Superuser packages from the links in this page: wiki.cyanogenmod.com/index.php?title=HTC_Hero_%28CDMA%29:_Full_Update_Guide (be sure to unzip the files into the directory where your adb.exe program is unless you've put it in your path)
5) reboot your phone and plug it in
6) adb push rageagainstthecage-arm5.bin /data/local/tmp
7) adb shell
8) cd /data/local/tmp
9) chmod 755 rageagainstthecage-arm5.bin
10) ./rageagainstthecage-arm5.bin
11) wait until you get booted back out to your DOS command prompt
12) adb kill-server
13) adb start-server
14) adb shell
15) you should now be at a # prompt. The first few times I tried, I wasn't - I was at $. Doing this from a fresh boot seemed to be the trick. Reboot your phone and try again if you're getting a $.
16) mount -o remount,rw /dev/block/stl9 /system
17) exit
18) adb push su /system/xbin
19) adb shell chmod 4755 /system/xbin/su
20) adb push Superuser.apk /system/app
21) adb shell mount -o remount,ro /dev/block/stl9 /system
22) exit
23) reboot the phone then run an app that requests root, such as Root Explorer, to verify
(p.s. sorry for having to mangle the URL's above, XDA won't let me include links since I haven't posted 8 times yet)
josby said:
16) mount -o remount,rw /dev/block/st19 /system
18) adb push su /system/xbin
19) adb shell chmod 4755 /system/xbin/su
20) adb push Superuser.apk /system/app
21) adb shell mount -o remount,ro /dev/block/st19 /system
Click to expand...
Click to collapse
Just to note, on step 16 and 21... it is /dev/block/stl9 rather than st19
Also, after step 20, I had to run the following commands for the superuser application to grant root privledges to applications..
adb shell echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
adb shell echo "root::0:" > /etc/group
Awesome to see it being rooted so fast.
I'm really interesting in getting this phone but I'm not in the US. Does anyone know if the phone will work outside US?
brenix said:
Just to note, on step 16 and 21... it is /dev/block/stl9 rather than st19
Click to expand...
Click to collapse
Dang, good catch, thanks. That's what I get for not copying and pasting from my terminal window...stupid, since I was just chastising two people at work for making the same mistake yesterday. I've edited the original post to prevent problems for people who might start before reading the entire thread.
Interesting about having to create a passwd and group file...I've only run a few root apps so far, but they've worked without me doing this. I wonder if it's app-specific.
Now to start removing some of the damn bloatware this thing comes with!
19) adb shell chmod 4755 /system/xbin/su
i get stuck on there it says unable to chmod no such file or directory . there's SU in my android-sdk/tools
i'm so glad this thing got rooted. i used to be a scene kid with a kick. i dont have this phone, i doubt i'm going to get this phone considering the sensation is droppin soon.... but for nostalgia purposes, i'm glad it got rooted. now you can really hack it!!!
not like the old ones!!
Good looking out...I rooted mine earlier today. What version of Clockworkmod Recovery are you all using?
fawkReviewz said:
19) adb shell chmod 4755 /system/xbin/su
i get stuck on there it says unable to chmod no such file or directory . there's SU in my android-sdk/tools
Click to expand...
Click to collapse
Double-check your step 18...that's the step that copies the su file from your computer onto the phone. I forget the exact output format, but it shows you a Kb/second number of how fast the file transfer went when it finishes successfully.
droctii said:
Good looking out...I rooted mine earlier today. What version of Clockworkmod Recovery are you all using?
Click to expand...
Click to collapse
I'm not brave enough to try putting the ClockworkMod for one of the Samsung devices on the list onto mine, for fear of bricking it. Don't know enough about that works as far as hardware differences go.
I have removed the APK's listed below from /system/app with no apparent ill-effects. Not that YOU should remove them necessarily - just that they're things I don't have a need for:
AccountAndSync.apk
AmazonMp3.apk
AppPack.apk
DriveSmart.apk
DriveSmartHelper.apk
install_flash_player.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
Memo.apk
MiniDiary.apk
MobileBackup.apk
MyFiles.apk
PhoneSetupWizard.apk
Twitter-2.0.1-121.apk
vvm-signed.apk
Though there must be something I don't fully understand, because even after a reboot, Amazon MP3 and AppPack are still on my phone, and they still work.
FYI, don't remove Settings.apk - I got stuck in a loop where the launcher kept crashing then reloading itself (thank goodness I was able to put it back in place with adb).
Can anyone tell me if Setcpu works for them?
Ace42 said:
Can anyone tell me if Setcpu works for them?
Click to expand...
Click to collapse
Appears to work fine.. no crashes although the Max Hz is 1000. U can still raise the Min Hz.
Sent from my Nexus S using XDA App
Can someone post a full:
ls of / and /dev/block and /efs
Thanks
Will this phone get a proper sub-forum on xda?

ADB question

I have read many posts about ADB push/remount permission issues, etc. But unfortunately I still have not figured out what's wrong with my situation. First of all, I don't have a micro SD card, so I have to push files directly to the phone memory.
I firstly tried "adb push" but seems it doesn't work for me
$ adb push email.apk /system/app
failed to copy 'email.apk' to '/system/app/email.apk': Read-only file system
Click to expand...
Click to collapse
Then I searched online and people said you need to remount first. Then I got the infamous permission problem
$ adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Then I tried open shell first. no go
$ adb shell
$ mount -o remount rw system/app
mount: Operation not permitted
Click to expand...
Click to collapse
I searched more and found it can get su permission so to make things work. But when I hit "su(enter)" after open adb shell, I don't see the "#" showing up but still got an error message after waiting for a while
$ adb shell
$ su
Permission denied
Click to expand...
Click to collapse
Any one can please tell what's wrong with my operation? I rooted my G2x but didn't flash it. I installed the ROM manager and installed CWM but didn't proceed to reboot into recovery mode.
tangyoulei said:
I have read many posts about ADB push/remount permission issues, etc. But unfortunately I still have not figured out what's wrong with my situation. First of all, I don't have a micro SD card, so I have to push files directly to the phone memory.
I firstly tried "adb push" but seems it doesn't work for me
Then I searched online and people said you need to remount first. Then I got the infamous permission problem
Then I tried open shell first. no go
I searched more and found it can get su permission so to make things work. But when I hit "su(enter)" after open adb shell, I don't see the "#" showing up but still got an error message after waiting for a while
Any one can please tell what's wrong with my operation? I rooted my G2x but didn't flash it. I installed the ROM manager and installed CWM but didn't proceed to reboot into recovery mode.
Click to expand...
Click to collapse
you need to look at your phone and allow superuser app to grant permission
crazythunder said:
you need to look at your phone and allow superuser app to grant permission
Click to expand...
Click to collapse
su app? how should I set it? I didn't see anyone mentioned that. Do you care to give a bit more details? Thanks.
I think I figured out. I have to manually run the superuser app and let it say in active. Then when I type in "adb shell" the app on the handset will ask my permission. Thanks for the reminder.
Plus I am doing the following as the following that I read from another thread
adb shell
$ su
# mkdir /data/yourname
# chmod 777 /data/yourname
# exit
$ exit
adb push gps.conf /data/yourname
adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock6 /system (copy biggrin.gif)
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system (copy biggrin.gif)
# mv /data/yourname/gps.conf /system/etc
Click to expand...
Click to collapse

[Q] Rooting the motorola atrix 2

i tried a few ways to root my atrix 2 but i cant. I tried super one click, lazy one click (or however its called) and i cant root it i have a mac someone help! is there another way to root the atrix 2?
I heard there was an app that can do it too. Its in this forum somewhere.
I used the manual method on my Mac with no issues, did it twice actually.
What error messages are you getting?
I'll be home in about 15 mins and I can help further
Sent from my MB865 using Tapatalk
If all else fails, you could always reflash the fkz's, than try to root again, but the problem here is that you have a mac. Perhaps borrow a friends pc, or install Windows through bootcamp. (I wouldn't recommend a Virtual Machine though).
OK so if you used a root tool in the first place then I assume that-
-You have adb set up
-You have the necessary files to push (zerg, su, superuser.apk)
If you have no idea of what I'm talking about then just look around the folders of the root tools and you'll find them.
OK, here's what you have to do:
1. Open up a terminal.
2. CD (change directory) to where you have the necessary files located, ex. "cd ~/Desktop/" if they're on the desktop
3. Enter the following commands (one line at a time):
Code:
adb shell
cd /data/local
rm ./temp/*
exit
This removes temporary files created by the root exploit.
4. Now enter these commands (again, one at a time)
Code:
adb push zerg /data/local
adb push su /data/local
adb push Superuser.apk /data/local
adb shell
cd /data/local
chmod 777 zerg
./zerg
adb shell
mount -o rw,remount /dev/null /system
cat /data/local/su > /system/bin/su
cat /data/local/Superuser.apk > /system/app/Superuser.apk
chmod 4755 /system/bin/su
chmod 4755 /system/app/Superuser.apk
reboot
I hope you understand this... good luck getting complete root.
thread moved to general forum
If you find a specific android app that can do this for you and you can post it in the OP, I will gladly move it down to its original location. Until there, it doesnt belong in the app and themes forums.
What's your android version ?
Deliberate said:
I heard there was an app that can do it too. Its in this forum somewhere.
Click to expand...
Click to collapse
Unfortunately that app seems to have only been in the market and was recently removed... I tried looking for it today. Please correct me if I'm wrong!
jpumford said:
Unfortunately that app seems to have only been in the market and was recently removed... I tried looking for it today. Please correct me if I'm wrong!
Click to expand...
Click to collapse
You're correct, the app was written by an author who made it just to make money... he never even tested it. He took it down because it didn't work.
Most important question of all here: What OS are you running on your Mac?
If you're running 2.3.6 you can't root yet. You need to downgrade to 2.3.5

Categories

Resources