Has anyone been successful in flashing a splash screen? initially we had a nice black splash screen, but when flashing the ruu for VZW, we got a nasty bright white splash screen.
anyone tried this yet or attempted?
-4ndr01d- said:
Has anyone been successful in flashing a splash screen? initially we had a nice black splash screen, but when flashing the ruu for VZW, we got a nasty bright white splash screen.
anyone tried this yet or attempted?
Click to expand...
Click to collapse
On the M9 and before, the splash screen was in sp1.img. Now sp1.img is merely a black field. The splash screen is in \system\customize\resource, which means to access/alter it, you need to write to system. While I have always customized my splash screens on previous devices, I don't want to write to system just yet, so I'm stuck with stock.
I've been a little curious about this, I've changed the .png and have system permission but still doesn't change. There is a splash.nb0 in the firmware, not sure if that can be edited like on previous devices.
andybones said:
I've been a little curious about this, I've changed the .png and have system permission but still doesn't change. There is a splash.nb0 in the firmware, not sure if that can be edited like on previous devices.
Click to expand...
Click to collapse
I was wondering whether bind mount would work, the way xposed originally did (I haven't gotten that to succeed with a different boot animation).
Guess I'll just have to wait for the 1.8x OTA for Verizon, then flash a custom ROM after all.....systemless be damned. :good:
hgoldner said:
I was wondering whether bind mount would work, the way xposed originally did (I haven't gotten that to succeed with a different boot animation).
Guess I'll just have to wait for the 1.8x OTA for Verizon, then flash a custom ROM after all.....systemless be damned. :good:
Click to expand...
Click to collapse
I'm on my stock custom Verizon ROM and changed the splash.png before flashing and it didn't change. I haven't tried an international based ROM like LeeDrOid or Baadnewz but I'm thinking they will act the same.
I want to make a splash to test flash.
EDIT: I made a TEST splash. However I did not test it, as I don't know what's going to happen. I'm posting it so it's here. Maybe someone is sending their device back and can test it before they do so. Or possibly some brave soul willing to risk a device brick for us. Regardless, this is how I made it for my M7, M8, and M9 - but that doesn't mean it's going to work on the 10.
CAUTION THIS .ZIP HAS NOT BEEN TESTED, YOU HAVE BEEN WARNED.
If you want to test the splash screen here are the instructions:
1) Download this .zip - https://dl.dropboxusercontent.com/u/26383143/HTC/HTC 10/HTC10-Splash-TEST!!!.zip
2) adb reboot bootloader
3) fastboot oem rebootRUU
4) fastboot flash zip NameOfSplash.zip
5) fastboot reboot
CAUTION THIS .ZIP HAS NOT BEEN TESTED, YOU HAVE BEEN WARNED.
I have successfully changed my splash screen. I have the unlocked carbon grey HTC 10. it is S-OFF and converted to VZW
I used the batch tool from @Sneakyghost which can be found here
This is what I posted on how I changed my splash screen.
http://forum.xda-developers.com/showpost.php?p=67775626&postcount=389
JWhetstone02 said:
I have successfully changed my splash screen. I have the unlocked carbon grey HTC 10. it is S-OFF and converted to VZW
I used the batch tool from @Sneakyghost which can be found here
This is what I posted on how I changed my splash screen.
http://forum.xda-developers.com/showpost.php?p=67775626&postcount=389
Click to expand...
Click to collapse
I saved your splash file, placed it in dump folder that was created by the batch tool utility, ran the script, chose options 23 then 2 .... my phone rebooted and it is perfect! there is no longer any white splash screen
thanks!
What's everyone's phone?
Is it the branded Verizon phone or the unlocked then converted phone?
-HTC One m8-
JWhetstone02 said:
What's everyone's phone?
Is it the branded Verizon phone or the unlocked then converted phone?
-HTC One m8-
Click to expand...
Click to collapse
Mine's Verizon's version, running Verizon's current ROM, which is still 1.19.605.22. I have no idea when Verizon will approve the next OTA, but it's out there.....
hgoldner said:
Mine's Verizon's version, running Verizon's current ROM, which is still 1.19.605.22. I have no idea when Verizon will approve the next OTA, but it's out there.....
Click to expand...
Click to collapse
Yea, I'm not sure. I know the s-off procedure is different from the Verizon variant vs the unlocked. Well from what I remember, you had to send it in if you want to achieve full s-off for the Verizon device.
Maybe that has something to do with it. Otherwise the method I used should work, given you have USB debugging enabled.
-HTC 10-
JWhetstone02 said:
Yea, I'm not sure. I know the s-off procedure is different from the Verizon variant vs the unlocked. Well from what I remember, you had to send it in if you want to achieve full s-off for the Verizon device.
Maybe that has something to do with it. Otherwise the method I used should work, given you have USB debugging enabled.
-HTC 10-
Click to expand...
Click to collapse
I'm already S-OFF, bootloader unlocked and rooted (I did mail out my device to @beaups for the Sunshine treatment). I will try your approach to modify my sp1 partition (that's where the splash screen was on the M9).
andybones said:
I'm on my stock custom Verizon ROM and changed the splash.png before flashing and it didn't change. I haven't tried an international based ROM like LeeDrOid or Baadnewz but I'm thinking they will act the same.
I want to make a splash to test flash.
EDIT: I made a TEST splash. However I did not test it, as I don't know what's going to happen. I'm posting it so it's here. Maybe someone is sending their device back and can test it before they do so. Or possibly some brave soul willing to risk a device brick for us. Regardless, this is how I made it for my M7, M8, and M9 - but that doesn't mean it's going to work on the 10.
CAUTION THIS .ZIP HAS NOT BEEN TESTED, YOU HAVE BEEN WARNED.
If you want to test the splash screen here are the instructions:
1) Download this .zip - https://dl.dropboxusercontent.com/u/26383143/HTC/HTC 10/HTC10-Splash-TEST!!!.zip
2) adb reboot bootloader
3) fastboot oem rebootRUU
4) fastboot flash zip NameOfSplash.zip
5) fastboot reboot
CAUTION THIS .ZIP HAS NOT BEEN TESTED, YOU HAVE BEEN WARNED.
Click to expand...
Click to collapse
Splash Screens for Verizon are now a GO!
http://forum.xda-developers.com/verizon-htc-10/development/splash-screens-t3421314
hgoldner said:
I'm already S-OFF, bootloader unlocked and rooted (I did mail out my device to @beaups for the Sunshine treatment). I will try your approach to modify my sp1 partition (that's where the splash screen was on the M9).
Click to expand...
Click to collapse
ok, I wouldn't see why it wouldn't work. these are my steps
Phone: unlocked s-off htc 10 converted to vzw with latest firmware running viper 2.3.0 with usb debugging enabled
- download the batch tool from here
- install said batch tool (I think it was in a different language, but I took the default settings and it installed)
- found me an image, resized it to the correct dimensions (1440x2560) and saved it as the correct format for the batch utility to work (.bmp)
- placed the above image into the 'C:\Android\Dump' folder (this is where it should be if you took the defaults when installing)
- the program automatically started up after installing, but if it doesn't. you can open it from this location: 'C:\Android\Tasker_1.4.0.bat'
- I selected option 23 and then 2 (my phone was booted up to the OS and sitting on the home screen at this time)
- when the process finished, my phone rebooted and the white splash screen was gone
the image I used, I linked in my dropbox: splash.bmp
when you choose option 2 you should see some information like this:
Code:
Please pick an option: 2
converting BMP to raw and pushing to partition 21...
FFmpeg version SVN-r25512, Copyright (c) 2000-2010 the FFmpeg developers
built on Oct 18 2010 04:06:45 with gcc 4.4.2
configuration: --enable-gpl --enable-version3 --enable-libgsm --enable-pthread
s --enable-libvorbis --enable-libtheora --enable-libspeex --enable-libmp3lame --
enable-libopenjpeg --enable-libschroedinger --enable-libopencore_amrwb --enable-
libopencore_amrnb --enable-libvpx --arch=x86 --enable-runtime-cpudetect --enable
-libxvid --enable-libx264 --extra-libs='-lx264 -lpthread' --enable-librtmp --ext
ra-libs='-lrtmp -lpolarssl -lws2_32 -lwinmm' --target-os=mingw32 --enable-avisyn
th --cross-prefix=i686-mingw32- --cc='ccache i686-mingw32-gcc' --enable-memalign
-hack
libavutil 50.32. 3 / 50.32. 3
libavcore 0. 9. 1 / 0. 9. 1
libavcodec 52.92. 0 / 52.92. 0
libavformat 52.83. 0 / 52.83. 0
libavdevice 52. 2. 2 / 52. 2. 2
libavfilter 1.52. 0 / 1.52. 0
libswscale 0.12. 0 / 0.12. 0
Input #0, image2, from '..\dump\splash.bmp':
Duration: 00:00:00.04, start: 0.000000, bitrate: N/A
Stream #0.0: Video: bmp, bgr24, 1440x2560, 25 tbr, 25 tbn, 25 tbc
[buffer @ 0035fb00] w:1440 h:2560 pixfmt:bgr24
[ffsink @ 0035fce0] auto-inserting filter 'auto-inserted scaler 0' between the f
ilter 'src' and the filter 'out'
[scale @ 0035ff50] w:1440 h:2560 fmt:bgr24 -> w:1440 h:2560 fmt:rgb565le flags:0
x4
Output #0, rawvideo, to '..\dump\Splash1.nb0':
Metadata:
encoder : Lavf52.83.0
Stream #0.0: Video: rawvideo, rgb565le, 1440x2560, q=2-31, 200 kb/s, 90k tbn
, 25 tbc
Stream mapping:
Stream #0.0 -> #0.0
Press [q] to stop encoding
frame= 1 fps= 0 q=0.0 Lsize= 7200kB time=0.04 bitrate=1474560.0kbits/s
video:7200kB audio:0kB global headers:0kB muxing overhead 0.000000%
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
sending 'sp1' (7200 KB)...
OKAY [ 1.302s]
writing 'sp1'...
(bootloader) HOSD CL#749324
finished. total time: 2.351s
htc_fastboot finished. total time: 2.519s
rebooting, watch your new splash!
htc_fastboot v3.0.9.2 (2015-05-29)
rebooting...
finished. total time: -0.000s
htc_fastboot finished. total time: 0.147s
Press any key to continue . . .
hope this helps you and anyone else!
EDIT: Well, just seen andy's thread while I was typing this up. now every one has 2 ways about changing the splash image
LINK : splash screens by andybones
JWhetstone02 said:
ok, I wouldn't see why it wouldn't work. these are my steps
Phone: unlocked s-off htc 10 converted to vzw with latest firmware running viper 2.3.0 with usb debugging enabled
- download the batch tool from here
- install said batch tool (I think it was in a different language, but I took the default settings and it installed)
- found me an image, resized it to the correct dimensions (1440x2560) and saved it as the correct format for the batch utility to work (.bmp)
- placed the above image into the 'C:\Android\Dump' folder (this is where it should be if you took the defaults when installing)
- the program automatically started up after installing, but if it doesn't. you can open it from this location: 'C:\Android\Tasker_1.4.0.bat'
- I selected option 23 and then 2 (my phone was booted up to the OS and sitting on the home screen at this time)
- when the process finished, my phone rebooted and the white splash screen was gone
the image I used, I linked in my dropbox: splash.bmp
when you choose option 2 you should see some information like this:
Code:
Please pick an option: 2
converting BMP to raw and pushing to partition 21...
FFmpeg version SVN-r25512, Copyright (c) 2000-2010 the FFmpeg developers
built on Oct 18 2010 04:06:45 with gcc 4.4.2
configuration: --enable-gpl --enable-version3 --enable-libgsm --enable-pthread
s --enable-libvorbis --enable-libtheora --enable-libspeex --enable-libmp3lame --
enable-libopenjpeg --enable-libschroedinger --enable-libopencore_amrwb --enable-
libopencore_amrnb --enable-libvpx --arch=x86 --enable-runtime-cpudetect --enable
-libxvid --enable-libx264 --extra-libs='-lx264 -lpthread' --enable-librtmp --ext
ra-libs='-lrtmp -lpolarssl -lws2_32 -lwinmm' --target-os=mingw32 --enable-avisyn
th --cross-prefix=i686-mingw32- --cc='ccache i686-mingw32-gcc' --enable-memalign
-hack
libavutil 50.32. 3 / 50.32. 3
libavcore 0. 9. 1 / 0. 9. 1
libavcodec 52.92. 0 / 52.92. 0
libavformat 52.83. 0 / 52.83. 0
libavdevice 52. 2. 2 / 52. 2. 2
libavfilter 1.52. 0 / 1.52. 0
libswscale 0.12. 0 / 0.12. 0
Input #0, image2, from '..\dump\splash.bmp':
Duration: 00:00:00.04, start: 0.000000, bitrate: N/A
Stream #0.0: Video: bmp, bgr24, 1440x2560, 25 tbr, 25 tbn, 25 tbc
[buffer @ 0035fb00] w:1440 h:2560 pixfmt:bgr24
[ffsink @ 0035fce0] auto-inserting filter 'auto-inserted scaler 0' between the f
ilter 'src' and the filter 'out'
[scale @ 0035ff50] w:1440 h:2560 fmt:bgr24 -> w:1440 h:2560 fmt:rgb565le flags:0
x4
Output #0, rawvideo, to '..\dump\Splash1.nb0':
Metadata:
encoder : Lavf52.83.0
Stream #0.0: Video: rawvideo, rgb565le, 1440x2560, q=2-31, 200 kb/s, 90k tbn
, 25 tbc
Stream mapping:
Stream #0.0 -> #0.0
Press [q] to stop encoding
frame= 1 fps= 0 q=0.0 Lsize= 7200kB time=0.04 bitrate=1474560.0kbits/s
video:7200kB audio:0kB global headers:0kB muxing overhead 0.000000%
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
sending 'sp1' (7200 KB)...
OKAY [ 1.302s]
writing 'sp1'...
(bootloader) HOSD CL#749324
finished. total time: 2.351s
htc_fastboot finished. total time: 2.519s
rebooting, watch your new splash!
htc_fastboot v3.0.9.2 (2015-05-29)
rebooting...
finished. total time: -0.000s
htc_fastboot finished. total time: 0.147s
Press any key to continue . . .
hope this helps you and anyone else!
Click to expand...
Click to collapse
This unfortunately doesn't work on the Verizon variant. It would reboot but the Splash wouldn't change.
I took the plunge and used the old methods I used on M7, M8 M9 and it worked, which is nice as I like to do it using fastboot and creating the image myself (nothing against the batch tool)
http://forum.xda-developers.com/verizon-htc-10/development/splash-screens-t3421314/post67804699
Here is the output I got from the batch tool
Code:
[1] Pulls the Splash (mmcblk0p21) and converts it to a PNG file,
drops it into C:\Android\dump.
[2] Converts any correctly sized BMP into raw and pushes it to
the splash partition (mmcblk0p21). Make sure the BMP you use
has the right size of 1440x2560! Put BMP into C:\Android\dump!
[1] Pull Splash and convert PNG
[2] Convert bmp to raw and push to device
[3] Restore original Splash
[x] go back to main script
Please pick an option: 2
converting BMP to raw and pushing to partition 21...
FFmpeg version SVN-r25512, Copyright (c) 2000-2010 the FFmpeg developers
built on Oct 18 2010 04:06:45 with gcc 4.4.2
configuration: --enable-gpl --enable-version3 --enable-libgsm --enable-pthread
s --enable-libvorbis --enable-libtheora --enable-libspeex --enable-libmp3lame --
enable-libopenjpeg --enable-libschroedinger --enable-libopencore_amrwb --enable-
libopencore_amrnb --enable-libvpx --arch=x86 --enable-runtime-cpudetect --enable
-libxvid --enable-libx264 --extra-libs='-lx264 -lpthread' --enable-librtmp --ext
ra-libs='-lrtmp -lpolarssl -lws2_32 -lwinmm' --target-os=mingw32 --enable-avisyn
th --cross-prefix=i686-mingw32- --cc='ccache i686-mingw32-gcc' --enable-memalign
-hack
libavutil 50.32. 3 / 50.32. 3
libavcore 0. 9. 1 / 0. 9. 1
libavcodec 52.92. 0 / 52.92. 0
libavformat 52.83. 0 / 52.83. 0
libavdevice 52. 2. 2 / 52. 2. 2
libavfilter 1.52. 0 / 1.52. 0
libswscale 0.12. 0 / 0.12. 0
[bmp @ 01d8ed70] bad magic number
[image2 @ 01d8c0c0] Could not find codec parameters (Video: bmp)
..\dump\splash.bmp: could not find codec parameters
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
htc_fastboot v3.0.9.2 (2015-05-29)
andybones said:
This unfortunately doesn't work on the Verizon variant. It would reboot but the Splash wouldn't change.
I took the plunge and used the old methods I used on M7, M8 M9 and it worked, which is nice as I like to do it using fastboot and creating the image myself (nothing against the batch tool)
http://forum.xda-developers.com/verizon-htc-10/development/splash-screens-t3421314/post67804699
Here is the output I got from the batch tool
Code:
[1] Pulls the Splash (mmcblk0p21) and converts it to a PNG file,
drops it into C:\Android\dump.
[2] Converts any correctly sized BMP into raw and pushes it to
the splash partition (mmcblk0p21). Make sure the BMP you use
has the right size of 1440x2560! Put BMP into C:\Android\dump!
[1] Pull Splash and convert PNG
[2] Convert bmp to raw and push to device
[3] Restore original Splash
[x] go back to main script
Please pick an option: 2
converting BMP to raw and pushing to partition 21...
FFmpeg version SVN-r25512, Copyright (c) 2000-2010 the FFmpeg developers
built on Oct 18 2010 04:06:45 with gcc 4.4.2
configuration: --enable-gpl --enable-version3 --enable-libgsm --enable-pthread
s --enable-libvorbis --enable-libtheora --enable-libspeex --enable-libmp3lame --
enable-libopenjpeg --enable-libschroedinger --enable-libopencore_amrwb --enable-
libopencore_amrnb --enable-libvpx --arch=x86 --enable-runtime-cpudetect --enable
-libxvid --enable-libx264 --extra-libs='-lx264 -lpthread' --enable-librtmp --ext
ra-libs='-lrtmp -lpolarssl -lws2_32 -lwinmm' --target-os=mingw32 --enable-avisyn
th --cross-prefix=i686-mingw32- --cc='ccache i686-mingw32-gcc' --enable-memalign
-hack
libavutil 50.32. 3 / 50.32. 3
libavcore 0. 9. 1 / 0. 9. 1
libavcodec 52.92. 0 / 52.92. 0
libavformat 52.83. 0 / 52.83. 0
libavdevice 52. 2. 2 / 52. 2. 2
libavfilter 1.52. 0 / 1.52. 0
libswscale 0.12. 0 / 0.12. 0
[bmp @ 01d8ed70] bad magic number
[image2 @ 01d8c0c0] Could not find codec parameters (Video: bmp)
..\dump\splash.bmp: could not find codec parameters
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
htc_fastboot v3.0.9.2 (2015-05-29)
Click to expand...
Click to collapse
Interesting that you could not get Sneaky's batch tool to work for you.
I have a branded Verizon device, I sent in to Beaups for S-Off, Super CID 22222222.
I've used Sneaky's to change the splash on the release firmware months ago, and again on the latest firmware.
It was very quick and easy.
Regardless, I'm glad you got it figured out.
sdamark said:
Interesting that you could not get Sneaky's batch tool to work for you.
I have a branded Verizon device, I sent in to Beaups for S-Off, Super CID 22222222.
I've used Sneaky's to change the splash on the release firmware months ago, and again on the latest firmware.
It was very quick and easy.
Regardless, I'm glad you got it figured out.
Click to expand...
Click to collapse
Have same thing, vzw sent to beaups, supercid, I and another user with same settings also tested. Perhaps it was error on our part, not blaming the tool at all.
Def glad that white is gone.
So....I have a Verizon variant which I sent off for S-off and all the goodies, but can not follow the steps laid out by @andybones. The .bat is a no-go for mac users and my windows machine will be down awhile. Any tips???
mhuntwork1 said:
So....I have a Verizon variant which I sent off for S-off and all the goodies, but can not follow the steps laid out by @andybones. The .bat is a no-go for mac users and my windows machine will be down awhile. Any tips???
Click to expand...
Click to collapse
Give this tool a try to create your image
http://forums.androidcentral.com/ht...ng-custom-hboot-flashable-splash-screens.html
If doesn't work upload the image and I'll get it done for you.
andybones said:
Give this tool a try to create your image
http://forums.androidcentral.com/ht...ng-custom-hboot-flashable-splash-screens.html
Click to expand...
Click to collapse
Will do, thank you for your help and time
Related
枫影2.3.4ROM Made in China I have already Translated into English!!welcome everyone
Adaptation of models for the MOTO ATRIX all versions, such as the following:
ATT
China (including Hongkong, Taiwan)
The Republic of Korea
Canada
Australia
France
Britain
Italy
Singapore
Distinguish between simple version - the MOTO ATRIX series of only two version - International Version and the version of ATT, the list above, ATT is the ATT version, other all belong to the international edition.
Ha ha ~ ~ ~ ~ you are not wrong, is all versions, have been more tests, through the brush is so simple ~ ~ ~
But there are a few points I want the next state:
In 1, the version of MOTO official BELL version of 2.3.4 system, the latest version of the official.
In 2, I'm really sorry you, waiting for such a long period of time, my personal life is very busy with work, busy busy building completed, feelings, really busy, I'm sorry......
3, the use of the system need machine BL unlock, unlock the following information:
( 1) the International Edition ( most ): http: / / bbs.gfan.com / android-2002585 - 32771; ] ...
( 2) named Hong Kong Version ( the presence of a hard tile probability, so listed separately ): http: / / bbs.gfan.com / viewthread.php? T... 20284 ];
( 3) named Singapore Edition ( the presence of a hard tile probability, so listed separately ): http: / / bbs.gfan.com / viewthread.php? From = favorites t...
In addition, after my system in external a batch to install the recommended software and AD advertisement software projects, I hope everyone on my work can support, thank you!
PS: advertising software can be removed, the specific use of built-in RE manager, enter the / system / APP /, find all com. APK at the beginning of program, deleted, restart the machine, is so simple, if you are not willing to do, that also is not brush.....
My note:
I love to toss, especially in Android mobile phone, no matter what his models, as long as I like, I can put him in a good
System description:
[ ] take reading system
Version number: Maple Shade v3.4.4
System improvement:
1, No. 100 baseband, relatively the baseband signal and fever are quite considerable. ( due to the discovery of before China baseband and 2.3.4 system in compatibility problems, so this version to give up in the country such as baseband baseband, line officially launched the 2.3.4 to update the version is. PS : Celestial does not update.. ).
2, support for H +, you read that right, is the real H +, don't argue with me, have more tests to download faster than 6XX KB / S, not KBPS, this I know!
( H + distinction, due to geographical questions, UniCom of different regions to H + at different rates, for example, Changsha here, if you are old 186 card, the speed will be locked in the 3XX KB / S, if it is in Zhengzhou, faster than 620KB / S, if it is in Shanghai, faster than the 680KB / S, if Kunming, faster than the 1MB / S )
3, support operator custom [ default Chinese operators, if necessary, can go to / system / etc / spn-conf.xml automatically controlled to modify, and do not want to show, name blank can be ] ( last edition 3.4 I forget to maple shade modified reduction, this version fixes, you can freely modify )
4, support all Google official upgrade ( I was not in favor of ROM direct update Google applications, because it will lead to a new version will not be able to update! So please update the best, direct electron market update )
5, system settings - Voice: can be manually opened, closed, four big Jin'gang vibration; open, closed, SD card sound load; open, close button sound;
6, the system has Deodexed, and through the official GOOGLE SDK zipalign acceleration
In 7, ROOT perfect
In 8, the perfect Chinese SMS, MMS CDMA mutual
In 9, the operator APN information automatic setting
In 10, AGPS by default, give you the most awesome GPS positioning!!! Default 10 seconds [ ] preliminary positioning
In 11, China Unicom, China Mobile 's revised Chinese status bar logo
In 12, the default MOTO BLUR official regional [ if you cannot login account, please register again ]
13, remove the system comes with official procedures, some built-in celestial cannot use function, parts can be replaced with the official program application removal system cache, cleaning
14, continue to optimize the streamlined, kill the voice commands ( to use GOOGLE voice command instead), kill the input method, system flow.
15, authentic Chinese (Simplified Chinese, traditional Chinese, English special join ) the system more smoothly
16, to support the 3G / 2G network switching
17, to join the system browser can shield the spam address function
In 18, WEBTOP distortion correction, and support for WEBTOP, break out.
19, increase of HDMI function, break out.
20, change the HDMI output of 16 : 9 mode
21, speed up external SD card read and write speed, especially for high-speed SD card is very obvious! ( please use the SDTOOL tool to contrast after the upgrade and upgrade the former change! )
In 22, the built-in battery taskbar display accurate to 1%, program control, Chinese, can be set, this thing is very strong
23, adjust the base configuration, enhanced 3G signal receiving capability and network transmission rate
24, open set is installed inside the unknown source APK function, for the user to select mode ( simply can install the pirate )
25, cancel the network operator display hidden
26, support the follow-up version upgrade
Special update:
1 additional systems, automatic memory consolidation, is an excellent system for their own mode of management, not an additional third party software.
2, adjust the JAVA virtual engine for 64M mode, instead of the official 32M mode, more quickly.
3, support time localization, the default for the Beijing + 8.
In 4, the battery 1%
In 5, GTALK video chat support 3G, 2.5G, WIFI
6, optimizing kernel, run 3500 + ( OC kernel, please brush into the official kernel, default )
7, delete from official duty software, YouTube and some useful official software
8, repair lock screen (actually a software: phonesleep, this version 2.3 or later seemingly does not support 2.2 dedicated the lock screen. )
In 9, WEBTOP is the official version ( XDA MOD V2 version of the current brush is a bit of a problem )
10, optimize, accelerate fan speed and system effects switching speed, so that the smooth without delay
11, multi-touch default 4 ( thanks to michael0619 Research ) ( I found more than 5 points sometimes is not very stable, so to stable 4 touch )
12, brush machine fool simplification, automatic restoration of the international version of RAM loss problem
13, open the HDMI settings, open DESK settings, open the APN editor
14, open 32 color dynamic wallpaper support
15, support the volume keys to awaken
16, system support the hard solution MKV 1080P!!! ( if you do not believe, do try)
[ ] to measure
1, download the zip, unzip to C: \
In 2, when I provide drive, of course you drive too would not be
3, the system unlock BL ( above the unlock field notes and links)
In 4, the original system data backup, and to ensure that your built-in SD card available space at least 3G.
In 6, the compression package [ FengYingV3.4.4-AtrixMB860.zip ] files are copied to the built-in SD card under the root directory, please note, is built in the SD card!!!
7, turn off your mobile phone, press the volume down + power key = boot, until the display FastBoot, release the button, press the volume!
( if you have brushed my master R recovery system, please ignore this step )
( if you brush the custom RECOVERY system is not R master version, please replace the master version of R, because CWM 4.0.1 5 does not support the built-in version of the SD card brushing machine!!! Many brush machine success ERROR 7 this error is the problem!!! )
[ here is the master R version RECOVERY Download ] http: / / u.115.com / file / aqkfs7ed
Brush RECOVERY method, please refer to [ 1-3 ] brush machine step
8, plug the USB data line.
OK, is ready to finish.
[ Methods ] upgrade
( if you have brushed my custom recovery recovery system, please continue to ignore the step 1-3 )
( if you are a ATT version, the upgrade method is similar, but the file name is not the same, remember to separate )
1, enter C: \ moto-fastboot-win32 folder, double-click the [ Command Prompt ]
2, see the CMD page, enter the following command to brush into the recovery custom recovery system (note, if you unzip the file is not in the C: \, the command also need corresponding change; does not support Chinese )
Input:
Moto-fastboot flash recovery C: \ moto-fastboot-win32 \ recovery-en-0630-1029.img
RECOVERY recovery system into the brush finish; ( when you see the computer screen display similar XXX / s this information is said to have a good brush )
In 3, then the input moto-fastboot reboot, such as mobile phone automatic restart after entering a system, shutdown.
4, enter recovery mode ( press the volume down + power button to see the FastBoot, press the volume down, switch to an droid recovery, press the volume selection into )
( volume the next choice, the power button to determine )
5, into the recovery model, the corresponding selection:
( 1 ) the first choice of wipe data / factory reset, to empty the historical data (warning: if your recovery CWM-based version, empty when it will prompt you whether or not to empty the sd-ext data, choose! Otherwise your external data of the SD card will disappear! )
Upon completion, will automatically return to the home page
( 2 ) install zip from sdcard
( 3 ) choose zip from sdcard
Select internal SD card ( 4)
( in the external SD card, select external SD card, the useless)
( 5) choose the FengYingV3.4.4-AtrixMB860.zip package, determine, start brushing machine.
Wait patiently for the brush machine to complete, and then select go back has been rolled back to programs
Select the reboot system ( 6 )
6, clean system completed.
System version - FengYing-v3.4.4
Prompt.
In 1, GPS by default, please manually shut down can save electricity
2, if you don't like with advertising, please use the RE manager, enter the / system / APP /, all com. Love can be deleted.
( thank you for your support of my work, please delete before activation; personal recommendations deleted)
Special on how to save:
1, if you are not a developer, please shut down USB debug mode.
2, ibid, using the Android assistant, usually during shut down unnecessary background resident services.
3, setting - > battery management - > Settings: the most power ( when playing the game can be set to a general )
4, usually GPS goes situation, please remember to close the AGPS.
[ I found the differences, some friends, some friends said that energy saving electricity; but I think that if more than my instructions well, basically should be - power ]
Download address
MOTO ATRIX series of the latest drivers, all users please update ( currently in June 6th before the latest )
Http: / / u.115.com / file / bhaxhed8
-- -- -- --
The official U4_2.1.1 SBF bottom bag, please GOOGLE brush machine method, a lot of [ ] for people to spare
Http: / / u.115.com / file / aqpxa6uz
-- -- -- --
Moto-atrix-mb860-2.3.4 - v3.4.4 - Maple Shade released - brush pack!
Http: / / u.115.com / file / e65lnr5r
-- -- -- --
Moto-atrix-mb860-2.3.4 - v3.4.4 - ATT version of Maple Shade - released - brush pack!
Http: / / u.115.com / file / bhish38w
This ROM is made in China also it Built in English
please read it carefully,this ROM in china is very popular!
Has anyone gave this a try?
Sent from my MB860 using XDA Premium App
Screenshots?
I would be very careful when flashing this.
The reason being is that the author of this project has annouced a pull back of this version due to major bugs.
This will be updated soon and that will be the one I would flash, personally.
i wouldn't flash it because it's in the wrong damn forum =p
somethings fisheh
Sorry, but does that say there is mirroring in landscape mode through HDMI?
i cant make sense of most of it..... id like to see some screenshots! most likely wont flash though
Just googled his version number
I am interested in his HDMI 16:9 comment... did he get HDMI Mirror in Landscape?? IF so we need to find out how!!
Found some screens of this guys ROM...
Also a little more information that he did not post i the OP:
About OC core (OC kernel version update is expected on the 25th release):
The system comes with 2 cores and 2 OC native official kernel (thanks to XDA faux123 provided), are:
INTL-MBR-1100-GB-Kernel-0.1.2-ext4-sv.zip (RAM-1100 to adapt the sequence: a variety of optimization OC 1.1G kernel, CWM brush into the can)
INTL-MBR-d00-GB-Kernel-0.1.2-ext4-sv.zip (d00 of RAM to adapt the sequence: a variety of optimization OC 1.1G kernel, CWM brush into the can)
INTL-MBR-1100-original-kernel.zip (adapted for the 1100 series RAM: official native kernel)
INTL-MBR-d00-original-kernel.zip (d00 of RAM to adapt the sequence: the official native kernel)
Most people say why some ROM to run sub-3500 +, in fact, the role of these cores, but the negative effect is that power consumption increases, in fact, in addition to running at the different system fluency, I did not feel much different.
Therefore, the default is system's native kernel.
How to distinguish your phone is 1100 series or d00 series?See above Brush tutorial RAM hour repair parts, similar
On the lock screen, bright screen response speed adjustment instructions:
1, the default lock-screen, once again light up the screen time is about 250 milliseconds.
2, If you think this is slow, need be
3, using the [manager] RE modify / system / build.prop file, find: mot.proximity.delay = 250, modified = 100 to save, you can restart.
Brush on some friends unsuccessful Description:
1, check whether your RECOVERY R master version, and is 6-30 in English that day!
2, check the available capacity of your SD card if there is more than 3G?
3, check whether the copy to Brush package is built-in SD card?
4 Note: The system will automatically restore the machine RECOVERY master version of R, if you are CWM version, when you want to change the system, replace your own version of RECOVERY for the CWM.
Any brave souls willing to flash this and check for HDMI mirroring?
If it's there, maybe someone could pass it along to agrabren. He's got HDMwin working pretty stellar on the EVO 4G so this might be the big push we need to get it on the Atrix.
I'll give a shot,i just need to get this right. download the file with 3.4.4 version and flash it on recovery or install with rds or fastboot?
Sent from my MB860 using XDA App
aaron.a said:
i wouldn't flash it because it's in the wrong damn forum =p
somethings fisheh
Click to expand...
Click to collapse
cm7 its on general and a lot of people are using, give this ROM a shot too.
Sent from my MB860 using XDA App
Downloading from Chinese servers is slow.
slow? i get 8kbps, its more than slow! lol
Sent from my MB860 using XDA App
Actually getting around 80KB/s at points, might have this ROM by the end of next June
I have the file at home, got it last night took an hour to download ill upload it if you want me to tomorrow
Sent from my MB860 using xda premium
JaronBang said:
I have the file at home, got it last night took an hour to download ill upload it if you want me to tomorrow
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
we would appreciate if you did it
Sent from my MB860 using XDA App
Yeah ill do that, just hang tight ill have it up tomorrow.
Sent from my MB860 using xda premium
So I downloaded it. And I tried to flash it. And it aborted
Almost tried it but read that the link was pulled due to bugs. THanks for trying and posting though.
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?
Only fresh flashed bootloader locked XT1058 AT&T - ROM LPAS23.12-21.7-1, and XT1060 VZW - ROM LPAS23.12-39.7-1 are supported!
See archive content for instructions. Time to install ~20 min. If you experience problems after Android boot, like not working buttons or quick settings, wipe cache + data partitions. Don't update SuperSU (disable auto updates), it won't work. Later I'll post complete debloated ROMs with fresh SuperSU version, and simplify instructions. Be informed also, that this method doesn't give you read-write rights like unlocked bootloader. You may read and write having root-rights, but only till a restart or shutdown occurs, and every change will be undo by the Qualcomm protection (like HTC' s=on).
At the moment patch includes:
SuperSU 2.65 Free
Xposed Framework v86 (installer, modules)
Busybox 1.25.0.YDS, path /system/xbin/busybox
Download
P.S. Install only on indicated above ROM versions, and it's obvious that you must have enough theory knowledge and practical experience to make use of 9008 patch, so I'm not responsible for any consequences, etc. Greets go to: CrashXXL (method inventor), Sabissimo (our former OP), and serg_gangubas (ROM guru).
==============================================================================================
31.07.2017 - Full ROM Patch for Bootloader Locked Moto X ATT/VZW/etc
Based on the same principle, and not depend on system partition content, so it suits any bootloader locked Moto X Gen1 ATT/VZW (possibly any model, besides 1049 RepW / 1055 US Cell), but takes about 4 hours to be done - prepare for that, 100% battery level only!
This full ROM patch includes:
SuperSU 2.82 Free
Xposed Framework v87 (installer, modules)
Busybox 1.26.2, path /system/xbin/busybox
ViperFX 2.5.0.5 - sorry needs polishing, removed now (
Gallery and Camera not depend on Moto services
Gboard instead AOSP Keyboard. If it eats too much RAM, see Simple Keyboard
GAPPSes updated. Use command like adb shell pm uninstall --user 0 com.blahblah.blah to block any unwanted app or service
ES File Explorer Free Edition (a clone, you can disable and install yours )
"Jedy" gesture
AdBlock support (effect lasts till the 1st reboot yet, I'll think about make it constant). Please, choose /data/hosts instead of /system/etc/hosts
ROM debloated, but not deodexed.
Download
Instruction
Be careful, phone will be WIPED then flashed in 9008 "brick" mode (CrashXXL idea). Before you start install Moto drivers, latest RSD Lite, and fully charge the battery.
1) Download and unpack zip on С: (or any), open Python27, launch RUN_path.bat (needs to be launched only single time), install driver QHSUSB_driver.exe, and launch file _Moto.X.BootLocked.*.exe (where * - is desired ROM).
2) Go into fastboot mode, execute RUN_blbroke.bat. Screen gets black, Device Manager in Windows finds "QHSUSB_DLOAD", and installs it as "Qualcomm HS-USB QDLoader 9008 (COM*)". If it doesn't install, google for Windows driver digital signature disable.
3) Now launch RUN_root.bat, and see that patching process took start.
4) A small patch *SPEAKERS.BOOST.exe (if exists) boosts both speakers' volume.
P.S. Please, don't flash anything extra into the phone. In case of trouble, all you need is inside this folder. Just make it work.
To make "Battery OK" in fastboot use fastboot_cyclecharge.bat
Completely drained out battery causing "USB input device" needs disassembly of the phone to charge externally.
In case Titanium Backup shows error "Batch backup interrupted: insufficient free storage space", delete default backup folder, and make a new:
Titanium Backup > Menu > Preferences > Backup folder location > Storage Provider > DocumentProvider storage > Show Internal Storage > Internal Storage > Select Internal Storage > Create the folder > Use the current folder. Done!
Notes for myself: Viper, force wipe, readme.txt, volume patch, Adblock, advanced debloat
Debloated, rooted, lightweight ROM - soon! )
PUBLISHED. Sorry, took long time.
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
This method is working on locked BL.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
Wait wait... If you can have now possibility to unlock bootloader - go for it immediately! You will have normal FULL root-rights (SuperSU 2.49). Don't install 5.1, if you plan to unlock, because Sunshine app (25$) works only on 4.4.2 Android.
This topic is to help those AT&T users that are boot locked forever (who missed out possibility to unlock on 4.4.2 by proceed to 5.1) to give them READ-ONLY root. Yes, it's limited, but anything at least.
s5610 said:
If you can have now possibility to unlock bootloader...
Click to expand...
Click to collapse
I guess anyone on 4.4.4 today. There is no possibility to use Sunshine anymore.
Anyway spasibo za method
Ahh, if I don't have to be BL unlocked that's great lol.
I haven't read too much into the 5.1 updates or sunshine for that matter.
I've been on krypton 1.4.1 since it was released, and I haven't been able to successfully upgrade to any 5.1 roms yet.
Works great!
Works great for me on Windows 10 RTM 64-bit! Thanks a ton, I was waiting for a post like this.
I only had 3 minor hiccups:
1. RSD Lite gave me an error about "getvar", so I had to go into flashfile.xml in the ROM zip and remove the line that said getvar
2. I had to reboot to disable driver signature enforcement twice for some reason because Windows Update
3. The run-root.bat got stuck on "Executing..." because I installed the wrong driver (the correct file is qcusb.inf when installed from device manager -> browse my computer for driver software -> let me pick from a list -> all devices -> have disk)
Otherwise, everything runs just as well as KitKat, including Xposed.
Hehe got to love step 9
System Write
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
Click to expand...
Click to collapse
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Need some help, I did all steps until step 9. I installed the QHSUSB_DLOAD driver manually, and I can see 'Qualcomm HS-USB QDLoader 9008 (COM4)' showed in my Device Manager, but when I run 'RUN_Root.bat', I got this
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Sending MAGIC ...
QCOM fast download protocol targ:
Version: 7
Compatible version 2
Maximum block size 1024 (0x00000400)
Base address of Flash 0x00000000
Flash: eMMC
Window size: 30
Number of sectors: 128
First sector size: 2097152 (0x00200000)
Feature bits: 09
Sending SBL Reset...
Done
c:\Python27>pause
Press any key to continue . . .
Then I tried to run 'RUN_Root.bat' again, then I got
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device progr
amming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91,ca,fd,bb,94,2a,0d
,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960.bin' to addr 0x2a000000...
Executing...
Could not find Qualcomm device in Emergency download mode
Done, with errors!!!
c:\Python27>pause
Press any key to continue . . .
any suggestions? Thanks
jahrule said:
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Click to expand...
Click to collapse
Ill put the files here
Fantastic!!! I was looking this. All the last week I was sleeping about 3 hours per day trying to root my phone.
----
I scream "Victory" before the process finish.
Damn! My phone reboot and stay in the android doll fallen screen.
DejanPet said:
Ill put the files here
Click to expand...
Click to collapse
What to do with these files?
Those files are needed by Jahrule
Sabissimo
Hello.
I did everything as instructed, but eventually got the screen "no command".
The only thing I did not flash rom - a month ago updated by an OTA to 5.1, thought it was not necessary.
Factory reset does not help.
Advise something.
In the end, everything worked, thank you))
It works
It works great! Thank you very much! ATT xt1058.
eze_cba17 said:
Damn! My phone reboot and stay in the android doll fallen screen.
Click to expand...
Click to collapse
Follow the OP instruction EXACTLY, no exceptions!
If you got your current 5.1 through AT&T OTA, it's not enough for root patching procedure. A full RSD 5.1 official SBF flash over is required.
Could someone please do a video on this. I'm having a little trouble.
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.
Nexus 7'13 CROSS - Custom ROM Scripted Setup (c)2020-2021 k23m
CROSS works on PC with Windows, or WinPE if you do not have Windows installed, or VirtualBox with a Windows guest.
Currently supported ROMs:
- Android 10 LineageOS 17.1
- Android 11 LineageOS 18.1
- Android 11 LineageOS 18.1-flox
Previously supported ROMs:
- Android 7 LineageOS 14.1
- Android 7 LineageOS 14.1-microG
- Android 10 LineageOS 17.1-flox
FEATURES
- automatic scan of developer's website for the latest ROM version
- automatic download of all required components
- automatic single-click installation
- optional components like root or special kernel
- all you have to do is select yes/no during the installation
- both flo and deb are supported
PREREQUISITES
- unlocked device
- installed N7 USB drivers
- original eMMC partition layout may be required
All of the above are ensured with RESTOCK - also a scripted tool, available here:
[+]RESTOCK - stock restore, repartition, repair and reset, including USB driver fix
RESTOCK is a new Nexus 7 2013 repair and factory reset tool for Windows. The NRT app (Nexus Root Toolkit) is similar but is old, closed-source, unsupported, abandoned, does no eMMC diagnostics and most importantly - it offers no repartitioning...
forum.xda-developers.com
---------------------
lineage-install-2.bat
---------------------
This script installs and/or offers the following optional components:
- Android 10 LineageOS 17.1 UNOFFICIAL maintained by ripee https://forum.xda-developers.com/nexus-7-2013/development/rom-lineageos-17-1-t4038425
- TWRP (optional, no need to reflash it if exists already)
- repartition: sysrepart-max.zip by k23m (optional, no need if already repartitioned)
- root: Magisk (optional)
- GApps: pico (optional)
---------------------
lineage-install-3.bat
---------------------
This script installs and/or offers the following optional components:
- Android 11 LineageOS 18.1 UNOFFICIAL maintained by followmsi https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-18-1-2021-04-07.3569067/
- TWRP (optional, no need to reflash it if exists already)
- repartition: sysrepart-ultimate.zip by k23m (optional, no need if already repartitioned)
- root: Magisk (optional)
- GApps: pico (optional)
NOTE: automatic scan of the developer's website is not possible.
Please download the ROM from: https://drive.google.com/drive/fold...HZThGTnM?resourcekey=0-0BunAmDBWluYPghT0Fs6CA
Save it in CROSS' folder and drag-and-drop it on lineage-install-3.bat to start the installation.
--------------------------
lineage-install-3-flox.bat
--------------------------
This script installs and/or offers the following optional components:
- Android 11 LineageOS 18.1-flox OFFICIAL maintained by npjohnson https://forum.xda-developers.com/t/...s-7-2013-wi-fi-repartition-only-flox.4255325/
- TWRP-flox (optional, no need to reflash it if exists already)
- repartition: sysrepart-ultimate.zip (flox compatible) by k23m (optional, no need if already flox-repartitioned)
- root: Magisk (optional)
- GApps: pico unofficial by ipdev (optional)
------------------------
getlog.bat and relog.bat
------------------------
If you see errors, copy and report them. Run getlog.bat and include "getlog.log" in your post. If possible, also run relog.bat and attach "relog-xxxxxx.zip" to your post.
----------
fstrim.bat
----------
Improve performance of your eMMC.
---------------
repartition.bat
---------------
If sysrepart repartition is impossible due to TWRP or GPT issues, run the repartition.bat script.
SUPPORT
[FIX][EMMC] Nexus 7 2013 ⊕ bricked, dead, frozen or stuck ⊕
Quick Links if fastboot mode is not available, try Unbricking Guide if fastboot mode is available, do RESTOCK In this thread I would like to consolidate information about eMMC flash memory failures and remedies. When flash memory fails it...
forum.xda-developers.com
[+]RESTOCK - stock restore, repartition, repair and reset, including USB driver fix
RESTOCK is a new Nexus 7 2013 repair and factory reset tool for Windows. The NRT app (Nexus Root Toolkit) is similar but is old, closed-source, unsupported, abandoned, does no eMMC diagnostics and most importantly - it offers no repartitioning...
forum.xda-developers.com
If you select the local file option, CROSS will scan the data folder and offer the newest found file for installation. If nothing is found, you can type/paste a specific file name to install. You can drop anything you like to the data folder - CROSS is now a basic universal ROM installer.
SAMPLE OUTPUT
Code:
Nexus 7'13 LineageOS 17.1 Install v1.3 @2020 k23m
SUPPORT - http://bit.ly/2C35sLZ
This script assumes that USB drivers are already installed.
If not, then run RESTOCK first or install them manually.
Enter device name (flo=WiFi; deb=LTE) - [flo/deb]: flo
Use local ROM file? (no if unsure) [y/n]:
--2020-05-15 06:17:53-- https://lineageos.wickenberg.nu/flo/
Resolving lineageos.wickenberg.nu... 88.129.42.110
Connecting to lineageos.wickenberg.nu|88.129.42.110|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: 'tmp1'
tmp1 [ <=> ] 6.32K --.-KB/s in 0.001s
2020-05-15 06:17:57 (5.33 MB/s) - 'tmp1' saved [6473]
Found for download: lineage-17.1-20200515-UNOFFICIAL-flo.zip
Use local TWRP file? (no if unsure) [y/n]:
Press any key to continue . . .
Downloading installation files.
--2020-05-15 06:19:02-- https://dl.twrp.me/flo/twrp-3.3.1-0-flo.img
Resolving dl.twrp.me... 45.249.91.154
Connecting to dl.twrp.me|45.249.91.154|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9271296 (8.8M) [application/octet-stream]
Saving to: 'twrp-3.3.1-0-flo.img'
twrp-3.3.1-0-flo.img 100%[=================================================>] 8.84M 945KB/s in 11s
2020-05-15 06:19:15 (788 KB/s) - 'twrp-3.3.1-0-flo.img' saved [9271296/9271296]
--2020-05-15 06:19:15-- https://lineageos.wickenberg.nu/flo/lineage-17.1-20200515-UNOFFICIAL-flo.zip
Resolving lineageos.wickenberg.nu... 88.129.42.110
Connecting to lineageos.wickenberg.nu|88.129.42.110|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 413523888 (394M) [application/zip]
Saving to: 'lineage-17.1-20200515-UNOFFICIAL-flo.zip'
lineage-17.1-20200515-UNOFFIC 100%[=================================================>] 394.37M 2.71MB/s in 3m 17s
2020-05-15 06:22:34 (2.01 MB/s) - 'lineage-17.1-20200515-UNOFFICIAL-flo.zip' saved [413523888/413523888]
--2020-05-15 06:22:34-- https://jaist.dl.sourceforge.net/project/opengapps/arm/20200515/open_gapps-arm-10.0-pico-202005
15.zip
Resolving jaist.dl.sourceforge.net... 150.65.7.130
Connecting to jaist.dl.sourceforge.net|150.65.7.130|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 101519489 (97M) [application/octet-stream]
Saving to: 'open_gapps-arm-10.0-pico-20200515.zip'
open_gapps-arm-10.0-pico-2020 100%[=================================================>] 96.82M 3.25MB/s in 36s
2020-05-15 06:23:11 (2.73 MB/s) - 'open_gapps-arm-10.0-pico-20200515.zip' saved [101519489/101519489]
--2020-05-15 06:23:11-- https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Resolving github.com... 52.64.108.95
Connecting to github.com|52.64.108.95|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/67702184/81204200-6ca5-11ea-8f19-3a5b8341b6e2?
X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200515%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-
Date=20200515T072529Z&X-Amz-Expires=300&X-Amz-Signature=681f649c20ad2b0eabf80411650867d6db9144197a42a639a13162209f0fff91
&X-Amz-SignedHeaders=host&actor_id=0&repo_id=67702184&response-content-disposition=attachment%3B%20filename%3DMagisk-v20
.4.zip&response-content-type=application%2Foctet-stream [following]
--2020-05-15 06:23:11-- https://github-production-release-asset-2e65be.s3.amazonaws.com/67702184/81204200-6ca5-11ea-8f1
9-3a5b8341b6e2?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200515%2Fus-east-1%2Fs3%2Faws4
_request&X-Amz-Date=20200515T072529Z&X-Amz-Expires=300&X-Amz-Signature=681f649c20ad2b0eabf80411650867d6db9144197a42a639a
13162209f0fff91&X-Amz-SignedHeaders=host&actor_id=0&repo_id=67702184&response-content-disposition=attachment%3B%20filena
me%3DMagisk-v20.4.zip&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com... 52.216.134.219
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com|52.216.134.219|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5942417 (5.7M) [application/octet-stream]
Saving to: 'Magisk-v20.4.zip'
Magisk-v20.4.zip 100%[=================================================>] 5.67M 2.30MB/s in 2.5s
2020-05-15 06:23:15 (2.30 MB/s) - 'Magisk-v20.4.zip' saved [5942417/5942417]
--2020-05-15 06:23:15-- https://forum.xda-developers.com/attachment.php?attachmentid=4480528
Resolving forum.xda-developers.com... 104.18.19.88, 104.18.18.88
Connecting to forum.xda-developers.com|104.18.19.88|:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://dl.xda-cdn.com/4/4/8/0/5/2/8/sysrepart.zip?key=Wwfo1oqhImScVpTSzXTlzA&ts=1589527594 [following]
--2020-05-15 06:23:16-- https://dl.xda-cdn.com/4/4/8/0/5/2/8/sysrepart.zip?key=Wwfo1oqhImScVpTSzXTlzA&ts=1589527594
Resolving dl.xda-cdn.com... 104.27.191.76, 104.27.190.76
Connecting to dl.xda-cdn.com|104.27.191.76|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 782958 (765K) [application/zip]
Saving to: 'sysrepart.zip'
sysrepart.zip 100%[=================================================>] 764.61K 591KB/s in 1.3s
2020-05-15 06:23:20 (591 KB/s) - 'sysrepart.zip' saved [782958/782958]
Press any key to continue . . .
1. boot the Nexus in fastboot mode: when OFF press POWER + VOLUME DOWN
2. when in the bootloader menu, connect it to your PC
3. wait a few seconds, then...
Press any key to continue . . .
Verify...
Lock status...
Flash TWRP? [y/n]: y
sending 'recovery' (9054 KB)...
OKAY [ 0.297s]
writing 'recovery'...
OKAY [ 0.516s]
finished. total time: 0.812s
1. on N7 select "Recovery mode" with volume button
2. on N7 press power button to boot Recovery
3. when you see TWRP main menu press any key to continue
Wait...
*
Installing...
*****
Repartition? (no if already repartitioned) [y/n]: y
Transferring: 782958/782958 (100%)
2575 KB/s (782958 bytes in 0.296s)
***
Wait...
Installing zip file '/sdcard/sysrepart.zip'
Checking for Digest file...
###############################
# k23m Nexus 7'13 Repartition #
###############################
Creating log and gpt backup
Removing partitions
Creating new partitions
Formatting new partitions
###############################
Operation completed. Copy backup gpt and log files from internal storage to PC before rebooting.
###############################
Done processing script file
***
...REBOOTING
When you see TWRP main menu press any key to continue...
*****
Proceed only if you really see TWRP main menu
Press any key to continue . . .
Do dirty flash? (no if unsure) [y/n]: n
Wiping data without wiping /data/media ...
Done.
Formatting Cache using make_ext4fs...
Done processing script file
Formatting System using make_ext4fs...
Done processing script file
Wiping Cache & Dalvik...
-- Dalvik Cache Directories Wipe Complete!
Done processing script file
Formatting cache using make_ext4fs...
Done processing script file
***
Transferring: 413523888/413523888 (100%)
3649 KB/s (413523888 bytes in 110.640s)
***
Wait...
Installing zip file '/sdcard/lineage-17.1-20200515-UNOFFICIAL-flo.zip'
Checking for Digest file...
Warning: No file_contextsTarget: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keysPatching system image unconditio
nally...script succeeded: result was [1.000000]Done processing script file
Install root? [y/n]: y
Transferring: 5942417/5942417 (100%)
3868 KB/s (5942417 bytes in 1.500s)
***
Wait...
Installing zip file '/sdcard/Magisk-v20.4.zip'
Checking for Digest file...
***********************
Magisk 20.4 Installer
***********************
- Mounting /system
- Device is system-as-root
- Mounting /apex/com.android.conscrypt
- Mounting /apex/com.android.media
- Mounting /apex/com.android.media.swcodec
- Mounting /apex/com.android.resolv
- Mounting /apex/com.android.runtime
- Mounting /apex/com.android.tzdata
- System-as-root, keep dm/avb-verity
- Target image: /dev/block/mmcblk0p14
- Device platform: arm
- Constructing environment
- Adding addon.d survival script
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
Done processing script file
Install GApps? [y/n]: y
Transferring: 101519489/101519489 (100%)
3623 KB/s (101519489 bytes in 27.359s)
***
Wait...
Installing zip file '/sdcard/open_gapps-arm-10.0-pico-20200515.zip'
Checking for Digest file...
##############################
_____ _____ ___ ____
/ _ \ | __ \ / _ \ | _ \
| / \ || |__) | |_| || | \ \
| | | || ___/| __/ | | | |
| \ / || | \ |__ | | | |
\_/ \_/ |_| \___| |_| |_|
___ _ ___ ___ ___
/ __| /_\ | _ \ _ \/ __|
| (_ |/ _ \| _/ _/\__ \
\___/_/ \_\_| |_| |___/
##############################
Open GApps pico 10.0 - 20200515
- Mounting partitions
- Gathering device & ROM information
- Performing system space calculations
- Removing existing/obsolete Apps
- Installing core GApps
- Installing swypelibs
- Installing calsync
- Installing googletts
- Installing packageinstallergoogle
- Miscellaneous tasks
- Copying Log to /sdcard
- Installation complete!
- Unmounting partitions
Done processing script file
***
Done.
Press any key to continue . . .
SUPPORT - http://bit.ly/2C35sLZ
Press any key to exit...
_____________________________________________________
REPARTITION
sysrepart.zip - 1.1GB system, data is not wiped
sysrepart-max.zip - 1.3GB system, data is not wiped, automatically downloaded by LOS 17.1 script
sysrepart-flox.zip - 1.5GB system, data is wiped, 'vendor' partition is added, automatically downloaded by LOS 17.1-flox script
sysrepart-ultimate.zip - 4GB system, data is wiped, 'vendor' partition is added, 'recovery' is enlarged to 64MB in-place and your current TWRP continues to function, flox compatible, automatically downloaded by LOS 18.1-flox script. For N7-16GB try sysrepart-ultimate-2.zip
sysrepart-stock.zip - data is wiped, original partitions are restored
reboot immediately after repartition!
sysrepart-ultimate/stock work on any previous repartitions
sysrepart/max/flox work reliably only on original partitions
to install GApps larger than pico/nano you need sysrepart-ultimate
sysrepart-ultimate supports custom, oversized TWRP builds
To recover from other repartition attempts, simply install sysrepart-ultimate if you intend to use LOS17+ or sysrepart-stock if you have other plans. If direct sysrepart installation is impossible due to TWRP or GPT issues, run the repartition.bat script. On rare occasions you may have to run RESTOCK and "Restore original partitions" with it.
_____________________________________________________
UPDATE version 2.5 changes:
- update components' URLs
- update relog.bat
- remove installation scripts of no longer available ROMs
- add update.bat cleanup script (run it once)
- add repartition.bat script for repartition-only
- add lineage-install-3.bat script
Download CROSS2.zip and unzip it then download cross-update-XXX.zip and unzip it to the CROSS folder, overwrite existing files.
Also check the very latest interim updates in this post https://forum.xda-developers.com/t/iiiii-cross-custom-rom-scripted-setup.4092215/post-87622749
____________________________________________________
NOTE - most of the attached files are meant for direct script download. Except for CROSS and its updates do not download them manually unless you know what you are doing.
Hi, thank you very much for this useful tool.
I wonder whether your script could be updated to support dirty flash also. Now it seems to always make a clean flash. But it is not very convenient to set up the device after each security update.
I am not very experienced in making batch files but I was thinking about adjusting your script like follows. From:
Code:
:adbd
ping -n 3 127.0.0.1 >nul
set /p =*<nul
adb devices >tmp0 2>&1
find /i "recovery" tmp0 >nul
if not %errorlevel% == 0 goto adbd
[COLOR="Red"]echo.
echo Installing...
call:wait 5
adb shell twrp wipe /data[/COLOR]
adb shell twrp wipe /system
adb shell twrp wipe dalvik
adb shell twrp wipe cache
call:wait 3
adb push -p %LNZN% /sdcard/
call:wait 3
echo Wait...
adb shell twrp install /sdcard/%LNZN%
To:
Code:
:adbd
ping -n 3 127.0.0.1 >nul
set /p =*<nul
adb devices >tmp0 2>&1
find /i "recovery" tmp0 >nul
if not %errorlevel% == 0 goto adbd
[COLOR="red"]echo.
set /p FLASHTYPE=Do you want to make clean flash or dirty flash? Clean flash will erase all data (except the files in the internal storage) [clean/dirty]: || set FLASHTYPE=null
echo Installing...
call:wait 5
if /i %FLASHTYPE%==dirty (
echo Skipping wiping data...
echo Performing dirty flash...
goto dirty)
if /i %FLASHTYPE%==clean (
adb shell twrp wipe /data
)
:dirty[/COLOR]
adb shell twrp wipe /system
adb shell twrp wipe dalvik
adb shell twrp wipe cache
call:wait 3
adb push -p %LNZN% /sdcard/
call:wait 3
echo Wait...
adb shell twrp install /sdcard/%LNZN%
Any comment on this? Would this worked correctly?
prorokrak said:
....Any comment on this? Would this worked correctly?
Click to expand...
Click to collapse
Thanks for the suggestion. This code can be abbreviated, same as the other optional items:
Code:
set /p ANS=Do dirty flash? (no if unsure) [y/n]: || set ANS=n
if /i !ANS!==n (
adb shell twrp wipe /data
)
I added it to the v1.2 update.
I just gave this script a try. This is quite slick and saves a bunch of time! Thanks for this. :good:
CROSS 2 release
CROSS version 2.0
- new log script
- new fstrim script
- updated components' URLs
- removed LOS microG as it is no longer available
Both LineageOS 14.1 and LineageOS 17.1 install flawlessly. There may be temporary download issues. If so, retry later. LOS17 server errors...
Code:
Resolving lineageos.wickenberg.nu... 83.209.185.118
Connecting to lineageos.wickenberg.nu|83.209.185.118|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2020-10-11 10:13:40 ERROR 500: Internal Server Error.
:highfive:
Hello I came here from my topic where you suggested me using this. When I fire up lineage-installer2.bat, it can't connect to the server. It asks if I want to use a local file, which I answered yes to. When i gave the name of the file ( "lineage-17.1-20201007-UNOFFICIAL-flo.zip" which I placed inside the CROSS folder, it gave me an error and exited.. What's the deal there?
jelles01 said:
Hello I came here from my topic where you suggested me using this. When I fire up lineage-installer2.bat, it can't connect to the server. It asks if I want to use a local file, which I answered yes to. When i gave the name of the file ( "lineage-17.1-20201007-UNOFFICIAL-flo.zip" which I placed inside the CROSS folder, it gave me an error and exited.. What's the deal there?
Click to expand...
Click to collapse
Hi again, first copy eg "lineage-17.1-20201009-UNOFFICIAL-flo.zip" to "CROSS\data" folder, then answer [y] to the question...
Code:
Nexus 7'13 LineageOS 17.1 Install v2.0 @2020 k23m
SUPPORT - http://bit.ly/2C35sLZ
This script assumes that USB drivers are already installed.
If not, then run RESTOCK first or install them manually.
Enter device name (flo=WiFi; deb=LTE) - [flo/deb]: flo
Use local ROM file? (no if unsure) [y/n]: y
Found local file: lineage-17.1-20201009-UNOFFICIAL-flo.zip
As you can see it is found automatically without entering a file name. If nothing is found, you could type any file name but the file must be located in the data folder.
It has worked! The install and setup was buttery smooth, thank you so much for this tool. Amazing!
A little help.
I am about to receive my refurbished unit in a couple of days. chances are that it will likely be on the last stock software. I have a general knowledge about rooting and installing custom ROMs on a variety of devices but nexus 7 seems different to work it. Will this script automatically root and install the TWRP apart from the designated flavor of lineageOS?
Also, will I need to go through the prerequisites (i.e. RESTOCK) procedures even if I am on stock ROM and partition by default? Will I need to repartition every time when switching ROMs after this? Can the CROSS be used again if i had to switch from say LOS 17.1 to 14.1?
Thanks in advance!:highfive:
GeekyTanuj said:
I am about to receive my refurbished unit in a couple of days. chances are that it will likely be on the last stock software. I have a general knowledge about rooting and installing custom ROMs on a variety of devices but nexus 7 seems different to work it. Will this script automatically root and install the TWRP apart from the designated flavor of lineageOS?
Also, will I need to go through the prerequisites (i.e. RESTOCK) procedures even if I am on stock ROM and partition by default? Will I need to repartition every time when switching ROMs after this? Can the CROSS be used again if i had to switch from say LOS 17.1 to 14.1? Thanks in advance!:highfive:
Click to expand...
Click to collapse
Refurbished N7s usually come with old KitKat stock and it is advisable to run RESTOCK first to update the bootloader before flashing LineageOS. Also RESTOCK will unlock it and install N7 USB drivers on your Windows.
Yes, CROSS can be used multiple times, and will root and install TWRP. Repartition is required only once.
Pro tip: for LineageOS updates answer [y] to the "Do dirty flash?" question to retain your OS settings and apps. But being "dirty", it may not work properly after major OS changes.
Should there be LOS17 server download issues, get lineage-17.1-20201017-UNOFFICIAL-flo.zip from an alternative server and drop it into CROSS' data folder as described in this post.
Cheers
:highfive:
You are a lifesaver!
k23m said:
Refurbished N7s usually come with old KitKat stock and it is advisable to run RESTOCK first to update the bootloader before flashing LineageOS. Also RESTOCK will unlock it and install N7 USB drivers on your Windows.
Yes, CROSS can be used multiple times, and will root and install TWRP. Repartition is required only once.
Pro tip: for LineageOS updates answer [y] to the "Do dirty flash?" question to retain your OS settings and apps. But being "dirty", it may not work properly after major OS changes.
Should there be LOS17 server download issues, get lineage-17.1-20201017-UNOFFICIAL-flo.zip from an alternative server and drop it into CROSS' data folder as described in this post.
Cheers
:highfive:
Click to expand...
Click to collapse
Thank you so much for developing this, RESTOCK as well as stock MM debloat script. it literally saved hours and hours of hassle that one has to face while getting to different versions of android! Running 10 with latest updates. feels so good!
kernel Configuration.
While Android 10 seems tempting and it actually is, it isn't just offering the kind of experience I am looking for and hinders my daily experience in one or the other way.
Looks like you might be using LOS 14.1 with the ElementalX kernel. Can you recommend the best settings for video playbacks and light gaming? Please share your configuration as well.
Thanks and cheers!:highfive:
GeekyTanuj said:
While Android 10 seems tempting and it actually is, it isn't just offering the kind of experience I am looking for and hinders my daily experience in one or the other way.
Looks like you might be using LOS 14.1 with the ElementalX kernel. Can you recommend the best settings for video playbacks and light gaming? Please share your configuration as well.
Thanks and cheers!:highfive:
Click to expand...
Click to collapse
For video and games LOS17 seems optimal, check these benchmarks.
Personally I use LOS14 without Gapps and with EX kernel including a modification to the battery life extender. I lowered max battery charge to 4.00V which is equivalent to 75% (under)charge resulting in 8x increase of battery life. Furthermore, the mod allows for constant external power connection and no battery overcharging nor overheating/swelling. I edited "buildconfig.sh" in EX zip:
Code:
replace
echo "write /sys/devices/i2c-0/0-006a/float_voltage 4200" >> $CONFIGFILE
with
echo "write /sys/devices/i2c-0/0-006a/float_voltage 4000" >> $CONFIGFILE
:good:
You gave my Nexus 7 (2013) a new lease on life! Woo-hoo!
I was running a years-old version of the vanilla stock FW and it was soooo slow. Somebody in some comment section somewhere mentioned RESTOCK & CROSS, so I tried out RESTOCK2 and it worked flawlessly.
Then I tried installing 17.1 via CROSS2 without repartitioning (as I believed RESTOCK did that). I got an error that I did not save, hoping it wasn't a big deal. I got stuck on the Google loading screen, so I ran CROSS again. I was going to try 14.1, but wasn't given the option again (bonus? 17.1 looks beautiful and it didn't make me redownload anything, which was smart coding on your part).
I think I should have run the logging programs when I first saw errors, because I'm afraid they were cleared by the reinstallation. I did send what I could after running the loggers post-successful installation, just in case.
Now, 17.1 is working so smoothly with a quick Netflix sideload (no GApps here, used APKMirror + the APKMirror Installer) - which certainly is only working thanks to Magisk. How long did it take me to figure out how to put app icons on the homescreen (swipe up, of course!) I don't think I want to reveal
I think the only thing I'm missing is DoubleTap2Wake which I installed with RESTOCK but see now it wasn't an option with 17.1 via CROSS. Apparently somebody has it goin' on LOS17.1 or 18 but this was so easy, not sure I want to try messing with a custom kernel just yet until I get a little bored.
Thank you so much--it's unbelievable there aren't 8 million comments on this thread, it's SO well done. If you made this for a modern/uber-popular tablet surely there would be though. Thank you thank you thank you!
iforget said:
I think the only thing I'm missing is DoubleTap2Wake which I installed with RESTOCK but see now it wasn't an option with 17.1 via CROSS. Apparently somebody has it goin' on LOS17.1 or 18 but this was so easy, not sure I want to try messing with a custom kernel just yet until I get a little bored.
Thank you so much--it's unbelievable there aren't 8 million comments on this thread, it's SO well done. If you made this for a modern/uber-popular tablet surely there would be though. Thank you thank you thank you!
Click to expand...
Click to collapse
If the Lineage build is using followmsi's sources, then you do not need to change kernels.
You just need to activate DT2W.
See this post on how to activate using a kernel manager.
The thread with the ever changing name. xda thread - Link
If you want something simple, I use a magisk module that enables it on boot.
DT2W GitHub - Link
Cheers.
PS.
Sorry for a bit of OT.
PPS.
The Lineage 17.1 build is using followmsi's sources.
hi
I have issue with otg on my N7, i used cross2 without problems : i installed twrp, lineageos 14, root the nexus and installed elementalx and googleapp
my usb otg cable with a usb key is never detected , i can mount the usbstick with twrp (sometime i can see it sometime not in twrp) but after few minutes it diseppear
someone can help me ?
it's a kernel issue?
any app works
thx
gibnexus said:
my usb otg cable with a usb key is never detected , i can mount the usbstick with twrp (sometime i can see it sometime not in twrp) but after few minutes it diseppear
someone can help me ? it's a kernel issue?
Click to expand...
Click to collapse
LOS14+EX kernel OTG is OK. Use the built-in file manager.
There could be a hardware issue - pin #4 may have a dry joint and work intermittently.
k23m said:
LOS14+EX kernel OTG is OK. Use the built-in file manager.
There could be a hardware issue - pin #4 may have a dry joint and work intermittently.
Click to expand...
Click to collapse
Hi man
thanks for your answer but it’s not a pin 4 issues , I have just changed the daughter board, and this evening I used restock2 , I restocked, install twrp, used the fix 30 and root but don’t install elementalx
I used the app usb otg helper and everything is ok
I can see my usb stick..
Help me please .. I like s2w and 2tw to turn on my screen
I would have the both otg and gesture to awake and used a better android system like lineageos
Thx
gibnexus said:
Hi man
thanks for your answer but it’s not a pin 4 issues , I have just changed the daughter board, and this evening I used restock2 , I restocked, install twrp, used the fix 30 and root but don’t install elementalx
I used the app usb otg helper and everything is ok
I can see my usb stick..
Help me please .. I like s2w and 2tw to turn on my screen
I would have the both otg and gesture to awake and used a better android system like lineageos
Thx
Click to expand...
Click to collapse
Hi
I begin to believe it’s my otg cable who has some trouble
I will buy a new one and see ...
Just a last question elementalx and los 14 support otg without nothing else ? ( no app or addons ? )
So thx to you for your work my old nexus was sleeping in a corner and now it’s relive
Thx for all
gibnexus said:
Hi
I begin to believe it’s my otg cable who has some trouble
I will buy a new one and see ...
Just a last question elementalx and los 14 support otg without nothing else ? ( no app or addons ? )
So thx to you for your work my old nexus was sleeping in a corner and now it’s relive
Thx for all
Click to expand...
Click to collapse
I can assure you that straight LOS14+EX OTG works fine.
You must have enabled the "USB OTG + charge mode" option which is meant for car use or externally powered OTG devices. It is NOT NEEDED for normal, N7-powered OTG storage.