[KERNEL][28/08/2014]FastCharge kernel for the Kindle Fire HD 7 - 7" Kindle Fire HD Android Development

Disclaimer:I am not responsible if anything I've provided suddenly deep-fries your device or causes alien abductions leading to thermonuclear war.
Hey guys!
For quite some time I've noticed people asking for a solution to the famous battery drain issue of the Kindle Fire HD. To solve this problem,I've compiled a kernel. May I present to you,
The FastCharge Kernel
by SafinWasi​
This is a kernel which has the fastcharge functionality added to the stock 7" Kindle Fire HD kernel. In other words,by using this kernel while enabling the fastcharge function on your device,you can use the full voltage of your AC power source,thereby speeding up the charging like crazy!! Yay!
Features:
By enabling fast charge,reduces charging time using the full power of the AC power source/USB cord connected to PC/car charger/any other power source.
Ensures longer lasting battery life
Easy to use,can be used by complete newbies as well.
Click to expand...
Click to collapse
How to flash:
Download the kernel/boot image and place it somewhere on your PC
Ensure that adb and fastboot can detect your device.
CD (change directory)to the image folder with a command prompt.
In the prompt,enter the following command:
Code:
fastboot -i 0x1949 getvar product
Power off your device and connect it the computer. It should boot into fastboot.
Enter this command to flash the kernel:
Code:
fastboot -i 0x1949 flash boot safinwasi-kernel-fastcharge-20142808-tate-v1.img
Finally,enter this command to reboot out of fastboot:
Code:
fastboot -i 0x1949 reboot
Profit!
Click to expand...
Click to collapse
How to activate and deactivare fast charge:
There are two ways to activate fast charge. 1:Through command line and 2:Through the dev's app.
To activate through command line:
Code:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
and deactivate:
Code:
echo 0 > /sys/kernel/fast_charge/force_fast_charge
Or,you can install the app made by the original developer of the fastcharge kernel. Find it on the Play Store.
Click to expand...
Click to collapse
Downloads:
Version 1:safinwasi-kernel-fastcharge-20142808-tate-v1.img - 7.96 MB
MD5 Sum:5dd8564b8ac119d2ed3ef0009b987fae
Version 2:safinwasi-kernel-fastcharge-20141011-v2-tate.img - 8.00 MB
MD5 Sum:9a5df74e5b4a28921932ad8507cc5303
Click to expand...
Click to collapse
Source:
https://github.com/SafinWasi/kernel_omap_bowser-common
Click to expand...
Click to collapse
Credits
Thanks to Hashcode,fattire,verygreen,r3pwn,BookCase,chad0989 and anyone else whose work helped me.​
XDA:DevDB Information
SafinWasi's FastCharge Kernel, Kernel for the Amazon 7" Kindle Fire HD
Contributors
SafinWasi
Kernel Special Features: Adds fastcharge function to the 7" KIndle Fire HD 2012(tate) kernel. Can be used with fastcharge apps.
Version Information
Status: Alpha
Created 2014-08-28
Last Updated 2014-08-28

[B]Q&A[/B]
Q:My device hangs on the blue Kindle Fire Logo! What happened?
Ans:Your device was running a more recent nightly of CyanogenMod 11,which is incompatible with this kernel. Please downgrade the ROM to an older nightly or the M8 Snapshot. In the meantime,you can access recovery to restore a nandroid or boot into fastboot to reflash your stock kernel.
Q:How can I backup my stock kernel?
Ans:Connect the device with ADB debugging enabled. Then issue the following commands(for Windows):
Code:
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/boot.img"
adb pull /sdcard/boot.img

Reserved

I'll be sure to try this later, after school!

r3pwn said:
I'll be sure to try this later, after school!
Click to expand...
Click to collapse
Okay, thanks bro!

Since I don't have a computer available I'd it OK to use flashlight or rashr to flash the boot image?

Mr. Xplosion Man said:
Since I don't have a computer available I'd it OK to use flashlight or rashr to flash the boot image?
Click to expand...
Click to collapse
Use fireflash.
Sent from my device running CyanogenMod 11

I'm using terminal to put in the command do I need to have my device plugged into the power source before turning it on?

Awesome, Man! I'll flash this as soon as I get a chance. Excellent work!

