Optimized gaming sysctl - Shield Tablet Android Development

Tweaked for for performance, should work with any rom.

What kind of battery life effects should I expect if I use this?

Where does this file go? Sysctl? Because their is a lot of em

Here's the OTA 4.4 upgrade patched boot with sysctl baked in, unzip the boot.img and flash it through fastboot flash boot boot.img, updated twrp too. after installing, boot to recovery and flash updated SuperSU and busybox.

m0nt3s said:
Here's the OTA 4.4 upgrade patched boot with sysctl baked in, unzip the boot.img and flash it through fastboot flash boot boot.img, updated twrp too. after installing, boot to recovery and flash updated SuperSU and busybox.
Click to expand...
Click to collapse
So, can i use these with a rooted stock 4.3? To specify. I flash the boot using fastboot, then the recovery (is it twrp 3.0.2.2?)? Then reboot into the new recovery and flash SuperSU? I don't really need busybox? Or is it required?

@rkocour So, can i use these with a rooted stock 4.3? To specify. I flash the boot using fastboot, then the recovery (is it twrp 3.0.2.2?)? Then reboot into the new recovery and flash SuperSU? I don't really need busybox? Or is it required?[/QUOTE]
Yes, this boot image will work with 4.4,4.3,4.2 and I'm pretty sure it would work on 1.4 but I only have the wifi version. If some one with a new K1 tablet wouldn't mind testing by flashing this and letting me know if it works, if not I'll build one for the K1. This boot image is userdebug which grants you ultimate root. you'll notice when you flash SuperSu on it, instead of applying system-less root you get tmp-mksh.
so if your on windows, I'm attaching the best adb drivers that aren't intrusive. takes 15 seconds to install but by default it will install to C:\adb
open my computer, go to C:\adb and there should be adb.exe,adbwinapi.dll,adbwinusbapi.dll, and fastboot.exe
hold down the shift key and right click any where open in the window and you'll see open command prompt here. select it
boot your tablet into bootloader mode by powering it off and then holding down vol - and powering it back on. use the volume rock - to move to fastboot option and press the power button to select fastboot, you should have your tablet connected to your computer through usb. also unzip boot.img and recovery.img to c:\adb
from the command prompt type this command, it will look like this
C:\adb>fastboot flash boot boot.img
it will give you conformation that it wrote and then type
C:\adb>fastboot flash recovery recovery.img
same thing and after conformation unplug tablet from usb, use volume rocker to select recovery and boot into recovery.
It's important to flash both this boot and recovery together due to the fact that with much from every one on here, i'll throw in the @ later, we were able to get f2fsf working and the boot and recovery both have the updated fstab files needed, if you only flash one without the other it will error due to mismatching fstabs.
even if you don't think you use it, it's always good to install busybox, this is the newest updated version with 398 updated aplets. you're better off flashing it then not.

m0nt3s said:
Yes, this boot image will work with 4.4,4.3,4.2 and I'm pretty sure it would work on 1.4 but I only have the wifi version. If some one with a new K1 tablet wouldn't mind testing by flashing this and letting me know if it works, if not I'll build one for the K1. This boot image is userdebug which grants you ultimate root. you'll notice when you flash SuperSu on it, instead of applying system-less root you get tmp-mksh.
so if your on windows, I'm attaching the best adb drivers that aren't intrusive. takes 15 seconds to install but by default it will install to C:\adb
open my computer, go to C:\adb and there should be adb.exe,adbwinapi.dll,adbwinusbapi.dll, and fastboot.exe
hold down the shift key and right click any where open in the window and you'll see open command prompt here. select it
boot your tablet into bootloader mode by powering it off and then holding down vol - and powering it back on. use the volume rock - to move to fastboot option and press the power button to select fastboot, you should have your tablet connected to your computer through usb. also unzip boot.img and recovery.img to c:\adb
from the command prompt type this command, it will look like this
C:\adb>fastboot flash boot boot.img
it will give you conformation that it wrote and then type
C:\adb>fastboot flash recovery recovery.img
same thing and after conformation unplug tablet from usb, use volume rocker to select recovery and boot into recovery.
It's important to flash both this boot and recovery together due to the fact that with much from every one on here, i'll throw in the @ later, we were able to get f2fsf working and the boot and recovery both have the updated fstab files needed, if you only flash one without the other it will error due to mismatching fstabs.
even if you don't think you use it, it's always good to install busybox, this is the newest updated version with 398 updated aplets. you're better off flashing it then not.
Click to expand...
Click to collapse
Thank you for the detailed instructions. :good:

