Hi guys, I got a little stuck here..
Got myself a new DesireX.
First tried to root it with the tool: http://forum.xda-developers.com/showthread.php?t=1943822
Got stuck on an error, so tried in manually http://forum.xda-developers.com/showthread.php?t=2076675
Followed the tutorial and flashed latest TWRP.
Flashed Superuser, checked in OS for SU access: worked.
So far, I have tested following ROMs:
AOKP http://forum.xda-developers.com/showthread.php?t=2291833
mySENSEdx+ http://forum.xda-developers.com/showthread.php?t=2249760
xPirt ROM v2.1 http://forum.xda-developers.com/showthread.php?t=2131511
MIUI http://forum.xda-developers.com/showthread.php?t=2336358
my procedure:
# erase cache via fastboot
# flash boot via fastboot
# reboot to bootloader
# full wipe / wipe dalvik
# install rom
# reboot
The only one working is MIUI, but total instable with reboots and hang ups.
The others dont boot, I get stuck with a black screen or at the htc logo.
Even the stockrom won't boot !!
I've also tried other recoverys:
TWRP
CWM
Nexusrecovery
Did I do something wrong during rooting?
TWPR sometimes wanted to repair my permissions.
The phone has not to be s-off for flashing roms I presume?
Help would be greatly appreciated. No phone right now
Unlocked
Proto PVT Ship S-On
Hboot 1.25.0002
Radio 1.15.40.04
emmc boot
cheers
What i miss in your procedure is the flashing of the Rom's boot image. In most topics from roms, the image is attached in the first post.
Sent from my HTC Desire X using xda app-developers app
You tried to reflash boot after flashing the ROM? I'm not sure, but it could be an issue.
---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------
fleischverpackung said:
my procedure:
# erase cache via fastboot
# flash boot via fastboot
# reboot to bootloader
# full wipe / wipe dalvik
# install zip
# reboot
Click to expand...
Click to collapse
DeXeS said:
What i miss in your procedure is the flashing of the Rom's boot image. In most topics from roms, the image is attached in the first post.
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
He flahes boot before ROM, you probably missed it...
People look at hboot 1.25 it means you have to install a JB recovery, @op did you install a JB version recovery?
Did you changed updater-script mountpoints before flash an ICS rom?
xpirt
Ok, so it seems that it doesn't matter, wether if you install rom first and then flash boot, or vice versa.
Ive tried it several times in several orders on all recoveries.
@xpirt
Yes, JB recoveries.
I don't know about updater-script mountpoints .
fleischverpackung said:
Ok, so it seems that it doesn't matter, wether if you install rom first and then flash boot, or vice versa.
Ive tried it several times in several orders on all recoveries.
@xpirt
Yes, JB recoveries.
I don't know about updater-script mountpoints .
Click to expand...
Click to collapse
If you install an ICS Rom like MIUI v4, ShadowDX, xPirt, etc. you have to edit META-INF/com/google/android/updater-script and there are the numbers 25-25-27, change them to 24-25-26.
And flash always boot.imgs attached on threads.
xpirt
I always use the boot.img provided with the rom.
there are the numbers 25-25-27, change them to 24-25-26
Click to expand...
Click to collapse
I checked MIUI and xPirt ROM @ META-INF/com/google/android/updater-script with the editor, but I cant find the numbers.
btw thanks for your fast reply
fleischverpackung said:
I always use the boot.img provided with the rom.
I checked MIUI and xPirt ROM @ META-INF/com/google/android/updater-script with the editor, but I cant find the numbers.
btw thanks for your fast reply
Click to expand...
Click to collapse
The ones with mount(), format() or delete/delete_recursive().. press CTRL-F on Notepad++ and search these numbers.
Eg. mmcblk0p25 <- edit this.
xpirt
I noticed a thingie :
fleischverpackung said:
my procedure:
# erase cache via fastboot
# flash boot via fastboot
# reboot to bootloader
# full wipe / wipe dalvik
# install rom
# reboot
Click to expand...
Click to collapse
First flash boot , and THEN erase cache .
I had the same problem yesterday when I flashed mySENSEdx+ and it fixed it for me .
Uizz.UW said:
I noticed a thingie :
First flash boot , and THEN erase cache .
I had the same problem yesterday when I flashed mySENSEdx+ and it fixed it for me .
Click to expand...
Click to collapse
ok just did it in the order you suggested.
bah if that's the reason it hasn't been working.. :silly:
it seems to be more stable.
@xpirt: numbers were already changed in the rom zips.
thx though
Related
Hi people!
Can you look into this boot.img? After editing it with kitchen to support init.d scripts, ecc. I get a new JB boot.img that have 4.4mb, is this normal?
If yes, it can be used with 1.24 hboot, right?
LINK: http://d-h.st/1Uz
If someone can give me some info about this kernel I will really appreciate this.
xpirt
xpirt said:
Hi people!
Can you look into this boot.img? After editing it with kitchen to support init.d scripts, ecc. I get a new JB boot.img that have 4.4mb, is this normal?
If yes, it can be used with 1.24 hboot, right?
LINK: http://d-h.st/1Uz
If someone can give me some info about this kernel I will really appreciate this.
xpirt
Click to expand...
Click to collapse
Hmm... What did you modify? Im sure you removed something to make it that small And I think you should have modified it using ubuntu (well thats the only way that I know to be able to modify a kernel and I don't use kitchen that much too ) correct me if Im wrong hehe maybe it should work though That would be awesome hurrah for not wating for the OTA LOL
4.4mb is not small... the actual size of JB boot.img is 4423 KB (4.31MB).
The Android Manual said:
Hmm... What did you modify? Im sure you removed something to make it that small And I think you should have modified it using ubuntu (well thats the only way that I know to be able to modify a kernel and I don't use kitchen that much too ) correct me if Im wrong hehe maybe it should work though That would be awesome hurrah for not wating for the OTA LOL
Click to expand...
Click to collapse
So.. Cygwin is a collection of tools which provide a Linux look and feel environment for Windows, so yes we can edit kernel on windows.
But I didn't edit manually nothing so far. Kitchen extracted automatically kernel & ramdisk to add init.d support and than it repacked it but the final kernel is only 4.4mb.
This is what I did and what I got
xpirt
ckpv5 said:
4.4mb is not small... the actual size of JB boot.img is 4423 KB (4.31MB).
Click to expand...
Click to collapse
For me is 15.9 mb
Did they not update hboot to make larger partitions like /boot?
xpirt
xpirt said:
......the final kernel is only 4.4mb.
This is what I did and what I got
xpirt
Click to expand...
Click to collapse
And that's a correct size... so what actually your problem is ?
---------- Post added at 12:22 AM ---------- Previous post was at 12:18 AM ----------
xpirt said:
For me is 15.9 mb
Did they not update hboot to make larger partitions like /boot?
xpirt
Click to expand...
Click to collapse
From where you got 15.9 mb ? a Nandroid backup ?
Get it from the OTA zip .. someone uploaded that somewhere before
xpirt said:
Hi people!
Can you look into this boot.img? After editing it with kitchen to support init.d scripts, ecc. I get a new JB boot.img that have 4.4mb, is this normal?
If yes, it can be used with 1.24 hboot, right?
LINK: http://d-h.st/1Uz
If someone can give me some info about this kernel I will really appreciate this.
xpirt
Click to expand...
Click to collapse
It's the correct size of jb kernel. Just the recovery generate bigger with the backup. But it's need to be less then 4mb for 1.24 hboot. But if you really want to try the jb rom, there is a way. You forgot that we have two boot partiton.
1. Install the jb rom with recovery and do a factory reset.
2. Reboot too bootloader
3. Flash jb kernel to recovery partition: fastboot flash recovery boot.img
4. Reboot to recovery will boot to the jb rom.
atis112 said:
It's the correct size of jb kernel. Just the recovery generate bigger with the backup. But it's need to be less then 4mb for 1.24 hboot. But if you really want to try the jb rom, there is a way. You forgot that we have two boot partiton.
1. Install the jb rom with recovery and do a factory reset.
2. Reboot too bootloader
3. Flash jb kernel to recovery partition: fastboot flash recovery boot.img
4. Reboot to recovery will boot to the jb rom.
Click to expand...
Click to collapse
I understand hehehe..
So kitchen remove recovery's backup extra stuff from kernel, also.
But what about two kernel partitions? There is not only one (/boot)?
Thanks,
xpirt
xpirt said:
I understand hehehe..
So kitchen remove recovery's backup extra stuff from kernel, also.
But what about two kernel partitions? There is not only one (/boot)?
Thanks,
xpirt
Click to expand...
Click to collapse
No. The recovery is the second boot partition If you flash the JB kernel to recovery partition you can boot to jb.
atis112 said:
No. The recovery is the second boot partition If you flash the JB kernel to recovery partition you can boot to jb.
Click to expand...
Click to collapse
But no more custom recovery, right?
xpirt
xpirt said:
But no more custom recovery, right?
xpirt
Click to expand...
Click to collapse
Yes.
atis112 said:
Yes.
Click to expand...
Click to collapse
Hehe.. Thanks for info.
But an uncertain, now.. If you go into bootloader->recovery.. It boots JB??
xpirt
xpirt said:
Hehe.. Thanks for info.
But an uncertain, now.. If you go into bootloader->recovery.. It boots JB??
xpirt
Click to expand...
Click to collapse
Yes. But you need to "reboot to recovery" every time when you want to reboot your phone.
atis112 said:
Yes. But you need to "reboot to recovery" every time when you want to reboot your phone.
Click to expand...
Click to collapse
Ah.. you're right
It can be used the same thing for recovery?
I will not be surprised if yes.. xD
xpirt
xpirt said:
Ah.. you're right
It can be used the same thing for recovery?
I will not be surprised if yes.. xD
xpirt
Click to expand...
Click to collapse
I don't know what do you mean now!!??
atis112 said:
I don't know what do you mean now!!??
Click to expand...
Click to collapse
If you use: fastboot flash boot recovery.img... xD
xpirt
xpirt said:
If you use: fastboot flash boot recovery.img... xD
xpirt
Click to expand...
Click to collapse
recovery image is bigger than boot partition, so no
@atis112,
The thing you mentioned, nice trick. I'm thinking of testing JB using that method. Seems safe enough to me.
So is there a JB ROM or backup which i can flash??? What i see is this:
1. Flash your modified recovery,
2. Restore the JB NAND backup from someone.
3. Install the kernel to recovery partition, reboot to recovery from fastboot and just wait.
Is that right???
Regards
atis112 said:
recovery image is bigger than boot partition, so no
Click to expand...
Click to collapse
Ah, you're right I forgot
Thank you atis!
xpirt
neXus PRIME said:
@atis112,
The thing you mentioned, nice trick. I'm thinking of testing JB using that method. Seems safe enough to me.
So is there a JB ROM or backup which i can flash??? What i see is this:
1. Flash your modified recovery,
2. Restore the JB NAND backup from someone.
3. Install the kernel to recovery partition, reboot to recovery from fastboot and just wait.
Is that right???
Regards
Click to expand...
Click to collapse
Just a bit correction: Use one of your ics recoverys! (You have the old partition table) And i think better if we made an installable zip from jb rom. And so:
Flash jb rom from your recovery
Wipe data and cache
Reboot to bootloader
Flash kernel to recovery partition
Reboot to recovery from bootloader
Enjoy the official jb rom
I think it's the only safe way to use JB without OTA update. You can reflash a recovery and go back to ics when you want.
hello,
I have got a Desire x after my sister becouse she got a new phone,
at first the desire x was randomly rebooting but ive read on different forums and there was lots of was to stop that ,
so i picked the easyest way to update
so i went to settings, about phone and clicked for the phone to cheak for updates
and it did find the update to jb so i did
and every thing worked fine but i like to play real racing 3 but this device is not compatable so i downloaded the apk from a different source
but i the app opened and than closed
so i toughed that i need to root to install this app so i began
http://forum.xda-developers.com/showthread.php?t=2316662
i read the aboves guide how to do it but i found a tool
http://forum.xda-developers.com/showthread.php?t=1943822
and i used it becouse i found it more easy and i unlocked bootloader flashed twrp 2.6,flashed superuser and cheaked if phone is rooted with root cheaker and it sayed that my device is not fully rooted (or something like this) even busy box was saying that there are no root premission
but so i was trying to redo it manually but when i wanted to do something it sayed [waiting for device]...
and nothing i tryed it on 2 pcs and nothing but i flashed a rom and thoughed that after i will do it i will be able to flash via fastboot the boot.img file but nothing and i think ive bricked my device so i need help to get out of this
the_ziom said:
hello,
I have got a Desire x after my sister becouse she got a new phone,
at first the desire x was randomly rebooting but ive read on different forums and there was lots of was to stop that ,
so i picked the easyest way to update
so i went to settings, about phone and clicked for the phone to cheak for updates
and it did find the update to jb so i did
and every thing worked fine but i like to play real racing 3 but this device is not compatable so i downloaded the apk from a different source
but i the app opened and than closed
so i toughed that i need to root to install this app so i began
http://forum.xda-developers.com/showthread.php?t=2316662
i read the aboves guide how to do it but i found a tool
http://forum.xda-developers.com/showthread.php?t=1943822
and i used it becouse i found it more easy and i unlocked bootloader flashed twrp 2.6,flashed superuser and cheaked if phone is rooted with root cheaker and it sayed that my device is not fully rooted (or something like this) even busy box was saying that there are no root premission
but so i was trying to redo it manually but when i wanted to do something it sayed [waiting for device]...
and nothing i tryed it on 2 pcs and nothing but i flashed a rom and thoughed that after i will do it i will be able to flash via fastboot the boot.img file but nothing and i think ive bricked my device so i need help to get out of this
Click to expand...
Click to collapse
It's not bricked, I think you need to reinstall a recovery. I recommend TWRP 2.5 instead of 2.6 because 2.5 has no bugs. Try to restore your nandroid backup (if you haven't any try one of these: http://forum.xda-developers.com/showthread.php?t=2324815 and choose your cid) and then flash SuperSU: http://download.chainfire.eu/supersu
PS: you can use the tool for installing custom recovery, only choose ''your own recovery'' and click on the recovery image
GtrCraft said:
It's not bricked, I think you need to reinstall a recovery. I recommend TWRP 2.5 instead of 2.6 because 2.5 has no bugs. Try to restore your nandroid backup (if you haven't any try one of these: http://forum.xda-developers.com/showthread.php?t=2324815 and choose your cid) and then flash SuperSU: http://download.chainfire.eu/supersu
PS: you can use the tool for installing custom recovery, only choose ''your own recovery'' and click on the recovery image
Click to expand...
Click to collapse
thank you but i dont have any backup and remeber i flashed a different rom and black screen al the time
the_ziom said:
thank you but i dont have any backup and remeber i flashed a different rom and black screen al the time
Click to expand...
Click to collapse
You can get a nandroid backup from that link, only read everything over there very carefully. And after that flashing superSU
GtrCraft said:
You can get a nandroid backup from that link, only read everything over there very carefully. And after that flashing superSU
Click to expand...
Click to collapse
yes but i cant get cid becouse system does not boot up and fastboot does not see my device bu i will try
the_ziom said:
yes but i cant get cid becouse system does not boot up and fastboot does not see my device bu i will try
Click to expand...
Click to collapse
Reinstall the drivers and you can use the All In One tool to get your cid
GtrCraft said:
Reinstall the drivers and you can use the All In One tool to get your cid
Click to expand...
Click to collapse
yes but i allready tryed reinstalling deivers maybe you could give me a link to specyfic drivers
the_ziom said:
yes but i allready tryed reinstalling deivers maybe you could give me a link to specyfic drivers
Click to expand...
Click to collapse
Use the drivers given in the tool: http://www.hasoon2000.info/getdownload.php?file=HTC Drivers/HTCDriver.exe
GtrCraft said:
It's not bricked, I think you need to reinstall a recovery. I recommend TWRP 2.5 instead of 2.6 because 2.5 has no bugs. Try to restore your nandroid backup (if you haven't any try one of these: http://forum.xda-developers.com/showthread.php?t=2324815 and choose your cid) and then flash SuperSU: http://download.chainfire.eu/supersu
PS: you can use the tool for installing custom recovery, only choose ''your own recovery'' and click on the recovery image
Click to expand...
Click to collapse
Dude if its saying not rooted you were supposed to flash the supersu.zip in twrp and then update it then you would have root privleges you flashed a rom without root the supersu didnt you? And it basically bricked it so hold vol down and power boot into h boot go to recovery it will boot you into twrp check to see if you do have that supersu.zip if you have it flash it and you dont have s-off look in that rom package and find the kernel (boot.img) flash it and wipe your dalvic cache and your cache and it should boot into that rom but if you dont have that supersu.zip you mite have to side load it then flash it
sent from my one x+ if i helped you out hit that thanks button
gothicasshole said:
Dude if its saying not rooted you were supposed to flash the supersu.zip in twrp and then update it then you would have root privleges you flashed a rom without root the supersu didnt you? And it basically bricked it so hold vol down and power boot into h boot go to recovery it will boot you into twrp check to see if you do have that supersu.zip if you have it flash it and you dont have s-off look in that rom package and find the kernel (boot.img) flash it and wipe your dalvic cache and your cache and it should boot into that rom but if you dont have that supersu.zip you mite have to side load it then flash it
sent from my one x+ if i helped you out hit that thanks button
Click to expand...
Click to collapse
but i flashed supersu and flashed the boot.img flashed the rom i want and still blank screen
the_ziom said:
but i flashed supersu and flashed the boot.img flashed the rom i want and still blank screen
Click to expand...
Click to collapse
Just restore the nandroid backup as I told earlier and flash the SuperSU I gave in the link
GtrCraft said:
Just restore the nandroid backup as I told earlier and flash the SuperSU I gave in the link
Click to expand...
Click to collapse
ahumm how to restore it?
sorry but i got no cloue about this phone
ive rooted htc wildfire, sensation
and samsung s2 and s3 but this phone i made a big fail with
the_ziom said:
ahumm how to restore it?
Click to expand...
Click to collapse
Look at the second post in thread with the nandroid backups
GtrCraft said:
Look at the second post in thread with the nandroid backups
Click to expand...
Click to collapse
unfortunetly i restored and still have the black screen promlem
the_ziom said:
unfortunetly i restored and still have the black screen promlem
Click to expand...
Click to collapse
You flashed the boot.img?
GtrCraft said:
You flashed the boot.img?
Click to expand...
Click to collapse
but what boot.img
im very confused
the_ziom said:
but what boot.img
im very confused
Click to expand...
Click to collapse
ok sry the stock boot.img but u forgot that pc does not see my device right?
the_ziom said:
but what boot.img
im very confused
Click to expand...
Click to collapse
Turn your phone into fastboot mode (holding power and volume down when turning on) and plug it into your pc.
Extract the zip file and run ''Install Boot.img.bat'' and reboot
GtrCraft said:
Turn your phone into fastboot mode (holding power and volume down when turning on) and plug it into your pc.
Extract the zip file and run ''Install Boot.img.bat'' and reboot
Click to expand...
Click to collapse
but u forgot that my pc does not see my device right?
the_ziom said:
but u forgot that my pc does not see my device right?
Click to expand...
Click to collapse
Even after reinstalling drivers?
Intro: Below are the instructions for 3 steps to get Kitkat 4.4 (140.44.3.ghost_att) running on the AT&T moto x with locked bootloaders:
Install full 139.44.44.ghost_att (leaked) rom
Patch the rom to 140.44.3.ghost_att (ota to leak)
Patch the modem to the 140.44.3.ghost_att version
The updates came in stages, otherwise it would not have been my intention for this to be so long and messy. I soon hope to create a single rom and simplify the instructions. Testers can help with the WIP items below...
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
This rom is simply a flashable zip made from the ATT 4.4 leak which will install version 139.44.44. It is intended for the ATT moto x with locked bootloaders, however it should work with an unlocked bootloader if you fastboot flash the included boot.img. The flashable zip does not modify the bootloader or anything besides /system, but the full instructions will wipe out everything.
Prerequisite:
Att moto x with either the .51 (original) or .54 (1st OTA) stock rom
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA AND SDCARD.
Instructions for ATT moto x with locked bootloader:
root with PwnMyMoto or RockMyMoto (for .51 or .54 respectively, thanks jcase)
install safestrap (thanks Hashcode and Team Win)
download rom to sdcard (motox-att-kitkat-leak-44.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
enter safestrap recovery (TWRP) and activate the stock-slot
flash rom (motox-att-kitkat-leak-44.zip) to the stock-slot using TWRP recovery
immediately flash supersu using TWRP recovery
within TWRP reboot to bootloader
flash boot.img (included in ROM) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
erase cache: fastboot erase cache
erase userdata: fastboot erase userdata (This wipes everything) This is not necessary. Thanks HeroSon.
powerup normally and enjoy
Update 11/17/2013: I made a patch to safely apply the ota that was received by people running the att 4.4 leak. This will bring the system build up to 140.44.3.ghost_att. The patch script DOES NOT modify anything except /system, and should be safe. The updated kernel (boot.img) is included in the zip. In case something goes wrong, backup your data to be on the safe side. Here are the Instructions:
Complete the installation of the att 4.4 leak (above instructions)
Reinstall safestrap This is not necessary. Thanks HeroSon.
Download the patch to sdcard (motox-140.44.3.ghost_att-ota-safepatch.zip, link below)
Reboot into safestrap recovery (TWRP)
Install the patch (motox-140.44.3.ghost_att-ota-safepatch.zip)
within TWRP reboot to bootloader
flash boot.img (included in the patch) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
powerup normally
Update 11/18/2013: I attached a link to the modem patch that will update the 139.44.44 modem to a 140.44.3 modem. I really wanted to create a fastboot flashable NON-HLOS.bin image, but I haven't tested the procedure. Here are the instructions for the modem patch that I have tested:
Download the modem patch to the sdcard (motox-140.44.3.ghost_att-modem-patch.zip, link below)
Fastboot flash NON-HLOS.bin (included within the zip): fastboot flash modem NON-HLOS.bin
erase modemst1: fastboot erase modemst1 (I've done these erases a few times. They are prudent when you flash a modem.)
erase modemst2: fastboot erase modemst2
Reboot into safestrap recovery TWRP
Install the modem patch (motox-140.44.3.ghost_att-modem-patch.zip)
Powerup normally
Notes:
I am running the modem from the .54 ota, and it works with kitkat. I am not sure about the original .51 modem. The 140.44.3 modem is necessary after running patch to 144.44.3. This fixes the settings->security force close.
The safestrap "recovery or continue" screen still appears when you boot. If you erased userdata, reinstall safestrap to get all of the program back.
You should always be able to flash back to stock, as this procedure does not modify your bootloader.
There is a new version of safestrap. These instructions work with either v3.63 and v3.65. (Thanks HeroSon.)
I get a FC in settings->security on the 140.44.3 (patched) version. So far this is the only problem I have noticed. This force close is fixed by the modem patch.
WIP: I would like testers to help with the following:
What happens if you skip step 12 and don't erase useradata (this will keep [more of] safestrap intact)?
How do you remove safestrap manually?
Safestrap has been updated. Does the original 139.44.44 rom now run in a rom slot with 4.2.2 running in the stock-slot? What about the patches? I tried it - doesn't work.
Once 4.4 is installed in the stock-slot, can you backup the stock slot and restore to a rom-slot? (I'm guessing it works this way.) I guessed wrong. This doesn't work. Apparently safestrap needs a bit of tweaking to work with KK.
Is it possible for Safestrap TWRP to flash boot.img to the stock slot? (My experience is that it did not flash boot.img when using a rom-slot)
To clean up this mess, I am considering making a single rom that includes the base 4.4 version with the safepatch included. PM if you want to help by testing this all in one rom once I have it finished. There is a new rom of the official att 4.4.
I have an 100MB ext4 image of /modem. I would like guidance making a fastboot flashable non-HLOS.bin image. (Otherwise I wont be able to combine the leak and the patch.) I see instructions that might work if someone wants to try it and report their findings: http://forum.xda-developers.com/showthread.php?t=1588461 The official att 4.4 SBF includes NON-HLOS.bin
Part of the stock modem procedure is to flash "fsg.mbn", but I have not done that because I have been able to confirm that you can downgrade after flashing it. Can anyone confirm that this is safe on the moto x? (http://forum.xda-developers.com/showthread.php?t=2529569) This works.
139.44.44 rom download : http://www.androidfilehost.com/?fid=23212708291677349
rom patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678076
modem patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678561
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
Original source files: http://rootzwiki.com/topic/107721-att-moto-x-44-leak/ (thanks designgears)
ooo yeah !! Nice job !!
Sa sens le Rooting icite !!
Wish mine was from AT&T, still have one year of warranty....cant see the time when kitkat comes global.
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
How do I do steps 9-12?
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Sent from my XT1053
rubiksmoose said:
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It might work without the wipe. Honestly, I tried this so many times that I quit once I had something that worked... I attributed most of my failures to a incompatibility between safestrap and the 4.4 boot process, but each of those attempts was done to a rom slot and not the stock slot.
Hopefully someone else can 'give it a whirl' and report their findings.
penpen72 said:
How do I do steps 9-12?
Click to expand...
Click to collapse
These steps are done using "FASTBOOT" from a PC while the phone is booted to the bootloader in fastboot mode.
phositadc said:
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Click to expand...
Click to collapse
The rom was made from the original leak. I have been thinking about the OTA, but I am unclear how to approach this.
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
penpen72 said:
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
Click to expand...
Click to collapse
I assume you are on windows. First you need to download the FASTBOOT.exe program for our Motorola phones, and make sure the fastboot drivers install on your PC. (Maybe someone can help with this link.) Then you can issue the "fastboot ..." commands 9-12 I listed above from your PC with your phone plugged into the PC.
You certainly need to flash /boot, and you should also flash boot to recovery to allow RW access to /system. It might be possible to skip the "erase userdata" step, but that is unclear to me at this moment.
How is the leaked ROM working for you? Worth it? Any bugs or anything?
rubiksmoose said:
How is the leaked ROM working for you? Worth it? Any bugs or anything?
Click to expand...
Click to collapse
Everything is working fine. Take a look here for other people's observations:http://forum.xda-developers.com/showthread.php?t=2517577
There are only two odd things I have noticed. 1) the recent apps screen acts a bit strange when you swipe away apps 2) the transparent status bar becomes less transparent when you go for a drive and the "driving" notification is displayed. It is almost not worth mentioning, and a reboot fixes this issue.
It is hard to answer the "worth it" question. Ultimately, it is a still a smartphone with the same core capabilities, but I enjoy the challenge and the opportunity to learn something.
[edit]I am starting to think that there is additional battery drain vs the .54 ota version. "Wakelock detector" doesn't work, and settings->battery shows "Android System" at the top. This is a 'deal breaker' for me. I'll try and figure out how to apply the 4.4 ota without modifying the bootloader.[/edit]
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
n1ckr0th said:
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
Click to expand...
Click to collapse
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Ctrl-Freak said:
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Click to expand...
Click to collapse
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
n1ckr0th said:
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
Click to expand...
Click to collapse
Yes. After you have 4.4 working, you must still boot to recovery to enable RW mode on /system. Step 10 ensures you have the 4.4 boot.img in the recovery partition.
(The stock bootloader is still enforcing RO mode for a normal boot.)
I install this and skip step 12 and don't erase useradata. Everything working and all the data still there.
So can I clarify a few things for myself?
You made this by taking the leak files and packaging them into the zip, and it just works with safestrap now? Can you explain what you did to make the leak imgs Safestrap-bootable?
j2cool2012 said:
You made this by taking the leak files and packaging them into the zip,
Click to expand...
Click to collapse
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Can you explain what you did to make the leak imgs Safestrap-bootable?
Click to expand...
Click to collapse
Nothing.
and it just works with safestrap now?
Click to expand...
Click to collapse
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Ctrl-Freak said:
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Nothing.
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Click to expand...
Click to collapse
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
j2cool2012 said:
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
Click to expand...
Click to collapse
the Att bloatware and carrier name in notification bar scared me away
Hi, first of all, my English is bad and i'm a noob at installing custom roms
My HOX+ is rooted and i have the TWRP Recovery installed.
So, i downloaded the newest CM11 Nightly for my device (enrc2b) from the Cyanogenmod site.
When i try to flash it with TWRP it says:
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E:Error executing updater binary in zip ' /sdcard/cm-11-20140902-NIGHTLY-enrc2b.zip
Error flashing zip ' /sdcard/cm-11-20140902-NIGHTLY-enrc2b.zip
I also downloaded a Snapshot version of CM11
It says:
Skipping MD5 check: no MD5 file found
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip ' /sdcard/cm-11-20140308-SNAPSHOT-M4-enrc2b.zip
Error flashing zip ' /sdcard/cm-11-20140308-SNAPSHOT-M4-enrc2b.zip
So finally i downloaded the CM10.2.1 Version
I wiped all cache and data and did a factory reset.
After flashing the .zip and rebooting the phone, but i got stuck in a boot loop (i think) because i waited like 20 minutes but the boot animation didn't change (blue guy with the arrow). Did i do something wrong
I just restored my phone to the backup i made (stock rom)
If you need any information about my phone or something just say it.
I also heard about using CWM instead of TWRP but i don't know how to change it.
PLZ HELP :crying:
CWM recovery
Install this recovery for installing CM.
And don't forget to redo your backup after installing the new recovery before installing CM.
[email protected] said:
Install this recovery for installing CM.
And don't forget to redo your backup after installing the new recovery before installing CM.
Click to expand...
Click to collapse
Thx, I will try it
Sent from my HTC One X+ using XDA Free mobile app
I'm working with a Mac so it might take a while before i understand everything but i'll let you know if it worked.
So yesterday i installed the CWM and flashed Cyanogenmod11 Nightlies at 00:10. I got the boot screen with the guy and the arrow spinning, but when i wake up at 7:00 it was still in the Cyanogenmod boot screen wit the arrow (the arrow was lagging).
So i tried flashing the Snapshot version and it also didnt pass the screen with the arrow (lagging)
After that i flashed the CM10.2 and the arrow wasnt lagging anymore but it didnt pass the screen with the arrow
Every time before i installed another version i did a Factory reset in CWM
So am i doing something wrong plz help?
Sent from my HTC One X+ using XDA Free mobile app
Anthony26 said:
So yesterday i installed the CWM and flashed Cyanogenmod11 Nightlies at 00:10. I got the boot screen with the guy and the arrow spinning, but when i wake up at 7:00 it was still in the Cyanogenmod boot screen wit the arrow (the arrow was lagging).
So i tried flashing the Snapshot version and it also didnt pass the screen with the arrow (lagging)
After that i flashed the CM10.2 and the arrow wasnt lagging anymore but it didnt pass the screen with the arrow
Every time before i installed another version i did a Factory reset in CWM
So am i doing something wrong plz help?
Sent from my HTC One X+ using XDA Free mobile app
Click to expand...
Click to collapse
did you flash the boot.img in fastboot before installing the rom?
reaper90 said:
did you flash the boot.img in fastboot before installing the rom?
Click to expand...
Click to collapse
Do you mean with "boot.img" the recovery-clockwork-touch-6.0.4.8-enrc2b.img
This is all i did (i dunno of the screenshot will display i uploaded it as attachment)
I've flashed the recovery.img, thats also the only thing i downloaded on the CWM site.
I also downloaded the Cyanogenmod rom on the CyanogenMod Download site or do i have to download it from the CWM enrc2b Roms?
Edit: I've found out that the boot.img is needed for the device to boot and that i can flash it in recovery.
But is there a special HOX+ boot.img or a Cyanogenmod boot.img or whatever i need? And where can i find it
Anthony26 said:
Do you mean with "boot.img" the recovery-clockwork-touch-6.0.4.8-enrc2b.img
This is all i did (i dunno of the screenshot will display i uploaded it as attachment)
I've flashed the recovery.img, thats also the only thing i downloaded on the CWM site.
I also downloaded the Cyanogenmod rom on the CyanogenMod Download site or do i have to download it from the CWM enrc2b Roms?
Edit: I've found out that the boot.img is needed for the device to boot and that i can flash it in recovery.
But is there a special HOX+ boot.img or a Cyanogenmod boot.img or whatever i need? And where can i find it
Click to expand...
Click to collapse
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
reaper90 said:
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
Click to expand...
Click to collapse
Thx,
I forgot to unzip the file :silly:
I'll try it and let you know of it worked
reaper90 said:
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
Click to expand...
Click to collapse
Alright i did what u said and i have 1 more question;
If i want to go back to the stock rom, do i need to flash a "stock" boot.img?
Edit: Cyanogenmod is working, i only need to install the Google apps (i think).
Stock boot image
You can flash the Nik3r version to come back to the stock boot image.
And you need to flash the GAPPS in recovery for the Google apps
Anthony26 said:
Alright i did what u said and i have 1 more question;
If i want to go back to the stock rom, do i need to flash a "stock" boot.img?
Edit: Cyanogenmod is working, i only need to install the Google apps (i think).
Click to expand...
Click to collapse
If you want to go back to stock completely (including relocked bootloader) you will need everything completely stock and matching your phones CID. Of course you will need to flash the corresponding boot.img for every rom. But as far as i know/tried, nik3rs oxp_kk kernel works for all 4.4 roms and the other version works for all Sense5 based custom roms and maybe stock rom (if you don't need relocked bootloader).
[email protected] said:
You can flash the Nik3r version to come back to the stock boot image.
And you need to flash the GAPPS in recovery for the Google apps
Click to expand...
Click to collapse
reaper90 said:
If you want to go back to stock completely (including relocked bootloader) you will need everything completely stock and matching your phones CID. Of course you will need to flash the corresponding boot.img for every rom. But as far as i know/tried, nik3rs oxp_kk kernel works for all 4.4 roms and the other version works for all Sense5 based custom roms and maybe stock rom (if you don't need relocked bootloader).
Click to expand...
Click to collapse
Thx, i have installed the Gapps and it's working good.
The only thing i notice is the fast battery drain, is it possible to underclock some thing so the battery last longer, and which apps are good for that?
And if i want to go back to the stock rom, i just have to go back to my "stock rom backup" in recovery and flash nik3rs oxp_kk kernel?
Anthony26 said:
Thx, i have installed the Gapps and it's working good.
The only thing i notice is the fast battery drain, is it possible to underclock some thing so the battery last longer, and which apps are good for that?
And if i want to go back to the stock rom, i just have to go back to my "stock rom backup" in recovery and flash nik3rs oxp_kk kernel?
Click to expand...
Click to collapse
no, oxp_kk is just for 4.4 (kitkat) AOSP like roms. there's another non- kk version which works with 4.2.2/sense5 roms, but i don't know about stock roms. There's also a fallback kernel version which should work with all stock and custom 4.2.2/Sense 5 roms.
Here's Repack of the stock kernel
with dm-verity
SONY RIC off
SperSU EnableD
Working on Z4 Tablet (SGP771 - SGP712) 7.1.1 FW 32.4.A.0.160
DOWNLOAD:
SECOND POST
HOW TO INSTALL :
1. Extract zip file And Flash in Fastboot
2. Install TWRP 3.1.1.0 From Here
3. Then Flash SuperSU.zip From Here
4. Done You Get ROOT
Download section
Changelog :
SGP712 aded
dm-verity is Disabled
Sony RIC is Disabled
SR1-SuperSU-v2.82-SYSTEMMODE.zip Installed
busybox Installed
@IlariJ Now Done
Nimadroid said:
@IlariJ
Click to expand...
Click to collapse
THANKS!! :victory:
May i ask, ... would it be possible for you to make a kernel for the SGP712 - Wifi only version too?
Nimadroid said:
@IlariJ Now Done
Click to expand...
Click to collapse
The device boots fine (no longer infinite bootloop), but once it has powered up, the touchscreen doesn't work.
I have rebooted several times and no help.
In TWRP even the touch works.
Can You fix this? @Nimadroid
IlariJ said:
The device boots fine (no longer infinite bootloop), but once it has powered up, the touchscreen doesn't work.
I have rebooted several times and no help.
In TWRP even the touch works.
Can You fix this? @Nimadroid
Click to expand...
Click to collapse
Flash Stock ftf
Then Flash kernel
If don't change I make another one for you
Mr. Schnabel said:
May i ask, ... would it be possible for you to make a kernel for the SGP712 - Wifi only version too?
Click to expand...
Click to collapse
Provide me the kernel.sin from lastest FTF of your device
And i update this poet for you with your device kernel
@Nimadroid -> Send ya a PM
Nimadroid said:
Flash Stock ftf
Then Flash kernel
If don't change I make another one for you
Click to expand...
Click to collapse
Didn't help.:crying:
@ Mr. Schnabel : Goog idea
@ Nimadroid : Thanks in advance for the SGP772 version
ilarij said:
didn't help.:crying:
Click to expand...
Click to collapse
steevou said:
@ mr. Schnabel : Goog idea
@ nimadroid : Thanks in advance for the sgp772 version
Click to expand...
Click to collapse
post updated new device aded
Nimadroid said:
post updated new device aded
Click to expand...
Click to collapse
Kernel works, thanks
---------- Post added at 07:07 PM ---------- Previous post was at 07:02 PM ----------
SGP712 should use this recovery
https://www.androidfilehost.com/?fid=673368273298956222
Nimadroid said:
post updated new device aded
Click to expand...
Click to collapse
Works, thanks!! :victory:
Upgrade from 7.0
Hi,
quick question:
I am on 7.0 with root and DRM fix comming from here: "[Guide] Nougat with DRM fix, root and TWRP* (SGP771)".
Can I simply flash kernel and TWRP as you described on top of these or do I have to restart with any TFT's on 7.11?
Thanks a lot and best regards
Hi guys, i need your help!
Flashed new tft .160 via Flashtool - check
Flash boot via ADB - check
Flash Twrp via ADB - check
Reboot into recovery - nope nope nope ...
No matter what or how i flash i simply cannot boot into recovery
Tried older Twrp versions, in ADB shell everything is ok, no error, .....
simply don´t know what to do anymore hmmmmm ....
Mr. Schnabel said:
Hi guys, i need your help!
Flashed new tft .160 via Flashtool - check
Flash boot via ADB - check
Flash Twrp via ADB - check
Reboot into recovery - nope nope nope ...
No matter what or how i flash i simply cannot boot into recovery
Tried older Twrp versions, in ADB shell everything is ok, no error, .....
simply don´t know what to do anymore hmmmmm ....
Click to expand...
Click to collapse
If you're using SGP712 you need to flash the proper recovery for that device, the one in OP is for SGP771
This one is the correct one (also linked 3 posts above): https://www.androidfilehost.com/?fid=673368273298956222
Well .. actually OP and your´s in 3rd post and here are all 3 the same
Like said tried these here, from androPlus thread, etc etc ...
Flash via fastboot is working but cannot enter recovery after flashing
Tried to access via Power button, volume button, adb command, ... i dont even have a led signal at power on
Mr. Schnabel said:
Well .. actually OP and your´s in 3rd post and here are all 3 the same
Like said tried these here, from androPlus thread, etc etc ...
Flash via fastboot is working but cannot enter recovery after flashing
Tried to access via Power button, volume button, adb command, ... i dont even have a led signal at power on
Click to expand...
Click to collapse
oh, didn't notice, although I'm pretty sure the one in OP was different
It's booting on my device, but the first time I tried it didn't. I think it booted when I accidentally flashed it on the boot partition instead of the recovery one maybe you can try that.
but before, try hot booting it with:
Code:
fastboot boot ~/Downloads/TWRP-3.1.1-lineageos-karin_windy-20170520.img
Hotboot endet in an Bootloop but flashing recovery to Boot helped! Many many Thanks
€dit: Ok my bad didnt work ....
Hotboot didnt work
Flashing recovery to boot did boot up Twrp - Wiped cache/dalvik, flashed SU, Tablet constanty reboot into TWRP instead of system
Flashed Kernel/Boot to Boot - Tab boots into system but no root
Tried to reboot into recovery - no luck