Figured out why it's not working for me. My wall charger only allows 1 amp to output so I need to buy a new charger.

Excellent. One thing, this kernel have any other feature, or only fast charge?

persano said:
Excellent. One thing, this kernel have any other feature, or only fast charge?
Click to expand...
Click to collapse
Only fast charge.

Mr. Xplosion Man said:
Only fast charge.
Click to expand...
Click to collapse
OK, is still excellent, it is a very necessary feature

Totally awesome idea, but I can't get it to boot. Hangs on blue KF logo. Tried adb and fireflash methods, same result. Double checked md5s. Running @Hashcode's cm11.

Rushead said:
Totally awesome idea, but I can't get it to boot. Hangs on blue KF logo. Tried adb and fireflash methods, same result. Double checked md5s. Running @Hashcode's cm11.
Click to expand...
Click to collapse
??? I'll take a look at it. And do try fastboot method.
Sent from my device running CyanogenMod 11

SafinWasi said:
??? I'll take a look at it. And do try fastboot method.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Sorry, I meant adb in fastboot mode.
Could be device specific, I suppose. @Maromi's kernel breaks my power button. Weird. [emoji51]

Also, I'm running ext4, but I didn't read anything about f2fs in the op.

Not booting past the blue logo for me, either. I tried on F2FS since the guy above said he was on EXT4. It's a dud.
Edit: I am able to boot into recovery and change the file system. I am unable to do much more.

BookCase said:
Not booting past the blue logo for me, either. I tried on F2FS since the guy above said he was on EXT4. It's a dud.
Edit: I am able to boot into recovery and change the file system. I am unable to do much more.
Click to expand...
Click to collapse
Reflash your rom to get back to booting. You should be able to do it dirty.

Rushead said:
Reflash your rom to get back to booting. You should be able to do it dirty.
Click to expand...
Click to collapse
I wiped data when I changed the file system and can't seem to get the kindle to mount in recovery to my PC. I have to remember how to push the files with adb, I think. lol
Anyone know how to install the ADB Drivers to use adb in recovery?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know the fastboot and adb drivers are different and I know you can adb from the device while on a ROM but, the adb drivers for recovery are different. Normally, I would right-click on My Computer > Manage > Device Manager & there is a yellow triangle like the one you see in this image above, I right-click on that and select "update driver software". If it doesn't find it automatically, then I > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Android device > Android Composite ADB Interface. But, that isn't working for me at this time. Any ideas?
EDIT: Found my answer HERE

Related

[MOD] White On Black Evo Splash Screen