NinjaCoool said:
Thank you for the detailed instructions. :good:
Click to expand...
Click to collapse
can someone post the shield tablet drivers please?

supertory said:
can someone post the shield tablet drivers please?
Click to expand...
Click to collapse
here you go

m0nt3s said:
here you go
Click to expand...
Click to collapse
Thanks , flashed it and everything but got a bootloop , running 10.6 DU , could it be due to having regular root from before and flashing the systemless one?

works good, small performance boost. shield k1, optimized stock rom

pietras83 said:
works good, small performance boost. shield k1, optimized stock rom
Click to expand...
Click to collapse
How's battery life?

@supertory
Are you using the OG tablet or the k1?

supertory said:
Thanks , flashed it and everything but got a bootloop , running 10.6 DU , could it be due to having regular root from before and flashing the systemless one?
Click to expand...
Click to collapse
did you use kingoroot? or superSU as root before?

pietras83 said:
works good, small performance boost. shield k1, optimized stock rom
Click to expand...
Click to collapse
How much of a boost did it give? Did you becnhmark?
Thanks

m0nt3s said:
did you use kingoroot? or superSU as root before?
Click to expand...
Click to collapse
Was using superSU

tinybilbo said:
How much of a boost did it give? Did you becnhmark?
Thanks
Click to expand...
Click to collapse
Yes I benchmarkt it, i get 96000 pts ~3000 more than before flash

So I finally got around to scripting my sysctl setting and other misc performance settings into a script that every one can use. You can either throw it in your init.d folder or run it from script manager. I've attched a init.d enabler for our device as well as the performance script. Let me know if you have any problems but I've tested and it works. feedback welcomed. the zip is not flashable, extract to your sd card and run with script manager.

m0nt3s said:
So I finally got around to scripting my sysctl setting and other misc performance settings into a script that every one can use. You can either throw it in your init.d folder or run it from script manager. I've attched a init.d enabler for our device as well as the performance script. Let me know if you have any problems but I've tested and it works. feedback welcomed. the zip is not flashable, extract to your sd card and run with script manager.
Click to expand...
Click to collapse
where should I place the files so I can see them in the init.d section in kernel auditor ?(sp)

m0nt3s said:
@supertory
Are you using the OG tablet or the k1?
Click to expand...
Click to collapse
just seeing this and the OG tablet

Related

Return to Stock Kernel

