Related
I believe I have a locked bootloader 0.03.12-ICS. I never could use any of the tools because I could never unlock my bootloader or replace it.
I was on Acer_AV041_A500_1.033.00_PA_CUS1 and I tried to flash a stock HC image 3.2 using the stock acer recovery. Then it quit booting. I have verified my cpuid and my sbk with afterota when it was still booting to the main os.
My only option at this point is to use the apx mode or fastboot option, I have tried the blackthund3r apx flashing tool v0.4, with several bundles but that never completes
I can only use the V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip
Here is the output of the first part of the v8.bat script from the v8 zip that is out there,
Loading bootloader...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0428018042bf1197
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (cod
e: 14) message: nverror:0x4 (0x4) flags: 0
What am I doing wrong? I have been trying for 4 months to change roms on this thing, but I never have been past the rooting stage with the ICR_Rooting scripts. I never could flash a recovery that wasnt the stock.
Now I dont even have a working tablet.
Join the club >< I'm trying to get the people who solved this problem to help me fix mine so I can write a tutorial. Anyone who can help me map out the bad sectors and create a dummy partition please let us know! Seems like everyone is falling victim to this issue lately.
Sent from my SAMSUNG-SGH-T769 using xda premium
dudeuh said:
I believe I have a locked bootloader 0.03.12-ICS. I never could use any of the tools because I could never unlock my bootloader or replace it.
I was on Acer_AV041_A500_1.033.00_PA_CUS1 and I tried to flash a stock HC image 3.2 using the stock acer recovery. Then it quit booting. I have verified my cpuid and my sbk with afterota when it was still booting to the main os.
My only option at this point is to use the apx mode or fastboot option, I have tried the blackthund3r apx flashing tool v0.4, with several bundles but that never completes
I can only use the V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip
Here is the output of the first part of the v8.bat script from the v8 zip that is out there,
Loading bootloader...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0428018042bf1197
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (cod
e: 14) message: nverror:0x4 (0x4) flags: 0
What am I doing wrong? I have been trying for 4 months to change roms on this thing, but I never have been past the rooting stage with the ICR_Rooting scripts. I never could flash a recovery that wasnt the stock.
Now I dont even have a working tablet.
Click to expand...
Click to collapse
Yr issue has been covered multiple times
- rooting does not give u the ability to flash a recovery.....rollback using timmydeans v4
dynospectrum said:
Join the club >< I'm trying to get the people who solved this problem to help me fix mine so I can write a tutorial. Anyone who can help me map out the bad sectors and create a dummy partition please let us know! Seems like everyone is falling victim to this issue lately.
Sent from my SAMSUNG-SGH-T769 using xda premium
Click to expand...
Click to collapse
Ppl are falling victim to this issue becoz they do not take the time to read things first....
There's a couple of very recent threads outlining the procedure u refer to
And an older thread describing how to
Its all beyond my small brain so I can't help u....."search fck partition "
Sent from my A500 using Tapatalk 2
This worked for me in your situation
dudeuh said:
I believe I have a locked bootloader 0.03.12-ICS. I never could use any of the tools because I could never unlock my bootloader or replace it.
I was on Acer_AV041_A500_1.033.00_PA_CUS1 and I tried to flash a stock HC image 3.2 using the stock acer recovery. Then it quit booting. I have verified my cpuid and my sbk with afterota when it was still booting to the main os.
My only option at this point is to use the apx mode or fastboot option, I have tried the blackthund3r apx flashing tool v0.4, with several bundles but that never completes
I can only use the V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip
Here is the output of the first part of the v8.bat script from the v8 zip that is out there,
Loading bootloader...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0428018042bf1197
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (cod
e: 14) message: nverror:0x4 (0x4) flags: 0
What am I doing wrong? I have been trying for 4 months to change roms on this thing, but I never have been past the rooting stage with the ICR_Rooting scripts. I never could flash a recovery that wasnt the stock.
Now I dont even have a working tablet.
Click to expand...
Click to collapse
I had what looks like the exact problem, used BABSECTOR from here http://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html and fixed my tab easily.
I edited the batch files by entering my sbk directly into them, (so I wouldn't have to retype & possibly make an error) but they worked for me. (To fix the same problem you have.)
Once you are able to write & format partitions again, you can follow various paths. The usually recommended path is TimmyDeans, or the HoneyComb 3.01 EUU from http://forum.xda-developers.com/showthread.php?t=1816560.
Both use the EUU method, both should work, Both take you back to HC, where you can follow the upgrade path on google play to get you back to stock 4.03. (It's a little more involved to get back to 4.03 with TimmyDeans.)
However, I found that I prefered to install this ROM http://forum.xda-developers.com/showthread.php?t=1969887 directly after running Babsector. Follow the directions exactly (including installing the correct bootloader) and you should be able to go from where you are now, (Only APX available) to a very nicely functionin ROM, in a lot!!!! less time than following the Stock upgrade path. (You
might make mistakes along the way, just start again, it will almost certainly work out.)
Coincidentally, this ROM will also give you OC, along with many other options, & is highly customizable, is still an ICS Rom, so doesn't suffer from the memory leak probs I believe affect all current versions of the hacked JB ROMS.
THANKS!
Danny2 said:
I had what looks like the exact problem, used BABSECTOR from here http://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html and fixed my tab easily.
I edited the batch files by entering my sbk directly into them, (so I wouldn't have to retype & possibly make an error) but they worked for me. (To fix the same problem you have.)
Once you are able to write & format partitions again, you can follow various paths. The usually recommended path is TimmyDeans, or the HoneyComb 3.01 EUU from http://forum.xda-developers.com/showthread.php?t=1816560.
Both use the EUU method, both should work, Both take you back to HC, where you can follow the upgrade path on google play to get you back to stock 4.03. (It's a little more involved to get back to 4.03 with TimmyDeans.)
However, I found that I prefered to install this ROM http://forum.xda-developers.com/showthread.php?t=1969887 directly after running Babsector. Follow the directions exactly (including installing the correct bootloader) and you should be able to go from where you are now, (Only APX available) to a very nicely functionin ROM, in a lot!!!! less time than following the Stock upgrade path. (You
might make mistakes along the way, just start again, it will almost certainly work out.)
Coincidentally, this ROM will also give you OC, along with many other options, & is highly customizable, is still an ICS Rom, so doesn't suffer from the memory leak probs I believe affect all current versions of the hacked JB ROMS.
Click to expand...
Click to collapse
I renamed the a 501.bat file to a.bat and ran it. Everything worked the way that it should have!!! Thanks, 4 months to get this thing going the way that I want.
Danny2 said:
I had what looks like the exact problem, used BABSECTOR from here http://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html and fixed my tab easily.
I edited the batch files by entering my sbk directly into them, (so I wouldn't have to retype & possibly make an error) but they worked for me. (To fix the same problem you have.)
Once you are able to write & format partitions again, you can follow various paths. The usually recommended path is TimmyDeans, or the HoneyComb 3.01 EUU from http://forum.xda-developers.com/showthread.php?t=1816560.
Both use the EUU method, both should work, Both take you back to HC, where you can follow the upgrade path on google play to get you back to stock 4.03. (It's a little more involved to get back to 4.03 with TimmyDeans.)
However, I found that I prefered to install this ROM http://forum.xda-developers.com/showthread.php?t=1969887 directly after running Babsector. Follow the directions exactly (including installing the correct bootloader) and you should be able to go from where you are now, (Only APX available) to a very nicely functionin ROM, in a lot!!!! less time than following the Stock upgrade path. (You
might make mistakes along the way, just start again, it will almost certainly work out.)
Coincidentally, this ROM will also give you OC, along with many other options, & is highly customizable, is still an ICS Rom, so doesn't suffer from the memory leak probs I believe affect all current versions of the hacked JB ROMS.
Click to expand...
Click to collapse
excellent post danny2, thanks so much for taking the time to write this up..
if its ok by you i would like to add it to the cpuid guide??
dibb_nz said:
excellent post danny2, thanks so much for taking the time to write this up..
if its ok by you i would like to add it to the cpuid guide??
Click to expand...
Click to collapse
Yes, feel free to do that, maybe just re-read & make sure it all is correct. I believe it to be correct info, but, as I have found the hard way, misunderstand one little instruction, and you get a mess.
---------- Post added at 06:27 PM ---------- Previous post was at 06:20 PM ----------
dudeuh said:
I renamed the a 501.bat file to a.bat and ran it. Everything worked the way that it should have!!! Thanks, 4 months to get this thing going the way that I want.
Click to expand...
Click to collapse
No problem, just want to make sure tho, you did also follow the instructions & ran the "b" batch file as well?
Team Win Recovery Project 3.0.2
Notice: This is a test build as a start to becoming an official build, I am looking for feedback right now - do not consider this stable!
I am currently looking for users to test all the features and report back with what works.
Quote the 2nd post and put a pass or fail in each of the [ ] boxes!
Please, if you can, post your recovery.log after doing the tests that fail, as well as dmesg.log
Code:
adb shell cat /tmp/recovery.log > recovery.log
adb shell dmesg > dmesg.log
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
https://idlekernel.com/twrp/kipper/ (temporary! THESE ARE TEST BUILDS!)
Find instructions on how to unlock and root your device with fastboot here:
https://twrp.idlekernel.com/devices/wileyfoxstorm.html (temporary device page - do not download from here!)
CHANGES
v3.0.2-0 - See here for the changes.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Brightness node not set (unknown location, join #twrp to help!)
Battery status possibly unknown
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
Device tree: https://github.com/jcadduono/android_device_wileyfox_kipper
Kernel sources: https://github.com/jcadduono/android_kernel_cyanogen_msm8916/tree/twrp-6.0
TWRP: https://github.com/omnirom/android_bootable_recovery
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Wileyfox Storm, Tool/Utility for the Wileyfox Storm
Contributors
jcadduono, The Team Win Recovery Project team
Source Code: https://github.com/jcadduono/android_device_wileyfox_kipper
Version Information
Status: Testing
Current Beta Version: 3.0.2-0
Beta Release Date: 2016-04-27
Created 2016-04-28
Last Updated 2016-04-29
TWRP functional checklist
Code:
Blocking checks
[ ] - Correct screen/recovery size
[ ] - Working touchscreen
[ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[ ] - Reboot to system
[ ] - ADB & ADB shell
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on :))
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level
Minor checks
[ ] - Reboot to bootloader
[ ] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
jcadduono said:
Code:
Blocking checks
[Pass ] - Correct screen/recovery size
[ Pass] - Working touchscreen
[ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[Pass] - Reboot to system
[ ] - ADB & ADB shell
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on :))
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level
Minor checks
[ ] - Reboot to bootloader
[ ] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
Click to expand...
Click to collapse
I really want to see this get done but I don't have time to test everything right now. Done some basic tests, will edit with the rest whenever I have the time to do so.
Hi, I'm on CM13 and i cannot maount microsdcard and usbotg in TWRP, any solutions?
aciupapa said:
Hi, I'm on CM13 and i cannot maount microsdcard and usbotg in TWRP, any solutions?
Click to expand...
Click to collapse
Flashed twrp-3.0.2-0-test3-kipper.img and found unable to use mirco SD card as available storage.
Previously had TWRP-2.8.7.0-kipper-recovery on device, however after updating to CM13 this was unable to find/use micro SD card as available storage too.
Marshmallow issue or recovery one.
To acces microsd and otg, you need to flash COS12.1.1, then it magically works. To use it on cm13 you need to backup cm13 install COS12 and resrore cm13 (yeah, complicated)
Sent from my Wileyfox Storm using XDA Labs
aciupapa said:
To acces microsd and otg, you need to flash COS12.1.1, then it magically works. To use it on cm13 you need to backup cm13 install COS12 and resrore cm13 (yeah, complicated)
Click to expand...
Click to collapse
So create a TWRP backup, install cos12 then simple restore the back and should work?
Yes. I use it like this now
Sent from my Wileyfox Storm using XDA Labs
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
But after flashing cos12 reboot into recovery ans check if partitons mount
Sent from my Wileyfox Storm using XDA Labs
aciupapa said:
Yes. I use it like this now
Sent from my Wileyfox Storm using XDA Labs
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
But after flashing cos12 reboot into recovery ans check if partitons mount
Click to expand...
Click to collapse
I Google for a TWRP cos 12.1.1.zip however no joy.
Fail to install via a custom recovery users advised.
The issue only occurred after I installed CM13, that's when TWRP couldn't find microsd storage.
Go to cyngn.com/support and look for zip withouth fastboot in name
Sent from my Wileyfox Storm using XDA Labs
aciupapa said:
Go to cyngn.com/support and look for zip withouth fastboot in name
Click to expand...
Click to collapse
Installed the none fastboot cos 12.1.1 zip via recovery, then let it run the install build, however when I rebooted into recovery I was unable to get the external sdcard to be accessible still.
Thanks for suggested fix. :good:
Idk, why, but it always helps me. have you rebooted phone after COS12 flashing?
aciupapa said:
Idk, why, but it always helps me. have you rebooted phone after COS12 flashing?
Click to expand...
Click to collapse
I made TWRP backup of my current CM13 ROM, then wiped all partitions except internal and external SD card storage. Installed cos12.1.1 zip within TWRP, then rebooted to let stock lollipop ROM initialised. Then rebooted to TWRP to find external SD still not found.
Maybe try reflashing twrp
aciupapa said:
Maybe try reflashing twrp
Click to expand...
Click to collapse
I tried reflashing TWRP-2.8.7.0 recovery, then twrp-3.0.2-0-test3-kipper, cm-13.0-20160305-recovery and final cm-12.1-none-sign-recovery.
None of them could find the external SD card only internal storage. Would love to say it worked however sadly not. When on stock lollipop 5.0.1 all the recovery storage paths worked, so you would think installing cos 12.1.1 zip would restore things.
Have noticed that the original boot loader has returned, but not the battery charging while powered down image that you see getting fuller if you hit the power button. The original one was much larger under stock.
What's the function of the image file compared to the zip one please?
cm-12.1-YOG7DAS2FI-kipper-boot-debuggable-a7322d8c3a.img
Did a final version get abandoned after the test 3 release?
Probably to less tests?
I loved TWRP on my good old S2 (which seems to have NAND rw corruption since last week). Now I have the Storm I would love TWRP on my device too, but it needs proper testing.
I'm wondering: what are the risks of testing this? I might be able to help.
Well I have the test 3 one running on my storm, no issue's found.
Ok thanks. I'll try flashing it.
Blinkin89 said:
Ok thanks. I'll try flashing it.
Click to expand...
Click to collapse
Link updated in next post
None test version here
Team Win Recovery Project 3.0.2-1
This is for the International SM-N930F/X, Duos SM-N930FD, and Korean SM-N930K/L/S Exynos models only! Do not flash on Snapdragon models!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy Note 7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WARNING #3: When using custom kernels on the Note 7, never turn off developer options or OEM unlock. If you do, you will lose all your data and have to flash a full stock firmware restore to use your device again!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxynote7exynos.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"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"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Do not ever turn off Developer Options or OEM unlock. Doing so will cause your device to refuse to boot and require a full factory restore.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for gracelte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] + [Power] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest Samsung Anti-Root Protection Removal zip.
Without exiting TWRP, transfer the samsung-antiroot-removal zip to your device over MTP* and flash it using [Install] in TWRP.
This zip will allow you to flash SuperSU versions earlier than 2.77 and use other rooting methods.
It uses a hex pattern (by Chainfire) replacement method in the kernel that simply disables the anti-rooting protection.
It will also disable the status bar notification about unauthorized changes.
It includes the functions of the no-verity-opt-encrypt zip.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-1 - Fix restoring of non-ext4 partitions, update f2fs drivers, update to BPID source & Linux 3.18.43, add 60% battery charging limiter
v3.0.2-0 - Official release on twrp.me
v3.0.2-0-b3 - Fix colors and use NTFS-3G
v3.0.2-0-b2 - Initialize new device tree based on Samsung OSRC N930FXXU1APGK kernel source.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (International): https://github.com/TeamWin/android_device_samsung_gracelte (android-6.0)
Device tree (Korea): https://github.com/TeamWin/android_device_samsung_graceltekor (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_universal8890 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy Note 7, Tool/Utility for the Samsung Galaxy Note 7
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_gracelte
Version Information
Status: Stable
Current Stable Version: 3.0.2-1
Stable Release Date: 2016-10-15
Created 2016-08-23
Last Updated 2016-11-08
jcadduono said:
Team Win Recovery Project 3.0.2-0-b2
This is for the International SM-N930F/X, Duos SM-N930FD, and Korean SM-N930K/L/S Exynos models only! Do not flash on Snapdragon models!
snip
Click to expand...
Click to collapse
For the current note 7 series, @jcadduono will be the primary maintainer. I will subscribe to this thread however, I will be getting the n930fd. Good job @jcadduono!
Thank you very much sir and i try now
Sent from my SM-N930F using Tapatalk
I am away from PC but will try later tonight or tomorrow. Meanwhile any N930F users face any issue or got bootloop after testing here is stock recovery and kernel based on N930FXXU1BPH6 to fix bootloop
http://d-h.st/cHao
Flash it with Odin for AP tab
I have faced this y'day while modifying CF auto root and experienced that it may fail initially to flash soon after Odin log showing Initializing - Fail
Repeated attempt should work.
...on your mark, get set, go! Bye bye Samsung Pay... again...
Nice to see you here, Im using your rom on my note 4, s6, next is note 7, but my note 7 is 930FD, 2sim, so I have to wait more...
dr.ketan said:
I am away from PC but will try later tonight or tomorrow. Meanwhile any N930F users face any issue or got bootloop after testing here is stock recovery and kernel based on N930FXXU1BPH6 to fix bootloop
http://d-h.st/cHao
Flash it with Odin for AP tab
I have faced this y'day while modifying CF auto root and experienced that it may fail initially to flash soon after Odin log showing Initializing - Fail
Repeated attempt should work.
Click to expand...
Click to collapse
lehongwang said:
Nice to see you here, Im using your rom on my note 4, s6, next is note 7, but my note 7 is 930FD, 2sim, so I have to wait more...
Click to expand...
Click to collapse
Yeah Samsung has so far only released APGK and not FD's BPH6. I don't know if the S7 bootloader changed that happened in BPH6 on G930 also applies to N930FD though, so this might work for N930FD just the same as N930F.
It works!
Whats the status on Canada/US models?
I have an N930W8, waiting patiently for root ^.^
Also, I remember having pretty bad wakelock / deep sleep problems with the Note 5 root, has that issue been figured out for Note devices? I remember having to use a modified SU and Dr.Ketans deep sleep fix in order to have my Note 5 sleep properly. Just wondering if this is still a thing or not ^.^
i23u8 said:
It works!
Click to expand...
Click to collapse
Awesome! If you have the time, join #twrp on irc.freenode.net and upload recovery.log for us from the build. We need to make sure everything is detected and pointed to the right locations, as well as features working.
Here's a checklist if you want to go through it for us as well:
Code:
Blocking checks
[ ] - Correct screen/recovery size
[ ] - Working touchscreen
[ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[ ] - Reboot to system
[ ] - ADB & ADB shell
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on :))
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Modem/Firmware/EFS (if applicable) partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level
Minor checks
[ ] - Reboot to bootloader
[ ] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
Use pass or fail in each box.
Data encryption/decryption will most certainly not work.
imatts said:
Whats the status on Canada/US models?
I have an N930W8, waiting patiently for root ^.^
Also, I remember having pretty bad wakelock / deep sleep problems with the Note 5 root, has that issue been figured out for Note devices? I remember having to use a modified SU and Dr.Ketans deep sleep fix in order to have my Note 5 sleep properly. Just wondering if this is still a thing or not ^.^
Click to expand...
Click to collapse
They will never receive TWRP support and it's unlikely that they will ever see root either, unless an engineering boot image is leaked similar to what happened with the S7, but being stuck on an old kernel for the rest of your devices life just to root is kind of crappy. Do advise selling it and buying an F or FD Exynos model.
Ok I can confirm - TWRP works
Root - No
Root didn't work may be because of I have updated to latest base PH6 and believe this base have some changes and issue reported on S7 on this base as well
Before this Y'day I have modified CF auto root based on PH6 recovery and sent log to CF as well tested file from CF as well. According to @Chainfire he is aware of this and he will first fix S7 issue and probably this should fix for us as well.
So game started and have to wait till new magic from @Chainfire
Again thank to @jcadduono and @bigbiff for great work. Again Thank you very much to all involved to this project behalf of N7 community.
Here attached logs.
PS : Very busy today and just arrived from out, couldn't resist to test. Will report more details later
Regards
Dr.Ketan
dr.ketan said:
Again thank to @jcadduono and @bigbiff for great work. Again Thank you very much to all involved to
Dr.Ketan
Click to expand...
Click to collapse
+1
thanks to all for your help!
Do I have to flash both SuperSU and no-verity? Or SuperSU alone is fine?
Also tried this on both APG7 and BPH6 and they bootloop.
Here are the results of the testing so far:
Status Blocking checks
Pass [ ] - Correct screen/recovery size
Pass [ ] - Working touchscreen
Pass [ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
Pass [ ] - Reboot to system
Pass [ ] - ADB & ADB shell
Pass [ ] - Flash zips in Install page
Pass [ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
Pass, yellow [ ] - UI colors (red/blue inversions)
Pass [ ] - Screen goes off (and back on )
Pass [ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
Pass [ ] - System, Data, Internal Storage, microSD card, and Modem/Firmware/EFS (if applicable) partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
Pass [ ] - Correct date
[ ] - MTP read/write
Pass [ ] - USB Mass Storage read/write
Pass [ ] - Set brightness level
Minor checks
Pass [ ] - Reboot to bootloader
Pass [ ] - Reboot to recovery
Pass [ ] - Power Off
Pass [ ] - Battery level
Pass [ ] - Temperature
[ ] - Encrypted backups
Pass [ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
It's works but no root
Sent from my SM-N930F using Tapatalk
i23u8 said:
Do I have to flash both SuperSU and no-verity? Or SuperSU alone is fine?
Also tried this on both APG7 and BPH6 and they bootloop.
Click to expand...
Click to collapse
Flash supersu on apg7 and see if boot
If not
Flash stock files I have provided on prev page
Flash twrp
Flash dm verify disabler
Now device will boot
Fixing screen colors, yellow should not be normal lol.
Okay what I want to know is:
Does USB-OTG work?
Does mounting and writing to NTFS work?
Does mounting and writing to exFAT work?
Does mounting and writing to f2fs work?
Does MTP work (microSD card)?
Does MTP work (format internal storage to mount data unencrypted after flashing opt-encrypt zip)?
Does USB Mass Storage button work in Mount page (with external SDcard) - allows oldschool access to microSD from PC?
Output of following commands from terminal:
Code:
ls -l /dev/block/bootdevice/by-name/
cat /proc/partitions
ls /dev/block
dr.ketan said:
Flash supersu on apg7 and see if boot
If not
Flash stock files I have provided on prev page
Flash twrp
Flash dm verify disabler
Now device will boot
Click to expand...
Click to collapse
Hi Dr Ketan, I've flashed APG and SuperSU and it didn't boot, it loops.
I'm able to recover the phone.
Hi jcadduono,
Does USB-OTG work? Yes it works.
Does mounting and writing to NTFS work? Yes, my external HDD on NTFS works.
Does mounting and writing to exFAT work? Yes it works, my USB-OTG is exFat.
Does mounting and writing to f2fs work? I didn't convert any of my storage.
Does MTP work (microSD card)? Yes, it works.
Does MTP work (format internal storage to mount data unencrypted after flashing opt-encrypt zip)? Yes it works before I make my first boot to system.
Does USB Mass Storage button work in Mount page (with external SDcard) - allows oldschool access to microSD from PC? Yes this works.
Apart from those I havent tested, booting to system and then booting back to TWRP, I lose access to the data partition and it looks like I need to re-wipe and install no-verity.
i23u8 said:
Apart from those I havent tested, booting to system and then booting back to TWRP, I lose access to the data partition and it looks like I need to re-wipe and install no-verity.
Click to expand...
Click to collapse
Is it encrypting again after installing no-verity zip? This was an issue on Exynos 7870 and if it's happening on 8890 that would be terrible. (they made it impossible to disable encryption on 7870)
Also, see if the colors are fixed in https://idlekernel.com/twrp/gracelte/twrp-3.0.2-0-b3-gracelte.tar.md5
They should be blue and black and grey, no yellow!
And check NTFS again, I removed kernel driver for pure ntfs-3g to see if I could trim it down a little and make NTFS more stable.
Just two things to add to previous report
1.flashing from USB storage working
2.adb and and shell working from recovery
I kind of liked the yellow, it looked more like Parallax-y.
Confirmed that the colors are back to the normal blue, black, gray combo.
I'm not able to recheck NTFS because I stepped away from my bag to attend to work for a few minutes (then back to reflashing).
{
"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"
}
Please read the instructions and notes before flashing anything. Don't ask me if you don't read the instructions.
Code:
###Disclaimer###
I am not responsible if your device will be damaged, broken, boot looping. YOU are choosing to make these modification.
WARNING:
IMPROPER FLASHING MAY POTENTIALLY BRICK YOUR DEVICE. SO PLEASE PROCEED AT YOUR OWN RISK. ME OR ANY OTHER DEVELOPER MENTIONED IN THIS POST WILL ASSUME NO RESPONSIBILITY FOR THIS.
DONATE ME HERE
Requirements
- Unlock bootloader
- For now Ticwatch S (Mooneye)
- Working adb/fastboot and driver
- Any FTP client to copy/read files to/from your watch (Optional)
HOW TO FLASH THE ROM
- Attach your devices to your PC and enable USB Debugging from settings menu
- Download the platform-tools (use either Linux or window..platform-tools-linux-Ticwatc-S.zip or platform-tools-windows-Ticwatch-S.zip) from the given links
- Unzip the folder- it includes boot.img, recovery.img and system.img
- For Linux run ./flash-all.sh
- For Windows double click on flash-all.bat
- Wait until your device reboot
- Done.. enjoy
HOW TO Flash Kernel/boot.img
- Attach your devices to your PC and enable USB Debugging from settings menu and follow the commands
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash boot boot.img
HOW TO ROOT
- Move SuperSU to your device. Use any FTP client to copy/read files to/from your device.
- Attach your device to your PC and enable USB debugging
- Reboot your device into TWRP recovery by following
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot recovery.img
- Now flash the SuperSu and reboot
- Open BusyBox and tap to install (Only if you flashed SuperSU FOR OLDER VERSION NOUGAT) and reboot
- Done. Don't forget to donate if you like my work, Thanks.
ROMs
ROM AND KERNEL FEATURES [6-MAY-2018]
- ROM is based on release WEAR OS S(Mooneye)-[NWD1.171211.002]
- All *apk system/data, system/app, Framework & priv-app zipalign & optimized for better RAM utilization
- Kernel is based on latest kernel source 3.18.24.Released (VERSION = 4,PATCHLEVEL = 18,SUBLEVEL = 24)
- Compiled WITH UBERTC 4.9.4 (gcc version 4.9.4(optimized) (UBERTC-4.9.4))
- forced-encryption disabled
- dm-verity removed/disabled
- Scheduler optimize/support for heterogenous multi-core
- Scheduler support for heterogenous multi-processor systems
- Enables the core control
- Multi-Cluster Power Management support
- Optimized the energy consumption for advanced multi-core SoCs including big.LITTLE.
- Multi-core scheduler enable/optimized
- APM driver updated reduce battery usage during sleeping
- A lot subsystems converted to use power efficient workqueues
- Serveral other patces to reduce battery usage
- Tweaked/optimized the scheduler to balance the load across all CPUs without any regards to the power costs
- Tweaked the scheduler to reduce/save power by scaling down the frequency of the CPUs or idling them,
- Tweaked to predict the best time to save power on the CPU without affecting performance
- Tweaked for Best Performance
- And many more can't remember
- clean and smooth
NOTE: FIRST BOOT GONNA TAKE SOME TIME. BE PATIENT
[Odexed ROM]-[For Linux User]-[6/MAY/2018]
[Odexed ROM]-[For windows User]-[6/MAY/2018]
------------------------------------------------------------
KERNEL/BOOT IMAGEs
-[6/MAY/2018]
Changelog
- See above
[Kernel/boot.img]6-MAY-2018
SUPERSU AND MAGISK FOR WEAR OS
Magisk Wear OS
BusyBox+SuperSU
Source/GitHub
-Source
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF WHISKY
DONATE ME HERE
Special thanks to:
If you can, donate and respect all the devs and enjoy
@Chainfire for great work in android
@Maxr1998 Big thanks for giving me knowledge and your great work for Asus Zenwatch_3 and your great github guide.
@topjohnwu for his great effort (Magisk)Thank you so much
@superR for the great kitchen
@Xmaster24 for system-less root-
Please always support devs and others (soon).
XDA:DevDB Information
[ROM+Kernel][Ticwatch S(Mooneye)], ROM for the Smart Watches
Contributors
janjan, JANJAN
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Stable Release Date: 2018-05-06
Created 2018-05-06
Last Updated 2018-05-07
Thanks,
Will test on my semi-bricked watch to try it out.
ETA when upload be done?
I'm surprised this wasn't locked. Normally mods lock a dev topic if uploads haven't been posted.
GuyInDogSuit said:
I'm surprised this wasn't locked. Normally mods lock a dev topic if uploads haven't been posted.
Click to expand...
Click to collapse
I am uploading the kernel source and update the instructions.Be patient
janjan said:
I am uploading the kernel source and update the instructions.Be patient
Click to expand...
Click to collapse
I'm being patient. Just pointing out this fact.
Mega - invalid key
Yup, decryption key is invalid.
Flashed on Mac.
Fastboot flash boot "boot.img"
Fastboot flash system "system.img"
Fastboot flash recovery "recovery.img"
Booted in about 2-3 mins.
Loads bloat removed.
Crashed when trying to run Google assistant.
Updating apps now to test further.
So far my bricked watch is working.
Very happy, great job!!
I've got a TicWatch E.. Any chance I'll be able to do the same? I'd love to donate for mentored stuff on my ticwatch e.
basicreece said:
Flashed on Mac.
Fastboot flash boot "boot.img"
Fastboot flash system "system.img"
Fastboot flash recovery "recovery.img"
Booted in about 2-3 mins.
Loads bloat removed.
Crashed when trying to run Google assistant.
Updating apps now to test further.
So far my bricked watch is working.
Very happy, great job!!
Click to expand...
Click to collapse
Enjoy
janjan said:
Enjoy
Click to expand...
Click to collapse
Unable to donate?!
I get this message:
"We cannot process this transaction because there is a problem with the PayPal email address supplied by the seller. Please contact the seller to resolve the problem. If this payment is for an eBay listing, you can contact the seller via the "Ask Seller a Question" link on the listing page. When you have the correct email address, payment can be made at www.paypal.com."
Would like to send you few £$£$£$ as a thanks
basicreece said:
Unable to donate?!
I get this message:
"We cannot process this transaction because there is a problem with the PayPal email address supplied by the seller. Please contact the seller to resolve the problem. If this payment is for an eBay listing, you can contact the seller via the "Ask Seller a Question" link on the listing page. When you have the correct email address, payment can be made at www.paypal.com."
Would like to send you few £$£$£$ as a thanks
Click to expand...
Click to collapse
Really appreciate. It link from first op is working fine.
https://www.paypal.com/donate/?toke...0ftYFV0vcrGeAA0cdWiW&country.x=DK&locale.x=DK
janjan said:
Really appreciate. It link from first op is working fine.
https://www.paypal.com/donate/?toke...0ftYFV0vcrGeAA0cdWiW&country.x=DK&locale.x=DK
Click to expand...
Click to collapse
Sent over a little something, thanks again!!
basicreece said:
Sent over a little something, thanks again!!
Click to expand...
Click to collapse
Appreciate that. I have some whiskey now it will keep me work more and more and give me effort to bring something different in future for our ticwatch s and e.
I will collect some money to buy ticwatch E to work with and bring some thing for future.
Ì followed the steps on my Ticwatch E and it all worked out nicely.
Expected to run into something not working but after 2 days of heavy use i can only say i did not encounter any malfunctions or bugs on my Ticwatch E.
Noticably better then what was on it stock.
Keep up the good work
Only thing i did not think of was that when i reset and unpair watch from settings i would need to go through the steps mentioned for flashing all over again.
I'll have to use ADB next time and see to make phone and watch pair without restart watch and unpair..
(If you could come up with some amazing solutions for this, that'd be great! )
What if we want to take a backup of the existing system image on the watch first? Mobvoi support wont release a factory image download (or the support person I was dealing with had no idea).
Do we also lose reference to which watch we had after this? IE mine is Ticwatch S 0261?
I get the below when trying.
"fastboot oem" unlock done, I then needed to do "adb reboot-bootloader" before the flash script would run otherwise it just sits there waiting for a device.
Code:
< waiting for device >
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
< waiting for device >
error: cannot load 'boot.img'
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
error: cannot load 'recovery.img'
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
< waiting for device >
error: cannot load 'system.img'
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
< waiting for device >
Creating filesystem with parameters:
Size: 2603089920
Block size: 4096
Blocks per group: 32768
Inodes per group: 7952
Inode size: 256
Journal blocks: 9930
Label:
Blocks: 635520
Block groups: 20
Reserved block group size: 159
Created filesystem with 11/159040 inodes and 20879/635520 blocks
target reported max download size of 134217728 bytes
erasing 'userdata'...
OKAY [ 0.741s]
sending 'userdata' (42564 KB)...
OKAY [ 1.282s]
writing 'userdata'...
OKAY [ 5.851s]
finished. total time: 7.875s
Creating filesystem with parameters:
Size: 67108864
Block size: 4096
Blocks per group: 32768
Inodes per group: 4096
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 16384
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/4096 inodes and 1294/16384 blocks
target reported max download size of 134217728 bytes
erasing 'cache'...
OKAY [ 0.047s]
sending 'cache' (5176 KB)...
OKAY [ 0.219s]
writing 'cache'...
OKAY [ 0.770s]
finished. total time: 1.051s
Press any key to exit...
Fcukfame said:
Ì followed the steps on my Ticwatch E and it all worked out nicely.
Expected to run into something not working but after 2 days of heavy use i can only say i did not encounter any malfunctions or bugs on my Ticwatch E.
Noticably better then what was on it stock.
Keep up the good work
Only thing i did not think of was that when i reset and unpair watch from settings i would need to go through the steps mentioned for flashing all over again.
I'll have to use ADB next time and see to make phone and watch pair without restart watch and unpair..
(If you could come up with some amazing solutions for this, that'd be great! )
Click to expand...
Click to collapse
So what happened? Did you happen to reset the watch, and end up having to flash this again? Why? But it DOES work on the Ticwatch E?
Yes it does work. Really nice actually.
I did have to flash the rom again but that was my bad..
https://forum.xda-developers.com/an.../app-reset-wear-client-switch-phones-t3058962
Ubuntu Touch 16.04 For Xiaomi Mi3
/*
* I'm not responsible for bricked devices, dead SD cards, ecc...
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
Click to expand...
Click to collapse
Hello everyone! Today i'm here to share with you a porting of ubuntu touch done by me, i used halium to develop it, so thanks to halium group and for their support.
Requirements
-You can use which operating system do you want
-Adb & Fastboot tools, you can download it here.
-The phone needs to be updated to android 6 or higher.
-Download all the files in this folder: folder.
-TWRP recovery, you can found it here.
Ok, let's start!
-Unzip my file
-Reboot your phone to recovery mode and connect it to the pc
-Open a terminal or cmd and run this commands: adb push system.img /data/system.img and adb push rootfs.img /data/rootfs.img
-Once it is done click on reboot and click on bootloader.
-When you are on fastboot mode run this command: fastboot flash boot halium-boot.img and fastboot reboot
-Done!
The default username is: phablet and password is: 12345
When the phone turns on run this command "echo manual > /etc/init/rsyslog.conf" and reboot so the process which uses all the cpu won't start up.
For audio you need to run "pulseaudio --start"
Wifi is buggy(sometimes work and sometimes no), when you turn on your phone you need to run this commands to turn on wifi
-sudo -i
-echo 1 > /dev/wcnss_wlan
-echo sta > /sys/module/wlan/parameters/fwpath
P.S Remember. It has some bugs, some apps crashing, audio not working and camera don't work! (GSM works, you can also use data but you can't call someone and you can't receive calls; SMS works).
If someone can help me he can send me a mail or comment below.
Try it and send me some feedbacks! Thank you!
Update
I see your comments and i tried myself. Halium-boot.img and system.img were corrupted so i uploaded all the file instead of zipping them.
With the latest update run these command to reduce the cpu usage:
- sudo -i
- mkdir /etc/system-image/config.d
- Reboot the phone
Reserved
Thanks Mattia!
I will try to understand it.
And after I will try to install too.
小米MIX标准版4GB128GB银色MIUI10中国开发者8.8.13.
halium-boot.img error
Hi Mattia990!
Thank you very much for your work!
The halium-boot.img file flash after an error:
Code:
target reported max download size of 805306368 bytes
sending 'boot' (12956 KB)...
OKAY [ 0.421s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.425s
Update:
I tried to install the boot image with TWRP. It will not start in 20 minutes.
rajen77 said:
Hi Mattia990!
Thank you very much for your work!
The halium-boot.img file flash after an error:
Code:
target reported max download size of 805306368 bytes
sending 'boot' (12956 KB)...
OKAY [ 0.421s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.425s
Update:
I tried to install the boot image with TWRP. It will not start in 20 minutes.
Click to expand...
Click to collapse
You have to unzip my file, go into "Ubuntu Mi3 Funz", open terminal app and do fastboot flash boot halium-boot.img
rajen77 said:
Hi Mattia990!
Thank you very much for your work!
The halium-boot.img file flash after an error:
Code:
target reported max download size of 805306368 bytes
sending 'boot' (12956 KB)...
OKAY [ 0.421s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.425s
Update:
I tried to install the boot image with TWRP. It will not start in 20 minutes.
Click to expand...
Click to collapse
CONFIRMED
target reported max download size of 805306368 bytes
sending 'boot' (12956 KB)...
OKAY [ 6.521s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 35.141s
of course all 3 files unzipped IMG
and I've followed correctly your tutorial step-by-step
I think we have to leave these unnecessary circles on how to install fastboot with something we know about it.
We're trying Windows with the latest fastboot components so far, all files have been installed on all phones, but that's not the case. I'm sorry, now I can not ask Linux to try it there, at most in a virtual machine.
Files uploaded
Mattia990 said:
Files uploaded
Click to expand...
Click to collapse
SUCCESS with NEW files !!! THANKS !!!!
@Mattia990
next problem, when I typed to Terminal
echo 1 > /dev/wcnss_wlan
I got: -bash: echo: write error: Bad address - message
What can I do? coz defaultly no Wi-Fi...
JulianJenner said:
@Mattia990
next problem, when I typed to Terminal
echo 1 > /dev/wcnss_wlan
I got: -bash: echo: write error: Bad address - message
What can I do? coz defaultly no Wi-Fi...
Click to expand...
Click to collapse
I know it's a known problem.
Try the other commands
Mattia990 said:
I know it's a known problem.
Try the other commands
Click to expand...
Click to collapse
Okay.
Solved.
You must ignore the error message after the third command and move on to the fourth command.
Ok. Now Wi-Fi working.
---------- Post added at 05:08 PM ---------- Previous post was at 04:50 PM ----------
Ok. Last, but MAIN issue...
It have no incoming and outgoing calling... GSM is not working... for me.
You wrote: "...It has some bugs, some apps crashing, audio not working and also the camera doesn't work..."
Okay no sound...but it is not able to receiving calls without sound, nothing happened on screen when I call my number...
JulianJenner said:
Okay.
Solved.
You must ignore the error message after the third command and move on to the fourth command.
Ok. Now Wi-Fi working.
---------- Post added at 05:08 PM ---------- Previous post was at 04:50 PM ----------
Ok. Last, but MAIN issue...
It have no incoming and outgoing calling... GSM is not working... for me.
You wrote: "...It has some bugs, some apps crashing, audio not working and also the camera doesn't work..."
Okay no sound...but it is not able to receiving calls without sound, nothing happened on screen when I call my number...
Click to expand...
Click to collapse
Sorry i haven't tested GSM because i haven't got a normal sim. I will resolve it. Sorry for the incovenience.
Mattia990 said:
Sorry i haven't tested GSM because i haven't got a normal sim. I will resolve it. Sorry for the incovenience.
Click to expand...
Click to collapse
No problemo! This is alpha test.
it need 15-20 minutes for boot?
Edit: i had aosp android 9, i wipe system,data, cache and install ubuntu touch with adb on recovery then with fastboot.Rebbot and it no boot, i wait 40 minutes...
harris123424 said:
it need 15-20 minutes for boot?
Edit: i had aosp android 9, i wipe system,data, cache and install ubuntu touch with adb on recovery then with fastboot.Rebbot and it no boot, i wait 40 minutes...
Click to expand...
Click to collapse
I think it is not normal.
Running it on top of Lineage OS 14.1 and it works great (despite having the WiFi issue from time to time).
However, is there any way to decrease dpi, i.e. making UI elements bigger?
harris123424 said:
it need 15-20 minutes for boot?
Edit: i had aosp android 9, i wipe system,data, cache and install ubuntu touch with adb on recovery then with fastboot.Rebbot and it no boot, i wait 40 minutes...
Click to expand...
Click to collapse
If you have followed correctly my instruction i think the problem is android 9. Try to install android oreo or lower
the_MUKe said:
Running it on top of Lineage OS 14.1 and it works great (despite having the WiFi issue from time to time).
However, is there any way to decrease dpi, i.e. making UI elements bigger?
Click to expand...
Click to collapse
For the moment i think no
Dear @Mattia990
BT, GPS, Developer options are not switchable. These can not be turned on.
GSM not working if I call my phonenumber, I hear that ringing on the other side. But nothing happened on Ubuntu Phone: no ringing, no picture incoming call feedback...
If I try to make call, Phone application exits itself after a few seconds.
Communication with Windows PC is not working. Or I am not able to find this function When I went home I will try with my Linux laptop
Thats all for now...
...I hope you have enough time, patience, and your ability to fix these issues.
I am very proud and grateful of your work and big thanks for you because of this ROM. We are waiting for patiently.