Here is a Splash Screen i wanted to share with the community, It's simple just the original with inverted colors
Please enjoy.
As always please backup before trying, I won't be responsible for anything that may go wrong if this fails
and mods if this is posted in the wrong place please move thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To apply just unzip the contents of the package below into the tools folder of the android sdk
How-to Enter fastboot mode .... While the phone is off hold down "Volume down key" and then "power button" hold both till you get a white screen with the androids and skateboards
to confirm your device is seen by adb use this command
Code:
fastboot devices
you should see your phone listed under the command you just typed. After that type the next command to flash the splash image
Code:
fastboot flash splash1 splash1.nb
Then you should see that it was successful and rebbot the phone and preview your new image by typing
Code:
fastboot reboot
Please Thank and post comments as needed, if there is any trouble i'll try to help if i can i'm rather busy lately...lol
There was a huge thread on how to change splash with win 7 and I am stuck in osx thanks for a tut on how to to it in fastboot
Thanks! I followed the instructions and applied it no problem. Makes booting up look seamless with Fresh's bootscreen
So I have been having nothing but problems with Sync, so have rooted, flashed and changed boot image by using a root file manager (which all have worked fine).
Where on the EVO is the splash screen logo located, so I can just manually apply it?
Thank you
Criim
Criimson said:
So I have been having nothing but problems with Sync, so have rooted, flashed and changed boot image by using a root file manager (which all have worked fine).
Where on the EVO is the splash screen logo located, so I can just manually apply it?
Thank you
Criim
Click to expand...
Click to collapse
I'm 99.9% sure that this image cannot be simply replaced in a folder but must be flashed, at least that's how it was for winmo
If you think about it this is where the carrier brands the phone the most, im pretty positive this is flashed to a specific partition
Am I missing something? I do everything step by step and it won't find fastboot command in the terminal (using OS X). I can't do anything.
JSZESZE said:
I'm 99.9% sure that this image cannot be simply replaced in a folder but must be flashed, at least that's how it was for winmo
If you think about it this is where the carrier brands the phone the most, im pretty positive this is flashed to a specific partition
Click to expand...
Click to collapse
Hmm that's too bad. My Vista sees my EVO, but it has an exclamation mark and the driver won't initialize no matter what I try.
Guess I'll wait till some other time then
Criim
Is there a way to flash from the EVO itself? I can copy files with no problem if I connect as a HDD.
add this file to the tools folder of android sdk or i think in OS x anywhere works as long as you direct the command line to it
Criimson said:
Hmm that's too bad. My Vista sees my EVO, but it has an exclamation mark and the driver won't initialize no matter what I try.
Guess I'll wait till some other time then
Criim
Click to expand...
Click to collapse
sounds like your in recovery and not fastboot
you should see the white screen with the androids riding skateboards once its there don't press anything on the phone
I can't connect to fastboot.
Code:
ERROR: could not get pipe properties
ideas?
JSZESZE said:
add this file to the tools folder of android sdk or i think in OS x anywhere works as long as you direct the command line to it
Click to expand...
Click to collapse
Awesome! Thanks man, I appreciate it. Looks great.
beautiful! thank you VERY much for this
JSZESZE said:
sounds like your in recovery and not fastboot
you should see the white screen with the androids riding skateboards once its there don't press anything on the phone
Click to expand...
Click to collapse
No it is in fastboot
From what I gather a lot of people have this issue with Vista 32bit and HTC Sync. I haven't been able to track down a solution. Even when trying to use Sync..it always just errors and says:
Unable to find HTC Sync on your PC. Please make sure.....
Kind of a pain, but so far I have been able to do everyting I want just doing it from the phone with files copied over. Using the terminal emu or file manager
Criim
imaxreed said:
I can't connect to fastboot.
Code:
ERROR: could not get pipe properties
ideas?
Click to expand...
Click to collapse
sounds like a permission issue... are you rooted and nand unlocked?
JSZESZE said:
sounds like a permission issue... are you rooted and nand unlocked?
Click to expand...
Click to collapse
should be. running caulkins rom custom recovery (amons) i have actually used fastboot before. any quick way for me to verify?
imaxreed said:
should be. running caulkins rom custom recovery (amons) i have actually used fastboot before. any quick way for me to verify?
Click to expand...
Click to collapse
in adb type
Code:
adb shell
then you should see
Code:
#
A $ prompt is the prompt for normal terminal ...
whereas:
a # prompt is the prompt for root (super user)
i am running osx and can access adb shell
http://imgur.com/t8MKg.jpg
does this look like the error?
$ fastboot devices
ERROR: could not get pipe properties
HTXXXXXXXXXX fastboot
i found a few things while googling the problem
most pointed to root issues
JSZESZE said:
does this look like the error?
$ fastboot devices
ERROR: could not get pipe properties
HTXXXXXXXXXX fastboot
i found a few things while googling the problem
most pointed to root issues
Click to expand...
Click to collapse
yes exactly. I haven't had a problem before this is strange.
Works great for me, no problems. This is a great way to save battery!
haha.

***ClockworkMod Touch recovery 5.8.0.2 available***

