help me.. i want to downgrade my zw 2 from aw.2 to aw.1 last version.
please tell me step by step
thnks
Also interested. Was going to buy ZW2 because AW2 sucks on my 360, but now that AW2 is out for ZW2 I want to be sure I can stay with AW1.
Try this guide I made. If it doesn't work let me know.
https://www.youtube.com/watch?v=C77cHOjXo_g
Poebat said:
Try this guide I made. If it doesn't work let me know.
https://www.youtube.com/watch?v=C77cHOjXo_g
Click to expand...
Click to collapse
Can you please provide more details? The battery life is horrible after the "upgrade" to AW 2.0
AthenaLod said:
Can you please provide more details? The battery life is horrible after the "upgrade" to AW 2.0
Click to expand...
Click to collapse
Just follow the guide?
Poebat said:
Just follow the guide?
Click to expand...
Click to collapse
I was hoping for a text step by step guide
AthenaLod said:
I was hoping for a text step by step guide
Click to expand...
Click to collapse
Did the video not make sense
Well. XDA is not the place to ask for spoon feeding. If you even get a nice video from Poebat you should be happy. Otherwise you are free to do what he did and find out yourself.
traffas said:
Also interested. Was going to buy ZW2 because AW2 sucks on my 360, but now that AW2 is out for ZW2 I want to be sure I can stay with AW1.
Click to expand...
Click to collapse
Do you still need any help with it?
i have the files for AW 1.5
Shaannoobrr said:
Do you still need any help with it?
i have the files for AW 1.5
Click to expand...
Click to collapse
I ended up just getting another OG Zenwatch, assuming it wouldn't ever get the AW2 upgrade. So far, I've been right. If it ever dies, I'll probably get a ZW2 since I know it can be held back to AW1.5.
downgrade Android 2.0 to 1.5
Good morning at all, my big screen zenwatch 2 has update to Android 2.0 (ota) but i do not like it at all....kindly tell me how to go back to Android 1.5 ? can i load 1.5 whith adb ? or do you ave to install twrp ?
thanks you in advance
P.S I wrote about this post not to open it an identical one, sorry.
Terp backup
mrt.angelo said:
Good morning at all, my big screen zenwatch 2 has update to Android 2.0 (ota) but i do not like it at all....kindly tell me how to go back to Android 1.5 ? can i load 1.5 whith adb ? or do you ave to install twrp ?
thanks you in advance
P.S I wrote about this post not to open it an identical one, sorry.
Click to expand...
Click to collapse
I have an twrp backup but you need to wipe you zenwatch after it. Do you want the files?
Shaannoobrr said:
I have an twrp backup but you need to wipe you zenwatch after it. Do you want the files?
Click to expand...
Click to collapse
Or thank you! Are you kind, kindly write the steps and commands to give on adb since i'm not very experienced on this model? Do i only need twrp latest version? Rest waiting and thank you again for support ?
---------- Post added at 08:23 PM ---------- Previous post was at 07:52 PM ----------
Can not install 1.5 without twrp and without root? I would probably like to receive future updates if possible but if you can not please .... also busybox and supersu service? In case you send me everything you need at least I'm sure I will not make any mistakes. Thanks !!!
Interested... Desperately want to downgrade. The comparison between my of 360 and my zenwatch2 is night and day.
Looking for the wren aw 1.5 ota if anyone has it.
mrt.angelo said:
Good morning at all, my big screen zenwatch 2 has update to Android 2.0 (ota) but i do not like it at all....kindly tell me how to go back to Android 1.5 ? can i load 1.5 whith adb ? or do you ave to install twrp ?
thanks you in advance
P.S I wrote about this post not to open it an identical one, sorry.
Click to expand...
Click to collapse
Shaannoobrr said:
I have an twrp backup but you need to wipe you zenwatch after it. Do you want the files?
Click to expand...
Click to collapse
....
btw. you dont need twrp .you still need the files and help with it.? i was busy with school so sorry for the late replie.
i will pass you the files but if you need more help just say it
https://mega.nz/#F!J90y0Q4Q!cBWru214ZLlora7gYGXWFw
first you need the adb setup for your pc and you need to set adb on the watch itself. just tap 7 times te build number and you have the developer options on the watch
now the flashing
you need to oem lock to oem unlock (search on yt)
then you need to open cmd (command prompt)
then the flash files.
you have three files
system.simg WATCH IT, IT IS .SIMG NOT IMG ( THE OTHER FILES IS IMG)
recovery.img
boot.img
.
.
so first you need to do this put your watch in your pc it will ask to trust pc with adb on the first time
then put in
adb reboot bootloader
wait for it is stuck at asus or something
then
fastboot flash system (then drag the file in cmd. it will popup an location\you will need to drag the system.simg here
wait before it suceeded
then
fastboot flash boot (drag boot.img )
wait agian
then fastboot flash recovery (drag recovery.img)
then wait
then
"fastboot -w" (Erases userdata and cache (and format if supported by partition type)).
then
fastboot reboot
wait
it will take max an hour!
hello thank you again for the support, it's this morning I try but I'm not bossed, I unblocked the bootloader, I installed twrp recovery but I can not copy busybox and supersu on sd card, it looks like it is not seen, typed adb push Busybox_1.24.1 / sdcard but nothing to do ... always gives me the error ... from adb recovery if i move it to sd card i will appear (you need a removable device) in red ... i do not know what to do .. ianto:
mrt.angelo said:
hello thank you again for the support, it's this morning I try but I'm not bossed, I unblocked the bootloader, I installed twrp recovery but I can not copy busybox and supersu on sd card, it looks like it is not seen, typed adb push Busybox_1.24.1 / sdcard but nothing to do ... always gives me the error ... from adb recovery if i move it to sd card i will appear (you need a removable device) in red ... i do not know what to do .. ianto:
Click to expand...
Click to collapse
Why you need root? If your bootloader is unlocked its all set. Root is stupid on an watch because you cant do anything with it i think.
Just follow the steps and it all good because it is an original file and it has the lastest security update of 5.1. But watch it. The watch will eventually say it has an update because it is original but you can ignore that and it is all good
Edit.
It was 1.5 version of the update because 5
1 doesnt excist. My bad.
error cmd:
C:\Users\Angelo>cd desktop
C:\Users\Angelo\Desktop>cd android wear 1.5
C:\Users\Angelo\Desktop\android wear 1.5>fastboot flash system
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\Angelo\Desktop\android wear 1.5>
I can not handle it ... please give me a hand .. write me the rows to enter in cmd step, step, it's this morning I try but nothing to do.
mrt.angelo said:
error cmd:
C:\Users\Angelo>cd desktop
C:\Users\Angelo\Desktop>cd android wear 1.5
C:\Users\Angelo\Desktop\android wear 1.5>fastboot flash system
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\Angelo\Desktop\android wear 1.5>
Click to expand...
Click to collapse
Did you drag the system simg file in it?
Can i see an screenshot?
---------- Post added at 05:12 PM ---------- Previous post was at 05:04 PM ----------
mrt.angelo said:
hello thank you again for the support, it's this morning I try but I'm not bossed, I unblocked the bootloader, I installed twrp recovery but I can not copy busybox and supersu on sd card, it looks like it is not seen, typed adb push Busybox_1.24.1 / sdcard but nothing to do ... always gives me the error ... from adb recovery if i move it to sd card i will appear (you need a removable device) in red ... i do not know what to do .. ianto:
Click to expand...
Click to collapse
.
.
.
And if you wanna root it make sure you put the files in /sdcard/downloads.
Still 1 question. Do you put the files on the watch trough adb or just with file explorer on your pc?
---------- Post added at 05:13 PM ---------- Previous post was at 05:12 PM ----------
mrt.angelo said:
error cmd:
C:\Users\Angelo>cd desktop
C:\Users\Angelo\Desktop>cd android wear 1.5
C:\Users\Angelo\Desktop\android wear 1.5>fastboot flash system
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\Angelo\Desktop\android wear 1.5>
Click to expand...
Click to collapse
Just click hold and drag the system file right with a space to cmd
yeaa !! finally i did it! now I'm back at 1.5 at last! thank you for your support, in the end there was no repeat in cmd for that did not work! thank you Shaannoobrr !
Microsoft Windows [Versione 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Tutti i diritti riservati.
C:\Users\Angelo>cd desktop
C:\Users\Angelo\Desktop>cd android wear 1.5
C:\Users\Angelo\Desktop\android wear 1.5>fastboot flash system
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\Angelo\Desktop\android wear 1.5>fastboot flash system.simg
unknown partition 'system.simg'
error: cannot determine image filename for 'system.simg'
C:\Users\Angelo\Desktop\android wear 1.5>fastboot flash system system.simg
target reported max download size of 63963136 bytes
erasing 'system'...
OKAY [ 0.671s]
sending sparse 'system' (61788 KB)...
OKAY [ 2.340s]
writing 'system'...
OKAY [ 6.042s]
sending sparse 'system' (62460 KB)...
OKAY [ 2.315s]
writing 'system'...
OKAY [ 6.097s]
sending sparse 'system' (59709 KB)...
OKAY [ 2.264s]
writing 'system'...
OKAY [ 5.982s]
sending sparse 'system' (57336 KB)...
OKAY [ 2.157s]
writing 'system'...
OKAY [ 5.730s]
sending sparse 'system' (61636 KB)...
OKAY [ 2.323s]
writing 'system'...
OKAY [ 6.118s]
sending sparse 'system' (59633 KB)...
OKAY [ 2.248s]
writing 'system'...
OKAY [ 5.870s]
sending sparse 'system' (61485 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 6.054s]
sending sparse 'system' (62460 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 6.113s]
sending sparse 'system' (11600 KB)...
OKAY [ 0.440s]
writing 'system'...
OKAY [ 1.163s]
finished. total time: 68.598s
C:\Users\Angelo\Desktop\android wear 1.5>fastboot flash boot boot.img
target reported max download size of 63963136 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.567s]
writing 'boot'...
OKAY [ 1.639s]
finished. total time: 2.210s
C:\Users\Angelo\Desktop\android wear 1.5>fastboot flash recovery recovery.img
target reported max download size of 63963136 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.569s]
writing 'recovery'...
OKAY [ 1.646s]
finished. total time: 2.219s
C:\Users\Angelo\Desktop\android wear 1.5>fastboot -w
Creating filesystem with parameters:
Size: 2759831552
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 10527
Label:
Blocks: 673787
Block groups: 21
Reserved block group size: 167
Created filesystem with 11/168672 inodes and 22128/673787 blocks
target reported max download size of 63963136 bytes
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
erasing 'userdata'...
OKAY [ 1.886s]
sending 'userdata' (45012 KB)...
OKAY [ 1.604s]
writing 'userdata'...
OKAY [ 4.484s]
erasing 'cache'...
OKAY [ 0.168s]
sending 'cache' (8192 KB)...
OKAY [ 0.292s]
writing 'cache'...
OKAY [ 0.849s]
finished. total time: 9.298s
C:\Users\Angelo\Desktop\android wear 1.5>fastboot reboot
rebooting...
finished. total time: 0.006s
C:\Users\Angelo\Desktop\android wear 1.5>
Related
I know that there are a lot of threads like this, and I was hesitant to start another, but I am starting to think that my situation is unique.
I tried to flash my Razr to do the OTA update on Tuesday, that broke, so I grabbed the china leak, and flashed it with the EternityProject tool.
Since then, I've been unable to even get into recovery mode, flashing seems to succeed:
Code:
ECHO is off.
Flashing BootLogo....
< waiting for device >
sending 'logo' (854 KB)... OKAY [ 0.127s]
writing 'logo'... INFOno such partition
FAILED (remote: )
Flashing EBR....
sending 'ebr' (16 KB)... OKAY [ 0.287s]
writing 'ebr'... OKAY [ 0.477s]
Flashing MBR....
sending 'mbr' (16 KB)... OKAY [ 0.274s]
writing 'mbr'... OKAY [ 0.438s]
Flashing DevTree....
sending 'devtree' (512 KB)... OKAY [ 0.335s]
writing 'devtree'... OKAY [ 0.504s]
Flashing Android System....
sending 'system' (262144 KB)... OKAY [ 28.953s]
writing 'system'... OKAY [ 11.239s]
sending 'system' (262144 KB)... OKAY [ 30.023s]
writing 'system'... OKAY [ 10.696s]
sending 'system' (262144 KB)... OKAY [ 30.955s]
writing 'system'... OKAY [ 10.660s]
sending 'system' (6912 KB)... OKAY [ 0.829s]
writing 'system'... OKAY [ 0.339s]
Flashing Kernel....
sending 'boot' (8192 KB)... OKAY [ 0.906s]
writing 'boot'... OKAY [ 0.945s]
Flashing Android Recovery....
sending 'recovery' (9216 KB)... OKAY [ 1.276s]
writing 'recovery'... OKAY [ 0.941s]
Flashing CDR....
sending 'cdrom' (216832 KB)... OKAY [ 25.298s]
writing 'cdrom'... OKAY [ 13.160s]
Flashing Radio (BP)....
sending 'radio' (14436 KB)... OKAY [ 1.936s]
writing 'radio'... OKAY [ 2.189s]
Flashing WebTop....
error: cannot load 'webtop_signed'
Erasing Cache....
erasing 'cache'... OKAY [ 1.221s]
Rebooting....
rebooting...
ECHO is off.
ECHO is off.
Greets from the EternityProject!
What I've tried:
1) http://forum.xda-developers.com/showthread.php?p=28006523#post28006523
Flashing the ROM linked at the top, no luck
Following the tutorial below, no luck.
2) DroidRazrUtility1.7 for ICS
I know it's for the USA version, but I was desperate, ran through the program, every option, nothing worked.
Any option in the boot menu leads me back to a black screen with white text.
Boot directly after a flash leads me to the following text:
Code:
Invalid CG OTV(GC: cdrom): Invalid SP Data
Invalid CG OTV(GC: system): Invalid SP Data
Invalid CG OTV(GC: webtop): Invalid SP Data
Invalid CG HAB(GC: webtop, Status: 0X0056)
Invalid CG OTV(GC: webtop)
I have rigged a factory cable to do the flashing, since my battery died ages ago, could this be a complication? Phone has 0 charge, I cannot make it charge either.
Anything else I should try before I take it in for repairs?
This tutorial works great ... Follow the step by step
start recovery as in 56, 57, 58 post
vervactor said:
This tutorial works great ... Follow the step by step
start recovery as in 56, 57, 58 post
Click to expand...
Click to collapse
Thanks!
I am giving it a try now, will report back.
Use only files from this tutorial
infinite.za said:
Thanks!
I am giving it a try now, will report back.
Click to expand...
Click to collapse
Appears to be the same symptoms, loading recovery afterwards ends up with a boot failiure.
Going to try the text file included in the link in post 58, perhaps there's more steps to help.
vervactor said:
Use only files from this tutorial
Click to expand...
Click to collapse
No luck - Unless I am not understanding which "this" tutorial you are referring to.
Thanks for the help
http://forum.xda-developers.com/showthread.php?p=28006523#post28006523
How did you system installed?
and what happened that you have a brick
vervactor said:
http://forum.xda-developers.com/showthread.php?p=28006523#post28006523
How did you system installed?
and what happened that you have a brick
Click to expand...
Click to collapse
It's been bricked like this since I flashed the chinese ROM ( 300~ MB )
I don't understand what you mean by "How did you system installed?" - I didn't know there was any way except with the flashing tools.
Some more research has told me that I might need something called "SDK Tools" - Is that just the android SDK? If so, then I am busy installing and will report back.
Can't believe that it's so simple..
infinite.za said:
Some more research has told me that I might need something called "SDK Tools" - Is that just the android SDK? If so, then I am busy installing and will report back.
Can't believe that it's so simple..
Click to expand...
Click to collapse
I have the exact same problem! may you could give me a link or something what you did with the SDK Tools?! would be great
---------- Post added at 08:24 PM ---------- Previous post was at 07:25 PM ----------
Or maby aynone else got a possible answere/solution?! :fingers-crossed:
What version is your Razr? —Gsm/cdma—
And region? —Asia, .Eu, latam, China—
Sent from my XT910 using xda premium
pedrotorresfilho said:
What version is your Razr? —Gsm/cdma—
And region? —Asia, .Eu, latam, China—
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
So on the back of it :
Model: XT910
Type Name: M0C2E
FCC ID: IHDP56ME2
IC ID: 1090-P56ME2
And region is .Eu
ali544 said:
So on the back of it :
Model: XT910
Type Name: M0C2E
FCC ID: IHDP56ME2
IC ID: 1090-P56ME2
And region is .Eu
Click to expand...
Click to collapse
I eventually solved it by flashing a new webtop_signed partition.
Turns out, I had formatted it earlier and even though the ICS builds do not have a webtop partition, it is still needed to boot.
So see if you can install the android SDK, then flash an old firmware with webtop, and then an ICS firmware - Should hopefully solve your problem
-- Good luck!
Thank you allready very much for the help!
May i ask you, which firmware you installed?
Or maby you/someone can give me some further information, because im realy scared, that my battery is getting empty and i cant charge it anymore, i tryied many things already but nothing worked, so now you are my last hope, but i dont realy know how to do it / which firmware i should use and schould i use RSD Lite to do it?
Hope for positive replay (relay needed!)
---------- Post added at 01:13 AM ---------- Previous post was at 12:17 AM ----------
Phoooooooo!
Finaly got it to work! :victory:
I falshed "SPDREM_U_01.6.5.1-167_SPU-15-M2-1-CEE_1C.91P_0A.6C_RTCEE_CFC_HWp2b_SIGNED.xml" with the alternative to RSD Lite: "Fla****" but i got only errors, after a while i got the background of the recovery and instantly pressed volume up + down and there i got the recovery, where i than wiped both chases.
Afterwards i connected it with my pc and flashed "SPDREM_U_01.6.7.2-180_SPU-19-TA-11.2_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml" and finaly got it to start and now got ICS 4.0.4 again working on my phone!
So, I tried to flash a GSI on my Treble Compatible Wiko Lenny 5, I checked with the app and I have A only.
So I downloaded the A Only ARM 64 IMG and I can't flash it.
It says:
$ fastboot flash system PixelExperienceP-a64-aonly.img
target reported max download size of 134217728 bytes
erasing 'system'...
OKAY [ 0.017s]
sending sparse 'system' 1/13 (131068 KB)...
OKAY [ 4.908s]
writing 'system' 1/13...
FAILED (remote: sparse image size span overflow.)
finished. total time: 4.929s
What can I do? I even tried -S (AMOUNT OF KB/MB) but nothing! :crying:
Hope someone can help.
Hi. I had the same issue about 3 days ago. I have not yet figured a way to flash the GSI rom yet. But I was able to get my phone working again.
What I did was to
1. Download my phone's stock rom
2. Extract the system.img
3. Flash it using adb.
As for your personal files, unless you've already backed them up, I don think there is a way to get them back.
Hope I was of enough help
OPTIONAL READING
Hi, let's go:
Scénario: you know nothing Jon Snow, but you want root, so you install fastboot, no matter which twrp, you follow a couple of tutorials you found in the wild and you play around with slot a -slot b twrp option. You find funny erase partitions, that way you have more internal space, maybe. You erase devil cache, and good boy cache and everything, because why not? You do not make backups, 'cause your not a coward, but a little nervous-impulsive. Magisk? it sound cool, I´ll take 4, thanks
Strange, things start going badly: The nokia 3.2 goes crazy and you just have fastboot. You manage to have twrp again thanks to the command fastboot flash boot twrp-3.2-dpl-00eea
Buuuuuuut you cannot install img nor zip files from sdcard using install options, then you discover that there is /sdcard an /external_sdcard¡¡¡ but it does not matter, file is corrupted, even drinking bleach does not improves the situation. Yo cannot install lineage-17.1-20200413-UNOFFICIAL-treble_arm64_avN. img or .zip (ahhhh it is RAR, so I have to change the extension to zip? maybe the system folder?) and you do not even know if you are arm64 a/b or just arm or legs.
You try to install system-quack-arm-ab-vanilla via adb push commands or fastboot commands, you fight with qualcomm drivers, the qfil tool, with not command found little android robot message, your system is corrupt message, go to see google nokia page (why? they are the enemy who bloats my phone!!!) you do not even know if you were in andorid 10 or 9 or 1909? You start filling up your desktop with images boot.img, .exe files OST LA bizarre programme... You try to open the nokia 3.2 to search 2 pins to enable eld supermode-mode with no chance 'cause you are not strong enough and it is really well ... glued? MAybe if I pay someone else tou fix it? 140 euros... 120 dollars, no, wait it is reaaaaaly expensive¡¡¡
REAL HINT
Have a try to download HMDSW_DPL_sprout-015B-0-00WW-B01 and search for boot vbmeta and other .img files and flash them manually via fastboot, if you are lucky as me, you may fix the self provocated prob:
PS C:\Users\ike\Desktop> cd platform-tools-new PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash boot \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\boot.img < waiting for any device >
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash boot \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\boot.img Sending 'boot' (65536 KB) OKAY [ 2.072s]
Writing 'boot' OKAY [ 0.620s]
Finished. Total time: 2.692s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash custom \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\custom.img Sending 'custom' (6204 KB) OKAY [ 0.203s]
Writing 'custom' OKAY [ 0.062s]
Finished. Total time: 0.282s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash persist \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\persist.img Sending 'persist' (32768 KB) OKAY [ 1.038s]
Writing 'persist' OKAY [ 0.315s]
Finished. Total time: 1.354s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash system \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\system.img Sending sparse 'system' 1/6 (523260 KB) OKAY [ 16.927s]
Writing 'system' OKAY [ 6.093s]
Sending sparse 'system' 2/6 (523260 KB) OKAY [ 16.899s]
Writing 'system' OKAY [ 6.657s]
Sending sparse 'system' 3/6 (523260 KB) OKAY [ 16.888s]
Writing 'system' OKAY [ 5.328s]
Sending sparse 'system' 4/6 (492416 KB) OKAY [ 15.869s]
Writing 'system' OKAY [ 6.127s]
Sending sparse 'system' 5/6 (502344 KB) OKAY [ 16.201s]
Writing 'system' OKAY [ 4.613s]
Sending sparse 'system' 6/6 (24680 KB) OKAY [ 0.793s]
Writing 'system' OKAY [ 1.132s]
Finished. Total time: 119.152s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash userdata \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\userdata.img Sending 'userdata' (1268 KB) OKAY [ 0.031s]
Writing 'userdata' OKAY [ 0.031s]
Finished. Total time: 0.079s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash vbmeta \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\vbmeta.img Sending 'vbmeta' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.016s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash vendor \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\vendor.img Sending 'vendor' (424560 KB) OKAY [ 13.363s]
Writing 'vendor' OKAY [ 3.931s]
Finished. Total time: 17.497s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot reboot Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
PS C:\Users\ike\Desktop\platform-tools-new>
I'm willing to help, as far as I have to stay home because of a biological hacking. And if you do not know what are you doing or you are not confident, do not do it. Thanks
hello
can you please explain step by step?
thank you
kntb said:
hello
can you please explain step by step?
thank you
Click to expand...
Click to collapse
First tell me what have you done so far
Hi
Thanks for guide
but I am unable boot after following all above steps
Just as a tip: I once got mine soft-bricked (that was a scary one. No partitions, can't flash, boot, or erase anything at all, even saw the linux penguin logo instead of "Android One"), but after lots of googling i decided to check my active slot, turned out it was something like "UNAVAILABLE" (or so)
So I just set my active slot to A (or B, doesn't matter) and I recovered everything.
Hi everyone, couldn't find anything relevant on the internet and the forum about the rollback problem, there is any way to install custons ROMs with that anabled? since i bought my moto g8 power mid last year i never could install any custom rom because of that, fastboot always give me anti-rollbakc warning and won't flash some partitons so it always ended up bootlooping and i go back to stock, there is any way to disable that feature? or bypass, how can i solve this problem?
Below is the fastboot log of what usually happens.
Code:
writing 'vbmeta_a'...
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 10 vs 14
OKAY [ 0.007s]
finished. total time: 0.017s
Here are the full version of the previous log i posted, i was trying to install the HavocOS via fastboot
Code:
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.519s]
writing 'boot_a'...
OKAY [ 1.058s]
finished. total time: 2.579s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 805261312 bytes
sending sparse 'product_a' 1/3 (720896 KB)...
OKAY [ 17.117s]
writing 'product_a' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.121s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
sending sparse 'system_a' 1/2 (720896 KB)...
OKAY [ 17.125s]
writing 'system_a' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.129s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.009s]
writing 'vbmeta_a'...
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 14
OKAY [ 0.011s]
finished. total time: 0.020s
You definitely are in fastboot d? Not just the bootloader?
When you are flashing the inages, if you have a green robot and some text down the bottom, that is fastboot/bootloader.
Fastboot d is different, you will definitely know if you are in fastboot d.
Beetle84 said:
You definitely are in fastboot d? Not just the bootloader?
When you are flashing the inages, if you have a green robot and some text down the bottom, that is fastboot/bootloader.
Fastboot d is different, you will definitely know if you are in fastboot d.
Click to expand...
Click to collapse
That was on bootloader, i searched about the fastboot d but couldn't find any explanation/tutorial how to enter it, i tried the command fastboot reboot fastboot but it gives unknown fastboot target, can you help me?
Fastboot reboot fastboot is the correct way from the bootloader.
You need to update your platform tools.
Also you need to be on android 10 for these roms to boot.
One of the guys helped me out with this earlier. After you've unlocked your boot loader and if your on android 11.
Use rescue & smart assistant to backup your stock rom, it will tell you what kind it is too....
Then go download the android 10 stock version.
Then use moto tools by vache and load the android 10 stock rom into it. Just follow the directions and place it in bootloader.
after that flash whatever puppy of your choosing. Also I'd advise against flashing twrp just boot it. Also if you do use twrp, make sure you don't reboot from side B! you will brick your device....
Beetle84 said:
Fastboot reboot fastboot is the correct way from the bootloader.
You need to update your platform tools.
Also you need to be on android 10 for these roms to boot.
Click to expand...
Click to collapse
That solved all the problem i was facing, thanks
revengesrage said:
One of the guys helped me out with this earlier. After you've unlocked your boot loader and if your on android 11.
Use rescue & smart assistant to backup your stock rom, it will tell you what kind it is too....
Then go download the android 10 stock version.
Then use moto tools by vache and load the android 10 stock rom into it. Just follow the directions and place it in bootloader.
after that flash whatever puppy of your choosing. Also I'd advise against flashing twrp just boot it. Also if you do use twrp, make sure you don't reboot from side B! you will brick your device....
Click to expand...
Click to collapse
Thansk for the tips, it is really important to set the partitions, i was struggling a lot to boot system since twrp redirected things to side B while A was set, i don't know why but now everthing is running flawlessly
11th Feb 2023
THIS GUIDE DOES NOT REQUIRE ROOT, BUT WILL WIPE YOUR EXISTING DATA! MAKE SURE TO HAVE A BACKUP.
Now before you start commenting that GSIs are not the same as Custom ROMs, please read below.
Spoiler Alert: There are probably not going to be any true Custom ROMs for the A52 5G for quite a long time. Due to the fact that Samsung's RIL system (the thing that makes your SIM/LTE/Mobile Data work) will not work on anything other than the Stock ROM, many developers have basically seen no point in developing even an official TWRP recovery for the phone. The above is true for all Samsung 5G Snapdragon-based devices. Using a GSI circumvents the RIL issue since all it does is sit in the system partition.
Therefore, your best bet if you really are intent on messing with your phone is to use GSIs. While some may argue that using GSIs for use as a daily driver comes with its issues, but I have been using mine with PE13+ for a few days now and everything functions as normal albeit while needing some workarounds (see POST-INSTALLATION section at bottom after installation).
You might be asking, why not use TWRP? The A52 5G does not have an official (or stable) TWRP yet. You can check this thread to be updated on the progress of the unofficial port! This guide is relatively simple, however, I have tried to make it as thorough as possible to help those who are just beginning on their GSI journey.
IT IS RECOMMENDED TO READ THROUGH THE GUIDE AT LEAST ONCE BEFORE UNDERTAKING ACTIONS!
----Your Warranty is Now Void (unless you live in AU or UK I guess)----
I am not responsible to any damage that comes from following this guide. While I have tried to keep information here as accurate and precise as possible, your mileage may vary. Be Warned!
This guide is tailored towards Windows devices and Samsung phones for target installation. Please seek alternatives to Odin such as Hiemdall if on Linux.
-----------------------------------------------------------------------------------
GUIDE:
Installing the PixelExperience+ GSI is recommended while using this guide as I cannot give any post-installation help to those using other GSIs.
General Commands for GSI Installation here:
Generic system images | Android Open Source Project
source.android.com
PixelExperience+ Stable GSI Download:
GitHub - ponces/treble_build_pe: Script and patches for building PHH-Treble Pixel Experience
Script and patches for building PHH-Treble Pixel Experience - GitHub - ponces/treble_build_pe: Script and patches for building PHH-Treble Pixel Experience
github.com
Prerequisites:
- An Android Treble-Enabled device. Use this app to check. Any devices launched at and after Android 10 should work.
- Windows system.
- Extraction software such as 7Zip or PeaZip.
- ADB and fastboot on computer, if not can download from official Google Android SDK. Make sure to add the platform-tools folder to PATH.
- Samsung Odin software (at the time of writing, the attached is the latest version).
- Stock Firmware for your phone model to completely reset if needed. Use this link to download yours. Make sure everything is correct before downloading!
- Your preferred GSI .xz file or .img
- Know which keys to press for your SPECIFIC Samsung model for Download Mode and Recovery Mode.
If your Samsung device already has fastbootd, boot into fastboot and skip straight to step 8!
Your Samsung device should be plugged into your computer from now on, with USB debugging enabled.
1. From the stock OneUI ROM, boot into Download Mode by holding VOL UP and VOL DOWN simultaneously when off or rebooting. Alternatively, you can run `adb reboot download`.
2. TURN OFF AUTO RESTART IN ODIN (options tab), AS RESTARTING TO STOCK ROM WILL WIPE CUSTOM RECOVERY!
3. If you are on an A52 5G, download the fastboot-recovery.tar file attached. If the file is missing, go to this thread and download the tar file. Otherwise, use this link and follow instructions to patch your model's recovery.img file. Then convert it back into a tar file for flashing.
4. Choose the patched recovery tar file. This is enables fastboot, as modern Samsung devices don't have this feature enabled. USE AP SLOT in ODIN TO FLASH.
5. Once flash is complete, hold VOL DOWN and SIDE KEY to exit Download Mode, then immediately change to VOL UP and SIDE KEY when screen goes black.
6. Press the VOL UP and VOL DOWN buttons to select the fastboot option once in Android recovery.
7. Press SIDE KEY to boot into fastbootd.
8. Run `fastboot devices` in Windows Terminal or Command Prompt to ensure the device is recognized.
9. If your GSI came in a compressed file (.xz, .zip, etc.) extract it with your program of choice. You should be left with a .img file. Rename this file to system.img. All of this should be done in your downloads folder.
10. Navigate your command prompt using `cd` to your Downloads folder. In my case, it was `cd C:\Users\User\Downloads\`. Your username might be different.
11. Run `fastboot erase system`.
12. Run `fastboot flash system system.img`. This might take a few minutes to complete. If you get an error about system partition size, scroll to the bottom of this article and run the command to free up space.
13. Once complete, run `fastboot -w`. If this returns an error, do not retry and proceed to the next step. If it ran successfully, skip to step 17.
14. Run `fastboot reboot`. Immediately after the screen goes black, hold the VOL UP and SIDE KEY buttons together until you reach Android recovery. If you fail to reach Android recovery, you may have to return to step 11. Worst case scenario, you may have to go to the PANIK GUIDE to completely reset, then go from step 1.
15. Use VOL UP and VOL DOWN to select 'Wipe Data/Factory Reset' and use SIDE KEY to confirm. Then repeat the process for 'Wipe Cache'.
16. After wiping data, use VOL UP and VOL DOWN to reboot (should be the first option in Android recovery).
17. If you ran `fastboot -w` without an error, run `fastboot reboot` and enjoy your newly flashed GSI! Make sure to check the POST-INSTALLATION section for some fixes.
POST-INSTALLATION SPECIFIC TO PIXELEXPERIENCE:
These are some quality-of-life improvements for your experience that I had to painstakingly test lol. If you have any of your own, make sure to share them with me in the comments!
1. Under-screen fingerprint sensor not working.
FIX: Go to Settings -> PHH Treble Settings -> Misc. -> Under-display fp color. Switch to the colour it was on your stock ROM (should be white for most Samsung devices). For some reason, PE13+ will only let you register fingerprints when the color is green. If you want to modify your fingerprints, switch the display fp color back to green. When done, return it to your stock ROM's colour.
2. Camera app features are extremely minimal.
FIX: Go to the GCam Hub to find the best app for your device.
3. No alternate refresh rate (or stuck at 60HZ)
FIX: Go to Settings -> PHH Treble Settings -> Misc. -> Force FPS. Choose the one you want.
4. Fingerprint sensor not working with Night Light.
FIX: There's no working fix yet. However, you can work around this by downloading a task automation app such as Tasker (paid) or Automator (freemium) to toggle the Night Light automatically when you are on the lock screen. Search online for a specific fix for your specific app. For starters, you can use 'toggle night light with <your automation app>'.
KNOWN UNFIXABLE ISSUES:
If you know any fixes that have worked for you, make sure to share them in the comments!
1. Face Unlock does not work on the A52 5G. It may or may not work on your device. IMO, it's not a deal breaker since I the fingerprint sensor is faster and more convenient in 99% of cases.
PANIK GUIDE:
If all hope seems lost and you somehow mess the phone up, wait until the next bootloop. When the screen goes black, press VOL UP and VOL DOWN immediately until it enters Download Mode. Then flash stock firmware through Odin. Use All files available in the stock firmware folder to their corresponding slot in Odin. Use the CSC file, NOT the HOME_CSC.
CONCLUSION:
Well, hopefully that just about sums up everything you need or wanted to know about the A52 5G and tinkering with the OS. If you need any more information just leave a comment on the thread and I'll try to get back to you.
Reserved.
Reserved.
Reserved.
{
"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"
}
Hello, I followed the steps, install the file fastboot a52 5g by odin, reboot into recovery, install img gsi, it seems that it gives a size error but it is installed. I follow these steps of course, unlocked booloader, fasboot mode fastboot erase system fastboot flash system system.img gives size error but does it install?. Finally the fastboot -w command and reboot but it stays rebooting. I have android 13 a52 5g. I put images fastboot delete-logical-partition product_a not working for me
For some reason, attempting to erase the system partition results in error:
Erasing 'system' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Worked like a charm. Thank you very much. I now have something else to play with my a52 5g. Will try with other gsi's.
markpanget1 said:
Worked like a charm. Thank you very much. I now have something else to play with my a52 5g. Will try with other gsi's.
Click to expand...
Click to collapse
Hello, what rom did you use? Well, I tried pixel, cdroid and it gives me a partition size error. I have the a52 5g android 13
ped1609 said:
Hello, what rom did you use? Well, I tried pixel, cdroid and it gives me a partition size error. I have the a52 5g android 13
Click to expand...
Click to collapse
Pixel experience plus. Did you erase the system properly? Try to check if fastboot drivers is properly installed. I do get some error but i just proceeded with every steps.
markpanget1 said:
ÇPixel experience plus. Did you erase the system properly? Try to check if fastboot drivers is properly installed. I do get some error but i just proceeded with every steps.
Click to expand...
Click to collapse
markpanget1 said:
Pixel experience plus. Did you erase the system properly? Try to check if fastboot drivers is properly installed. I do get some error but i just proceeded with every steps.
Click to expand...
Click to collapse
I follow all the steps, install the recovery with odin, enter recovery, then fasboot mode where fasboot devices recognize it with a number, then fastboot erase system, this is where fastboot flash fails system system.img partition size error, I hit fastboot delete-logical-partition product_a but it does nothing.
ped1609 said:
I follow all the steps, install the recovery with odin, enter recovery, then fasboot mode where fasboot devices recognize it with a number, then fastboot erase system, this is where fastboot flash fails system system.img partition size error, I hit fastboot delete-logical-partition product_a but it does nothing.
Click to expand...
Click to collapse
Im sorry, i'm not an expert on this, im afraid i cant answer your question about that except if i experience that error, maybe i can find a workaround with myself , then maybe i can help you. Maybe later i'll try to flash my phone again with gsi and record it all and share it with this forum.
markpanget1 said:
Im sorry, i'm not an expert on this, im afraid i cant answer your question about that except if i experience that error, maybe i can find a workaround with myself , then maybe i can help you. Maybe later i'll try to flash my phone again with gsi and record it all and share it with this forum.
Click to expand...
Click to collapse
Thanks, maybe it's a PC problem, I'll restore them to the factory and try.
Hello, I already managed to install gsi pixel plus, partition errors too large, pixel on the a52 5g with android 13. 1 root method a525g with android 13, use AP_A526BXXU3EWD2 according to your model to place it in the mobile memory 2 install magisk, patch the ap will create a file on the mobile pass it to pc, 3 open Odin, reinstall the official rom but with the patched ap, when you start the mobile, please install the magisk app again as it is removed, When you open it, you will be root. 4 then go back to odin to install the fastbootd-recovery file in the ap box as the tutorial says above. 5 when you install the file enter the recovery as it says above press power and volume down at the same time to exit odin and quickly when it exits black screen volume up and power to enter recovery. 5 when you enter recovery and you are in fasboot mode, this is where it gave me trouble normal cmd didn't work. Download platform-tools, create a folder called rom a52, inside the plattform -tools folder I opened cmd the commands i used and it worked, 1 fastboot devices to indicate that it recognizes it, 2 fastboot delete-logical-partition product this worked 3 fastboot erase system 4 fastboot flash system system.img 5 fastboot -w 6 fastboot reboot and reboot into the new pixel system, Sorry if it's too long but I had a hard time solving the partition size.
Más información sobre este texto de origenPara obtener más información sobre la traducción, se necesita el texto de origen
Enviar comentarios
Paneles laterales
https://translate.google.es/saved
https://translate.google.es/contribute
ped1609 said:
Hello, I already managed to install gsi pixel plus, partition errors too large, pixel on the a52 5g with android 13. 1 root method a525g with android 13, use AP_A526BXXU3EWD2 according to your model to place it in the mobile memory 2 install magisk, patch the ap will create a file on the mobile pass it to pc, 3 open Odin, reinstall the official rom but with the patched ap, when you start the mobile, please install the magisk app again as it is removed, When you open it, you will be root. 4 then go back to odin to install the fastbootd-recovery file in the ap box as the tutorial says above. 5 when you install the file enter the recovery as it says above press power and volume down at the same time to exit odin and quickly when it exits black screen volume up and power to enter recovery. 5 when you enter recovery and you are in fasboot mode, this is where it gave me trouble normal cmd didn't work. Download platform-tools, create a folder called rom a52, inside the plattform -tools folder I opened cmd the commands i used and it worked, 1 fastboot devices to indicate that it recognizes it, 2 fastboot delete-logical-partition product this worked 3 fastboot erase system 4 fastboot flash system system.img 5 fastboot -w 6 fastboot reboot and reboot into the new pixel system, Sorry if it's too long but I had a hard time solving the partition size.
Más información sobre este texto de origenPara obtener más información sobre la traducción, se necesita el texto de origen
Enviar comentarios
Paneles laterales
https://translate.google.es/saved
https://translate.google.es/contribute
Click to expand...
Click to collapse
Oh, that's what i forgot to mention, i'm already rooted with latest magisk long before i performed gsi flashing.
Good for you bro! congrats!
markpanget1 said:
Oh, that's what i forgot to mention, i'm already rooted with latest magisk long before i performed gsi flashing.
Good for you bro! congrats!
Click to expand...
Click to collapse
Thanks, I've tried 2 gsi but it has little pixel brightness, cdroid, I'll try lineage and evolution to see if the brightness is corrected.
I see mention of the Snapdragon variants. Does that mean the bootloader doesn't need to be unlocked to flash GSIs? I have the U1 variant
lowridincrew said:
I see mention of the Snapdragon variants. Does that mean the bootloader doesn't need to be unlocked to flash GSIs? I have the U1 variant
Click to expand...
Click to collapse
You need to unlock the bootloader to flash GSI, yes.
C:\Users\user\Downloads\PixelExperience_Plus_arm64-ab-13.0-20230503-UNOFFICIAL.img>fastboot flash system system.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.063s]
sending sparse 'system' (256443 KB)...
OKAY [ 6.929s]
writing 'system'...
OKAY [ 0.890s]
sending sparse 'system' (258773 KB)...
OKAY [ 6.679s]
writing 'system'...
OKAY [ 0.641s]
sending sparse 'system' (255920 KB)...
OKAY [ 6.754s]
writing 'system'...
OKAY [ 0.714s]
sending sparse 'system' (258109 KB)...
OKAY [ 6.957s]
writing 'system'...
OKAY [ 0.687s]
sending sparse 'system' (259589 KB)...
OKAY [ 6.674s]
writing 'system'...
OKAY [ 0.687s]
sending sparse 'system' (258310 KB)...
OKAY [ 6.678s]
writing 'system'...
OKAY [ 0.726s]
sending sparse 'system' (259101 KB)...
OKAY [ 6.910s]
writing 'system'...
OKAY [ 0.671s]
sending sparse 'system' (259985 KB)...
OKAY [ 6.582s]
writing 'system'...
OKAY [ 0.617s]
sending sparse 'system' (259396 KB)...
OKAY [ 7.228s]
writing 'system'...
OKAY [ 0.616s]
sending sparse 'system' (260673 KB)...
OKAY [ 6.939s]
writing 'system'...
OKAY [ 0.641s]
sending sparse 'system' (260774 KB)...
OKAY [ 6.919s]
writing 'system'...
OKAY [ 0.695s]
sending sparse 'system' (245741 KB)...
OKAY [ 6.211s]
writing 'system'...
OKAY [ 0.672s]
sending sparse 'system' (206734 KB)...
OKAY [ 5.591s]
writing 'system'...
OKAY [ 0.641s]
finished. total time: 96.193s
C:\Users\user\Downloads\PixelExperience_Plus_arm64-ab-13.0-20230503-UNOFFICIAL.img>fastboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Creating filesystem with parameters:
Size: 629145600
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 2400
Label:
Blocks: 153600
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/38400 inodes and 4936/153600 blocks
target reported max download size of 268435456 bytes
erasing 'userdata'...
OKAY [ 10.502s]
erasing 'cache'...
OKAY [ 0.015s]
sending 'cache' (11752 KB)...
OKAY [ 0.284s]
writing 'cache'...
OKAY [ 0.102s]
finished. total time: 10.932s
these are my fastboot logs, when I perform "fastboot reboot" I got an endless bootloop, I followed all steps and everything worked fine until this, any help please?
EDIT: I tried also to perform a factory data reset from recovery instead of "fastboot -w" command, nothing changed
Shiina_ said:
C:\Users\user\Downloads\PixelExperience_Plus_arm64-ab-13.0-20230503-UNOFFICIAL.img>fastboot flash system system.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.063s]
sending sparse 'system' (256443 KB)...
OKAY [ 6.929s]
writing 'system'...
OKAY [ 0.890s]
sending sparse 'system' (258773 KB)...
OKAY [ 6.679s]
writing 'system'...
OKAY [ 0.641s]
sending sparse 'system' (255920 KB)...
OKAY [ 6.754s]
writing 'system'...
OKAY [ 0.714s]
sending sparse 'system' (258109 KB)...
OKAY [ 6.957s]
writing 'system'...
OKAY [ 0.687s]
sending sparse 'system' (259589 KB)...
OKAY [ 6.674s]
writing 'system'...
OKAY [ 0.687s]
sending sparse 'system' (258310 KB)...
OKAY [ 6.678s]
writing 'system'...
OKAY [ 0.726s]
sending sparse 'system' (259101 KB)...
OKAY [ 6.910s]
writing 'system'...
OKAY [ 0.671s]
sending sparse 'system' (259985 KB)...
OKAY [ 6.582s]
writing 'system'...
OKAY [ 0.617s]
sending sparse 'system' (259396 KB)...
OKAY [ 7.228s]
writing 'system'...
OKAY [ 0.616s]
sending sparse 'system' (260673 KB)...
OKAY [ 6.939s]
writing 'system'...
OKAY [ 0.641s]
sending sparse 'system' (260774 KB)...
OKAY [ 6.919s]
writing 'system'...
OKAY [ 0.695s]
sending sparse 'system' (245741 KB)...
OKAY [ 6.211s]
writing 'system'...
OKAY [ 0.672s]
sending sparse 'system' (206734 KB)...
OKAY [ 5.591s]
writing 'system'...
OKAY [ 0.641s]
finished. total time: 96.193s
C:\Users\user\Downloads\PixelExperience_Plus_arm64-ab-13.0-20230503-UNOFFICIAL.img>fastboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Creating filesystem with parameters:
Size: 629145600
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 2400
Label:
Blocks: 153600
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/38400 inodes and 4936/153600 blocks
target reported max download size of 268435456 bytes
erasing 'userdata'...
OKAY [ 10.502s]
erasing 'cache'...
OKAY [ 0.015s]
sending 'cache' (11752 KB)...
OKAY [ 0.284s]
writing 'cache'...
OKAY [ 0.102s]
finished. total time: 10.932s
these are my fastboot logs, when I perform "fastboot reboot" I got an endless bootloop, I followed all steps and everything worked fine until this, any help please?
EDIT: I tried also to perform a factory data reset from recovery instead of "fastboot -w" command, nothing changed
Click to expand...
Click to collapse
Hello, that happened to me, above I put how to install..it seems to be installed but not.
ped1609 said:
Hello, that happened to me, above I put how to install..it seems to be installed but not.
Click to expand...
Click to collapse
Hi! Thanks for your reply, I just tried following your guide but nothing changed, still in bootloop
EDIT: I tried using another PixelExperience GSI and it worked, so I guess that I solved, thanks