Related
Hello!
This is actually a common "thing" across many devices so just because this thread is on the Oneplus 5 forum doesn't mean it won't work for your device!
So I know exactly what you're going through....
THE PROBLEM
You've flashed a Zip file, everything seemed to work fine, you pressed the reboot button.... But then... Black screen, blue LED (or something like that)....
You then try to reboot to recovery and then you see "Running Open Recovery Script" and you manage to decipher "Wiping Data", either you clean flashed your ZIP file and this is not a problem or you dirty flashed it and so you're screaming at your phone because it just wiped everything without you asking (I mean, this never happened to me or anything I'm just trying to imagine what it would look like :crying
You then try a few things but you're phone won't even get close to the Bootanimation and keeps trying to boot up into recovery and keeps on Wiping your data which is now non-existent.
THE FIX :fingers-crossed:
Method 1/
This is the most convenient and easiest method but it might not work for you, I'm not even entirely sure how I made it work for me... Anyway:
Once the phone has booted up into recovery and is flashing the ZIP, try the following:
WILL UPDATE AS SOON AS I FIND THE EXACT METHOD
-Taking a screenshot (Power+volume)
-Pressing the back, home and récents button as many times as you can
-Pressing the power button
Basically, for now until I'm certain on what gets you out of this script thing, press every button on the phone a few times (that's what I did)
Click to expand...
Click to collapse
Method 2 [FAILSAFE]/
This method will work no matter what (if your problem is the one this thread covers that is), but it's quite teedious!
Step1/ Boot into the Bootloader (Power+Volume up)
Step2/ Install ADB & Fastboot on your PC (Google)
Step3/Download Stock recovery & TWRP
Step 4/Move both files to the ADB folder for ease of access
Step5/Type in
Code:
fastboot flash recovery STOCK_RECOVERY.img
(change file name)
Step 6/Boot into this new recovery
Step 7/ Ponder for a minute at how useless it is
Step 8/Boot into Bootloader again
Step 9/Type into terminal
Code:
fastboot flash recovery TWRP_RECOVERY.img
(change file name)
Step 10/Boot into recovery and wipe everything except Internal storage
Step 11/Flash ROM again!
VOILA! :fingers-crossed:
Hope it helped, if you have any questions, feel free to ask me!
Cheers, Matt
I had this issue when I was flashing various roms, in my case it ended up being that some of the roms were incompatible with data being formatted as ext4 (mainly oos based ones, but a few others as well) since I went full f2fs, haven't seen this issue. That might be something to consider adding, it's pretty destructive, though, as going with f2fs on /data formats /sdcard, too
I had this issue when I was flashing various roms (xXx NoLimits, ExperienceOS) on the encrypted data partition. Only FreedomOS flashing and booting ok
dragynbane222 said:
I had this issue when I was flashing various roms, in my case it ended up being that some of the roms were incompatible with data being formatted as ext4 (mainly oos based ones, but a few others as well) since I went full f2fs, haven't seen this issue. That might be something to consider adding, it's pretty destructive, though, as going with f2fs on /data formats /sdcard, too
Click to expand...
Click to collapse
Ahh, that's interesting
R0iZ said:
I had this issue when I was flashing various roms (xXx NoLimits, ExperienceOS) on the encrypted data partition. Only FreedomOS flashing and booting ok
Click to expand...
Click to collapse
I had it on my old phone once (Oneplus X) so it's not rom/device specific... And I don't think it's a bug, more a compatibility issue...
first method doesnt work for me (and i have not expecting it to work)
second method should work but i have a little problem, i cant boot into bootloader
can someone help me with this
phone: Doogee X5
Fyzik753 said:
first method doesnt work for me (and i have not expecting it to work)
second method should work but i have a little problem, i cant boot into bootloader
can someone help me with this
phone: Doogee X5
Click to expand...
Click to collapse
You can't boot into bootloader? Are you sure? Long less power + Volume up
Fyzik753 said:
first method doesnt work for me (and i have not expecting it to work)
second method should work but i have a little problem, i cant boot into bootloader
can someone help me with this
phone: Doogee X5
Click to expand...
Click to collapse
Are you trying to install/fix TWRP designed for OnePlus 5 into a different phone? Good luck!
i have a problem with instaling twrp ...
example:
phone have bootloader unlocked
flashing original 4.5.14 firmware .... all good ... boot phone ... settings ... done
reboot to bootloader ... flash twrp (or blu_spark twrp) ... done ... reboot to twrp .. all good
reboot to system ... done. poweroff (or restart)...
boot to recovery ... surprise ... original recovery ... not twrp
flash again twrp ... done ... boot to system ... reboot to recovery ... original recovery ....
saw .. what is going on ?
thanks
aoprea said:
i have a problem with instaling twrp ...
example:
phone have bootloader unlocked
flashing original 4.5.14 firmware .... all good ... boot phone ... settings ... done
reboot to bootloader ... flash twrp (or blu_spark twrp) ... done ... reboot to twrp .. all good
reboot to system ... done. poweroff (or restart)...
boot to recovery ... surprise ... original recovery ... not twrp
flash again twrp ... done ... boot to system ... reboot to recovery ... original recovery ....
saw .. what is going on ?
thanks
Click to expand...
Click to collapse
OxygenOS overwrites the recovery with stock one when you boot into the OS..
to avoid this, after flashing twrp, (without rebooting to system) flash SuperSU or Magisk immediately..
iamelton said:
OxygenOS overwrites the recovery with stock one when you boot into the OS..
to avoid this, after flashing twrp, (without rebooting to system) flash SuperSU or Magisk immediately..
Click to expand...
Click to collapse
thanks ... solved with install magisk
ps. I was accustomed with samsung phones where this does not happen...
Hi, I hope there's somebody who can help me with this.
I think, method could help me, but when I try to flash the recovery, I get this message:
Code:
target reported max download size of 535822336 bytes
sending 'recovery' (27525 KB)...
OKAY [ 0.914s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.954s
Any Ideas to solve this?
iamelton said:
OxygenOS overwrites the recovery with stock one when you boot into the OS..
to avoid this, after flashing twrp, (without rebooting to system) flash SuperSU or Magisk immediately..
Click to expand...
Click to collapse
i have op5
i don't know what should i do - i install magisk and twrp - is it in the twrp i do that i wipe and i flash rom
but i find the some problem open and after boot i don't found the twrp and my recovery return to official recov
please help
my phone without root is worthless
Im_Mattgame said:
Hello!
This is actually a common "thing" across many devices so just because this thread is on the Oneplus 5 forum doesn't mean it won't work for your device!
So I know exactly what you're going through....
THE PROBLEM
You've flashed a Zip file, everything seemed to work fine, you pressed the reboot button.... But then... Black screen, blue LED (or something like that)....
You then try to reboot to recovery and then you see "Running Open Recovery Script" and you manage to decipher "Wiping Data", either you clean flashed your ZIP file and this is not a problem or you dirty flashed it and so you're screaming at your phone because it just wiped everything without you asking (I mean, this never happened to me or anything I'm just trying to imagine what it would look like :crying
You then try a few things but you're phone won't even get close to the Bootanimation and keeps trying to boot up into recovery and keeps on Wiping your data which is now non-existent.
THE FIX :fingers-crossed:
Method 1/
This is the most convenient and easiest method but it might not work for you, I'm not even entirely sure how I made it work for me... Anyway:
Once the phone has booted up into recovery and is flashing the ZIP, try the following:
Method 2 [FAILSAFE]/
This method will work no matter what (if your problem is the one this thread covers that is), but it's quite teedious!
Step1/ Boot into the Bootloader (Power+Volume up)
Step2/ Install ADB & Fastboot on your PC (Google)
Step3/Download Stock recovery & TWRP
Step 4/Move both files to the ADB folder for ease of access
Step5/Type in
Code:
fastboot flash recovery STOCK_RECOVERY.img
(change file name)
Step 6/Boot into this new recovery
Step 7/ Ponder for a minute at how useless it is
Step 8/Boot into Bootloader again
Step 9/Type into terminal
Code:
fastboot flash recovery TWRP_RECOVERY.img
(change file name)
Step 10/Boot into recovery and wipe everything except Internal storage
Step 11/Flash ROM again!
VOILA! :fingers-crossed:
Hope it helped, if you have any questions, feel free to ask me!
Cheers, Matt
Click to expand...
Click to collapse
You saved me bro my life is your from now thankyou love u♥
Very strange behavior on my Xiaomi A1, running stock Android 8.0...
I have been using Magisk for quite some time, and did not have any issues. But this changed with the most recent (April) OTA update
After using for 1/2 a day or so, I found my phone hanging in 'Recovery mode', telling me that some system files are damaged. Restart did not heelp
So I reinstalled the phone using Mi-Flash-Tool, unlocked, installed the latest OTA, installed Magisk (direct method), and again after a couple of hours the phone ended in a boot-loop.
And again, I reinstalled the phone using Mi-Flash-Tool, installed the latest OTA, unlocked, installed the 'patched_boot.img', the phone booted, showed 'no Sim Card', a dimmed screen, and rebooted again and again..
So it seems it's getting worse ...
I have Magisk-Manager installed, with some Modules, but the most recent problems happen even before installing Magisk.
With the stock-installation (stock boot image) everything is fine.
Any idea what went wrong?
I'd like to know too. Our device is rather wonky. Sometimes it gets stuck on the boot animation. Other times, the baseband is damaged which causes the no SIM Card error. All of which is corrected on a reboot.
oreo27 said:
I'd like to know too. Our device is rather wonky. Sometimes it gets stuck on the boot animation. Other times, the baseband is damaged which causes the no SIM Card error. All of which is corrected on a reboot.
Click to expand...
Click to collapse
I tried several reboots, and finally decided to re-install
My Xiaomi A1 is acting more weird and worse ....
I have been following every lead I found, but no success:
Every of these 3 approaches started with Re-Flashing the original FW using MiFlashTool (keeping my data), and updating the latest OTA. => I assume having a clean system to start with. Magisk Safety Check says: OK
First approach:
1) After following the procedure 'fastboot oem unlock' and 'fastboot boot patched-boot.img' my A1 starts booting but hangs forever at boot-animation.
2) When I do a force reboot (hold on/off key for 15sec) the device boots normally.
3) Going to MagiskManager I see 'ctsProfile: false', and when trying to install I am only offered 'download' and 'patch boot image', but no 'direct install' => so it seems the patched boot-image is not installed
Second approach:
1) After following the procedure 'fastboot oem unlock' and 'fastboot flash boot patched-boot.img' my A1 starts booting but hangs forever at boot-animation.
2) A reboot does not help, A1 starts booting but hangs forever at boot-animation.
3) a 'fastboot flash boot_a original-boot.img' and 'fastboot flash boot_a original-boot.img' brings the A1 back to normal life, but of cause with no MAGISK installable
Third Approach:
1)After 'fastboot oem unlock' and 'fastboot boot recovery-3.2.1-2-oreo.img' my A1 boots into TWRP recovery
2) I install Magisk-v16.3.zip, and reboot.
3) Booting lasts a couple of minutes and then I see my homescreen, dimmed, with wrong time, 'No SIM Card found' - and the device reboots after 10-15 seconds. Additional reboots don't help
As nothing is installed, or I have to re-flash I am not able to provide any log files.
The only step I have not tried yet is a full factory reset ....
Any idea what is wrong?
First approach does nothing. You can't boot a boot image, it needs to be flashed.
Second approach should normally work. But just to make sure, the patched boot image is from your current firmware, right? If it doesn't match your current setup, that can cause issues.
Third approach: try this again, but experiment with keeping dm-verity and forced encryption.
Tiemichael said:
My Xiaomi A1 is acting more weird and worse ....
I have been following every lead I found, but no success:
Every of these 3 approaches started with Re-Flashing the original FW using MiFlashTool (keeping my data), and updating the latest OTA. => I assume having a clean system to start with. Magisk Safety Check says: OK
First approach:
1) After following the procedure 'fastboot oem unlock' and 'fastboot boot patched-boot.img' my A1 starts booting but hangs forever at boot-animation.
2) When I do a force reboot (hold on/off key for 15sec) the device boots normally.
3) Going to MagiskManager I see 'ctsProfile: false', and when trying to install I am only offered 'download' and 'patch boot image', but no 'direct install' => so it seems the patched boot-image is not installed
Second approach:
1) After following the procedure 'fastboot oem unlock' and 'fastboot flash boot patched-boot.img' my A1 starts booting but hangs forever at boot-animation.
2) A reboot does not help, A1 starts booting but hangs forever at boot-animation.
3) a 'fastboot flash boot_a original-boot.img' and 'fastboot flash boot_a original-boot.img' brings the A1 back to normal life, but of cause with no MAGISK installable
Third Approach:
1)After 'fastboot oem unlock' and 'fastboot boot recovery-3.2.1-2-oreo.img' my A1 boots into TWRP recovery
2) I install Magisk-v16.3.zip, and reboot.
3) Booting lasts a couple of minutes and then I see my homescreen, dimmed, with wrong time, 'No SIM Card found' - and the device reboots after 10-15 seconds. Additional reboots don't help
As nothing is installed, or I have to re-flash I am not able to provide any log files.
The only step I have not tried yet is a full factory reset ....
Any idea what is wrong?
Click to expand...
Click to collapse
Which option do you choose in the MiFlash tool? Try this:
1. Flash using MiFlash Tool (Save User Data) > Reboot
2. adb reboot bootloader or simply boot to Fastboot
3. Boot the TWRP img
4. Flash Magisk 16.3.
5. Reboot.
Didgeridoohan said:
First approach does nothing. You can't boot a boot image, it needs to be flashed.
Click to expand...
Click to collapse
Yes, according to 'fastboot help' it should not work ..
But I have used it sucessfully before, and there is a lot of threads advocation 'fastboot boot patched_boot.img' e.g. https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
Didgeridoohan said:
ust to make sure, the patched boot image is from your current firmware, right? .
Click to expand...
Click to collapse
I downloaded, and created the patched boot-image myself, no difference
Didgeridoohan said:
Third approach: try this again, but experiment with keeping dm-verity and forced encryption.
Click to expand...
Click to collapse
I will try when I have some time
Thank you!
oreo27 said:
Which option do you choose in the MiFlash tool? Try this:
1. Flash using MiFlash Tool (Save User Data) > Reboot
2. adb reboot bootloader or simply boot to Fastboot
3. Boot the TWRP img
4. Flash Magisk 16.3.
5. Reboot.
Click to expand...
Click to collapse
There is a OTA update after flashing, the rest is exactly my Third approach!
Thank you!
Tiemichael said:
There is a OTA update after flashing, the rest is exactly my Third approach!
Thank you!
Click to expand...
Click to collapse
It won't install properly though if Magisk is installed. To get the OTA update, you need to re-flash the stock boot.img.
oreo27 said:
It won't install properly though if Magisk is installed. To get the OTA update, you need to re-flash the stock boot.img.
Click to expand...
Click to collapse
It seems my comment was not clear:
My Third approach:
1) Flash the original ROM using MiFlash, with 'keep data'
2)OTA Update
3)Unlock Bootloader
4)Boot TWRP
5)install Magisk 16.3 via TWRP
6)Reboot
Is there anything wrong with this?
Thanks!
Tiemichael said:
It seems my comment was not clear:
My Third approach:
1) Flash the original ROM using MiFlash, with 'keep data'
2)OTA Update
3)Unlock Bootloader
4)Boot TWRP
5)install Magisk 16.3 via TWRP
6)Reboot
Is there anything wrong with this?
Thanks!
Click to expand...
Click to collapse
Nothing wrong with that. Should work... But, as always with the fragmented Android ecosystem: YMMV.
Didgeridoohan said:
Third approach: try this again, but experiment with keeping dm-verity and forced encryption.
Click to expand...
Click to collapse
I put both into TWRP terminal before installing Magisk: no difference
Thanks!
Tiemichael said:
It seems my comment was not clear:
My Third approach:
1) Flash the original ROM using MiFlash, with 'keep data'
2)OTA Update
3)Unlock Bootloader
4)Boot TWRP
5)install Magisk 16.3 via TWRP
6)Reboot
Is there anything wrong with this?
Thanks!
Click to expand...
Click to collapse
Looks good. I would insert a reboot to system between 2 and 3 to ensure that the OTA completes properly.
oreo27 said:
Looks good. I would insert a reboot to system between 2 and 3 to ensure that the OTA completes properly.
Click to expand...
Click to collapse
Thanks!
Yes, there is definitely a Reboot after the OTA
Finally - it's working! Not sure what was wrong ...
How did I fix it:
Note: Xiaomi published a new FW yesterday, which included the latest (April) OTA update-> so need for OTA !
1) Installed original ROM using MiFlash
2) Fastboot oem unlock
3) fastboot boot twrp-recovery
4) TWRP: install Magisk-Uninstaller.zip (to get rid of all Magisk remains)
5) reboot system
6) fastboot boot twrp-recovery
7) TWRP: install Magisg-16.3.zip
8) reboot
9) Open Magisk Manager, install module1, reboot (to detect any module causing problems)
10) Open Magisk Manager, install module2, reboot
At the moment I am a 'Happy Magiscian', but let's wait and see
Thanks to all to helped with their valuable comments!
This happens with the beta release of Magisk. Change to stable channel, then patch the boot.img and you will have no problems.
I am trying it on an old vivo phone and getting somewhat same error but my phone keeps getting on and off, it doesn't even boots up completely it just shows VIVO and then off .... again VIVO and then off, and it goes on. I flashed the original boot.img and my phone working but then I cant root my device.
hi friends! I tried lineageos but can't live without reliable camera. Now trying to restore stock. but unsuccessful so far. My current status is,
1. I am able to boot to fastboot
2. I am able to boot to recovery. (twrp 3.2.1.0)
3. tried to flash OEM rom bellow (had to modify "updater-script", delete first two lines of code), after reboot, phone stuck on Leeco boot screen. This is the instructions I followed, https://youtu.be/v_aohNnvT_Q
S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
Any helps are much appropriated. :good::good::good:
apparently, I didn't do anything wrong. tried to flash again and again, suddenly it booted back to stock.
What am I missing here, your description says x522, even the filenames you list and the video say x526...
leo221 said:
apparently, I didn't do anything wrong. tried to flash again and again, suddenly it booted back to stock.
Click to expand...
Click to collapse
Where are you from?
leo221 said:
hi friends! I tried lineageos but can't live without reliable camera. Now trying to restore stock. but unsuccessful so far. My current status is,
1. I am able to boot to fastboot
2. I am able to boot to recovery. (twrp 3.2.1.0)
3. tried to flash OEM rom bellow (had to modify "updater-script", delete first two lines of code), after reboot, phone stuck on Leeco boot screen. This is the instructions I followed,
S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
Any helps are much appropriated. :good::good::good:
Click to expand...
Click to collapse
I am also having same problem on letv x526 indian version. After installing stock rom the phone stucks in bootloop. I tried using the chinese recovery also but no luck. I waited atmost 30 min for the phone to get out of boot loop.
Any solution. Pls help
amrit0 said:
I am also having same problem on letv x526 indian version. After installing stock rom the phone stucks in bootloop. I tried using the chinese recovery also but no luck. I waited atmost 30 min for the phone to get out of boot loop.
Any solution. Pls help
Click to expand...
Click to collapse
I flashed multiple times to make it work. you try the same. follow the exact wipe...restore sequence in the video.
leo221 said:
I flashed multiple times to make it work. you try the same. follow the exact wipe...restore sequence in the video.
Click to expand...
Click to collapse
Kk i will try that.
By the way which rom version have you flashed?
amrit0 said:
Kk i will try that.
By the way which rom version have you flashed?
Click to expand...
Click to collapse
S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
my phone is X522 US version.
leo221 said:
S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
my phone is X522 US version.
Click to expand...
Click to collapse
And which recovery were u using? Were you wiping cache immidiately after installing the rom?
Also should i wipe internal storage or not?
amrit0 said:
And which recovery were u using? Were you wiping cache immidiately after installing the rom?
Also should i wipe internal storage or not?
Click to expand...
Click to collapse
twrp 3210. I followed EXACT steps in the video and must be in that wiping sequence. if i don't, phone wouldn't boot.
leo221 said:
twrp 3210. I followed EXACT steps in the video and must be in that wiping sequence. if i don't, phone wouldn't boot.
Click to expand...
Click to collapse
I installed the rom 7-8 times but phone didnt booted. What should i do now?
Is this for rom mtk or not snapdragon?
When you flash stock rom via twrp successfully then before reboot flash andromax kernel for le2 after flash kernel then reboot system now this time your phone starts eui rom but remember first boot take some time maybe 2-5 minutes.
Use Red Wolf Recovery
For le S3 X522 US Version
--------------------------------
leo221 said:
hi friends! I tried lineageos but can't live without reliable camera. Now trying to restore stock. but unsuccessful so far. My current status is,
1. I am able to boot to fastboot
2. I am able to boot to recovery. (twrp 3.2.1.0)
3. tried to flash OEM rom bellow (had to modify "updater-script", delete first two lines of code), after reboot, phone stuck on Leeco boot screen. This is the instructions I followed, https://youtu.be/v_aohNnvT_Q
S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
Any helps are much appropriated. :good::good::good:
Click to expand...
Click to collapse
Hi i also suffered from this problem very long time.
But phone stuck on Leeco boot screen
I accidentally found custom recovery "Red Wolf"
which supports EUI ROMs
which was mentioned in features as "Automatic EUi boot image patching"
Recovery X52X V3.1-017
You can download it from my Google drive also.
Steps to Install ( For le S3 X522 US Version)
----------------------------------------------
1. delete first two lines in update-script
2. Install red wolf recovery
3. This can be installed from fastboot
Or you can install it directly from
twrp. (if you dont know ask here / google)
4. Go to recovery > swipe to allow modifications
5. wipe all partitions (excluding boot)
6. plug your le S3 X522 to computer
7. Go to my computer and copy
S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
to internal storage
8. you can copy supersu also at same time
and root if you want
9. Steps from 9-11 only needed if you have ever
encountered no os installed after flashing and reboot
10. press power button long and restart system
your phone wont have any os this time so your phone
will go to boot screen and show leeco logo
11. wait 30 seconds and press volume up(+) button and power key
you will go to recovery
12. Now you have followed step 6 so you will have
S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
in internal storage(additionally supersu file if you copied)
13. install S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
and ( additionally you can install supersu).
wait until all install finishes.
14. reboot it eui should appear within 5 minutes
enjoy
Finally when you rebooting if wolf recovery said os not installed
system will stuck on boot screen so
concentrate on steps 9-11
I have tested installation more than 10 times around 4 times i received os not installed message.
I have been able to install LineageOS, it is working but with bugs, for example the 5GHz Wifi is not working & It have been hard to make it connect to the 2.4 GHz, once connected for first time it worked fine (2.4 only)
Here is how to do:
You need fastboot, connect T5 to computer.
Download TWRP for Huawei P20 Lite, I used this one:
https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692
Copy downloaded file to adb&fastboot folder
Open a DOS box or command line, use:
adb reboot bootloader
fastboot flash recovery_ramdisk TWRP.img
fastboot reboot
Press volume+ & diconnnect USB, TWRP will start.
From the main menu of TWRP, tap Wipe, and then tap Format Data.
Follow TWRP’s instructions.
Tap on Advanced Wipe.
Check the boxes: Dalvik/ART Cache, System, and Cache. Leave all the others unchecked.
Swipe from left to right on the slider marked Swipe.
Download LineageOS 16 from:
https://openkirin.net/download/
go down to EMUI 8-based Builds
Copy downloaded file to adb&fastboot folder
Extract the compressed .XZ file
Go to command line & enter:
adb reboot bootloader
fastboot flash system lineage16.img
fastboot reboot
Disconnect USB, LineageOS will start.
stuck on recovery
Hi,
I followed the tuto and flashed a GSI rom following this tuto, and I ended up stuck on the recovery boot page, I can't access fastboot anymore, even if I flash it from the PotatoNV tool, it blink on the fastboot an then reboot on the recovery.
Does anyone know how to clean flash the fastboot. I think that way I could flash the recovery and the system...
Please help me
fixed my mistake
EtienneHD said:
Hi,
I followed the tuto and flashed a GSI rom following this tuto, and I ended up stuck on the recovery boot page, I can't access fastboot anymore, even if I flash it from the PotatoNV tool, it blink on the fastboot an then reboot on the recovery.
Does anyone know how to clean flash the fastboot. I think that way I could flash the recovery and the system...
Please help me
Click to expand...
Click to collapse
I fixed it by rebooting using vol+, vol-, power to reboot in the special mode from huawei. it allowed me to download and flash the firmware from here.
I will try again later, I hope it will work better next time :silly:
Kgonla said:
I have been able to install LineageOS, it is working but with bugs, for example the 5GHz Wifi is not working & It have been hard to make it connect to the 2.4 GHz, once connected for first time it worked fine (2.4 only)
Here is how to do:
You need fastboot, connect T5 to computer.
Download TWRP for Huawei P20 Lite, I used this one:
https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692
Copy downloaded file to adb&fastboot folder
Open a DOS box or command line, use:
adb reboot bootloader
fastboot flash recovery_ramdisk TWRP.img
fastboot reboot
Press volume+ & diconnnect USB, TWRP will start.
From the main menu of TWRP, tap Wipe, and then tap Format Data.
Follow TWRP’s instructions.
Tap on Advanced Wipe.
Check the boxes: Dalvik/ART Cache, System, and Cache. Leave all the others unchecked.
Swipe from left to right on the slider marked Swipe.
Download LineageOS 16 from:
https://openkirin.net/download/
go down to EMUI 8-based Builds
Copy downloaded file to adb&fastboot folder
Extract the compressed .XZ file
Go to command line & enter:
adb reboot bootloader
fastboot flash system lineage16.img
fastboot reboot
Disconnect USB, LineageOS will start.
Click to expand...
Click to collapse
Have any screenshots ?
OpenKirin doesn't support TWRP.
Read the point 4:
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
I installed twrp and then flashed LineageOS it just stuck at TWRP recovery splash screen. I could access adb commands, nothing else.
Fortunately I managed to boot into stock recovery by pressing Vol + and start button, it allowed me to download the stock firmware and flash it back to original firmware.
I don't know how to remove TWRP completely and I am scared to flash lineage os 16 again.
gunpal5 said:
OpenKirin doesn't support TWRP.
Read the point 4:
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
I installed twrp and then flashed LineageOS it just stuck at TWRP recovery splash screen. I could access adb commands, nothing else.
Fortunately I managed to boot into stock recovery by pressing Vol + and start button, it allowed me to download the stock firmware and flash it back to original firmware.
I don't know how to remove TWRP completely and I am scared to flash lineage os 16 again.
Click to expand...
Click to collapse
TWRP do not work when LineageOS is installed.
When LineageOS is deleted or replaced by the Huawei firmware TWRP will work again.
If you want to delete the firmware you can do it via fastboot:
fastboot erase system
To delete TWRP I think this is the command (not 100% sure):
fastboot erase recovery_ramdisk
Hi, did you trie to install ROM without TWRP ?
Hi guys, I have successfully installed LineageOS 16 on my Mediapad T5 LTE. So far everything seems to work fine including wifi and LTE and i haven't had any problems with it. I followed this: https://forum.xda-developers.com/mediapad-t5/how-to/how-to-unlock-bootloader-t4141705 to unlock the bootloader. I then followed the instructions on OpenKirin website to flash LineageOS 16. I have also successfully installed magisk on LOS16 by patching the ramdisk from ags-l09. Hope it works for you guys as well. Here are screenshots.
wesmat95 said:
Hi guys, I have successfully installed LineageOS 16 on my Mediapad T5 LTE. So far everything seems to work fine including wifi and LTE and i haven't had any problems with it. I followed this: https://forum.xda-developers.com/mediapad-t5/how-to/how-to-unlock-bootloader-t4141705 to unlock the bootloader. I then followed the instructions on OpenKirin website to flash LineageOS 16. I have also successfully installed magisk on LOS16 by patching the ramdisk from ags-l09. Hope it works for you guys as well. Here are screenshots.
Click to expand...
Click to collapse
Netflix and Prime is working?
Sent from my ELE-AL00 using Tapatalk
sheenswizner said:
Netflix and Prime is working?
Sent from my ELE-AL00 using Tapatalk
Click to expand...
Click to collapse
Just tested it. Netflix needs the old app but prime works fine
So have any way to install magisk on this system
Got my mediapad t5 working with the latest lineageOS 16 and magisk 21.1!
Took a while but finally figured it out.
TWRP will get stuck on the boot screen after you fastboot flash lineageOS so either erase the recovery partition or leave it if you want to take the risk (I never got stuck on it, just press and hold the power button, plug in cable + volume down when it restarts to go into fastboot mode).
Follow the instructions here: https://openkirin.net/user_guide/how-to-install-magisk/ for magisk install without TWRP. You'll need to find the closest firmware download to your device model #. Mine was AGS2-L03 but I could only find AGS2-L09 to be the closest here: https://pro-teammt.ru/en/online-firmware-database/?firmware_model=ags2&firmware_page=0.
You'll need to extract the update.APP, and then extract the ramdisk using the Huawei recovery tool. Then patch with magisk manager (and flash the patched boot.img with fastboot).
I lately tried to flash my mediapad t5 with lineage but after several tries and searches I couldnt for the live of me get the pad unlocked to flash. i followed the instructions but it will always say 'phone - locked' on the dev screen.
some searchresults suggested that huawei had a service website where you could request an unlock code for your t5 but the site was shut a while ago. how do i unlock MY mediapad?!
Edit: Is the only option to open the case and short the testpoint?
Trying to install LineageOS 16 but I see FRP is Locked. Is it safe to continue? If not, how do I unlock FRP?
Has anyone here heard of the hcu repair tool? has anyone used it before and does it work to unlock the ags2-w09 mediapad t5 completely?
mine says 'phone locked' and the only option i seem to have atm is to short the testpoint. that seems to be a last resort for me. any suggestions?
Unlocked the bootloader without any problems and flashed LineageOs 16.0 B6 on ags2-l09.
Sound and wifi works fine, the cam works with androin.camera2.
Compared to the stock rom it runs a lot better.
As been mention small quirk with the blured text can be fixed by disable HW overlays.
Is it posible to set this option permanently? It gets reseted after reboot.
There is one bigger inconiniane.
When i plug the tablet to a pc(windows) it does not show in the explorer(file transfer is enabled). In the devce menager it gets mounted as composite device.
Under linux i also cannot mount it.
Has anyone the same issue? Any fix?
Luckily adb/fastboot works.
Can someone send me the lineageOs image? I went through all the trouble unblocking the bootloader and now the website is down. Thanks!
geist_patrick said:
Can someone send me the lineageOs image? I went through all the trouble unblocking the bootloader and now the website is down. Thanks!
Click to expand...
Click to collapse
Here it is, version 16.0 with gapps. This is the only one I have:
File on MEGA
mega.nz
borja113 said:
Here it is, version 16.0 with gapps. This is the only one I have:
File on MEGA
mega.nz
Click to expand...
Click to collapse
Thank you very much! Finally I'll have lineageOS on my device!
I didn't know there is a version with gapps. Actually I was searching for the version without them to improve speed but I can just remove them.
I see that Openkirin site is back again. You can pick a more recent build there, and without gapps if it's you preference.
I successfully flashed my European oneplus 10 pro using the instructions - see link below.
Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
I spend hours and hours making it perfect.
I had the perfect phone.
So if someone wants to know how to use lineageos with full GAPS, just follow the link below.
Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
Meaning that I cannot repair my phone.
All I can do is push the volume down and go to recovery mode. That's all.
My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.
This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
and this is where I CRUSHED down by running this:
The rootingget you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
THANK YOU FOR YOUR HELP !!!
This should work for you
Note: You are already in FastbootD (Recovery).
Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
yedashare said:
I successfully flashed my European oneplus 10 pro using the instructions - see link below.
Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
I spend hours and hours making it perfect.
I had the perfect phone.
So if someone wants to know how to use lineageos with full GAPS, just follow the link below.
Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
Meaning that I cannot repair my phone.
All I can do is push the volume down and go to recovery mode. That's all.
My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.
This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
and this is where I CRUSHED down by running this:
The rootingget you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
THANK YOU FOR YOUR HELP !!!
Click to expand...
Click to collapse
Savio Dantes said:
This should work for you
Note: You are already in FastbootD (Recovery).
Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
Click to expand...
Click to collapse
Thank you Savio, but this is my main issue, I cannot enter fastbootD.
Whether using the tool "fastboot enhance" or using the command line. I cannot reach FastboodD.
When I try to reach this using the tool, it's looping with no error log.
And when I try from CMS:
C:\Users\me\Downloads\from dumper> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
It also still sounds like your recovery.img and/r boot.img still may be corrupted.
this needs to MATCH in BOTH slots A & B
Try this:
https://forum.xda-developers.com/t/...e-rom-root-and-recovery.4525451/post-87806713
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
yedashare said:
and this is where I CRUSHED down by running this:
The rootingget you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Click to expand...
Click to collapse
This is where your fatal mistake was.... the red line above is incorrect !
It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"
you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.
The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.
Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.
When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.
hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.
cheers
u can try to fix sms mms problem using this thread
xiaomi 12/moto edge x30(or any device with sm8450) sms＆ims error · Issue #2246 · phhusson/treble_experimentations
Now gsi is able to boot on devices with sm8450.But sms doesn't work.And ims settings shows "not supported" .I tried to install q-ims.apk or ims.apk from the stock rom.Still ,ims does work at all. A...
github.com
@yedashare
@dladz maybe we can share it groups ?
beatbreakee said:
This is where your fatal mistake was.... the red line above is incorrect !
It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"
you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.
The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.
Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.
When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.
hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.
cheers
Click to expand...
Click to collapse
Thank you, BB, for the clear explanations about respecting the structure of the partitions and not messing directly with the boot partition using a modified img.
Do I need to reach the conclusion that my phone is broken forever and there is nothing I can do to fix it?
I thought that as long as I reach the recovery mode, I can still fix it.
If you have a brilliant solution just as brilliant as your teaching, could you please help me restoring my phone to a functional state?
And BTW, it was a TRIPLE FLAW, because I had a wonderful lineageos 19 working like a charm with GAPS and I just wanted to root it for no reason.
Many thanks for your efforts.
Damn. Nice to know Lineage works well on this phone with extensive tweaking. GSI's can be pretty unstable from what I've seen, missing cell reception and the like.
Yeah, flashing that image killed the phone. I've seen some people recover by flipping their boot slot to the other one and forcing the phone to boot the stock boot there. But if you've flashed to both slots, you're most likely SOL and need a MSM flash. In which case, you could try flashing the complete stock boot image for your OOS version you were on before moving to GSI to both slots as sort of a last resort, but even then I've only seen minimal success.
Savio Dantes said:
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
Click to expand...
Click to collapse
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use
Savio Dantes said:
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
Click to expand...
Click to collapse
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use MSM.
I understand that MSM is no longer available.
Any other direction how I can just fix the booting process?
And this is another error I received which gets closer to the source of the problem:
FAILED (remote: 'Failed to load/authenticate boot image: Bad Buffer
I’m assuming Adb does not work?
why don't we get boot_debug and vendor_boot_debug images to debug and then boot into fastbootd and flash it again, why waste time researching these unrelated things.
Arealhooman said:
I’m assuming Adb does not work?
Click to expand...
Click to collapse
Yes right, adb doesn't work, only fastboot is still alive
TuLy2702 said:
why don't we get boot_debug and vendor_boot_debug images to debug and then boot into fastbootd and flash it again, why waste time researching these unrelated things.
Click to expand...
Click to collapse
Thanks for taking time to answer.
Could you be more specific?
I SAVED MY PHONE
BACK ONLINE
THANKS TO THIS POST:
[TOOL] Oppo/Realme Flash .OFP File on Bootloader
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool. THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED Features soft unbrick install stock firmware switch device region Credits...
forum.xda-developers.com
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!
One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.
A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.
yedashare said:
I SAVED MY PHONE
BACK ONLINE
THANKS TO THIS POST:
[TOOL] Oppo/Realme Flash .OFP File on Bootloader
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool. THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED Features soft unbrick install stock firmware switch device region Credits...
forum.xda-developers.com
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!
One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.
A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.
Click to expand...
Click to collapse
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS
yedashare said:
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS
Click to expand...
Click to collapse
you make me laugh
yedashare said:
EoS
Click to expand...
Click to collapse
Damn. I think what happened is you lost your persist.img when initially flashing the first ofp, that thing controls low level stuff like fingerprint unlock and charger cable auth I've seen on these forums. I'm not sure there's a way to get it back either outside of a MSM Flash, certainly haven't seen one here.
Prant said:
Damn. I think what happened is you lost your persist.img when initially flaahing the first ofp, that thing controls low level stuff like fingerprint unlock and charger cable auth I've seen on these forums. I'm not sure there's a way to get it back either outside of a MSM Flash, certainly haven't seen one here.
Click to expand...
Click to collapse
It's okay to spend a little money. It's very risky to do it yourself
Did you managed to get fingerprint working on gsi ?