ClockworkMod Touch recovery 5.8.0.2 is now available for the HTC Desire
ALL CREDITS TO @Koush
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installing The Recovery
There are primarily three methods of installing a custom recovery to your phone. Please note that the first method is specific to ClockworkMod recovery only while the other two methods can be used for any custom recovery supported by your phone.
Using ROM Manager
Using Fastboot
Using flash_image
I still prefer the Fastboot method so these instructions are for Windows users, but the equivalent steps should work for mac and linux:
Open up a cmd window and go to your SDK tools folder. Now type
Code:
Code:
fastboot
and press enter. You should see a list of fastboot commands available. If you don't get that, you're probably not in the right folder. Check your path and where you installed the SDK and make sure you are in the /tools folder.
Once you've verified you can run fastboot, it's time to move the recovery image to the /tools folder (easier not to have to specify a path to the recovery file). I would also rename the recovery file to something short like recovery.img.
Once the recovery image is in the same /tools folder as fastboot, you'll need to put your phone in fastboot USB mode. To do this:
1) make sure the Fast Boot option is disabled. Note, this "Fast Boot" has nothing to do with the fastboot executable I've been talking about. This is a setting in Sense to allow the phone to boot up faster. To disable this setting, go to Settings > Power > Fast boot (uncheck the box).
2) Hold down the power button and select Power Off from the menu. Wait 1 minute for the phone to completely power off.
3) Boot into HBOOT. See this post for detailed instructions on how to boot into HBOOT:
How to boot into bootloader (HBOOT)
4) Once you're in HBOOT, you'll see it scan for a few files. This is normal. When it is done, you can make selections in the menu. Vol-UP and Vol-DOWN allows you to move up and down the menu list. POWER button acts as ENTER and selects whatever you're highlighted over.
By default, FASTBOOT is selected. So just press power.
5) now you should be in the FASTBOOT section of HBOOT. Plug the phone in via the USB cable to the computer where you installed the Android SDK. You should see the red FASTBOOT banner turn into FASTBOOT USB. If that doesn't happen, it means that your HBOOT drivers aren't working.
Your phone is now ready to accept commands from the fastboot executable that came with the Android SDK. Go back to that cmd window where we tested the fastboot command earlier. From there, issue the following command:
Code:
Code:
fastboot flash recovery recovery.img
Here's a quick explanation of the above command:
fastboot: that's the executable tool
flash: that's the function we want the fastboot tool to perform
recovery: this is the name of the partition we want to flash into. since we are flashing a recovery image, it needs to go to the recovery partition.
recovery.img: this is the name of the actual file to flash. Your filename may be different. Just make sure it matches the actual filename.
Fastboot will flash the image and give you a success/failure notification. If successful, you're all set. To check out the new recovery image, verify that BOOTLOADER is selected in the HBOOT menu (should be highlighted in blue). Press POWER button to select it. Now you should be back at the main HBOOT menu.
Use VOL-DOWN to highlight RECOVERY and press POWER button. The phone will now attempt to boot into the new recovery image.
You'll see the htc splash screen briefly and then the recovery image. That's it!
Nice....
Woow that is fast ....
I'm now running EXT4 touch. Lets give this a go.......
Nice work. Thanks.
Very Nice, ty
Thank you. Will try it tonight.
screenshots of recovery? what does this have over 4ext?
Anyone try it? the Ext4's lauching time is too long, whatever the touch version or classic version. I dont know why.
But the RMD 1. 034 is faster than that. I will try it this weekend.
Anyway, well done Yorzua!
Rastaman-FB said:
screenshots of recovery? what does this have over 4ext?
Click to expand...
Click to collapse
Reported by @koush himself as :
Currently, supported devices include (stay tuned, as I am updating this list as I build):
Samsung Nexus S
Samsung Nexus S 4G
Samsung Galaxy Nexus (CDMA and GSM)
HTC Desire
HTC Desire HD
HTC Evo
HTC Evo 3D (GSM and CDMA)
HTC Thunderbolt
Motorola Atrix 4G
But my thread here is for the HTC Desire only as i dont own the other devices.
The touch code is still beta, so please flash it, test it, report bugs and be patient
@yorsua, Where can I see the source code?
Did you just modify the recovery directory in the cm tree?
Rastaman-FB said:
screenshots of recovery? what does this have over 4ext?
Click to expand...
Click to collapse
Koush got this working just a couple of days ago. 4ext has the advantage of time and a fabulous dedicated developer
Was waiting for koush to get it working, so I can peep into the source.
If i install this recovery, can i still use my nandroid backups from an older version (4)
Cause I don't want to lose them.
"Backup may not be supported on this device. Skipping backup of sd-ext"
That's what I call useless. Interface itself is too plain. It has touch support, but that's it. It's not been tweaked to make use of its touch interface.
have an error while entering finale command, any ideas?
super_turbo said:
have an error while entering finale command, any ideas?
Click to expand...
Click to collapse
Are you s-off ?
nope its s-on
Sorry guys, i have been extremely busy at work and releasing my whatsapp mods
Droidzone said:
"Backup may not be supported on this device. Skipping backup of sd-ext"
That's what I call useless. Interface itself is too plain. It has touch support, but that's it. It's not been tweaked to make use of its touch interface.
Click to expand...
Click to collapse
As i wrote, the touch code on CWM is still a Beta.
So please flash it, test it, report bugs if you want.
Be patient
super_turbo said:
have an error while entering finale command, any ideas?
Click to expand...
Click to collapse
Must be S-OFF indeed !
Need s-off with patched hboot for fastboot commands.
I want to report a bug, not sure of the cause though
It's in my post
http://forum.xda-developers.com/showthread.php?t=1476978
ikidntu said:
I want to report a bug, not sure of the cause though
It's in my post
http://forum.xda-developers.com/showthread.php?t=1476978
Click to expand...
Click to collapse
Thanks for your testing and feedback.
Bug reported.
sjn01 said:
Anyone try it? the Ext4's lauching time is too long, whatever the touch version or classic version. I dont know why.
But the RMD 1. 034 is faster than that. I will try it this weekend.
Anyway, well done Yorzua!
Click to expand...
Click to collapse
Delete 4EXT Folder on SD and try it!
@OP, Did you notice that the official recovery build has been updated to 5.8.0.2? I wish you'd pull the faulty version you've attached here.

