Related
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Rojikku said:
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Click to expand...
Click to collapse
First I use usb 2.0 as I have no 3.0 ports and have no problems (just for info).
The 4.2 update changed the bootloader menu. Now when you enter the menu if you do nothing it will automatically enter fastboot - watch the upper left for a message. You will need usb debugging. I suggest leaving it turned on as you never know when there will be an issue and you can't get into the os to turn it on.
Good Luck!
Rojikku said:
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Click to expand...
Click to collapse
You lost your version of Cwm when you flashed the official update.
You will need to find the version of TWRP that is posted on here that has been modified to work with new bootloader and flash it thru fastboot.
tobdaryl said:
First I use usb 2.0 as I have no 3.0 ports and have no problems (just for info).
The 4.2 update changed the bootloader menu. Now when you enter the menu if you do nothing it will automatically enter fastboot - watch the upper left for a message. You will need usb debugging. I suggest leaving it turned on as you never know when there will be an issue and you can't get into the os to turn it on.
Good Luck!
Click to expand...
Click to collapse
Thanks! That was INCREDIBLY helpful. I noticed that message but I didn't know what it meant. Funny the solution was so obvious...
flumpster said:
You lost your version of Cwm when you flashed the official update.
You will need to find the version of TWRP that is posted on here that has been modified to work with new bootloader and flash it thru fastboot.
Click to expand...
Click to collapse
Alright, thanks. I have no idea how that works, but if that's what I need to do to fix it whatever. xD
Rojikku said:
Thanks! That was INCREDIBLY helpful. I noticed that message but I didn't know what it meant. Funny the solution was so obvious...
Alright, thanks. I have no idea how that works, but if that's what I need to do to fix it whatever. xD
Click to expand...
Click to collapse
The twrp mentioned above can be found here.
tobdaryl said:
The twrp mentioned above can be found here.[/URL]
Click to expand...
Click to collapse
Thanks... I actually installed openrecovery-twrp-2.2.2.0-tf300t-JB.blob
On that note, I get a password prompt every time I boot into it. I read somewhere wiping and reinstalling helped with that, but even after wiping everything with every button I had I could still boot and everything was there...
And since APPARENTLY my internal storage isn't good enough, I can't install a 4.2.2 ROM(I'm still debating what ROM I will end up using.) I can't find anything in TWRP...
EDIT: To clarify, I can't find anything under / or /sdcard where I would normally find stuff.
Rojikku said:
Thanks... I actually installed openrecovery-twrp-2.2.2.0-tf300t-JB.blob
On that note, I get a password prompt every time I boot into it. I read somewhere wiping and reinstalling helped with that, but even after wiping everything with every button I had I could still boot and everything was there...
And since APPARENTLY my internal storage isn't good enough, I can't install a 4.2.2 ROM(I'm still debating what ROM I will end up using.) I can't find anything in TWRP...
EDIT: To clarify, I can't find anything under / or /sdcard where I would normally find stuff.
Click to expand...
Click to collapse
Wrong twrp! You need openrecovery-twrp-2.4.4.0-tf300t-4.2.blob until you are off stock 4.2 then you need openrecovery-twrp-2.4.4.0-tf300t-JB.blob. Unless the rom you flash is also for 4.2 bootloader. Both are located at teamwin.
4.2 changes directories in your sdcard for multi-user operation. Look under the 0 directory in /sdcard/0.
The password is for encryption that 4.2 uses to provide multi-user. The /sdcard allows total freedom under normal roms(even without root) but to stop user interaction 4.2 encrypts for user restriction. The first user gets directory 0 and so on.
Flash the proper twrp for 4.2 stock.
As far as flashing a new rom look at the op and determine if it is for the new stock 4.2 bootloader. If not do not flash over 4.2 but downgrade first. I have upgraded from 10.4.2.20 to stock 4.2 and downgraded from stock 4.2 to 10.4.2.20 several times without issue.
Stock 4.2 includes an assert to only allow upgrade from 10.4.2.20.
tobdaryl said:
Wrong twrp! [/URL]You need openrecovery-twrp-2.4.4.0-tf300t-4.2.blob until you are off 4.2 then you need openrecovery-twrp-2.4.4.0-tf300t-JB.blob. Both are located at teamwin.[/URL]
4.2 changes directories in your sdcard for multi-user operation. Look under the 0 directory in /sdcard/0.
The password is for encryption that 4.2 uses to provide multi-user. The /sdcard allows total freedom under normal roms(even without root) but to stop user interaction 4.2 encrypts for user restriction. The first user gets directory 0 and so on.
Flash the proper twrp for 4.2 stock and hold a minute or you are going right back where you were or worse. You need slightly more info before going forward and I need to check my notes while you get the proper twrp flashed.
Click to expand...
Click to collapse
Yeah, I really don't know that much about all this. I'd basically barely used android before I got this tablet a couple days ago, so I only have two days worth of experience...and I didn't get to use it a horribly large amount.
You seem like you're going to help a lot though, so thanks in advance. xD I'll get to flashing that twrp.
Rojikku said:
Yeah, I really don't know that much about all this. I'd basically barely used android before I got this tablet a couple days ago, so I only have two days worth of experience...and I didn't get to use it a horribly large amount.
You seem like you're going to help a lot though, so thanks in advance. xD I'll get to flashing that twrp.
Click to expand...
Click to collapse
I'll try but this new stock 4.2 is a new animal with many changes and we are just learning.
tobdaryl said:
I'll try but this new stock 4.2 is a new animal with many changes and we are just learning.
Click to expand...
Click to collapse
It actually was stock 4.1.1 >>; I just upgraded it. WHICH APPARENTLY WAS A HORRID DECISION. Regardless, I'm trying to install my twrp.img file, ran the command, and it's been writing for like ten minutes... 7672KB. I'm not certain if it's still writing or not...but it claims to be.
Rojikku said:
It actually was stock 4.1.1 >>; I just upgraded it. WHICH APPARENTLY WAS A HORRID DECISION. Regardless, I'm trying to install my twrp.img file, ran the command, and it's been writing for like ten minutes... 7672KB. I'm not certain if it's still writing or not...but it claims to be.
Click to expand...
Click to collapse
OK. Sometimes it takes seconds and sometimes longer. When you upgraded you used 4.2 (10.6.1.8)?
tobdaryl said:
OK. Sometimes it takes seconds and sometimes longer. When you upgraded you used 4.2 (10.6.1.8)?
Click to expand...
Click to collapse
Uhm. First. ****. It was frozen, so I canceled it and restarted it(Been a good twenty minutes doing nothing). Is it safe to reboot my tablet? I can't restart it, fastboot crashes. >>; Restart? Leave it? What?
I decided to take the risk and reboot it. Everything fine. I flashed the tool, ran the reboot command(Which actually didn't work... >>; But I rebooted it manually and it seems fine...)
On that note, is it actually possible to destroy a device beyond repair accidentally? And the TWRP tool said it flashed fine but I still have the old version. Odd....
I do have the image you said currently installed, I checked the version against my download.
Rojikku said:
Uhm. First. ****. It was frozen, so I canceled it and restarted it(Been a good twenty minutes doing nothing). Is it safe to reboot my tablet? I can't restart it, fastboot crashes. >>; Restart? Leave it? What?
Click to expand...
Click to collapse
I'm not sure where you are reading the above. Tell me your current situation and what rom you were on when you began this flash.
tobdaryl said:
I'm not sure where you are reading the above. Tell me your current situation and what rom you were on when you began this flash.
Click to expand...
Click to collapse
I originally flashed the ROM image of TF300T_US_epaduser_10_6_1_8_SDupdate, and I can still boot into that fine. I tried to install the RCK tool you recommended, but it froze. I did a ctrl+c, and then coldbooted the tablet. I tried to do it again, said it was fine, nothing happened. So I think "Maybe I need to boot into the OS and retry it after rebooting from there." So I do that, and now the recovery is frozen again. my command is fastboot -i 0x0b05 flash recovery twrp.img.
That the info you needed?
Rojikku said:
I originally flashed the ROM image of TF300T_US_epaduser_10_6_1_8_SDupdate, and I can still boot into that fine. I tried to install the RCK tool you recommended, but it froze. I did a ctrl+c, and then coldbooted the tablet. I tried to do it again, said it was fine, nothing happened. So I think "Maybe I need to boot into the OS and retry it after rebooting from there." So I do that, and now the recovery is frozen again. my command is fastboot -i 0x0b05 flash recovery twrp.img.
That the info you needed?
Click to expand...
Click to collapse
Go back and check my previous post with the links for twrp, I specified use of blob files. Either should work but some units seem to have an issue with img files. Also check that you have usb debugging turned on in developer options.
tobdaryl said:
Go back and check my previous post with the links for twrp, I specified use of blob files. Either should work but some units seem to have an issue with img files. Also check that you have usb debugging turned on in developer options.
Click to expand...
Click to collapse
I downloaded the .blob version now. That one worked fine. I guess it either didn't like the .img or my download was a bit corrupt.
I now have TWRP version 2.4.4.0.It still wants a password I never set though. I was just finishing making sure it actually worked as you posted.
Rojikku said:
I downloaded the .blob version now. That one worked fine. I guess it either didn't like the .img or my download was a bit corrupt.
I now have TWRP version 2.4.4.0.It still wants a password I never set though. I was just finishing making sure it actually worked as you posted.
Click to expand...
Click to collapse
When it asks for the password hit cancel and just ignore the error.
tobdaryl said:
When it asks for the password hit cancel and just ignore the error.
Click to expand...
Click to collapse
Okay. THEN what do I do? It doesn't seem to detect an OS even though I can boot into one. I can't find my ROM.zip in there and I'm not sure what to do from there... If I could find the ROM I would be fine, possibly. I'm trying to flash this one http://fitsnugly.euroskank.com/?rom=cm10&device=tf300t just to see if it works right. (I want it to show my dock's battery and have the overclocking menu in that drag-up interface.)
Rojikku said:
Okay. THEN what do I do? It doesn't seem to detect an OS even though I can boot into one. I can't find my ROM.zip in there and I'm not sure what to do from there... If I could find the ROM I would be fine, possibly. I'm trying to flash this one http://fitsnugly.euroskank.com/?rom=cm10&device=tf300t just to see if it works right. (I want it to show my dock's battery and have the overclocking menu in that drag-up interface.)
Click to expand...
Click to collapse
Thanks for the link. I looked at the info provided for that rom. You don't want to flash that over an encrypted tablet which you now have. The only safe way I have found to go to or from stock 4.2 rom is with stock 10.4.2.20.
To do that you would flash 10.4.2.20 with twrp, boot into os, reboot back to the bootloader which will now be four icons, select usb, use fastboot to flash twrp again, and now flash your new rom.
This sounds long but removes encryption from your tablet and you should be able to flash the jb rom of choice that does not require stock 4.2 bootloader.
Greetings!
I'd like to present a TWRP recovery for the Xperia X Compact. This release should work on Xperia X single and dual-SIM variant of the device. I am an owner of Xperia X, but some users reported that my recovery works just fine on its smaller brother.
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-kugo-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds, you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee
it works perfectly! well can't say I tried all functions yet, but it certainly seems so.
thank you so much. finally a proper lastest version of twrp for XC that supports encryption on nougat.
btw. you have to flash it over fotakernel as described in OP. (hotbooting did not work. blank screen.)
I did try other regular X twrp versions with the same result in the past in hopes of finding something better, so the issue was likely the same since I hotbooted them too for a fast test. I guess that's what you get for being lazy. doh.
thanks again for posting it here.
/tuxen
Thank you for sharing.
thanks
Thanks for sharing brother
Working ⚒ perfectly on stock 7.0
no problem
Perfect, thanks. Only annoyance is that I can only reboot the system or power off now.
XperienceD said:
Perfect, thanks. Only annoyance is that I can only reboot the system or power off now.
Click to expand...
Click to collapse
That shouldn't work anyway. I can enable these flags if you want.
eagleeyetom said:
That shouldn't work anyway. I can enable these flags if you want.
Click to expand...
Click to collapse
For all I use the other options there's no need to go out of your way, but if you do make another for whatever reason having the options would be nice.
XperienceD said:
For all I use the other options there's no need to go out of your way, but if you do make another for whatever reason having the options would be nice.
Click to expand...
Click to collapse
It didn't work for me on X. I can enable them in the next version.
realtuxen said:
it works perfectly! well can't say I tried all functions yet, but it certainly seems so.
thank you so much. finally a proper lastest version of twrp for XC that supports encryption on nougat.
btw. you have to flash it over fotakernel as described in OP. (hotbooting did not work. blank screen.)
I did try other regular X twrp versions with the same result in the past in hopes of finding something better, so the issue was likely the same since I hotbooted them too for a fast test. I guess that's what you get for being lazy. doh.
thanks again for posting it here.
/tuxen
Click to expand...
Click to collapse
What do you mean by hot booting? I did this to boot to twrp without installing and have no problem
Code:
fastboot boot twrp.img
Thanks for the twrp, with this I can make full backup before trying to update to 7.1 or 8.0 later :good:
MTP is not working in this version. Everything else is top notch, will test backup/restore a bit later and report back.
trewelu said:
What do you mean by hot booting? I did this to boot to twrp without installing and have no problem
Code:
fastboot boot twrp.img
Thanks for the twrp, with this I can make full backup before trying to update to 7.1 or 8.0 later :good:
Click to expand...
Click to collapse
Exactly. I know hotbooting is not the best description, but you understood anyway.
Strange, I am not a flashophile so I usually just booted twrp this way after a upgrade with flashtool. When the phone was connected to the pc anyway.
But it only works for me with the androplus version, oshmoun's version won't boot that way either. It's not the first time I have talked odd twrp behaviour though, as another guy could not get the androplus one to work at all. I have no reason to doubt him, as this is pretty casual stuff.
I see you are still on MM, I have been on N since it came out and if I remember correctly I backed up ta just before N came out (exploit and N came out very close to each other), took the ota, and unlocked BL. So I performed all the 'fastboots' (better word? heh) on that and 7.1.1. Perhaps the bootloader changed someway? I have no idea.
Edit: if I learned to read properly the first time, you are NOT on MM (doh) but 7.0. Sorry and even more strange. Does MTP work for you? (see below)
---------- Post added at 20:00 ---------- Previous post was at 19:58 ----------
kekistaneerefugee said:
MTP is not working in this version. Everything else is top notch, will test backup/restore a bit later and report back.
Click to expand...
Click to collapse
MTP works absolutely fine here..
This version uses Sony init, so you can see the Sony screen and led indicator while entering the recovery mode. I'm not planning to change it before creating an official TWRP.
eagleeyetom said:
This version uses Sony init, so you can see the Sony screen and led indicator while entering the recovery mode. I'm not planning to change it before creating an official TWRP.
Click to expand...
Click to collapse
Is this in response to something functional, or just general cosmetics info? Doesn't the sony screen origin from the bootloader? How should a official twrp look while booting it? I get the sony boot and led then the TWRP boot image, isn't that normal when booting fotakernel replaced by TWRP? ie. the bootloader handles it when turning the phone on while holding vol down.
An official version would sure be nice. I more than appreciate what you already done. So just take your time.
realtuxen said:
But it only works for me with the androplus version, oshmoun's version won't boot that way either. It's not the first time I have talked odd twrp behaviour though, as another guy could not get the androplus one to work at all. I have no reason to doubt him, as this is pretty casual stuff.
Edit: if I learned to read properly the first time, you are NOT on MM (doh) but 7.0. Sorry and even more strange. Does MTP work for you? (see below)
Click to expand...
Click to collapse
Strange, I don't have problem booting twrp without installing for either of twrp.
I'm on 7.0. I tried to update to 7.1, but I don't get signal if I do the ta_poc + tobias drm fix method, and the drm is still marked as broken.
I really hate mtp and avoid it. I don't think I even have mtp working properly on my pc. I can't help you test that one. Sorry.
trewelu said:
Strange, I don't have problem booting twrp without installing for either of twrp.
I'm on 7.0. I tried to update to 7.1, but I don't get signal if I do the ta_poc + tobias drm fix method, and the drm is still marked as broken.
Click to expand...
Click to collapse
Why are you running it through both ta_poc and Tobias rootkernel with drm fix?
Either you use ta_poc to mount your ta backup from before the bootloader was unlocked thereby bringing the whole trim area back including drm.
Or you use Tobias rootkernel to fix or 'emulate" drm.
Both tools can disable dm verity, sony ric, etc. there is no reason (other than likely creating trouble) to run the kernel image though both tools?!
If you for example run a boot.img with drm fix through ta_poc it will remove the drm fix first. So I imagine things could go wrong of you apply drm fix again (if that is what you're doing) after using ta_poc.
I really hate mtp and avoid it. I don't think I even have mtp working properly on my pc. I can't help you test that one. Sorry.
Click to expand...
Click to collapse
Lol I hate it general too, it can come in handy when only twrp is booted though. I am not sure I have any drivers installed either. Regardless I can access a drive resembling my phone labeled 'mtp device' in 'my computer' when I boot twrp.
Edit: sorry for sidetracking the thread a bit.
eagleeyetom said:
NEEDS TESTING
USB-OTG
Click to expand...
Click to collapse
Thanks! and i can confirm that USB OTG works well.
Working on Sony Nougat
This is the only TWRP I can decrypt my data with on Sony Nougat Stock ROM, Thanks !
realtuxen said:
Both tools can disable dm verity, sony ric, etc. there is no reason (other than likely creating trouble) to run the kernel image though both tools?!
Click to expand...
Click to collapse
Using both tools stems from users reporting they had to to get Magisk to work.
XperienceD said:
Using both tools stems from users reporting they had to to get Magisk to work.
Click to expand...
Click to collapse
There was an info in one of threads, that you should get the stock kernel first through TA_POC and then through kernel repack tool. If you did not, it would work, but occassionally reboots. I am now on 7.1.1 build 206 with Genesis Kernel 1.05 (no_DRM patch version) and it works ok.
As for TWRP, thanks for this! It works ok. Can not fastboot it, must be flashed in recovery parition, but no deal for me. Only thing that I wonder, there are options to backup system, data etc, but not Internal SD (/data/data). Why?
Hi I have a question, I have N 7.1.1, and i want to root it, so i need the twrp, if I flash this twrp, its okay? Ty!
Hello,
i have a TF700KL, and i want to flash it.
But i don't find Something about it. Only about TF700.
Can You Help me?
Warm regards
Please Guys, i want help... Please...
Thx for ignore me
TF700 & TF700KL same, KL is the last version and the one listed on Asus's Global Website. All files should work once you A) Update firmware to the latest version B) Unlock bootloader. - NP
I did update it to Version VF_V5.0.4.17 but still can't manage to make the unlock app to get installed.
hard resetted3 times also with no GMAIL account, but still nothing
please help me
Donnie87 said:
I did update it to Version VF_V5.0.4.17 but still can't manage to make the unlock app to get installed.
hard resetted3 times also with no GMAIL account, but still nothing
please help me
Click to expand...
Click to collapse
Took me a few minutes to find it and a few hoops to jump through to extract the archive, but the official apk is still out there. Try to install this:
https://www.androidfilehost.com/?fid=5862345805528055095
AMAZING I MANAGED!!! THANK YOU BROOOOOOOOOOOOOOOOOOOOOOOOOOOO
how can I now install a custom rom? I'd just like to have the original one but faster....
and of coruse no I don't want to lose the 4g support
---------- Post added at 02:42 PM ---------- Previous post was at 02:03 PM ----------
I tried to reboot but even if it's unlocked, I have no bootloader. it still remain with the screen normal version
Donnie87 said:
AMAZING I MANAGED!!! THANK YOU BROOOOOOOOOOOOOOOOOOOOOOOOOOOO
how can I now install a custom rom? I'd just like to have the original one but faster....
and of coruse no I don't want to lose the 4g support
---------- Post added at 02:42 PM ---------- Previous post was at 02:03 PM ----------
I tried to reboot but even if it's unlocked, I have no bootloader. it still remain with the screen normal version
Click to expand...
Click to collapse
You are welcome.
Rest assured you do have a bootloader. You may not have the bootloader interface the other Transformers have and possibly there is no way to get fastboot to work on this thing - I don't know.
There is no custom rom for this tablet, and if you do not want to loose 4G you cannot use one made for another Transformer either (no idea if that is even possible, I do not know the KL).
Your best bet is to gain root and uninstall a bunch of cr**, maybe use Greenify - I don't know. Very limited what you can do on stock....
I seem to recall that people got root with Framaroot on this thing. Google it, the info is out there. If I can find it so can you
berndblb said:
You are welcome.
Rest assured you do have a bootloader. You may not have the bootloader interface the other Transformers have and possibly there is no way to get fastboot to work on this thing - I don't know.
There is no custom rom for this tablet, and if you do not want to loose 4G you cannot use one made for another Transformer either (no idea if that is even possible, I do not know the KL).
Your best bet is to gain root and uninstall a bunch of cr**, maybe use Greenify - I don't know. Very limited what you can do on stock....
I seem to recall that people got root with Framaroot on this thing. Google it, the info is out there. If I can find it so can you
Click to expand...
Click to collapse
ok let me get to the keypoints here that made me ask for help, and so you'll see that i'm not just a lazy person that doesn't use google
1) Some people they say that the KL can accept all the roms of the Tf700T. for example katkiss is saying to use one of their roms
1.a) some say that it will brick the device.
so, first question here, what will happen if i'll get a custom rom of the TF700T?
2) some people say that I should have a version of the "unlock bootloder" after unlocking with the asus app.
Well I don't have anything, I just have a small phrase which is "device unlocked" and that's it. nothing else.
3) some say on google that there is a cyanogen mod for the KL. Unfortunately cyanogenmod wiki and forum are down, so I can't find either assistance, either the files.
nothing to do here, then.
4) let's say I'll follow your guide, and i'll flash a custom rom. will I lose the 4g?
4.a) how can I get to the old rom, even original, in order to get 4g back?
5) about root: i managed to root it a long time ago. Unfortunately, even disabling most of the package and all the bloatware, the device really sucks.
that's the main reason why I abandoned there 3 years ago. now it's full of dust, and as I've been working a lot, I wanted to get it back with basic functions, but without waiting 10 seconds from the moment i press on APPS BUTTON and the actual time for which I see the apps page.
so, here's my google searching experience.
Donnie87 said:
1) Some people they say that the KL can accept all the roms of the Tf700T. for example katkiss is saying to use one of their roms
1.a) some say that it will brick the device.
so, first question here, what will happen if i'll get a custom rom of the TF700T?
Click to expand...
Click to collapse
I'd say the first question is: Is there a compatible custom recovery for the KL and how to install it? I do not know that there ever was a custom recovery made for the KL and using one made for another Transformer may or may not brick your device. I do not see a single post from anyone stating that they successfully installed a custom rom or recovery on the KL, so my guess is: It cannot be done unless you develop a custom recovery for this tablet and find a way to flash it.
2) some people say that I should have a version of the "unlock bootloder" after unlocking with the asus app.
Well I don't have anything, I just have a small phrase which is "device unlocked" and that's it. nothing else.
Click to expand...
Click to collapse
Well, there's the first difference to other Transformers: Most of them have a bootloader menu from where you can boot into recovery or into Android and perform a data wipe. Booted into the bootloader you also have fastboot access. The KL does not seem to have any of this. Do you have fastboot working on your PC? Try it, boot with Vol down or Vol Up and then check if you have fastboot access to the tablet. I doubt it....
3) some say on google that there is a cyanogen mod for the KL. Unfortunately cyanogenmod wiki and forum are down, so I can't find either assistance, either the files.
nothing to do here, then.
Click to expand...
Click to collapse
I've only seen post users expressing hope or wishes for CM for the KL. I don't think there ever was a working CM rom for the KL
4) let's say I'll follow your guide, and i'll flash a custom rom. will I lose the 4g?
Click to expand...
Click to collapse
You cannot follow my guide unless you figure out a way to get fastboot working. You could try to flash TWRP recovery using their app or Flashify, but which TWRP?? Which version might be compatible with your bootloader? Nobody knows it seems. But heck! What have you got to loose? You are not going to use the tablet in its current state anyway, so if you brick it - who cares?
But to answer your question: Yes, you would definitely loose the 4G. The software for your modem has its own partition and no rom made for the wifi-only Transformers even knows this partition exists, let alone about the hardware
4.a) how can I get to the old rom, even original, in order to get 4g back?
Click to expand...
Click to collapse
Again: Untested territory. If you had a custom recovery or fastboot you might be able to flash the Asus firmware in either. Maybe
you won't believe me
I was away for 1 month
got back
installed framaroot
installed greenify
now it runs with like 10 apps total (including the keyboard)
tablet STILL UNUSABLE, takes 1 minutes to open youtube, 2 mins to open play store
Id really like to brick it rather than keep it like that
Well, there's the first difference to other Transformers: Most of them have a bootloader menu from where you can boot into recovery or into Android and perform a data wipe. Booted into the bootloader you also have fastboot access. The KL does not seem to have any of this. Do you have fastboot working on your PC? Try it, boot with Vol down or Vol Up and then check if you have fastboot access to the tablet. I doubt it....
Click to expand...
Click to collapse
tried but the max i get is the screen wghere
"press volume button to select
1) enter sd down mode
2) factory reset
3) exit update mode
press power button to enter"
so i then flashed with flashify, read after
berndblb said:
You cannot follow my guide unless you figure out a way to get fastboot working. You could try to flash TWRP recovery using their app or Flashify, but which TWRP?? Which version might be compatible with your bootloader? Nobody knows it seems. But heck! What have you got to loose? You are not going to use the tablet in its current state anyway, so if you brick it - who cares?
But to answer your question: Yes, you would definitely loose the 4G. The software for your modem has its own partition and no rom made for the wifi-only Transformers even knows this partition exists, let alone about the hardware
Click to expand...
Click to collapse
I then flashed the TWMR
when i rebooted it said
"no usb connected"
i then connected to the PC
and it say
"READY FOR DOWNLOAD" with an android picture
i can't boot it up again
what should i do now?
when i now do the FASTBOOT DEVICES command on pc, I see the serial of the asus
it's the first time fastboot sees it
I tried doing "fastboot update kitkatnougatellaxxxx.zip"
but it say that android-info.txt & android-product.txt not find so not flashable
what now, then? I can't even use it with the old OS
You need to boot into the TWRP that you flashed, hold the volume button down and press the power button (hold both) until you get the fastboot screen, the square with [RCK] should be blinking. Now press the volume up button to enter the TWRP recovery console. - NP
Nektopoli said:
You need to boot into the TWRP that you flashed, hold the volume button down and press the power button (hold both) until you get the fastboot screen,
Click to expand...
Click to collapse
this is what i get when i press the button normal boot button
this is what i get when i press the volum down + boot button
I just did flashifty with the latest TMWR recovery for TF700T
help pliz
best bet would be to do a factory reset, I don't believe this rom will work on the KL model. - NP
it doesn't even allow the factory reset, as if i press it it gives the NO USB CONNECTED screen
i'd say it's bricked
Donnie87 said:
it doesn't even allow the factory reset, as if i press it it gives the NO USB CONNECTED screen
i'd say it's bricked
Click to expand...
Click to collapse
Try selecting [1] "Enter SD down mode" which is Enter SD download mode and see if you get to the next menu. - NP
I can't
I mean it doesn't get to the next menu
I've been trying to find the threads on how to re-flash the stock ASUS ROM from the SD cardseeing this is the only way to get the TF700k working but I can't find it know. It involved have the ROM in the root directory on the SDcard and giving it a specific name, this name triggers the tablet to update itself. - NP
I haven't turned this phone on in years.
I unlocked the bootloader and flashed roms years ago and i remember trying to get it back to stock and trying to relock it but i couldn't fully do it.
I tried to install TWRP and put a rom on it but it wont work so i thought trying to get it back to stock as much as i can might help. then i can start again
1. the phone doesn't work by USB if plugged in while it's on. I have to leave it plugged in and then restart it for it to work
2. ADB works while phone is on (doing 1)
3. Fastboot does not and i have no idea why. I can't install TWRP
Passportpowell said:
I haven't turned this phone on in years.
I unlocked the bootloader and flashed roms years ago and i remember trying to get it back to stock and trying to relock it but i couldn't fully do it.
I tried to install TWRP and put a rom on it but it wont work so i thought trying to get it back to stock as much as i can might help. then i can start again
1. the phone doesn't work by USB if plugged in while it's on. I have to leave it plugged in and then restart it for it to work
2. ADB works while phone is on (doing 1)
3. Fastboot does not and i have no idea why. I can't install TWRP
Click to expand...
Click to collapse
do you have usb debugging enabled, are your sdk tools up to date?
Yes to both.
When doing the adb fastboot part it restarts into one of the screen I attached to my post.
My computer makes a noise like a USB had been connected but nothing comes up.
fastboot devices command shows nothing and when I check device manager it just says android with a yellow! If that helps.
Passportpowell said:
Yes to both.
When doing the adb fastboot part it restarts into one of the screen I attached to my post.
My computer makes a noise like a USB had been connected but nothing comes up.
fastboot devices command shows nothing and when I check device manager it just says android with a yellow! If that helps.
Click to expand...
Click to collapse
then you need to update your htc drivers.
here you go.
Aldo101t said:
do you have usb debugging enabled, are your sdk tools up to date?
Click to expand...
Click to collapse
Aldo101t said:
here you go.
Click to expand...
Click to collapse
Super star
I now have another issue though. I can't sideload and it's asking for a password for twrp to mount decrypt data. If you don't mind trying to help me here too
I've done a format data on twrp and it won't ask for a password anymore but I still can't sideload anything. Going to try to copy the rom to the storage and see what happens there
I've only could see a twrp folder on my phone when I connect it to my pc while still in twrp so I copied a rom there and went into install zip, data, media, twrp. My file was there.
Installing rom now I'll update if it worked.
Passportpowell said:
Super star
I now have another issue though. I can't sideload and it's asking for a password for twrp to mount decrypt data. If you don't mind trying to help me here too
View attachment 5087597
View attachment 5087599
Click to expand...
Click to collapse
you may have to format data, then flash magisk after then reboot, why are you trying to side load the rom just put it on your ex-sdcard, and flash it in twrp. twrp won't decrypt your data, what version of twrp you using, the latest is 3.4.0-0
try hitting cancel when it asks for a password, then see if it works.
here is magisk
if you are on pie that viper rom is based on oreo. just so you know.
Aldo101t said:
you may have to format data, then flash magisk after then reboot, why are you trying to side load the rom just put it on your ex-sdcard, and flash it in twrp. twrp won't decrypt your data, what version of twrp you using, the latest is 3.4.0-0
try hitting cancel when it asks for a password, then see if it works.
Click to expand...
Click to collapse
Yeah i sorted that bit. it confused me because there were no files and didn't know how to get to anything i copied over but that's how i got the rom on
Aldo101t said:
if you are on pie that viper rom is based on oreo. just so you know.
Click to expand...
Click to collapse
Yeah i realised after you said it. I believe i was on pie because i was on build no. 3.34.401.1 and now i'm on 2.33.401.19 after installing the rom. I shouldn't be trying to do this at almost 12:30 at night haha.
Is that bad that its gone through and, so far, worked? What would you recommend I do/ what would you do if you were in my position currently?
I was originally going to to try to get back to stock but im not even sure what RUU to use as i think the one that i had used a few years ago might not have been the original.
you've been an amazing help so far so thank you
Passportpowell said:
Yeah i sorted that bit. it confused me because there were no files and didn't know how to get to anything i copied over but that's how i got the rom on
Yeah i realised after you said it. I believe i was on pie because i was on build no. 3.34.401.1 and now i'm on 2.33.401.19 after installing the rom. I shouldn't be trying to do this at almost 12:30 at night haha.
Is that bad that its gone through and, so far, worked? What would you recommend I do/ what would you do if you were in my position currently?
I was originally going to to try to get back to stock but im not even sure what RUU to use as i think the one that i had used a few years ago might not have been the original.
you've been an amazing help so far so thank you
Click to expand...
Click to collapse
well, see how it goes, if you start to have issues go back to stock, if you made a backup of stock just restore it.
use the ruu for 401 make sure it's 3.34.401.x
that software number doesn't mean you are on 2.33 firmware you'll still be on pie firmware, 3.34
Aldo101t said:
well, see how it goes, if you start to have issues go back to stock, if you made a backup of stock just restore it.
use the ruu for 401 make sure it's 3.34.401.x
that software number doesn't mean you are on 2.33 firmware you'll still be on pie firmware, 3.34
Click to expand...
Click to collapse
I can't seem to find a RUU for 401 3.34.401.x that isn't dual sim version. Could you point me in the right direction please in case I do ever want to attempt stock again?
Edit: I've found it. Also why this one instead of 3.37.617.1?
Edit: im guessing because 3.37.617.1 is for NA and the one you mentioned is for EU which is where i am
Also I think im getting an idea about why it won't charge or connect until I restart.
I've installed lineage room 17.1 and it's constricted showing as "charging connected device via usb" even when it's nothing is plugged in. I'm guessing it's a hardware issue?
Passportpowell said:
I can't seem to find a RUU for 401 3.34.401.x that isn't dual sim version. Could you point me in the right direction please in case I do ever want to attempt stock again?
Edit: I've found it. Also why this one instead of 3.37.617.1?
Edit: im guessing because 3.37.617.1 is for NA and the one you mentioned is for EU which is where i am
Also I think im getting an idea about why it won't charge or connect until I restart.
I've installed lineage room 17.1 and it's constricted showing as "charging connected device via usb" even when it's nothing is plugged in. I'm guessing it's a hardware issue?
Click to expand...
Click to collapse
3.37.617.1 is for the us-unlocked
Hello to everyone...I just got from my older brother his HTC U11 4gb 64gb phone. And it has locked bootloader and does not have root. So please what should I have to do so I can install custom rom. Stock rom is old full of bloatrware. There is so many information that I am confused.
Thx so much !
Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R
Try nother USB C cable. Some not able to handle data.
rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.
BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,
Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone