[Q] How to fix initlogo.te for Ubuntu Touch - Samsung Galaxy S II Plus

Hi guys
After following the porting guide to port ubuntu touch for our phone here the list of my some succeed list:
-recovery.img CWM based designed to install only this system is worked.
-Installation done with Project-Rootstock-NG tool as described on official porting guide with TWRP recovery but installation stuck under Ubuntu recovery by saying device not found after transfer tar archive.
- shell access is work only when flash the Phablet 4.4.2 MIR package but boot stuck.
so i was able to got syslog by adb pull /proc/kmsg
http://www.mediafire.com/edit/zxc494tn41ejpz4/3.txt
It would be interesting if someone can help.

Related

Advice for how to get my HTC Magic working again?

Hi.
I recently tried to root my Magic to install CyanogenMod, but it didn't work. I can't remember exactly what I did, but I followed various tutorials that I found on this site and other similar ones. I couldn't find a tutorial that went all the way from unrooted phone to rooted with CyanogenMod installed, so I switched between a couple of different ones that seemed easy to follow.
Since breaking my Magic I have tried various methods to get it working again and used google and XDA posts, but I can't do it and I'm getting quite frustrated.
Please can someone provide steps to follow that will let me access my Android OS (preferably with the latest CyanogenMod installed, but that isn't as important).
At the moment I can access fastboot on the phone, but not the main OS or the Recovery ROM I installed (cm-recovery-1.4).
I have '32B' (not sure what it means though) and 'G'
Thank you in advance for any help.
first, download recovery rom here:
http://forum.xda-developers.com/showthread.php?t=530492
Latest :
RAv1.2.1H if it's an htc phone
RAv1.2.1G if it's a google (marked with google behind)
then download android sdk and install it.
then type in a command window:
fastboot boot adressofyourrecoveryrom.img
once your phone has booted in recovery:
adb shell mount /sdcard
adb push adressofyourupdate.zip /sdcard
and on your phone:
wipe data
apply: update.zip
it's ok :-D
kiltaiga said:
first, download recovery rom here:
http://forum.xda-developers.com/showthread.php?t=530492
Latest :
RAv1.2.1H if it's an htc phone
RAv1.2.1G if it's a google (marked with google behind)
then download android sdk and install it.
then type in a command window:
fastboot boot adressofyourrecoveryrom.img
once your phone has booted in recovery:
adb shell mount /sdcard
adb push adressofyourupdate.zip /sdcard
and on your phone:
wipe data
apply: update.zip
it's ok :-D
Click to expand...
Click to collapse
Thanks for your quick reply.
RapidShare is being incredibly annoying and won't let me download the file. Do you have a mirror?
google branded
for htc branded, i've not mirror

[Q] Need URGENT help............? Nexus S. Problem with Android Bootloader Interface.

Need URGENT help............? Nexus S. Problem with Android Bootloader Interface or perhaps i don't have any idea what the problem is.
I am using nexus s 19020T, rooted, clockworkmod . My problem starts with ICS update. I got update and tried to install it. I got bellow error
"Opening update package...
Installing update...
Verifying current system...
failed to stat "/system/app/Gmail.apk": No such file or directory
file "/system/app/Gmail.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/Gmail.apk", "94d64de3d567cb9205f52a734e95f9053e6e6e99", "e2a3cf5648dbfa057787610d3f35f557297ea6bb")
assert failed: apply_patch_check("/system/app/Gmail.apk", "94d64de3d567cb9205f52a734e95f9053e6e6e99", "e2a3cf5648dbfa057787610d3f35f557297ea6bb")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/update.zip")
"
Then i reverted every thing back to 2.3.1 (nandroid backup). Now I am not able to become superuser. But I got 2.3.6 OTA. Again tried to update super user binaries. I am getting error "signature verification failed. Installation aborted."
I able to access the adb via command prompt whenever my mobile is power on but when I am in fastboot I am not able to access adb and fastboot commands. I can clearly see whenever device reboots under "devmgmt.msc" Android Phone - Android Bootloader Interface is disappearing.
It seems same problem faced here http://forum.xda-developers.com/archive/index.php/t-1304158.html. But in my case I don't have clockworkrecovery access also, My mobile is just unlocked without root access. I don't have any idea how to install image. At least I want to install clockwork recovery. Is there any other way around to do that?
Please let me know if you need further information.
Thanks in advance. Really not being a superuser sucks..........!
Earlier few days i tried [ROM][AOSP] ICS build for Nexus S - kwiboo for few days and back to 2.3.6 using rommanager. Is it got to do any thing with " ICS build for Nexus S"?
Try format /system, becareful not to format the wrong partition. Then flash a full ROM, eg. 4.0.3 full ROM (about 160MB). Apply root afterwards.
Si_NZ said:
Try format /system, becareful not to format the wrong partition. Then flash a full ROM, eg. 4.0.3 full ROM (about 160MB). Apply root afterwards.
Click to expand...
Click to collapse
May I know the procedure? Because I am not able to install any rooted application and I am not able to use adb/fastboot commands while I am in Fastboot mode.
My problem seems to be faced by one person http://forum.xda-developers.com/archive/index.php/t-1304158.html. But in my case I don't have clockworkrecovery access also, My mobile is just unlocked without root access.
229 views no reply...!
When in bootloader mode, does fastboot devices display the device ID correctly?
sorry i don't know how to solve it
suksit said:
When in bootloader mode, does fastboot devices display the device ID correctly?
Click to expand...
Click to collapse
yup we can see device serial number in fastboot mode.
sriharshavr.y said:
May I know the procedure? Because I am not able to install any rooted application and I am not able to use adb/fastboot commands while I am in Fastboot mode.
Click to expand...
Click to collapse
Try read the stickied thread for rooting carefully. You need to get at least fastboot working, so that you can flash CWM. I suspect you have a driver issue. Believe it or not, doing it in Linux is probably easier than you think... Most modern Linux distributions have drivers for these phones out of the box. When I was trying to resurrect my bricked phone, I used the Ubuntu live CD. It detected the phone on the live CD without me doing anything! If you want, you can read the stickied root guide for Ubuntu. Do it in a VM or install it on a spare computer, whatever you prefer.
You need to install stock rom from rom manager ver 2.3.3 then update to 2.3.6 then apply the update.zip from the stock recovery =] that worked for me
irizwan said:
You need to install stock rom from rom manager ver 2.3.3 then update to 2.3.6 then apply the update.zip from the stock recovery =] that worked for me
Click to expand...
Click to collapse
Hey irizwan thaks for giving reply. But here my problem is, I lost super user binaries and I am not able to install anything which requires root access.
sriharshavr.y said:
Hey irizwan thaks for giving reply. But here my problem is, I lost super user binaries and I am not able to install anything which requires root access.
Click to expand...
Click to collapse
Opps sorry ... i don't know how to help you here ... right now i'm on ICS completely stock waiting for a stable root =]
sriharshavr.y said:
yup we can see device serial number in fastboot mode.
Click to expand...
Click to collapse
If fastboot devices command works, then you shouldn't have any problem installing CWM recovery.
Put the downloaded recovery image in the same directory as fastboot.exe then use the command fastboot flash recovery your-downloaded-recovery.img to flash it.
Si_NZ said:
Try read the stickied thread for rooting carefully. You need to get at least fastboot working, so that you can flash CWM. I suspect you have a driver issue. Believe it or not, doing it in Linux is probably easier than you think... Most modern Linux distributions have drivers for these phones out of the box. When I was trying to resurrect my bricked phone, I used the Ubuntu live CD. It detected the phone on the live CD without me doing anything! If you want, you can read the stickied root guide for Ubuntu. Do it in a VM or install it on a spare computer, whatever you prefer.
Click to expand...
Click to collapse
Can I have link or some resource for more information to follow the above mentioned procedure because I am quiet new to linux.
I actually formatted my 'nexus s' with windows 7 operating system, because win 7 is prompting when ever I plugged in my mobile to access sdcard. My question is
"Is there any relation between formatting sdcard and corrupting bootloader"?
You can ROOT your device very easy...
first download : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
sriharshavr.y said:
Can I have link or some resource for more information to follow the above mentioned procedure because I am quiet new to linux.
Click to expand...
Click to collapse
If you have a 9020T, follow this guide http://forum.xda-developers.com/showthread.php?t=895545
If you have a i9023 or i9020A, follow this guide http://forum.xda-developers.com/showthread.php?t=1007782
Try that first, hopefully you can get fastboot working in Windows. Otherwise, I have to walk you through the steps to do it in Ubuntu.