Best ROM to flash?

Hi I'm new to the Xoom and haven't gotten it rooted or unlocked yet (been trying no luck) but for when I do what ROM would you suggest me to install? Thanks in advanced
Sent from my SAMSUNG-SGH-I997 using xda premium
get rooted or get booted
deathblade said:
Hi I'm new to the Xoom and haven't gotten it rooted or unlocked yet (been trying no luck) but for when I do what ROM would you suggest me to install? Thanks in advanced
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
hello, and welcome. i suggest using this rom. its ICS and it's AWESOME!!!!! as for rooting. someone else can walk you through it. once you set up all the files (fastboot&adb) you'll be good to go with a few simple terminal commands.
here's a link to the team Eos ICS rom:http://forum.xda-developers.com/show....php?t=1426838
ENJOY
m!kelcz said:
hello, and welcome. i suggest using this rom. its ICS and it's AWESOME!!!!! as for rooting. someone else can walk you through it. once you set up all the files (fastboot&adb) you'll be good to go with a few simple terminal commands.
here's a link to the team Eos ICS rom:http://forum.xda-developers.com/show....php?t=1426838
ENJOY
Click to expand...
Click to collapse
Thank you, for the suggestion, and on the note of rooting, I've tried the command and I get stuck at the boot loader screen with nothing doing any thing, the computer says waiting on device and the Xoom just sis there at the dual core boot and the words starting fast boot services at the top left hand corner, and it doesn't do anything, I've tried this on two different computers, one using Ubuntu the other win 7 ultimate both do the same thing
Sent from my SAMSUNG-SGH-I997 using xda premium
Also link is down..
Sent from my SAMSUNG-SGH-I997 using xda premium
deathblade said:
Thank you, for the suggestion, and on the note of rooting, I've tried the command and I get stuck at the boot loader screen with nothing doing any thing, the computer says waiting on device and the Xoom just sis there at the dual core boot and the words starting fast boot services at the top left hand corner, and it doesn't do anything, I've tried this on two different computers, one using Ubuntu the other win 7 ultimate both do the same thing
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
make sure you have your adb & fastboot installed to C:/ and no sub folder (this makes sure everything is clean and no interferences). after that you must hard reset your xoom (hold in power button and vol up) than press vol up to access fastboot. after this navigate to your android SDK install directory and hold in left ctrl button and right click on the working folder and hit open cmd here.
also did you try the command fastboot devices? this lists the devices connected to your computer aka your xoom
here's a list of command just in case
Commands:
adb - Android Debug Bridge - One of the two things you'll need to know if you ever want to do anything non-conventional on your android based phone.
List of commands that can be used by adb can be prompted by typing adb at the system shell (command prompt or terminal)
Notable adb commands:
adb devices - If you don't know anything, this is the ONE thing you have to know.
adb devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
adb reboot (bootloader|recovery)
adb reboot - this will reboot your phone normally.
adb reboot bootloader - this will reboot your phone back into the bootloader (white screen with the android on wheels)
adb reboot recovery - this will reboot your phone back into recovery console (either default or amon_ra's recovery).
adb shell - this will shell into the phone and you can now explore the phone. Remember phone's native backend os is linux so know your linux commands.
adb remount - remounts the system partition on the phone so you can you read/write to it.
adb push xxx yyy - will push xxx file from computer into yyy location/file on phone (needs rooted access)
adb pull xxx yyy - will pull xxx file from phone into yyy location/file on computer (needs rooted access)
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Notable fastboot commands:
fastboot devices - If you don't know anything, this is the ONE thing you have to know.
fastboot devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
fastboot reboot - this will reboot your phone normally
fastboot oem unlock - this will unlock your bootloader - NOTE THIS WILL VOID YOUR NEXUS ONE WARRANTY
fastboot erase XXX - Will erase the partition XXX (such as userdata, cache) - mainly used for resetting phone and clearing userdata / factory settings.
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image.
e.g: fastboot flash system system_update.img will flash/update your system partition with an image called system_update
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
also here's a link to the official team Eos rom. this is the best rom by far out right now. loving it. my xoom runs so much faster than HC.
http://forum.xda-developers.com/showthread.php?t=1484770
---------- Post added at 02:02 PM ---------- Previous post was at 02:01 PM ----------
hi sorry.. had to get to ten posts XD
This is exactly what I did, I used adb to put in fast boot mode and used the command to try and unlock it, tried with files in c drive and in user profile, all just kinda sit there and say waiting on device, though about how long should I wait for it to unlock boot loader? And what will happen once it does, also I'm running Android v 4.0.3
Sent from my SAMSUNG-SGH-I997 using xda premium
IM stuck at this screen on the Xoom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here on my computer
Sent from my SAMSUNG-SGH-I997 using xda premium
Try a different USB cable? I had the same problem and changed the cable, problem solved.
I did and I even used two different computers with two different oses
Sent from my SAMSUNG-SGH-I997 using xda premium

HOW TO UNLOCK BOOTLOADER ON LENOVO TAB TB-7504X

I am using 'fastboot oem unlock' but
Erorr shows me
'fastboot (remote : unknown command)
How to solve this problem
???
Please help me
Download the latest version of fastboot & ADB.
You can see what version adb and fastboot you have installed, just open a command window and type: sudo adb --version (then hit enter) sudo fastboot --version (hit enter key) that will show your installed version of those tools. I believe right now the latest is 31.02 but I could be wrong. It is updated often and using an older release of adb and fastboot can and will cause issues..
Go here to download adb and fastboot. https://developer.android.com/studio/releases/platform-tools
Just download the android sdk for whatever OS you use on your computer, unzip...
What is the device you are trying to unlock? Have you enabled developer options on the phone and changed usb settings to file transfer instead of the default which is charging? Also have if that was done did you keep a close eye on your device because there will be a small box that pops up that must be immediately checkmarked so that your computer can communicate with your device. Have you selected "allow oem unlock"Also in the developer options? it might be good idea to set your lock screen to "none" instead of having a lock set for it. Any time anything is installed on a computer it almost always needs to be rebooted. If you have not done any of that I would suggest doing it all.
Also depending on what device you are attempting to unlock the bootloader on, the wording could be slightly different. My Pixel 4XL uses: fastboot flashing unlock , to unlock bootloader. So keep that in mind as well. If you use Windows OS on your computer some day when you have a minute check out Linux. You can make a "live USB" burn a copy of a Linux distro to a USB drive and boot from it and or install it along with your Windows OS, aka dual boot... The very first time I used Linux, it was Ubuntu and quite a few years ago and I would never return to Windows!! Can't stand it! Linux is made for doing what we do to our phones.
If you need more any help with this some other time and still cannot get it installed message me on here or should I say "start a conversation" with me here on xda. Same thing with the new layout.. My user name is the same here on XDA as it is on telegram. Feel free to shoot me a message any time. It may take a some time to respond depending on what day it is and what time and all that but I will respond.
Here is one of the best guides in my opinion on how to get and setup adb and fastboot tools on MAC, Linux and Windows OS. https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
(Edited)
flash713 said:
it is not working, same error after update.............
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MBF_9802 said:
View attachment 5323891
Click to expand...
Click to collapse
Try typing: sudo fastboot --version & sudo adb --version and make 100/% that they are most current and up to date. I'll go grab a link really fast...
Okay idk how you installed adb & fastboot but this guide in my opinion is the best!!! https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
Try using different ports, reboot your computer..
Did you already have the pop up on your device once connected to computer or no? If not your it won't work at all.
Enable developer options
USB debugging
Now plug in to a different USB port.
Now scroll down on phone to default USB configuration and change it from the default which is "charging" to "file transfer" but keep your eyes on your device screen because the pops up will only show itself for a few seconds. When it does checkmark the box. You should be good then. Windows has driver issues alot of the time!! I switched to Linux years ago and I have no driver issues. Or anything else far as that goes.
flash713 said:
Try typing: sudo fastboot --version & sudo adb --version and make 100/% that they are most current and up to date. I'll go grab a link really fast. Brb
Click to expand...
Click to collapse
MBF_9802 said:
View attachment 5323897
Click to expand...
Click to collapse
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
All try but reason only command not found
Please help......
flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
Same error in updated version
How to solve
MBF_9802 said:
Same error in updated version
How to solve
Click to expand...
Click to collapse
Did you ever onstll universal usb drivers for adb? If not install them and afterwards reboot your computer and then try.
flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
Same error in updated version
flash713 said:
Did you ever onstll universal usb drivers for adb? If not install them and afterwards reboot your computer and then try.
Click to expand...
Click to collapse
yes but same problem in universal usb drivers

[ROM] [11] PixelExperience for Alldocube iPlay30 / Pro(T1012 & T1012C) [UNOFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​PixelExperience for Alldocube iPlay30 / Pro(T1012 & T1012C)​Alldocube, please public kernel source according to GPL rules if you see this thread.​What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11​Whats working?
Wifi
RIL
Mobile data
VoLTE
GPS
Auto Brightness
Camera
Camcorder
Bluetooth
Sound
Stylus
Faceunlock
Selinux
Enforced
Known issues
You tell me.
DON'T FLASH GAPPS, ALREADY INCLUDED
Download
AFH
Donation
https://paypal.me/sjllls
Flashing and updating
*/* Unlock bootloader
1. Exit your google account.
2. Enable OEM unlock in developer settings.
3. Enable adb debug in developer settings.
4. Download latest adb driver from google, install it to make sure your PC recognized your pad in adb mode.
5. Download latest platform-tools from google.
6.Run with adb:
Code:
adb reboot-bootloader
7. Download latest fastboot driver from google, install it to make sure your PC recognized your pad in fastboot mode.
8. Run with fastboot:
Code:
fastboot flashing unlock
9. Unlock bootloader according the tissues on screen.
10. Pad will reboot and all data will be wiped
*/* Flash ROM
1. All files needed was uploaded to AFH, copy vbmeta.img and recovery.img to the rootdir of platform-tools.
2. Enable adb debug in developer settings.
3. Run with adb:
Code:
adb reboot-bootloader
4. Run with fastboot:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
fastboot reboot recovery
5. After entering recovery, you can control pad by volume keys and power keys, power keys is enter.
then choose Apply update - Apply from ADB
6. Connect your pad with PC via USB cable, then run with adb:
Code:
adb sideload <The-Path-of-ROM(Modify it according to your file path)>
7. Wipe data in recovery.
8. After finished flashing, reboot and enjoy.
If you met any issue, you need to try to flash this official ROM before flashing PE 11. (T1012 & T1012C)
iPlay30 Pro(T1012C)-Android10-210129. You can download from AFH.
Root permission
Sideload Magisk in recovery
Contributors
Sjll
Source Code:
ROM source: https://github.com/PixelExperience
Kernel source: Non, use stock prebuilt kernel.
ROM OS Version: Android 11
ROM Kernel: Linux 4.14
Version Information
Status: Stable
Created 2021-06-20
Last Updated 2021-06-20
Waw. Waiting for custom ROM for my alldocube. Do you mine to adding video how this ROM perform. Since I use my tablet for works what's the difference between this and stock.
Did it still have 4 axis orientation? Thank you before for your work
Hi, Thanks for the great work.
I installed the ROM and I encountered an issue that the tablet unable to adjust sound volume, it is always in maximum volume.
Thanks
ken1941716 said:
Hi, Thanks for the great work.
I installed the ROM and I encountered an issue that the tablet unable to adjust sound volume, it is always in maximum volume.
Thanks
Click to expand...
Click to collapse
I aleady fixed it, new build will be uploaded today after new build finish.
aiseno said:
Waw. Waiting for custom ROM for my alldocube. Do you mine to adding video how this ROM perform. Since I use my tablet for works what's the difference between this and stock.
Did it still have 4 axis orientation? Thank you before for your work
Click to expand...
Click to collapse
Orientation works.
Sjll said:
I aleady fixed it, new build will be uploaded today after new build finish.
Orientation works.
Click to expand...
Click to collapse
That's great, I will try to flash the tablet again tonight. Is it just go to recovery and use side load to push the ROM to tablet but without WIPE the data/cache?
Thanks again
0622 build uploaded, audio volume tweaking fixed.
ken1941716 said:
That's great, I will try to flash the tablet again tonight. Is it just go to recovery and use side load to push the ROM to tablet but without WIPE the data/cache?
Thanks again
Click to expand...
Click to collapse
Uploaded, yup , you do not need to wipe data if you do PixelExperience build update.
Sjll said:
Uploaded, yup , you do not need to wipe data if you do PixelExperience build update.
Click to expand...
Click to collapse
Great Thanks
ken1941716 said:
That's great, I will try to flash the tablet again tonight. Is it just go to recovery and use side load to push the ROM to tablet but without WIPE the data/cache?
Thanks again
Click to expand...
Click to collapse
Please let us know how it perform? Battery? Dual sim work? I'm using active stylus to take a note, is it palm rejection still working? Gesture navigation is it work in third party launcher? I'm still considering for install this ROM. Thank you in advance.
aiseno said:
Please let us know how it perform? Battery? Dual sim work? I'm using active stylus to take a note, is it palm rejection still working? Gesture navigation is it work in third party launcher? I'm still considering for install this ROM. Thank you in advance.
Click to expand...
Click to collapse
I feel the preformce is running smoother than stock rom, battery life seems no difference with stock rom.
However, I just use the tablet at home watch YouTube so I have not try dual sim and stylus
Hope this help
problem by installing ...."Total xfer: 1.00x" reinstall stock and new installation of PE with same result. device stucks in boot screen.
Groger said:
problem by installing ...."Total xfer: 1.00x" reinstall stock and new installation of PE with same result. device stucks in boot screen.
Click to expand...
Click to collapse
Did you wipe data in recovery?
Sjll said:
Did you wipe data in recovery?
Click to expand...
Click to collapse
yes wipe data done but no booting of device. the return to stock doesnt solve the problem, second machine, other cable, diff version of adb brings no booting...
Groger said:
yes wipe data done but no booting of device. the return to stock doesnt solve the problem, second machine, other cable, diff version of adb brings no booting...
Click to expand...
Click to collapse
Which stock firmware you flashed?
Sjll said:
Which stock firmware you flashed?
Click to expand...
Click to collapse
the verson which was installed by delivery "iplay30(T1012)-EN-20210119" the other from the op isnt available
Groger said:
the verson which was installed by delivery "iplay30(T1012)-EN-20210119" the other from the op isnt available
Click to expand...
Click to collapse
I provided the stock firmware I used, you might try it.
Sjll said:
I provided the stock firmware I used, you might try it.
Click to expand...
Click to collapse
thx,,,,,i will give it a try
(~47%) adb: failed to read command: Undefined error: 0
Same as rinat.nexus.
Tablet say "script succeeded: result was [1.000000]
Install completed with status 0.
Command prompt says
C:\android\platform-tools>adb sideload PixelExperience_iPlay30-11.0-20210622-0539-UNOFFICIAL.zip
serving: 'PixelExperience_iPlay30-11.0-20210622-0539-UNOFFICIAL.zip' (~47%) adb: failed to read command: No error
I have the same problem.
Can you help. I do not know.

Categories

Resources