so I have a spare m7(UL) that I'd like to experiment with. I would like to try to port a rom made for the m8 to the m7, but cannot find any tutorials based on this specifically. If such a thing exists, could someone link me? if not, does anyone have any expertise with this?
at this point I have been able to successfully get the script to flash with successcode=1.0. ROM will not boot(as I expected) staying stuck on the boot logo. I don't know what logs would be useful besides the installer log which I will attach here, so please let me know.
EDIT: included kernel log and system log
Try use logcat
Sent from my One using XDA-Developers mobile app
tathanhlam66 said:
Try use logcat
Sent from my One using XDA-Developers mobile app
Click to expand...
Click to collapse
I can't reach adb until after the boot logo. just hangs at waiting for device. is there another way of getting the logcat, or anything else I can do?
bbmaster123 said:
I can't reach adb until after the boot logo. just hangs at waiting for device. is there another way of getting the logcat, or anything else I can do?
Click to expand...
Click to collapse
extract boot.img
edit ramdisk/default.prop
change line ro.adb.secure=1 -> ro.adb.secure=0
add botton line persist.sys.usb.config=mtp,adb
use new boot.img
tathanhlam66 said:
extract boot.img
edit ramdisk/default.prop
change line ro.adb.secure=1 -> ro.adb.secure=0
add botton line persist.sys.usb.config=mtp,adb
use new boot.img
Click to expand...
Click to collapse
Just finished installing cygwin and android kitchen, unpacked boot.img, and opened default.prop. all those were already set exactly like you said, so I just closed the file. copied over boothpath from "BASE" rom's boot.img in init_environ.rc (I believe thats what it was called, but I'm sure you know what I mean) repacked, and flashing now.
UPDATE: Rom failed to finish flashing with error code 7. ended with set_perm: some changes failed caused by a chown command for busybox in the updater-script, but I double checked and busy box is in /system/xbin like it should be. If I remove that line, the rom finishes flashing with success code 1.0 but fails to boot...
Related
consider this thread deprecated, will keep the original post here for historic sake, and maybe it will help someone down the road
there are way easier ways to do this now
please do not try any of this
if you do decide to do anything on this thread, it is at your own risk
you have been warned
Code:
get:
[url]http://www.droidaftermarket.com/koush//test/inc.zip[/url]
[url]http://www.droidaftermarket.com/koush//test/keys[/url]
1. Boot to recovery with adb (if u dont know how...learn)
2. Run the unrEVOked method to get an adb shell, then do su to get # (if u dont know how...learn)
3. push the inc.zip to /sdcard/update.zip
4. push the keys file to /sdcard/keys
5. Do:
/system/bin/mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
/system/bin/rm /res/keys
/system/bin/cat /sdcard/keys > /res/keys
/system/bin/ps recovery // note the pid of it
/system/bin/kill <pid>
6. Vol+ and Power to get menu again
7. Vol - then power to run the update.zip
8. Profit!
Big thanks to the unrEVOked team and koush for making this happen!
This method does not stick, it is only good until reboot, but adb works now so have fun
Some problems with accessing /data and some other stuf, but well get it sorted out
i have rooted my phone and was able to get the adb shell working originally; however it seems that now when i get back into adb shell in recovery i am not able to run adb shell to get su....any thoughts? I just continue to get -exec '/system/bin/sh' failed: No such file or directory (2) -
my apologies for being such a n00b...i got it!
WOW
Worked like a charm
Video Tut
http://www.youtube.com/watch?v=BuPFee7IIfM
test key
the test key download is just a bunch of #s do i copy it and put that in a file then push? it doesnt download for me it just opens a window with keys
B-dub25 said:
the test key download is just a bunch of #s do i copy it and put that in a file then push? it doesnt download for me it just opens a window with keys
Click to expand...
Click to collapse
right click on the link and hit save as, remove the .txt extension once it downloads. Look at my video which i have a link for one post above if you need help.
thanks
thanks i`ve been doing three things at once lol got conf. i had to make a program for my finiles c++ programming fun and linux adm. finile too thanks thou
ejlax said:
i have rooted my phone and was able to get the adb shell working originally; however it seems that now when i get back into adb shell in recovery i am not able to run adb shell to get su....any thoughts? I just continue to get -exec '/system/bin/sh' failed: No such file or directory (2) -
my apologies for being such a n00b...i got it!
Click to expand...
Click to collapse
You need to go through the rooting process again, since we can't flash recovery yet, for anyone that was wondering. At least up until the point where you inject the payload.
Has anyone managed to use the nanadroid backup option with this recovery? It seems to backup ok and I can see the backup on my sd card, but if you try and restore, it says:
Code:
Checking MD5 sums...
MD5 mismatch!
This even happens when doing an advanced restore and choosing the file. Here is what is in the Recovery.log file.
Code:
Checking MD5 sums...
md5sum: nandroid.md5: No such file or directory
MD5 mismatch!
Then it just quits. Can you fix it please?
I can get adb to work just about everytime
I can even get recovery to update but still it wont stick no matter what I try. So needless to say anytime I want to try anything I must do the entire procedure over again
There has to be a better way or is this all caused but the nand protection many talk about. Sorry im kindof of newbie to this sort of problem.
All other phones I have rooted for friends usually take once you get it to work. Mytouch 3g fender, a bunch of Moto droids and one N1 so far, and of course my DI
I hope someone figures this out soon then we may start seeing some ROMS, I cant wait for a vanilla rom that I can dress up the way I want and not have all the bloat from SenceUI. Ony thing i'd like to keep would have been htc's weather widget and maybe freindstrean. If I can use it with Sweeter home preview 2. Im so happy with this last release of SH2 its rock solid on my incredible like its been on the moto droid the last 2 or 3 releases for me.
ihtfp69 said:
Has anyone managed to use the nanadroid backup option with this recovery? It seems to backup ok and I can see the backup on my sd card, but if you try and restore, it says:
Code:
Checking MD5 sums...
MD5 mismatch!
This even happens when doing an advanced restore and choosing the file. Here is what is in the Recovery.log file.
Code:
Checking MD5 sums...
md5sum: nandroid.md5: No such file or directory
MD5 mismatch!
Then it just quits. Can you fix it please?
Click to expand...
Click to collapse
Thats basically the hurdle everyone is trying to jump right now. getting a valid nand backup that works, once that is done, custom recovery and roms will be flowing. Im also working on some messing around to try to help out, but on the same hand being careful not to brick since theres no way to restore at this time.
Has anyone heard how progress of making sp recovery stick going? Thanks.
tats_06 said:
Has anyone heard how progress of making sp recovery stick going? Thanks.
Click to expand...
Click to collapse
From what I hear its going well..stay tuned as we might see something from the unrevoked team soon.
760hacker said:
From what I hear its going well..stay tuned as we might see something from the unrevoked team soon.
Click to expand...
Click to collapse
Thanks!!! Thats reassuring.
Can anyone please post a copy of the keys file? The link is down and I can't find it anywhere else either!
Would really appreciate some help here guys...
basically i have a new SLCD nexus one with Ramons 1.8.01 recover image.
I tried uploading a few roms but none of them worked..
so I'm trying to restore one of two nandroid backups i made before i started messing..
on the phone if i go into recovery and select nandroid restore then i get an error telling me to run nandroid-mobile.sh via ADB.
So, i set up adb, follow a guide (here) and end up with an error saying
error: unyaffs not found in path
does anyone know how i can get that backup working???
I've attached a copy of my cmd window..
Any help would be gratefully appreciated
Quick update, I have Cyanogen 6.0.0 working on the phone now..
But i'd still like to be able to restore!
jamin100 said:
Would really appreciate some help here guys...
basically i have a new SLCD nexus one with Ramons 1.8.01 recover image.
I tried uploading a few roms but none of them worked..
so I'm trying to restore one of two nandroid backups i made before i started messing..
on the phone if i go into recovery and select nandroid restore then i get an error telling me to run nandroid-mobile.sh via ADB.
So, i set up adb, follow a guide (here) and end up with an error saying
error: unyaffs not found in path
does anyone know how i can get that backup working???
I've attached a copy of my cmd window..
Any help would be gratefully appreciated
Click to expand...
Click to collapse
I would suggest trying to type the directory instead of using default. When the restore prompts you to either type the directory or hit enter... instead of hitting enter type:
/sdcard/nandroid/HT08BP800418/BCDS-20100911-2252
See if it gives you the same error.
NOTE: That IS case sensitive.
Thanks for your reply, unfortunately it does give the same error, I have 3 nandroid backups but cant restore any of them which is worrying incase anything happens to the phone!
Please help
Try this... while in the shell... type the following:
Code:
ls -l /sdcard/nandroid/HT08BP800418/BCDS-20100911-2252
It should bring up a list of 5 files. Go ahead and attach a screen if you can if you are getting a list of files. If not let me know what error you get.
Thanks for your help,
here's the screen shot
Nobody encountered this problem?
Ok... sorry had you look in the wrong place. I thought it was looking in the directory with the image in it for what it needed. I just looked at the nandroid code. Turns out... it looks for some executables that are required for the script to run. It doesn't have to do with your image and I think your images are probably fine.
I need you to run 2 more commands so I can see where the problem is. First run:
Code:
env
Next run:
Code:
which unyaffs
The "env" command should show your enviroment variables. What we are looking for is for /system/bin to be in your "PATH" variable. It should be because it checks for another executable first "flash_image" and it is not coming up with an error. The second file it is checking for is "unyaffs". Next you need to check and make sure unyaffs is actually in your /system/bin folder. It is probably not... and would explain the error you are getting.
I guess my first question is... is this happening on all ROMs you have tried (or have you only gotten one up and running)? If it is there may have been a problem when you flashed it. Even though it is possible that you could copy it to the /system/bin I would suggest not doing this. The reason is because if that one file is missing... there may be other files missing that should be there from when you flashed your ROM. These missing files... if there are any... could cause problems later. It might be best just to reflash whatever ROM you are using. I would suggest CM6 (not nighties) and then moving to some other ROM once you get a "known good" to work with.
Hey GoblinLord,
Thanks for your help on this, really appreciate it..
OK, well i've ran the two commands that you said and have attached the screenshot with the output. I've tried going to /system/bin but get permission denied errors through adb.
Although it looks like the PATH is actually /sbin rather than /system/bin ???
As for the roms..
I'm currently using CM6 (the stable version) as this was the only one that I could manage to get to work. As this is a SLCD nexus i dont think there are many roms that have the right drivers for the screen. Its does work fine though.. The nandroid restore is the only part of the phone that i cannot get working....
Again thanks for the help...
jamin100 said:
Hey GoblinLord,
Thanks for your help on this, really appreciate it..
OK, well i've ran the two commands that you said and have attached the screenshot with the output. I've tried going to /system/bin but get permission denied errors through adb.
Although it looks like the PATH is actually /sbin rather than /system/bin ???
As for the roms..
I'm currently using CM6 (the stable version) as this was the only one that I could manage to get to work. As this is a SLCD nexus i dont think there are many roms that have the right drivers for the screen. Its does work fine though.. The nandroid restore is the only part of the phone that i cannot get working....
Again thanks for the help...
Click to expand...
Click to collapse
Hmmm... the permission denied is normal. That is because it is a folder and not an executable. You should be able to do:
Code:
ls -l /system/bin
This will list what is in your /system/bin directory. As for your path being different... that seems a bit strange. I am doing the commands from a terminal on my device... once I get back home today I will do it through the ADB shell and see what I get. The "which" command will only look in the folders in your "PATH" variable for the executable. If /system/bin is not in there I am not sure how it is passing the part where it looks for "flash_image". In my sbin folder I only have the ADB daemon (adbd) executable. What you could do is manually add the /system/bin to your PATH variable while in the shell... that may work. You can try the following:
Code:
PATH=$PATH:/system/bin
Run that before running your restore command. That should manually place the directory you need into your PATH environment variable. I will do a little testing with ADB once I get home and update this if I get to before you try it.
Thanks for the reply....
I won't be able to try this until Wednesday as I have left the USB cable at work ....
I will try it Wednesday and let you know...
Thanks
Sent from my Nexus One using XDA App
jamin100 said:
Thanks for the reply....
I won't be able to try this until Wednesday as I have left the USB cable at work ....
I will try it Wednesday and let you know...
Thanks
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I checked my environment variables via ADB. Mine did show the /system/bin in my PATH variable. Seeing as this is a shell being run on your device... I would still venture to say that something may have went wrong when you flashed your ROM originally. That or something you installed changed it for some crazy reason (and shouldn't have). Either way, I still think it would be best to flash again... possibly to a different version. I know you would have had to get a modified version of CM6 so... if you don't mind me asking where did you get your copy?
EDIT: Correction... I am getting the same path variable as you when in recovery mode. I am not quite sure why this is... the guide I found for using nandroid restore through ADB doesn't seem to run into this issue. It might be some kind of issue related to just Amon_Ra recovery. This would mean that Amon_Ra Recovery just didn't add it to the PATH variable... which I guess is rather odd... but whatever. Just try manually adding it to the PATH variable as mentioned above and then run the restore. It should work then.
EDIT 2: I did a bit of researching on that error you are getting when you try and restore in recovery. Reference:
http://forum.xda-developers.com/showthread.php?t=621940
Various people point to things that may cause this error. Is your phone charged? Do you have plenty of space on your SD card?
I'm developing a app which flashes a zip through cwm, its working fine apart from i need to know how to send a command to cwm so that when it reboots it also disables signature verification. Heres how i'm already sending the infomation to cwm to know what to flash on reboot
Code:
os.writeBytes("echo '--update_package=/data/data/carbon.assassin.tweaks/beats.zip' >> /cache/recovery/command\n");
carbonassassin said:
I'm developing a app which flashes a zip through cwm, its working fine apart from i need to know how to send a command to cwm so that when it reboots it also disables signature verification. Heres how i'm already sending the infomation to cwm to know what to flash on reboot
Code:
os.writeBytes("echo '--update_package=/data/data/carbon.assassin.tweaks/beats.zip' >> /cache/recovery/command\n");
Click to expand...
Click to collapse
why dont you sign your zip with a test key???Signapk will do the job.
That seems to work but it doesn't print any of the UI while flashing which is a bit annoying, any idea's on how to make it? (The signing bit isn't affecting this but the flashing it from terminal seems to)
carbonassassin said:
That seems to work but it doesn't print any of the UI while flashing which is a bit annoying, any idea's on how to make it? (The signing bit isn't affecting this but the flashing it from terminal seems to)
Click to expand...
Click to collapse
AFAIK this is the easiest method.I dont think you might turn of signature verification through terminal.But I may be wrong.As for the printing statement goes,could you attach your updater-script???I might have a look.
I want to run this on Samsung galaxy s4 i9505 jfltexx.
Anyone want to work on this?
Im willing to help in anyway i can
Sent from my GT-I9505 using xda app-developers app
Update: port is almost ready
Trying to sort a few compile errors
I would like to see this happen.
Relys said:
I would like to see this happen.
Click to expand...
Click to collapse
Me too
Sent from my GT-I9505G using Tapatalk
Awesome, can you dualboot it? And how big is the port rom?
Sent from my GT-I9505 using Tapatalk
JustSueMe said:
Update: port is almost ready
Trying to sort a few compile errors
Click to expand...
Click to collapse
Need any help?
Sent from my GT-I9505 using Tapatalk
Download link ! Alpha !
http://www.datafilehost.com/d/44a25a60
link is to download phablet
instructions:
reboot to recovery
wipe all partitions
flash phablet in above link
flash trusty-preinstalled-touch-armhf.zip [u can find on cdimages.ubuntu.com]
reboot phone to system
--
at this point youll have a black screen and no activity
plug phone into pc
grab this file : (70-jfltexx.rules) http://www.datafilehost.com/d/17d6dd77
now open terminal
$ su
$ adb push 70-jfltexx.rules /usr/lib/lxc-android-config/
$ reboot
phone will look like its doing nothing for a bit, but wait.
now it will boot back up like normal but you will have a ubuntu touch gui
BUGS:
no conectivity
no sound
edge swipe is small but works without case
camera
frame jumps to the right for some apps occasionally (unsure if thats on purpose of buggy... i vote buggy)
app crashing (maybe reason for camera crash?)
doesnt show imei
no sdcard mounted
terminal app doesnt even work so need to use adb to run commands
enjoy lol ... note alpha in title if anyone wants to complain ... also note only you are responsible for what happens to your device.
now have connectivity via reverse tether
adb root
adb shell setprop sys.usb.config rndis,adb
if you get permission error use adb server as root
ubuntu network manager will show that samsung android is connecting.
open network settings edit that connection and change auto DHCP to shared
adb shell
run this command (logged into phone)
dhclient usb0 -v
now on phone open webbrowser and you should be able to connect
just got WIFI !
haha progress
adb shell
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
now wifi will turn on
make it auto load at boot
touch /data/local/userinit.sh
add to the file :
#!/bin/bash
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
make it run
chmod +x /data/local/userinit.sh
help !
im trying to fix the gsm
here is my output
[email protected]:/# nmcli dev
DEVICE TYPE STATE
/ril_0 gsm disconnected
wlan0 802-11-wireless connected
[email protected]:/etc/NetworkManager/system-connections# ls
TALKTALK-FCF354 Three
TalkTalk--* is my WIFI
Three is my mobile 3g data
so ill try to load Three
[email protected]:/etc/NetworkManager/system-connections# nmcli con up id Three
Error: Connection activation failed: The connection was not supported by oFono.
here is the contents of Three :
[connection]
id=Three
uuid=39a02ed3-d946-45f8-9abb-81ef997add03
type=gsm
autoconnect=false
[ppp]
refuse-eap=true
refuse-chap=true
refuse-mschap=true
refuse-mschapv2=true
nobsdcomp=true
nodeflate=true
no-vj-comp=true
[ipv4]
method=auto
[serial]
baud=115200
[gsm]
number=*99#
username=three
apn=3internet
contents of TalkTalk
[connection]
id=TALKTALK-FCF354
uuid=1bcf8cdf-9152-49de-b279-7770e94e5006
type=802-11-wireless
[802-11-wireless]
ssid=TALKTALK-FCF354
mode=infrastructure
mac-address=5C:F8:A1:90:2F:FB
security=802-11-wireless-security
[802-11-wireless-security]
key-mgmt=wpa-psk
auth-alg=open
psk=Password1
[ipv4]
method=auto
[ipv6]
method=auto
Why is TalkTalk supported and Three is not ?
as i understand it it uses https://github.com/rilmodem/ofono
AND if fixed this configuration may only give 3g data connection on the THREE 3 UK newtork not calls or sms but one step at a time/
JustSueMe said:
http://www.datafilehost.com/d/44a25a60
link is to download phablet
instructions:
reboot to recovery
wipe all partitions
flash phablet in above link
flash trusty-preinstalled-touch-armhf.zip [u can find on cdimages.ubuntu.com]
reboot phone to system
--
at this point youll have a black screen and no activity
plug phone into pc
grab this file : (70-jfltexx.rules) http://www.datafilehost.com/d/17d6dd77
now open terminal
$ su
$ adb push 70-jfltexx.rules /usr/lib/lxc-android-config/
$ reboot
phone will look like its doing nothing for a bit, but wait.
now it will boot back up like normal but you will have a ubuntu touch gui
BUGS:
no conectivity
no sound
edge swipe is small but works without case
camera
frame jumps to the right for some apps occasionally (unsure if thats on purpose of buggy... i vote buggy)
app crashing (maybe reason for camera crash?)
doesnt show imei
no sdcard mounted
terminal app doesnt even work so need to use adb to run commands
enjoy lol ... note alpha in title if anyone wants to complain ... also note only you are responsible for what happens to your device.
Click to expand...
Click to collapse
Will this work with an ATT that has a locked bootloader that needs loki file for the kernel?
toxicpaulution said:
Will this work with an ATT that has a locked bootloader that needs loki file for the kernel?
Click to expand...
Click to collapse
well for one this is for jfltexx, and secondly if the boot loader is locked i doubt that could flash it as u need a new the boot.img.
if you want it on att model you ill prob need to buid depreciated ubuntu touch.
depreciaed UT boots android then ubuntu in a container
this boots ubuntu then andriod in container.
JustSueMe said:
well for one this is for jfltexx, and secondly if the boot loader is locked i doubt that could flash it as u need a new the boot.img.
if you want it on att model you ill prob need to buid depreciated ubuntu touch.
depreciaed UT boots android then ubuntu in a container
this boots ubuntu then andriod in container.
Click to expand...
Click to collapse
Well see with ATT we can boot custom roms(MDL users) as long as the kernel is already lokidokied, or you can flash the loki zip and it will bypass the ATT check and allow you to boot a custom rom, Now seeing how this is based of CM10.2(thats what the file is saying so i am just taking a guess) if I flashed the Loki zip after flashing the rom would it work? But I am doing a backup as of now and I am going to test and see if it works :3 I will report back lol
---------- Post added at 01:49 PM ---------- Previous post was at 01:03 PM ----------
toxicpaulution said:
Well see with ATT we can boot custom roms(MDL users) as long as the kernel is already lokidokied, or you can flash the loki zip and it will bypass the ATT check and allow you to boot a custom rom, Now seeing how this is based of CM10.2(thats what the file is saying so i am just taking a guess) if I flashed the Loki zip after flashing the rom would it work? But I am doing a backup as of now and I am going to test and see if it works :3 I will report back lol
Click to expand...
Click to collapse
Didn't work, Getting status 7 which would mean I would have to edit the update script so it doesn't just look for the inital phone. I will do that now and try again.
toxicpaulution said:
Well see with ATT we can boot custom roms(MDL users) as long as the kernel is already lokidokied, or you can flash the loki zip and it will bypass the ATT check and allow you to boot a custom rom, Now seeing how this is based of CM10.2(thats what the file is saying so i am just taking a guess) if I flashed the Loki zip after flashing the rom would it work? But I am doing a backup as of now and I am going to test and see if it works :3 I will report back lol
---------- Post added at 01:49 PM ---------- Previous post was at 01:03 PM ----------
Didn't work, Getting status 7 which would mean I would have to edit the update script so it doesn't just look for the inital phone. I will do that now and try again.
Click to expand...
Click to collapse
the base may be cm10 but it doesnt boot cm10. the boot.img gets flashed and it boots ubuntu , the cm part is in a container within ubuntu
i dont think att will be able to use this is the bootloader cant be flashed
JustSueMe said:
the base may be cm10 but it doesnt boot cm10. the boot.img gets flashed and it boots ubuntu , the cm part is in a container within ubuntu
i dont think att will be able to use this is the bootloader cant be flashed
Click to expand...
Click to collapse
Yeah changing the updater script didnt do the job :/ lame lol well it was work the try, I will follow this htread though seems promising.
toxicpaulution said:
Yeah changing the updater script didnt do the job :/ lame lol well it was work the try, I will follow this htread though seems promising.
Click to expand...
Click to collapse
okay it wont let me adb push the file says bash: adb: command not found
edit: im running now but the connectivity through reverse thether isnt working. btw im on the att s4
JustSueMe said:
haha progress
adb shell
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
now wifi will turn on
make it auto load at boot
touch /data/local/userinit.sh
add to the file :
#!/bin/bash
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
make it run
chmod +x /data/local/userinit.sh
Click to expand...
Click to collapse
I have successfully ported the zip to the SGH-I337 AT&T model same as yours wifi no data after fixes. Are you having trouble with the roms sliding from the lockscreen to home trouble?
---------- Post added at 02:34 AM ---------- Previous post was at 01:59 AM ----------
Joeyxc said:
I have successfully ported the zip to the SGH-I337 AT&T model same as yours wifi no data after fixes. Are you having trouble with the roms sliding from the lockscreen to home trouble?
Click to expand...
Click to collapse
link for att or tmobile http://www.androidfilehost.com/?fid=23252070760974893
Enjoy
This is just the cm, still follow the other instructions for everything else
http://www.youtube.com/watch?v=mJLKX_QWSpc&feature=youtu.be
Joeyxc said:
I have successfully ported the zip to the SGH-I337 AT&T model same as yours wifi no data after fixes. Are you having trouble with the roms sliding from the lockscreen to home trouble?
---------- Post added at 02:34 AM ---------- Previous post was at 01:59 AM ----------
link for att or tmobile http://www.androidfilehost.com/?fid=23252070760974893
Enjoy
This is just the cm, still follow the other instructions for everything else
http://www.youtube.com/watch?v=mJLKX_QWSpc&feature=youtu.be
Click to expand...
Click to collapse
So I should flash that first and then the others as stated?
toxicpaulution said:
So I should flash that first and then the others as stated?
Click to expand...
Click to collapse
Yup! Let me know if you run into any issues don't forget to thank if it worked!
Sent from my SGH-I337 using Tapatalk
Joeyxc said:
Yup! Let me know if you run into any issues don't forget to thank if it worked!
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Forgot you need to use the Loki file for att, I'm doing adb on my other lappy haha xD then I'll boot it
Sent from my SGH-I337 using Tapatalk
First of all, many thanks for 4pda members.
It's time to post new thread for Lollipop.
This is for Kitkat me572c users.
(I can't make link so just copy the url)
● Lollipop firmware (UL-K007-WW-12.14.1.12) with root
Code:
mega.nz/#!LwJ3VBxK!4V4Ay-RzLS8x609zvyWL8IlcgI3xxfLcSqZ3gZkc52Q
● Install-Recovery.rar
Code:
mega.nz/#!C5ghzL6R!GR0WgLCumy6a429kB0ZjQOMxjPSylz07fVnHtKVm8ng
● ADB Driver
Code:
mega.nz/#!YAlxVbYS!7xfADRLuvcyO1GxRHtre3_e1TaVPmtIykqGbKCzUkkk
1) Can only be set on 4.4.2 (Kitkat). If you have already installed Lolipop, you must first revert to Kitkat. The computer should be installed ADB driver for the tablet and the tablet is turned on for the USB debugging. (no need to backup Internal memory. every data remain. but just in case, back up your data.)
2) Connect powered tablet to the computer. Download the firmware and rename it MOFD_SDUPDATE.zip, copy to the root of the memory card(MicroSd card) of the tablet. Download the archive Install-Recovery.rar and unpack it on your computer.
3) Run Install-Recovery.cmd, after the black command window turns up, volume buttons to select SD Download and power button for confirm. This will start the process of firmware.
Can anyone post instructions (in English hopefully because I'm lingual challenged) on how to revert back to KitKat if you've already upgraded to Lollipop? I didn't think that was possible...
Thanks so much!
I did a rough translation of the steps for downgrading in this thread. I haven't tried it myself, though, so I can't guarantee success.
It worked yes! Thanks! The only problem I have is my navbar icons is still kitkat, so is my wifi icon/battery. I'm just going to get the xposed module I guess and figure out later while it hasn't changed. But woo!
edit: (DOH!) that's what exposed moduel Xstana is for, nevermind the issue about navbar icons and the other icon problems.
You should include this in OP.
The link you posted for xposed lollipop in the other thread
"Xposed Installer for Lollipop
is.gd/jSVa1Q"
does this work on ME176CX??
redhk886 said:
does this work on ME176CX??
Click to expand...
Click to collapse
I wouldn't try it. The process involves loading ROM images made specifically for the ME572C..
A few questions about this.:
* Is there a way to do this in Linux? I don't own a Windows computer, but I have the full Android SDK installed, including ADB and fastboot.
* Is the Recovery.rar necessary if I am still on Kitkat? I assume this changes out the stock recovery with something else. Is that correct?
* Does this actually unlock the bootloader?
* My tablet is currently running 4.4.2. KVT49L.WW_epad-11.8.3.31-20150126 release-keys
044000309_201407240016. Any problems upgrading from this version?
Thanks
EDIT: Here is a very slightly modified script from the original for Linux. You must have adb and fastboot already installed for this work. These are included in the Android SDK for Linux. Copy and past this into a new file called Install-Recovery.sh and make it executable. You will still need the recovery.img file from the original Install-Recovery.rar archive. I don't think you will need anything else.
THIS IS UNTESTED!
Code:
#!/bin/bash
echo "Waiting for device connection..."
adb wait-for-device
adb reboot bootloader
fastboot flash recovery recovery.img
lexridge said:
A few questions about this.:
* Is there a way to do this in Linux? I don't own a Windows computer, but I have the full Android SDK installed, including ADB and fastboot.
* Is the Recovery.rar necessary if I am still on Kitkat? I assume this changes out the stock recovery with something else. Is that correct?
* Does this actually unlock the bootloader?
* My tablet is currently running 4.4.2. KVT49L.WW_epad-11.8.3.31-20150126 release-keys
044000309_201407240016. Any problems upgrading from this version?
Thanks
EDIT: Here is a very slightly modified script from the original for Linux. You must have adb and fastboot already installed for this work. These are included in the Android SDK for Linux. Copy and past this into a new file called Install-Recovery.sh and make it executable. You will still need the recovery.img file from the original Install-Recovery.rar archive. I don't think you will need anything else.
THIS IS UNTESTED!
Code:
#!/bin/bash
echo "Waiting for device connection..."
adb wait-for-device
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I'm using linux tools comes with Intel Phone Flash Lite tool instead of google tools.
https://01.org/android-ia/downloads/intel-phone-flash-tool-lite
adb and fastboot are installed into /usr/lib/phoneflashtoollite/ and changed path for the tools are changed and done manually.
Now I've just succeeded to install LoliPop into my tab after almost 2 days efforts(thank all contributors!!) but I can't reproduce accurate steps in linux(ubuntu) environment.... At least I used windows environment for downgrading from non-rooted 5.01 to 4.4.2...
Good luck !
gmaxjp said:
I'm using linux tools comes with Intel Phone Flash Lite tool instead of google tools.
https://01.org/android-ia/downloads/intel-phone-flash-tool-lite
adb and fastboot are installed into /usr/lib/phoneflashtoollite/ and changed path for the tools are changed and done manually.
Now I've just succeeded to install LoliPop into my tab after almost 2 days efforts(thank all contributors!!) but I can't reproduce accurate steps in linux(ubuntu) environment.... At least I used windows environment for downgrading from non-rooted 5.01 to 4.4.2...
Good luck !
Click to expand...
Click to collapse
As I do not need to downgrade, I think my script will work. I just have not had the time to try it. When I do flash this, I will probably just type in the commands manually so I can what is happening easier. I would just really like to know more about this new Recovery before flashing. Is a CWM based recovery or a stock recovery? If stock, what differs in it from the stock recovery currently present on it?
I grabbed the link you sent, but it's a .deb file. I will search for a RPM or just convert this one, as I am using Fedora 21 and CentOS 7 on my two machines.
Thanks
lexridge said:
As I do not need to downgrade, I think my script will work. I just have not had the time to try it. When I do flash this, I will probably just type in the commands manually so I can what is happening easier. I would just really like to know more about this new Recovery before flashing. Is a CWM based recovery or a stock recovery? If stock, what differs in it from the stock recovery currently present on it?
I grabbed the link you sent, but it's a .deb file. I will search for a RPM or just convert this one, as I am using Fedora 21 and CentOS 7 on my two machines.
Thanks
Click to expand...
Click to collapse
Recovery is not CMW/TWRP, perhaps modified from stock.
Yep, What I did were execute series of command lines manually and crossing my fingers for several times
I'm expecting that will work in RPM based distros.
confirm, successful update using links/directions here.
kk stock rooted -> custom rooted 5.0 as above
yay!
significant speed increase in the ui animations, etc.
...google probably did a lot of support work for the moorefield
SacredMyths said:
It worked yes! Thanks! The only problem I have is my navbar icons is still kitkat, so is my wifi icon/battery. I'm just going to get the xposed module I guess and figure out later while it hasn't changed. But woo!
edit: (DOH!) that's what exposed moduel Xstana is for, nevermind the issue about navbar icons and the other icon problems.
You should include this in OP.
The link you posted for xposed lollipop in the other thread
"Xposed Installer for Lollipop
is.gd/jSVa1Q"
Click to expand...
Click to collapse
Thanks for Xposed info. I installed framework and installer from linux to tablet (by trying install command lines manually) and now they are working perfect. Eating pies with lollipop now, yummmm.
gmaxjp said:
Thanks for Xposed info. I installed framework and installer from linux to tablet (by trying install command lines manually) and now they are working perfect. Eating pies with lollipop now, yummmm.
Click to expand...
Click to collapse
Good , no problem.
Now the only issue I'm having is a few emojis are black D:
where can i download the xposed apk for this model...
javcarbe said:
where can i download the xposed apk for this model...
Click to expand...
Click to collapse
Xposed Installer for Lollipop http://is.gd/jSVa1Q Use latest rev.
Since is a zip
How can I install a zip if I don't have a twrp recovery
---------- Post added at 06:17 PM ---------- Previous post was at 05:47 PM ----------
i unzip run the bat but doesnt work i need an instructions to do it manually
C:\Temp\XposedForZenFoneLollipop_20150607>InstallXposedFramework.bat
'
'
' Connecting ZenFone ..
'
'
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
'
'
' Pushing files ..
'
'
error: device not found
error: device not found
'
'
' Installing Xposed Framework,
' please GRANT permission for this script on your phone !
'
'
error: device not found
error: device not found
error: device not found
'
'
' Done, rebooting ..
'
'
error: device not found
Instructions fail with the recovery not being able to mount the SDCard for some reason.
But the zip sideloaded just fine.
Thanks.
Also, any idea what recovery is compatible?
i tried with flash gordon but doesnt work.... also i tried to recovery and run the bat file and nope... no luck .... any ideas how can I do it, i create a zip file with the framework, the apk is easy to install my issue is with the framework.
Thanks,
javcarbe said:
i tried with flash gordon but doesnt work.... also i tried to recovery and run the bat file and nope... no luck .... any ideas how can I do it, i create a zip file with the framework, the apk is easy to install my issue is with the framework.
Thanks,
Click to expand...
Click to collapse
I guess you just have to turn on usb debugging, connect your device to your pc and execute InstallXposedFramework.bat and InstallXposedInstaller.bat
I did and nothing