Hi to everyone,
after two weeks I wrecked my Alcatel Tablet (Telekom Puls).
The Android system recovery 3e offers me among others:
apply update from ADB, sdcard or cache
Root and USB-Debugging are activated.
After starting >adb device< on my windows 7 (USB) I get a correct answer.
The copied file build.porp misses the file permissions I assume.
Any hints and suggestions are welcome.
Thanks in advance.
rfine said:
Hi to everyone,
after two weeks I wrecked my Alcatel Tablet (Telekom Puls).
The Android system recovery 3e offers me among others:
apply update from ADB, sdcard or cache
Root and USB-Debugging are activated.
After starting >adb device< on my windows 7 (USB) I get a correct answer.
The copied file build.porp misses the file permissions I assume.
Any hints and suggestions are welcome.
Thanks in advance.
Click to expand...
Click to collapse
Hello,
If there is a permission issue, You may push your build.prop and give it correct permissions according to these commands.
Code:
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
adb reboot
-Vatsal
adb sideload
Thank you for your post, Vatsal.
Before I start the adb prompt on the pc the following message I get from the tablet:
Now send the package you want to apply to the device with adb sideload <filename> ...
Related
This is an FAQ for the Huawei Ideos as there have been many questions on how to do the same things. Hopefully this should help. There are other FAQs but this one tries to compile as many as it can into one FAQ.
Feel free to reply to this if there are any questions or if you want me to make any additions. The FAQ won't be complete to begin with but I will add as I get time.
One thing I will say is that I WON'T TAKE RESPONSIBITY IF YOU DAMAGE YOUR PHONE. I AM PROVIDING THE INFORMATION AND WILL TRY TO HELP YOU IF SOMETHING BAD HAPPENS BUT I CAN'T TAKE ANY RESPONSIBILITY
1. How to root the IDEOS
This can be done quite simply by adapting what quail wrote:
There is a couple away you can go about gaining root access with this phone I have tested all 3 ways but only had success with 2 of them.
a) You can download 'z4root' from here (WORKS)
b) Search the XDA forums for 'SuperOneClick' which requires mono to work on Linux. I have read people that have had success with 'SuperOneClick' but that was not the case for me. (HAVEN'T CHECKED)
c) My preferred method: (HAVEN'T CHECKED)
Prerequisite:
knowledge of Linux and Terminal
knowledge of ADB (guide available in forums)
I did all this using Debian (testing) 64bit, Android SDK.
Creating correct permissions to access the phone via USB:
i) create
Code:
/etc/udev/rules.d/51-android.rules
ii) in the file put
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
iii) then
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
iv) restart udev or reboot
Downloading and/or Installing required software:
1) Downloading and installing the android-sdk from: developer.android.com/sdk/index.html
2) Downloading and extracting 'SuperOneClick' (you will only need these 5 files: rageagainstthecage, sqlite3, su, busybox and superuser.apk)
3) Copy rageagainstthecage, sqlite3, su, busybox and superuser.apk into the platform-tools directory of android-sdk. Put phone in debug mode.
4) From a terminal (command line) change to the android/platform-tools directory and carefully do these steps.
Check to see if adb can see your phone properly:
Code:
./adb devices
You should see the serial number of you device, if you see bunch of '?' you have done something wrong.
Now for the fun part rooting the phone: <= no phun intended hehe
Code:
./adb push rageagainstthecage /data/local/tmp/rageagainstthecage
Code:
./adb shell
Code:
cd /data/local/tmp
Code:
chmod 0755 rageagainstthecage
Code:
./rageagainstthecage
5) Now wait until you get kicked out from adb before you do the following:
Code:
./adb shell
If everything worked now you should see a "#" instead of the "$" you saw previously in the adb shell which means you shouldn't get "permission denied" in the following steps:
Code:
mount -o rw,remount /dev/block/mdtblock4 /system
Code:
exit
Code:
./adb push su /system/bin/su
Code:
./adb push busybox /system/bin/busybox
Code:
./adb push sqlite3 /system/bin/sqlite3
Code:
./adb push Superuser.apk /system/app/Superuser.apk
Code:
./adb shell
Code:
cd /system/bin
Code:
chmod 4755 su
Code:
chmod 4755 busybox
Code:
chmod 4755 sqlite3
Code:
./adb reboot
Now you should be able to use apps like 'Cache Cleaner NG', 'Root Explorer', 'SetCPU' etc that require root access to work correctly.
Enjoy
2. How to flash the Ultrakiller Recovery Image
Now this has been covered many times but there have been a lot of problems with the BSOD on the IDEOS. A few days ago Ultrakiller came up with a solution that works regardless of the LCD type. Now this was distributed as an IMG file so many people were confused so here is a link to one with everything you need included. All I did was remove the amon'ra image and copied the Ultrakiller recovery IMG to the folder and edited the scripts to point to the new file.
After you download the file:
* Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys (Yes, bootloader is just the IDEOS logo) WHILE YOUR DEVICE IS PLUGGED IN
* WINDOWS - double click 'install-recovery-windows.bat'
* MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-mac.sh' followed by './install-recovery-mac.sh'
* LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-linux.sh' followed by './install-recovery-linux.sh'
See Q3 if you have Windows and the prompt hangs on "Waiting for Device"
3. How to solve problems with drivers on Windows in bootloader mode?
1. Unplug your phone
2. Download and install PDANet from here - at the end of the setup it will tell you to plug in your phone - do that
3. Put the phone into bootloader (See Q2 above)
4. Go to device manager and right click on "Android 1.0" and click "Update drivers"
5. Click "No, not this time" and Next
6. When it asks you where to look for drivers point it to PDANet's install location
7. Hopefully it should find the driver and prompt you to install it - it will take some time
8. You can now access your device in bootloader!
Thanks to the following people:
Quail for the base of the guide and the ROM I'm using - it's amazing BTW
Ultrakiller for the recovery image
Changelog:
21/01/2010: Initial writeup
22/01/2010: Added Q3 and made some minor changes
i unfortunately deleted a system app and upon restarting my phone it wont boot.....it keeps hanging at the startup and reboots.. help me how to system restore...
Hi - the Ultrakiller recovery IMG in the ZIP from the Link above is "Ultrakiller.img.img". Dunno if it didnt work cause of this - sry didnt test, just downloaded new Ultrakillers "UltraJack-Recovery_v4.6.2.img", saved into that folder and changed the .bat to "fastboot-windows.exe flash recovery UltraJack-Recovery_v4.6.2.img" and it worked for me Even superuser.apk didnt work for usb-root but z4root does it perfect and DroidExplorer showing files now .
Thanks so far to all investing their time here
P.S.: the HUAWEI background of Ultrakillers recovery is very delicious
General guide to Flash ROM
Can you please provide a detailed guide for flashing Huawei Ideos. Because it is super guide. So it must contain this topic also.
I want to flash official ROM on following link:
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS
Waiting for your response
yrnehukuht said:
i unfortunately deleted a system app and upon restarting my phone it wont boot.....it keeps hanging at the startup and reboots.. help me how to system restore...
Click to expand...
Click to collapse
Dear have u find out the solution of this problem?? COZ im also suffering from this if u find it then plz tell me [email protected]
I have downloaded a rom from xda-developers wiki from this link
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS
then updated my device software by going in to update mode(press vol up + end key + power button) .
This step returned me my original recovery.
But I am not going to recommend it bcoz i am facing problems like my cd drive which is automatically displayed has become inaccessible.
I am having problem to copy files to sd card.
My upgrade mode is not working now.
all these things were working immediately after the above mentioned process but I am now stuck with these things.
I think it is because i have flashed lower version number of rom on phone.
If you want to recover recovery mode only then I have successfully flashed UltraJack-Recovery 5.2.1 from this link
http://forum.xda-developers.com/showthread.php?t=860189&page=24
Inform about your progress
Thanx. Very useful
Hi guys. I am in a lot of trouble with my ideos.
Tried installing a custom ROm using ROM manager and it failed, although the original ROM is still there and its booting up and working perfectly.
However, when i try to boot into recovery, only the lit blackscreen shows.
I have tried everything from running ULTRAjack recovery on windows(which only shows 'waiting for device' on cmd, with the pdanet drivers installed) to ubuntu(which shows 'waiting for device' on Amon-ra recovery and permission denied on ULTRAjack).
Could it be i didnt root the device properly since i used z4 root?
Any more ideas?
900/2100 or 850/1700/1900/2100
Hello, How do I tell which sub-model my U8150 is please? Either HSDPA 900 / 2100 / AWS or HSDPA 850 / 1900 / 2100 / 1700. baseband = 22201003; build no.= U8150V100R001C183B825; IMEC = 355093040562676; IMEC-SV = 39.
Check out your fcc id suffix. I have heard there is a b version and a d version.
hi do flashing many roms affects my ideos mobile?
netskink said:
Check out your fcc id suffix. I have heard there is a b version and a d version.
Click to expand...
Click to collapse
All I got is a U8510-1, no letter... any thoughts?
Unlock u8150
Hello.
i have a T-Mobile Ideos u8150, also known as Comet.
it is locked to T-Mobile and requests a pin code when using another sim card.
is there a way to unlock the phone?
please help me...
thank you.
Enable USB Debugging & One Click Root with Unlock Root Tool
Can any one plz root this tablet...... M so depressed coz it doesn't include google play if it can be rooted....i could buy dis.....
successfully rooted HCL ME U1 Tablet
jeevan92ultimate said:
Can any one plz root this tablet...... M so depressed coz it doesn't include google play if it can be rooted....i could buy dis.....
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. Then extract the zip file to desktop :\ & you will see 2 folders as “System” and “Meta-INF”.
4. Download the drivers from here. 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 there using this.
6. Continue with the following commands:
Code:
>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) 7. Now restart the tablet & wait till the home screen appears. Now continue with the following commands:
Code:
>adb shell getprop ro.secure (output should be 0)
>adb shell mount -oremount,rw /dev/block/system /system
>adb push d:\system/bin/su /system/bin/
>adb push d:\system/bin/su /system/_install/bin/
>adb shell chmod 4777 /system/bin/su
>adb shell mount -oremount,ro /dev/block/system /system 8. Exit adb, disconnect the tab, restart it again.
9. Open the new Superuser app just once.
10. Download apks of BusyBox, Google Play & Titanium Backup (Google is your friend!!).
11. Install BusyBox first, then check the rooting status with Titanium Backup. After that, install Google Play.
Move your discussion into device forum.
If it doesn't have it, move it to Android Hacking and Development
Trolls, trolls everywhere
ppero196 said:
Move your discussion into device forum.
If it doesn't have it, move it to Android Hacking and Development
Trolls, trolls everywhere
Click to expand...
Click to collapse
Sorry, ppero196. OK
Hello Friends my previous question went totally unnoticed http://forum.xda-developers.com/moto-g/help/restore-downloading-stock-firmware-t2949283
But I hope you will help me this time Moto G xt1033
It is not ROOTED..
I have a couple of saved WiFi passwords in my phone. I forgot them and want to retrieve them now. I know /data folder can not be accessed on non-rooted phone. So I tried it by using adb. I have latest adb, fastboot and Motorola drivers. So let's start. Usb debugging is enabled and my phone is recognised when I use "adb devices" commands. Then I type "adb pull /data/misc/wifi/wpa_supplicant.conf" but it says it does not exist. I have been trying this for many days but I don't want to root my phone for some time. I browsed Internet and all sites say adb pull or adb push can be used successfully without root. Adb pull from /SDcard is always successful but not from /data folder. When I try to open /data/misc or data/misc/WiFi using adb commands it says permission denied. Adb push is also unsuccessful in /data folder. I made a fake wpa_supplicant.conf file in C:\wp folder and then I typed "adb push C:\wp\wpa_supplicant.conf /data/misc/WiFi (I also tried /data/misc/wifi/wpa_supplicant.conf) but it says permission denied. I also can't make these folders readable writable as it says permission denied. Later I also tried using terminal emulator on my phone but no gain. Please help me how can I make proper use of adb without rooting my phone. I don't type commands wrong as I have visited countless sites for many days. And sorry for my English mistakes, if any.
Thanks.
Guru.Eclairs said:
Hello Friends my previous question went totally unnoticed http://forum.xda-developers.com/moto-g/help/restore-downloading-stock-firmware-t2949283
But I hope you will help me this time Moto G xt1033
It is not ROOTED..
I have a couple of saved WiFi passwords in my phone. I forgot them and want to retrieve them now. I know /data folder can not be accessed on non-rooted phone. So I tried it by using adb. I have latest adb, fastboot and Motorola drivers. So let's start. Usb debugging is enabled and my phone is recognised when I use "adb devices" commands. Then I type "adb pull /data/misc/wifi/wpa_supplicant.conf" but it says it does not exist. I have been trying this for many days but I don't want to root my phone for some time. I browsed Internet and all sites say adb pull or adb push can be used successfully without root. Adb pull from /SDcard is always successful but not from /data folder. When I try to open /data/misc or data/misc/WiFi using adb commands it says permission denied. Adb push is also unsuccessful in /data folder. I made a fake wpa_supplicant.conf file in C:\wp folder and then I typed "adb push C:\wp\wpa_supplicant.conf /data/misc/WiFi (I also tried /data/misc/wifi/wpa_supplicant.conf) but it says permission denied. I also can't make these folders readable writable as it says permission denied. Later I also tried using terminal emulator on my phone but no gain. Please help me how can I make proper use of adb without rooting my phone. I don't type commands wrong as I have visited countless sites for many days. And sorry for my English mistakes, if any.
Thanks.
Click to expand...
Click to collapse
Hey mate, that folder is off limits unless you have root (to protect against malicious apps modifying stuff)
Cheers
itouchables said:
Hey mate, that folder is off limits unless you have root (to protect against malicious apps modifying stuff)
Cheers
Click to expand...
Click to collapse
Yes /data folder and its subfolders are private by default and can be accessed only after root. But adb push and pull are possible in /data/misc/wifi/ xda-developers and all other major tech sites can not be wrong.
Ok then, i think there is no other method than rooting. It says wpa_supplicant.conf doesn't exist in /data/misc/wifi/
So it may be there in any other folder. Where to look other than /data/misc/wifi folder
Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans
skatehans said:
Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans
Click to expand...
Click to collapse
If you can get root on ADB then just install SuperSU app and its binaries and you are good to go.
Flashing the attached ZIP will install SuperSU app and everything it requires to function.
NOTE: You probably need a custom recovery because the zip isn't signed.
Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?
skatehans said:
Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?
Click to expand...
Click to collapse
You should be able to flash it via fastboot.
Thats the next Problem. I cant boot into fastboot mode. When i execute "adb reboot bootloader" or "adb reboot download" the device boots up like normal, so i guess fastboot is not available on this device.
Do you know any other way?
Here's the SE link with my issue.
https://android.stackexchange.com/questions/131577/cannot-remove-rename-move-build-prop?newreg=528098aed3b24c58a1949dbf850b4387
But I think you guys are able to help me better because I think it's a device/huawei kind of thing, not generally android.
Anyhow, what I did aside from that SE link...
I've downloaded a "template" from here http://forum.xda-developers.com/showthread.php?t=732957, update-apps-signed, and done what he said, afterwards I resigned the zip with SignAPK.
Then I went into recovery and applied update from sd card, but I get the same error every time...
-- Installation /sdcard ...
Installation aborted.
I googled some more and from the looks of it I need an OEM key from Huawei to unlock the bootloader and flash CWM before I can proceed. I seriously hope I don't need to do this.
So here's what tools I got:
ADB accessible phone in normal boot. Phone appears to work, the interface just won't load.
Android system recovery 3e in recovery.
This is incredibly frustrating as I know just changing one bit is all I need to get my phone working again.
Anyone got ideas how to proceed?
XDA Visitor said:
Here's the SE link with my issue.
https://android.stackexchange.com/q...-prop?newreg=528098aed3b24c58a1949dbf850b4387
But I think you guys are able to help me better because I think it's a device/huawei kind of thing, not generally android.
Anyhow, what I did aside from that SE link...
I've downloaded a "template" from here http://forum.xda-developers.com/showthread.php?t=732957, update-apps-signed, and done what he said, afterwards I resigned the zip with SignAPK.
Then I went into recovery and applied update from sd card, but I get the same error every time...
-- Installation /sdcard ...
Installation aborted.
I googled some more and from the looks of it I need an OEM key from Huawei to unlock the bootloader and flash CWM before I can proceed. I seriously hope I don't need to do this.
So here's what tools I got:
ADB accessible phone in normal boot. Phone appears to work, the interface just won't load.
Android system recovery 3e in recovery.
This is incredibly frustrating as I know just changing one bit is all I need to get my phone working again.
Anyone got ideas how to proceed?
Click to expand...
Click to collapse
Hello,
Since adb works for you. You can try these (One by one)
Code:
adb root
adb remount
adb pull /system/build.prop
Make the required changes which you messed in build.prop
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
adb reboot
Alteratively, you could register for a XDA Account so you could reply to the threads in the forums as well as get expertise help
-Vatsal
adb root -> I can't do that, it says it cannot run as root in production builds.
adb remount -> Not permitted
adb pull /system/build.prop -> This works, that's how I got the build.prop
Make the required changes which you messed in build.prop -> Donezo.
adb push build.prop /system/build.prop -> Read-only file system
adb shell chmod 644 /system/build.prop -> Read-only file system
adb reboot -> Works fine
And yes, I'm op, no idea how to claim the thread or change my name... xda said the mail address was already taken with this username.
I've already tried this as seen in the comments.
UsernameNotRecognized said:
adb root -> I can't do that, it says it cannot run as root in production builds.
adb remount -> Not permitted
adb pull /system/build.prop -> This works, that's how I got the build.prop
Make the required changes which you messed in build.prop -> Donezo.
adb push build.prop /system/build.prop -> Read-only file system
adb shell chmod 644 /system/build.prop -> Read-only file system
adb reboot -> Works fine
And yes, I'm op, no idea how to claim the thread or change my name... xda said the mail address was already taken with this username.
I've already tried this as seen in the comments.
Click to expand...
Click to collapse
Hello,
You need to get adb root working, Try running it as administrator.
If still doesnt work, then give a try to this
-Vatsal
I need root access before with ADB if I want to change that, which I can't get. To enable root access with ADB I need to have acccess to my device the normal way and edit the file with something like root ES Explorer. This is impossible as my device is soft-bricked. That's what I think, unless I'm overseeing some things?
UsernameNotRecognized said:
I need root access before with ADB if I want to change that, which I can't get. To enable root access with ADB I need to have acccess to my device the normal way and edit the file with something like root ES Explorer. This is impossible as my device is soft-bricked. That's what I think, unless I'm overseeing some things?
Click to expand...
Click to collapse
Hello,
Well, you edited build.prop and saved that so that would mean you were rooted? Isn't it?
ADB commands work without root. However the /data partition is only accessible by rooted users* and while /system can be read by anyone, it's a read-only partition and root is needed to remount it as writable.
-Vatsal
I did that before it was soft bricked with SuperSU and ES Xplorer. I don't know how to use SuperSU with ADB. su -s and su overall appear to do nothing.
UsernameNotRecognized said:
I did that before it was soft bricked with SuperSU and ES Xplorer. I don't know how to use SuperSU with ADB. su -s and su overall appear to do nothing.
Click to expand...
Click to collapse
Hello,
You may try posting your query here regarding this.
Android Q&A, Help & Troubleshooting or [URL="http://forum.xda-developers.com/showthread.php?t=2259645]General Q&A[/URL]
The experts there maybe able to assist you
-Vatsal
Abstrk_2dx said:
just flash the stock build.prop it will boot up
Click to expand...
Click to collapse
Yeah.... How
Spflasher doesn't work.
I do have a rom, but spflasher does not work.
UsernameNotRecognized said:
I do have a rom, but spflasher does not work.
Click to expand...
Click to collapse
Hello,
Read the post above, You may try asking there in that forum/thread. The experts there may be able to assist you
-Vatsal
I have but no one has replied as of yet.
UsernameNotRecognized said:
I have but no one has replied as of yet.
Click to expand...
Click to collapse
Hello,
I would recommend you waiting and having a bit of patience untill they figure out your problem and reply to it.
Thank you
-Vatsal