This is not my creation. I merely took the OTA of DP5 and swapped out the boot.img with @bouchigo 's modified boot.img to keep the OTA from forcing encryption.
Big thanks to @bouchigo for his modified boot.img. And to Google for the Developer Preview.
I hope I answer all question that may be asked upfront. I'll briefly explain what I did and how I tested on my own device. Which is the device and OS I'm posting this thread from.
*****Bootloader must be unlocked******
*****And using custom recovery*****
1. I was on stock 6.0.1 rooted and bootloader unlocked.
2. I have Multirom TWRP installed. I have a Pure Nexus in the secondary slot and stock rooted in the primary.
3. Make a back up before you start. Hell live on the edge and don't back it. But don't come complaining here if something happens. You've been warned.
4. Download my zip of the OTA.
5. Download the beta supersu.zip thats floating around.
6. Make sure bootloader is unlocked and you have some version of custom recovery installed.
7. Flash the OTA then the beta SuperSU.
Now this part is up to you.
I did not wipe anything but cache and dalvik before I flashed. So basically I dirty flashed in my primary rom slot over stock rooted 6.0.1.
And then I flashed the SuperSU zip. Everything booted fine, no issues, no hiccups.
I'm now running DP5 with all my data still here and set up just like it was on the previous OS. The only thing I had to do was uninstall all my layers themes and the layers manager apk then install the layers manager that has been fixed for Android N then install all your themes back.
Beware not all themes work. I've had some issues with some causing the settings to Force Close and some causing Developer Options to force close. So I uninstalled those particular layers and used another theme .
I'm using the unlocked 32 gig variant on T-Mobile.
So enough of the jibber jabber here it is:---:
https://drive.google.com/file/d/0B2OabWtEBQcpMkN2MlN2SFVJQnc/view?usp=drivesdk
So to recap :
Yes you can dirty flash over 6.0.1 .
It doesn't matter if you're rooted or not.
Yes you can flash via TWRP or MultiRom
(I have no idea about any rom slot except
The primary rom slot)
No this will not encrypt.
No you don't have to wipe data.
Yes all your data, apks, and settings will remain
If you dirty flash.
Yes this will attracted bikini clad women.
And yes if you make milkshakes at home it.
will bring all the boys to your yard.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6P using XDA-Developers mobile app
Awesomeness! Thanks for this and for the funny read!
Sent from my Nexus 6P using XDA Labs
Will recovery work if we want to revert back to our backup?
Sent from my Nexus 6P using Tapatalk
Couldn't get this to flash using Multirom TWRP.
I always get an error on patching system image unconditionally during install :/
Ended up booting even though TWRP swore there was no OS installed. Thanks!
mattwheat said:
This is not my creation. I merely took the OTA of DP5 and swapped out the boot.img with @bouchigo 's modified boot.img to keep the OTA from forcing encryption.
Big thanks to @bouchigo for his modified boot.img. And to Google for the Developer Preview.
I hope I answer all question that may be asked upfront. I'll briefly explain what I did and how I tested on my own device. Which is the device and OS I'm posting this thread from.
*****Bootloader must be unlocked******
*****And using custom recovery*****
1. I was on stock 6.0.1 rooted and bootloader unlocked.
2. I have Multirom TWRP installed. I have a Pure Nexus in the secondary slot and stock rooted in the primary.
3. Make a back up before you start. Hell live on the edge and don't back it. But don't come complaining here if something happens. You've been warned.
4. Download my zip of the OTA.
5. Download the beta supersu.zip thats floating around.
6. Make sure bootloader is unlocked and you have some version of custom recovery installed.
7. Flash the OTA then the beta SuperSU.
Now this part is up to you.
I did not wipe anything but cache and dalvik before I flashed. So basically I dirty flashed in my primary rom slot over stock rooted 6.0.1.
And then I flashed the SuperSU zip. Everything booted fine, no issues, no hiccups.
I'm now running DP5 with all my data still here and set up just like it was on the previous OS. The only thing I had to do was uninstall all my layers themes and the layers manager apk then install the layers manager that has been fixed for Android N then install all your themes back.
Beware not all themes work. I've had some issues with some causing the settings to Force Close and some causing Developer Options to force close. So I uninstalled those particular layers and used another theme .
I'm using the unlocked 32 gig variant on T-Mobile.
So enough of the jibber jabber here it is:---:
https://drive.google.com/file/d/0B2OabWtEBQcpMkN2MlN2SFVJQnc/view?usp=drivesdk
So to recap :
Yes you can dirty flash over 6.0.1 .
It doesn't matter if you're rooted or not.
Yes you can flash via TWRP or MultiRom
(I have no idea about any rom slot except
The primary rom slot)
No this will not encrypt.
No you don't have to wipe data.
Yes all your data, apks, and settings will remain
If you dirty flash.
Yes this will attracted bikini clad women.
And yes if you make milkshakes at home it.
will bring all the boys to your yard.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
How do you put Black theme??
Enviado do meu Nexus 6P através de Tapatalk
r3ix said:
How do you put Black theme??
Enviado do meu Nexus 6P através de Tapatalk
Click to expand...
Click to collapse
The black them is installed by "Layers Manager". It's called "Swift Black".
These are a few dark/black themes I myself have found to work on with DP5. Well except for "Beltz" and the "Transparent Pro". Those two theme everything OK. It's just in settings a few options , like "About Device" & "Developer Options" for close on me. So I usually just don't install the theme portion for the related apks and use another theme to handle those. Oh and the "Transparent Pro" doesn't seem to wanna them Google Contacts or Dialer.
But other than that I believe the rest seem to do pretty good.
Sent from my Nexus 6P using XDA-Developers mobile app
cvsolidx17 said:
Couldn't get this to flash using Multirom TWRP.
I always get an error on patching system image unconditionally during install :/
Ended up booting even though TWRP swore there was no OS installed. Thanks!
Click to expand...
Click to collapse
No problem. I don't know why it said that. Maybe cuz it hasn't built it from the .img files till first boot. I don't know. Just a guess. Did you dirty flash or wipe everything. And was it on primary or secondary rom slot.
Me myself ...I haven't had much luck getting Android N to boot on a secondary slot. I can flash it there but seems like to get it to boot I have to swap it with the primary. And I assume that's mainly due to having to flash the correct vendor for either "MM" or "N". Kinda like back in the day when you had safestrap but you had to stick with the same Android version because of shared bootloader and kernel and stuff.
Sent from my Nexus 6P using XDA-Developers mobile app
cracjackson said:
Will recovery work if we want to revert back to our backup?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Ive had no issue with just wiping the main 4 (cache, dalvik, system, data) and restoring your backup as long as it has the boot.img and the vender saved with it. If not you may have to flash the proper vender and it boot.img.
Sent from my Nexus 6P using XDA-Developers mobile app
For some reason the download keeps failing.
Sent from my Nexus 6P using Tapatalk
Yea download keeps failing
Sent from my Nexus 6P using Tapatalk
Let me see why
Sent from my Nexus 6P using XDA-Developers mobile app
It's working for me. Don't click the blue "download" button. Click the download arrow at the top of the page.
Sent from my Nexus 6P using XDA-Developers mobile app
Thanks for this, I have this as my primary ROM in Multirom, but I can't load my secondary which is MM based because it needs the Multirom kernel. After installing the MR kernel, DP5 and the secondary ROM refuses to boot. Any ideas?
You need to flash the MM vendor file. Every time you switch between MM and N you need to flash the appropriate Vendor image.
Sent from my Nexus 6P using XDA-Developers mobile app
Download works, rom works. I did a full wipe from pure nexus rom. Installed as instructed on the 1st post.
Now rocking with latest rooted android N!
Thank you very much @mattwheat!
edit:
@mattwheat It turns out I dont have root. I didnt test it at first but now I did. And I can not enter the twrp anymore, it stays on the twrp splashscreen... Any suggestions?
I thought that was the leaked official OTA but just still DP as title said, i feel dumb lol
petzku said:
Download works, rom works. I did a full wipe from pure nexus rom. Installed as instructed on the 1st post.
Now rocking with latest rooted android N!
Thank you very much @mattwheat!
edit:
@mattwheat It turns out I dont have root. I didnt test it at first but now I did. And I can not enter the twrp anymore, it stays on the twrp splashscreen... Any suggestions?
Click to expand...
Click to collapse
Exact thing just happened to me, Full wipe, flashed rom then beta supersu, booted and runs great but no root and TWRP sticks at the splash screen when booting to recovery. Any ideas how to get back into recovery without starting fresh?
Yep, experienced the same thing. Had to back everything up to the laptop and push a factory image back to stock and start all over. Took awhile but phone is nice and clean now. I like N but too many of my apps don't play well with it yet
joefloater said:
Exact thing just happened to me, Full wipe, flashed rom then beta supersu, booted and runs great but no root and TWRP sticks at the splash screen when booting to recovery. Any ideas how to get back into recovery without starting fresh?
Click to expand...
Click to collapse
Just backup everything and wipe userdata and cache with adb.
Related
Hi Xda,
I decided to revert back to stock, got a MD5 checksum error on my nandroid backup (which was in the phone storage). Decided to use one of the custom ROMs which were available on my external SD or even a nandroid backup of my current system but to my surprise CWM won't recognize my external SD anymore and I already wiped cache, system data, and all that stuff clean so I have no OS anymore. Note that until very recently CWM could see my external SD and if I plug it in another phone it works fine so that eliminates the possibility of it being corrupted. I also tried to plugin my usb cable and tried to mount it but got an error. I had another nandroid backup on the phone which worked 5 minutes prior but I deleted it which was obviously a stupid move.
tl;dr: Wiped my phone clean, only have CWM left. Through CWM I Couldn't mount usb, external SD doesn't work anymore, and nandroid backup on the phone storage failed the checksum. What should I do?
if your phone is working download rom manager and flash recovery thru the app...first find the new rom you want and gapps...then flash thru rom manger recovery....then when your done..make sure you make a backup this time....the roms now thru recovery only show sd card because when making backups its more secure..they don't get erased ...
Thanks for your reply but my phone is no longer working CWM is the only thing I have left
reflash cwm with Odin
Get the Odin version HERE
Load it in the pda slot of Odin, out phone in download mode, connect to pc, and let her rip
That version will see the external sd, the new one from Rom manager will not..
Or, get into cwm, mount your USB storage, copy ROM to phone, flash, sigh in relief, feed the zombie...
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
^^ op says he tried that and "got an error"
But yes, feed the zombie, I'm starving!
Just because you wiped everything doesn't mean you only have cwm left. You just have a fresh install of whatever Rom you were running when you did all the wipes. You can reboot into the Rom and move backups around or flash the latest cwm of you're on an old one.
Have you tried just rebooting and moving whatever junk to internal or whatever you need?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
if you format /system, which he says he did, you do not have an os whatsoever.
Boot up your pc and delete the Windows folder then reboot... You think you're gonna have a fresh install of Windows?
My first post is what he needs to do...
Anyone else got anything they wanna add for me to correct? Hahaha
studacris said:
if you format /system, which he says he did, you do not have an os whatsoever.
Boot up your pc and delete the Windows folder then reboot... You think you're gonna have a fresh install of Windows?
Anyone else got anything they wanna add for me to correct? Hahaha
Click to expand...
Click to collapse
I'm guessing he hit the wipe data/factory reset option in cwm. Which wipes data and factory resets and leaves you with a fully functional Rom. He never said he formatted /system but maybe reading comprehension isn't your thing. Thanks for being an ass though.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
studacris said:
if you format /system, which he says he did, you do not have an os whatsoever.
Boot up your pc and delete the Windows folder then reboot... You think you're gonna have a fresh install of Windows?
My first post is what he needs to do...
Anyone else got anything they wanna add for me to correct? Hahaha
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sent from my Galaxy Nexus running official Jelly Bean!!!!
Yup, you're welcome
Phatsnake said:
I already wiped cache, system data, and all that stuff clean so I have no OS anymore.
Click to expand...
Click to collapse
Reading is fun!
studacris said:
Yup, you're welcome
Reading is fun!
Click to expand...
Click to collapse
wiping system data/factory reset != formatting system
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
"And all that stuff, so i have no os anymore"
We can only go by what the op tells us...You assume he means factory reset and doesn't know that doing that doesn't wipe the os... but he says he had no os so that is what we have to go by
Don't assume...it only makes an ass out of u and me
studacris said:
"And all that stuff, so i have no os anymore"
We can only go by what the op tells us...You assume he means factory reset and doesn't know that doing that doesn't wipe the os... but he says he had no os so that is what we have to go by
Don't assume...it only makes an ass out of u and me
Click to expand...
Click to collapse
I'm thinking he only thinks he has no os, he has not mentioned ever trying to reboot. Seeing as he's being noobish (no offense), I'm guessing he's following the standard procedures of pretty much every tutorial and ROM OP, and simply wiping data/factory reset and clearing caches. Thus he should have a nice clean os. I could be completely wrong and he formatted everything, but I doubt that is the case.
I realize assuming can be bad, but I'm just trying to help him in the absolute simplest way possible which seems quite reasonable. :thumbup:
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
yollasho said:
I'm thinking he only thinks he has no os, he has not mentioned ever trying to reboot. Seeing as he's being noobish (no offense), I'm guessing he's following the standard procedures of pretty much every tutorial and ROM OP, and simply wiping data/factory reset and clearing caches. Thus he should have a nice clean os. I could be completely wrong and he formatted everything, but I doubt that is the case.
I realize assuming can be bad, but I'm just trying to help him in the absolute simplest way possible which seems quite reasonable. :thumbup:
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Or you could go by post 3, where he said
Phatsnake said:
Thanks for your reply but my phone is no longer working CWM is the only thing I have left
Click to expand...
Click to collapse
jde984 said:
Or you could go by post 3, where he said
Click to expand...
Click to collapse
he still never said he tried to reboot, but whatever. I'm done. Noobs shouldn't be messing in advanced formatting partitions and **** when they have no idea how to recover. I'm sure you guys can sort it out for him. :thumbup:
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Thanks a lot for the help everyone specially yollasho and studacris and I'm sorry if I caused an argument. I never formatted the phone. I just did data/factory reset, deleted cache and dalvik. I tried to boot to the phone and I did get the custom ROM's splash screen but it never booted so I made the assumption that I lost my OS. I will carefully read the advice everyone gave me again and I will report back once I hopefully get it fixed.
son of a ....
Hahaha well, it's not often i have to say this...but I'm sorry dude, you were right.
Still stand by everything i said....but, my foot tastes funny
Saw this looking for roms for wife's new Note and thought I'd chime in. Since you have cwm, try booting your phone into recovery, and push a new rom to your sd card with adb and flash that.
What you'll do is boot your phone into recovery, connect to your computer and then from a cmd prompt :
1) adb devices
(you should see your device I'd here)
2) adb push somerom.zip /sdcard/somerom.zip
(see transfer here....)
Obviously you'll need to be in the directory on your computer that contains your rom and have your path variable set so you can run adb from anywhere. Then reboot your phone back into recovery, flash, be happy. Hope that helps!
Sent from my SAMSUNG-SGH-I747 using xda premium
studacris said:
reflash cwm with Odin
Get the Odin version HERE
Load it in the pda slot of Odin, out phone in download mode, connect to pc, and let her rip
That version will see the external sd, the new one from Rom manager will not..
Click to expand...
Click to collapse
I used these steps and it did the trick! Thanks a lot! Unfortunately my stock Rom backup is corrupt so I used Team Perfection's UCLF6. Any idea where I can find a pure ATT stock Rom not rooted or deodexed or anything?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
hey, im installed the nightmare rom bassed of cm9 RC 1.5 and i wiped everything and instelled the rom, but everytime i reboot it gets stuck on the boot logo
help Thank u
amazeboy said:
hey, im installed the nightmare rom bassed of cm9 RC 1.5 and i wiped everything and instelled the rom, but everytime i reboot it gets stuck on the boot logo
help Thank u
Click to expand...
Click to collapse
Flash the kernel manually via hasoons tool or adb.
Dark Nightmare said:
Flash the kernel manually via hasoons tool or adb.
Click to expand...
Click to collapse
the nightmare kernel?
amazeboy said:
the nightmare kernel?
Click to expand...
Click to collapse
Any kernel compatible with cm9. You can simply extract the .zip from the rom and flash the boot.img via fastboot (available in Hasoon's tool).
If you still have issues we will need more info about your sytem: s-on? Already on ICS? Which carrier? SuperCID? and anything else you think about.
johnride said:
Any kernel compatible with cm9. You can simply extract the .zip from the rom and flash the boot.img via fastboot (available in Hasoon's tool).
If you still have issues we will need more info about your sytem: s-on? Already on ICS? Which carrier? SuperCID? and anything else you think about.
Click to expand...
Click to collapse
ok thnank u its working but after i did the data trick, data still doesn't work
amazeboy said:
ok thnank u its working but after i did the data trick, data still doesn't work
Click to expand...
Click to collapse
Wipe and flash again, don't forget to flash the kernel again as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe you guys can help me out a little bit. Can't get passed HTC screen.
I'm no expert at flashing, but on simple things I know what I am doing. Everything was fine and I wanted to flash Sport stars CM10 ROM. I did a backup on 4ext like I always do and then wipe flash reboot.
The issue here now is that once i flashed cm10 my phone got stuck on the HTC screen. Did my research found out sports ROM that he uploaded wasn't booting up. I instantly went back to 4ext. Wiped data and cache and restored my fourth bar nexus ROM.
Apparently it said the backup was successful yet when ever I boot it stays stuck at the HTC screen. This happened last night and I just can't seem to figure out shaft to do. I wiped, restored still nothing. Wiped download a different ROM. Still nothing.
S-on, T-Mobile
Edit: Also should be noted on last screenshot I never saw this splash screen before in 4ext. Happens the second I boot up in recovery. And in the small rectangle says something about 4ext not being configured due to an app or something.
I think I should be okay if I just flash clockwork and restore, but I'm not entirely sure.
Sent from my SGH-T959 using xda app-developers app
Flash the kernel for fourth bar manually.
Or reflash fourth bar, then do an advanced restore and restore your data only.
sent from a galaxy you'll never see.
Dark Nightmare said:
Flash the kernel for fourth bar manually.
Or reflash fourth bar, then do an advanced restore and restore your data only.
sent from a galaxy you'll never see.
Click to expand...
Click to collapse
Already in the process of re-downloading Fourth Bar and I will try that method out.
Any idea on why this happened though? I'm still curious.
Sent from my SGH-T959 using xda app-developers app
Dark Nightmare said:
Flash the kernel for fourth bar manually.
Or reflash fourth bar, then do an advanced restore and restore your data only.
sent from a galaxy you'll never see.
Click to expand...
Click to collapse
Did exactly what you said man and still nothing. Still stuck at the HTC screen. Wiped everything flashed a new fresh downloaded ROM, backed up just the data and still nothing. I'm getting worried here.
Sent from my SGH-T959 using xda app-developers app
ifatalityx said:
Did exactly what you said man and still nothing. Still stuck at the HTC screen. Wiped everything flashed a new fresh downloaded ROM, backed up just the data and still nothing. I'm getting worried here.
If all else fails, reload a stock ruu via hboot, that'll wipe everything and restore your device to stock, once it boot's, throw on a custom recovery and go through the usuals to get your custom rom.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Did you manually reflash the kernel like I told you to?
Dark Nightmare said:
Did you manually reflash the kernel like I told you to?
Click to expand...
Click to collapse
How'd I go about doing that? Never had to manually flash a kernel before.
Edit: Researched, flashed Fourth Bar, flashed an ICS kernel. Rebooted Reflashed the kernel. Rebooted, still nothing.
ifatalityx said:
How'd I go about doing that? Never had to manually flash a kernel before.
Edit: Researched, flashed Fourth Bar, flashed an ICS kernel. Rebooted Reflashed the kernel. Rebooted, still nothing.
Click to expand...
Click to collapse
Flash the kernel in the zip file, which is the rom itself.
If that doesn't help, restore to stock via a ruu then attempt again, remembering to flash the kernel manually, in most cases 4EXT will flash the kernel when you reboot from recovery, it will tell you it has a task to complete, the phone should auto reboot on it's not, no this is not a bootloop, just let it be and it should be fine.
Dark Nightmare said:
Flash the kernel in the zip file, which is the rom itself.
If that doesn't help, restore to stock via a ruu then attempt again, remembering to flash the kernel manually, in most cases 4EXT will flash the kernel when you reboot from recovery, it will tell you it has a task to complete, the phone should auto reboot on it's not, no this is not a bootloop, just let it be and it should be fine.
Click to expand...
Click to collapse
I don't know what happened, but my phone is now working. All I did was wipe, restore (didn't flash a kernel or anything fancy just restored) and the phone booted, shutdown and then rebooted and finally started working. Thank you for helping me.
ifatalityx said:
I don't know what happened, but my phone is now working. All I did was wipe, restore (didn't flash a kernel or anything fancy just restored) and the phone booted, shutdown and then rebooted and finally started working. Thank you for helping me.
Click to expand...
Click to collapse
Patience buddy, you're welcome.
ifatalityx said:
I don't know what happened, but my phone is now working. All I did was wipe, restore (didn't flash a kernel or anything fancy just restored) and the phone booted, shutdown and then rebooted and finally started working. Thank you for helping me.
Click to expand...
Click to collapse
Just for future reference, anytime anyone has a bootloop issue that they can't fix in 20 minutes or less.. they should just flash the stock RUU. You can flash the RUU, flash a recovery, and restore a rom in a little over 30 minutes, and then you know that ANY quirk you may have had will have been written over.
Since you had an issue like yours, where you did nothing and it started booting, I am thinking you may have something wrong with your partition scheme.. if you have future issues reflash the RUU as it redoes the actual partitions and everything on them.
Moto X Flashable ROM zip of TMobile 4.3
engineering build System Dump
Huge thanks to TheOrangeRemix for posing the original files at XDA.
This is a flashable zip of the system and boot.img for Moto X 4.3.
This is an engineering build so there are extra logging tools and whatnot but it runs smooth.
This is ghost_retail which is for Tmobile so radio may or may not work on other carriers but it will flash on any Moto X.
As always I am not responsible for you eatting cats or ruining your device
Flash in CWM or TWRP. If you have issues when you reboot you may have to factory reset or at least wipe cache and dalvik.
Download: http://androidhosting.org/Devs/Dhacker29/MotoX/ghost_retail_13.10.0Q2.X_25_eng.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Going to flash this , thanx dhacker. Just one question is the baseband? Can I inject the Rogers radio into this ? and where is it located in the ROM or dies it have to be flashed in fastboot? Coming from an HTC unit and the baseband ( radio) could be flashed in fastboot mode as an update
Sent on my Moto X
The baseband is stsored in a seperate partition so the baseband will not be changed by this. If you don't have data you may need to update the build.prop to match rogers and possibly use system/lib/libqmiservices.so and system/lib/libril-qc-qmi-1.so from the rogers build. Chances are since they are both GSM it may work without any changes.
dhacker29 said:
The baseband is stsored in a seperate partition so the baseband will not be changed by this. If you don't have data you may need to update the build.prop to match rogers and possibly use system/lib/libqmiservices.so and system/lib/libril-qc-qmi-1.so from the rogers build. Chances are since they are both GSM it may work without any changes.
Click to expand...
Click to collapse
Thank, my HTC phone I could flash different basebands but you had to be s- off to do it. I'll let you know what's happens. Probably a good idea to back up apn's I guess
Sent on my Moto X
You can flash radios on the X through fastboot. the fsg.img and NON-0HLOS.img are the radios. I looked in this build and the apns-conf has rogers listed.
Can anyone confirm or deny data out of the box for VZW?
well thinking no...and if u look at dhacker29's pick thats the vzw baseband
Sent from my XT1060 using xda app-developers app
It flashes fine, I get mobile data out of the box on rogers but the only issue I have encountered is navigation home button does absolutely nothing, I suspect it could be that I restored my data and xposed framework messed up system ui. So I'm trying another flash and restore my backed up apps and see if it works
Edit. Navigation home button works now, so you can't restore data from recovery if you installed xposed framework but I guess it would work if you uninstalled xposed and then did a data back up. Oh well, now I have to set everything again
Sent from my A2109A using Tapatalk 4
I'm on sprint, I haven't flashed this yet. Any thoughts on the Sprint version working
Sent from my XT1056 using Tapatalk 2
flashallthetime said:
It flashes fine, I get mobile data out of the box on rogers but the only issue I have encountered is navigation home button does absolutely nothing, I suspect it could be that I restored my data and xposed framework messed up system ui. So I'm trying another flash and restore my backed up apps and see if it works
Edit. Navigation home button works now, so you can't restore data from recovery if you installed xposed framework but I guess it would work if you uninstalled xposed and then did a data back up. Oh well, now I have to set everything again
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Do you find it slower, same or faster then stock 4.2.2?
Sent from my XT1058 using Tapatalk 2
scorpion667 said:
Do you find it slower, same or faster then stock 4.2.2?
Sent from my XT1058 using Tapatalk 2
Click to expand...
Click to collapse
Way slower than the Rogers image, there's so much more bloatware, also the rogers status bar is cleaner, if you use motoxposed module on this the WiFi and data icons over lap. Also getting system ui crash on start up, boot is so much slower, you must realize this is not an official release so it has its bugs.
I would suggest using the rogers image as a base . Back to my back up
Thanks dhacker for your hard work, waiting for some terrific development
Edit: so o reflashed this but a totally clean install and everything is working fine, if you plan on restoring your data I don't recommend it, my system ui problem was caused by xposed framework and motoxposed
Sent from my A2109A using Tapatalk 4
That's odd I didn't notice it being slow. And what bloatware? Are you referring to the debug utilities?
Sent from my XT926 using Tapatalk 2
dhacker29 said:
That's odd I didn't notice it being slow. And what bloatware? Are you referring to the debug utilities?
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
A reflash worked like a charm, it was the exposed modules which I reinstalled through ROM toolbox that caused me grief, I just removed all those debugging apks and Google magazine,videos games etc
Sent on my Moto X
So this is only working on T-Mobile devices? I'm curious to flash it but I am on sprint.
Sent from my XT1056 using Tapatalk 2
flashallthetime said:
A reflash worked like a charm, it was the exposed modules which I reinstalled through ROM toolbox that caused me grief, I just removed all those debugging apks and Google magazine,videos games etc
Sent on my Moto X
Click to expand...
Click to collapse
Any noticeable differences with regards to RF performance? What about the phone in general?
johnny grep said:
Any noticeable differences with regards to RF performance? What about the phone in general?
Click to expand...
Click to collapse
No noticeable difference although it seems I dont receive LTE signal but it could be the icons from the T-Mobile ROM. I will have to check by doing a speed test at a location where I did receive a LTE signal on the Rogers rom
Edit: LTE is available, got a download speed if over 45mb's
Sent on my Moto X running JB 4.3
Do a back up and test is all I can say can't hurt
Sent from my XT926 using Tapatalk 2
what all apps are safe to remove from this built ? anyone have a list ? battery drain is high specially in standby mode, not sure if it's due to this being a test built or those extra apps, I like it so far, but if I can't better battery life will go back to 4.2.2
dhacker29 said:
Do a back up and test is all I can say can't hurt
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
Yeah I might bite the bullet but my bootloader's still locked. I'm holding out because I want to keep my warranty. BTW I think I read about Rogers pushing an OTA update... Anyone notice anything? My OTA app is disabled so I'm not sure.
Sent from my Moto X
Dhacker,
Sent you a hangout msg but not sure if you got it.
This build does flash cleanly on the VZW Droid MAXX Dev Edition and as such I expect it would be fine on the Moto X Dev Edition
For those planning to do the same, please note the following:
Capacitive keys do not presently function. Just like the Moto X, it will have on-screen keys with the hard keys dormant as if they didn't exist. I am working on how to enable them and would appreciate any assistance anyone can offer. This will not affect anyone on the VZW Moto X Dev Edition as they do not have hard keys .
Upon first boot, the phone will be in GSM/LTE mode. This will allow data but WILL NOT ALLOW PHONE CALLS as they are carried on the CDMA network which is disabled by default (this is a Tmobile ROM so that's to be expected).
***Fix: Dial *#*#4636#*#* - Go into Phone Information - Scroll down and change "Set preferred network type" to LTE/GSM/CDMA auto (PRL). Change nothing else. The phone will disconnect from the network momentarily and switch to emergency only mode for about 20sec. Don't be alarmed, it's just re-registering and attaching itself to the CDMA network. Mine took about 45s-1min to complete the cycle. Subsequent reboots will not require this process unless you wipe your cache.***
build.prop will ID your phone to the world as a TMO Moto X. No real issue here but just be aware of it as it may affect some of your apps.
I am not really sure how to explain what is going on so I made a video to kind of show.
Sorry it is shaky I was holding my camera and trying to use the phone at the same time.
So I did the HTC Unlock Bootloader thing about 2 months ago and I have been stuck with a phone that will not update or anything anymore.
I got fed up with trying to get it to work so I have just been using the phone as is, but it is getting slow and buggy on me so I would like to finish the rooting or get it back to stock or something.
When I boot into recovery as you will see nothing works.
HTC has an update right now on my phone and if I download and go to install the update it reboots into recovery and there is an error saying it could not mount the internal storage or something so update was aborted.
I was hoping someone could watch this video and then point me in the right direction of what to do next.
I tried to get a good shot of the recovery screen so you could see S-ON and the versions n junk.
https://www.youtube.com/watch?v=z2BC1nwo5V4
Thank you guys!
The first problem is CWM does not play nice with the Evo 4G LTE you need to use TWRP.
If you want to take the OTA Update you will need to re-lock your bootloader and install a stock recovery.
bigdaddy619 said:
The first problem is CWM does not play nice with the Evo 4G LTE you need to use TWRP.
If you want to take the OTA Update you will need to re-lock your bootloader and install a stock recovery.
Click to expand...
Click to collapse
^This. You've most likely borked your misc partition with CWM, so you'll need to fix that at some point. As for the rest, you can either do as Bigdaddy says, or install TWRP recovery and flash a ROM.
Sent from my HTC EVO 4G LTE
I downloaded GooManager and attempted to install TWRP. It said it installed but when I rebooted in to recovery it was still using CWM.
Any thoughts on how to force this install? Also when I tried to reboot into recovery using the GooManager app it would not reboot.
I will keep fussing with it and see if I can get TWRP to install.
Oh Bam! I got TWRP working.
Beautiful. I just need to find a ROM to use now..
Psywar28 said:
Oh Bam! I got TWRP working.
Beautiful. I just need to find a ROM to use now..
Click to expand...
Click to collapse
Keep in mind if you're S-on you'll need to install the kernel separately from the ROM. For more info hit the top link in my sig.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Keep in mind if you're S-on you'll need to install the kernel separately from the ROM. For more info hit the top link in my sig.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Thank you! I will attempt to use Moonshine to get S-OFF
I was going to download this ROM would I then just download the S-OFF Version?
I was going to do the S-ON before.
If you're S-on use the S-on version.
Sent from my HTC EVO 4G LTE
FinZ28 said:
If you're S-on use the S-on version.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Moonshine was successful! I am now S-OFF!
Psywar28 said:
Moonshine was successful! I am now S-OFF!
Click to expand...
Click to collapse
Good deal:thumbup:
Sent from my HTC EVO 4G LTE
Ran into an issue.. I was attempting to install CM 11
It has failed on me. Any idea's why?
EDIT: weird note too.. I just went to boot back into the System and TWRP told me I lost Root Permissions.. and it attempted to fix it.. Dunno if it did yet or not.
BAH... Wont reboot back into the System.. Cycles twice and then goes back into TWRP Recovery.
EDIT EDIT: Ok.. So I got some of it fixed.. I ended up getting this Sense 5 ROM installed.. now I am installing this CM 10.2 ROM which seems to be working..
I just can't figure out why CM 11 wont install.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Psywar28 said:
Ran into an issue.. I was attempting to install CM 11
It has failed on me. Any idea's why?
EDIT: weird note too.. I just went to boot back into the System and TWRP told me I lost Root Permissions.. and it attempted to fix it.. Dunno if it did yet or not.
BAH... Wont reboot back into the System.. Cycles twice and then goes back into TWRP Recovery.
EDIT EDIT: Ok.. So I got some of it fixed.. I ended up getting this Sense 5 ROM installed.. now I am installing this CM 10.2 ROM which seems to be working..
I just can't figure out why CM 11 wont install.
Click to expand...
Click to collapse
You probably have the wrong twrp for cm11. You need to use the recovery that is in the first post of the cm11 thread. To install it you'll need to do fastboot flash recovery.
You can get it from the first post here
http://forum.xda-developers.com/showthread.php?t=2518211
Sent from my EVO using XDA Premium 4 mobile app
NaterTots said:
You probably have the wrong twrp for cm11. You need to use the recovery that is in the first post of the cm11 thread. To install it you'll need to do fastboot flash recovery.
You can get it from the first post here
http://forum.xda-developers.com/showthread.php?t=2518211
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I noticed I do have the wrong recovery for it.
I will attempt to install the one for CM 11..
Any idea why this Sense 5 ROM I am using will make phone calls but will not send any SMS's to anyone? Just keeps saying failed...
I kinda dig this Sense 5 ROM.. I have not been able to figure it out.
EDIT:
Got the new TWRP.img file installed.. I had a hard time doing it in Terminal Emulator so I just downloaded a freaking app that installed custom recoveries.
So it successfully installed CM11.. Now I am sitting here waiting for it to boot up.
I have the logo spinning around and around.. I hate these boot animations cuz I can never tell if it is stuck in a boot loop or if it is just working hard.
So I will give it 15/20mins.. Then I am not sure wtf to do other than go back to Sense 5.. Which I installed for a second time and I still could not get SMS to send or receive.
Glad you got it to boot.
If it's spinning it will probably boot up.
Since you did moonshine you should have been able to install the recovery with fast boot.
It's a good practice to have.
Sent from my EVO using XDA Premium 4 mobile app
NaterTots said:
Glad you got it to boot.
If it's spinning it will probably boot up.
Since you did moonshine you should have been able to install the recovery with fast boot.
It's a good practice to have.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah CM 11 finally booted up.
I can make phone calls but I cannot send or receive SMS. Same issue I was having with the Sense 5 ROM.
I have been through all the settings I can find and nothing has worked yet.. Any ideas what might be wrong?
Psywar28 said:
Yeah CM 11 finally booted up.
I can make phone calls but I cannot send or receive SMS. Same issue I was having with the Sense 5 ROM.
I have been through all the settings I can find and nothing has worked yet.. Any ideas what might be wrong?
Click to expand...
Click to collapse
After you did moonshine did you make a call on sense and use the self activate feature in settings?
Sent from my EVO using XDA Premium 4 mobile app
NaterTots said:
After you did moonshine did you make a call on sense and use the self activate feature in settings?
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I did.
When I loaded into the Sense 5 ROM it did not have any of my Profile Information so I could not use the phone with out doing the activation thing.
Psywar28 said:
Yes I did.
When I loaded into the Sense 5 ROM it did not have any of my Profile Information so I could not use the phone with out doing the activation thing.
Click to expand...
Click to collapse
Hmm. I don't know then. I never tried any of the sense 5 ROMs.
Personally at this point I would flash stock rooted, then self activate, update prl and profile, then call sprint and ask them to refresh my connection with them.
Then verify everything works, create a backup of that, and then go back to cm11.
Sent from my EVO using XDA Premium 4 mobile app
NaterTots said:
Hmm. I don't know then. I never tried any of the sense 5 ROMs.
Personally at this point I would flash stock rooted, then self activate, update prl and profile, then call sprint and ask them to refresh my connection with them.
Then verify everything works, create a backup of that, and then go back to cm11.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright sounds like a plan! Not a fun one though haha!!
Thanks for the advise!
Turns out I just needed to update to the latest firmware!
Download videos directly from the Vine app. This module is based on MohammadAG's Vine Downloader.
The Vines are saved in the /Downloads/Vine/ directory.
App download: Xposed thread
App source: GitHub
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the lack of info. This is my first module.
Bootloop of worst kind
The module is causing bootloop of the worst kind. After enabling the module, when I rebooted, it went in a bootloop. Annoying, but not unexpected. I hard reset. Still bootloop. Another hard reset. This time it completes boot and reaches the "optimizing android" screen. But right when it is about to optimize 211th app (of 211 total), it crashes and reboots and bootloops again. And the whole cycle repeats. I have had this crash at 211 twice now. I've deleted the modules.xml from /data/data and trying to reboot as I write this.
bagarwa said:
The module is causing bootloop of the worst kind. After enabling the module, when I rebooted, it went in a bootloop. Annoying, but not unexpected. I hard reset. Still bootloop. Another hard reset. This time it completes boot and reaches the "optimizing android" screen. But right when it is about to optimize 211th app (of 211 total), it crashes and reboots and bootloops again. And the whole cycle repeats. I have had this crash at 211 twice now. I've deleted the modules.xml from /data/data and trying to reboot as I write this.
Click to expand...
Click to collapse
Hmm. May I ask way version of Vine you have installed?
Sent from my Nexus 5 using XDA Free mobile app
Cvballa3g0 said:
Hmm. May I ask way version of Vine you have installed?
Click to expand...
Click to collapse
The latest version from play store. I had that crash 2 more times. Then I flashed the xposed uninstaller zip from twrp and still getting the same crash. Now I'm having to flash the lmy48m system image. Let's see.
EDIT -
I'm royally screwed. How does a phone bootloop even after flashing factory image...!!! These are the things I've done so far -
Hold down the power button to hard reset.
Boot into recovery and delete modules.lst and modules.xml
Boot into recovery and flash xposed uinstaller.
Flash image-hammerhead-lmy48m (after removing -w)
And even now, the boot reaches the "optimizing app 219 of 219" and crashes again..!! Any advice?
bagarwa said:
The latest version from play store. I had that crash 2 more times. Then I flashed the xposed uninstaller zip from twrp and still getting the same crash. Now I'm having to flash the lmy48m system image. Let's see.
EDIT -
I'm royally screwed. How does a phone bootloop even after flashing factory image...!!! These are the things I've done so far -
Hold down the power button to hard reset.
Boot into recovery and delete modules.lst and modules.xml
Boot into recovery and flash xposed uinstaller.
Flash image-hammerhead-lmy48m (after removing -w)
And even now, the boot reaches the "optimizing app 219 of 219" and crashes again..!! Any advice?
Click to expand...
Click to collapse
Have you tried uninstalling my app via TWRP to see if you still get the crashes? The package name is "science.anthonyalves.vinedownloader"
bagarwa said:
The latest version from play store. I had that crash 2 more times. Then I flashed the xposed uninstaller zip from twrp and still getting the same crash. Now I'm having to flash the lmy48m system image. Let's see.
EDIT -
I'm royally screwed. How does a phone bootloop even after flashing factory image...!!! These are the things I've done so far -
Hold down the power button to hard reset.
Boot into recovery and delete modules.lst and modules.xml
Boot into recovery and flash xposed uinstaller.
Flash image-hammerhead-lmy48m (after removing -w)
And even now, the boot reaches the "optimizing app 219 of 219" and crashes again..!! Any advice?
Click to expand...
Click to collapse
Lmao so glad I read this before installing.
Have you tried wiping the system?
>TWRP
>Wipe
>Advanced Wipe
>System check
>Wipe
If you just wipe the system and nothing else (Or just do a factory reset) you should he fine. Just make sure you don't wipe internal storage and that you have a rom saved on your SD
Also, have you updated the xposed module? The latest I believe is 74.
No bootloop issues here. Works as it should, thank you for the module!
AndroidNoob22 said:
No bootloop issues here. Works as it should, thank you for the module!
Click to expand...
Click to collapse
Glad it works!
Sent from my Nexus 5 using XDA Free mobile app
Animescity said:
Lmao so glad I read this before installing.
Have you tried wiping the system?
>TWRP
>Wipe
>Advanced Wipe
>System check
>Wipe
If you just wipe the system and nothing else (Or just do a factory reset) you should he fine. Just make sure you don't wipe internal storage and that you have a rom saved on your SD
Also, have you updated the xposed module? The latest I believe is 74.
Click to expand...
Click to collapse
I did try the "wipe cache" option from twrp. That also didn't work. I finally did a factory reset and now restoring everything painstakingly. What makes it worse is that Marshmallow is gonna be released next week and I'll have to go through this factory reset and restore all over again.
What version of vine should I use? Cjz its not working there
kur1oso said:
What version of vine should I use? Cjz its not working there
Click to expand...
Click to collapse
I have Vine v3.3.08 and Xposed v73.
I'm just dropping by to report that after my last factory reset, this module is now working fine with the latest Vine version.
bagarwa said:
I'm just dropping by to report that after my last factory reset, this module is now working fine with the latest Vine version.
Click to expand...
Click to collapse
YAY!! =D
Works on the latest version 3.3.09 perfectly. Many thanks as I have been using a really old version of vine with Mohammed's module.
nghia0423 said:
Works on the latest version 3.3.09 perfectly. Many thanks as I have been using a really old version of vine with Mohammed's module.
Click to expand...
Click to collapse
No problem! Thanks for the reply.
Sent from my Nexus 5 using XDA Free mobile app
It works great but once iI download one Vine, anytime i go to revine another video, it starts downloading. i then have to restart Vine so ican revine again. Any help on this?? Thanks!
Update
Please update the module for the latest version of the app
iyzerdx said:
Please update the module for the latest version of the app
Click to expand...
Click to collapse
Updated!
Cvballa3g0 said:
Updated!
Click to expand...
Click to collapse
App wont install when dowloading from xposed installer.
Im using CM 12.1 Oneplus One.