Database Info

[Q] [TF700] Root not working after updating Cromi-X to 4.7.0

Hello there ! Newbie here.
I've just updated my Asus TF700T to Cromi-X 4.7.0.
After the installation, I noticed that it was not rooted anymore. When opening SuperSU, an error message appears: "There is no SU binary installed and SuperSu cannot install it, it's a problem."
I tried afterwards a fresh install of Cromi-X, but the problem was still there.
Then I tried to execute the Motochopper script, which appeared as successful, but the error message is still there.
Do you know what could be the solution for this problem ? Without root, I cannot execute applications like lagfix, titanium backup and full screen, which is annoying.
Thanks in advance for your help !
And sorry for my english (french talking here !)

Sounds like the ROM didn't flash properly. Flash it again please.

sbdags said:
Sounds like the ROM didn't flash properly. Flash it again please.
Click to expand...
Click to collapse
I did, several times...
First I tried with and without the TWRP root option (after the Cromi-X install, TWRP proposes to root the tablet). Both of these two options didn't work.
Then I tried with full wipe, even the microsd (just let the Cromi-X installation archive on it). At this point, the tablet offered me the possibility of updating the supersu. I did update it, but when opening super su, the same error message appears.
I don't know what other test I can do. Any ideas ?
Thanks for your answer.

Soralito said:
I did, several times...
First I tried with and without the TWRP root option (after the Cromi-X install, TWRP proposes to root the tablet). Both of these two options didn't work.
Then I tried with full wipe, even the microsd (just let the Cromi-X installation archive on it). At this point, the tablet offered me the possibility of updating the supersu. I did update it, but when opening super su, the same error message appears.
I don't know what other test I can do. Any ideas ?
Thanks for your answer.
Click to expand...
Click to collapse
The only time I have ever seen this is when the ROM doesn't complete its flash in twrp. So it gets partially flashed.
When you flash you get the chance to save a log. It gets saved to the same folder as the zip file you flashed. Can you post it please.
Also make sure you turn on signature verification in twrp before flashing. My files are signed and this will stop it flashing a corrupted download.