[ADB] Trying to backup - Birck? Hope not

Hi! I was trying to backup my Orange Monte Carlo following a Portuguese tutorial but I'm stuck in the middle and I've got no help! Hope you can provide some! These are the steps I followed (translated)
1 - Install ADB Made Easy;
2 - Open cmd;
3 - Activate cellphone debug mode;
4 - Connect via usb (without mass storage) and install drivers if request [it was requested and i installed];
5 - Run adb devices, it should show your device [it did];
6 - Run adb reboot bootloader, your cellphone will boot in Fastboot, wich is an Android image without menus [correct until here];
7 - Run fastboot devices, your device yor a question mark(?) should show up (advance to next step), else you miss drivers [step not completed];
cmd says 'fastboot' is not recognized as a command. Now my phone is stuck connected to the computer with an adriod pick and I have no clue on what to do next!
Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked
shanman-2 said:
Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked
Click to expand...
Click to collapse
Thank you! Do you have any idea why the last command doesn't work? I believe it has something to do with file location... I'm trying to backup my Monte Carlo. Next steps were to "fastboot boot recovery.img" and then backup.
It should be in the platform-tools directory of the android-sdk. Verify that it's there...if so cd to that directory and it should work
I already fixed it for myself, thanks! Now I can't seem to be able to install clockwork!
Doing <<fastboot boot "C:\Users\R&J\Downloads\recovery.img">> reboots the device but doesn't enter recovery.
Doing <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> , <<fastboot reboot>> and <<adb wait-for-device reboot recovery>> results the phone entering android's default recovery (no acess to backup feature).
Any way to help? Thank you!
The first command <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> is trying to write the recovery.img you downloaded to a recovery partition on your device. It may not be overwriting the original recovery.
try changing permissions by doing
adb shell
su
chmod 777 /recovery
then try to flash again
Lol it seems like I have been luck enough to solve my own problems, I have sucessfully installed ClockworkMod Recovery 4.0.1.4 unofficial MoDaCo Edition using a bat file . Now I can't seem to find a way to flash recovery back to stock. I though this was an option inside the modded recovery. Any tips? Thanks again!
EDIT: I have the stock recovery file . God... this tutorials I'm folowing aren't that noob friendly...

