Hi all, I'm trying to get my TF101 up to speed so to speak. I had previously ( a year or 2 ago) installed TWRP and a Jelly Bean ROM, and decided to update to KatKiss. After some tribulation, I got TWRP updated so I could install the ROM, and I got KatKiss installed. However, I'm having issues flashing SuperSU. Whenever I install the ZIP via TWRP recovery, I get the following message:
Code:
- Placing files
********************
-Finding boot image
--- Boot image: not found, aborting
Then a warning telling me not to let TWRP install SuperSU if it asks (it doesn't) and TWRP tells me the install was Successful. But no SuperSU is installed when I boot into KatKiss. Any idea why this is happening?
Also, I flashed the Pico version of OpenGApps, and am constantly getting a message saying GooglePlay Services has stopped working. Any help on this would be appreciated to.
Thanks!
EDIT: In my frustrations, I thought maybe it would be best to go back to stock and start at square one. I used EasyFlasher to go back to the stock Asus ROM and unroot everything. I'll give installing KatKiss another go tomorrow. I guess mods can delete this thread.
mods, this thread can be locked/deleted.
Related
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The stock Asus firmware includes bootloader, kernel, recovery and apps. You have flashed the stock recovery. Head over to the twrp thread or my ROM thread in my sig to see how to get twrp 2.5 onto your tab.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
Yes, you did. Everytime you install stock file of any version, it will update your bootloader, rom, and kernel. Just use Motochopper to root your device and reinstall your custom recovery with goomanager.
No, it is stock recovery. Just reroot with motochopper and install custom recovery with goomanager. Have fun. :good:
Right, thanks! If I want to stay completely stock I just need to figure out why the newer update is failing. Could be the file name now I think about it.
Otherwise I'll re-root and re-TWRP...
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The Android on his back is your stock recovery and it does not find a valid update file.
Weird is, that your system seems to see the 10.6.1.14 file (I assume you get an automatic notification and click "install" or "update" ) and then the recovery does not seem to install it...?
You could have a bad download, so try that first if you want to get the latest stock rom, or you can try to rename the downloaded file to EP201_768_SDUPDATE.zip, put it on your microSD card and reboot into recovery. The recovery should recognize the update file and start flashing it.
But since you are unlocked anyway - why don't you give CromiX a try? It runs so much better than the stock rom!
And for that, yes you would have to root again using the Motochopper tool and then install TWRP 2.5 with Goo Manager.
If you go that route make sure you flash the latest bootloader from the OP of the CROMiX thread first, boot back into your old rom once before you flash CROMiX.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Anatosuchus said:
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Click to expand...
Click to collapse
It's based on the stock rom, cleaned up and tweaked and optimized. Everything works - and better than on stock! I recommend selecting the option to disable fsync during installation. It boosts performance considerably, and since the rom is totally stable, the "risk" is neglible.
You will love it!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
OK, ChromiX installed! Looks interesting already, will tinker with it over the next couple of days.
xt926 with unlocked bootloader and can run 10.1 nightly from get.cm with no problem. However, when I install a 10.2 nightly - whether from get.cm, epinter, dhacker or skrilaz - even though the initial boot comes up clean, rebooting after the initial boot gets stuck on the boot logo.
I have tried different recovery images - cwm, twrp, oudhs - and different versions of each.
I have tried clean installs, full formats and dirty upgrades from 10.1.
I have tried multiple force boots from this state (power+vol up).
I have tried with and without the updated gapps and UPDATE-SuperSU-v1.51.zip.
Restoring from backup does not get past this hang. The only way out is to revert to stock (I use mattlegroff's DROID_RAZR_HD_Utility_1.21).
Does anyone have any idea how I might get past this or even get a log?
Only thing that fixed this for me was to flash back to stock 4.1.2, flash newest CWM touch recovery, then flash newest nightly, Gapps, and SU. Then, a popup comes up saying something about the ROM wants to flash your boot image, and asks if you'd like to fix this. I answered YES (fix) and been working since.
Any chance you could link where you got your recovery and SU?
Much appreciated.
Same issue here...
I've also tried everything listed above. I've done everything i can possibly think of to get cm 10.2 on my xt926. For some reason my phone just isn't making it after the first reboot. I've searched and found similar issues but none of the troubleshooting has been working for me. I hope to find a way around this. I need that 10.2!
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
GeorgeHahn said:
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
Click to expand...
Click to collapse
one of 2 things should fix this problem,
use cwm 6.0.3.5 from here or
go to recovery/mounts and storage and format the data-media line (i know it says sd card but its internal, do not format the external ed card line or you will loose data on it)
also i updated matts utiliity to the latest ota, so you dont have to take the ota just to get the baseband. its in the dev forum. i will be updating it to a newer version if you wait until later, with the newest recoveries.
edit, btw 2.6.0.0 is not the latest twrp although i recommend using cwm as some have had issues with twrp including me.
First off, the latest TWRP seems to have fixed the problems (for me, anyway). Second, you'll need to use the most up-to-date GAPPs when you flash. Also, a lot of people have noted that mounting sytem prior to doing their wipes has solved the reboot issues.
Thanks a ton for the help. Flashed latest CWM and bumped up to 4.4 and everything's working fine. I appreciate the help!
Hello, I am having some problems installing a working recovery, here is my story... So first the device was 10.6.1.27.5 and its unrootable, so i downgraded to 10.6.1.15.3, where I installed TWRP recovery, and flashed CM 10.2 ROM, but it was too glitchy, so i wiped all data, and fastbooted 10.6.1.15.3 build and stock ROM. So I am now stock,
I am rooted using MottoChop method, and I cant install a custom recovery... I tryed to install TWRP 2.5.0.0 thats the version I was on before, and also tied 2.6.3.0, when flashing the .blob My device turns unresponsive, even when rebooting it with fastboot.
So left with no choice i tried flashing the .img one for JB, (Note: It is currently NOT a OTA update, but manual, so i used the 4.2 first)
I was Able to Flash the custom recovery 2.6.3.0 JB.img and it booted up and worked fine, but then it couldnt mount anything,
I was getting error message:
E: Cant mount /data
and so on... I then tried to flash 2.5.0.0 and got the same result.
GooManager cant find a recovery script for this device...I flashed the TF300T, since thats the kind i have not TF300TG
Im really lost now... I tried ClockworkManager to find a recovery and it said the same thing, I dont want to flash a CWM with flashboot since i here It is terrible.
Any Help Is greatly Appreciated
I notice that alot of these problems, I end up fixing myself... I fixed the issue
But If anyone ever comes into the same situation, heres the fix...
UPDATE to 10.6.27.5 (Yes newest version) Im using US...
Install openrecovery-twrp-2.5.0.0-tf300t-4.2.blob IMPORTANT dont flash the JB version because its only for OTA updates
Open recovery and TWRP will prompt you to install, and beleive it or not, but apparently you can root the newest version,
Just not With MottoChopper and other quick root methods!
If you have any more question, post!
First, I have to apologize for being more or less a noob. I have been away from Android for a few years and just returned with a Galaxy S5. I used to flash ROMs all the time but it has been awhile and I have not had a Samsung before.
I was running stock Lollipop, then I rooted and installed phillZ CWM recovery. I then downloaded MOAR 6.2 and attempted to flash it from recovery, but keep getting errors, it says something about the signature and then it fails and reboots. I tried downloading it several times from both the main source and the mirror, and I did check the MD5. It is on the root of my SD card. So what am I doing wrong? Hopefully someone can help me get back into my Android ROM flashing!
Thank you in advance for your help.
I figured it out - I had flashed the CWM recovery but for some reason I still had the stock android recovery. It's all good now!
Hello, and thank you for taking the time to read this thread!
There were a lot of things that I did to my phone that could be the cause of this problem, so I'll lay it all out chronologically:
I was running CM12 and discovered that the crDroid team developed a 6.0 ROM for the G2. I installed the CAF bootloader, ROM, and GApps zips. Everything went smoothly, but when I rebooted to recovery to install the zip for Xposed, I got a "secure boot error" at the LG screen. Granted, I could boot to system just fine, but not having recovery was kind of a dealbreaker; I love tweaking my phone so I use Xposed frequently. I didn't know what could have broken my recovery, so I just kind of gave up. I scrapped Marshmallow and decided I would go back to using CM12.
I then used the .tot method with LGFlashTool to get everything back to stock, and from there I rooted the phone and installed TWRP using loki. After that, I used TWRP to flash the LP bootloader, CM12, and GApps. But for some reason, when I tried installing GApps it gave me an error: "error executing updater binary in script". I didn't really know what to do so I downloaded AOSPA with the respective GApps and flashed both files successfully.
This is where I am now. After I rebooted to system, the message "Unfortunately, [everything] has stopped." flooded the screen and now I can't really do anything. Any help would be greatly appreciated.
XDA Visitor said:
Hello, and thank you for taking the time to read this thread!
There were a lot of things that I did to my phone that could be the cause of this problem, so I'll lay it all out chronologically:
I was running CM12 and discovered that the crDroid team developed a 6.0 ROM for the G2. I installed the CAF bootloader, ROM, and GApps zips. Everything went smoothly, but when I rebooted to recovery to install the zip for Xposed, I got a "secure boot error" at the LG screen. Granted, I could boot to system just fine, but not having recovery was kind of a dealbreaker; I love tweaking my phone so I use Xposed frequently. I didn't know what could have broken my recovery, so I just kind of gave up. I scrapped Marshmallow and decided I would go back to using CM12.
I then used the .tot method with LGFlashTool to get everything back to stock, and from there I rooted the phone and installed TWRP using loki. After that, I used TWRP to flash the LP bootloader, CM12, and GApps. But for some reason, when I tried installing GApps it gave me an error: "error executing updater binary in script". I didn't really know what to do so I downloaded AOSPA with the respective GApps and flashed both files successfully.
This is where I am now. After I rebooted to system, the message "Unfortunately, [everything] has stopped." flooded the screen and now I can't really do anything. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hello,
it seems more like an incompatible gapps issue.
Further, you could make XDA account so we could assist you in moving this thread to LG G2 Q & A whereall the LG g2 experts could help you in fixing the issue.
-Vatsal