Hey guys, I have a quick question about my warranty and root with the Elemental recovery. I rooted my tablet and loaded the recovery and now am having some issues UNRELATED to the modding of my tablet. Now I am going to send it in for repair and want to make sure they don't receive a modded tablet. Do I just need to do a factory reset or are there some other steps I need to take to make sure that when they receive my tablet, they can't tell it was ever modified? I read about a flash counter somewhere, so I'm not sure if I have to do anything with that, or if it really is as easy as a factory reset. I would love any and all help and look forward to hearing back.
Thanks a bunch,
Chris
ChrispyChris said:
Hey guys, I have a quick question about my warranty and root with the Elemental recovery. I rooted my tablet and loaded the recovery and now am having some issues UNRELATED to the modding of my tablet. Now I am going to send it in for repair and want to make sure they don't receive a modded tablet. Do I just need to do a factory reset or are there some other steps I need to take to make sure that when they receive my tablet, they can't tell it was ever modified? I read about a flash counter somewhere, so I'm not sure if I have to do anything with that, or if it really is as easy as a factory reset. I would love any and all help and look forward to hearing back.
Thanks a bunch,
Chris
Click to expand...
Click to collapse
I would say to do a back up if possible. After what I did is a flash the factory image and I relock the bootloader. If you don't flash the factory image and you don't relock the bootloader , they would just send it back.
Here are the commends for the flashing of recovery images.
Fastboot flash bootloader bootloader...
Fastboot reboot
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
Fastboot erase system
Fastboot flash system system.img (this can take up to 15 minutes do not cancel process)
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot erase vendor
Fastboot flash vendor vendor.img
Fastboot reboot bootloader
After you finish that, you must type the following command.
Command to relock your devices
Fastboot oem_lock
I hope this was helpful.
I don't see why you can't just use the "flash all" batch file. Does the batch file do something different?
whowatchlist said:
I don't see why you can't just use the "flash all" batch file. Does the batch file do something different?
Click to expand...
Click to collapse
Yes but must of the time it says the it could found files. Try it and if it doesn't flash all do the steps that I posted before
Just wanted to thank you jonny, I'm fresh on the newest factory image.
Its no problem
Related
I am new to cell phone mods. My goal was to gain some experience by rooting and replacing the os image on my Atrix 4G. I use it for my alarm clock which uses an application that won't run on newer version of android than v2.x.x. I successfully rooted and installed super use. I then installed Titanium Backup and did a full backup to sdcard. I installed Rom Manager, chose ClockworkMod Recovery and then the correct image, and told it to flash the recovery partition. Rebooted. Got an error with the android logo and a circle with a triangle. Went back to all the how to's and attempted to install unlockable_bootloader. It now comes up to rsd, seems to fail, then goes into fastboot. Fastboot devices sees it and I can reboot from fastboot but it goes back to the same place. HELP.
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Try this guide. http://forum.xda-developers.com/showthread.php?t=2262869
ravilov said:
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Click to expand...
Click to collapse
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
flash recovery failed
andresrivas said:
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I previously found a thread that described that process and tried it. Fastboot reported it failed flashing recovery.
That usually happens if the BL is not unlocked (properly).
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
reflash the pudding sbf to unlock the bl, then go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
flash boot failed
palmbeach05 said:
reflash the pudding sbf to unlock the bl, th
en go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
Click to expand...
Click to collapse
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Phatdaddy said:
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Click to expand...
Click to collapse
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
palmbeach05 said:
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
Click to expand...
Click to collapse
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Phatdaddy said:
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Click to expand...
Click to collapse
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
palmbeach05 said:
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
Click to expand...
Click to collapse
ls of /system/etc/install-recovery.sh says the file does not exist.
When I bricked my atrix i used the xatrix tool to unbrick it. works really well and once unbricked was fully unlocked so was easy to flash new roms
xatrix (dot) webs (dot) com
once on there website click to download tab to get the downloads
This tool will remove everything from phone root, unlock and install cwm. What you do after that is upto you. sometimes its easier to start over then figure out what went wrong when installing a mod.
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
And thats the part that confuses me. It says 141, but the recovery issue is acting like its a 145. I'm stumped, but i do believe there is an install-recovery.sh script or something thats preventing this thing from sticking after flashing. I'm really baffled by this b/c i ran 141 for the longest time, i did all my rooting, unlocking, and recovery flashing on 141, and got no issues. I could advise that you download and flash the ICS leak (the true leak, not the ROMs we have available) via fastboot and see if that changes the situation, but i don't want to advise you to do something and then a bigger mess appears.
Sent from my MB886 using xda app-developers app
Phatdaddy said:
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
Click to expand...
Click to collapse
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
overboard1978 said:
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
Click to expand...
Click to collapse
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
palmbeach05 said:
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
Click to expand...
Click to collapse
That should do it. If for some reason it doesnt the xatrix tool will wipe everything off the phone and start it over with 141 unlocked bootloader, with cwm. Only automated tool i found that will unbrick phone with rsd lite. Make sure phone is fully charged before starting xatrix tool as it wipes battery fast and if it dies you will need to start over.
Erase cashe was successful, erase data failed. Found reference to additional file to delete but it did not exist either. If I conttinue, I will repost. Thanks for everyone's effort trying to get this working.
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Fastboot flash the images. Then reroot.
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
TenderloinShadow said:
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56921581&postcount=33
That post left out flashing recovery. The download should have 6 files. I flashed recovery at the end (but I don't think it matters how you flash the files, I could be wrong though).
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
di11igaf said:
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
Click to expand...
Click to collapse
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
ericplatham said:
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
Click to expand...
Click to collapse
You're right, now that I think about it, I believe I had to do that as well last time I flashed a factory image.
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
GatorsUF said:
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
Click to expand...
Click to collapse
maybe I'll write up a guide, but download the factory image, extract it. In there is a zip file, extract it too. Then Google 15 second adb install xda. That'll set up fastboot on your pc. Then boot into the bootloader and in a command window opened in the folder where the bootloader image is located run the commands:
fastboot flash bootloader bootloader.img. Note, use the full name of the bootloader.img
fastboot reboot-bootloader
fastboot -w
Open the folder where the boot, system, cache, system, and vendor images are located. Open a command window in that folder and run the commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then you're done
Click to expand...
Click to collapse
He will still have to reroot and flash custom recovery... but you got 95% of the process :laugh:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
rank78 said:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
Click to expand...
Click to collapse
Since its a small update you could probably get by just flashing the system and boot images. But I haven't tried it
Sent from my Nexus 5 using XDA Free mobile app
I'd flash everything as described to be safe, I just prefer simply flashing a zip and moving on.
Will updating thru adb wipe my device?
GatorsUF said:
Will updating thru adb wipe my device?
Click to expand...
Click to collapse
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I have actually flashed a few times thru fastboot in the past so I'm not totally lost on the idea. I've always used tibu in the past, will Google restore my data too?
TenderloinShadow said:
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Click to expand...
Click to collapse
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
fhem said:
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
Click to expand...
Click to collapse
Why erase recovery twice?
Just dont flash stock recovery
fhem said:
STEP #1
fastboot flash bootloader {bootloader.img}
Click to expand...
Click to collapse
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Double_U said:
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Click to expand...
Click to collapse
Hi, Double_U...
Are you sure you've typed the EXACT command..?
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
Reboot the bootloader, enter fastboot, and try again.
Rgrds,
Ged.
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
tdct12 said:
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
Click to expand...
Click to collapse
If your able to access the bootloader menu or the fastboot menu, you could flash the stock and would fix the brick,soft brick or boot-loop.
Head to Google developer nexus image. Download the factory image of your devices on your devices. Extract all the files and copy paste the fastboot and adb files. Head to your devices and open the fastboot menu.
Type the following commends to restore your devices if the flashall did not work.
Fastboot oem unlock
Fastboot flash bootloader bootloader....
Fastboot reboot-bootloader
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
Fastboot erase system
Fastboot flash system system.img (this could take up to 15 minutes, don't do anything to stop the process you can make your devices and a worst state)
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot erase vendor
Fastboot flash vendor vendor.img
Fastboot reboot
This should fix your devices. I did not and it save each time I broke my device or anything similar.
If you want after all that. You can enter the following commends to relock your devices but don't make the same mistake you did before. If you want to avoid that same mistake just don't enter the commends.
What the guy above me said, also pro tip, some times not all the files will extract just keep extracting till all the image files are there.
Hi guys!
I was relocking my bootloader on my Huawei P20 Lite and now it isn't booting at all. It goes to the eRecovery screen and that's it.
I tried reverting what I've done, but now the FRP lock is preventing me from executing any fastboot commands from my PC.
Does anyone know what to do?
Why you decided to do that? To avoid initial screen, your device has been unlocked and can't be trusted...
Did you do any kind of modification in the partitions before relock bootloader?
I had done something similar and could not do anything anymore by the frp lock,
I have downloaded the ROM from this link, (make sure this rom is for ure model of phone)
https://forum.xda-developers.com/hu...om-official-emui-8-0-huawei-p20-lite-t3773999
then I used this
https://www.dc-unlocker.com/file-list/DC-unlocker_softwares/DC_Phoenix/DC_Phoenix_v52.rar.html
and I paid 15€ ( to use the dc app ) to flash update.app even though there is frplock they can get around this.
it costs money but that's how my p20 works
I have not found a free way yet
why did you paid for that?
I did it myself, factory reset then I simply flashed the stock system. IMG and did a fastboot relock...
Who did you paid?
mchtt said:
why did you paid for that?
I did it myself, factory reset then I simply flashed the stock system. IMG and did a fastboot relock...
Who did you paid?
Click to expand...
Click to collapse
@mchtt can you post the instruction on how to flash from the China version to the international version.
I downloaded the system.img file you uploaded but have no idea how to use it - create update.app and drag the system.img file in there?
Thanks ahead of time.
You should not continue of you don't know how to use files, flashing phone is not as easy we think.
First, you be to provide informations, what's your phone ID, your rom version, and what did you do exactly to your phone ?
My system.img was extracted from the stock update.app version P20 Lite ANE-LX1-C432.
U can simply flash it:
Fastboot flash system system.img
But before or after is mandatory to do a factory reset or full wipe.
It will reset your phone to stock and you will be able to re-lock the bootloader with fastboot if it's not done already.
mchtt said:
why did you paid for that?
I did it myself, factory reset then I simply flashed the stock system. IMG and did a fastboot relock...
Who did you paid?
Click to expand...
Click to collapse
My phone was in a bootloop and there was no recovery and there was no way to factory reset..
To flash img file u need frp unlock and mine was locked
Update on the situation: I sent the device to the atores warranty and they swapped it straight away. Got lucky this time
Disregard
I used a payload extraction tool to open up the OTA file and then flashed each partition via fastboot manually (saw it in a oneplus thread) phone is currently at the boot screen which is much further than it was any time before this, going to give it a little more time before trying anything further as I did a factory reset before upgrading so it could just be first booting.
thoughtlesskyle said:
I messed up while trying to install the android 10 update, I have backups of my stock boot images but not my system paritionwas on MP2) my system partition is now wiped
I can only get to the bootloader but accessing anything else just results in a bootloop so I can't install the OTA updates, I do however still have a working fastboot.
does anyone have a backup of their paritions that I can flash via fastboot?
I also can't seem to boot twrp from fastboot anymore either
any help is appreciated
Click to expand...
Click to collapse
First you didn't state your device model or version.
Android 10 update will lock your bootloader, and till now the unlocking code is no where to be found, and so it can't be rooted unless it is unlocked.
So what you could do is swapping your current partition slot to the one with Android 9 if you want to have root, flash your phone, or booting TWRP.
Code:
fastboot set_active other
Then reboot your phone to bootloader, and you will see that it is unlocked, and do 'Factory Reset' if needed.
Warning do not try to flash anything while the bootloader is locked.
If you have BS 2 Pro global and want to flash MP2 back, check my thread.
Goodluck
KM7 said:
First you didn't state your device model or version.
Android 10 update will lock your bootloader, and till now the unlocking code is no where to be found, and so it can't be rooted unless it is unlocked.
So what you could do is swapping your current partition slot to the one with Android 9 if you want to have root, flash your phone, or booting TWRP.
Code:
fastboot set_active other
Then reboot your phone to bootloader, and you will see that it is unlocked, and do 'Factory Reset' if needed.
Warning do not try to flash anything while the bootloader is locked.
If you have BS 2 Pro global and want to flash MP2 back, check my thread.
Goodluck
Click to expand...
Click to collapse
Okay further update, I am using a SKW-H01, I flashed all the partitions from the 10 update manually and hung at a bootloop rebooted to recovery after waiting a little while and factory reset now I am fully booted. I didn't read enough or else I would have been smarter about trying an android 10 build to recover the phone because of it locking the bootloader. Either way we are all good to go. Thanks for your help. I was just stupid and went into it unprepared. I have messed around with a lot of devices over the years but never one that had a payload.bin instead of a factory image.
WE'RE ALL GOOD NOW THOUGH!
thoughtlesskyle said:
Okay further update, I am using a SKW-H01, I flashed all the partitions from the 10 update manually and hung at a bootloop rebooted to recovery after waiting a little while and factory reset now I am fully booted. I didn't read enough or else I would have been smarter about trying an android 10 build to recover the phone because of it locking the bootloader. Either way we are all good to go. Thanks for your help. I was just stupid and went into it unprepared. I have messed around with a lot of devices over the years but never one that had a payload.bin instead of a factory image.
WE'RE ALL GOOD NOW THOUGH!
Click to expand...
Click to collapse
Good to know that you managed to boot it. Hope things are working well for you.
thoughtlesskyle said:
Okay further update, I am using a SKW-H01, I flashed all the partitions from the 10 update manually and hung at a bootloop rebooted to recovery after waiting a little while and factory reset now I am fully booted. I didn't read enough or else I would have been smarter about trying an android 10 build to recover the phone because of it locking the bootloader. Either way we are all good to go. Thanks for your help. I was just stupid and went into it unprepared. I have messed around with a lot of devices over the years but never one that had a payload.bin instead of a factory image.
WE'RE ALL GOOD NOW THOUGH!
Click to expand...
Click to collapse
22 sections.
Yes, all the partitions had to be flashed to run it.
Code:
fastboot flash xbl_config_a rom/xbl_config.img
fastboot flash xbl_a rom/xbl.img
fastboot flash vendor_a rom/vendor.img
fastboot flash vbmeta_a rom/vbmeta.img
fastboot flash uefisecapp_a rom/uefisecapp.img
fastboot flash tz_a rom/tz.img
fastboot flash system_a rom/system.img
fastboot flash qupfw_a rom/qupfw.img
fastboot flash modem_a rom/modem.img
fastboot flash keymaster_a rom/keymaster.img
fastboot flash imagefv_a rom/imagefv.img
fastboot flash hyp_a rom/hyp.img
fastboot flash dtbo_a rom/dtbo.img
fastboot flash dsp_a rom/dsp.img
fastboot flash devcfg_a rom/devcfg.img
fastboot flash custom_a rom/custom.img
fastboot flash cmnlib64_a rom/cmnlib64.img
fastboot flash cmnlib_a rom/cmnlib.img
fastboot flash boot_a rom/boot.img
fastboot flash bluetooth_a rom/bluetooth.img
fastboot flash aop_a rom/aop.img
fastboot flash abl_a rom/abl.img
All writing* [OK].
But having root on board this operation passes with the format userdata error.
In the flash writing* [FAILED].
Only by deleting hidden folders and files via the /data/directory... in internal storage, writing* [OK].