[Q] Recovering from soft brick

Hi all,
I was fiddling around with a rooted android 7 inch tablet (its a china-made tablet i believe - TWD_MID) with android 4.0.4 installed. In order to hide the status bar i tried to follow certain tricks (replaced the /system/app/settings.apk and /system/framework/android.policy.jar). This caused the tablet to go into a bootloop (the boot animation kept on playing)
The obvious solution offcourse was to install a new custom ROM (since i unfortunately did not hav a backup ROM) ; however doing it manually i came across these problems:
1. The tablet doesn't seem to have any sort of bootloader / custom recovery mode. I've tried power +volume up and power+ volume down; even did adb reboot-bootloader , adb reboot [recovery] but nothing - the tablet just kept booting normally and going into bootloop.
2. There seems to be some problem with fastboot as well - almost all the commands entered along with fastboot yield "<waiting for device>"
I even tried using uniflash to install a custom rom; the tablet reboots twice and uniflash gives a success message; but in reality there seems to be no change in the tablet
Till this point though, adb was working properly
Out of sheer desperation (I know i shouldn't have, but still ) I used adb push to push all the entire /system folder from the extracted folder of custom rom into the /system of the tablet.
Now i can't even use adb shell - any adb shell "[command]" gives the error :
- exec '/system/bin/sh' failed: Permission denied (13) -
Please if possible can someone give me some advice??
I'm hoping to find a way to:
1. Get adb shell working again
2. Install and enter into some sort of bootloader/custom recovery mode on the tablet; so i can install a rom from TF(ext sd) card
I want to get my tablet working again....
Please Help...
Thanx a lot in advance...

Error in ADB: Can't push apps/files due to system is read only.

Hello guys! Hope I can find my salvation here. Hehe
I've been coding my Windows App that functions much like a custom recovery but I came into a problem which is bugging me
since last week. I can't seem to push files to my phone through adb. I have no idea why it wont work because pull is working fine, and shell as well. I tried remounting the file system as rw but still no luck. Hope you can help me out guys
My phone's Specification:
-Spreadtrum SC7731
-Running Android 5.1
My environment:
-Windows 10
-adb installed
-device drivers installed.
PS: If you are wondering why make a recovery that runs in PC while you can just have it in your phone?
-Unfortunately, I got a problem with that. I ported TWRP for my phone, but touch wont work which makes it useless.
Please help me sensei's!
Unlock the bootloader, flash a custom recovery (CMW for exmpl), put the root package at the root dir of the sdcard, now boot the phone into recovery mode and select install zip from sdcard then reboot
On pc, write the following command : "adb remount"
Gratzz you're now rooted and able to push files into system partition ��
Root at your own risk. Unlocking the bootloader makes you lose the warranty and will wipe your data .. So take a backup.
FinnTheHuman. said:
Unlock the bootloader, flash a custom recovery (CMW for exmpl), put the root package at the root dir of the sdcard, now boot the phone into recovery mode and select install zip from sdcard then reboot
On pc, write the following command : "adb remount"
Gratzz you're now rooted and able to push files into system partition ��
Root at your own risk. Unlocking the bootloader makes you lose the warranty and will wipe your data .. So take a backup.
Click to expand...
Click to collapse
Reread the OP. :fingers-crossed::fingers-crossed: I'm on Spreadtrum phone which means no source(yet.. or forever). I don't really know if you just misinterpreted the post or just trying to acquire post count. :3

Categories

Resources