Here is the deal. Got my wifi only on launch day. Soon there after rooted. Installed bigdogrush 1.3 kernel. Tried to update to sdcard support. Each time I tried it would screw up my wifi....so I eventually gave up. Here is the real problem. Now I can't install recently released 3.1 update. Can anyone explain to me how to return to the stock kernel? I understand this will allow me to install the 3.1 update. Thanks for any help.
xhuck1 said:
Here is the deal. Got my wifi only on launch day. Soon there after rooted. Installed bigdogrush 1.3 kernel. Tried to update to sdcard support. Each time I tried it would screw up my wifi....so I eventually gave up. Here is the real problem. Now I can't install recently released 3.1 update. Can anyone explain to me how to return to the stock kernel? I understand this will allow me to install the 3.1 update. Thanks for any help.
Click to expand...
Click to collapse
try this, i just did it and works great. you basically need to download the stock images and use adb to push them. btw i assume you have a us version wifi only xoom. i would skip the last step about relocking it, if you plan to upgrade your kernel after your on 3.1.
http://developer.motorola.com/products/software/
once your back to stock everything, you can safely update to 3.1
I appreciate your help. Problem is I don't know how to do the things you are talking about. I've downloaded the images and the sdk. I'm not sure where I should put them on my zoom. Also when I try to run fastboot I get a device not found message. I also get a AdbWinApi.dll not found. I have no idea how to fix any of this. Yes I have a U.S. WIFI. I used the one click rook method. Is there a one click method out there that would help me?
If you're using windows, open the SDK folder and browse to the tools folder. Copy the img files to that folder.
Now open a command prompt and browse to the SDK Folder\tools folder (this folder as the fastboot.exe file that we're going to use and now the img files are also here!)
Now reboot your XOOM into fastboot mode (turn off the xoom, then turn the XOOM back on and while at the "Dual Core" logo, start pressing volume down until you see "--> Fastboot" up on the top left corner then press volume up to start the fastboot protocol).
Once you're in fastboot mode, in the command prompt, type fastboot devices to make sure your xoom is listed on there. If not, check to make sure your system isn't missing drivers, if so, download the xoom drivers again or if you have the Motorola Mobile Drivers installed already, open the Motorola Mobile Driver Installer and do an update to make sure you have the latest drivers).
Once you've confirmed that fastboot can talk to your xoom, run this commands:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Your xoom will then relock itself, format, and reboot.
This is as clear as I can be.
If need to, re-run the SDK Manager and make sure you have the correct packages installed needed.
xhuck1 said:
Here is the deal. Got my wifi only on launch day. Soon there after rooted. Installed bigdogrush 1.3 kernel. Tried to update to sdcard support. Each time I tried it would screw up my wifi....so I eventually gave up. Here is the real problem. Now I can't install recently released 3.1 update. Can anyone explain to me how to return to the stock kernel? I understand this will allow me to install the 3.1 update. Thanks for any help.
Click to expand...
Click to collapse
I'm betting the reason your wifi isn't working is because you didn't push the .ko files. Think of those as driver files. You probably just flashed the boot partition.

[Q] home to root

