Just an FYI =D
Downloading now!
Head over to development!
DroidHam said:
Just an FYI =D
Downloading now!
Head over to development!
Click to expand...
Click to collapse
As I said in that thread, it doesnt currently work. Here are my posts in that thread:
Just installed the official CM9 Nightly
I don't think i did anything wrong...
Fresh Wipe, Install Zip with Gapps..
After boot animation I get force close loop of 2 different things:
Unfortunately, System UI has Stopped
Unfortunately, SetupWizard has Stopped
Anyone with any luck?
If you had the same issue as me, and want to go back to your old rom (in my case Virtuous)
Step 1: Wipe CM9
Step 2: Restore Nandroid of Virtuous (Restores everything BUT Boot img)
Step 3: Flash the latest Virtuous over top of what you just restored. (flashes virtuous kernel/bootimg again)
Profit?
Oh well..
ryun33 said:
Has anyone tried using "Rom Manager" to flash it?
Click to expand...
Click to collapse
Rom Manager will be the same as CWM, except the current RM scripts don't allow for 'reboot into recovery', so it will just reboot back into the OS after you select that option in Rom manager
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
DroidHam said:
Downloading the zip from the link now!
Does this work? Any tips on how to install?
Click to expand...
Click to collapse
It won't work as I and others have said. System UI issue.
But a tip is
Wipe
Install zip
Install GAPPs
Assuming future versions will work.
---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------
ricoroadstar said:
Hey,
Yup, I too had the same UI stop and what not. Tried it twice with unmounting and mounting staging as well as trying to install with and without gapps.
Just went back to Virtuous for now, I just wiped and reflashed the rom so dont know about the boot img deal.
To bad though, was hoping for some stable cm9 with youtube working.
Click to expand...
Click to collapse
The "Boot img deal" is the following:
CM9 flashes its own kernel.
Nandroids Cannot restore kernels currently on the prime.
So if you decide you dont like CM9, restoring a nandroid still has the cm9 kernel, which is why I have said:
Step 1: Wipe CM9
Step 2: Restore Nandroid of Virtuous (Restores everything BUT Boot img)
Step 3: Flash the latest Virtuous over top of what you just restored. (flashes virtuous kernel/bootimg again)
Flashing over top of your restore, restores the correct kernel img
OK, so I successfully S-Off'd this phone using DirtyRacun. I backed up the stock functioning ROM, then went to flash Viperlte 2.2.0. Went through all the Aroma installer options, then went to flash. It breezed through the install process, leaving the phone without any operating system on it (Recovery didn't actually flash anything). Tried both CWM and TWRP, and same results each time.
So, I decided to simply try flashing the boot.img in the downloads for Viperlte 2.2.0 via fastboot, and after doing that, the phone still won't boot, and now whenenver I try to reboot into recovery, recovery flashes for a second, and then screen goes blank and boot loops.
Tried reflashing the stock boot.img and reflashed recoveries, same results each time. I'm at a loss. I don't understand what got messed up by fastboot flashing the boot img.
Any help is greatly appreciated!
Boostjunky said:
OK, so I successfully S-Off'd this phone using DirtyRacun. I backed up the stock functioning ROM, then went to flash Viperlte 2.2.0. Went through all the Aroma installer options, then went to flash. It breezed through the install process, leaving the phone without any operating system on it (Recovery didn't actually flash anything). Tried both CWM and TWRP, and same results each time.
So, I decided to simply try flashing the boot.img in the downloads for Viperlte 2.2.0 via fastboot, and after doing that, the phone still won't boot, and now whenenver I try to reboot into recovery, recovery flashes for a second, and then screen goes blank and boot loops.
Tried reflashing the stock boot.img and reflashed recoveries, same results each time. I'm at a loss. I don't understand what got messed up by fastboot flashing the boot img.
Any help is greatly appreciated!
Click to expand...
Click to collapse
how did you install recovery, the first time you must use adb and flash the recovery.img.
command is: fastboot flash recovery(what ever here).img example: fastboot flash recovery recovery-clockwork-touch-6.0.2.9-fireball.img
Ok, have the phone booting again (flashed ruu, then reflashed the dirtyracun hboot). Question still remains, why did I start bootlooping recovery after flashing the boot.img? And why wouldn't the Rom actually flash in recovery?
Again, any insight is appreciated.
Boostjunky said:
Ok, have the phone booting again (flashed ruu, then reflashed the dirtyracun hboot). Question still remains, why did I start bootlooping recovery after flashing the boot.img? And why wouldn't the Rom actually flash in recovery?
Again, any insight is appreciated.
Click to expand...
Click to collapse
flash the rom then the boot img then boot.
Aldo101t said:
how did you install recovery, the first time you must use adb and flash the recovery.img.
command is: fastboot flash recovery(what ever here).img example: fastboot flash recovery recovery-clockwork-touch-6.0.2.9-fireball.img
Click to expand...
Click to collapse
Yeah, did that. I was in recovery (TWRP) when I tried flashing Viperlte, but it never flashed the Rom after selecting all the options in Aroma. It stated that it did, but there's no way it did. It took less than a second to go from "installing" to "complete".
So, something is funky there.
Boostjunky said:
Yeah, did that. I was in recovery (TWRP) when I tried flashing Viperlte, but it never flashed the Rom after selecting all the options in Aroma. It stated that it did, but there's no way it did. It took less than a second to go from "installing" to "complete".
So, something is funky there.
Click to expand...
Click to collapse
what version of twrp are you using
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
for what it's worth some of the guys had problems, and went back to 2.3.3 and solved the problem, I've never had a problem and i'm running 2.4.4
also you must wipe cache,dalvic, data/factory reset,system
Aldo101t said:
what version of twrp are you using
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
for what it's worth some of the guys had problems, and went back to 2.3.3 and solved the problem, I've never had a problem and i'm running 2.4.4
Click to expand...
Click to collapse
I was on the latest release of TWRP (2.4.4.0). I have a recovery log from when it wouldn't flash the ROM. I'll spare the unnecessary strings, and just post the error itself:
error: file_write: write: I/O error
Installer Error (Status 1)
Edit: Just to add, I just successfully flashed SuperSU on the stock ROM using the same TWRP version (2.4.4.0).
Boostjunky said:
I was on the latest release of TWRP (2.4.4.0). I have a recovery log from when it wouldn't flash the ROM. I'll spare the unnecessary strings, and just post the error itself:
error: file_write: write: I/O error
Installer Error (Status 1)
Edit: Just to add, I just successfully flashed SuperSU on the stock ROM using the same TWRP version (2.4.4.0).
Click to expand...
Click to collapse
well, I don't know for sure i'd try 2.3.3 and see what happens
Aldo101t said:
well, I don't know for sure i'd try 2.3.3 and see what happens
Click to expand...
Click to collapse
I appreciate the suggestions. I'll give a few things a try.
Looks like it was the recovery, afterall. Flashed 2.3.3.0, and the ROM is currently flashing as we speak.
Thanks again!
Boostjunky said:
Looks like it was the recovery, afterall. Flashed 2.3.3.0, and it's currently flashing as we speak.
Thanks again!
Click to expand...
Click to collapse
anytime
Aldo101t said:
what version of twrp are you using
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
for what it's worth some of the guys had problems, and went back to 2.3.3 and solved the problem, I've never had a problem and i'm running 2.4.4
also you must wipe cache,dalvic, data/factory reset,system
Click to expand...
Click to collapse
Hmmm, what's going on here? Aldo101t, do aroma installers work for you on 2.4.4.0? I wonder if its a simple reboot after flashing recovery problem. I need a way to reproduce this.
Sent from my Incredible 4G LTE using Tapatalk 2
mdmower said:
Hmmm, what's going on here? Aldo101t, do aroma installers work for you on 2.4.4.0? I wonder if its a simple reboot after flashing recovery problem. I need a way to reproduce this.
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
I confirm aroma not working on 2.4.4.0 at least on my end.
http://img716.imageshack.us/img716/3192/1362812254888.png
mdmower said:
Hmmm, what's going on here? Aldo101t, do aroma installers work for you on 2.4.4.0? I wonder if its a simple reboot after flashing recovery problem. I need a way to reproduce this.
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
well, i'm not sure. when i tried to flash viper 2.2 i had a problem, but i can't remember what i did now. i used the same recovery, got it installed, i think i restored a stock rom then reflashed viper and it worked, but i'm not sure.
it's been awhile since i've tried to flasn with aroma, so
i just tried flashing viper 2.2, DID NOT WORK, so i miss spoke.sorry
I have also had problems with aroma on several builds of twrp and several builds of cwm. I'm currently on cwm touch and if it fails to install (goes from 7% to done in a few seconds) just try it again till it flashes. Also seems to help me if zips are on the ext SD card. Not sure what's up with this but that's how I got it to work. Seems to be an aroma thing. Regular zips have no problems flashing.
Sent from my Incredible 4G LTE using xda premium
Is there a complete and idiot proof way to make my X into a lollipop S on AT&T without losing 4g and still able to use the tablet docking?
Thanks in advance to the wizards!
If you are rooted and your bootloader is unlocked .
0. If not, Root it using kingroot or towelroot v2(not v4) and use flashily (from the playstore) to flash cwm or twrp to flash crowlock to unlock the boot loader. (careful to tap recovery and not boot)
1.Back up everything through custom recovery. (Latest Twrp or CWM would be fine)
Optional: If you dont want to lose any of your 4g lte connection use this recovery.(This one will be a black screen so leave it alone for 2 mins then wake it up then you are fine)
-- While at that recovery back up System, Boot and the EFS partition and cache(This recovery has the Efs option, and since the efs partition contains the communication info its best to do that so you cannot lose the bands.)
Great now you have just backed up every thing so now I will say for the next set of steps install Cyanogenmod, preferably 12.1 since cm13 is a bit unstable.
2. --For this to work with the conversion I suggest now you will need to install the latest version of twrp. (That could be found under this link)
*Make sure You put cm12.1 some where you can find when you are going to flash it*
3. Using the newest version of twrp available, flash cm12.1 on to your phone (Great Almost done) (your choice if you want gapps or not)
4. When its booting up and everything is set up put the latest WW firmware in a place you will remember when you flash it. (Also put in crowlock too, since flashing this fw will relock your Bootloader)
5. Once thats done Boot into Twrp and select advanced wipe. Under there Choose to wipe System, Data, and Cache.
6. Now its time to flash that WW firmware, which does take some time.
7. After that, flash crowlock again since your bootloader has been locked again. (Reflash Twrp.img too after that, using the img flashing option and make sure you flash the recovery and not boot)
8. Great Now you can boot and everything should be alright
Optional con't: If you are bothered by the lack of LTE connection at times, flash that other version of twrp I gave you earlier (only if you bothered to back it up before flashing the ww firmware.)
Then you can restore the EFS partition from there. (I didn't need to do that since I live near the city and even if I traveled away I still found my self LTE connection)
Then just reboot your phone and thats it
For future updates refresh your recovery to quarx's twrp, but keep the Adam's n5 recovery to future updates when you lose band 17 and connectivity options.
---------- Post added--------- Previous post was at 10-30-2015 ----------
Credit goes to tjsooley for figuring out this process and the other people who were present during the thread at the time.
cm12.1 did'nt work PAD/Dock or you install cm12.1 for flash Padfone S WW ?? PAD/Dock work correctly with ww Padfone s ???
thanks
colla.paolo said:
cm12.1 did'nt work PAD/Dock or you install cm12.1 for flash Padfone S WW ?? PAD/Dock work correctly with ww Padfone s ???
thanks
Click to expand...
Click to collapse
Flash ww firmware after cm12.1 through twrp and the dock should work again.
The Dock isn't supported on cm12.1 yet. (Stay tuned though it could happen in a couple of months)
When I boot into recovery freezes at the Asus screen. Is there a way to flash cwm with out using a comp or going through recovery mode?
---------- Post added at 05:46 AM ---------- Previous post was at 05:41 AM ----------
wattseb said:
When I boot into recovery freezes at the Asus screen. Is there a way to flash cwm with out using a comp or going through recovery mode?
Click to expand...
Click to collapse
Nvm. Posting that seemed to fix the problem lol.
---------- Post added at 05:50 AM ---------- Previous post was at 05:46 AM ----------
Justatechie said:
If you are rooted and your bootloader is unlocked .
Back up everything through custom recovery. (Latest Twrp or CWM would be fine)
If you dont want to lose any of your 4g lte connection use this recovery.(This one will be a black screen so leave it alone for 2 mins then wake it up then you are fine)
--
Then you can restore the EFS partition from there. (I didn't need to do that since I live near the city and even if I traveled away I still found my self LTE connection)
Then just reboot your phone and thats it
Click to expand...
Click to collapse
The link to the lte recovery is dead.
wattseb said:
When I boot into recovery freezes at the Asus screen. Is there a way to flash cwm with out using a comp or going through recovery mode?
---------- Post added at 05:46 AM ---------- Previous post was at 05:41 AM ----------
Nvm. Posting that seemed to fix the problem lol.
---------- Post added at 05:50 AM ---------- Previous post was at 05:46 AM ----------
The link to the lte recovery is dead.
Click to expand...
Click to collapse
The link is updated for the twrp recovery that supports efs backups.
If you dont know how to flash cm12.1 check this out He recommends cwm recovery
Afterwards after you successfully flash and booted cm12.1 up just flash to the newer version of twrp then install ww firmware.
Works like a charm. I still have to go back and restore the efs to get LTE back but its pretty fool proof. I did have to reflash CM12 after wiping the system partition and then flash the WW zip on top. It acted like it couldnt flash the OS to an empty system partition. But its running and rooted. Waiting on them to release MM for the Padphone S now lol.
wattseb said:
Works like a charm. I still have to go back and restore the efs to get LTE back but its pretty fool proof. I did have to reflash CM12 after wiping the system partition and then flash the WW zip on top. It acted like it couldnt flash the OS to an empty system partition. But its running and rooted. Waiting on them to release MM for the Padphone S now lol.
Click to expand...
Click to collapse
Yes thats what it did with me but it ignored it anyway
to be exact it said "are you sure you want to leave recovery with an empty system partition" funny how I flashed it so I left and it booted it up pretty normally,
I always flash cyanogenmod with an empty system partition, too, eh
next time I booted recovery up after booting system (just to root it with supersu) recovery and left it, the message went away.
How Can I unlock bootloader ATT 11.10.8.16? is posible? help me pls
Hi i did a previous thread
http://forum.xda-developers.com/honor-5x/help/os-installed-error-7-t3512747
After that I managed to start Emui and tried to update it
After the update my phone restarted and twrp ran an open recovery script after that when turn on my phone i get honor logo
Im really sorry to start another thread but its not the same problem and i really need help
Calyptos said:
Hi i did a previous thread
http://forum.xda-developers.com/honor-5x/help/os-installed-error-7-t3512747
After that I managed to start Emui and tried to update it
After the update my phone restarted and twrp ran an open recovery script after that when turn on my phone i get honor logo
Im really sorry to start another thread but its not the same problem and i really need help
Click to expand...
Click to collapse
So u installed stock update with twrp right ?
And can u tell me your device model ?
you just followed what isaid right??
you restored a backup that has stock recovery in it..
then how come twrp do anything to you??you sure you didnt uncheck the recovery option while restoring??
---------- Post added at 09:09 AM ---------- Previous post was at 09:06 AM ----------
Calyptos said:
Hi i did a previous thread
http://forum.xda-developers.com/honor-5x/help/os-installed-error-7-t3512747
After that I managed to start Emui and tried to update it
After the update my phone restarted and twrp ran an open recovery script after that when turn on my phone i get honor logo
Im really sorry to start another thread but its not the same problem and i really need help
Click to expand...
Click to collapse
anyway, if you are able access the fastboot, then you got only one way out of this..
just boot into fastboot and flash twrp,
then rebbot recovery and restore again..(make sure the recovery option is selected while restoring menu appears)
and you can boot to emui..
I managed o flash cm thanks forhelping me
Calyptos said:
I managed o flash cm thanks forhelping me
Click to expand...
Click to collapse
good to hear .. GD luck .
Calyptos said:
I managed o flash cm thanks forhelping me
Click to expand...
Click to collapse
finally, you did it!
Hi,
My Redmi note 3 SD doesn't boot up and gets stuck on logo after flashing SuperSU 2.82 zip.I wanted to flash supersu n remove magisk n several mods so I dirty flashed miui 8.5.3.0 ROM then flashed SuperSU zip but after flashing it gets stuck on logo with three dots above android blinking for forever.I have done this before with previous versions of miui it used to work every time but it doesn't work on miui 8.5.3.0
What should I do is there a work around ?
Do I have to do a clean start ?
@bHi71 said:
Hi,
My Redmi note 3 SD doesn't boot up and gets stuck on logo after flashing SuperSU 2.82 zip.I wanted to flash supersu n remove magisk n several mods so I dirty flashed miui 8.5.3.0 ROM then flashed SuperSU zip but after flashing it gets stuck on logo with three dots above android blinking for forever.I have done this before with previous versions of miui it used to work every time but it doesn't work on miui 8.5.3.0
What should I do is there a work around ?
Do I have to do a clean start ?
Click to expand...
Click to collapse
I don't think magisk removal works that way.
flash fastboot rom
Simoom Sadik said:
I don't think magisk removal works that way.
flash fastboot rom
Click to expand...
Click to collapse
Actually my phone boots up if I avoid flashing super su but I want root that's my actual problem
Flash lazy flasher zip on top of that
[email protected] said:
Flash lazy flasher zip on top of that
Click to expand...
Click to collapse
Tried, didn't work
Try with clean flash
Wipe data factory reset
Then flash miui ROM zip
Then SuperSU + lazy flasher
---------- Post added at 11:59 AM ---------- Previous post was at 11:57 AM ----------
@bHi71 said:
Tried, didn't work
Click to expand...
Click to collapse
[email protected] said:
Try with clean flash
Wipe data factory reset
Then flash miui ROM zip
Then SuperSU + lazy flasher
Click to expand...
Click to collapse
(Ur data is currupt )
[email protected] said:
Try with clean flash
Wipe data factory reset
Then flash miui ROM zip
Then SuperSU + lazy flasher
---------- Post added at 11:59 AM ---------- Previous post was at 11:57 AM ----------
(Ur data is currupt )
Click to expand...
Click to collapse
Yeah after booting up a pop up said "there is problem with it your internal" something like that.I guess I have to do a clean flash,btw tnx for replying