Request - HTC Desire 10 Questions & Answers

I flashed supersu zip several times, and i have lost the original boot.img and system.img. Can someone extract those files?
HTC Desire 10 Pro a56dj_pro_dugl, Vietnamese market
Software number 1.10.400.20
------------------------
I cannot perform a factory reset. Are the files have something to do with resetting?

Smithienious said:
I flashed supersu zip several times, and i have lost the original boot.img and system.img. Can someone extract those files?
HTC Desire 10 Pro a56dj_pro_dugl, Vietnamese market
Software number 1.10.400.20
------------------------
I cannot perform a factory reset. Are the files have something to do with resetting?
Click to expand...
Click to collapse
Flash UnSu.zip
It will restore stock boot img.

Hasibur Rahman said:
Flash UnSu.zip
It will restore stock boot img.
Click to expand...
Click to collapse
I flashed the supersu.zip several times, and i have lost the backup boot img.

Related

Unable to install OTA LRX21O

Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash the OTA LRX21O (I'm on LNX07M) in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
RandoTheKing said:
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash LRX21O in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
Click to expand...
Click to collapse
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
akellar said:
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
Click to expand...
Click to collapse
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
RandoTheKing said:
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
Click to expand...
Click to collapse
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
well what will you do for future updates? Full wipe?
RandoTheKing said:
well what will you do for future updates? Full wipe?
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
jj14 said:
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Click to expand...
Click to collapse
Any instructions on how to do that? I'm assuming I can still get the update that way
RandoTheKing said:
Any instructions on how to do that? I'm assuming I can still get the update that way
Click to expand...
Click to collapse
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Edit - flash the cache.img instead of just erasing cache
I had trouble flashing the factory image initially. I kept getting an error so I used this method and it worked perfectly. Hope it helps. http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
So i am root and have done a bit of work on my Nexus 6 (changing system sounds, setting it up and a few other things) If i want to install LRX21O, what is the step by step to do that and after i install it if i do a Nandroid Backup, can i restore the backup on LRX21O? I am currently on LNX07M.
I am curious as well. Also do you happen to have a link to the file to just update.?
EDIT... Found it. Will flash when home
Sent from my Nexus 6 using XDA Free mobile app
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Click to expand...
Click to collapse
Should that be `fastboot format cache`?
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
Actually, you should just flash the cache.img
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
You don't reboot into recovery if you are using fas boot. You boot into boot loader at least that's how I've done it on every Nexus that I've had.
Edit - flash the cache.img instead of just erasing cache
Click to expand...
Click to collapse
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
You can use both commands to first format, then flash the new one it doesn't really matter. I've used both methods
jj14 said:
Actually, you should just flash the cache.img
Click to expand...
Click to collapse

Rooted Nexus 6 fails to update 5.1.1

Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
I'm not sure you can be rooted on lollipop to take updates. That could be the problem. Try unrooting.
flash your current versions stock system.img. Lollipop updates don't patch files like the older updates, it does block level patching of the /system so you can't have any changes or the update will fail. On previous versions you could add files to /system and an update would patch the stock /system files and not care you had added other files. Now they patch at the block level so you can't add/delete files, you have to have a 100% untouched /system to take an update.
Download the factory image of what your phone is currently running. Fastboot flash the system.img and then take the OTA. You can then root after updated.
You could also just download the LMY47Z factory image and flash the bootloader, boot.img and system.img and be good to go (root again after). As long as you don't flash the userdata.img or wipe data you retain all your settings/apps/files.
vampire_8_7 said:
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
Click to expand...
Click to collapse
You don't.
YOU obtain the full factory system image from https://developers.google.com/android/nexus/images
doitright said:
You don't.
YOU obtain the full factory system image from https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
tcrews said:
flash your current versions stock system.img. Lollipop updates don't patch files like the older updates, it does block level patching of the /system so you can't have any changes or the update will fail. On previous versions you could add files to /system and an update would patch the stock /system files and not care you had added other files. Now they patch at the block level so you can't add/delete files, you have to have a 100% untouched /system to take an update.
Download the factory image of what your phone is currently running. Fastboot flash the system.img and then take the OTA. You can then root after updated.
You could also just download the LMY47Z factory image and flash the bootloader, boot.img and system.img and be good to go (root again after). As long as you don't flash the userdata.img or wipe data you retain all your settings/apps/files.
Click to expand...
Click to collapse
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
vampire_8_7 said:
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
Click to expand...
Click to collapse
Hey doitright
So I can download the 5.1.1 (For Sprint, USC ONLY) (LMY47Z) even tho its saying US Only, and this was the one I received on the system update!!!
vampire_8_7 said:
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
Click to expand...
Click to collapse
To "restore" your system to stock, you just need to flash the system.img and recovery.img to take the OTA. To "update" your system to the next version with factory images you would flash bootloader, restart the bootloader, flash the radio, restart the bootloader then flash boot.img and system.img and then reboot the phone. Re-root after.
All Done
Thanks to everyone, all done now, and special thanks to "tcrews" all sorted out now mate, I used fastboot to flash 5.1 (recovery, bootloader, boot and system) then did the same thing for the 5.1.1. I didn't lose any data or apps all working perfectly fine. I had to "Root" the device after, then flashed the "Xposed Firmware". :good: :good:
Yes, thanks as well! I had this issue when the OTA showed up on my Nexus 6 yesterday. Did what vampire_8_7 indicated above, and everything is working with no loss of data or apps. Thanks everyone!
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
mar1nasr said:
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
Click to expand...
Click to collapse
You cannot flash the OTA. You can only flash stock. I also have no idea if you're doing something wrong. Probably though, that is usually the case.
vampire_8_7 said:
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
Click to expand...
Click to collapse
- Fastboot erase system
- Fastboot flash system system.img
- Fastboot flash boot boot.img if you have a custom kernel
- Fastboot flash recovery recovery.img if you have a custom recovery
- Fastboot erase cache and then fastboot flash cache cache.img.
Reboot and sideload the OTA and that should do it because you still have have modified system files on your phone.
mar1nasr said:
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
Click to expand...
Click to collapse
Hey mate
The idea is to go complete stock before you flash any OTA, and this can be achieved by just flashing the "System.img" and the "bootloader.img" file to you device.
DON'T FORGET TO TAKE A FULL BACKUP ​Note: This warning above is more precaution thing, and this method never wiped any data but its good to have the backup always.
You need to download the official stock image for your device, if you have that's fine keep reading through.
Factory Images
You have to extract the image and get the "system.img" and "bootloader.img"
Copy and Paste the "System.img" and "bootloader.img" files in the fastboot folder.
Open the cmd as admin navigate to the directory where the fastboot resides, then start typing these commands.
fastboot flash bootloader bootloader-XXXX.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
fastboot flash system system.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Now you have to copy (Boot.img , bootloader.img, system.img and the radio.img) from the OTA image you have and paste it in the fastboot folder, then you will run the previous 2 commands in addition to these 2 commands below.
fastboot flash radio radio-XXX-XXX.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
After performing this you should have 5.1.1 on your device without wiping any of your personal data or apps.
vampire_8_7 said:
...
Click to expand...
Click to collapse
Thanks a million for the step by step. i think my stock 5.1 is the issue. i'll download the factory image and try again now.
cheers,
EDIT: just finished, and it seems my old 5.1 image was crap. i downloaded a new factory image and did what you mentioned above. now running 5.1.1 and all my old data is there. thanks again, appreciate your time.
mar1nasr said:
Thanks a million for the step by step. i think my stock 5.1 is the issue. i'll download the factory image and try again now.
cheers,
EDIT: just finished, and it seems my old 5.1 image was crap. i downloaded a new factory image and did what you mentioned above. now running 5.1.1 and all my old data is there. thanks again, appreciate your time.
Click to expand...
Click to collapse
No Problems bro. Happy to hear that it worked. XDA is always the place where you can get help
another update for those using TWRP.
TWRP recovery 2.8.7.0 cannot decrypt data for recovery mode, and the 5.1.1 udpate comes encrypted. only way to decrypt is to factory wipe if your device is encrypted and the patternlock/pin doesnt work.
TWRP released 2.8.7.1 yesterday that fixes this issue. this saved me from factory wipe and starting from scratch. also no data needed to be wiped.
^^ just in case anyone is running into the same issue.
cheers,
mar1nasr said:
another update for those using TWRP.
TWRP recovery 2.8.7.0 cannot decrypt data for recovery mode, and the 5.1.1 udpate comes encrypted. only way to decrypt is to factory wipe if your device is encrypted and the patternlock/pin doesnt work.
TWRP released 2.8.7.1 yesterday that fixes this issue. this saved me from factory wipe and starting from scratch. also no data needed to be wiped.
^^ just in case anyone is running into the same issue.
cheers,
Click to expand...
Click to collapse
All official updates encrypt.
tcrews said:
To "restore" your system to stock, you just need to flash the system.img and recovery.img to take the OTA. .
Click to expand...
Click to collapse
Hi,
Can I ask for more details how to flash the system.img and recovery.img ? From where to download it and how to flash?
I have rooted Nexus 6 5.1 Verizon
Thanks
ikirilenko said:
Hi,
Can I ask for more details how to flash the system.img and recovery.img ? From where to download it and how to flash?
I have rooted Nexus 6 5.1 Verizon
Thanks
Click to expand...
Click to collapse
I always place these img`s in the /android/sdk/platform-tools/ folder, or extract them and right-click/shift copy to path. Then with cmd in fastboot erase system then flash system system.img and fastboot flash recovery recovery.img. Dowloadlink below in my signature Phantasmagoria and extract the downloaded file until you see the img`s.
gee2012 said:
Then with cmd in fastboot erase system then flash system system.img
Click to expand...
Click to collapse
Out of curiosity, why do you erase system first?

[FIX]Marshmallow BOOTLOOP

OK people, so i bring another (hopefuly helpful to someone) exprecience with BOOTLOOP.
Problem: I had stock B200 firmware (5.0.2). I wanted to try beta update of marshmallow, so i decided to try it. It was told me i can update directly from B200 one, so i just copied update.zip to DLOAD folder, went to settings and run local update. The phone restarted, booted into recovery and started flashing. BUT, i forgot that i had custom TWRP recovery and not stock one, anyway, TWRP started flashing the zip, error after error, but some files still copied and bricked the phone. I couldnt start any recovery, just fastboot and some mode that should download online file and reflash system, but it would be very easy so it has error too.
Here is what i did:
1. Download the update zip of marshmallow you were trying to flash and unpack UPDATE.APP
2. Extrac: RECOVERY.img and BOOT.img
3. set phone to fastboot mode and flash extracted BOOT.img, then RECOVERY.img
4. after that, you need somehow copy whole B200 firmware into sdcard / dload folder (i took micro sd and inserted into another phone, then copied it)
5. now you can boot into force flashing mode (power + volume up + volume down buttons) and it automaticaly reflash whole system.
6. after reboot you can use your P8
OK, i got it work!
00471 said:
OK, i got it work!
Click to expand...
Click to collapse
Great to hear that, can you please answer how you did it,as this might help someone having the same problem
Salman Al-Badgail said:
Great to hear that, can you please answer how you did it,as this might help someone having the same problem
Click to expand...
Click to collapse
of course, i wanted to do it but didnt have time, ill update OP with solution
00471 said:
of course, i wanted to do it but didnt have time, ill update OP with solution
Click to expand...
Click to collapse
Thanks :good:
00471 said:
OK people, so i bring another (hopefuly helpful to someone) exprecience with BOOTLOOP.
Problem: I had stock B200 firmware (5.0.2). I wanted to try beta update of marshmallow, so i decided to try it. It was told me i can update directly from B200 one, so i just copied update.zip to DLOAD folder, went to settings and run local update. The phone restarted, booted into recovery and started flashing. BUT, i forgot that i had custom TWRP recovery and not stock one, anyway, TWRP started flashing the zip, error after error, but some files still copied and bricked the phone. I couldnt start any recovery, just fastboot and some mode that should download online file and reflash system, but it would be very easy so it has error too.
Here is what i did:
1. Download the update zip of marshmallow you were trying to flash and unpack UPDATE.APP
2. Extrac: RECOVERY.img and BOOT.img
3. set phone to fastboot mode and flash extracted BOOT.img, then RECOVERY.img
4. after that, you need somehow copy whole B200 firmware into sdcard / dload folder (i took micro sd and inserted into another phone, then copied it)
5. now you can boot into force flashing mode (power + volume up + volume down buttons) and it automaticaly reflash whole system.
6. after reboot you can use your P8
Click to expand...
Click to collapse
Tried exactly as you say, STILL Software install failed.
Can you send me link which system you are trying to flash? Maybe you have just bad package
Odoslané z HUAWEI GRA-L09 pomocou Tapatalku
Can't get it to work
00471 said:
OK people, so i bring another (hopefuly helpful to someone) exprecience with BOOTLOOP.
Problem: I had stock B200 firmware (5.0.2). I wanted to try beta update of marshmallow, so i decided to try it. It was told me i can update directly from B200 one, so i just copied update.zip to DLOAD folder, went to settings and run local update. The phone restarted, booted into recovery and started flashing. BUT, i forgot that i had custom TWRP recovery and not stock one, anyway, TWRP started flashing the zip, error after error, but some files still copied and bricked the phone. I couldnt start any recovery, just fastboot and some mode that should download online file and reflash system, but it would be very easy so it has error too.
Here is what i did:
1. Download the update zip of marshmallow you were trying to flash and unpack UPDATE.APP
2. Extrac: RECOVERY.img and BOOT.img
3. set phone to fastboot mode and flash extracted BOOT.img, then RECOVERY.img
4. after that, you need somehow copy whole B200 firmware into sdcard / dload folder (i took micro sd and inserted into another phone, then copied it)
5. now you can boot into force flashing mode (power + volume up + volume down buttons) and it automaticaly reflash whole system.
6. after reboot you can use your P8
Click to expand...
Click to collapse
I did exactly the same mistake as you and the same steps to fix it. I flashed those 2, places the update.app + the other files to dload and then 3 button update and I got to the huawei music and animation. Then it restarted.
mega:///#!IEhCRaRR!GT6Ds9EywDoW5Dd8ZdKVesyQUItbiSwCPaapFhAenEY
is the file I use.
Is there any advice you could give?
T1mb3 said:
I did exactly the same mistake as you and the same steps to fix it. I flashed those 2, places the update.app + the other files to dload and then 3 button update and I got to the huawei music and animation. Then it restarted.
mega:///#!IEhCRaRR!GT6Ds9EywDoW5Dd8ZdKVesyQUItbiSwCPaapFhAenEY
is the file I use.
Is there any advice you could give?
Click to expand...
Click to collapse
Actually i do, i bricked my phone one after that later, and this helped: http://www.huawei-info.de/p8-mm-rollback flash B300 rollback zip with 3 buttons combination, then flash B200 full zip. I hope it will help :good:
00471 said:
Actually i do, i bricked my phone one after that later, and this helped: xx flash B300 rollback zip with 3 buttons combination, then flash B200 full zip. I hope it will help :good:
Click to expand...
Click to collapse
I'll give it a try.
Thank you!
It says Software install failed when trying to flash rollback.. I'll try to install the b200 full zip now
T1mb3 said:
I'll give it a try.
Thank you!
It says Software install failed when trying to flash rollback.. I'll try to install the b200 full zip now
Click to expand...
Click to collapse
okay, do this:
in fastboot flash those files from Marshmallow B313: recovery.img, boot.img and cust.img
then try to flash rollback, the CUST.img is very important to flash
00471 said:
okay, do this:
in fastboot flash those files from Marshmallow B313: recovery.img, boot.img and cust.img
then try to flash rollback, the CUST.img is very important to flash
Click to expand...
Click to collapse
There is no cust in the update.app
T1mb3 said:
There is no cust in the update.app
Click to expand...
Click to collapse
Okay have chaos in this all files, maybe it was B200 cust, or B170 cust, try one of them, but boot.img and recovery.img must be from Beta
00471 said:
Okay have chaos in this all files, maybe it was B200 cust, or B170 cust, try one of them, but boot.img and recovery.img must be from Beta
Click to expand...
Click to collapse
I think I'll get it working as soon as I get a large enough sdcard..
Thanks for your help!
I'll comment here if I face more problems
T1mb3 said:
I think I'll get it working as soon as I get a large enough sdcard..
Thanks for your help!
I'll comment here if I face more problems
Click to expand...
Click to collapse
No problem, let me know if you solve it
00471 said:
No problem, let me know if you solve it
Click to expand...
Click to collapse
Awesome, I got it working.
I used b170 cust, if someone has trouble.
Thank you so much!
T1mb3 said:
Awesome, I got it working.
I used b170 cust, if someone has trouble.
Thank you so much!
Click to expand...
Click to collapse
Glad it worked!
Offtopic: if i root after reverting to 5.0.1 using twrp should i then flash stock recovery from b200 or b313 or which one? I mean when the non beta marshmallow update is available
Qqman55 said:
Offtopic: if i root after reverting to 5.0.1 using twrp should i then flash stock recovery from b200 or b313 or which one? I mean when the non beta marshmallow update is available
Click to expand...
Click to collapse
If you are on 5.0.1 with root and twrp then you are good, or do you want try BETA? if yes then you need stock recovery flash before flashing beta
00471 said:
OK people, so i bring another (hopefuly helpful to someone) exprecience with BOOTLOOP.
Problem: I had stock B200 firmware (5.0.2). I wanted to try beta update of marshmallow, so i decided to try it. It was told me i can update directly from B200 one, so i just copied update.zip to DLOAD folder, went to settings and run local update. The phone restarted, booted into recovery and started flashing. BUT, i forgot that i had custom TWRP recovery and not stock one, anyway, TWRP started flashing the zip, error after error, but some files still copied and bricked the phone. I couldnt start any recovery, just fastboot and some mode that should download online file and reflash system, but it would be very easy so it has error too.
Here is what i did:
1. Download the update zip of marshmallow you were trying to flash and unpack UPDATE.APP
2. Extrac: RECOVERY.img and BOOT.img
3. set phone to fastboot mode and flash extracted BOOT.img, then RECOVERY.img
4. after that, you need somehow copy whole B200 firmware into sdcard / dload folder (i took micro sd and inserted into another phone, then copied it)
5. now you can boot into force flashing mode (power + volume up + volume down buttons) and it automaticaly reflash whole system.
6. after reboot you can use your P8
Click to expand...
Click to collapse
can you upload stock recovery of b313?

Restore to stock

I had restored stock system.img, boot.img and recovery.img after wiping the phone with TWRP recovery. But still my phone is not working properly and some traces are still left in my phone. What things do it don't wipes please tell me and share stock version of those things.
I used advanced wipe and selected all options in TWRP.
Also pls tell me how to flash, if it can't be flashed with flash tool.
For information, I didn't made any changes to kernal, so it doesn't need to be restored.
Which file are you using to flash the phone to stock ?
Truely Simple said:
I had restored stock system.img, boot.img and recovery.img after wiping the phone with TWRP recovery. But still my phone is not working properly and some traces are still left in my phone. What things do it don't wipes please tell me and share stock version of those things.
I used advanced wipe and selected all options in TWRP.
Also pls tell me how to flash, if it can't be flashed with flash tool.
For information, I didn't made any changes to kernal, so it doesn't need to be restored.
Click to expand...
Click to collapse
Did you check the box of dl checksum on the flash tool ?
If not then go to options menu on the top left corner ,click on download and check both the box present there .
If you already did that . Tell me the process you are using to flash the file
iliyas61 said:
Tell me the process you are using to flash the file
Click to expand...
Click to collapse
Yes I already did that.
Firstly, I selected agent, then scatter file, and finally the boot, recovery and system imgs.
Obviously, then I clicked on download with 'download only' selected and connected the phone.
Go for format download
Truely Simple said:
Yes I already did that.
Firstly, I selected agent, then scatter file, and finally the boot, recovery and system imgs.
Obviously, then I clicked on download with 'download only' selected and connected the phone.
Click to expand...
Click to collapse
Try doing format and download instead of download only ... maybe this will work ...
Else your process is all right ...
Or try downloading the flash file once again ...
iliyas61 said:
Try doing format and download instead of download only ... maybe this will work ...
Else your process is all right ...
Or try downloading the flash file once again ...
Click to expand...
Click to collapse
I don't have other images, for bootloader, logo etc.
Truely Simple said:
I had restored stock system.img, boot.img and recovery.img after wiping the phone with TWRP recovery. But still my phone is not working properly and some traces are still left in my phone. What things do it don't wipes please tell me and share stock version of those things.
I used advanced wipe and selected all options in TWRP.
Also pls tell me how to flash, if it can't be flashed with flash tool.
For information, I didn't made any changes to kernal, so it doesn't need to be restored.
Click to expand...
Click to collapse
Flash stock with sp flash tool you need to flash the whole firmware

P20 Pro - Bricked - tried everything...(!)

I was rooted through Magisk on firmware .255, but I saw an approved update for firmware .280 which I wanted, and I also wanted to go back to stock for a while. I downloaded the update.zip, extracted the .img needed and flashed accordingly; cust, erecovery, system, cache, kernel, recovery, userdata, etc, all I could.
I now can't get it to boot no matter what I try. I always end up on the screen "Your device has been unlocked and can't be trusted" and then stuck on "Your device is booting now". I can get into eRecovery and/or flash TWRP.
I've tried the below;
Flashing dload folder on a USB OTG
Flashing update zip in TWRP
Flashing update zip with Huruupdater in TWRP
Flashing through fastboot update (update.app extracted)
Flashing through fastboot update_full_base (update.app extracted)
Going through HiSuite - it sees the recovery but then says "No recovery packages found for your phone"
Wipe data etc.
I did forget to remove fingerprint security before I did this, my bootloader is unlocked and FRP.
Genuinely never bricked a phone before! Any help would be appreciated.
I think it's because I need to flash boot.img but I can't see that when I extract from update.app
Does anyone have one please?
Don't make me buy a pixel tomorrow!
belloni said:
I think it's because I need to flash boot.img but I can't see that when I extract from update.app
Does anyone have one please?
Click to expand...
Click to collapse
it because there's no boot.img for EMUI 9, it's recovery_ramdis.img and kernel.img did you flash that ?
try to pull recovery_ramdis.img from the Update.app and patch it using latest magisk 19.4 and flash it then try to boot again
otonieru said:
it because there's no boot.img for EMUI 9, it's recovery_ramdis.img and kernel.img did you flash that ?
try to pull recovery_ramdis.img from the Update.app and patch it using latest magisk 19.4 and flash it then try to boot again
Click to expand...
Click to collapse
Yeah I've flashed those two.
How can I patch it if I can only get into TWRP?
belloni said:
Yeah I've flashed those two.
How can I patch it if I can only get into TWRP?
Click to expand...
Click to collapse
EDIT: I've found the old magisk_patched.img but when I flash it says "FAILED (remote: partition length get error)
belloni said:
Yeah I've flashed those two.
How can I patch it if I can only get into TWRP?
Click to expand...
Click to collapse
from other phone with magisk installed.
other thing you might want to try is enter stock recovery (not TWRP) and wipe /data and cache from there
just a heads up though,
your way of updating the OS is totally dangerous, you could.messed up partition,
you should use EMUI Flasher instead
I have a guide to fix this in the guides section. Follow it and you'll be fine.
Find somebody that had a p20 pro rooted to send you a backup of their software (with the data partition wiped).
https://forum.xda-developers.com/showpost.php?p=79107368&postcount=82

Categories

Resources