please dont shout, just take pitty on me.
I have been getting into the world of rooting and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not fully understanding exactly what im doing.
but i can flash by:
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
PS
my cid is VADAP001
my MID is PG5813000
taffytim said:
please dont shout, just take pitty on me.
I have been getting intot he world of routing and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not flly understanding exactly what im doing.
but i can flashing by
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
Click to expand...
Click to collapse
Hi,
Are you talking about wifi?
Have you got a router?
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Malybru, i do have a router but my wifi wont turn on so i cant connect to it.
T-Macgnolia said:
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Click to expand...
Click to collapse
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
taffytim said:
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
Click to expand...
Click to collapse
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
T-Macgnolia said:
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
Click to expand...
Click to collapse
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
For every custom rom you install you need to follow the same procedure.
1. First flash/install the rom via recovery
2. Get the boot.img and flash it via fastboot (some rom's have more than one kernel then choose the best you want)
As long as you stay in HTC unlocked bootloader the above steps are necessary to flash the rom completely to prevent bootloops and wifi errors
sent from my blazing fast pyramid through sonic waves
ta gane shp, this is a good place with good people
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Asskicker2 said:
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Click to expand...
Click to collapse
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
malybru said:
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
Click to expand...
Click to collapse
Yeah, that isn't working.
Wifi ain't working now.
Asskicker2 said:
Yeah, that isn't working.
Wifi ain't working now.
Click to expand...
Click to collapse
Hi,
Just restore the nandroid backup you made.
malybru said:
Hi,
Just restore the nandroid backup you made.
Click to expand...
Click to collapse
Yeah, but I wanted to update to newest kernel. Thanks though
Doesn't work with me.
taffytim said:
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
Click to expand...
Click to collapse
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Wi-Fi Issues
theumairahmad said:
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Click to expand...
Click to collapse
Post 3 in this thread explains exactly where the problem is. But ........you will never unlock that boot partition if ur phone is S-ON. The trick with the wire works...it took me couple of times to do it but it worked. Then.....the lates ViperS version does it for you. You do not have to use ADB or whatever that program was to flash the boot.img It is all in the ROM. I even flashed the newest bricked 1.4 kernel on top.....but that 3rd comment is the key to all problems with Wi-Fi and other kernel issues:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:

Recovery no longer allows me to select files from memory (twrp)

I updated now I can't do anything. Im able to book ROM and to boot into recovery but am no longer able to select anything while in recovery.. basically if i want to changes roms or whipe data and etc.. i can't do that anymore..
Is there a way to revert back to stock? ( bootloader is unlocked before this happened and rom is rooted)
Is there a way to fix this? same thing happens when i install clockworkmod recovery..
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4
let it boot and set for 30 min then reflash twrp and it works same thing happened to me
toolhas4degrees said:
let it boot and set for 30 min then reflash twrp and it works same thing happened to me
Click to expand...
Click to collapse
Can you recommend which version of twrp to use ? Link?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 4
I"m still trying to fix this issue.. any help would be great
dilfatx said:
I"m still trying to fix this issue.. any help would be great
Click to expand...
Click to collapse
twrp 2.5 is the only one that has no issues as of now.
FIXED!
After doing some more extensive reading and trials and errors.. these two threads where helpful
[UNLOCKED BL] Method 2: Update using fastboot
Notes:
You will keep all your data
This is the best method to update your tablet if you want to keep all your data, and the safest one
Ensure you have the correct drivers for the tablet installed on your computer, or you will have a "waiting for device" error
To update using fastboot, follow this steps:
If you don't have fastboot yet, download it from here an unpack it somewhere on your computer
Extract the Asus firmware file and put the blob file inside fastboot folder
Open a command line on fastboot folder (write "cmd" on Windows search bar at the Start menu, and then
Code:
cd "FOLDER WHERE YOU EXTRACTED FASTBOOT"
, or you can just use SHIFT + RIGHT CLICK on the folder and select "Open command line window here" or something like that)
Reboot the tablet holding the volume down key until you see some icons. Use the volume down key to select the USB icon and then volume up to select it
Connect the tablet to the computer if you didn't do so
Write
Code:
fastboot -i 0x0B05 flash staging blob
, hit enter and wait until it completes
Hold the power button for 10 seconds to reboot the tablet
You are now updated to Android 4.2
Click to expand...
Click to collapse
and to install recovery I used this step from the same thread
[UNLOCKED BL]-- Installing TWRP (Recovery) --
Since this new update brings a new bootloader, older recovery versions from 4.1 won't work at all. Don't try to flash one!
This guide will give you a recovery that works just fine on the new bootloader. And yes, it can read/write to an external SD just fine. Follow this steps to install the new recovery on your device:
Connect the tablet to the computer
Reboot the tablet using the proper button on the power menu, holding Volume down until you see three icons (RCK, Android and Wipe Data)
Download this file and unpack it (it contains fastboot and a version of TWRP 2.5.0.0 that works with the new bootloader)
Open a command line on the extracted folder (you can use the instructions I wrote in Method 2 if you don't know how to do this) and type
Code:
fastboot -i 0x0b05 flash recovery twrp.blob
Wait for the script to complete. Once it is done, reboot the tablet by holding volume down and power button for 10 seconds or using
Code:
fastboot reboot
on the command line. Don't enter recovery directly!
You have now the new recovery for Android 4.2 .
Click to expand...
Click to collapse
from [GUIDE][14/09]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices and it was successful using this specific method :laugh:
dilfatx said:
After doing some more extensive reading and trials and errors.. these two threads where helpful
and to install recovery I used this step from the same thread
from [GUIDE][14/09]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices and it was successful using this specific method :laugh:
Click to expand...
Click to collapse
Thank you for this, I have had to go back to 2.4.4 because it was the only working one, going to try this when I'm home.
Got it working (updated from 2.4.4 to 2.5.0 finally made it work thanks and now my external SD can finally be used going to buy one only for backups
frankgreimes said:
Thank you for this, I have had to go back to 2.4.4 because it was the only working one, going to try this when I'm home.
Got it working (updated from 2.4.4 to 2.5.0 finally made it work thanks and now my external SD can finally be used going to buy one only for backups
Click to expand...
Click to collapse
no problem

New replacement tablet stopped working properly! Help!

So after I got my new tabby, I proceeded to update it to 3.1. When it finished downloading, the tablet froze and rebooted, but the screen did not come back on! Literately, the pixels were not on (tested by going into a dark room and seeing if the pixels were on but colored black)
So I held power for 15 secs, rebooted, updated, and all that. Then, I decided to root using Kingroot. The first 3 times, it failed. It stopped at around 17-21%. The fourth time it just...worked. Then, shortly after replacing it's root with supersu using the kingroot replacement app, I went to DL titanium backup so I could restore stuff.
Then, out of nowhere, the tablet reboots, and shows the nvidia boot screen like normal.... But it was frozen. The tablet will NOT get past this screen! I tried going into the bootloader using VOL Down + Power, which works! I then tried "fastboot protocol", but when I select it, it just goes black, then takes me back to the bootloader!
I then tried recovery, but I forgot to install twrp, so all it shows is "No command" underneath a android! Help! I don't know what to do!
I did not enable usb debugging in dev options either, because I did not think to do that first when getting a brand freaking new tablet that should not be doing this!!!
My old one works! (Albeit with unstable audio glitches and general lagginess)
I would try to flash all new from recovery images (via fastboot, you can download from Nvidia page), then flash latest TWRP (MultiROM patched, if you prefer....) and from TWRP flash latest SuperSU.zip...
Lynco said:
I then tried "fastboot protocol", but when I select it, it just goes black, then takes me back to the bootloader!
Click to expand...
Click to collapse
that's what is supposed to happen
@BitOBSessiOn @Bogdacutu
But how would I flash via fastboot? What tool should I use?
I completely forgot how to do all of that stuff.
Lynco said:
@BitOBSessiOn @Bogdacutu
But how would I flash via fastboot? What tool should I use?
I completely forgot how to do all of that stuff.
Click to expand...
Click to collapse
First step: If you have downloaded recovery image, and unpacked everything, you get a script named "flash-all.sh" (for linux, flash-all.bat for win), execute it while in fastboot mode and connected to PC...
Lynco said:
@BitOBSessiOn @Bogdacutu
But how would I flash via fastboot? What tool should I use?
I completely forgot how to do all of that stuff.
Click to expand...
Click to collapse
Are you running linux or windows? Either way you'll need to get fastboot and adb. Download twrp and put the img file in the same directory as the fastboot and adb files. Put the tablet in bootloader mode. In a terminal window run fastboot flash recovery recovery.img (or whatever the filename for your twrp file you downloaded is). After it's done, run 'fastboot reboot-bootloader' and then go into recovery. From there you can either sideload a rom zip file or use adb to push it over to the tablet and then flash it. If you want stock, just download and flash a zip from the stock rom thread. Or if you want 100% stock, just flash the factory images from bootloader as described here

Bootloop when starting android or RCK

I tried to flash a custom rom (KatKiss), and it seems that I did something wrong along the way because the tablet is stuck in a bootloop.
So I rebooted my tablet and access the bootloader ("fastboot devices" recognize my device) and try to go to the recovery (with the TWRP splash screen, "adb devices" recognize my device). Unfortunately after 20 seconds on the splash screen, the tablet reboots (tries to load my katkiss android but bootloop everytime).
Bootloader : 10.6.1.14.10
TWRP : 3.1.1.0
Since the fastboot recognize my device while in bootloader, I think that I should try to flash twrp since it seems to be corrupted somehow.
Every time I flashed a rom nothing went wrong but now that I have a problem I don't want to worsen it and would like some help on the issue.
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Sent from my Nexus 5X using Tapatalk
Thank you for the fast reply!
I did flash the rom with my current TWRP and only downloaded the rom version for the TF700. Below is what I tried from your suggestion:
I check that my device is recognized:
fastboot device
So I tried flashing TWRP:
fastboot flash recovery twrp-3.1.1-0-tf700t
After it succeeded, I reboot the tablet:
fastboot reboot
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
That is very strange indeed. Yes, try a 3.0.2 version of TWRP and see if that works.
If not, I would flash the Asus stock blob in fastboot and start from scratch....
Sent from my TF700T using Tapatalk
Kromlech said:
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
Click to expand...
Click to collapse
Not sure if this will help but I had a reboot problem with trying to load into TWRP. I posted my solution into a different thread but will toss it out here..
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basically the same.
https://forum.xda-developers.com/tra...prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessary .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
double post
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
Unidave's link would only help you if you generated your device specific nvflash blobs when the tablet was still functioning. Did you:
flash a specifically modded recovery - flash the moddded bootloader, use wheelie to generate and save your blobs, return everything to factory specs?
I highly doubt it since you would have mentioned...
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/my/support/Download/28/1/0/11/29/8/
Extract the zip twice until you see a blob and a meta-inf file.
Move the blob into your fastboot folder, discard the rest of the file
Issue these commands one by one, letting each one finish before starting the next. Some will finish quick, others may take up to 3 minutes:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
The first boot will take a while, but that should put you back on a stock JB 4.2 system.
Trash all the files you used in your last attempt and redownload the rom, gapps and supersu
Fastboot flash TWRP
Reboot
Format /data in TWRP (this will take up to 1 hour - let it finish!!), then convert /data to f2fs
Flash the rom, gapps, supersu
If you flash Nougatella remember that you have to turn on wifi right after the language selection during setup or Google framework will crash.
Spend the end of the day doing it, but it worked flawlessly! Thanks a lot @berndblb, now I can use my tablet again!
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
My apologies for the problem with my link, looks like you resolved it, but wanted to post a correct working link to take someone else into the full conversation and context...
https://forum.xda-developers.com/showpost.php?p=71150385
berndblb said:
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Click to expand...
Click to collapse
Broken link ? that post isn't very old, either. ??
berndblb said:
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Click to expand...
Click to collapse
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
ketulharini said:
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
Click to expand...
Click to collapse
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
monogwai said:
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
Click to expand...
Click to collapse
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
ketulharini said:
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
Click to expand...
Click to collapse
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/forum/transformer-pad-infinity-tf700-tegra-3-development/46302-guide-help-my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
monogwai said:
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
Click to expand...
Click to collapse
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
ketulharini said:
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
Click to expand...
Click to collapse
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
monogwai said:
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
Click to expand...
Click to collapse
You mean a batch file with the adb commands right? Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8). Depending on what situation he came from before, it might be a good idea to start all fresh...
The tricky thing are the adb push bootit.ko and the insmod command. Those have to be timed just right to get executed, so a batch file might come in handy. Both commands only take a second or two to execute, so your window of 5 seconds could work. Maybe not in the same session, but they should work.
If the insmod command does not kick the tablet into the bootloader, there are 2 possible reasoons:
adb push bootit.ko did not work
the insmod command did not work
To find out if the file push worked you could add a simple list command for the contents of /sdcard/. Again - tricky, I know since you still are working with the 5 sec window, but that's what you got to work with...
That would look something like in the attached picture. So after pushing bootit.ko you issue:
Code:
adb shell ls /sdcard/
Try it with the batch file, try it with single commands... Don't give up. As long as you have any kind of adb access you should be able to solve it.
Good luck!
berndblb said:
You mean a batch file with the adb commands right?
Click to expand...
Click to collapse
Yeah.
berndblb said:
Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8).
Click to expand...
Click to collapse
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
monogwai said:
Yeah.
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
Click to expand...
Click to collapse
Care to share the batch file?

Categories

Resources