Q&A for [ROM][AOSP][KK]**C-RoM** -4.4.2- -v6.6[ROM][AOSP]
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Hi. I get error code 7 at "Creating symlink". Then the phone tells me to reboot and when I do so, I get the sony logo and after a while it bootloops. (the sony logo) I rolled back to generic .17. Is there a fix for this? (I have C2015, bootloader unlocked, rooted, cwm recovery)
kxait said:
Hi. I get error code 7 at "Creating symlink". Then the phone tells me to reboot and when I do so, I get the sony logo and after a while it bootloops. (the sony logo) I rolled back to generic .17. Is there a fix for this? (I have C2015, bootloader unlocked, rooted, cwm recovery)
Click to expand...
Click to collapse
ur recovery is not updated.. extract zip ,,,flash boot.img then go to recovery n flash
Is the source updated?
Rohan purohit said:
ur recovery is not updated.. extract zip ,,,flash boot.img then go to recovery n flash
Click to expand...
Click to collapse
how can i get the latest recovery? i couldnt find it anywhere. i dont get the "flash boot.img" thing either
Related
Q&A for [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)
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] Root for SHIELD Tablet 2.0 (Lollipop). 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!
UK Root?
Wondering if i should try root since im in UK.
Heres the boot.img from the UK update, is it any different from the NA version before i try root?
EDIT: Wont let me post outside links
Should i try it or no?
DazEB said:
Wondering if i should try root since im in UK.
Heres the boot.img from the UK update, is it any different from the NA version before i try root?
EDIT: Wont let me post outside links
Should i try it or no?
Click to expand...
Click to collapse
If it is the WiFi Only model it should work, but no promises. If it is LTE please PM the link to the boot.img
Cwm and future ota
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Sweet, I followed the "Locked bootloader" method step by step and it working perfectly, no problem whatsoever. Thank you very much!!
layanto said:
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Click to expand...
Click to collapse
Cwm had not prevented any OTAs on the shield tablet for me yet.
Sent from my SHIELD Tablet using XDA Free mobile app
Hi,
Thanks for the instructions. I followed the unlocked bootloader one, but now I cant boot. I flashed the modified LTE boot img and now everytime I boot it keeps going into fastboot mode.
Unlocked bootloader
flashed CWM
Booted into CWM and flashed SuperSU Beta
Selected Yes to fix Root
Reboot system
Boot back into fastboot and flash the modified boot.img
Reboot system...............now keeps booting into fastboot.
Please help.
EDIT: I'm an idiot. Unzip the boot.img before you flash it. Problem solved.
layanto said:
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Click to expand...
Click to collapse
You can also restore stock recovery afterward by flashing this
SuperPichu said:
You can also restore stock recovery afterward by flashing this
Click to expand...
Click to collapse
Possibly dumb question, but is the stock recovery on 4.4.2 KK the same as stock recovery on L? If I backup the stock recovery on KK with flashify, can I then restore once I am rooted and on L?
layanto said:
Possibly dumb question, but is the stock recovery on 4.4.2 KK the same as stock recovery on L? If I backup the stock recovery on KK with flashify, can I then restore once I am rooted and on L?
Click to expand...
Click to collapse
You can definitely restore it if you make a backup. I'm actually not sure if they are the same.
Can this be done without a computer?
Jaybenosa said:
Can this be done without a computer?
Click to expand...
Click to collapse
No
Sent from my SHIELD Tablet using XDA Free mobile app
Yah I figured. So I'm pretty much a noob and I'm trying to unlock my bootloader right now but I'm so lost lol
So I failed miserably, accidentally hit reboot system after step 4 so now I'm on lollipop not rooted and no unlocked boot loader nor have a recovery ??
Jaybenosa said:
Yah I figured. So I'm pretty much a noob and I'm trying to unlock my bootloader right now but I'm so lost lol
Click to expand...
Click to collapse
This is how to unlock the bootloader. It will erase all your userdata.
https://developer.nvidia.com/sites/...eld/SHIELD_tab/HowTo-Flash-Recovery-Image.txt
In reading through the other thread, I can't seem to definitively find what I'm looking for.
My Shield has a locked bootloader, but I've installed the OTA. Is my only option to unlock the bootloader and then follow the unlocked bootloader root method? Or is there a way to root only (I'd like to keep stock recovery) with the OTA already installed?
KentuckyHouse said:
In reading through the other thread, I can't seem to definitively find what I'm looking for.
My Shield has a locked bootloader, but I've installed the OTA. Is my only option to unlock the bootloader and then follow the unlocked bootloader root method? Or is there a way to root only (I'd like to keep stock recovery) with the OTA already installed?
Click to expand...
Click to collapse
You will have to unlock. You can restore the stock recovery afterward if you wish
Sent from my SHIELD Tablet using XDA Free mobile app
Does towelroot still work for the LTE devices when moving to lolli?
OK, so I had to unlock my bootloader since I'd already taken the OTA.
Now I'm at this point. I can't seem to get recovery to stick. I've flashed it multiple times in fastboot and it just won't stick. Now, over in the other thread, someone has asked if I've done the "fastboot flash boot boot-root.img" step yet. This confuses me, as that step comes AFTER you flash recovery, then flash SuperSU with CWM. But seeing as how I can't get recovery to stick, I can't flash SuperSU, and that means I can't move on to that step.
So I guess what I'm asking is, can I run "fastboot flash boot boot-root.img" before "fastboot flash recovery recovery.img"? Will that make a difference? Will it brick my tablet?
I'm all out of ideas here.
Locked bootloader and updated to ver 2.0 lollipop.
Hi there.
I have downloaded and installed version 2 lollipop and I would like root to store my games on SD. When checking the root guide it informed me to download update but not install. I have already installed the update and was wandering if they is a way to root my device still.
Kind regards
Q&A for [RECOVERY][m8wlv] TWRP 2.8.1.0 touch recovery [2014-10-29]
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][m8wlv] TWRP 2.8.1.0 touch recovery [2014-10-29]. 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!
So after using Philz since I got my M8, I decided to switch to TWRP since obviously Philz isn't being developed any longer. I had zero problem flashing this through fastboot and have had no problems with it since doing so. But if I tried to flash it any other way using TWRP managher, or Flashify, or Nandroid Manager, it would work, but then it said it couldn't mount /system and the phone said there was no OS installed. Something wonky with the partition. Flashing back to Philz through fastboot solved this and I could reboot into my phone normally. And then flashing TWRP through fastboot instead worked fine. Weird.
I do not trust apps for flashing a recovery. Period. Any app.
And Flashify, TWRP Manager seem to be especially wonky on the M8....
Cant download
Just want clarify something. For some reason every time i download twrp recovery from their site, it always stops at 99%, and when i download it using my device it will finish downloading but it will have a different md5. Can someone enlighten me why that always happen?
daring0 said:
Just want clarify something. For some reason every time i download twrp recovery from their site, it always stops at 99%, and when i download it using my device it will finish downloading but it will have a different md5. Can someone enlighten me why that always happen?
Click to expand...
Click to collapse
With the new download server, this should no longer be an issue. Just make sure you navigate to the TWRP page and access the Primary Download link from there.
I flashed the new twrp 3.0 I keep getting failure to mount reserve. Any fix for this.
Droid0351 said:
I flashed the new twrp 3.0 I keep getting failure to mount reserve. Any fix for this.
Click to expand...
Click to collapse
Ignore it.
Q&A for [TOOL][TF300T|TF700T|ME301T|N5] Transformer Toolkit v3.2.1
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 [TOOL][TF300T|TF700T|ME301T|N5] Transformer Toolkit v3.2.1. 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!
im lost here , any recovery i try to use keeps failling and say FAILED(data transfer failure(too many links))flashing recovery with fastboot failed!
im using android 4.4.2 kernel 3.1.10-10.6.1.14.10 cyanogenmod 11.0
tried to get the logcat but the tool froze
Driver Not Found
I attempted to flash a twrp recovery. I thought I had the correct drivers installed but on my TF700T tablet it said Key driver not found. Can you help me out at all?
Thanks!
Jen
algren said:
im lost here , any recovery i try to use keeps failling and say FAILED(data transfer failure(too many links))flashing recovery with fastboot failed!
im using android 4.4.2 kernel 3.1.10-10.6.1.14.10 cyanogenmod 11.0
tried to get the logcat but the tool froze
Click to expand...
Click to collapse
JenR said:
I attempted to flash a twrp recovery. I thought I had the correct drivers installed but on my TF700T tablet it said Key driver not found. Can you help me out at all?
Thanks!
Jen
Click to expand...
Click to collapse
Both of you need to provide more details and both of you probably have a driver issue...
The "key driver not found" is totally normal. Every Asus tablet has it and it has absolutely nothing to do with not being able to flash a recovery.
nvflash tool
Hello
Is it possible to extend for NVFLASH this tool ?
A simple tool to make the Tablet Unbrickable would be great
Or does anyone have a step by step instructions ?
My tablet is rooted and unlocked with the bootloader 10.6.1.14.10 .
Skyjumper_GR said:
Is it possible to extend for NVFLASH this tool ?
A simple tool to make the Tablet Unbrickable would be great
Or does anyone have a step by step instructions ?
Click to expand...
Click to collapse
Step by step instructions are here: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Questions
Hello
Thank you for this information, I 've known this manual and have some unanswered questions.
I have the bootloader 10.6.1.14.10
I can leave this out or do I have to downgrade it? ( 10.6.1.14.4 is not available from Asus !)
If it works with the current bootloader , I have modified the boot loader 10.6.1.14.4 apparently after NVFLASH . right?
It must remain on the device or can I switch to the latest after NVFLASH again?
Newer Roms require 10.6.1.14.10 !?
Sorry for my english, I 'm from Germany .
Thanks for the help.
Skyjumper_GR said:
I have the bootloader 10.6.1.14.10
I can leave this out or do I have to downgrade it? ( 10.6.1.14.4 is not available from Asus !)
Click to expand...
Click to collapse
The Flatline tool will replace your bootloader with the hacked version of 10.6.1.14.4. After successfully pulling your blobs you can flash another bootloader.
Q&A for Shield Tablet OTA 2.2 Update
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 Shield Tablet OTA 2.2 Update. 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!
Wipes
There is no need to do any wipe before flash?
Anyone know if this will break my ROOT?
Thanks!
Mat11095 said:
There is no need to do any wipe before flash?
Click to expand...
Click to collapse
No need to wipe unless you're a purist.
Atticus21 said:
Anyone know if this will break my ROOT?
Thanks!
Click to expand...
Click to collapse
It will break root, but if you have an unlocked bootloader, you can easily reinstall cwm,philz, or twrp (if you have to) and reinstall the latest supersu.zip. Also redownload or restore the supersu app.
Then, you'll have root again.
Sent from my SHIELD Tablet using Tapatalk
Tried it update from lollipop 5.0.1
I have the OTA update before this one, and i unlocked boot loader and root the device. IT has a custom recovery.img flashed to install the root.
When i try to install this update, it pops into the update then immediately back to the recovery saying "invalid argument."
I assume its because the device has a custom recovery.img partition. My guess to fix this problem is put back the original recovery image?
Question is, how can i do this without wiping the device? Or if its necessary... how?
Thanks
Fishcake21 said:
I have the OTA update before this one, and i unlocked boot loader and root the device. IT has a custom recovery.img flashed to install the root.
When i try to install this update, it pops into the update then immediately back to the recovery saying "invalid argument."
I assume its because the device has a custom recovery.img partition. My guess to fix this problem is put back the original recovery image?
Question is, how can i do this without wiping the device? Or if its necessary... how?
Thanks
Click to expand...
Click to collapse
You can't use the OTA that comes directly ota from Nvidia's servers because you've altered the recovery and system positions. It well fail.
Instead flash the "full" ota. The links to the full OTA are everywhere on xda since the release. The file is about 725mb . If link to one but I'm using tapatalk right now.
Remember that you have to flash supersu afterward to retain root.
Also, depending on your recovery, you may have to flash that as well.
Fishcake21 said:
I have the OTA update before this one, and i unlocked boot loader and root the device. IT has a custom recovery.img flashed to install the root.
When i try to install this update, it pops into the update then immediately back to the recovery saying "invalid argument."
I assume its because the device has a custom recovery.img partition. My guess to fix this problem is put back the original recovery image?
Question is, how can i do this without wiping the device? Or if its necessary... how?
Thanks
Click to expand...
Click to collapse
Another user, on another thread, said that if you are rooted, flashing the original recovery wont work because the Shield is modified (rooted)
With the custom recovery, you need to flash a full 2.2 ota (is around here somewhere) and wipe cache & dalvik; then flash supersu and your custom recovery*
*Optional: some said they needed to flash the custom rec, some said they didn't flash it and kept their cust. recovery. Personally I'd flash it again.
Q&A for [RECOVERY][BUMPED][D850] TWRP 2.8.5.1 w/ F2FS [03/01]
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][BUMPED][D850] TWRP 2.8.5.1 w/ F2FS [03/01]. 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!
TWRP Recovery issue
Good day, I have an LG G3 D850 rooted on 5.0.1 OTA with stock recovery from unjustified dev root. I flashed twrp from the instructions here with flashify and later tried with rashr, I Also tried to install it through cmd adb on my pc. When I try to reboot to recovery (from rashr/flashify, and even manually) I get a boot certification error and then I guess a boot loop. The screen goes black and the led flashes red and blue. I have to take the battery out to restart. I must be doing something wrong. Any ideas?
Sandmann1381 said:
Good day, I have an LG G3 D850 rooted on 5.0.1 OTA with stock recovery from unjustified dev root. I flashed twrp from the instructions here with flashify and later tried with rashr, I Also tried to install it through cmd adb on my pc. When I try to reboot to recovery (from rashr/flashify, and even manually) I get a boot certification error and then I guess a boot loop. The screen goes black and the led flashes red and blue. I have to take the battery out to restart. I must be doing something wrong. Any ideas?
Click to expand...
Click to collapse
Did you resolve this issue? If so, how'd you do it. I'm having the same one.
No, But I believe they have a fix here where you would have to flash a kit kat bootloader. From what I read this, method works. I just feel more comfortable waiting for it to be done with all lollipop coding.
Sandmann1381 said:
No, But I believe they have a fix here where you would have to flash a kit kat bootloader. From what I read this, method works. I just feel more comfortable waiting for it to be done with all lollipop coding.
Click to expand...
Click to collapse
My thoughts precisely. Thanks for the quick response. Much appreciated.