Q&A for Pure AOSP 4.4.4 ***international rom***
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Pure AOSP 4.4.4 ***international rom***. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
plsdontpwn.me seems to be down
plsdontpwn.me does not respond. Cloudflare reports host error.
sameersbn said:
plsdontpwn.me does not respond. Cloudflare reports host error.
Click to expand...
Click to collapse
Thanks, looking into it
sameersbn said:
plsdontpwn.me does not respond. Cloudflare reports host error.
Click to expand...
Click to collapse
It's back online now, thanks for pointing it out.
Lloir,
Trying to figure out why my SuperSU won't work properly on this ROM is beyond my skills. Works fine on Omni. Relocked, unlocked bootloader multiple times, flashed the ROM/gapps/supersu (2.16) via CWM, but still get "SU binary not installed and SuperSU can't install it...". Found su in system/xbin where my root checker app said it was, busybox installed v1.22.1 in system/xbin. Maybe su binary permissions are not correct? Anyway, if there is anything else I can do, please let me know when you get a moment. In the meantime, I am loving your AOSP 4.3. Yeah, I know, why go back to JB? Wanted to try your AOSP ROM as a daily driver (and need a camera) so it works perfectly.
I did learn from my past mistake and actually posted in the CORRECT thread.
Lloir,
I asked Chainfire about my SuperSU issues. From the logs I sent, was told the su daemon wasn't starting at boot time. Was told to ask if ROM supported starting install-recovery.sh at boot time? I hope my explanation makes sense. Thank you for your time.
stickt73 said:
Lloir,
I asked Chainfire about my SuperSU issues. From the logs I sent, was told the su daemon wasn't starting at boot time. Was told to ask if ROM supported starting install-recovery.sh at boot time? I hope my explanation makes sense. Thank you for your time.
Click to expand...
Click to collapse
I'm one person...Give me time
I have problem with starting ROM.
After flashing it is stuck on screen where is showing word Android (with animation). Left it like that for one hour and something, still didn't want to boot, restarted it, same thing. CWM is from link from thread.
Steps for flashing I applied:
1.Flashes rom zip from recovery, deleted cache and data before
2. Booted to fastboot and flashed kernel
3. Flashed gapps and rebooted
While waiting rom to start adb on my pc cannot see device.
Can you help me with this?
Sent from my HTC One X+ using XDA Free mobile app
komple said:
I have problem with starting ROM.
After flashing it is stuck on screen where is showing word Android (with animation). Left it like that for one hour and something, still didn't want to boot, restarted it, same thing. CWM is from link from thread.
Steps for flashing I applied:
1.Flashes rom zip from recovery, deleted cache and data before
2. Booted to fastboot and flashed kernel
3. Flashed gapps and rebooted
While waiting rom to start adb on my pc cannot see device.
Can you help me with this?
Sent from my HTC One X+ using XDA Free mobile app
Click to expand...
Click to collapse
you should have deleted system too not just cache and data. This rom 100% boots so it's something you are doing wrong.
komple said:
I have problem with starting ROM.
After flashing it is stuck on screen where is showing word Android (with animation). Left it like that for one hour and something, still didn't want to boot, restarted it, same thing. CWM is from link from thread.
Steps for flashing I applied:
1.Flashes rom zip from recovery, deleted cache and data before
2. Booted to fastboot and flashed kernel
3. Flashed gapps and rebooted
While waiting rom to start adb on my pc cannot see device.
Can you help me with this?
Sent from my HTC One X+ using XDA Free mobile app
Click to expand...
Click to collapse
Also, make sure you are flashing the Elite Kernel from nik3r and NOT the boot.img from the ROM zip. Like Lloir said, there's no reason for the ROM not to boot unless you've done something wrong.
Lloir said:
you should have deleted system too not just cache and data. This rom 100% boots so it's something you are doing wrong.
Click to expand...
Click to collapse
I was wrong sorry guys, wrong kernel.
Sorry for asking this, when can we expect camera or version 5.0?
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
stickt73 said:
Also, make sure you are flashing the Elite Kernel from nik3r and NOT the boot.img from the ROM zip. Like Lloir said, there's no reason for the ROM not to boot unless you've done something wrong.
Click to expand...
Click to collapse
I had wrong kernel, after posting this I realized that , off course
stickt73 said:
Lloir,
Trying to figure out why my SuperSU won't work properly on this ROM is beyond my skills. Works fine on Omni. Relocked, unlocked bootloader multiple times, flashed the ROM/gapps/supersu (2.16) via CWM, but still get "SU binary not installed and SuperSU can't install it...". Found su in system/xbin where my root checker app said it was, busybox installed v1.22.1 in system/xbin. Maybe su binary permissions are not correct? Anyway, if there is anything else I can do, please let me know when you get a moment. In the meantime, I am loving your AOSP 4.3. Yeah, I know, why go back to JB? Wanted to try your AOSP ROM as a daily driver (and need a camera) so it works perfectly.
I did learn from my past mistake and actually posted in the CORRECT thread.
Click to expand...
Click to collapse
Lloir,
After what seemed like forever, I found a solution to my problem of not having root access. Found this in another forum, but it solved the same problem I had:
Run in adb shell:
mount -o remount,rw /system
echo persist.sys.root_access=1 >> /system/build.prop
reboot
It's amazing what can happen when the search button is used.
Download links do not work
shalane said:
Download links do not work
Click to expand...
Click to collapse
It's being worked on, huge issue when the server got moved.
Lloir when will you upload bug free aosp 4.4.4 Rom for one x plus
Thanks in advance
pranavrocksharma said:
Lloir when will you upload bug free aosp 4.4.4 Rom for one x plus
Thanks in advance
Click to expand...
Click to collapse
Never :good:
Lloir said:
Never :good:
Click to expand...
Click to collapse
Sorry for posting the same post here and there.
Please don't change your decision.
Please
Related
I have been trying since yesterday evening to install the CM9 nightly build. I've read through every single post in the thread ( http://forum.xda-developers.com/showthread.php?t=1778170 ) and I still can't seem to do it. I've flashed a few ROMs in the past with no issues, but for some reason this one is not making any sense. Maybe it's a good thing because I've learned so much and had my heart drop a few times thinking my phone is ruined. My issue seems to be with my version of CWM I guess? The first step of the instructions says to: 1. Install ClockworkMod Recovery for "quincyatt".
I don't understand this. I click on the link in the thread and the CWM file is a .img file, so I don't understand how to flash it to my phone. I've downloaded ROM manager (and paid for the premium version) and flashed the newest version through there. When I do that, it completely messes up CWM and keeps giving me errors anytime I try to install any ROM. It freezes on most things I do, keeps giving cache errors, etc. It seems like there's an issue with flashing the newest version through ROM manager. So how do I get CM9 on my phone? Do I need to update CWM someway? I currently have the version in the CWM thread ( http://forum.xda-developers.com/showthread.php?t=1584576 ) with the latest release 04-14. If someone can please give me an explanation for what I'm missing here, that would help greatly. I've been on this forum for a few years and always read and search. I actually just made my first post yesterday to help someone when I was encountering the same issue with CWM that they were and finally figured it out after hours of reading.
THANK YOU!
jaxjonesdrew32 said:
I have been trying since yesterday evening to install the CM9 nightly build. I've read through every single post in the thread ( http://forum.xda-developers.com/showthread.php?t=1778170 ) and I still can't seem to do it. I've flashed a few ROMs in the past with no issues, but for some reason this one is not making any sense. Maybe it's a good thing because I've learned so much and had my heart drop a few times thinking my phone is ruined. My issue seems to be with my version of CWM I guess? The first step of the instructions says to: 1. Install ClockworkMod Recovery for "quincyatt".
I don't understand this. I click on the link in the thread and the CWM file is a .img file, so I don't understand how to flash it to my phone. I've downloaded ROM manager (and paid for the premium version) and flashed the newest version through there. When I do that, it completely messes up CWM and keeps giving me errors anytime I try to install any ROM. It freezes on most things I do, keeps giving cache errors, etc. It seems like there's an issue with flashing the newest version through ROM manager. So how do I get CM9 on my phone? Do I need to update CWM someway? I currently have the version in the CWM thread ( http://forum.xda-developers.com/showthread.php?t=1584576 ) with the latest release 04-14. If someone can please give me an explanation for what I'm missing here, that would help greatly. I've been on this forum for a few years and always read and search. I actually just made my first post yesterday to help someone when I was encountering the same issue with CWM that they were and finally figured it out after hours of reading.
THANK YOU!
Click to expand...
Click to collapse
Try using TWRP recovery. I believe it flashes successfully.
http://forum.xda-developers.com/showthread.php?t=1647575
It is a zip not a. Img i just clicked it myself. Dont use the stock browser. Download dolphon browser hd. And click the link. The zip file you download is there. Flash it in cwm recovery. Easy easy stuff.
Download rom manager from the market. From within the app you can install CWM. This is what the post means.
Oops, sorry didn't read your whole post at first.
I had the same problem. What I did to fix it was purchase the touch recovery upgrade from within rom manager and that fixed my problems. If you have $2 to spare give it a shot. Good luck!
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks for the replies. I finally got it to work with TWRP. Now of course when it loads up everywhere I click I get an error saying 'Unfortunately, the process android.process.acore has stopped. :laugh: Here we go again.
Do what i said in my post above. Make sure to wipe data cache and dalvik cache in CWM recovery. Or dont listen and continue to enjoy the issues. Also dont use rom manager. Its more problems then its worth. Good luck
Thank you, I appreciate your help. Well I figured out how to get that error to stop. Now just need to figure out how to get all my contacts on here that were only saved on my SIM and I'll be good to go. This was a really good learning experience. I'm really liking TWRP
Do yourself a favor and put all contacts on your Gmail account. You can enter them on a PC quickly. Just be sure to always select your Gmail account to sync.
Another option is to use Titanium Back Up and restore the contacts once moving to a new ROM.
Sent from my SAMSUNG-SGH-I717 using xda premium
Big Dawg 23 said:
Do yourself a favor and put all contacts on your Gmail account. You can enter them on a PC quickly. Just be sure to always select your Gmail account to sync.
Another option is to use Titanium Back Up and restore the contacts once moving to a new ROM.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Thanks, I synced them all to Gmail. Much faster now! Finally got it all up and running. Just a question about using the 'touch key notification lights' Does this kill the battery? It seems like it stays on until you read your text, so if you get one while asleep those lights just stay on?
Use bln app from market and uncheck in system settings. You can set that to turn off whenever you'd like
froidroid said:
Use bln app from market and uncheck in system settings. You can set that to turn off whenever you'd like
Click to expand...
Click to collapse
awesome app!! bought the paid version. thanks man!
silver03wrx said:
It is a zip not a. Img i just clicked it myself.
Click to expand...
Click to collapse
Some of the links are .zip files and some are .img files.
Hey people.
I rooted my ANDROID HTC ONE from T mobile, using a guide I found on here and the all in one toolkit.
I am using TWRP newest 2.5.0.0, I can access the bootloader and recovery, and have been sat here now looking for answers for about 5 hours.
It freezes on the HTC quietly brilliant screen.
Also says that there is no OS installed.
I am looking for help via TEAMVIEWER, or someway to get my phone working.
If you need more information please let me now ASAP so I can give it you.
UPDATE: Okay people I successfully installed the XenonHD ROM and it is now stuck in bootloop i have tried clearing the cache and it doesn't do anything, this is the only ROM that is currently working.
I have searched the net searched the post and still nothing.
I am almost got my phone back guys and am willing to DONATE or repay the favour via modding something through XBOX or whatever I can.
Please contact me soon as possible.
I am still on TEAMVIEWER.
Changed my recovery to ClockWorkMod Touch.
Still need help?
Sent from my HTC One using Tapatalk 4 Beta
osmosizzz said:
Still need help?
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah mate, really bad.
Can you offer any help please.
ScouseCarl said:
Hey people.
I rooted my ANDROID HTC ONE from T mobile, using a guide I found on here and the all in one toolkit.
I am using TWRP newest 2.5.0.0, I can access the bootloader and recovery, and have been sat here now looking for answers for about 5 hours.
It freezes on the HTC quietly brilliant screen.
Also says that there is no OS installed.
I am looking for help via TEAMVIEWER, or someway to get my phone working.
If you need more information please let me now ASAP so I can give it you.
Click to expand...
Click to collapse
There have been a lot of posts on similar issues. You can "sideload" a ROM via ADB commands from your computer. If you can get into recovery, your phone can be fixed. I haven't done this myself (still stock), but do a search on google or xda on sideloading a ROM from ADB.
stevedebi said:
There have been a lot of posts on similar issues. You can "sideload" a ROM via ADB commands from your computer. If you can get into recovery, your phone can be fixed. I haven't done this myself (still stock), but do a search on google or xda on sideloading a ROM from ADB.
Click to expand...
Click to collapse
Already tried sideloading, said it was complete successfully on the phone and on the computer, never worked still says no OS installed.
ScouseCarl said:
Already tried sideloading, said it was complete successfully on the phone and on the computer, never worked still says no OS installed.
Click to expand...
Click to collapse
Did you clear the cache? Also, I've seen some people have to format the partitions.
EDIT: But formatting does not seem to be needed if you sideloaded successfully.
stevedebi said:
Did you clear the cache? Also, I've seen some people have to format the partitions.
EDIT: But formatting does not seem to be needed if you sideloaded successfully.
Click to expand...
Click to collapse
Tried all that, Any chance you could try helping VIA teamviewer, you now more about it than me I think i could of done it in wrong order or use a bad ROM or KERNAL..
Teamviewer Info:
ID: 928 366 143
PASS: 8119
Im on now just looking for anyone to help. I will have a notepad up so when you access my laptop just let me now your from here.
ScouseCarl said:
Tried all that, Any chance you could try helping VIA teamviewer, you now more about it than me I think i could of done it in wrong order or use a bad ROM or KERNAL..
Teamviewer Info:
ID: 928 366 143
PASS: 8119
Im on now just looking for anyone to help. I will have a notepad up so when you access my laptop just let me now your from here.
Click to expand...
Click to collapse
Sorry, I've not even rooted my phone, and I would not want to use your device as a learning tool. Let me look around and see if I can find a nandroid backup.
EDIT: Nope, I don't see one. Try opening a thread requesting a nandroid back for your recovery.
stevedebi said:
Sorry, I've not even rooted my phone, and I would not want to use your device as a learning tool. Let me look around and see if I can find a nandroid backup.
EDIT: Nope, I don't see one. Try opening a thread requesting a nandroid back for your recovery.
Click to expand...
Click to collapse
Ok thanks.
Still looking for help guys. Really need my phone up and running, I got a job to run.
UPDATE: Installed XENONHD ROM and it has got passed the HTC Quietly Brilliant screen and moved onto their load up screen.
BUT, then resets backs to the HTC load up screen then back to there's.
Any more help is appreciated and am willing to donate to them for getting my phone back online.
ScouseCarl said:
UPDATE: Installed XENONHD ROM and it has got passed the HTC Quietly Brilliant screen and moved onto their load up screen.
BUT, then resets backs to the HTC load up screen then back to there's.
Any more help is appreciated and am willing to donate to them for getting my phone back online.
Click to expand...
Click to collapse
I think i will be able to help you, am at work atm but when i get home around 6:30 pm est i will teamviewer with you to try to get you back on track.
ScouseCarl said:
UPDATE: Installed XENONHD ROM and it has got passed the HTC Quietly Brilliant screen and moved onto their load up screen.
BUT, then resets backs to the HTC load up screen then back to there's.
Any more help is appreciated and am willing to donate to them for getting my phone back online.
Click to expand...
Click to collapse
You have to be careful with No o.s installed .
Normally if u reboot when u see that you'll brick.
Without a o.s you have no bootloader..
I bricked my s3 and had to jtag it when it said no o.s I rebooted and black blank screen nothing.
I've had this happen also when choosing format system and format data /media some reason it botches the boot up .
My only fix was to sideload a rom or wipe factory and restore a nandroid .
Sent from my M7 using xda premium
iamfightaa said:
I think i will be able to help you, am at work atm but when i get home around 6:30 pm est i will teamviewer with you to try to get you back on track.
Click to expand...
Click to collapse
Thankyou.
How long is that about as I am in UK.
lojak29 said:
You have to be careful with No o.s installed .
Normally if u reboot when u see that you'll brick.
Without a o.s you have no bootloader..
I bricked my s3 and had to jtag it when it said no o.s I rebooted and black blank screen nothing.
I've had this happen also when choosing format system and format data /media some reason it botches the boot up .
My only fix was to sideload a rom or wipe factory and restore a nandroid .
Sent from my M7 using xda premium
Click to expand...
Click to collapse
No i got a ROM working, the XenonHD.
I am basically I think stuck in a bootloop, I am currently sideloading the ROM again wiped the data and that.
So going to check again inabit.
After all that did you try erasing cache one more time? Maybe through recovery or fastboot?
Sent from my HTC One using xda app-developers app
iamfightaa said:
I think i will be able to help you, am at work atm but when i get home around 6:30 pm est i will teamviewer with you to try to get you back on track.
Click to expand...
Click to collapse
Thanks for helping him. I just didn't feel comfortable working on this when I have not done it on my own phone first.
Okay guys i will add a thanks to all your posts.
My phone is now working I got it to stop bootlooping but just need a little help to check if my phone is rooted and what not.
So how can i check since I have nothing on my phone including the playstore or anything.
ScouseCarl said:
Thankyou.
How long is that about as I am in UK.
Click to expand...
Click to collapse
in about 2 - 3 hours from now.
---------- Post added at 04:12 PM ---------- Previous post was at 04:08 PM ----------
ScouseCarl said:
Okay guys i will add a thanks to all your posts.
My phone is now working I got it to stop bootlooping but just need a little help to check if my phone is rooted and what not.
So how can i check since I have nothing on my phone including the playstore or anything.
Click to expand...
Click to collapse
my recomendation is that you get s -off and supercid asap so next time you run into a similar problem you can just install any ruu(note only do this if your phone has no official ruu) and work it out from there.
ScouseCarl said:
Okay guys i will add a thanks to all your posts.
My phone is now working I got it to stop bootlooping but just need a little help to check if my phone is rooted and what not.
So how can i check since I have nothing on my phone including the playstore or anything.
Click to expand...
Click to collapse
What ROM did you flash? It should say if it was rooted (most are).
ScouseCarl said:
Thankyou.
How long is that about as I am in UK.
No i got a ROM working, the XenonHD.
I am basically I think stuck in a bootloop, I am currently sideloading the ROM again wiped the data and that.
So going to check again inabit.
Click to expand...
Click to collapse
What you need to do is this exactly .
Dload a rom on pc reboot recovery on phone first .IMORTANT FIRST FORMAT SYSTEM.
Then when that's done choose factory reset.
Rename the rom to Rom.zip or anything you want but make sure it says.zip
Sometimes sideload won't work if roms not renamed , that's mentioned in another thread about sideloading.
Then sideload the rom
Let it load and install .
When it reboots itl take a while .
I just did this to my HTC one the other day after I got stuck after formating data media .
Sent from my M7 using xda premium
lojak29 said:
What you need to do is this exactly .
Dload a rom on pc reboot recovery on phone first .IMORTANT FIRST FORMAT SYSTEM.
Then when that's done choose factory reset.
Rename the rom to Rom.zip or anything you want but make sure it says.zip
Sometimes sideload won't work if roms not renamed , that's mentioned in another thread about sideloading.
Then sideload the rom
Let it load and install .
When it reboots itl take a while .
I just did this to my HTC one the other day after I got stuck after formating data media .
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Yeah my phone is currently working now, but I have no play store nor do I now if my phone is rooted.
I have a custom ROM on it XenonHD. http://forum.xda-developers.com/showthread.php?t=2290785
That one.
Just currently trying to get to grips on how to work it and that.
I can't download the playstore because it says it is currently installed but it is nowhere to be seen.
Q&A for Root
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Root. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Nexus 9 root
I'm a newbie so can't post in Chainfire's root thread; but thought I'd post an issue with rooting my N9 in case it helps anyone.
When trying to boot inject.img, it returned "FAILED (data transfer failure (Unkown error))". Tried multiple times, rebooted, etc. Confirmed connection by fastboot devices command.
Not sure exactly what caused it to work, but I rebooted my PC, tried it, it failed, so I unplugged USB connector, plugged it back in to a different port on PC, and SUCCESS! (Maybe just bad USB connection??)
Hopefully this helps someone out there.
Cheers,
Is autoroot working in 25L, the New update?
thebrainkafka said:
Is autoroot working in 25L, the New update?
Click to expand...
Click to collapse
The new update is Q. Some have gotten auto root to work, others have not. You can do the manual root method and flash the elemental x kernel. That was updated with the latest commits.
Sent from my Nexus 9 using Tapatalk
Flash LRX21Q manually. You will need to unzip the package and fastboot flash all img files manually (see this thread: http://forum.xda-developers.com/nexus-9/help/factory-image-flash-t2929019). After that Auto CF will work.
Sent from my Nexus 9 using XDA Free mobile app
I have learnt so many things from your artic,thank you.
---------------------------------------------------------------------------------
I don't know how you guys got it working. I'm on the latest factory image. I ran CF auto root just fine, but then I rebooted and went to flash the SuperSu update to 2.25 via TWRP, and apps just freeze when I try to grant them root now. SuperSu itself will open and I can configure it, but it never comes up when I should be getting an access prompt from using an app requesting root. The app and SuperSu just seem to freeze.
I'm on the latest TWRP as well. I had some issues and went into fastboot and rewrote the system image from the factory image and my device booted again, but updating SuperSu via TWRP says it works but I still get freezing on every app I attempt to grant root. So basically I cannot use root at all.
Moved the above here from Chainfire's root thread. I don't have a clue what's causing the freezing.
EDIT: It gets odder. It's as if the prompts are the problem. I changed SuperSu to grant by default and an app worked. But if I set it to prompt, nothing comes up. Logs only appear when I set it to allow by default.
MikeRL100 said:
I don't know how you guys got it working. I'm on the latest factory image. I ran CF auto root just fine, but then I rebooted and went to flash the SuperSu update to 2.25 via TWRP, and apps just freeze when I try to grant them root now. SuperSu itself will open and I can configure it, but it never comes up when I should be getting an access prompt from using an app requesting root. The app and SuperSu just seem to freeze.
I'm on the latest TWRP as well. I had some issues and went into fastboot and rewrote the system image from the factory image and my device booted again, but updating SuperSu via TWRP says it works but I still get freezing on every app I attempt to grant root. So basically I cannot use root at all.
Moved the above here from Chainfire's root thread. I don't have a clue what's causing the freezing.
EDIT: It gets odder. It's as if the prompts are the problem. I changed SuperSu to grant by default and an app worked. But if I set it to prompt, nothing comes up. Logs only appear when I set it to allow by default.
Click to expand...
Click to collapse
I lost root somehow. Probably kernel. I just reflashed stock recovery and R boot image, ran CFAR again, flashed TWRP and then 2.25. All good now.
Maybe I need to do a complete wipe. Or perhaps I could wait - if anybody knows what I should do. I would log it, but how do I get logs without root? Chainfire may be interested.
MikeRL100 said:
Maybe I need to do a complete wipe. Or perhaps I could wait - if anybody knows what I should do. I would log it, but how do I get logs without root? Chainfire may be interested.
Click to expand...
Click to collapse
I just wiped recovery, boot and reflashed those stock images. Ran CFAR. Flashed TWRP. Flashed 2.25 in TWRP. All good now.
prdog1 said:
I lost root somehow. Probably kernel. I just reflashed stock recovery and R boot image, ran CFAR again, flashed TWRP and then 2.25. All good now.
Click to expand...
Click to collapse
There's a few lines in init.rc that need to be changed to get root working if flashing a factory google boot.img. Kernel itself doesn't just the kernel zimage won't break root, but flashing a boot.IMG will unless you make a small edit to the ramdisk.
For those having problems after flashing 2.25 go into SU settings aand uncheck and recheck the Enable SU checkbox. Worked for me. Working as should now.
Yes I mentioned that in a thread earlier. Must have not been the only one with the problem.
Latest beta 2.27
I'd wait before rooting, seems Chainfire may be able to root without the kernel patches soon: https://plus.google.com/u/0/+Chainfire/posts/K7n4e1q5SMD
Diesel779 said:
I'd wait before rooting, seems Chainfire may be able to root without the kernel patches soon: https://plus.google.com/u/0/+Chainfire/posts/K7n4e1q5SMD
Click to expand...
Click to collapse
Seems to be working. Reports are good.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
prdog1 said:
Seems to be working. Reports are good.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Things are moving along quickly I'm going to hold off from rooting for a few days maybe longer. Give Flar2 time to do some more work on his kernel too.
SU 2.27
I was on R unlocked and rooted w/CFAR using su 2.25 and TWRP 2.8.2.1. Here is what i did - uninstalled/deleted SU, fastboot erased recovery and boot, fastboot flashed stock R boot and recovery. Rebooted all was ok NO ROOT. Then -> fastboot erase recovery -> fastboot flash TWRP -> flashed SU 2.27 w/TWRP -> wipe dalvik/cache -> reboot -> BAAAM ROOT. Thank you Chainfilre!!!!!!
After root dont get updates
After root my tablet nexus 9, I don't get updates. The device detect that there is a update, download it, try to install and then say error!!!
I have did the CF-auto root flasheable. Do you have any solution for that???
Algruista said:
After root my tablet nexus 9, I don't get updates. The device detect that there is a update, download it, try to install and then say error!!!
I have did the CF-auto root flasheable. Do you have any solution for that???
Click to expand...
Click to collapse
Read this forum http://forum.xda-developers.com/nexus-9/orig-development/root-t2929118
or try this one http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
Q&A for [RECOVERY][volantis] TWRP 2.8.2.1 touch recovery [2014-11-18]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][volantis] TWRP 2.8.2.1 touch recovery [2014-11-18]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Skid71 said:
...The .img file is in the same folder I start the command line from. The output reads just like the picture in your guide
At this point I'm wondering if the recovery_fixed.img is supposed to look like stock/aosp and not like TWRP...
Click to expand...
Click to collapse
The same happend to me yesterday. I don't know why. And not, the TWRP recovery looks like 'TWRP recovery'.
Finally, i chose the new CF-Auto-Root's ChainFire, because i only wanted to become root.
But i haven't TWRP recovery
Hi all, when I reboot into twrp recovery it takes a long time before its booted in recovery. Any ideas why?
hill67 said:
Hi all, when I reboot into twrp recovery it takes a long time before its booted in recovery. Any ideas why?
Click to expand...
Click to collapse
Maybe it's decrypting the data partition upon starting recovery...
guyd said:
Maybe it's decrypting the data partition upon starting recovery...
Click to expand...
Click to collapse
So decrypting the n9 would help getting faster in recovery?
hill67 said:
So decrypting the n9 would help getting faster in recovery?
Click to expand...
Click to collapse
Perhaps, but only the dev can really answer that with certainty.
hill67 said:
So decrypting the n9 would help getting faster in recovery?
Click to expand...
Click to collapse
Decrypting the N9 would do R/W operations a little bit faster (N9's Procesor is enought fast for this, although maybe something isn't optimized completly). I don't think your problem is because N9 is Encrypted.
But with you guys it boots at a normal speed into recovery?
hill67 said:
But with you guys it boots at a normal speed into recovery?
Click to expand...
Click to collapse
No, it takes a fair amount of time. Longer than my n5. I think what you're seeing is normal for the n9
Sent from my Nexus 9 using XDA Free mobile app
recovery with dead android and red triangle
So I think I may have done things out of order. I first logged into android and enable developer options and checked enable oem unlock. Rebooted into fastboot and ran the oem unlock. Without rebooting, I ran the fastboot command to rewrite twrp ( i think was the mistake ). I rebooted and now I have no recovery. I then reflashed the 5.0.1 factory image. https://developers.google.com/android/nexus/images . Still no default recovery or twrp. Any ideas on what I need to do.
zoidberg_md said:
So I think I may have done things out of order. I first logged into android and enable developer options and checked enable oem unlock. Rebooted into fastboot and ran the oem unlock. Without rebooting, I ran the fastboot command to rewrite twrp ( i think was the mistake ). I rebooted and now I have no recovery. I then reflashed the 5.0.1 factory image. https://developers.google.com/android/nexus/images . Still no default recovery or twrp. Any ideas on what I need to do.
Click to expand...
Click to collapse
Flash twrp again in fastboot. Then flash supersu 2.37 in twrp.
Sent from my Nexus 9 using XDA Free mobile app
Any news on twrp for the LTE model?
Vendor partition can't be unmounted
TWRP 2.8.5.0 can't unmount the /vendor partition, and also can't restore it from a nandroid backup. Maybe it's due to the changed vendor location in Lollipop. Can you please update TWRP to deal with this properly? Plz!!!!
Well i used to have a hox+ with Android Revolution custom rom and a custom kernel. I tried to power it up but it stucks at htc logo,then reboots and goes straight to twrp recovery. I tried to flash again the rom via adb but i can't see my device in cmd. I found and dowloaed htc drivers my htc,plus adk and htc sync manager but still no luck..any ideas what is going on here?
do a full system reset in cwm recovery
now install the rom
reboot into fastboot
fastboot flash boot boot.img for the rom
i360droid said:
do a full system reset in cwm recovery
now install the rom
reboot into fastboot
fastboot flash boot boot.img for the rom
Click to expand...
Click to collapse
fastboot is not recognised etc...........any ideas?
smavr said:
fastboot is not recognised etc...........any ideas?
Click to expand...
Click to collapse
ok, add me on skype, i360faceplant, i will walk you through it step by step
i360droid said:
ok, add me on skype, i360faceplant, i will walk you through it step by step
Click to expand...
Click to collapse
Well i actually found what happened..my old hox+ works perfectly now..thanks for your help anyway
smavr said:
Well i actually found what happened..my old hox+ works perfectly now..thanks for your help anyway
Click to expand...
Click to collapse
what was up with it?
i360droid said:
what was up with it?
Click to expand...
Click to collapse
Well, i just made a mistake at adb sideload...
smavr said:
Well, i just made a mistake at adb sideload...
Click to expand...
Click to collapse
lol
i360droid said:
lol
Click to expand...
Click to collapse
Somewhat similar situation. I previously rooted my HTC One X+ (Intl) with Viper X+ rom. I thought I would experiment with it as it is no longer my daily phone, and since I liked the Cyanogen experience on OnePlus One, thought i would try to install it on the HOX+.
I followed these official (?) instructions http://wiki.cyanogenmod.org/w/Install_CM_for_enrc2b#Installing_recovery_using_fastboot, however, after getting CWM recovery on and then flashing via sideload command the ROM, I am now stuck in the CM bootloop animation and computer no longer recognises the device, and can't find anyway to get back to bootloader, recovery etc.
I did read about bootloop issues after this and some people said that the boot.imhg file should have been flashed separately (thanks CM for not including that instruction!), and somehow my computer recognised it one more time after the bootlooping started and I managed to get into fastboot to flash boot.img, but, then rebooted and bootloop again. Since then I have had no way to get back into recovery or bootloader, so it just runs until battery dies.
Should it go into the bin? Or anything else I should try?
Thanks so much for any
EDIT: Solved...I was able to get recovery back, then did full reset and followed instructions above re boot.img flash and now am back into my phone with a new lease on life and CM ROM!!
Two more noob questions if I may, now that I have my HOX+ back...
I am now running CM 10.2.1-enrc2b.
I have 3 updates available and being offered to me (upgrade to CM11 from CM10):
- cm-11-20140308-SNAPSHOT-M4
- cm-11-20140916-SNAPSHOT-M10
- cm-11-20140916-SNAPSHOT-M12
1. I downloaded and installed the latest M12, but upon rebooting it went into a bootloop for 15mins+. I then followed your instructions again to get back. So, it seems I at least need to install them in order starting from the earliest (ie M4), but before doing so I wanted to check if anyone knows if these are even compatible with my HOX+ (Intl)?
2. Which would be the best place to get the right gapps package and installation instructions (if CM can get it wrong, am now wary of someone else leaving out the critical boot.img flash step eg)?
Thanks!
Sent from my Nexus 7 using XDA Free mobile app
EDIT: Nothing like some self-help. I am good now.
ahighfield said:
Somewhat similar situation. I previously rooted my HTC One X+ (Intl) with Viper X+ rom. I thought I would experiment with it as it is no longer my daily phone, and since I liked the Cyanogen experience on OnePlus One, thought i would try to install it on the HOX+.
I followed these official (?) instructions http://wiki.cyanogenmod.org/w/Install_CM_for_enrc2b#Installing_recovery_using_fastboot, however, after getting CWM recovery on and then flashing via sideload command the ROM, I am now stuck in the CM bootloop animation and computer no longer recognises the device, and can't find anyway to get back to bootloader, recovery etc.
I did read about bootloop issues after this and some people said that the boot.imhg file should have been flashed separately (thanks CM for not including that instruction!), and somehow my computer recognised it one more time after the bootlooping started and I managed to get into fastboot to flash boot.img, but, then rebooted and bootloop again. Since then I have had no way to get back into recovery or bootloader, so it just runs until battery dies.
Should it go into the bin? Or anything else I should try?
Thanks so much for any
EDIT: Solved...I was able to get recovery back, then did full reset and followed instructions above re boot.img flash and now am back into my phone with a new lease on life and CM ROM!!
Click to expand...
Click to collapse
to get into bootloader, hold down the vol down and power, the home lights will flash (atleast they do when its booting), it will reboot, when you get the htc logo, let go of power button. and now try a stable er version of the rom.
---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------
ahighfield said:
Two more noob questions if I may, now that I have my HOX+ back...
I am now running CM 10.2.1-enrc2b.
I have 3 updates available and being offered to me (upgrade to CM11 from CM10):
- cm-11-20140308-SNAPSHOT-M4
- cm-11-20140916-SNAPSHOT-M10
- cm-11-20140916-SNAPSHOT-M12
1. I downloaded and installed the latest M12, but upon rebooting it went into a bootloop for 15mins+. I then followed your instructions again to get back. So, it seems I at least need to install them in order starting from the earliest (ie M4), but before doing so I wanted to check if anyone knows if these are even compatible with my HOX+ (Intl)?
2. Which would be the best place to get the right gapps package and installation instructions (if CM can get it wrong, am now wary of someone else leaving out the critical boot.img flash step eg)?
Thanks!
Sent from my Nexus 7 using XDA Free mobile app
EDIT: Nothing like some self-help. I am good now.
Click to expand...
Click to collapse
ok, dont do an ota update in cm, you need s-off, which you cant get on the hox+
flash the rom, flash the boot image, boot, reboot into recovery, SIDELOAD gapps and that should work. use cm10 for the moment, as cm11 has an annoying system ui crash loop bug.
Thanks again for your clear and helpful pointers that got me out of a mess, I seem to have figured it out, downloaded the latest CM11 update and extracted boot.img for separate flashing and it all worked, then added gapps and seems working good now (except for dead touch zone from kids dropping it too many times probably!). The OTAs clearly don't work as is and CM probably should update their instructions and how they push major updates that need a new boot.img. Now to work out what to do with my spare phone...!
Sent from my A0001 using XDA Free mobile app
ahighfield said:
Thanks again for your clear and helpful pointers that got me out of a mess, I seem to have figured it out, downloaded the latest CM11 update and extracted boot.img for separate flashing and it all worked, then added gapps and seems working good now (except for dead touch zone from kids dropping it too many times probably!). The OTAs clearly don't work as is and CM probably should update their instructions and how they push major updates that need a new boot.img. Now to work out what to do with my spare phone...!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
The phone will boot loop, as the kernal is different to the rom