Hello guys,
i am little bit new into custom ROMs but i think that i've learned the basics. To my problem. I've followed the guides to unlock tablet, flash TWRP and I've flashed ROM to KatKiss - Nougatella #013. First boot and every other boot looks similar to me. I see the Asus default screen and it looks like it is in a boot loop but if i keep it in it sometimes i see the Timduru animation and then again it starts from begining. I left it in this state all night and when i woke up i saw that the system is booted in first initial setup. With Nougatella i was not able to finish this initial setup as some Google aps constatnly fails.
So i wiped/formated everything and tryed KatKiss - KatshMallow #029. Again there was similar boot loop but if i keep it for some time it was booted and in this case i was able to set everything and run the tablet in normal way. Problem here is that if i reboot its again in a boot loop for couple hours until it boots correctly.
If i flash back the stock ROM everything is booting fine.
Thank you in advance for any advice how to solve this and sorry for my english.
xsida said:
Hello guys,
i am little bit new into custom ROMs but i think that i've learned the basics. To my problem. I've followed the guides to unlock tablet, flash TWRP and I've flashed ROM to KatKiss - Nougatella #013. First boot and every other boot looks similar to me. I see the Asus default screen and it looks like it is in a boot loop but if i keep it in it sometimes i see the Timduru animation and then again it starts from begining. I left it in this state all night and when i woke up i saw that the system is booted in first initial setup. With Nougatella i was not able to finish this initial setup as some Google aps constatnly fails.
So i wiped/formated everything and tryed KatKiss - KatshMallow #029. Again there was similar boot loop but if i keep it for some time it was booted and in this case i was able to set everything and run the tablet in normal way. Problem here is that if i reboot its again in a boot loop for couple hours until it boots correctly.
If i flash back the stock ROM everything is booting fine.
Thank you in advance for any advice how to solve this and sorry for my english.
Click to expand...
Click to collapse
Do you have Kang TWRP 2.8.7.2 and did you follow exactly the install instruction in each post #1 especially flashing Rom, Gapps and SuperSU in one run?
Plus: Did you format data in TWRP prior to flashing the Rom? Sounds almost as if you flashed right on top of stock.
Did you flash the Pico gapps - no other gapps version?
Changing the file system on /data to f2fs also will help
Sent from my K00C using Tapatalk
Yes, i got Kang TWRP 2.8.7.2 and followed the instructions. Wipe/format flash, set /data filesystem to f2fs, flashed ROM then SuperSU and Gaps Pico (or the version which is recommended in KatKiss thread) Wipe cache/dalvik and then reboot.
xsida said:
,
With Nougatella I was not able to finish this initial setup as some Google aps constantly fails.
Thank you in advance for any advice how to solve this and sorry for my english.
Click to expand...
Click to collapse
Did you really flash "OpenGapps ARM 7.1 Pico" ? If not, try again after format /data.
ebonit said:
Did you really flash "OpenGapps ARM 7.1 Pico" ? If not, try again after format /data.
Click to expand...
Click to collapse
Maybe it was not PICO but NANO, anyway if i fix the initial setup problem with this I think that the problem with booting will be the same as i got in KatKiss - KatshMallow #029.
xsida said:
Maybe it was not PICO but NANO, anyway if i fix the initial setup problem with this I think that the problem with booting will be the same as i got in KatKiss - KatshMallow #029.
Click to expand...
Click to collapse
I'm sorry, but you might be right in general. However there seems to be something hidden you didn't take care of. For instance KatshMallow #029 needs OpenGapps ARM 6.0 and KatKiss - Nougatella #13 needs OpenGapps ARM 7.1.
As you mentioned you switched between 6.0 and 7.1. Did you everytime make a "clean install" and also switched gapps?
Install Rom, Gapps and SuperSU in one run means use the possibility of Kang TWRP to add them all for one install. After that wipe dalvik and reboot by TWRP. Did you do so?
Please find out where you failed perhaps and try to run a clean reinstall following Timduru's instruction very carefully step by step.
BTW, your device runs on stock without issues as you mentioned. That's a great evidence that's it OK.
ebonit said:
I'm sorry, but you might be right in general. However there seems to be something hidden you didn't take care of. For instance KatshMallow #029 needs OpenGapps ARM 6.0 and KatKiss - Nougatella #13 needs OpenGapps ARM 7.1.
As you mentioned you switched between 6.0 and 7.1. Did you everytime make a "clean install" and also switched gapps?
Install Rom, Gapps and SuperSU in one run means use the possibility of Kang TWRP to add them all for one install. After that wipe dalvik and reboot by TWRP. Did you do so?
Please find out where you failed perhaps and try to run a clean reinstall following Timduru's instruction very carefully step by step.
BTW, your device runs on stock without issues as you mentioned. That's a great evidence that's it OK.
Click to expand...
Click to collapse
Yes when i switched to KatshMallow i've formated and wiped everything again and used the packages that Timduru is suggesting in his thread for 6.0 ROM. I did not used the TWRP option to link the .zip installs into one run but i run it one by one without restart(Pressed Install, choosed ROM.zip file, after successfull end i've pressed back button and choosed install SuperSU.zip, Gapps.zip and after that wiped dalvik and reboot). I will try it once more with linked install into one run if this makes some difference.
Ok here is my procedure :
booted into TWRP [email protected]
wipe/format : factory reset, /data, /system, cache and dalvik cache
changed /data to f2fs
pushed through adb these zip files: KatKiss-6.0_TF300T_029, BETA-SuperSU-v2.52, open_gapps-arm-6.0-pico-20161125
installed in this order : ROM, SuperSU, Gapps
wipe dalvik/cache
reboot
now its in a boot loop where the asus screen with 'the device is unlocked' si changing with black screen(30minutes allready). I will keep it in this state to see if it boots to ROM as last time.
xsida said:
Ok here is my procedure :
booted into TWRP [email protected]
wipe/format : factory reset, /data, /system, cache and dalvik cache
changed /data to f2fs
pushed through adb these zip files: KatKiss-6.0_TF300T_029, BETA-SuperSU-v2.52, open_gapps-arm-6.0-pico-20161125
installed in this order : ROM, SuperSU, Gapps
wipe dalvik/cache
reboot
now its in a boot loop where the asus screen with 'the device is unlocked' si changing with black screen(30minutes allready). I will keep it in this state to see if it boots to ROM as last time.
Click to expand...
Click to collapse
Bad luck! I have no idea at that time, because I have never flashed this zip files through adb. I always used TWRP and never had any issues. Lets wait for berndblb if he has an idea.
Could you start into TWRP? If yes, meanwhile you could try to roll back the whole process using sole TWRP.
There's an error somewhere in your procedure. If the tablet runs fine on stock it will run fine on this rom.
I don't like this line, sounds unclear...
xsida said:
Ok here is my procedure :
wipe/format : factory reset, /data, /system, cache and dalvik cache
Click to expand...
Click to collapse
Too many people mix up wipes and formats... You format only data, not factory reset, not wipe - you format it ext4, then convert it to f2fs. Formatting in TWRP takes 1 hour +. If it went faster you did not format.
So break down your steps further for us. Details please.
If that process was ok, you are messing up some other place. Delete all the files you have been working with and download them again. Take your time, make sure you get the right one and then check the md5
ok last time it booted to initial setup after couple hours but on reboot it was back in boot loop. Now iam doing everything once more and here is detailed procedure:
Boot to recovery TWRP 2.8.7.2.
Wipe - swipe to factory reset
Wipe - format data - typed yes to continue
Wipe - advanced wipe - select cache, dalvik, system (just to be sure)
Wipe - advanced wipe - select data - change filesystem to f2fs
Reboot(just in case, trying this step for first time)
Boot to recovery TWRP
from computer through adb pushed the zip files
Install - KatKiss-6.0_TF300T_029.zip - MD5 matched
Install - BETA-SuperSU-v2.52 - no md5 found
Install - open_gapps-arm-6.0-pico-20161205 - MD5 matched
Wipe cache/dalvik
Reboot system
Looks like that its in a same boot loop as always. 1 of 100(my guess) boot attempts is finished with successful boot. In rest it ends on Asus logo or sometimes it get stuck on Timduru animation.
You seem to be doing everything right... Scratching my head here.... What's your bootloader version?
berndblb said:
You seem to be doing everything right... Scratching my head here.... What's your bootloader version?
Click to expand...
Click to collapse
it says Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.27.5-20130902" A03
berndblb said:
You seem to be doing everything right... QUOTE]
I agree with you, he did really a good job. The bootloader is also correct.
However Kang TWRP is a very strong tool. I swear on it. So I would roll back the whole process using TWRP only. That means to put the zip files (Rom, SuperSU and Gapps) on the extern SD card and run the whole succession step by step using TWRP only.
Whatever it takes. It's worth to try.
Click to expand...
Click to collapse
That inspires an idea. Load the Rom files on a microSD and flash them from there. Maybe the adb push is doing something screwy....
Sent from my K00C using Tapatalk
first, thank you guys, that you are still trying to help me
I installed the files from sd card without adb. At first it looked promising. After first reboot i saw some progress bar(not sure if i just did not noticed that before) but it was really fast, then black screen for a while and Katkiss logo. But now its back in boot loop, my personal feeling is that now i see more often the Katkiss logo then before but still its not booting correctly.
Just a note, not sure that matters but i got stock rom there before flashing.
Boot to recovery TWRP 2.8.7.2.
Wipe - swipe to factory reset
Wipe - advanced wipe - select cache, dalvik, system (just to be sure)
Wipe - format data - typed yes to continue
Wipe - advanced wipe - select data - change filesystem to f2fs
Install - KatKiss-6.0_TF300T_029.zip - MD5 matched
Install - BETA-SuperSU-v2.52 - no md5 found
Install - open_gapps-arm-6.0-pico-20161205 - MD5 matched
Wipe cache/dalvik
Is there some log file where i can dig more info about why its not booting?
xsida said:
first, thank you guys, that you are still trying to help me
I installed the files from sd card without adb. At first it looked promising. After first reboot i saw some progress bar(not sure if i just did not noticed that before) but it was really fast, then black screen for a while and Katkiss logo. But now its back in boot loop, my personal feeling is that now i see more often the Katkiss logo then before but still its not booting correctly.
Just a note, not sure that matters but i got stock rom there before flashing.
Boot to recovery TWRP 2.8.7.2.
Wipe - swipe to factory reset
Wipe - advanced wipe - select cache, dalvik, system (just to be sure)
Wipe - format data - typed yes to continue
Wipe - advanced wipe - select data - change filesystem to f2fs
Install - KatKiss-6.0_TF300T_029.zip - MD5 matched
Install - BETA-SuperSU-v2.52 - no md5 found
Install - open_gapps-arm-6.0-pico-20161205 - MD5 matched
Wipe cache/dalvik
Is there some log file where i can dig more info about why its not booting?
Click to expand...
Click to collapse
Great job, however it is an exceptional situation. In my opinion only a developer could help. So please open the Terminal Emulator (recommend Jack Palevich version) and run the following two commands:
Code: su
Code: logcat
Save the file and send it with a kind note to Timduru. Maybe he can figure out the reason for your issue, because it is of general interest.
To run a terminal app the darn thing would need to boot! :cyclops:
First of all, the brief blue bar during first boot is the kernel being written to the boot partition - that is normal.
Just like everything is normal with you - except that it doesn't work! I have a similar situation at my job with our behemoth of a booking software and I solved that today - I think....
And then I come home to this! You're killing me! :laugh:
You could try to run a logcat in adb. You did say that eventually it sometimes boots, right?
I just tried it on my 700, the kernel does not seem to support running a logcat of the boot process. No return whatsoever before Android is booted.
If you want to try that, get it to boot and then run
Code:
adb logcat
if you want to watch the log in the cmd window. Even better is
Code:
adb logcat > logcat.txt
.
That creates a text file in your adb folder which you can then post somewhere where a kind soul may take it look at it. I will, but I'm lousy at reading logs...
To stop capturing the log hit Ctrl+c
So stock runs fine but both Katkiss N and M won't. Mhhhhh
Try this: Format data one more time and this time leave it ext4 and flash the rom again. The rom supports data on ext4 and should run fine. Not as well as on f2fs but it should run.
If it does run on ext4 something may be wrong with TWRP's f2fs conversion. Maybe.....
Edit: You know, that may be it. I just googled "problems TWRP 2.8.7.2 f2fs" and found some indicators on github that there were some quirky things going on. Interestingly enough your version of the recovery is not even on Teamwin's website anymore. Which is another very good hint that you probably don't want to use it. Download the latest TWRP from here: https://dl.twrp.me/tf300t/
Flash it in fastboot, reboot once, then reboot to recovery and start the whole process again.
And you better report success this time!! :highfive:
berndblb said:
Edit: You know, that may be it. I just googled "problems TWRP 2.8.7.2 f2fs" and found some indicators on github that there were some quirky things going on. Interestingly enough your version of the recovery is not even on Teamwin's website anymore. Which is another very good hint that you probably don't want to use it. Download the latest TWRP from here: https://dl.twrp.me/tf300t/
Click to expand...
Click to collapse
First of all I would like to note that in my point of view TWRP 2.8.7.2 and Kang TWRP [email protected] are two different things. Kang TWRP made by Josh ( lj50036 Recognized Contributor) is still recommended by Timduru for KatKiss Rom. It was never for download shown on the general TWRP site. The mentioned issues on github however stand directly in reference to TWRP 2.8.7.2.
On the other hand I would like to mention that there were many problems in the past by using TWRP 3.0 and this Rom especially with F2FS . So I have warned several times to use TWRP 3.0 instead of Kang TWRP.
PS: Genuine Kang TWRP download with md5: https://www.androidfilehost.com/?fid=24052804347781183
Related
OK, I've done this many times to many devices, never had this happen before. Unlocked, rooted, TWRP installed, have tried two different ROMS, Slim and CM11, tried both direct download and from my PC then transferred, can't get a custom ROM to install, keeps erroring out while trying to install ROM from TWRP, even though I wipe System, Dalvik, and Cache. 'Error updating binary executor in zip'
thoughts?
EDIT: on twrp 2.5.0.0 - maybe need a newer version?
Tried 2.6.3.0 - it won't wipe dalvik, cache, or system? Actually, it cant see or mount any drives...
And CM Recovery has the same issue...?
This worked:
http://forum.xda-developers.com/devdb/project/dl/?id=3727
friedsonjm said:
OK, I've done this many times to many devices, never had this happen before. Unlocked, rooted, TWRP installed, have tried two different ROMS, Slim and CM11, tried both direct download and from my PC then transferred, can't get a custom ROM to install, keeps erroring out while trying to install ROM from TWRP, even though I wipe System, Dalvik, and Cache. 'Error updating binary executor in zip'
thoughts?
EDIT: on twrp 2.5.0.0 - maybe need a newer version?
Tried 2.6.3.0 - it won't wipe dalvik, cache, or system? Actually, it cant see or mount any drives...
And CM Recovery has the same issue...?
This worked:
http://forum.xda-developers.com/devdb/project/dl/?id=3727
Click to expand...
Click to collapse
If you are trying to install CM11, which is based on KitKat, looks like everyone says to use the Omni version of TWRP. Here's a link to that zip in my Dropbox. https://www.dropbox.com/s/cctivhx2kcpwnfz/TWRP-TF300T-2_7_0_1.zip. Install is different for it though. Put the zip file on a micro SD card or in the internal storage and then boot into whatever custom recovery you have working (I usually go back to stock and flash TWRP 2.4.0.0 or 2.4.4.0 whenever I run into problems. I found a great TWRP recovery installer someone made for Windows, here's that zip. https://www.dropbox.com/s/jut7sytp8n7c94u/recoverytf300t4.2.zip). Once in recovery, go to Install and flash the Omni version 2.7.0.1. After that finishes, reboot to system so that the Omni version can complete installation (you'll see the blue install bar, like what shows when you Fastboot install a recovery). Your tablet will reboot after that so I usually hold Volume Down when the display goes dark so that I can go into the new recovery. I've also recently found 2 "new" recoveries that work fairly with CM11, probably due to the fact that they are based on CM Recovery. I'll include the links for you. They both get installed via Fastboot. Hope this helps!
Philz Touch Recovery - https://www.dropbox.com/s/eea29g652s34p76/philz_touch_6.19.3-tf300t.img
Flatline Recovery (from the process of Wheelie/NVFlash for Jelly Bean, which I recommend you do if you haven't yet. It's been a life saver.) -https://www.dropbox.com/s/xvn7tg3tt0pxo8s/flatline_tf300.img
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Hey Your in the right place
Shoot me an email, we can review your issues and if we find a solution we can post back here to help
XDA users with there issues....
My email is everywhere talke a look around
Thx Josh
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Sounds like you are on an old bootloader. Flash the stock rom from asus by unzipping the zip you download from their website and placing in the root folder of your micro sd and then go into rck from the bootloader menu (power + volume down whilst booting)
Or you could just flash it from recovery....
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Asphodele said:
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Click to expand...
Click to collapse
I buy a tf700 with cm 11 a few days ago i am really interessted on how this steps works. I really want to make it unbrickeable, But i dont really understand how it works. I can not enter in fastboot. at least i got cwm interface when rebooting with adb into recovery.
Can u explain how you did it?
It invovles flashing a modified bootloader and the flatline recovery and then using Wheelie to generate your nvflash blobs.
Step-by-step instructions (which you need to follow to the letter) are here:
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Stuck in boot loop, fastboot and recovery accessible
Hello,
I'm having a similar issue and I need help! Initially my tablet was rooted with Cromi-X 5.4. Then I decided to try Crombi-KK.
Here is what happened:
- Updated TWRP recovery
- Did a full wipe as recommended
- Flashing got stuck at the Crombi-KK loading sign
- Tried to reflash but TWRP wasn't detecting data partition anymore
- Instead installed the other recommended recovery CWMR.
- Flashed Crombi-KK, it worked. Played around with it for a few days, it was wonderful, fast and responsive.
- Battery died out and when I turned it back on I got a UIDs system inconsistent error.
- I found online many recommendations to reflash so I tried to do that
- Since then I'm stuck in a boot loop. I see the initial "bios" Asus logo then it restarts over and over.
- I am able to access bootloader and recovery
I've tried reflashing the asus stock blob. I've tried wiping the data through CWMR but it starts working and then it restarts. I don't know what to do anymore, so if anyone can help me, I would really appreciate it!
Thanks
Which recovery and bootloader version do you have now?
A (for KK) outdated bootloader seems the most likely culprit.
You can try save the recovery log when you flash or grab a logcat of the bootloop, but probably it'll only tell you that the recovery cannot mount /data.
Determine that you are on the correct bootloader, if not update it. If you're lucky the tablet will start right up. If it doesn't, formatting /data is the only way I know to get it back. Not just wiping - formatting it. You will loose everything on internal SD, so I hope you have a nandroid you can restore from later.
If you use TWRP 2.7+ be aware that formatting can take more than an hour. Let it finish!
For good measure, download CROMBi-KK again, check the md5 and then flash that file.
I'm on 10.6.1.14.10 bootloader which I think is the latest one
I have 6.0.4.7 CWMR
I'm trying to format data completely but when i do it in CWMR it starts and then the tablet reboots on it's own after a couple of minutes.
How can I retrieve the logs, I never had to do it before.
Thanks for your help
Mhh, getting a little more complicated.
Your BL is ok...
What do you see in CWM when you go into Mounts and Storage? What is mounted?
The recovery logs are under Advanced > show logs.
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
yasyas said:
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
Click to expand...
Click to collapse
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
sbdags said:
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
Click to expand...
Click to collapse
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
yasyas said:
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
Click to expand...
Click to collapse
To be in the safe side, yes, that is what I would do. TWTRP 2.7.+ takes a long time to format and it may seem the process got stuck. Give it at least 90 minutes to finish.
Then reflash CROMBi
I'm back up and running !!!
This time installing TWRP, everything was mounted (maybe my previous flash before CWMR wasn't good), did a format data, waited until it was done, flashed latest Crombi-KK and going through setup now. Hopefully won't have the same UID issue on next shutdown. I didn't enable fsync or journaling so hopefully it won't happen again.
Thanks both of you for your help!
Good deal! Happy for you!
Rooting google pixel zl
hey guys, I have moto g xt1033 after installing cm13 i stuck in boot loop cm13 logo..please help me out
please..i dont wanna loose my phone.
you sure it's a boot loop? I just installed mine on a GS Tab and noticed a significant amount of time for booting, which I thought was a loop also, which took much longer than usual.
Try booting into recovery mode and see if there are any error messages that will show
Do you have any kind of custom recovery?
We need more info about your device.
chacky13200 said:
Do you have any kind of custom recovery?
We need more info about your device.
Click to expand...
Click to collapse
yeah i have twrp custom recovery, toady i have wiped my cell and now my device says os is not install,
and my device is working on "fastboot device" but does not works on "adb devices" help me and thank you for reply
Abhishek_singh said:
yeah i have twrp custom recovery, toady i have wiped my cell and now my device says os is not install,
and my device is working on "fastboot device" but does not works on "adb devices" help me and thank you for reply
Click to expand...
Click to collapse
TWRP is still working?
user822 said:
TWRP is still working?
Click to expand...
Click to collapse
yeah recovery shows twrp v2.8.0.6....how may i know is that working or not??
Abhishek_singh said:
yeah recovery shows twrp v2.8.0.6....how may i know is that working or not??
Click to expand...
Click to collapse
Then you are all set.
In the wipe menu, wipe /system and /data and /cache (this will nuke your data) to get rid of all leftovers that might have caused the bootloop.
Plug it into a PC, copy Cyanogenmod over (this time verify the sha1sum, against the one on the download website, to make sure the download is correct and did not cause the bootloop)
Install Cyanogenmod, without Gapps for the first test
Bootloop should be gone
If the bootloop happens again, you might need a newer version of TWRP, but 2.8.x.x should do the job.
user822 said:
Then you are all set.
In the wipe menu, wipe /system and /data and /cache (this will nuke your data) to get rid of all leftovers that might have caused the bootloop.
Plug it into a PC, copy Cyanogenmod over (this time verify the sha1sum, against the one on the download website, to make sure the download is correct and did not cause the bootloop)
Install Cyanogenmod, without Gapps for the first test
Bootloop should be gone
If the bootloop happens again, you might need a newer version of TWRP, but 2.8.x.x should do the job.
Click to expand...
Click to collapse
Thank you bro thank you so much....:good::good:
hey I am still facing "adb devices" problem what can i do?
user822 said:
Then you are all set.
In the wipe menu, wipe /system and /data and /cache (this will nuke your data) to get rid of all leftovers that might have caused the bootloop.
Plug it into a PC, copy Cyanogenmod over (this time verify the sha1sum, against the one on the download website, to make sure the download is correct and did not cause the bootloop)
Install Cyanogenmod, without Gapps for the first test
Bootloop should be gone
If the bootloop happens again, you might need a newer version of TWRP, but 2.8.x.x should do the job.
Click to expand...
Click to collapse
on my moto g xt1033,
after, installing ROM CM-13.0-20160820-SNAPSHOT-ZNH5YAO0J1-falcon
Then i, installed Gapps = ARM_6.0_micro (opengapps.org)
then everything is fine play games, etc.
i installed super su from play store, but unable to update binary!
so boot into recovery and flash UPDATE-SuperSU-v2.46.zip
now i stuck in boot loop,
(Earlier Point)now what to do?> and after installation of rom twrp asking me for partition modification- Keep Read-Only OR Allow Modification. i select allow modification. so where i go wrong?
NOw stuck in boot loop, i can able to in Fastboot and select recovery also,
so what do i do, option 1-> wipe everything n install rom , gapps again.
option2-> without wiping install rom (like doing overwrite) on already installed rom.
and also suggest how to ROOT? which superSU.zip i flash on cm13
I have TWRP 3.0.2-0 version working fine.
OK, so I've got the original shield tablet. I have lost root, and whenever I try to boot to recovery, the system attempts, goes to a black screen, then proceeds to normal system boot. Environment:
stock 6.0
non-rooted (not since updating to 6.0)
shield version 4.0
build MRA58K.41524_664.1902
previously had TWRP
I understand loss of root/recovery w/that last update is normal. However, I've tried:
flashing the new TWRP via fastboot w/o success (3.0.2)
flashing the rooted boot img w/o success
even flashing the stock recovery w/o success
ADB & fastboot commands chug happily along, & I'm left with the same behavior. Flashing the stock recovery actually gave me the dead android at the recovery screen (was this b/c I flashed the one for 4.0.1 & I need the one for 4.0?). So, what's my next move here?
Aaaaaaannnnnd.... I've also completely lost my WiFi. Says that it's on, but it's got the slash through it in quick settings & doesn't find any networks.
t-readyroc said:
OK, so I've got the original shield tablet. I have lost root, and whenever I try to boot to recovery, the system attempts, goes to a black screen, then proceeds to normal system boot. Environment:
stock 6.0
non-rooted (not since updating to 6.0)
shield version 4.0
build MRA58K.41524_664.1902
previously had TWRP
I understand loss of root/recovery w/that last update is normal. However, I've tried:
flashing the new TWRP via fastboot w/o success (3.0.2)
flashing the rooted boot img w/o success
even flashing the stock recovery w/o success
ADB & fastboot commands chug happily along, & I'm left with the same behavior. Flashing the stock recovery actually gave me the dead android at the recovery screen (was this b/c I flashed the one for 4.0.1 & I need the one for 4.0?). So, what's my next move here?
Click to expand...
Click to collapse
1) the twrp you linked to is for lollipop, states that in the notes section half way down the page.
2) to get root with this method you also have to install phh superuser
3) that dead Android IS the stock recovery
Now for help: flash this recovery(there are two here read and find the one for MM)
https://r.tapatalk.com/shareLink?ur...share_tid=2877117&share_fid=3793&share_type=t
[RECOVERY] [unofficial] TWRP 3.0.2-0 (2.8.7.1 for Lollipop) [2016-04-05]
Sent from my SHIELD Tablet K1 using Tapatalk
Thanks Exile. I've got TWRP installed ok now, but it doesn't seem to be able to wipe anything - just kinda hangs there (trying to wipe dalvik & cache - just sits at "formatting cache using make_ext4fs"). It's also weirdly unresponsive with UI lag on button presses; not sure if that's a known thing. I'm assuming that the "E: Failed to mount decrypted adopted storage device" is in reference to my external SD card.
I also still don't have my WiFi. I've grabbed the WiFi full OTA from this post & adb pushed it. TWRP was able to successfully flash it, but then couldn't do the ensuing dalvik/cache wipe. I let it sit for a good 10mins just to see if it would finish, but it still sat at the same point. Force power-cycling booted it into the new 4.1/6.0.1 version, and I do have my WiFi back
So, how to get root back? Can I just flash the SU 2.65 I have from TWRP? Or do I have to flash the rooted boot img again? I do already have the Superuser app installed...
t-readyroc said:
Thanks Exile. I've got TWRP installed ok now, but it doesn't seem to be able to wipe anything - just kinda hangs there (trying to wipe dalvik & cache - just sits at "formatting cache using make_ext4fs"). It's also weirdly unresponsive with UI lag on button presses; not sure if that's a known thing. I'm assuming that the "E: Failed to mount decrypted adopted storage device" is in reference to my external SD card.
I also still don't have my WiFi. I've grabbed the WiFi full OTA from this post & adb pushed it. TWRP was able to successfully flash it, but then couldn't do the ensuing dalvik/cache wipe. I let it sit for a good 10mins just to see if it would finish, but it still sat at the same point. Force power-cycling booted it into the new 4.1/6.0.1 version, and I do have my WiFi back
So, how to get root back? Can I just flash the SU 2.65 I have from TWRP? Or do I have to flash the rooted boot img again? I do already have the Superuser app installed...
Click to expand...
Click to collapse
Ok, from here just flash the supersu.zip and you should be good. I can't remember if 2.65 works or not but I know you can find a copy of 2.71. someone else has a problem with 2.72 so it may or may not work.
As for twrp it has touch screen lag issues, I don't think any of the mm compatible versions have been able to fully fix this. I've had the same problem with dalvik cache and cache wipe, it is slow as molasses but will complete eventually. Once you have root I would suggest using a program called flashfire to flash zips and do things like cache wipe. It works like a charm.
https://r.tapatalk.com/shareLink?ur...share_tid=3075433&share_fid=3793&share_type=t
[Android 4.2+][ROOT][2016.05.11] FlashFire v0.33 - Play BETA
Sent from my SHIELD Tablet K1 using Tapatalk
Thanks again, Exile. I actually had to re-flash TWRP, oddly, but after some searching, I found a mirror for su2.71, & adb pushed it. Once I had TWRP back in order, I was able to then flash it & my root is back together.
Glad you got it working. Have fun and be safe
Sent from my SHIELD Tablet K1 using Tapatalk
Goodmorning everyone
I have a problem on my TF300TG which I picked up from my drawer after a while
I upgraded to 7.1 nougat following the instructions given in the letter (very clear) but now my tablet does not start the system, I explain better:
it turns on and the writing unlock remains The device is unlocked with the ASUS logo in the Center but does not start.
I can go back to recover twrp at any time and reflect what I have repeated several times even with different versions but I always have the same problem.
I can also re-revise the original flash blob and start again
Giangi_TF300TG said:
I upgraded to 7.1 nougat following the instructions given in the letter (very clear) but now my tablet does not start the system, I explain better:
it turns on and the writing unlock remains The device is unlocked with the ASUS logo in the Center but does not start.
I can go back to recover twrp at any time.
Click to expand...
Click to collapse
First of all format data through Kang TWRP recovery. It may take until one hour. Be patient. Let it run. After that install rom, SUSuperuser and pico Gapps in one run.
Not boot again
ebonit said:
First of all format data through Kang TWRP recovery. It may take until one hour. Be patient. Let it run. After that install rom, SUSuperuser and pico Gapps in one run.
Click to expand...
Click to collapse
I just finished the procedure that you suggested that it did not return me errors but does not boot.
just restarted of the recovery mode updates the twrp restarts and remains nailed on the Asus screen if I want I can restart in recovery.
Any other suggestions?
Giangi_TF300TG said:
I just finished the procedure that you suggested that it did not return me errors but does not boot.
just restarted of the recovery mode updates the twrp restarts and remains nailed on the Asus screen if I want I can restart in recovery.
Any other suggestions?
Click to expand...
Click to collapse
Yes, you should do carefully a Buster99: https://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
This procedure brings you back on a clean stock rom Android 4.2 Jelly Bean. Then you have to flash Kang TWRP firstly.
PS: Attention! If you restart in recovery with the 3 icons, never touch the third one in order to "Wipe Data". It bricks your device!
ebonit said:
Yes, you should do carefully a Buster99: https://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
This procedure brings you back on a clean stock rom Android 4.2 Jelly Bean. Then you have to flash Kang TWRP firstly.
PS: Attention! If you restart in recovery with the 3 icons, never touch the third one in order to "Wipe Data". It bricks your device!
Click to expand...
Click to collapse
The factory reset has been done correctly the system has restarted correctly after reinserting the nougant yet the system does not boot the only thing that has changed and that now reboots into the loop by returning to the asus screen repeatedly
Giangi_TF300TG said:
The factory reset has been done correctly the system has restarted correctly after reinserting the nougant yet the system does not boot the only thing that has changed and that now reboots into the loop by returning to the asus screen repeatedly
Click to expand...
Click to collapse
It seems there has been a big misunderstanding by you. I advised to format data through Kang TWRP, but you did a factory reset, didn't you?.
Too many people mix up wipes and formats. Format only data means, not factory reset, not wipe - you format it ext4, then convert it to f2fs. Formatting in Kang TWRP takes until 1 hour. If it went faster you did not format. Kang TWRP does a deep format that rewrites everything in the partition. No moldy leftovers.
Now your device is in a boot loop, but not bricked. So doing a Buster99 is the only way to solve the problem. If you need help with fastboot, head over to the General section. Download and install "Minimal ADB and Fastboot" on your PC.
ebonit said:
It seems there has been a big misunderstanding by you. I advised to format data through Kang TWRP, but you did a factory reset, didn't you?.
Too many people mix up wipes and formats. Format only data means, not factory reset, not wipe - you format it ext4, then convert it to f2fs. Formatting in Kang TWRP takes until 1 hour. If it went faster you did not format. Kang TWRP does a deep format that rewrites everything in the partition. No moldy leftovers.
Now your device is in a boot loop, but not bricked. So doing a Buster99 is the only way to solve the problem. If you need help with fastboot, head over to the General section. Download and install "Minimal ADB and Fastboot" on your PC.
Click to expand...
Click to collapse
Excuse me surely I did not understand here now I follow your advice step by step.
Now I'm running a buster99 but I don't need ADB, I already have a fastboot working.
PS that is I'm starting fastboot not from adb but from a folder on my pc that is executing the buster commands
Then what do I reinsert the right Kang bootloader?
Excuse my ignorance
Giangi_TF300TG said:
Excuse me surely I did not understand here now I follow your advice step by step.
Now I'm running a buster99 but I don't need ADB, I already have a fastboot working.
PS that is I'm starting fastboot not from adb but from a folder on my pc that is executing the buster commands
Then what do I reinsert the right Kang bootloader?
Excuse my ignorance
Click to expand...
Click to collapse
Now my system is restarted with the original rom I reinsert twrp_tf300t_kang_2.8.7.2.img,
after how do I proceed?
Giangi_TF300TG said:
Now my system is restarted with the original rom I reinsert twrp_tf300t_kang_2.8.7.2.img,
after how do I proceed?
Click to expand...
Click to collapse
Congratulations, good job!
Please look here: https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479
ebonit said:
Congratulations, good job!
Please look here: https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479
Click to expand...
Click to collapse
I have already inserted this twrp tf300t kang 2.8.7.2.img, through fastboot do I have to do it with the linux procedure?
the system now has boot recovery and starts normally with the old system.
Now that I do I have to delete the given partition or do I flash the three roms?
Giangi_TF300TG said:
I have already inserted this twrp tf300t kang 2.8.7.2.img, through fastboot do I have to do it with the linux procedure?
the system now has boot recovery and starts normally with the old system. What does old system mean?
Click to expand...
Click to collapse
I'm sorry, but it is not easy to understand what you did. As far as I know your device is on stock rom Android 4.2 Jelly Bean. Correct?
The next step should be to flash (not insert!) "twrp_tf300t_kang_2.8.7.2_signed.zip" via fastboot. The command is: "fastboot -i 0x0B05 flash recovery foo.img". Replace foo.img with the recovery image name! Did you?
If yes, you may start the device into recovery. Kang TWRP should start. After that install through TWRP Nougatella #39, pico Gapps and Super SU from the external memory of your device in one run. That's it!
Please pay attention you did download the newest versions in post #1: https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 !
ebonit said:
I'm sorry, but it is not easy to understand what you did. As far as I know your device is on stock rom Android 4.2 Jelly Bean. Correct?
The next step should be to flash (not insert!) "twrp_tf300t_kang_2.8.7.2_signed.zip" via fastboot. The command is: "fastboot -i 0x0B05 flash recovery foo.img". Replace foo.img with the recovery image name! Did you?
If yes, you may start the device into recovery. Kang TWRP should start. After that install through TWRP Nougatella #39, pico Gapps and Super SU from the external memory of your device in one run. That's it!
Please pay attention you did download the newest versions in post #1: https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 !
Click to expand...
Click to collapse
Sorry I'm using google translate
So far I have flashed the recovery twrp_tf300t_kang_2.8.7.2.img.
I restarted in recovery mod TWRP and I installed the 3 zip in sequence through sd card
KatKiss-7.1_TF300T_039.zip, open_gapps-arm-7.1-pico-20200325.zip, SuperSU-v2.82-201705271822.zip all OK
I ran Wipe cache / dalvik
I restarted
performed a first start where the bar under ASUS quickly colored blue
It has restarted
but later stuck on ASUS. I don't know where I'm wrong
From the fact that you have not replied to my last message, I think we have given up.
Just one thing I'm curious to know are there versions of this Tablet with different hardware or different firmware (bios) you can update? I don't know I thought even if I had to have a rom already cooked and functioning on an equal tablet I could shoot it in a single flash
Giangi_TF300TG said:
Sorry I'm using google translate
I don't know where I'm wrong
Click to expand...
Click to collapse
I'm sorry, but I also don't know where have been wrong? How should I reply after so less information about the situation. There are many different possibilities.
Hopefully you have a backup of the system through TWRP after finishing the Buster99. If so, please start the TWRP recovery and restore the backup.
Search here for "TF300TG": https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702
ebonit said:
I'm sorry, but I also don't know where have been wrong? How should I reply after so less information about the situation. There are many different possibilities.
Hopefully you have a backup of the system through TWRP after finishing the Buster99. If so, please start the TWRP recovery and restore the backup.
Search here for "TF300TG": https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702
Click to expand...
Click to collapse
Sorry but once done the Buster99 procedure I don't need to do a restore of the Backup since the tablet restarts regularly with the original system I didn't perform any backup I didn't need it