Hello everyone,
I have the P20 Pro 9.0.0.283(C792E5R1P9) - Canadian version and during my attempt to install TWRP and Magisk I endup flashing the twrp.img on my boot partition and now I can't upgrade to 9.1.0.317(C792E8R1P9) or even hard reset, because when it boots the original boot partition is damage and not even via HiSuite I can't upgrade to the new one.
I need to know if someone has this build 9.0.0.283 (C792E5R1P9) that I can extract the boot.img and re-flash on my phone.
And the phone works normally, just the boot that is compromised.
Thank you
You will half to boot it into fastboot and fix it that way
what do you mean i have same issue as him ? do i need the stock boot.img to flash or can it be solved with another way ?
Bcoates84 said:
You will half to boot it into fastboot and fix it that way
Click to expand...
Click to collapse
what do you mean i have same issue as him ? do i need the stock boot.img to flash or can it be solved with another way ?
Bcoates84 said:
You will half to boot it into fastboot and fix it that way
Click to expand...
Click to collapse
Related
Hi Guys
After a hard brick I use the tool Msm8974DownloadTool;
Oneplus one reboot in color OS
This morning I have to change I installed the last CYANOGEN OS 13.1.2-ZNH2KAS3PO Bacon
The problem is that I lost my root access and I can not install a recovery custum
I install android sdk slim
fastboot works
bootloader unlock
BUT don' t install twrp-3.0.2-0-bacon rename to (recovery.img )error not charger
Do you have any ideas.
Thinks for help
Jjul said:
Hi Guys
After a hard brick I use the tool Msm8974DownloadTool;
Oneplus one reboot in color OS
This morning I have to change I installed the last CYANOGEN OS 13.1.2-ZNH2KAS3PO Bacon
The problem is that I lost my root access and I can not install a recovery custum
I install android sdk slim
fastboot works
bootloader unlock
BUT don' t install twrp-3.0.2-0-bacon rename to (recovery.img )error not charger
Do you have any ideas.
Thinks for help
Click to expand...
Click to collapse
After you fastboot flash recovery don't let the phone boot into system it will rewrite to stock recovery. Instead boot immediately into recovery by holding volume down and power.
Thank you for your reply
but but precisely
fastboot flash recovery img. don't work do not want to load the recovery
it's ok now !!
good!
thanks
Jjul said:
Thank you for your reply
but but precisely
fastboot flash recovery img. don't work do not want to load the recovery
Click to expand...
Click to collapse
What exactly happens after you fastboot flash recovery?
You didn't accidentally name the file recovery.IMG.IMG?
You could also try a toolkit http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
Jjul said:
it's ok now !!
good!
thanks
Click to expand...
Click to collapse
I'm wondering...
If you accidentally overwrote your /boot (happened to me once) by fastboot flash boot XXX.img
be sure to flash again by fastboot flash boot boot.img before you ever need reboot your phone.
Code:
Warning! any damage done to your device is not my fault, use at your own risk!
This zip should be used mainly if you wiped system for some reason and didn't back up, its TA-1060 May patch system image + kernel + vendor files
Unlocked bootloader required!
TWRP
1. Boot into TWRP
2. Format /data partition in TWRP
3. Use 'adb push ta_1060_oreo_may_18.zip /sdcard/' in windows/linux/mac
4. Go to sdcard in TWRP and flash ta_1060_oreo_may_18.zip
5. Reboot to bootloader
6. use 'fastboot flash recovery recovery.bin' (Link bellow)
7. Optional: fastboot oem lock
8. reboot
9. on boot you will get encryption, click on the reset button when android loads
10. You will reboot into recovery then back into system, done
Fastboot
1. Extract zip file
2. flash system.img, boot.img, vendor.img in fastboot
3. fastboot reboot
Links:
Stock ROM zip May
Recovery image
Good luck
XDA:DevDB Information
[ROM][STOCK][TWRP][27/06/18]TA-1060 Stock Oreo 8.1, ROM for the Nokia 1
Contributors
sooti
ROM OS Version: 8.x Oreo
Version Information
Status: Stable
Created 2018-06-27
Last Updated 2018-06-27
So we can flash either through TWRP or Fastboot right?
Zeenat11 said:
So we can flash either through TWRP or Fastboot right?
Click to expand...
Click to collapse
I haven't tested fastboot but it should work. TWRP works 100%
Thank you very much, you are a life saver!!
I was stuck in a TWRP loop.
I tried flashing through TWRP but it didn't work but the fastboot method worked like a charm!
My phone is running again.
Thank you very much.
Is there any userdata.img available?
alexstarc said:
Thank you very much.
Is there any userdata.img available?
Click to expand...
Click to collapse
Nope but do you really need it? just format in fastboot or TWRP.
sooti said:
Nope but do you really need it? just format in fastboot or TWRP.
Click to expand...
Click to collapse
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
I wrote in the instructions...
If you get a password just enter a random one, then it will ask you to wipe the device, click ok and it will reboot to recovery and then wipe userdata and boot fine.
just make sure you flash the recovery.bin and not twrp before you wipe
alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
Same happened to me. I solved it by a hard reset via the stock recovery.
Make sure you flash the recovery.bin like Sooti said.
Wiping through twrp doesn't work.
Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs
A little warning.
It looks like the recovery.bin I took from another nokia 1 device doesn't match the checksum check which causes a failed during ota updates, please only flash this rom if you soft bricked your device.
If anyone can get me TA-1060 stock recovery image that should solve it. for now you can't update the phone until a fix is found
I have Nokia Ta 1066. Will this rom work on mine? Also I read somewhere Ta 1060 is single sim variant. What about the second sim?
Has anyone with TA 1066 tried it?
Thanks. Both methods work fine. Don't ask how I found out.....
Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...
coolboyforeva said:
Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...
Click to expand...
Click to collapse
I don't have stock recovery from our device i have from another variant of Nokia 1
Hey guys i have a TA-1056 and after unlocking bootloader and flashing TWRP it booted to recovery and came up encrypted, after looking around the only solution was to format data, afterwards when rebooting it always boots to recovery, i tried flashing this zip and i get the same issue and i can't find the stock ROM for the 1056 anywhere online, can anyone help me out? i really appreciate it
Kurajmo said:
Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs
Click to expand...
Click to collapse
got any custom roms?
Does Nokia 1 support DT2W?
Sir, is that possible to get a stock rom of TA 1056 ?
I have searched everywhere but whole thing available over net just left my phone bricked. All i need is a working rom source. Even if that’s a custom rom too to flash via sp flash tool. Thanks in advance
Can any please repost the firmware , the link isn't working
Hi all,
so after system update of OOS which ended up in a boot loop and losing the TWRP recovery (back to stock)
I was trying to get TWRP (back again) via fastboot I was able once to get TWRP loaded once and was even lucky to able to load the Nandroid backup "successfully".
but unfortunately, after restarting...nothing... always getting back to fastboot main screen with no success of booting normally or into recovery mode.
also, not able to re-flash the twrp.img to reach again for the backup.
is there another way to get back TWRP and load my backup file? by using fastboot commands?
I just had the same issue.
I managed to fix it using a fastboot image https://drive.google.com/open?id=1fqvjJ-lC7w2wtcxYwlbmZ4pRW60psODV
After the flash completed I booted into the OS then rebooted back to fastboot and from there I was able to use fastboot command to boot into TWRP
Had a similar issue after installing a rom a while back. Posted about it here https://forum.xda-developers.com/oneplus-6/help/stuck-fastboot-trying-to-install-omnirom-t3849882
Google the mega unbrick guide on the OnePlus forums. Let me know if this helps at all. Or give the other link posted there a try as well.
dekela said:
I just had the same issue.
I managed to fix it using a fastboot image https://drive.google.com/open?id=1fqvjJ-lC7w2wtcxYwlbmZ4pRW60psODV
After the flash completed I booted into the OS then rebooted back to fastboot and from there I was able to use fastboot command to boot into TWRP
Click to expand...
Click to collapse
Nice, we're from the same city.
anyhow, have you flashed this by doing "fastboot flash XYZ.zip" ? & afterwards flashed the TWRP again?
nicb1 said:
Had a similar issue after installing a rom a while back. Posted about it here https://forum.xda-developers.com/oneplus-6/help/stuck-fastboot-trying-to-install-omnirom-t3849882
Google the mega unbrick guide on the OnePlus forums. Let me know if this helps at all. Or give the other link posted there a try as well.
Click to expand...
Click to collapse
Thanks for the tip. so after this operation/guide will I'll be able to restore my Nandorid Backup or with will erase it completely ? just a new ROM with stock recovery, right?
QIQgame said:
Nice, we're from the same city.
anyhow, have you flashed this by doing "fastboot flash XYZ.zip" ? & afterwards flashed the TWRP again?
Thanks for the tip. so after this operation/guide will I'll be able to restore my Nandorid Backup or with will erase it completely ? just a new ROM with stock recovery, right?
Click to expand...
Click to collapse
Np. I cant remember exactly but i think it wiped the phone. You won't be able to restore that backup unless you happen to have copied it externally from your phone before the brick.
Let us know if you manage to get it all fixed and going again. Know its frustrating having your phone bricked. Pretty much brought it back to its factory shipped state from what I remember.
QIQgame said:
Nice, we're from the same city.
anyhow, have you flashed this by doing "fastboot flash XYZ.zip" ? & afterwards flashed the TWRP again?
Thanks for the tip. so after this operation/guide will I'll be able to restore my Nandorid Backup or with will erase it completely ? just a new ROM with stock recovery, right?
Click to expand...
Click to collapse
Use this to flash a fastboot image:
https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993
Solution to below problem found in this thread: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
------------------------------------------------------------------------------
So I tried to root my OnePlus 7 Pro, somehow managed to get it stuck in fastboot. No matter what I flash or do to reboot, it just boots back into fastboot.
Normally I'd just flash stock recovery / ROM found on OnePlus' website, but they haven't added anything for OnePlus 7 (Pro) yet.
Anyone got any clue about this?
Nozemi said:
So I tried to root my OnePlus 7 Pro, somehow managed to get it stuck in fastboot. No matter what I flash or do to reboot, it just boots back into fastboot.
Normally I'd just flash stock recovery / ROM found on OnePlus' website, but they haven't added anything for OnePlus 7 (Pro) yet.
Anyone got any clue about this?
Click to expand...
Click to collapse
Give this a read and see if solution helps you
https://forum.xda-developers.com/oneplus-7-pro/help/oneplus-7-pro-bricked-t3931629
SysAdmNj said:
Give this a read and see if solution helps you
https://forum.xda-developers.com/oneplus-7-pro/help/oneplus-7-pro-bricked-t3931629
Click to expand...
Click to collapse
Found the solution there! Thanks a bunch!
(I'll update the OP with exact solution)
Nozemi said:
Found the solution there! Thanks a bunch!
(I'll update the OP with exact solution)
Click to expand...
Click to collapse
Hello,
What post was it ????
im still stuck in fastboot, when i flash persistent.img with fastboot flash boot persistent.im nothing changes an with fastboot flash persistent persisten.img it just says that you cant flash critical partitions HELP PLZ
BeatsXD said:
im still stuck in fastboot, when i flash persistent.img with fastboot flash boot persistent.im nothing changes an with fastboot flash persistent persisten.img it just says that you cant flash critical partitions HELP PLZ
Click to expand...
Click to collapse
You have to get the original boot image and recovery image flash the boot image make sure the phone is in fast boot mode it's the same flashing sequence for the Oppo 10x zoom
after download and reboot apprear this error..refer photo..
Try shutting it down, entering fastboot mode and flashing it from here.
bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
ok thanks..no need unlockboot loader rite?
Boi. said:
ok thanks..no need unlockboot loader rite?
Click to expand...
Click to collapse
You can't flash anything with a locked bootloader
ctfrommn said:
You can't flash anything with a locked bootloader
Click to expand...
Click to collapse
ok thanks..hmmm..
Boi. said:
ok thanks..no need unlockboot loader rite?
Click to expand...
Click to collapse
For Android Flash Tool you need to have OEM unlocking enabled in developer options, but don't need to actually have the bootloader unlocked beforehand. The tool will unlock your bootloader during the process (assuming you are able to unlock the bootloader, e.g. not a Verizon model). It will also lock it afterwards if you choose to do so.
bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
already try..still not work
Boi. said:
already try..still not work
Click to expand...
Click to collapse
You probably need to be more specific. What exactly happened after using Android Flash Tool? How did you initially try to install QPR1B1? Are you using the latest Platform Tools? Do you have the latest USB drivers installed? Have you tried using an A to C cable using a USB 2.0 port?
If you're flashing environment is set up correctly, you can also try sideloading the OTA image.
bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
Thank you!
For the last 4 years I was updating my Pixels by downloading full official image and flashing without -w option, then patching boot.img via magisk and this process worked flawlessy every time. Tried same method with my new Pixel 6a on bluejay-tp1a.220624.021.a1 and every time I'd flash September's update bluejay-tp1a.220905.004.a2 my phone wouldn't boot and I would get "Your device is corrupt. It can't be trusted" error followed by google boot image and then boot loop. OK I thought, I'll wait until I've got time for a clean flash and that will solve it. To my surprise, it did not... Flashed clean image with full wipe and still same issue So now I did it via Android Flash Tool and it worked! For curiosity, then flashed the same image I had issues with via ADB and it also works now So what was the cause of the problem remains a mistery to me...
Pakabidu said:
Thank you!
For the last 4 years I was updating my Pixels by downloading full official image and flashing without -w option, then patching boot.img via magisk and this process worked flawlessy every time. Tried same method with my new Pixel 6a on bluejay-tp1a.220624.021.a1 and every time I'd flash September's update bluejay-tp1a.220905.004.a2 my phone wouldn't boot and I would get "Your device is corrupt. It can't be trusted" error followed by google boot image and then boot loop. OK I thought, I'll wait until I've got time for a clean flash and that will solve it. To my surprise, it did not... Flashed clean image with full wipe and still same issue So now I did it via Android Flash Tool and it worked! For curiosity, then flashed the same image I had issues with via ADB and it also works now So what was the cause of the problem remains a mistery to me...
Click to expand...
Click to collapse
Update:
I think I was able to flash that image with ADB after doing with Android Flash Tool first is because it was the same image. Later tried flashing next month's update via ADB and had same issue again. So today decided to sideload November's update via ADB instead of flashing full image and that worked.
Just wonder what did I mess up for me not to be able to flash with ADB...
Pakabidu said:
Update:
I think I was able to flash that image with ADB after doing with Android Flash Tool first is because it was the same image. Later tried flashing next month's update via ADB and had same issue again. So today decided to sideload November's update via ADB instead of flashing full image and that worked.
Just wonder what did I mess up for me not to be able to flash with ADB...
Click to expand...
Click to collapse
That is really weird behaviour for a Pixel device. I update using the stock rom method for all my pixels and never had issues. I have the Pixel 6 and the only instance I got the device is corrupt when I tried to roll back the November update to the October update causing a bootloop.
I wonder if there is something wrong with the 6A and some people having issues with the oem unlocking being greyed-out. Hopefully, Google will fix the issue with a future patch or monthly update.