Related
Update: As a temporary solution I replaced the boot.img from 9/26 nightly with the one from 9/19 and have it working for now.
I can install the official release fine, and even CM nightly of Sept 19, (maybe 20 too, I didn't test). But if I try any nightly higher than that, it shows it installed fine, then I see the 1+ boot logo, then a bunch of strange color vertical lines and boot logo fades out, then reboot over and over. This even happens when installing custom roms from dev section if it's based on a build higher than 9/19.
I've done a full system and data wipe, installed official build, then tried to install latest nightly, but same error. Is there a way to check a log to see what's going on? The only thing I can think of is a while back I installed colorOS & miui to test them out. Maybe it affected partitions? I have no idea.
Thanks :good:
Here is what it looks like when I try to dirty flash latest nightly on top of stock CM11S:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is what it looks like when the install is "successful" of latest CM nightly after I wipe:
And here is a video showing what happens when I install something higher than 9/19 CM or any rom based off of higher:
https://www.youtube.com/watch?v=YVPkmEi3PGE
Thanks
Update your TWRP to 2.8.0.1
I updated and tried. It didn't show any errors on install but the same boot loop happens
Factory wipe and then re flash the rom gapps kernels etc
I did fastboot flash all of the original 11S files and it boots fine. Attempt at latest nightly, and bootloop. I found out how to copy the log, maybe this will help.
Also, according to the colorOS rom thread, when I flashed back to CM I did not get static_nvbk.bin & reserve4.img. Maybe this could be the issue? unfortunately I didn't back these up.
Here is the log:
Code:
I:Set page: 'flash_zip'
Installing '/sdcard/cm9-25nightly.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Device or resource busy
about to run program [/tmp/backuptool.sh] with 2 args
grep: /tmp/gapps.prop: No such file or directory
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
about to run program [/tmp/otasigcheck.sh] with 1 args
Creating filesystem with parameters:
Size: 1388314624
Block size: 4096
Blocks per group: 32768
Inodes per group: 7712
Inode size: 256
Journal blocks: 5296
Label:
Blocks: 338944
Block groups: 11
Reserved block group size: 87
Created filesystem with 11/84832 inodes and 11157/338944 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
minzip: Extracted 2 file(s)
minzip: Extracted 1525 file(s)
symlink(): created [/system/etc/firmware/wcd9320]
about to run program [/tmp/backuptool.sh] with 2 args
Writing radio image...
about to run program [/sbin/dd] with 3 args
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.046166 seconds, 21.7MB/s
about to run program [/sbin/dd] with 3 args
1000+0 records in
1000+0 records out
512000 bytes (500.0KB) copied, 0.018902 seconds, 25.8MB/s
about to run program [/sbin/dd] with 3 args
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.496146 seconds, 32.2MB/s
about to run program [/sbin/dd] with 3 args
64+0 records in
64+0 records out
32768 bytes (32.0KB) copied, 0.001728 seconds, 18.1MB/s
about to run program [/sbin/dd] with 3 args
1000+0 records in
1000+0 records out
512000 bytes (500.0KB) copied, 0.020736 seconds, 23.5MB/s
about to run program [/sbin/dd] with 3 args
131072+0 records in
131072+0 records out
67108864 bytes (64.0MB) copied, 2.224255 seconds, 28.8MB/s
about to run program [/sbin/dd] with 3 args
1024+0 records in
1024+0 records out
524288 bytes (512.0KB) copied, 0.023172 seconds, 21.6MB/s
script succeeded: result was [1]I:Legacy property environment disabled.
Updating partition details...
I:mount '/data/media/0' '/sdcard' process ended
On Sept 21 the CM nightlies made a change of "input: touchscreen: Update TP firmware to 14001219" I believe this is what's causing my bootloop problem. If this is the case, is it a hardware issue?
[Update]
If you use official unlock app to unlock bootloader, you will not receive OTA notify.
For now, there are no way to re-lock bootloader, so you can not receive OTA notify.
If you want to receive OTA notify, you should use Un-official bootloader unlock method to unlock bootloader.
ZE552KL
ZE552KL_SIGNED_Android_M_UnlockTool_2016_0715.zip
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE552KL/ZE552KL_SIGNED_Android_M_UnlockTool_2016_0715.zip
ZE520KL
ZE520KL_SIGNED_Android_M_UnlockTool_2016_0715.zip
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/ZE520KL_SIGNED_Android_M_UnlockTool_2016_0715.zip
============================
Unlock Device App: Unlock boot loader for Andriod M
Unlock Device App: Unlock boot loader
Notice:
1. Update your software image to V 13.16.5.36 or latest version
2. Before you download, install, and use the Unlock Device App you acknowledge and assume
complete risk to the quality and performance of this App, including but not limited to the following:
once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions;
the Original Product with the activated App will not be deemed the Original Product;
the Revised Product will no longer be covered under the warranty of the Original Product;
the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.
You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product,
including events involving paid service requested by you to be performed to the Revised Product.
Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product;
the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.
Original Article : https://www.asus.com/zentalk/tw/thread-177309-1-1.html (thanks [email protected])
UN-official unlock method:
All-in-one zip (unlock App+driver+adb+fastboot+twrp+SuperSU.zip) :
https://github.com/snowwolf725/RootZenfone3/archive/master.zip
1. Unzip the file.
2. Boot your zenfone 3 to boot-loader mode (you should firstly turn the phone off, then press and hold the volume up and power buttons )
3. Double click to execute "0.unlock_{Device}.bat"
0.unlock_ze520kl.bat (for ZE520KL)
0.unlock_ze552kl.bat (for ZE552KL)
If the bat file not work, you can try to execute following commands：
1. fastboot flash all unlock_{Device}.raw
(for ZE520KL)
Code:
fastboot flash all unlock_ze520kl.raw
or (for ZE552KL)
Code:
fastboot flash all unlock_ze552kl.raw
2. fastboot reboot-bootloader
3. fastboot oem unlock-go
im using apk ure given to unclok the bootloader, is that officials or un-offcials ??
kuranzi said:
im using apk ure given to unclok the bootloader, is that officials or un-offcials ??
Click to expand...
Click to collapse
XXXX.APK => Official Unlock
XXXX.RAW => UN-Offical Unlock
Official Unlock => Easy to use, stable , No computer need, can't receive OTA notify
UN-Offical Unlock => Can receive OTA notify
Be careful, unlock boot-loader will void the warranty.
After unlocking bootloader, both methods (official or un-official) got warning message when boot device.
https://www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=177309&page=4#pid929774
So, Asus engineer can easily known that this device is been unlocked.
We didn't find out the method to remove this message yet.
So we have to wait till asus release how to lock boorloader ?
Does the unofficial unlock reformat the phone?
emeraldsrs said:
Does the unofficial unlock reformat the phone?
Click to expand...
Click to collapse
Yes. The same as the official one as well.
will this work with other versions of the zenfone 3 max, such as the us version(ze520tl)? the hardware is the same, just wondering.
/////////////////////////////////////////////////
// ASUS Fastboot Tool (Android L)
// Version V4.1 dbg (2015/07/01)
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_PROJECT_NAME = ZE552KL
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// CPU ID = 046
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// RE-PARTITION ENABLE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// WIPE-DATA/CACHE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_RAW_VERSION = V1
/////////////////////////////////////////////////
target reported max download size of 536870912 bytes
Invalid sparse file format at heade
Creating filesystem with parameters:
Size: 67108864
Block size: 4096
Blocks per group: 32768
Inodes per group: 4096
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 16384
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/4096 inodes and 1294/16384 blocks
Creating filesystem with parameters:
Size: 57583562752
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14058487
Block groups: 430
Reserved block group size: 1024
Created filesystem with 11/3515680 inodes and 266738/14058487 blocks
Creating filesystem with parameters:
Size: 134217728
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 32768
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/8192 inodes and 1550/32768 blocks
sending 'config' CRC (0x884ab0fe)...
OKAY [ 0.016s]
writing 'CRC'...
OKAY [ 0.047s]
sending 'config' (512 KB)...
OKAY [ 0.047s]
writing 'config'...
OKAY [ 0.109s]
sending '' CRC (0x0)...
OKAY [ 0.047s]
writing 'CRC'...
OKAY [ 0.031s]
sending '' (0 KB)...
FAILED ()
finished. total time: 0.296s
When I run fastboot flash all unlock_ze552kl.raw, I get the above output. I have tried restarting both my pc and my phone, using another usb port, deleting and reinstalling asus drivers, but it did not help. What could be the problem?
On the other hand, I can reflash boot.img and recovery.img successfully.
Also, in the course of trying out other solutions, I ran fastboot erase system. Currently my phone is stuck on the asus bootloader screen when started normally.
1. Could it be caused by fastboot erase system?
2. If so, where can I find a system image to reflash?
Thanks in advance,
Jack
Could you please check if the boot warning is just the logo like on other phones which can be replaced by the original logo image?
After failing to root my device using windows, I used my mac terminal.
When I enter
Code:
fastboot flash all unlock_ze520kl.raw
I get
Code:
target reported max download size of 536870912 bytes
sending 'all' (522 KB)...
OKAY [ 0.040s]
writing 'all'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.061s
I was having a similar problem using windows
Sorry for this dumb question, but is this any where close to rooting the phone ?
catalinrcd said:
Sorry for this dumb question, but is this any where close to rooting the phone ?
Click to expand...
Click to collapse
Nope. As with other brands that lock their bootloaders, unlocking the bootloader is only the first step to rooting your phone. After bootloader unlock, you can proceed to root your phone.
Some brands like Samsung even have an extra layer of work to go: disabling the flash counter so that the phone doesn't detect future flashings of custom ROMs, etc.
Few minutes ago i just used this tool.
all i can say is that after i check "adv devices" , now i get my phone serial but it also says "unauthorized"
It also reseted my phone. The Zenfone 3 One click tool, still does nothing for me after this . Still can't root phone.
No idea if my phone has bootloader unlocked...? A message was on the screen before OS boot, but it was to fast,and i did not get to read it. So there for i can't really say if this works or not.
Now it seams i need to install this twrp . No idea what this is, or what will it do to my phone. Will return with more news.
Nougat update
snowwolf725 said:
Original Article : https://www.asus.com/zentalk/tw/thread-177309-1-1.html (thanks [email protected])
UN-official unlock method:
All-in-one zip (unlock App+driver+adb+fastboot+twrp+SuperSU.zip) :
https://github.com/snowwolf725/RootZenfone3/archive/master.zip
1. Unzip the file.
2. Boot your zenfone 3 to boot-loader mode (you should firstly turn the phone off, then press and hold the volume up and power buttons )
3. Double click to execute "0.unlock_{Device}.bat"
0.unlock_ze520kl.bat (for ZE520KL)
0.unlock_ze552kl.bat (for ZE552KL)
If the bat file not work, you can try to execute following commands：
1. fastboot flash all unlock_{Device}.raw
(for ZE520KL)
Code:
fastboot flash all unlock_ze520kl.raw
or (for ZE552KL)
Code:
fastboot flash all unlock_ze552kl.raw
2. fastboot reboot-bootloader
3. fastboot oem unlock-go
Click to expand...
Click to collapse
Did anyone try on the new OTA Nougat? Is it safe? Does it still work?
Hi there, I have a problem when I try to get into boot-loader mode (power + volume up) , i got this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
soved: it was fastboot, the wy to get into recovery was power + volume down.
Hi @snowwolf725.
My ZE552KL was rooted following some tutorials that I found in this forum, but I don't remember which bootloader I am currently using.
Since I'd like to receive OTA notification I'd like to know if I follow your tutorial I will lose my data and the root or it just change the booloader?
Best regards.
snowwolf725 said:
Original Article : https://www.asus.com/zentalk/tw/thread-177309-1-1.html (thanks [email protected])
UN-official unlock method:
All-in-one zip (unlock App+driver+adb+fastboot+twrp+SuperSU.zip) :
https://github.com/snowwolf725/RootZenfone3/archive/master.zip
1. Unzip the file.
2. Boot your zenfone 3 to boot-loader mode (you should firstly turn the phone off, then press and hold the volume up and power buttons )
3. Double click to execute "0.unlock_{Device}.bat"
0.unlock_ze520kl.bat (for ZE520KL)
0.unlock_ze552kl.bat (for ZE552KL)
If the bat file not work, you can try to execute following commands：
1. fastboot flash all unlock_{Device}.raw
(for ZE520KL)
Code:
fastboot flash all unlock_ze520kl.raw
or (for ZE552KL)
Code:
fastboot flash all unlock_ze552kl.raw
2. fastboot reboot-bootloader
3. fastboot oem unlock-go
Click to expand...
Click to collapse
hi.. are we able to use this unofficial method after upgrading to N, or we should do it before?
snowwolf725 said:
Original Article : https://www.asus.com/zentalk/tw/thread-177309-1-1.html (thanks [email protected])
UN-official unlock method:
All-in-one zip (unlock App+driver+adb+fastboot+twrp+SuperSU.zip) :
https://github.com/snowwolf725/RootZenfone3/archive/master.zip
1. Unzip the file.
2. Boot your zenfone 3 to boot-loader mode (you should firstly turn the phone off, then press and hold the volume up and power buttons )
3. Double click to execute "0.unlock_{Device}.bat"
0.unlock_ze520kl.bat (for ZE520KL)
0.unlock_ze552kl.bat (for ZE552KL)
If the bat file not work, you can try to execute following commands：
1. fastboot flash all unlock_{Device}.raw
(for ZE520KL)
Code:
fastboot flash all unlock_ze520kl.raw
or (for ZE552KL)
Code:
fastboot flash all unlock_ze552kl.raw
2. fastboot reboot-bootloader
3. fastboot oem unlock-go
Click to expand...
Click to collapse
im upgrade my zen 3 520kl to android 7.0 but i unlock bootloader my phone then it's not successfully
T M L said:
After failing to root my device using windows, I used my mac terminal.
When I enter
Code:
fastboot flash all unlock_ze520kl.raw
I get
Code:
target reported max download size of 536870912 bytes
sending 'all' (522 KB)...
OKAY [ 0.040s]
writing 'all'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.061s
I was having a similar problem using windows
Click to expand...
Click to collapse
me too !!
u can unlock bootloader ? help me !
my zen3 520kl upgraded android 7.0
Hi,
Because I could not find a reliable rooting mechanism I soldered a serial FTDI UB232, and I gain shell access.
The serial works ok as long I am in u-boot prompt.
Texas Instruments X-Loader 1.41 (Apr 12 2012 - 12:06:17)
OMAP4460: 1.2 GHz capable SOM
**** DDR SDRAM PATTERN TEST ****
DDR SDRAM DATA BUS TEST..... [PASSED]
DDR SDRAM ADDRESS BUS TEST..... [PASSED]
Starting OS Bootloader from EMMC ...
U-Boot 1.1.4 (Nov 9 2012 - 20:33:58)
Load address: 0x80e80000
DRAM: 1024 MB
Flash: 0 kB
Using default environment
printenv
bootargs=console=ttyO2,115200n8 [email protected] [email protected] init=/init vram=48M omapfb.vram=0:32M androidboot.console=ttyO2
bootcmd=booti mmc1
bootdelay=1
baudrate=115200
ipaddr=128.247.77.90
serverip=128.247.77.158
netmask=255.255.254.0
bootfile="uImage"
ethact=KS8851SNL
Environment size: 285/131068 bytes
As soon android boots when everything is settled down, the tty input is totally ignored, though the shell
prints all the os messages. There is no prompt. ?!?
[ 33.844390] wlan0: moving STA 00:90:a9:a5:51:a1 to state 3
[ 58.387908] omap_cpu_thermal_manager:sensor 66200 avg sensor 59795 pcb 0, delta 18897 hot spot 85097
[ 58.397766] omap_monitor_zone:hot spot temp 85097
[ 58.887908] omap_cpu_thermal_manager:sensor 63800 avg sensor 59795 pcb 0, delta 17742 hot spot 81542
[ 58.897827] omap_safe_zone:hot spot temp 81542
no prompt
Any idea how to outcome and enable the shell tty input.
Here are the pictures of the serial soldering and the serial to usb adapter.
(The pictures are mine, from the stack-over-flow post)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The ftdi
I found and android for OMAP blaze (GB and a kernel from https://e2e.ti.com/support/omap/f/849/t/310839),
After having all cowboys engineering from Texas headaches I finally end up with:
boot.img cache.img fastboot mkbootimg MLO_es2.1_gp MLO_es2.2_emu ramdisk.img ramdisk-recovery.img recovery.img system.img u-boot.bin userdata.img zImage files.
I tried first a non destructive flash, trying to flash the system, (then boot, kernel, recovery / all of them encountering same error)
Linux console:
sudo fastboot flash system system.img
[sudo] password for mpang:
< waiting for device >
sending 'system' (110304 KB)...
OKAY [ 42.127s]
writing 'system'...
FAILED (remote failure)
finished. total time: 42.137s
marquis tablet serial output, as shown in previous post
OMAP44XX TAB # fastboot
I2C read: I/O error
I2C read: I/O error
Device Serial Number: 5C28000200000001
Fastboot entered...
Starting download of 112951340 bytes
................................................................................... many dots
downloading of 112951340 bytes finished
writing to partition 'system'
Wrong Image... Failed to program
How did we get here fastboot.c 993 ?
Anyone ?, Thank you
So, I managed to wipe my filesystem when trying to root (going by the board that happens way too often I noticed).
I posted about it here https://forum.xda-developers.com/showpost.php?p=80579913&postcount=295 first.
But despite the quick and nice suggestions it still won't work.
Going by https://forum.xda-developers.com/showthread.php?t=3984875 I also tried to flash boot.img for Fastboot.
Yes, it's the right model ( GM21BA ) for Europe/Global 12gb/256
From make_f2fs.exe I get the following:
PS C:\temp> .\make_f2fs.exe [SERIAL]
F2FS-tools: mkfs.f2fs Ver: 1.9.0 (2017-11-13)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is enabled
Error: Failed to get device size!
Click to expand...
Click to collapse
Which has me thinking the filesystem is gone.
And then I erased and formated boot twice, and am still left with RAW fs.
PS C:\temp> fastboot format:ext4 boot
Warning: boot type is raw, but ext4 was requested for formating.
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
target reported max download size of 805306368 bytes
sending 'boot' (5688 KB)...
OKAY [ 0.021s]
writing 'boot'...
OKAY [ 0.107s]
finished. total time: 0.130s
Click to expand...
Click to collapse
And then I tried F2FS with Fastboot Format:
PS C:\temp> fastboot format:f2fs boot
Warning: boot type is raw, but f2fs was requested for formating.
Formatting is not supported for filesystem with type 'f2fs'.
Click to expand...
Click to collapse
So, as I'm writing this I'm reading up on make_f2fs to have it format a new 'boot' for me to flash unto.
Well, at least I have fastboot even if I can't seem to manage flashing anything, so it could be lot worse...
User MSM tool to restore to factory default. It will ease everything, but you will have a working phone. Follow the directions on the thread located here.
For future reference, I'll write how I did manage to fix this:
I had tried using MSM earlier, but couldn't get the qualcom-drivers installed (as mentioned in the thread linked).
So, I tried having the tool already active (and certificates installed) as I pressed both volume up & down and plugged in the phone.
Now a port reacted and I could (with great excitment and haste) press install:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As expected it's back to stock.
Here was a Guide. Someone said people don't care about Me or My Work so...
there is no Xperia 5 III or even the Xperia 1 III at the Sony Website
I Think you can use xperia 5 II. For xperia 5 II was Xperia 5 the right option before Xperia 5 II was listed
Not one notice that this nulls your warranty........
riahc3 said:
Not one notice that this nulls your warranty........
Click to expand...
Click to collapse
You get this Info from SONY, and it just makes Sense... You don't have trouble if You can relock Your Device. So stop spreading random Infos like "nulls Your Warranty". No One here complains about that...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flash Firmware with newflasher ends in bootloop and "your device is corrupt"....
How can i fix it?
Edit: I Fixed it with set_active:a
which file i need from there for A 11
Generic System Image releases | Platform | Android Developers
developer.android.com
DanielMode said:
which file i need from there for A 11
Generic System Image releases | Platform | Android Developers
developer.android.com
Click to expand...
Click to collapse
Basic knowledge for all Tech around the World before You continue with anything of this:
ARM = Mobile Chips
ARM64 = Mobile Chips with 64Bit Support
X86 = Desktop Chips like from AMD or Intel
X86_64 = You guessed it? Desktop 64Bit Chips...
GMS = Google Services or Google Apps
You want to use an Xperia Mobile Device with GMS?
ARM64 GMS... No GMS no Play Store...
i don't get it where i have to look for this sin file
3. Extract the File boot_********.sin with the Unsin Exe (Drag and drop the Image on the Exe)
DanielMode said:
i don't get it where i have to look for this sin file
3. Extract the File boot_********.sin with the Unsin Exe (Drag and drop the Image on the Exe)
Click to expand...
Click to collapse
Before Modding Your Device...
Download the Firmware for Your Model with Xperifirm. It will include everything that's needed. Including Your Way back to a working Device if You screw something...
I will edit the Threads soon with a hint for this. Sorry for the trouble!
already found it at patched too but was confusing buddy
to find at the main folder of downloaded FW from XperFirm
DanielMode said:
already found it at patched too but was confusing buddy
to find at the main folder of downloaded FW from XperFirm
Click to expand...
Click to collapse
To be honest with everyone, I don't have much time usually but I do my best to help out if I can! I have many Projects running and writing Guides isn't my Top Priority. But I will rework them ones more! Thank You for pointing out that part of the Guide!
so far so good, but now i'm getting nervis
after flashing patched boot.img i'm at this step now
PS C:\platform-tools> fastboot -w
erasing 'userdata'...
OKAY [ 39.720s]
formatting 'userdata' partition...
how long it takes to formating 'userdata' ??
i wait 30min already
looks like i messed it up
PS C:\platform-tools> fastboot -w
erasing 'userdata'...
OKAY [ 38.658s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type f2fs not supported.
OKAY [ 0.009s]
erasing 'cache'...
FAILED (remote: No such partition.)
finished. total time: 38.698s
PS C:\platform-tools>
how can i revive it now.??
k started all over again and now at this step again and waiting
formatting 'userdata' partition...
will see if its done when i get up tomorrow
6 hours later and still
formatting 'userdata' partition...
erasing and/or formating isn't finishing anymore
after flashing patched boot.img
finaly i could flash latest FW with newflasher
but root wasn't there so
i flashed patched boot.img with fastboot again and i got root acces
was a bit of'n struggel but now its rooted
now i was trying die relock the bootloader...u said wipe userdata again and i did and got stuck there now
PS C:\platform-tools> fastboot -w
erasing 'userdata'...
OKAY [ 41.602s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 107809730560
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 26320735
Block groups: 804
Reserved block group size: 1024
Created filesystem with 11/6586368 inodes and 461507/26320735 blocks
sending 'userdata' (144159 KB)...
writing 'userdata'...
Can i Lock the Bootloader with Root Access?
Hi @Miustone ,
At the GSI flashing stage, I am getting an error.
fastboot flash system_a system.img
Click to expand...
Click to collapse
returns FAILED (remote: 'No such partition.')
Click to expand...
Click to collapse
I tried dropping the _a but that didn't help.
My eventual goal is to replace the MBN files following :https://forums.oneplus.com/threads/...ell-volte-and-vowifi-calling-working.1284987/
When I try to access su from adb shell, I just get a cursor that doesn't seem to execute commands. But doesn't give the error from before rooting. So I'm semi rooted?