sbdags said:
The only time I have ever seen this is when the ROM doesn't complete its flash in twrp. So it gets partially flashed.
When you flash you get the chance to save a log. It gets saved to the same folder as the zip file you flashed. Can you post it please.
Also make sure you turn on signature verification in twrp before flashing. My files are signed and this will stop it flashing a corrupted download.
Click to expand...
Click to collapse
Hello, I can't find any log file in the folder of my zip file... What would be the name of this log file ? Maybe I can find it somewhere else...
I have re-downloaded the rom from another source and try a new flash tonight.
Anyway thanks for your help ! (I just noticed I was talking to THE developer of Cromi-X Sir, it's an honor )

It's working now !
I flashed the rom downloaded from another mirror, and activated the zip signature verification, and it works now
Many thanks for your help, and your fabulous work on this rom.
See you soon on this forum !

Soralito said:
It's working now !
I flashed the rom downloaded from another mirror, and activated the zip signature verification, and it works now
Many thanks for your help, and your fabulous work on this rom.
See you soon on this forum !
Click to expand...
Click to collapse
You are welcome - glad you got it sorted

Hey there guys and gals. Newbie here. I've read this thread and I am having the same issue as the original poster. I don't really understand what was said here but this is my question: if I downloaded the motochopper root app to the tablet and opened it from there and did the root right from my tablet would the root take hold then? I have an Asus TF700 by the way.

Motochopper is an exe you use on your PC. You cannot install it on the tablet. And it worked only up to firmware version 10.6.1.14.8.
Read this, most of your answers should be answered...
http://forum.xda-developers.com/showthread.php?t=2688891

berndblb said:
Motochopper is an exe you use on your PC. You cannot install it on the tablet. And it worked only up to firmware version 10.6.1.14.8.
Read this, most of your answers should be answered...
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
Should I factory reset to stock software first or just go ahead and run the new root software?
---------- Post added at 03:32 AM ---------- Previous post was at 02:47 AM ----------
reubdog30 said:
Should I factory reset to stock software first or just go ahead and run the new root software?
Click to expand...
Click to collapse
It worked!!! I'm good now. Thanks for your help!!

[Q] Can't upgrade to 10.6.1.14.10 in TWRP

Hi,
I'm no expert in flashing tablets but I have done a few phones in the past, but I'm stuck with a problem trying to get the firmware file (10.6.1.1.10) upgraded to my Jellybean 4.2.1 install, so that I can eventually get CROMI-X on my tablet. I had '10' on my TF700 via OTA and downgraded to '8' to get root (as per the CROMI-X instructions but I can't get '10' to load via TWRP, I just get "refresh failed. Please try again" I've tried shortening the filename-loading from SD card and Internal storage-redownloading the file but nothing changes. I did notice that when I boot into TWRP, it will say 'Updating partition tables' even before I attempt to flash the update and it will appear to be stuck at this point after checking the .md5 file.
Can anyone offer any suggestions or anything I can try without bricking the thing?

Argenti12 said:
Hi,
I'm no expert in flashing tablets but I have done a few phones in the past, but I'm stuck with a problem trying to get the firmware file (10.6.1.1.10) upgraded to my Jellybean 4.2.1 install, so that I can eventually get CROMI-X on my tablet. I had '10' on my TF700 via OTA and downgraded to '8' to get root (as per the CROMI-X instructions but I can't get '10' to load via TWRP
Click to expand...
Click to collapse
Any 10.6.1.14.x bootloader is compatible with CROMI-X 5.x, so you don't need to upgrade to .10.

_that said:
Any 10.6.1.14.x bootloader is compatible with CROMI-X 5.x, so you don't need to upgrade to .10.
Click to expand...
Click to collapse
So you think I can just go ahead and install CROMI-X now? For future reference, is the 'Updating partition details' in TWRP normal? I don't remember seeing this when I first installed.
Thanks for the help.

Argenti12 said:
So you think I can just go ahead and install CROMI-X now?
Click to expand...
Click to collapse
To be 100% sure, check in the bootloader menu (before you select RCK) that your bootloader build version is 10.6.1.14.x, with x either 4, 8, or 10.
Argenti12 said:
For future reference, is the 'Updating partition details' in TWRP normal?
Click to expand...
Click to collapse
Yes.

_that said:
To be 100% sure, check in the bootloader menu (before you select RCK) that your bootloader build version is 10.6.1.14.x, with x either 4, 8, or 10.
Yes, its '8'.
Yes.
Click to expand...
Click to collapse
I was going to just try and install Cromi but now TWRP doesnt see the downloaded .zip!
This is becoming a headache.

Argenti12 said:
I was going to just try and install Cromi but now TWRP doesnt see the downloaded .zip!
This is becoming a headache.
Click to expand...
Click to collapse
Did you browse to the right folder that has the cromi zip file? In TWRP, you can select the internal sd or external sd. Make sure that you have selected the right sd card...

LetMeKnow said:
Did you browse to the right folder that has the cromi zip file? In TWRP, you can select the internal sd or external sd. Make sure that you have selected the right sd card...
Click to expand...
Click to collapse
Okay, I redownloaded the ROM file and copied it to the SD...plugged it back in the tablet and booted into TWRP, ....now I see both! oh well, I installed the ROM and now have CROMI-X running on this baby! Thanks for your help and advice guys.
One small thing that I noticed, again with TWRP is that when I invoke the power menu, I don't get any options to boot to recovery...or anything non-standard for that matter. I think my TWRP might be broken, is there a way to uninstall/reinstall?
Thanks again guys.

Argenti12 said:
Okay, I redownloaded the ROM file and copied it to the SD...plugged it back in the tablet and booted into TWRP, ....now I see both! oh well, I installed the ROM and now have CROMI-X running on this baby! Thanks for your help and advice guys.
One small thing that I noticed, again with TWRP is that when I invoke the power menu, I don't get any options to boot to recovery...or anything non-standard for that matter. I think my TWRP might be broken, is there a way to uninstall/reinstall?
Thanks again guys.
Click to expand...
Click to collapse
TWRP on tf700t, you have only two options on the boot menu. One is a reboot to your system. Second is power off your device.
About the uninstall/reinstall, all you need is to flash the TWRP blob on top of your existing one....
Edit: I think that your TWRP is working properly. If you don't have to flash your custom recovery again, you can minimize the risk of brick your device. Please don't mess with your bootloader and your recovery unless you must touch them for a good reason. Otherwise, just leave them alone. Just my two cents....

LetMeKnow said:
TWRP on tf700t, you have only two options on the boot menu. One is a reboot to your system. Second is power off your device.
About the uninstall/reinstall, all you need is to flash the TWRP blob on top of your existing one....
Edit: I think that your TWRP is working properly. If you don't have to flash your custom recovery again, you can minimize the risk of brick your device. Please don't mess with your bootloader and your recovery unless you must touch them for a good reason. Otherwise, just leave them alone. Just my two cents....
Click to expand...
Click to collapse
Great, thanks for clearing up that doubt...and also for the good advice! I'm already enjoying the CROMI-X experience!

[Q] Force OTA udpate?

Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!

Nikojiro said:
Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!
Click to expand...
Click to collapse
I'm having the same issue. No idea, we might just have to wait a while.

Delete Data from Google Framework Apk and then start the Update Checker.

UNCUT88RAW said:
Delete Data from Google Framework Apk and then start the Update Checker.
Click to expand...
Click to collapse
Aah didn't think of that trick, it works, <thank you> pressed :laugh:

Could someone please give me a link to the Stock Recovery and maybe a description what the best way is to flash it instead of the Custom Recovery? Thanks ...

I have had no problems flashing updates with ClockWorkMOD revocery.
However if you have the 1.0 version from http://forum.xda-developers.com/showthread.php?t=2390389 the update will fail with an error.
1.0 had a name wrong that makes it think the update are for a different device.
the command to flash the stock recovery (if every thing is in the correct place) is "fastboot flash recovery recovery.img"

chevyowner said:
1.0 had a name wrong that makes it think the update are for a different device.
Click to expand...
Click to collapse
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!

fquadrat said:
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!
Click to expand...
Click to collapse
When I was checking to see if I had 1.1 I found the naming error is still there.
This brings me to my next point. I had edited the ramdisk on 1.0 to correct the naming error, and not updated to 1.1
Here is a link to 1.1 with the edited ramdisk.
Update
I messed up the link in Google drive i think i fixed it now.

chevyowner said:
Here is a link to 1.1 with the edited ramdisk.
Click to expand...
Click to collapse
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.

fquadrat said:
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.
Click to expand...
Click to collapse
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"

chevyowner said:
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
Sorry, I just flashed stock recovery and my Shield is installing Android 4.3 right this second ...

chevyowner said:
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?

desertflame said:
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?
Click to expand...
Click to collapse
should be

update to latest OTA and recovery issue

HI all, I have CM12 installed on my rooted phone and this morning when I switched it on, I got a message saying:
"WARNING: Update Cyanogen recovery is disabled. This may cause issues with updating your device. Please enable Update Cyanogen recovery in developer options"
Now, that option is off because I have my custom recovery TWRP installed on the phone, I'd like to keep that and I don't want to reinstall it after the update, so I believe I should ignore the message, but what I wanted to check with you guys is whether ignoring it will in fact cause any issues as this is the first time ever I've seen this message (this update by the way I think is the first one after installing CM12).
Any idea?
thanks

Disregard the message.

Thanks Heisenberg,
I did that but when the phone restarts trying to install the update, it goes straight into recovery mode (TWRP) and from there I don't think I can install the update, as none of the options seem to allow me to do so, see screenshot http://s23.postimg.org/6d6s7wyq3/IMG_20150625_135453.jpg

All right, I downloaded the zip from here http://cyanogen-ota-bacon.somee.com/ and tried to flash it from TWRP, but I get an error, screenshot here http://s28.postimg.org/zb06wtcpp/OTA_error.jpg, any idea why?

Same here, got an error in TWRP logs that prevented the update to install.
I'd like to avoid reflashing stock recovery only to install the update...
Heres the log: http://s29.postimg.org/njqqqlfc7/Screenshot_2015_06_25_08_49_42.png
Seems something related to outdated "build fingerprint" my device has currently 12.0-YNG1TAS17L

I guess the alternative would be to do it thru Cyanogen Recovery, but let's see what more knowledgeable members have to say as, like you, I don't want to have to reinstall TWRP and SU just for the sake of the update

Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official

Thanks for clarifying that davebugyi, then so be it, I'll do it thru cyanogen recovery and then reflash TWRP and probably SU as well
thanks
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse

Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse

duratto said:
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
Click to expand...
Click to collapse
For example here: http://forum.xda-developers.com/showthread.php?t=2810365

thanks! Ah OK I see so that's the whole ROM there as opposed to just an update

davebugyi said:
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
Click to expand...
Click to collapse
Do you mean flashing only this update found at the end of the first post?
YNG1TAS2I3 Radio, etc - Mirror - Same as YNG1TAS0YL
md5 - 6d5db5af6c92b814b9a0ebd18341dd8e
Click to expand...
Click to collapse
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?

Yes, but if I'm not mistaken, judging from the file size, that's the whole ROM
tsnake said:
Do you mean flashing only this update found at the end of the first post?
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Click to expand...
Click to collapse

The file I quoted is not a whole ROM, it's 31 MB.

AH OK, sorry I thught you referred to the 500mb file

Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.

I'm having the same issue. Anyone?

Got the same problem. Any idea?

duratto said:
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
Click to expand...
Click to collapse
Bump for a fix?

Juergen1337 said:
Got the same problem. Any idea?
Click to expand...
Click to collapse
The solution seems to be installing the new ROM provided. Related problem here http://forum.xda-developers.com/oneplus-one/help/twrp-cm-android-version-mismatch-t3147658

Nexus 5 blue circle (doesn't start).

Hi, my nexus 5 (16gb) is not starting. I get the Google logo and after it, a blue circle going smoothly from right to left, again and again. I can start bootloader and recovery (TWRP). I know I did something wrong years ago, maybe flashing a ROM, but I didn't need the Nexus at the time and I let it be. I don't remember what I tried or changed when it happened.
I don't know how to search for a solution since I don't know what the problem is. Does anyone know a solution?

That's the LineageOS 14 boot animation, sounds like a bootloop. If you want to go back to stock, flash the factory image from here https://developers.google.com/android/images#hammerhead
Keep in mind that factory images wipe all data on the device, backup things you want to keep if any from TWRP.

goo.gle said:
That's the LineageOS 14 boot animation, sounds like a bootloop. If you want to go back to stock, flash the factory image from here https://developers.google.com/android/images#hammerhead
Keep in mind that factory images wipe all data on the device, backup things you want to keep if any from TWRP.
Click to expand...
Click to collapse
Thanks for that! When trying to flash I get the error "E: unknown command [log]" (with LineageOS) and just flashing error (with factory image).

CincoNuestro said:
Thanks for that! When trying to flash I get the error "E: unknown command [log]" (with LineageOS) and just flashing error (with factory image).
Click to expand...
Click to collapse
Try flashing a newer version of twrp, and then LAOS. If it doesn't work then sorry, I won't be of help

goo.gle said:
Try flashing a newer version of twrp, and then LAOS. If it doesn't work then sorry, I won't be of help
Click to expand...
Click to collapse
That worked!!! Thanks :good::good::good:

CincoNuestro said:
That worked!!! Thanks :good::good::good:
Click to expand...
Click to collapse
Great, glad to hear it.