Hi!
I create this litle software to install Virtual Gyroscope sensor in a easy way!
Just follow what is write in software!
I test it with TWRP and work 100% :good:
To use it just download it and extract the folder, open it and execute the shortcut, follow what is write in there!
Install_Virtual_Gyroscope_sensor.zip
https://mega.nz/#!RsZz3CyJ
Key: !gW5uVBsQDPtiRdElmkTlXHzD5Q3Xfin1RqDGCGJa0_E
Enjoy it! :highfive:
I think in this case, it would be easier to just link the zip, so that we could just flash it with TWRP. I'm guessing you got it from sokobans Blog?
Vinnipinni said:
I think in this case, it would be easier to just link the zip, so that we could just flash it with TWRP. I'm guessing you got it from sokobans Blog?
Click to expand...
Click to collapse
This?
No, i create this one.
.
It works in 7.1?
Enviado desde mi ALE-L21 mediante Tapatalk
peligropowers said:
It works in 7.1?
Enviado desde mi ALE-L21 mediante Tapatalk
Click to expand...
Click to collapse
7.1 gyroscope is enabled afaik
Ok.thnx
Enviado desde mi ALE-L21 mediante Tapatalk
Getting this.
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.
wackyleaks said:
Getting this.
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.
Click to expand...
Click to collapse
Phone is not recognised by adb. Try enabling USB-Debugging in Developer settings.
Now when i try again im getting this.
- exec '/system/bin/sh' failed: No such file or directory (2) -
adb: error: failed to copy 'android.hardware.sensor.gyroscope.xml' to '/system/etc/permissions': remote Permission denied
android.hardware.sensor.gyroscope.xml: 0 files pushed. 0.4 MB/s (806 bytes in 0.002s)
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.
wackyleaks said:
Now when i try again im getting this.
- exec '/system/bin/sh' failed: No such file or directory (2) -
adb: error: failed to copy 'android.hardware.sensor.gyroscope.xml' to '/system/etc/permissions': remote Permission denied
android.hardware.sensor.gyroscope.xml: 0 files pushed. 0.4 MB/s (806 bytes in 0.002s)
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.
Click to expand...
Click to collapse
Unlcok phone, there should be a USB-Debugging Pop-up. You need to allow the conection from your computer. And from what I see, you need root acces. No root = No Gyroscope. There is another way, but you need TWRP recovery. If you have TWRP, you could try rebooting to it and then go to mount and check system. Then try to run the programm again.
Vinnipinni said:
Phone is not recognised by adb. Try enabling USB-Debugging in Developer settings.
Click to expand...
Click to collapse
Its enabled the device is running twrp and is rooted
---------- Post added at 07:31 PM ---------- Previous post was at 07:29 PM ----------
Vinnipinni said:
Unlcok phone, there should be a USB-Debugging Pop-up. You need to allow the conection from your computer. And from what I see, you need root acces. No root = No Gyroscope. There is another way, but you need TWRP recovery. If you have TWRP, you could try rebooting to it and then go to mount and check system. Then try to run the programm again.
Click to expand...
Click to collapse
Its rooted USB debugg is enabled so i should just load twrp and plug usb in then run the software? Thats what I have done.
wackyleaks said:
Its enabled the device is running twrp and is rooted
---------- Post added at 07:31 PM ---------- Previous post was at 07:29 PM ----------
Its rooted USB debugg is enabled so i should just load twrp and plug usb in then run the software? Thats what I have done.
Click to expand...
Click to collapse
well, acually you should run it from the system. But if that doesn't work, you could try to go to twrp, mount system and then run the program.
Vinnipinni said:
well, acually you should run it from the system. But if that doesn't work, you could try to go to twrp, mount system and then run the program.
Click to expand...
Click to collapse
Tried both still getting
mount: Operation not permitted
adb: error: failed to copy 'android.hardware.sensor.gyroscope.xml' to '/system/etc/permissions/android.hardware.sensor.gyroscope.xml': remote Permission denied
android.hardware.sensor.gyroscope.xml: 0 files pushed. 0.2 MB/s (806 bytes in 0.004s)
chmod: /system/etc/permissions/android.hardware.sensor.gyroscope.xml: No such file or directory
umount: not root
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.
---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------
You dont have it as a .zip file so we can flash it?
wackyleaks said:
Tried both still getting
mount: Operation not permitted
adb: error: failed to copy 'android.hardware.sensor.gyroscope.xml' to '/system/etc/permissions/android.hardware.sensor.gyroscope.xml': remote Permission denied
android.hardware.sensor.gyroscope.xml: 0 files pushed. 0.2 MB/s (806 bytes in 0.004s)
chmod: /system/etc/permissions/android.hardware.sensor.gyroscope.xml: No such file or directory
umount: not root
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.
---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------
You dont have it as a .zip file so we can flash it?
Click to expand...
Click to collapse
https://yadi.sk/d/XjR7KlYPtSf4G Flash this zip. It's from sokoban, not from OP. It always worked fine for me.
Will this work for the p9 lite?
Vinnipinni said:
https://yadi.sk/d/XjR7KlYPtSf4G Flash this zip. It's from sokoban, not from OP. It always worked fine for me.
Click to expand...
Click to collapse
thank you !
how to install it?
why the sensor is not calibrated?
hi um installed it but my apps dont detect the gyro i got this output btw while installing
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
mount: '/dev/block/mmcblk0p38'->'/system': Device or resource busy
android.hardware.sensor.gyroscope.xml: 1 file pushed. 0.0 MB/s (806 bytes in 0.019s)
chmod: /system/etc/permissions/android.hardware.sensor.gyroscope.xml: Not a directory
umount: /system: Invalid argument
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.
In aida64 the gyro entry is blank
{
"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 btw i also tried an xposed based virtual sensor but that doesnt work with the app i want to use it with pls help
Related
Hey Samsung Galaxy tab users and devs.
So im' having a bit of a problem here trying to remount my galaxy tab so i can read/write to it. My cache size is the famous and well hated 25 MB file size limit so i wanted to change it by using this method:
http://forum.xda-developers.com/showpost.php?p=18840882&postcount=227
Im currently running gingerbread 2.3 with root priviliges, and Clockworkmod 3.0.5
{
"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"
}
[/URL] [/IMG]
Whenever i've try to use the remount command it get this error:
http://imageshack.us/photo/my-images/600/androidadb.jpg/
So what am im doing wrong? running WIn 7 64 bit and my tablet is set to usb debugging mode.
Been searching Google and XDA the couple of days but haven't found any solution.
In advance thanks, jakk212
Jakk212 said:
Hey Samsung Galaxy tab users and devs.
So im' having a bit of a problem here trying to remount my galaxy tab so i can read/write to it. My cache size is the famous and well hated 25 MB file size limit so i wanted to change it by using this method:
http://forum.xda-developers.com/showpost.php?p=18840882&postcount=227
Im currently running gingerbread 2.3 with root priviliges, and Clockworkmod 3.0.5
[/URL] [/IMG]
Whenever i've try to use the remount command it get this error:
http://imageshack.us/photo/my-images/600/androidadb.jpg/
So what am im doing wrong? running WIn 7 64 bit and my tablet is set to usb debugging mode.
Been searching Google and XDA the couple of days but haven't found any solution.
In advance thanks, jakk212
Click to expand...
Click to collapse
Hi Jakk,
I'm not a developer, but, the error seems indicate that adb can't remount as RW the /system, so:
1) adb shell work? (you must see a "#" if you are root)
2) have you installed busybox?
3) the 01newcache script in init.d directory work if you have a rom/kernel that suppor init.d
I use the script and i can confirm that work very fine
Bye
Idk
1) How am i able to see that? Should i see a # at the ADB CMD box? Root checker veryfies that my device is rooted.
2) Yes it's installed using V1.16.2androidminimal - updating now.
3) How can i check if my ROM supports that? My rom is the Stock safe Rom provided when flashing to Overcome.
Using the "adb shell" command in ADB gives me a $
using the adb shell command gives me the $ as i said.
When using the command su it gives me the # you're where talking about.
Jakk212 said:
using the adb shell command gives me the $ as i said.
When using the command su it gives me the # you're where talking about.
Click to expand...
Click to collapse
Though im still not capable of remounting my galaxy tab
Jakk212 said:
using the adb shell command gives me the $ as i said.
When using the command su it gives me the # you're where talking about.
Click to expand...
Click to collapse
Hi Jakk,
Yes, so you have a working superuser thats ok, but if you have stock kernel (i think) there isn't any init.d support so the only way is to try manually.
Another way is installing a custom rom (boca, overcome, etc..) or custom kernel that have init.d support.
Bye
Idk
---------- Post added at 02:01 PM ---------- Previous post was at 01:55 PM ----------
Jakk212 said:
Though im still not capable of remounting my galaxy tab
Click to expand...
Click to collapse
There is some errore message when you try to remount via adb? Try to remount filsystem directly in a root shell, here :
http://forum.xda-developers.com/showthread.php?t=859712
there is, at the end of first post, the instruction to mount r/o the /system
Bye
Idk
Hmm actually not sure that there is a custom kernel installed (i don't suppose since it's a stock firmware, then the kernel should be stock - dosen't allow me to overglock however xD )
I've get this message:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
30336CA087D400EC device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
# adb remount
adb remount
adb: not found
# remount
remount
remount: not found
#
Gonna try with to remount it directly in a root shell as you've said - see if that works.
I'll suppose that this is what im gonna write in adb?
Code:
> adb shell
# mount -o remount,rw -t rfs /dev/block/stl9 /system
# exit
Tried to flash the overcome kernel v3.3.1
Also i've connected the tab while in recovery mode now i get a ~$ when entering adb shell.
Jakk212 said:
Hmm actually not sure that there is a custom kernel installed (i don't suppose since it's a stock firmware, then the kernel should be stock - dosen't allow me to overglock however xD )
I've get this message:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
30336CA087D400EC device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
# adb remount
adb remount
adb: not found
# remount
remount
remount: not found
#
Gonna try with to remount it directly in a root shell as you've said - see if that works.
I'll suppose that this is what im gonna write in adb?
Code:
> adb shell
# mount -o remount,rw -t rfs /dev/block/stl9 /system
# exit
Click to expand...
Click to collapse
Hi Jakk,
1) adb is use only from PC (windows or linux), there isn't any adb command into android OS...
2) My mistake: read this links: http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html and http://forum.xda-developers.com/showthread.php?t=685146; the above command is about rfs (Samsung Robust File System); if you have converted the filesystem into ext4, i'm not sure that above command work....
sorry
Bye
Idk
Im am able to mount using the
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Command you told me about but when i try to push the newcache file
Code:
adb push 01newcache /system/etc/init.d/
it simply says:
adb: Not found
When trying to copy it outside the shell it says:
failed to copy "01newcache" to "system/etc/init.d/": Is a directory.
Jakk212 said:
Im am able to mount using the
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Command you told me about but when i try to push the newcache file
Code:
adb push 01newcache /system/etc/init.d/
it simply says:
adb: Not found
When trying to copy it outside the shell it says:
failed to copy "01newcache" to "system/etc/init.d/": Is a directory.
Click to expand...
Click to collapse
Hi,
if you try the adb into android phone shell, simply don't work because adb is a windows command (adb = android debug bridge).
The good is seems you have the init.d directory, so try this:
go to android phone shell and remount /system
in a windows cmd shell do this:
adb push 01newcache /system/etc/init.d/
return into android phone shell:
adb shell
cd /system/etc/init.d
chmod 777 01newcache
ls -l /system/etc/init.d (to show the contend of init.d)
exit
Bye
So you mean that i'll just simply open a cmd box without refering to adb and then use the adb push 01newcache /system/etc/init.d/ command? How's that gonna work?
If you've got the time could you please assist me over teamwiever or something similair?
Jakk212 said:
So you mean that i'll just simply open a cmd box without refering to adb and then use the adb push 01newcache /system/etc/init.d/ command? How's that gonna work?
If you've got the time could you please assist me over teamwiever or something similair?
Click to expand...
Click to collapse
Hi Jakk,
Rollback, read this:
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
The operation is in 2 steps, pc and android terminal: adb is pc side the rest in android terminal.
I'm sorry, i prefer forum support, i've no time at this moment.....
If i'm not clear enough please tell me, i don't know your skill level...
Bye
Idk
pretty skilled, gonna start my IT-technician education after christmas, and i've know a bit bat programming from working with windows server and also a bit html and php.
capable of flashing ROMS, unbricking etc but haven't used ADB before. I've configured adb the exact same way as the tut you've sent me.
However i still just get's error codes like adb not found, remount not found, Is a directory, or are you sure you are rooted?
Jakk212 said:
pretty skilled, gonna start my IT-technician education after christmas, and i've know a bit bat programming from working with windows server and also a bit html and php.
capable of flashing ROMS, unbricking etc but haven't used ADB before. I've configured adb the exact same way as the tut you've sent me.
However i still just get's error codes like adb not found, remount not found, Is a directory, or are you sure you are rooted?
Click to expand...
Click to collapse
Is working ?:
Code:
adb shell
If yes then:
Code:
su
mount -o remount rw /system
then - if you are not able to use "push" - copy the file in your SDcard then, while in adb shell:
Code:
cp /sdcard/yourfile /your-destination/
Seem easy
then which one am i going to choose? The overwrite?
and am i just supposed to write it like this:
cp /mnt/sdcard/01newcache /system/etc/init.d/
Because then i've get a cp can't create /system/etc/init.d/: Is a directory
Jakk212 said:
then which one am i going to choose? The overwrite?
and am i just supposed to write it like this:
cp /mnt/sdcard/01newcache /system/etc/init.d/
Because then i've get a cp can't create /system/etc/init.d/: Is a directory
Click to expand...
Click to collapse
Try this:
cp /mnt/sdcard/01newcache /system/etc/init.d/01newcache
Bye
If you have the init.d folder then just manul copy "01newcache" to your sd card and from your tab, with a root explorer (i use esfile explorer with root option enabled from option menu) copy it to system/etc/init.d.
...to solve the original problem...
I fixed this on my device from a windows command prompt by typing "adb root" , which restarts the daemon on the device with root permissions.
Photo by Logxen (aka not my trash!)
{
"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"
}
No warranties, no guarantees. If this ruins your device, your fault, not mine. Consider this a test build, backup important stuff manually to your PC for now (photos etc)
This requires an sdcard installed
[Image]
http://download.cunninglogic.com/cwr_ventana_2.img
39b5557cf3802d677e33cce76047ef60 *cwr_ventana_2.img
[Source]
https://github.com/CunningLogic/android_device_lenovo_ventana
[Instructions]
Code:
adb push cwr_ventana_2.img /data/local/
adb shell
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/cwr_recovery_2.img of=/dev/block/mmcblk0p1
[Credits]
djrbliss - For rooting the thinkpad
utkanos - walking me through the device config setup
CM, Koush and everyone who has worked on CWR
FIRST
yea, FIRST!
J/K, space reserved for future use.
Yo second!!!!!
Indeed. Thanks jcase and everyone else..
thanks!
Will check every hours this thread for image link
Thats fantastic! will try this as soon as an image file gets posted! Hopefully it wont be long till it will be running ICS!
Can confirm root as I'm currently running it on my tablet. Bliss did it himself and is going to package it and release it in a couple of hours.
Thanks to everyone for their hard work with this.
quyTam said:
thanks!
Will check every hours this thread for image link
Click to expand...
Click to collapse
Same here.
TS
Umm, I can't find a "HOW-TO-ROOT" thread.
Where is it??
yirsung said:
Umm, I can't find a "HOW-TO-ROOT" thread.
Where is it??
Click to expand...
Click to collapse
its not released yet waiting for confirmation for bounty collection
Sent from my ThinkPad Tablet using Tapatalk
Thanks for sharing this it worked great, except for the instructions I needed to use
dd if=/data/local/cwr_ventana_2.img of=/dev/block/mmcblk0p1
rather than
dd if=/data/local/cwr_recovery.img of=/dev/block/mmcblk0p1
to match the name of your file.
Thanks again for sharing, CWR seems to be running perfectly.
Also for those looking for root the exploit has been posted here.
Hello, can't install CWM. Made everything as in first post (but changed filename). After reboot tried to enter recovery mode, there was text on screen entering recovery or something but device booted to system and nothing happend. Whats wrong. Here is output of instalation:
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb push cwr_ventana_2
.img /data/local/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1298 KB/s (4452352 bytes in 3.347s)
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
su
# mount -o rw,remount /system
mount -o rw,remount /system
# echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
# dd if=/data/local/cwr_ventana_2.img of=/dev/block/mmcblk0p1
dd if=/data/local/cwr_ventana_2.img of=/dev/block/mmcblk0p1
8696+0 records in
8696+0 records out
4452352 bytes transferred in 1.903 secs (2339648 bytes/sec)
#
CWR test
did not seem to work . doesn't reboot in recovery but straight in normal boot
what info do you need to help debugging
redbaron said:
Hello, can't install CWM. Made everything as in first post (but changed filename). After reboot tried to enter recovery mode, there was text on screen entering recovery or something but device booted to system and nothing happend. Whats wrong. Here is output of instalation:
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb push cwr_ventana_2
.img /data/local/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1298 KB/s (4452352 bytes in 3.347s)
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
su
# mount -o rw,remount /system
mount -o rw,remount /system
# echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
# dd if=/data/local/cwr_ventana_2.img of=/dev/block/mmcblk0p1
dd if=/data/local/cwr_ventana_2.img of=/dev/block/mmcblk0p1
8696+0 records in
8696+0 records out
4452352 bytes transferred in 1.903 secs (2339648 bytes/sec)
#
Click to expand...
Click to collapse
have you tried usiing rom manager? ¿? I have not had the chance if not I would test currently backing up using titanium backup
Sent from my ThinkPad Tablet using Tapatalk
I installed it. It works. Though /sdcard cannot be found and backup doesn't work. But I'm sure these will be figured out in the near future
I've got it installed just fine and even got the back up files
Gonna do a clean install and then see about dumping the images
ClockworkMod Recovery boots for me and was backing up but failed while it was backing up /data for me (I have tried twice now). It seems to backup /system just fine though, I don't know why it would fail during the /data backup. Has anyone else successfully made a backup yet?
failed to restart in recovery for me (exactly as redBaron)
Try to install CWM 3 times
OK, booting in recovery works fine, but NOT via Rom Manager !
(only by pressing and releasing vol+ button when booting)
jhankinson said:
Thanks for sharing this it worked great, except for the instructions I needed to use
dd if=/data/local/cwr_ventana_2.img of=/dev/block/mmcblk0p1
rather than
dd if=/data/local/cwr_recovery.img of=/dev/block/mmcblk0p1
to match the name of your file.
Thanks again for sharing, CWR seems to be running perfectly.
Also for those looking for root the exploit has been posted here.
Click to expand...
Click to collapse
Yes ... one has to take great care with naming files ... I did something similar and used Root Explorer to rename the cwr file correctly.
recovery
still not workign for me.
tried to re-install it a few times
when i boot in recovery with Vol++ i see the booting into recovery message and then after a second or so vibrate again and start normal boot
I am very excited to see this news - though i'm going to wait until there is a semi-stable, well establish path for Root. Hopefully this achievement leads to the Thinkpad Tablet getting much more attention, its a pretty badass tablet and should prove to be a pretty good performer once all the Lenovo crapware is tossed out. Glad I remained faithful and patient!
Here is a nood friendly tutorial for fastboot flashing the new CWM Touch Recovery .
Download the zip file attached and extract it anywhere .
LE:\\ You need ENG S-OFF and a rooted phone , too.
Your phone needs to be in debugging mode and you need the lastest usb drivers instaled . ( HTC Sync )
FLASHING VIA FAST BOOT :
Step 1 : Run Start Here.bat , a comand promt window will open.
Step 2 : Type in "adb reboot bootloader" . <This works on every rom , it will reboot in fastboot mod.>
Step 3 : After the phone rebooted in fastboot , type in "fastboot flash recovery recovery-clockwork-touch-5.8.0.0-ace.img" .
Step 4 : You have your Touch Recovery flashed .
UPDATE TO LASTEST VERSION :
Step 5 : Download and install "ROM Manager" from Android Market.
Step 6 : Open ROM Manager , and select "Flash ClockworkMod Touch".
Step 7 : Confirm your phone model and in about 20 seconds a message should appear "Successfully flashed ClockworkMod Recovery!" press ok and you are done.
FLASH VIA BOOTLOADER (Without enghboot) : //Thx. nteeb
nteeb said:
For those who don't have enghboot.
The recovery is flashable from bootloader if you pack it in a PD98IMG.zip.
I tried it,this is the zip,use if you want:
PD98IMG.zip
md5: E19E4461F73AB6449760D70AE906341D
Click to expand...
Click to collapse
If you are unable to flash recovery do this and try again : //THX. CostaTX
CostaTX said:
Connect phone via usb and turn on debugging/just charging
Open up cmd (eventually as administrator) and type in "adb shell"
Find out how your system partition is named: "cat /proc/mounts | grep /system"
Mount system partition write/read. replace the X's "mount -o remount,rw -t yaffs2 /dev/block/XXXXX /system"
Use the terminal emulator to install the recovery:
su
flash_image recovery /sdcard/touch.img (or whatever the recovery image is named)
remount the system partition again as read only "mount -o remount,ro -t yaffs2 /dev/block/XXXXX /system
and you're done
Click to expand...
Click to collapse
Donate to ClockworkMod for awesome job .
A new version of recovery (5.8.1.5) is available here: http://www.clockworkmod.com/rommanager
You can also use Terminal Emulator: (I prefer to place the .img file in the root of the SD card and rename the image to something simple like touch.img so I don't have to type the long name from my phone)
su
flash_image recovery /sdcard/touch.img (or whatever the recovery image is named)
reboot recovery
Enjoy!
hello, this method does n't work for me, tried in fastboot with adb, same.... it's showing "remoot error" or something lik that
Do you have S-off? That error usually indicates you do not, and it is required for this method... Any luck using Terminal Emulator, as described two posts above?
Sent from my BNTV250 using Tapatalk
winsettr said:
You can also use Terminal Emulator: (I prefer to place the .img file in the root of the SD card and rename the image to something simple like touch.img so I don't have to type the long name from my phone)
su
flash_image recovery /sdcard/touch.img (or whatever the recovery image is named)
reboot recovery
Enjoy!
Click to expand...
Click to collapse
Hey dude. This method doesn't work for me.
I keep getting a message saying 'flash_image: not found'.
I have placed the image on the root of the sd card as well as in the original download folder. Neither location works.
{
"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"
}
Any ideas?
Greg.
Sent from my Desire HD using Tapatalk
Two thoughts: when you download the recovery image its actually named something like touch-recovery-ace-5.8.0.2.img; if you want to just type in touch.img in Terminal Emulator you need to rename the file that you downloaded. If you have already done this then you may not have busybox installed (CM and MIUI do, I don't know for sure about other ROMs). To test, from Terminal Emulator type "busybox"; if it's installed, you will get a list of available commands.
Sent from my BNTV250 using Tapatalk
works perfect, thx for the new recovery
winsettr said:
Two thoughts: when you download the recovery image its actually named something like touch-recovery-ace-5.8.0.2.img; if you want to just type in touch.img in Terminal Emulator you need to rename the file that you downloaded. If you have already done this then you may not have busybox installed (CM and MIUI do, I don't know for sure about other ROMs). To test, from Terminal Emulator type "busybox"; if it's installed, you will get a list of available commands.
Sent from my BNTV250 using Tapatalk
Click to expand...
Click to collapse
Hey dude.
I had indeed already renamed the file to touch.img.
I checked TE and I do seem to have busybox installed, I'm rocking RCMIX3D V4.
Curious.
Greg.
Sent from my Desire HD using Tapatalk
Also, I took the ***** way out and I bought the touch recovery, it's only £2.
Cheers,
Greg.
Sent from my Desire HD using Tapatalk
Supporting developers is never looked down upon, glad you are up and running!
Sent from my BNTV250 using Tapatalk
It did not work for me. i get these errors:
Code:
C:\Users\Jan>cd c:\touchrecovery
c:\TOUCHRECOVERY>fastboot flash recovery touch.img
sending 'recovery' (3554 KB)... OKAY [ 0.597s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.598s
c:\TOUCHRECOVERY>notepad
i ran cmd as admin but i still get the same error. when i try installing it via terminal emulator it also says "file not found". idea?
Do you have ENG S-off (different from just rooting)? That error usually indicates you do not, and it is required for the OP method... You might try updating Busybox (search Market for Busybox Installer) if you are sure when using Terminal Emulator that the path and filename are correct.
Sent from my BNTV250 using Tapatalk
I do have eng s-off . i was able to update the the recovery in the first place. i updated busybox and su-binaries as well but still got the same error. rebooted the phone just in case but still got the errors.
i can't say if it would have worked flashing via fastboot, now with the updated busybox. I'll give it a try when i'm back home. I believe it won't work neither. Maybe you got another idea?
edit: nothing changed using fastboot
So just to confirm, you only have this problem flashing the touch recovery, and can flash other versions of CWM just fine (using fastboot or terminal)?
Sent from my Desire HD using Tapatalk
Thanks for the guide, but I have a problem. When flashing the .img file, I get the following error:
sending 'recovery' (3554 KB)... OKAY [ 0.633s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.634s
I have S-OFF, but not ENG S-OFF. Is it possible to flash this without ENG S-OFF?
ROM Manager Premium says: "Error while downloading from server. Please make sure that you have a stable internet connection, and that your SD card is inserted and has free space!"
The internet connection and the SD card are of course all right...
Edit: I read that "Engineering HBOOT is required to flash the recovery area remotely." How can I flash the recovery on the phone (not remotely)?
winsettr said:
So just to confirm, you only have this problem flashing the touch recovery, and can flash other versions of CWM just fine (using fastboot or terminal)?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
i've tested flashing a non-touch recovery right now but nothing changed. i noticed that flashing a recovery via rom manager works without any problem.
I read a while back that some users (from a G1 forum, so may not be as helpful, but it's an idea) had to mount the recovery partition r/w manually from fastboot. I'll see if I can find the link... http://www.droidforums.net/forum/dr...e-busybox-flash_image-more-app.html#post87383
That might fix your error while flashing from fastboot, but it seems the issue with terminal emulator is that it's not recognizing the flash_image command. The above link also has instructions for installing flash_image which may be the key!
I downloaded this file: recovery-clockwork-touch-5.8.1.5-ace.zip
Is it safe to install this zip (which is a recovery) in recovery?
winsettr said:
I read a while back that some users (from a G1 forum, so may not be as helpful, but it's an idea) had to mount the recovery partition r/w manually from fastboot. I'll see if I can find the link... http://www.droidforums.net/forum/dr...e-busybox-flash_image-more-app.html#post87383
That might fix your error while flashing from fastboot, but it seems the issue with terminal emulator is that it's not recognizing the flash_image command. The above link also has instructions for installing flash_image which may be the key!
Click to expand...
Click to collapse
here ist what i did with that link
Code:
C:\TOUCHRECOVERY>adb shell
# cat /proc/mounts |grep /system
cat /proc/mounts |grep /system
/dev/block/mmcblk0p25 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
# mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p25 /system
mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p25 /system
# cat /sdcard/touch.img > /system/bin/touch.img
cat /sdcard/touch.img > /system/bin/touch.img
# chmod 755 /system/bin/touch.img
chmod 755 /system/bin/touch.img
# sync
sync
# mount -o remount,r -t yaffs2 /dev/block/mmcblk0p25
mount -o remount,r -t yaffs2 /dev/block/mmcblk0p25
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument
# mount -o remount,r -t yaffs2 /dev/block/mmcblk0p25 /system
mount -o remount,r -t yaffs2 /dev/block/mmcblk0p25 /system
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument
busybox was already installed so i skipped this part and started with installing the recovery right away. I don't know why i'm not able to remount the system partition as read only at the end. It looks like as if everything seems to have worked properly but the touch recovery is not showing up.
Okay I've done enough research before deciding to make this post but couldn't find any solution.
Situation is I tried to install CF3D using CWM and now I'm stuck at the black boot screen that says GT N7000.
I tried to log into ADB shell and execute /system/lib/cf3d_uninstall.sh since that is the general solution but it seems I do not have the file there. Can someone give me the sh file if they have or tell me how to remove the drivers manualls through the ADB shell so that I can boot back normally. I did not backup before doing this..and I guess today isn't my day! Please help me remove the drivers! It's a little urgent.
I am new to the ADB shell concept and these are the commands I executed after connecting:
adb devices
adb shell
su
ls -d */
cd system
cd lib
sudo cf3d_uninstall.sh
Here it says that the file isn't found.
Edit: Nevermind.. Restoring back to CM9 for tonight...
Click to expand...
Click to collapse
tried these ?
sh system/lib
sh /cf3d_uninstall.sh
Should I just execute the contents of this shellscript via ADB? I found these on Google Code
Code:
#!/system/bin/sh
mount -o rw -o remount /dev/block/mtdblock4 /system
stop
cat /system/lib/libGLESv1_CM_ORG_CF3D.so > /system/lib/libGLESv1_CM.so
chown 1000.1000 /system/lib/libGLESv1_CM.so
chown 1000:1000 /system/lib/libGLESv1_CM.so
chown system.system /system/lib/libGLESv1_CM.so
chown system:system /system/lib/libGLESv1_CM.so
chmod 644 /system/lib/libGLESv1_CM.so
cat /system/lib/libGLESv2_ORG_CF3D.so > /system/lib/libGLESv2.so
chown 1000.1000 /system/lib/libGLESv2.so
chown 1000:1000 /system/lib/libGLESv2.so
chown system.system /system/lib/libGLESv2.so
chown system:system /system/lib/libGLESv2.so
chmod 644 /system/lib/libGLESv2.so
#rm /system/lib/libGLESv1_CM_ORG_CF3D.so
#rm /system/lib/libGLESv2_ORG_CF3D.so
rm /system/lib/cf3d_uninstall.sh
rm /system/lib/cf3d_sh
reboot -f
reboot
reboot normal
toolbox reboot
busybox reboot -f
busybox reboot
busybox reboot normal
nokiamodeln91 said:
tried these ?
sh system/lib
sh /cf3d_uninstall.sh
Click to expand...
Click to collapse
Heya it says "Can't open 'cf3d_uninstall.sh' "
What Rom are you on?
nokiamodeln91 said:
What Rom are you on?
Click to expand...
Click to collapse
Ultimate N7000 XXLSC JellyBean 4.1.2 v5.1 ... And I really don't wanna reflash :/
Pl first try to locate where the cf3d files are and then run the command with right paths
[RESOLVED] CF3D Uninstall after boot loop
agvulcan said:
Okay I've done enough research before deciding to make this post but couldn't find any solution.
Situation is I tried to install CF3D using CWM and now I'm stuck at the black boot screen that says GT N7000.
I tried to log into ADB shell and execute /system/lib/cf3d_uninstall.sh since that is the general solution but it seems I do not have the file there. Can someone give me the sh file if they have or tell me how to remove the drivers manualls through the ADB shell so that I can boot back normally. I did not backup before doing this..and I guess today isn't my day! Please help me remove the drivers! It's a little urgent.
I am new to the ADB shell concept and these are the commands I executed after connecting:
adb devices
adb shell
su
ls -d */
cd system
cd lib
sudo cf3d_uninstall.sh
Here it says that the file isn't found.
Click to expand...
Click to collapse
Resolved (for me) :
I actually had the same error using the same command you did. You made a mistake though : when using an "sh" script, you have to invoke it's command, simply using "sh" before the name of the script you attempt to launch.
This is the way you have to go :
you should have typed : "sudo sh cf3d_uninstall.sh"
I actually managed to get it to work this way, and to stop boot loop / freeze (call it whatever you want), as it actually DID uninstall CF3D faulty drivers.
DO NOT USE CF3D with Jelly Bean, at the moment at least. Though Chainfire wrote he wouldn't develop anymore his drivers for JB, as it would need too much coding, again. Stick to GB or even ICS (it used to work for me)
--------
Full technique :
Prerequisites :
-CWM
-Aroma File Manager : Download it here :
Way to go :
-Take out your SD card from your device
-Copy Aroma FM to your Ext. SD Card using a microSD adapter (you can find one at any classical SD card retailer for a few bucks)
-Stick it back in your device
-Launch ClockWorkRecoveryMod
-"Install zip file"
-"Install from SD Card'
-Choose Aroma FM zip file, and install it.
-Tap on option key to get option menu, and launch the shell
-Then type :
su
cd system
cd lib
sh cf3d_uninstall.sh
Your device will automatically reboot, and boot your system normally.
See Ya
Chain Fire 3d boot loop .. not booting help plz ASAP
hello.. i am facing the same problem
i am using Panasonic T11, i had rooted it but it does not have any CWM,etc
when i installed Chain Fire 3d. it prompt me to reboot, bt it was boot looped, and i tried the ways u suggested
the problem its shows this errors in pic . plz suggest me something i can do about my phone
{
"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"
}
when i tried to go in recovery mode it shows ENTRY QPST DOWNLOAD
plz help me
{
"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"
}
Requirements
Android 10 firmware for your device:
Redmi 9A/9AT dandelion: LINK.
Dandelion
Download the latest fastbootable image: droidian-UNOFFICIAL-phosh-phone-xiaomi_dandelion-api29-armhf-nightly_XXXXXXXX.zip
Installation
Extract the archive
run the flash_all script
Boot to fastboot and let the script flash everything.
UBports Installer
Alternatively the UBports installer can also be used to install Droidian.
Notes
The default password is 1234.
List of working things can be found at https://github.com/droidian-mt6765/device-page
Bugs
Encryption is not supported.
Mobile data needs an APN to be set up from Settings -> Mobile -> Access Point Names.
RIL gets broken after switching airplane mode or modem off/on.
Mobile data might stop working after making or receiving phone calls. Toggle Mobile Data from the settins off/on.
Mobile data quick toggle doesn't work.
Bluetooth can be used via the terminal using bluetoothctl command or using blueman sudo apt install blueman but does not work via the settings app.
GPS works partially via Epiphany (tested with open street map).
Signal strength is reported at 1% but Mobile data and calls work just fine.
Anything related to cameras do not work it is a global issue across all devices, it does however work in Waydroid.
Changing audio to speaker in calls does not work on dandelion but works on angelica.
When a headphone is plugged in audio output must be changed manually in the settings.
Dual SIM functionality is currently not implemented in Phosh so only one SIM works at the moment.
Mobile hotspot does not work
Final notes
I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Support
Device specific telegram group: @ut_angelica.
Droidian telegram group: @DroidianLinux.
All the sources are available at
Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
All repositories related to Droidian on Redmi 9A/9AT and Redmi 9C/9C NFC (MT6765/MT6762) - Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
github.com
Attached images are from different devices but the interface looks and acts the same.
I cant flash this on the recovery touchscreen dont Work what can i do for fix?il dont know my type of redmi 9a the data code is m2008c3lg
laharl_22 said:
I cant flash this on the recovery touchscreen dont Work what can i do for fix?il dont know my type of redmi 9a the data code is m2008c3lg
Click to expand...
Click to collapse
recovery touchscreen? if you mean the rootfs or adaptation package you can sideload them
FakeShell said:
recovery touchscreen? if you mean the rootfs or adaptation package you can sideload them
Click to expand...
Click to collapse
I cant do nothing on orangefox recovery tested many times the touchscreen and mouse with otg nothing work only the power button
laharl_22 said:
I cant do nothing on orangefox recovery tested many times the touchscreen and mouse with otg nothing work only the power button
Click to expand...
Click to collapse
can you try some other recovery such as the pbrp?
i will edit the post and add a second installation method soon
Just added the second installation method
you can try that out now
FakeShell said:
Just added the second installation method
you can try that out
Click to expand...
Click to collapse
It fails at the last step install.sh no such file or directory but the dir of the script is mounted and chmod work .sorry for my double post
laharl_22 said:
It fails at the last step install.sh no such file or directory but the dir of the script is mounted and chmod work .sorry for my double post
Click to expand...
Click to collapse
my bad it was a typo in my documentation
redo the second installation method
cd /tmp/adaptation-garden-script && chmod +x install.sh && sh install.sh
mount: '/dev/block/loop10'->'/mnt/': Block device required
mknod: /dev/loop1: File exists
losetup: /dev/loop1=/data/rootfs.img: Device or resource busy
mkdir: '/rootfs': File exists
cp: bad './etc/systemd/system/pulseaudio.service.d/*': No such file or directory
cp: /rootfs/etc/udev/rules.d/: No such file or directory
cp: /rootfs/etc/pulse/: Is a directory
cp: /rootfs/etc/ofono/: Is a directory
cp: '/rootfs/etc/modules-load.d/' not directory
cp: /rootfs/etc/apt/sources.list.d/: No such file or directory
cp: /rootfs/usr/share/keyrings/garden.gpg: No such file or directory
chroot: exec /bin/bash: No such file or directory i have this at the final step
laharl_22 said:
cd /tmp/adaptation-garden-script && chmod +x install.sh && sh install.sh
mount: '/dev/block/loop10'->'/mnt/': Block device required
mknod: /dev/loop1: File exists
losetup: /dev/loop1=/data/rootfs.img: Device or resource busy
mkdir: '/rootfs': File exists
cp: bad './etc/systemd/system/pulseaudio.service.d/*': No such file or directory
cp: /rootfs/etc/udev/rules.d/: No such file or directory
cp: /rootfs/etc/pulse/: Is a directory
cp: /rootfs/etc/ofono/: Is a directory
cp: '/rootfs/etc/modules-load.d/' not directory
cp: /rootfs/etc/apt/sources.list.d/: No such file or directory
cp: /rootfs/usr/share/keyrings/garden.gpg: No such file or directory
chroot: exec /bin/bash: No such file or directory i have this at the final step
Click to expand...
Click to collapse
Can you drop me a message at @FakeShell at telegram?
because this seems to work and run fine on my 9A
have to troubleshoot a bit
FakeShell said:
Can you drop me a message at @FakeShell at telegram?
because this seems to work and run fine on my 9A
have to troubleshoot a bit
Click to expand...
Click to collapse
I think my device is corrupted on all zip i have error 1 and unable to mount storage i dont know why.i dont have telegram
laharl_22 said:
I think my device is corrupted on all zip i have error 1 and unable to mount storage i dont know why.i dont have telegram
Click to expand...
Click to collapse
you can try flashing back android
Where to write it: cd /tmp/adaptation-garden-script && chmod +x install.sh && ./install.sh ???
vipinc said:
Where to write it: cd /tmp/adaptation-garden-script && chmod +x install.sh && ./install.sh ???
Click to expand...
Click to collapse
in adb shell
FakeShell said:
View attachment 5665895
Requirements
Android 10 firmware for your device:
Redmi 9A dandelion: LINK.
Redmi 9C angelica: LINK.
Dandelion
Download the latest rootfs: droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip.
Download the adaptation package: adaptation-droidian-garden.zip.
Download boot-dandelion.img, dtbo-dandelion.img, vbmeta-dandelion.img.
Download our customized version of OrangeFox recovery OrangeFox-R11-garden-droidian.img
Angelica
Download the latest rootfs: droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip.
Download the adaptation package: adaptation-droidian-garden.zip.
Download boot-dandelion.img, dtbo-dandelion.img, vbmeta-dandelion.img.
Download our customized version of OrangeFox recovery OrangeFox-R11-garden-droidian.img
Dandelion installation
Flash boot-dandelion.img: fastboot flash boot boot-dandelion.img.
Flash dtbo-dandelion.img: fastboot flash dtbo dtbo-dandelion.img.
Flash vbmeta-dandelion.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-dandelion.img.
Flash OrangeFox-R11-garden-droidian.img: fastboot flash recovery OrangeFox-R11-garden-droidian.img.
Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.
Now boot into recovery.
Go into sideload mode and sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip: adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip
Go into sideload mode and sideload adaptation-droidian-garden.zip: adb sideload adaptation-droidian-garden.zip
Now boot into your device.
If for some reason sideload or recovery did not work out for you should try my second installation method:
Download the adaptation script (not the adaptation package): [adaptation-garden-script.zip] (https://garden.bardia.tech/adaptation-garden-script.zip).
Download PBRP: [PBRP-3.1.0.img] (https://garden.bardia.tech/PBRP-3.1.0.img)
Flash PBRP-3.1.0.img: fastboot flash recovery PBRP-3.1.0.img.
Now boot into recovery
Now extract adaptation-garden-script.zip on your PC/Laptop and push it to your device: adb push adaptation-garden-script /tmp
adb shell and Change directory to /tmp and run the script: cd /tmp/adaptation-garden-script && chmod +x install.sh && ./install.sh
Now boot into your device.
The first boot will take a while.
Angelica installation
Flash boot-angelica.img: fastboot flash boot boot-angelica.img.
Flash dtbo-angelica.img: fastboot flash dtbo dtbo-angelica.img.
Flash vbmeta-dandelion.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-angelica.img.
Flash OrangeFox-R11-garden-droidian.img: fastboot flash recovery OrangeFox-R11-garden-droidian.img.
Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.
Now boot into recovery.
Go into sideload mode and sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zipip: adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip
Go into sideload mode and sideload adaptation-droidian-garden.zip: adb sideload adaptation-droidian-garden.zip
Now boot into your device.
If for some reason sideload or recovery did not work out for you should try my second installation method:
Download the adaptation script (not the adaptation package): [adaptation-garden-script.zip] (https://garden.bardia.tech/adaptation-garden-script.zip).
Download PBRP: [PBRP-3.1.0.img] (https://garden.bardia.tech/PBRP-3.1.0.img)
Flash PBRP-3.1.0.img: fastboot flash recovery PBRP-3.1.0.img.
Now boot into recovery
Now extract adaptation-garden-script.zip on your PC/Laptop and push it to your device: adb push adaptation-garden-script /tmp
Change directory to /tmp and run the script: cd /tmp/adaptation-garden-script && chmod +x install.sh && ./install.sh
Now boot into your device.
The first boot will take a while.
Notes
The default password is 1234.
Xiaomi has not updated their kernel source tree and as a result some models of 9A and 9C have non functional display panels with our kernel.
Droidian GSIs are experimental! Bugs and missing features are expected.
List of working things can be found at https://garden.bardia.tech
Bugs
Mobile data needs an APN to be set up from Settings -> Mobile -> Acess Point Names.
RIL gets broken after switching airplane mode or modem off/on.
Mobile data might stop working after making or recieving phone calls. Toggle Mobile Data from the settins off/on.
Mobile data quick toggle doesn't work.
Bluetooth can be used via the terminal using bluetoothctl command or using blueman sudo apt install blueman but does not work via the settings app.
GPS works partially via Epiphany (tested with open street map).
Signal strengh is reported at 1% but Mobile data and calls work just fine.
Anything related to cameras do not work it is a global issue across all devices, it does however work in Waydroid which is currently not available on angelica and dandelion.
Changing audio to speaker in calls does not work on dandelion but works on angelica.
When a headphone is plugged in audio output must be changed manually in the settings.
Dual SIM functionality is currently not implemented in Phosh so only one SIM works at the moment.
Just like bluetooth, hotspot does not work from settings either and has to be used from a GUI application (such as the default advanced network app) or from terminal.
Flashlight can be used via the desktop icons only.
Final notes
I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Support
Device specific telegram group: @ut_angelica.
Droidian telegram group: @DroidianLinux.
All the sources are available at
Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
All repositories related to Droidian on Redmi 9A/9AT and Redmi 9C/9C NFC (MT6765/MT6762) - Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
github.com
Click to expand...
Click to collapse
Ow Lord, atomic bomb breaked myself on knees
+1
FakeShell said:
in adb shell
Click to expand...
Click to collapse
Hello FakeShell I have a kernel sources arm64 for redmi 9a can you compile and make droidian arm64
if you want i can upload the kernel sources
Hello bro
Your work is appreciable but i have a question that your droidian rom is based on Android 10 (Q) and it is became old in this big community Android 11 (R) and Android 12 (T) will (maybe) also release soon then who wants downgrade to an old android version from the latest android and latest security patches
My main question is that this rom droidian cant be based on latest android ?
the_arxyn said:
Hello bro
Your work is appreciable but i have a question that your droidian rom is based on Android 10 (Q) and it is became old in this big community Android 11 (R) and Android 12 (T) will (maybe) also release soon then who wants downgrade to an old android version from the latest android and latest security patches
My main question is that this rom droidian cant be based on latest android ?
Click to expand...
Click to collapse
This is a Linux OS its not an Android ROM they are very different. It uses the Android 10 vendor and kernel and thats it. the rest is done on droidian itself. The kernel we have right now is patched to work with all variants of dandelion, angelica and angelican thanks to TheKit and Muhammad. as we all know xiaomi did not update their kernel source for these devices (garden). but we have all the needed drivers that Xiaomi did not include. for vendor the reason it cannot be upgraded is that we don't use the android vendor the way you might think we do. the system partition is completely wiped and the OS is completely up to date so I will argue that right now Droidian is much more secure than android itself. upgrading to Android 12 is impossible right now as we don't have a general Halium container image for Android 12 but Android 11 is doable albeit a waste of time. because of how low end these devices are and the ram usage will increase without any benefit on our end.
The main concern right now is with the vendor being armhf which forces us to also work with armhf rootfs instead of arm64 (while the kernel is arm64!).
But then again arm64 vendor will also just increase memory usage and there are variants of garden with 2GB of memory which already suffer with armhf so at least for now arm64 is completely out of the question.