Finally made the video tutorial to Root Nexus 6P
Starting from the beginning to flash the stock factory images which is modified by Chainfire to be rooted :
Thereafter One needs to Unlock Bootloader and Install TWRP recovery on Nexus 6P :
And at the end successfully rooted Nexus 6p with the help of modded Boot.IMG for Amrshmallow done byChainfire:
If you are struck anywhere
Then let me know
Thank You
Kernels Coming soon
cant flash image of angler factory
Please let me know if anyone can help with this problem been 24 hours of trial and error and researching on the boards but need some help.
I have device unlocked ready to boot load and run the flash.bat as you have tutored and I get this error message:
after flash attempt of angler factory image: "angler-mdb08m-factory-dbc17940"
target reported max download size of 494927872 bytes
sending 'bootloader' (3524 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
OKAY [ 0.203s]
finished. total time: 0.297s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
target reported max download size of 494927872 bytes
sending 'radio' (48360 KB)...
OKAY [ 1.063s]
writing 'radio'...
OKAY [ 2.156s]
finished. total time: 3.235s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
W/ ( 7004): Zip: unable to truncate file to 2004185752: File too large
failed to extract 'system.img': I/O Error
Press any key to exit...
Hey, thanks for the videos man. So if we flash the boot.img provided by Chainfire, does that also decrypt the phone or do we have to format userdata as well?
dhuddart said:
Please let me know if anyone can help with this problem been 24 hours of trial and error and researching on the boards but need some help.
I have device unlocked ready to boot load and run the flash.bat as you have tutored and I get this error message:
after flash attempt of angler factory image: "angler-mdb08m-factory-dbc17940"
target reported max download size of 494927872 bytes
sending 'bootloader' (3524 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
OKAY [ 0.203s]
finished. total time: 0.297s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
target reported max download size of 494927872 bytes
sending 'radio' (48360 KB)...
OKAY [ 1.063s]
writing 'radio'...
OKAY [ 2.156s]
finished. total time: 3.235s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
W/ ( 7004): Zip: unable to truncate file to 2004185752: File too large
failed to extract 'system.img': I/O Error
Press any key to exit...
Click to expand...
Click to collapse
Well this should not happen! If at all try changing PC and then installing drivers again. Make sure that you have UNLOCKED BOOTLOADER BEFORE FLASHING FACTORY IMAGE.
Related
Seems that with every "update" my 7840 gets slower and slower. The latest 5.1 has made things unbearable so I am looking to go back to KK, root nice to have but non essential. I installed the latest drivers and downloaded IntelAndroid-FBRL-01-17-2015 per the rooting thread, but when I try to run launcher.bat I get the following
Code:
copy needed files to our device
target reported max download size of 536870912 bytes
sending '/tmp/recovery.zip' (3477 KB)...
OKAY [ 0.390s]
writing '/tmp/recovery.zip'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.667s
target reported max download size of 536870912 bytes
sending '/tmp/recovery.launcher' (469 KB)...
OKAY [ 0.278s]
writing '/tmp/recovery.launcher'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.546s
target reported max download size of 536870912 bytes
sending '/sbin/partlink' (158 KB)...
OKAY [ 0.281s]
writing '/sbin/partlink'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.547s
issue fastboot oem "stop_partitioning" command to start cwm recovery:
...
FAILED (remote: command not allowed in this device state)
finished. total time: 0.394s
This thread suggests that what I am trying to do may be impossible
http://forum.xda-developers.com/dell-venue/general/dell-venue-8-7840-rollback-to-kitkat-t3157770
What are my options here. I am pretty much ready to throw the tablet in the trashcan if I can't remove the atrocious 5.1 update.
[IOON] OPT RESET & Recovery Tool
Hi everyone,
I have created a Recovery Tool for the OPT. IOON is a OPEN SOURCE Project this mean that everyone can share ideas and develop. However if you have ideas please share.
IOON should be the (NON OFFICAL) OFFICAL Recovery Tool. It fix software bricks, wifi issues, fingerprint, imeu, simcard & bluetooth. And new features will follow.
Please note I’m a human if I do something wrong please tell me
I want that IOON should be a community Project developed for the Community by the Community
Note:
For Windows and Linux
IOON recover the partitions over fastboot
Fastboot is required !
Warning
You do this on your one risk. I’m not responsible for any damage. I’m also not responsible:
If your alarm clock is not working and you gets fired.
If you phone will get overheat
If the phone don’t turn on.
Features
1) Erase everything
2) Back to stock
2.1) Oxygen 2.1
2.2) Oxgen 3.0
3) [Auto] custom Recovery
4) Auto root
IOON erase:
Cache
Userdata & Userdata_64
System
Modem
Modemst1
Modemst2
And More
Instructions:
1) Download and install fastboot
2) Download the ZIP file
3) Extract the ZIP file
$ sudo unzip restore.zip
4) Move in the folder
$ cd restore
5) Type:
sudo chmod +x restore.sh
sudo ./restore
[now a Menu should pop up]
Select Erase
Select back to stock
Select custom recovery (please select costum recovery if something goes wrong you have access to your phone & and file storage )
Download the newest oxygen version
Reboot into recovery [Press volume button down and power button at the same time]
Connect your phone with PC
Drag and Drop the oxygen version on your phone
Go to flash
Select oxygen version and click on flash
Click on change recovery
Reboot
Done!
Solves:
Fingerprint BUG ( 50 % changes ) [If it is a software Brick]
Fix IMEU BUG
Wifi and simcard and bluetooth should now work
Fix crashes after flashing a android 6 ROM
Bugs:
Downloads
Version 1.0 Deleted
Version 1.1 :Mod Edit link removed.
Version 1.2 Uploaded soon!
Source Code
https://github.com/deltaxflux/IOON
I now my English is bad :angel:
Wrong Link....
Updated !
Or try this one http://www.mediafire.com/download/1jf67jsvlm1thr5/restore.zip
Yes it's work ! Thanks
@deltaxflux Instructions are more from linux POV.. need commands for windows..
@s_vohra I will add the Instruction soon, let me work on the windows version
Hello,
@deltaxflux
I would like to erase all partitions and recreate them from scratch.
Is it possible with this tool?
If so, how?
jukyO said:
Hello,
@deltaxflux
I would like to erase all partitions and recreate them from scratch.
Is it possible with this tool?
If so, how?
Click to expand...
Click to collapse
@deltaFlux,
used erase option.
Now my Internal storage is 9 Gb only. Solution?
jukyO said:
@deltaFlux,
used erase option.
Now my Internal storage is 9 Gb only. Solution?
Click to expand...
Click to collapse
What did u do ?
Notice: IOON will not longer developt because I'm to busy at the moement and there better reset tools out there
deltaxflux said:
What did u do ?
Notice: IOON will not longer developt because I'm to busy at the moement and there better reset tools out there
Click to expand...
Click to collapse
used Erase option.
recovered all partitions except EFS (modemst1, modemst2) - mmcblkop17 and mmcblk0p18.
I have backed up EFS through TWRP recovery, but it does not contain modemst1 and modemst2, but 'oem_stanvbk', which is mmcblk0p20.
Do you have an idea? Can I recreate mmcblkop17 and mmcblk0p18 again?
How does restore of EFS works?
So u have root? Try the back to stock option -) root -) custom recovery modemst1 and modemst2 will be restored After reboot into recovery. Go to wipe -> advanced wipe -> select the partitions -> select recovery / repaire
to this twice !
After flash the oxygen 2.21 ROM. It should work if not contact me
deltaxflux said:
So u have root? Try the back to stock option -) root -) custom recovery modemst1 and modemst2 will be restored After reboot into recovery. Go to wipe -> advanced wipe -> select the partitions -> select recovery / repaire
to this twice !
After flash the oxygen 2.21 ROM. It should work if not contact me
Click to expand...
Click to collapse
Link to OOS 2.2.1? Some special version or any?
Sent from my A0001 using XDA-Developers mobile app
deltaxflux said:
So u have root? Try the back to stock option -) root -) custom recovery modemst1 and modemst2 will be restored After reboot into recovery. Go to wipe -> advanced wipe -> select the partitions -> select recovery / repaire
to this twice !
After flash the oxygen 2.21 ROM. It should work if not contact me
Click to expand...
Click to collapse
Did that.
Output of tool:
#########################################################
# #
# OPT [RECOVERY] 1.1 < Fluxion Is The Future > #
# by Deltax #
# #
#########################################################
Select your option
1) Back to stock
2) Root
3) Erase all
4) Custom recovery
5) Reboot
6) Exit
#> 1
#########################################################
# #
# OPT [RECOVERY] 1.1 < Fluxion Is The Future > #
# by Deltax #
# #
#########################################################
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.048s]
finished. total time: 0.048s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.490s]
finished. total time: 0.490s
erasing 'recovery'...
OKAY [ 0.028s]
finished. total time: 0.028s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.477s]
finished. total time: 1.477s
erasing 'userdata_64'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.020s
erasing 'modem'...
OKAY [ 0.038s]
finished. total time: 0.038s
erasing 'modemst1'...
OKAY [ 0.032s]
finished. total time: 0.032s
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
erasing 'recovery'...
OKAY [ 0.024s]
finished. total time: 0.024s
#########################################################
# #
# OPT [RECOVERY] 1.1 < Fluxion Is The Future > #
# by Deltax #
# #
#########################################################
target reported max download size of 536870912 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.057s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.057s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'apdp' (256 KB)...
OKAY [ 0.039s]
writing 'apdp'...
OKAY [ 0.024s]
finished. total time: 0.063s
target reported max download size of 536870912 bytes
sending 'bluetooth' (1024 KB)...
OKAY [ 0.057s]
writing 'bluetooth'...
OKAY [ 0.031s]
finished. total time: 0.087s
target reported max download size of 536870912 bytes
sending 'boot' (21165 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.179s]
finished. total time: 0.710s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.022s]
sending 'cache' (6248 KB)...
OKAY [ 0.186s]
writing 'cache'...
OKAY [ 0.072s]
finished. total time: 0.280s
target reported max download size of 536870912 bytes
sending 'config' (512 KB)...
OKAY [ 0.048s]
writing 'config'...
OKAY [ 0.026s]
finished. total time: 0.074s
target reported max download size of 536870912 bytes
sending 'ddr' (1024 KB)...
OKAY [ 0.057s]
writing 'ddr'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.077s
target reported max download size of 536870912 bytes
sending 'devinfo' (1 KB)...
OKAY [ 0.040s]
writing 'devinfo'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'dpo' (1 KB)...
OKAY [ 0.040s]
writing 'dpo'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'driver' (32768 KB)...
OKAY [ 0.800s]
writing 'driver'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.816s
target reported max download size of 536870912 bytes
sending 'fsc' (1 KB)...
OKAY [ 0.040s]
writing 'fsc'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'fsg' (1536 KB)...
OKAY [ 0.066s]
writing 'fsg'...
OKAY [ 0.034s]
finished. total time: 0.100s
target reported max download size of 536870912 bytes
sending 'hyp' (512 KB)...
OKAY [ 0.048s]
writing 'hyp'...
OKAY [ 0.028s]
finished. total time: 0.076s
target reported max download size of 536870912 bytes
sending 'hyp' (512 KB)...
OKAY [ 0.048s]
writing 'hyp'...
OKAY [ 0.027s]
finished. total time: 0.076s
target reported max download size of 536870912 bytes
sending 'keystore' (512 KB)...
OKAY [ 0.048s]
writing 'keystore'...
FAILED (remote: image is not a keystore file)
finished. total time: 0.072s
target reported max download size of 536870912 bytes
sending 'limits' (1 KB)...
OKAY [ 0.040s]
writing 'limits'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'LOGO' (16384 KB)...
OKAY [ 0.409s]
writing 'LOGO'...
OKAY [ 0.144s]
finished. total time: 0.553s
target reported max download size of 536870912 bytes
sending 'misc' (1024 KB)...
OKAY [ 0.057s]
writing 'misc'...
OKAY [ 0.030s]
finished. total time: 0.087s
target reported max download size of 536870912 bytes
sending 'modem' (81920 KB)...
OKAY [ 1.983s]
writing 'modem'...
OKAY [ 0.626s]
finished. total time: 2.609s
target reported max download size of 536870912 bytes
sending 'msadp' (256 KB)...
OKAY [ 0.049s]
writing 'msadp'...
OKAY [ 0.026s]
finished. total time: 0.075s
target reported max download size of 536870912 bytes
sending 'oem_dycnvbk' (10240 KB)...
OKAY [ 0.268s]
writing 'oem_dycnvbk'...
OKAY [ 0.096s]
finished. total time: 0.364s
target reported max download size of 536870912 bytes
sending 'oem_stanvbk' (10240 KB)...
OKAY [ 0.269s]
writing 'oem_stanvbk'...
OKAY [ 0.098s]
finished. total time: 0.368s
target reported max download size of 536870912 bytes
sending 'param' (1024 KB)...
OKAY [ 0.057s]
writing 'param'...
OKAY [ 0.035s]
finished. total time: 0.092s
target reported max download size of 536870912 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.800s]
writing 'persist'...
OKAY [ 0.261s]
finished. total time: 1.061s
target reported max download size of 536870912 bytes
sending 'pmic' (128 KB)...
OKAY [ 0.039s]
writing 'pmic'...
OKAY [ 0.021s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'pmic' (128 KB)...
OKAY [ 0.039s]
writing 'pmic'...
OKAY [ 0.021s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'reserve1' (8096 KB)...
OKAY [ 0.214s]
writing 'reserve1'...
OKAY [ 0.097s]
finished. total time: 0.311s
target reported max download size of 536870912 bytes
sending 'reserve2' (16192 KB)...
OKAY [ 0.410s]
writing 'reserve2'...
OKAY [ 0.138s]
finished. total time: 0.547s
target reported max download size of 536870912 bytes
sending 'rpm' (500 KB)...
OKAY [ 0.048s]
writing 'rpm'...
OKAY [ 0.027s]
finished. total time: 0.075s
target reported max download size of 536870912 bytes
sending 'recovery' (28144 KB)...
OKAY [ 0.688s]
writing 'recovery'...
OKAY [ 0.232s]
finished. total time: 0.921s
target reported max download size of 536870912 bytes
sending 'sbl1' (1024 KB)...
OKAY [ 0.057s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'sbl1' (1024 KB)...
OKAY [ 0.057s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
error: cannot load 'sdi.img': No such file or directory
target reported max download size of 536870912 bytes
sending 'sec' (128 KB)...
OKAY [ 0.039s]
writing 'sec'...
OKAY [ 0.023s]
finished. total time: 0.062s
target reported max download size of 536870912 bytes
sending 'ssd' (8 KB)...
OKAY [ 0.040s]
writing 'ssd'...
OKAY [ 0.021s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'tz' (1024 KB)...
OKAY [ 0.057s]
writing 'tz'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'tz' (1024 KB)...
OKAY [ 0.057s]
writing 'tz'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.223s]
sending 'userdata' (510526 KB)...
OKAY [ 12.347s]
writing 'userdata'...
OKAY [ 3.906s]
finished. total time: 16.477s
target reported max download size of 536870912 bytes
sending 'userdata_64' (515143 KB)...
OKAY [ 12.662s]
writing 'userdata_64'...
FAILED (remote: partition table doesn't exist)
finished. total time: 12.678s
So those 5 failed:
erasing 'userdata'...
OKAY [ 1.477s]
finished. total time: 1.477s
erasing 'userdata_64'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.020s
sending 'ddr' (1024 KB)...
OKAY [ 0.057s]
writing 'ddr'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.077s
target reported max download size of 536870912 bytes
writing 'driver'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.816s
target reported max download size of 536870912 bytes
writing 'keystore'...
FAILED (remote: image is not a keystore file)
finished. total time: 0.072s
target reported max download size of 536870912 bytes
writing 'userdata_64'...
FAILED (remote: partition table doesn't exist)
finished. total time: 12.678s
After reboot to recovery, under wipe-advance wipe there is:
Dalvik
System
Data
Internal Storage
Cache
If I try to mount system, cannot do it.
Internal storage shows 9 Gb.
Do you have another ideas?
Thanks!
Just reset it with Qualcomm tool
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
[
omrij said:
Just reset it with Qualcomm tool
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
[
Click to expand...
Click to collapse
Did that 1st. Removed tampered bit before the procedure. No go.
Still
oem_nv_backup the nv partition is invalid
is shown.
Anyone knows how to check if modemst1 modemst2 blocks/partitions are created properly?
Will this erase internal storage too?
I want to use this tool because my FP sensor isnt working so i wanna give it a try
LOL9988 said:
Will this erase internal storage too?
I want to use this tool because my FP sensor isnt working so i wanna give it a try
Click to expand...
Click to collapse
It'll wipe everything, but I wouldn't use it because some of your partitions don't need to be wiped and some of the fastboot commands in the restore.sh file are wrong and will cause issues
For example:
sudo fastboot flash userdata userdata.img will flash the 16GB version's userdata.img even if you have a 64GB version of the phone.
sudo fastboot flash userdata_64 userdata_64G.img won't work because there is no userdata_64 partition - it's called userdata on both versions.
TBH, you're better off using advanced wipe in TWRP to wipe internal storage.
Waiting for the windows version to see if this app do the miracle fixing the second IMEI number on my phone, I tried everything already. Thanks for make this app.
Sent from my unknown using Tapatalk
iam newbie and want to try this solution to repair my fingerprint how to?
BEWARE, DO NOT SELECT ERASE OR IT WILL ERASE ALL YOUR MODEMS AND WONT BE ABLE TO GET THEM BACK. MY PHONE'S IMEIs ARE BROKEN. BOTH IMEI SHOW 0 AND CANNOT CONNECT MY PHONE TO ANY CELLPHONE COMPANY
Hi,
Can someone clarify what this message means and why fastboot is failing?
Thanks
Code:
# fastboot flash aboot aboot_300032.bin
target reported max download size of 536870912 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.036s]
writing 'aboot'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.038s
Probably because your phone has unlocked bootloader and needs to be locked .
Instruction how to do that .
https://www.google.rs/amp/s/www.theandroidsoul.com/relock-bootloader-fastboot-android/amp/
Good luck : )
Any ideas how to solve this catch 22? I mean other than using the LG Flash Tool or LG UP. I didn't much success with them.
Thanks
Code:
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.749s]
writing 'modem'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 2.750s
# fastboot oem lock
...
(bootloader) Erasing userdata and cache
OKAY [ 1.881s]
finished. total time: 1.882s
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.775s]
writing 'modem'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 2.776s
greerdd said:
Any ideas how to solve this catch 22? I mean other than using the LG Flash Tool or LG UP. I didn't much success with them.
Thanks
Code:
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.749s]
writing 'modem'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 2.750s
# fastboot oem lock
...
(bootloader) Erasing userdata and cache
OKAY [ 1.881s]
finished. total time: 1.882s
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.775s]
writing 'modem'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 2.776s
Click to expand...
Click to collapse
I have the same problem. Did u solve this ?
exact same problem, is there any solution exist?
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.
I was trying to upgrade from Android 11 to 12 with an Android 12 GSI using Fastboot, but whenever I try to install the system.img, it always fails with the error:
(bootloader) Preflash validation failed FAILED (remote failure)
Click to expand...
Click to collapse
I have seen that this error is common if you have the bootloader locked, but mine is unlocked.
Here's the full list of commands I used:
Code:
F:\Programs\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (52224 KB)...
OKAY [ 1.276s]
writing 'boot_b'...
OKAY [ 0.779s]
finished. total time: 2.056s
F:\Programs\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.005s]
writing 'vbmeta_b'...
(bootloader) WARNING: vbmeta_b anti rollback downgrade, 0 vs 16
OKAY [ 0.036s]
finished. total time: 0.041s
F:\Programs\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/3 (786340 KB)...
OKAY [ 19.870s]
writing 'system_b' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.962s
Why do I get this error, and is there any way to solve it?
ByteSeb said:
I was trying to upgrade from Android 11 to 12 with an Android 12 GSI using Fastboot, but whenever I try to install the system.img, it always fails with the error:
I have seen that this error is common if you have the bootloader locked, but mine is unlocked.
Here's the full list of commands I used:
Code:
F:\Programs\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (52224 KB)...
OKAY [ 1.276s]
writing 'boot_b'...
OKAY [ 0.779s]
finished. total time: 2.056s
F:\Programs\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.005s]
writing 'vbmeta_b'...
(bootloader) WARNING: vbmeta_b anti rollback downgrade, 0 vs 16
OKAY [ 0.036s]
finished. total time: 0.041s
F:\Programs\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/3 (786340 KB)...
OKAY [ 19.870s]
writing 'system_b' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.962s
Why do I get this error, and is there any way to solve it?
Click to expand...
Click to collapse
You need to be in fastboot d to flash system images. In regular fastboot, type fastboot reboot fastboot.
Beetle84 said:
You need to be in fastboot d to flash system images. In regular fastboot, type fastboot reboot fastboot.
Click to expand...
Click to collapse
It seems like that was working, but now I get this error:
FAILED (remote: Operation not permitted)
Click to expand...
Click to collapse
Here's the commands I used:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot_a' (52224 KB)...
OKAY [ 1.373s]
writing 'boot_a'...
OKAY [ 1.584s]
finished. total time: 2.958s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 268435456 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.003s]
writing 'vbmeta_a'...
OKAY [ 0.047s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/7 (262108 KB)...
OKAY [ 7.087s]
writing 'system_a' 1/7...
OKAY [ 1.746s]
sending sparse 'system_a' 2/7 (262120 KB)...
OKAY [ 7.075s]
writing 'system_a' 2/7...
OKAY [ 1.723s]
sending sparse 'system_a' 3/7 (262112 KB)...
OKAY [ 7.015s]
writing 'system_a' 3/7...
OKAY [ 1.746s]
sending sparse 'system_a' 4/7 (262124 KB)...
OKAY [ 7.001s]
writing 'system_a' 4/7...
OKAY [ 1.736s]
sending sparse 'system_a' 5/7 (262088 KB)...
OKAY [ 7.013s]
writing 'system_a' 5/7...
FAILED (remote: Operation not permitted)
finished. total time: 43.777s
ByteSeb said:
It seems like that was working, but now I get this error:
Here's the commands I used:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot_a' (52224 KB)...
OKAY [ 1.373s]
writing 'boot_a'...
OKAY [ 1.584s]
finished. total time: 2.958s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 268435456 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.003s]
writing 'vbmeta_a'...
OKAY [ 0.047s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/7 (262108 KB)...
OKAY [ 7.087s]
writing 'system_a' 1/7...
OKAY [ 1.746s]
sending sparse 'system_a' 2/7 (262120 KB)...
OKAY [ 7.075s]
writing 'system_a' 2/7...
OKAY [ 1.723s]
sending sparse 'system_a' 3/7 (262112 KB)...
OKAY [ 7.015s]
writing 'system_a' 3/7...
OKAY [ 1.746s]
sending sparse 'system_a' 4/7 (262124 KB)...
OKAY [ 7.001s]
writing 'system_a' 4/7...
OKAY [ 1.736s]
sending sparse 'system_a' 5/7 (262088 KB)...
OKAY [ 7.013s]
writing 'system_a' 5/7...
FAILED (remote: Operation not permitted)
finished. total time: 43.777s
Click to expand...
Click to collapse
if you update adb, you will see that it gives you an error for no space (atleast for me it did). To fix this, since your phone uses AB partitioning, you will need to do fastboot delete-logical-partition product_a and it should be good since you are using a GSI
Thanks! That worked
GigaPVP said:
if you update adb, you will see that it gives you an error for no space (atleast for me it did). To fix this, since your phone uses AB partitioning, you will need to do fastboot delete-logical-partition product_a and it should be good since you are using a GSI
Click to expand...
Click to collapse
i tried "fastboot delete-logical-partiton product_a" (a partition was active)
but error message occurs "unknown command delete-logical-partiton "
~using latest platform toot
~installing Android 13 GSI arm64+GSM .img
~on pixel 3