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.
Related
Since there have been enormous amounts of questions of how to this, how do I do that. I am laying out the steps, in order, the way I did it. It works perfectly, and was very short. You can do this from ANY version of your phone, even an Alpha/Vanilla version of Froyo, this includes 2.1 Eclair.
THIS VERSION IS NONVOODOO, disable if you are using it.
THIS VERSION IS 100% ODIN FREE.
**I AM NOT RESPONSIBLE FOR WHAT YOU DO TO YOUR PHONE**
DOWNLOAD:
DL30 ROM and Kernel.
http://dl.dropbox.com/u/18199645/DL30.zip
MIRRORS:
http://rom.galaxysense.com/kaos/DL30-leak.zip
Http://youkanged.me/kaos/DL30-leak.zip
http://www.multiupload.com/LES2LLVUIC
http://kaessa.com/files/froyo/DL30-leak.zip
NEW CWM Recovery
http://dl.dropbox.com/u/18199645/new_cwm.zip
MIRRORS:
http://dl.dropbox.com/u/11670464/new_cwm.zip
http://kaessa.com/files/froyo/DL30-cwm.zip
PUT BOTH OF THESE FILES ON YOUR SD CARD. In any folder you like, or just the SD card main folder, as long as you know where it is.
Steps
1) Flash OLD ClockWork Mod Recovery to your phone. Do this by going to the Market and downloading ROM Manager. Once installed, click "Flash ClockWork Recovery" and choose the Fascinate.
1A) This is an ALTERNATIVE to step 1, a VERY good one. If you aren't able to get into Clockwork Recovery then do this. "Rooting Regardless of OS". Do that first and then come back here and proceed with Step 2. ---------------- Thanks ditobot
2) Once finished, choose Reboot Into Recovery. If it doesn't boot into recovery, then "Apply sdcard:update.zip".
3) Next, go back to the main menu and choose "Wipe Data/Factory Reset", do this twice for good measure. Then choose "Wipe Cache Partition", do it twice for good measure, it doesn't hurt anything.
4) Once in Recovery, choose "Install zip from sdcard" > "Choose zip from sdcard" > Then locate your "DL30.zip" file that you downloaded earlier. Choose it and then hit YES. Once complete, takes less than a couple minutes usually.
5) FINALLY, choose "Install zip from sdcard" > "Choose zip from sdcard" > Then locate your "new_cwm.zip" file you downloaded earlier. Choose it and hit YES. YOU ARE DONE!!!!
Reboot the phone and enjoy your rooted, bloated, official copy of Verizon Froyo.
For the record, this update ONLY works with DJ05 and DL09 radio. Meaning you must download and flash it to your phone if you do not have it or you won't get texts and probably won't be able to make calls.
Don't hesitate to ask questions.
Many questions are being asked and I will do my best to answer them, but you may find some of your answers in the Leaked thread started by punk.kaos himself. You can find this here: http://forum.xda-developers.com/showthread.php?t=937237
{
"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"
}
Check out my profile page! There you can find out a little bit of info about me and some other stuff. You may, if you choose,
to my PayPal. I guarantee you I will not use it towards tuition, just BEER, as I am in college and broke. Thanks a lot.
force close?
my tw.launcher keeps force closing, i cant get into the OS either! what did i do wrong?
malvoc said:
my tw.launcher keeps force closing, i cant get into the OS either! what did i do wrong?
Click to expand...
Click to collapse
Did you wipe EVERYTHING? That usually is what causes what you're saying, by not wiping everything.
Syn, what's the difference between the *old* Green CWM and the *new* Green CWM? If you've got the old green cwm, can't you just reboot into recovery, wipe wipe wipe, and then flash the DL30 leak?
I previously had blackhole 3.0 DI09 on it. I jumped when i saw froyo was released so I restored it to a previous ROM (touchwiz rooted and cwm) i put it on my sd card (DI30) went into cwm recovery and did then searched for the the DI30 then applied it. it rebooted then it seemed to be working fine the google account and all the setup menus appeared but when i did it all then closed the menus, Force close tw.launcher came up?
iceman1183 said:
Syn, what's the difference between the *old* Green CWM and the *new* Green CWM? If you've got the old green cwm, can't you just reboot into recovery, wipe wipe wipe, and then flash the DL30 leak?
Click to expand...
Click to collapse
Yes you boot into old CWM then you install NEW CWM from there then wipe and install.
New CWM works with the new kernel .32 as the old one didn't. Blame Verizon. Thank punkkaos and jt.
oh
and then i did like 3 factory resets and it STILL vibrates once then 3 times in succession then force close tw launcher appears.....
Not to be a dink, as I'm still downloading this, but where is this from and is it really ok to post this up? I'm looking forward to this as much as anyone, but not at anyone's expense.
malvoc said:
and then i did like 3 factory resets and it STILL vibrates once then 3 times in succession then force close tw launcher appears.....
Click to expand...
Click to collapse
Wipe data > Wipe cache > Wipe dalvik cache > ReDOWNLOAD both DL30leak.zip or my DL30.zip. Reinstall. You may have a bad copy.
I did this exactly how it says, and now my home and search buttons don't work?
TheBadBen said:
Not to be a dink, as I'm still downloading this, but where is this from and is it really ok to post this up? I'm looking forward to this as much as anyone, but not at anyone's expense.
Click to expand...
Click to collapse
It's ok because punkkaos told everyone that he would release the leaked copy once he knew that it was OK to distribute, so that noone would lose their job. So this is the real deal.
i think i really messed up
to my last 3 posts, i decided to try to fix it myself. i flashed cwm recovery again, and now my phone will load the samsung logo then it will go to the little menu automatically that says
-reboot system now
-apply sdcard:update:zip
wipe data/factory reset
wipe cache partition.....
i dont want this to be a brick! i really screwed up and i'm a major idiot.
skater95 said:
I did this exactly how it says, and now my home and search buttons don't work?
Click to expand...
Click to collapse
Thats strange. What version of Android are you coming from? DI01, DJ05, DL09, alpha Froyo?
I apply the zip via Clockwork and I didn't delete anything. I do not have any FCs plus it prompted me to do a firmware update on my camera
malvoc said:
to my last 3 posts, i decided to try to fix it myself. i flashed cwm recovery again, and now my phone will load the samsung logo then it will go to the little menu automatically that says
-reboot system now
-apply sdcard:update:zip
wipe data/factory reset
wipe cache partition.....
i dont want this to be a brick! i really screwed up and i'm a major idiot.
Click to expand...
Click to collapse
Click "-apply sdcard:update:zip"
ODIN back to DJ05 and start over.
achandler2 said:
I apply the zip via Clockwork and I didn't delete anything. I do not have any FCs plus it prompted me to do a firmware update on my camera
Click to expand...
Click to collapse
Yeah it asks to do a Firmware update. Do it. I did and then it reboots and won't ever ask again. Just a small thing I guess.
Wiping is just a safety thing to do so your chances of stuff getting messed up is really low. It may not be necessary in this package, as you have done it without problems. Good job on finding that out.
larry0071 said:
ODIN back to DJ05 and start over.
Click to expand...
Click to collapse
Basically, if EVERYTHING goes wrong, this is your backup plan.
+1
I had no issues installing from the green cwm. Froyo is installed and I am loving it.
Sent from my SCH-I500 using XDA App
Lodingi said:
I had no issues installing from the green cwm. Froyo is installed and I am loving it.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Glad to hear it. You used my method?
Exactly what the title says. I've tried restoring a back-up, but I can't get the ROM to boot up. It just keeps bringing me back to the CWM screen.
Is there any way I can turn the device off from here just to save the battery while I receive some assistance?
edit: My Prime is now fixed thanks to the excellent support of XDA.
At first, when my prime booted into CWM I was like,
{
"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"
}
Then after it kept bootlooping into CWM things felt worse.
After I got everything fixed up. This is what I felt like. (Only due to the excellent help though!)
Thanks guys!
Yes press and hold power and volume down until it vibrates. Release and it will shut down. Then just restart in recovery and wipe all and reflash rom.
It's still boot-looping back into CWM. It's version v5.8.2.0 if that helps. I'm hitting reboot system now with the power button, holding that and the volume down until I feel the vibration. I release, and a few seconds later it boots up again.
BrianMigs said:
Exactly what the title says. I've tried restoring a back-up, but I can't get the ROM to boot up. It just keeps bringing me back to the CWM screen.
Is there any way I can turn the device off from here just to save the battery while I receive some assistance?
Click to expand...
Click to collapse
Read the following thread it should help but you need some adb knowledge
http://forum.xda-developers.com/showthread.php?t=1514088
When you did a factory reset you erased the rom. You will have to reflash the virtious prime.
You wont need to unbrick. You are still able to get to recovery.
What will happen if my Prime dies though? Will I be able to charge it back up again? I'm not sure I'll have enough time to set up ADB before the battery passes.
fredgar75 said:
When you did a factory reset you erased the rom. You will have to reflash the virtious prime.
You wont need to unbrick. You are still able to get to recovery.
Click to expand...
Click to collapse
I wiped data, cache, in dalvik in CWM. Then I formatted system, and tried re-installing Virtuous. It's still rebooting to CWM.
Well it sounds like you may have to follow the guide then. But it should charge in recovery and while it is off.
But it sounds like you got a corrupted file and I would suggest a new dl.
BrianMigs said:
What will happen if my Prime dies though? Will I be able to charge it back up again? I'm not sure I'll have enough time to set up ADB before the battery passes.
Click to expand...
Click to collapse
See if it will shut down by pressing power button only...I don't recall seeing a shut down option in CWM
recovery...if its there it should work
eg1122 said:
See if it will shut down by pressing power button only...I don't recall seeing a shut down option in CWM
recovery...if its there it should work
Click to expand...
Click to collapse
Unfortunately no "Shut Down" option. It was the first thing I looked for as I think it's included in other recoveries.
Can anybody else confirm that the device will charge while in CWM?
BrianMigs said:
Unfortunately no "Shut Down" option. It was the first thing I looked for as I think it's included in other recoveries.
Can anybody else confirm that the device will charge while in CWM?
Click to expand...
Click to collapse
Sorry It should charge as long as its plugged into the charger and not the pc.
Just booted into recovery and the charging led stays on, but not sure if it is charging.
Nice man I like it.
Hey OP, are you /b/ from forechan?
Sent from my Transformer Prime TF201 using XDA Premium HD app
How did you end up getting it to work? ive recently tried updating my virtuous to the latest but after the install it rebooted and loaded cwm and now thats all it will do.
Sent from my Transformer Prime TF201 using XDA Premium HD app[/QUOTE]
Wasteland_Vixen said:
How did you end up getting it to work? ive recently tried updating my virtuous to the latest but after the install it rebooted and loaded cwm and now thats all it will do.
Sent from my Transformer Prime TF201 using XDA Premium HD app
Click to expand...
Click to collapse
[/QUOTE]
It sounds like you got a common bug with the CWM recovery; that bootloop into recovery. This can be fixed if you have ADP setup. See the how-to thread "Unbricking your Prime"; the first solution should get you back up. Then after that, I'd strongly urge you to consider TWRP. Though CWM is decent, and has got us by for a long time in the Android rooting community, you won't have problems like this with TWRP.
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.
{
"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"
}
(I actually set this up days ago and shared on my G+ but figured why not share here for those who don't follow me)
In short this is simply a early look as to what CM13 will have to offer. You will be experiencing Marshmallow the way Google and the Cyan team has set fit. Please keep in mind that these are still early development so there will be issues.
!!! Flash on your own risk !!!
We can and will not take any responsibility for bricked devices or lost data. So please watch out!
Installation
- Make a (Nandroid) Backup of your current ROM
- Full WIPE (wipe data/factory reset + wipe cache partition + wipe dalvik cache)
- Select ROM from sdcard
- Install ROM (Make sure you use anything from 12/12/15 and up)
- After flashing, reboot device (First reboot will take a while)
- Enjoy CM13 on your device!
BETA 1 [12/12/15]
- First release
Use Builds from 12/12/15 and up
Download
To stay updated on the original post and see what is happening when it happens see my Google Plushttps://plus.google.com/u/0/+IsaiahPEz
sub.
Runs pretty good but I am running into an issue with Titanium backup. I cannot find out why It cannot write to the SD card even with the correct entries in the platform.xml file and the Fix SD app doesn't work anymore like it has since KK through LP (Says the entry is missing in the .xml but, it isn't. So :/ )
EDIT: Nevermind, found out what was wrong with TB on the way it access's storage.
"You need to change the way that the app accesses your SD card. Go into the Titanium Backup preferences (Menu > Preferences) and click 'Backup folder location'. Then click on 'Storage provider' and then 'DocumentProvider storage'. Then just select the root of your SD card. You can then use TB to set your backup location on the SD card."
Did that and Boom. Works fine.
Still a few niggling issues but nothing more than 12.1 had so I am still debating on rolling with this or not for a while.
Been running for a couple of days. Everything has ran pretty smooth so far.
I've been running this super smooth for the last couple of days then about an hour ago with 60% battery it just died. I can't get it to charge or turn on at all. Any ideas on where to go from here?
Edit: After tying everything u could think of a few minutes ago it just turned on like nothing was wrong. No idea what caused it.
Edit: It appears that qksms was causing the crashes. Everything else is running great except for the domestic roaming thing.
Sent from my SM-T530 using Tapatalk
AOSP keyboard fails when first booted.
Can't continue with setup
mesacarvin said:
AOSP keyboard fails when first booted.
Can't continue with setup
Click to expand...
Click to collapse
I'd redownload and try again. Additionally you may want to try another gapps package.
What nightly did you flash?
Additionally which Gapps package did you use?
bmtdan said:
I'd redownload and try again. Additionally you may want to try another gapps package.
What nightly did you flash?
Additionally which Gapps package did you use?
Click to expand...
Click to collapse
Flashed the ROM in the OP and did not flash a Gapps package.
So will re-download and flash a Gapps package (any suggestions?)
mesacarvin said:
Flashed the ROM in the OP and did not flash a Gapps package.
So will re-download and flash a Gapps package (any suggestions?)
Click to expand...
Click to collapse
I'd grab them from here: http://opengapps.org/
Select arm,6.0, stock.
Is anyone else getting "domestic roaming"? I'm not sure if it's a bug out something wrong, other than that the data connection seems solid.
Sent from my LG-ls990 using Tapatalk
PlagaDeRock said:
Is anyone else getting "domestic roaming"? I'm not sure if it's a bug out something wrong, other than that the data connection seems solid.
Sent from my LG-ls990 using Tapatalk
Click to expand...
Click to collapse
I get that when I connect to LTE, on 3g it just says sprint..
kangta05 said:
I get that when I connect to LTE, on 3g it just says sprint..
Click to expand...
Click to collapse
I got the same thing. When I go to check the apn's the system crashes. Could this be the problem?
tenchi_kioto said:
I got the same thing. When I go to check the apn's the system crashes. Could this be the problem?
Click to expand...
Click to collapse
I'm hoping its just a bug. Everything else it butter for me
Yea same issue with mine but everything seemed to work.
Went back to CM12.1 though as a lot of my Cardboard apps appear to not be working correctly with 13 yet and a few crashes to hard black screen. Will give it another go in a month or so.
Seeing Domestic Roaming is normal but it is fine to ignore. Everything should be resolved soon
Nexus11 said:
Seeing Domestic Roaming is normal but it is fine to ignore. Everything should be resolved soon
Click to expand...
Click to collapse
I had this on the other MM rom. Is it just a bug with MM/CM mods? Also it's just UI bug right? It's not actually roaming right?
Sent from my LGLS990 using Tapatalk
JESUSARIUS REX said:
I had this on the other MM rom. Is it just a bug with MM/CM mods? Also it's just UI bug right? It's not actually roaming right?
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
I just checked on sprints website no roaming showing. I've been on a 6.0 Rom for 2 days now.
Nexus11 said:
Seeing Domestic Roaming is normal but it is fine to ignore. Everything should be resolved soon
Click to expand...
Click to collapse
Cool. I kind of figured it was just a bug and that I wasn't actually on roaming. Other than that and a problem I had with another app this is incredibly smooth and stable. The battery life unreal too. I can leave my phone unplugged while I sleep for 8 hours and only lose 3% of my battery.
Sent from my LG-ls990 using Tapatalk
PlagaDeRock said:
Is anyone else getting "domestic roaming"? I'm not sure if it's a bug out something wrong, other than that the data connection seems solid.
Sent from my LG-ls990 using Tapatalk
Click to expand...
Click to collapse
I'm getting that on XenonHD (latest).
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
tenchi_kioto said:
I just checked on sprints website no roaming showing. I've been on a 6.0 Rom for 2 days now.
Click to expand...
Click to collapse
How do you check on sprint's website? DO I have to log in?
tenchi_kioto said:
I just checked on sprints website no roaming showing. I've been on a 6.0 Rom for 2 days now.
Click to expand...
Click to collapse
Thanks. I switched back to a stock based ROM, but I'll definitely give this a go as my daily. I played with it for about 4 hours and loved it.
Sent from my LGLS990 using Tapatalk
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.