Related
hey
when my phone boots shows that my device is not verified by google , what to do?
Jwtiyar said:
hey
when my phone boots shows that my device is not verified by google , what to do?
Click to expand...
Click to collapse
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around
sukhwant717 said:
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around
Click to expand...
Click to collapse
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related
Jwtiyar said:
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related
Click to expand...
Click to collapse
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.
sukhwant717 said:
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.
Click to expand...
Click to collapse
You made it really complex bro i dont understand what to do.
Jwtiyar said:
You made it really complex bro i dont understand what to do.
Click to expand...
Click to collapse
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.
sukhwant717 said:
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.
Click to expand...
Click to collapse
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?
Jwtiyar said:
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?
Click to expand...
Click to collapse
device model ze551ml oe ze550ml?
sukhwant717 said:
device model ze551ml oe ze550ml?
Click to expand...
Click to collapse
ze551
Jwtiyar said:
ze551
Click to expand...
Click to collapse
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error
sukhwant717 said:
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error
Click to expand...
Click to collapse
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .
Jwtiyar said:
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .
Click to expand...
Click to collapse
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
I installed RBR ROM which based on MM , now the error gone after flashing boot.img but the will boot to asus logo and will reboot again it seems its bootloop .
sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/
Jwtiyar said:
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/
Click to expand...
Click to collapse
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?
sukhwant717 said:
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?
Click to expand...
Click to collapse
custom MM
Jwtiyar said:
custom MM
Click to expand...
Click to collapse
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question
sukhwant717 said:
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question
Click to expand...
Click to collapse
thank you very much now its booted successfully
Jwtiyar said:
thank you very much now its booted successfully
Click to expand...
Click to collapse
great good to know your device is alive again
sukhwant717 said:
great good to know your device is alive again
Click to expand...
Click to collapse
Thank you bro
I just bricked my phone :crying: :crying:
I wanna get back to the official rom, after trying android P (without make it work).
(the rom is from http://en.miui.com/download-354.html)
But I run the wrong script and take the flash_all_lock.img
And my device is stuck on android 8.1 bootloop (It boot, but i get an animated line loop ...)
Any ideas or tricks before i get it back to warranty ?
Thanks
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
BubuXP said:
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
Click to expand...
Click to collapse
But since I flashed the official rom with data whipe, I'm unable to go to dev option and enter OEM Unlocking .... And Fastboot respond me that my device is locked
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
droopeur said:
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
Click to expand...
Click to collapse
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
BubuXP said:
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
Click to expand...
Click to collapse
In fact, both work, but my phone still stucked at the bootloader (infinite line animation in both cases).
BubuXP said:
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
Click to expand...
Click to collapse
Yes I can enter recovery and I have already tried this, but I always end up with the error:
Code:
E: Unknow volume for path [/sideload/package.zip]
Verifying update package...
Update package verification took 17.3 s (result 0)
Installing update...
E:Error il /sideload/package.zip (Status 1)
Installation aborted
BubuXP said:
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
Click to expand...
Click to collapse
Yes of course !
But I revert to stock rom with Mi Flash and I click on Flash all and lock, since the telephone should have been "brand new" it should not have any problems but ...
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
LUNARIO said:
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
Click to expand...
Click to collapse
But since I can't activate OEM I can't unlock bootloader....
try this http://www.xiaomitool.com/ not sure if it works on our phone but maybe can unlock the bootloader so you can use miflash
Have you sideloaded the zip? I think it's better to copy the OTA zip to microSD than ADB sideload.
droopeur said:
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
Click to expand...
Click to collapse
There should be only two methods for entering EDL:
1- request authorization in en.miui.com forum. Sometimes the admins accept requests to give an account one EDL flash permission (but I don't know if it works with AndroidOne devices).
2- finding the test point in the phone's motherboard.
Hi guys,
i tried to install this twrp but it doesnt work...
so i searched on internet and i found another article, i tried to check the current partition and install in another way
for first:
fastboot getvar current-slot
after i do this
fastboot boot_b recovery.img
and then
fastboot set_active b
so nothing to do....but right now my MI A2 lite not boot.
i try again to check my partition but this time i have no replay.
i have unlocked bootloader but i cant go to recovery and i cant boot!!
someone can help me please?
I HAVE THE SAME PROBLEM
everything you said is completely simillar to mine. Can someone help us? Or did you already fix it? Please help me i need my phone working.
I have same problem fastboot flash but after that, it started to reboot automatically. The phone was automatically turning off and on. I again did a "clean all and lock" via miflash tool but still now, no result!
I can boot into recovery without having any problem. But when I boo to setup country date....etc, it starts its auto rebooting process,
Any help ?
droopeur said:
But since I can't activate OEM I can't unlock bootloader....
Click to expand...
Click to collapse
Same situation here. I am desperate!! Did you solve it?
Isso resolve
steledama said:
Same situation here. I am desperate!! Did you solve it?
Click to expand...
Click to collapse
gadgetsfarm.com/download-mi-a2-lite-fastboot-rom-v9-6-4-download/[/url]
How to unbrick?
Hey guys. I bricked my Mi2 Lite as well. Is there any step by step way to unbrick?
had the same problem, was stuck in the bootloop even after I flashed img with MiFlash! NOTE: MY BOOTLOADER WAS UNLOCKED!!! (LUCKLY I DID NOT TRIED FLASH ALL AND UNLOCK!)
headed to this thread
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
did not work, I get error saying FAILED
but after i used
Code:
fastboot oem edl
I went to MiFlash and used "Clean all" option (again note DON'T use "Clean all and lock"!!!). It took around 5 minutes to flash and my notif. light blinked whole the time. After it say "Success" I was able to normaly boot the phone again
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Hi, where i can find MI A2 Lite Tool Kit? i open my device and i can put in EDL mode., my computer detect my pone in EDL mode, but i can not know do.
I like bypass FRP, can anybody help me
Thanks.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse
Hi all,
I also had same problem and I just resolve it.
My phone was in bootloop mode after stock rom flashing...
You don't need apply "fastboot oem edl" !
Just be sure your device is unlocked.
Download first stock rom (V9.6.4.0.ODLMIFF Firmware for Mi A2 Lite). If you flash last ROM, it don't work.
Flash it with XiaoMiFlash tool (don't forget to enable "Clean All") in bottom of the tool.
After reboot, you can apply OTA updates.
Enjoy !
I unlocked bootloader of my phone, flashed TWRP then installed new ROM and then tried to boot bt the only thing I get on my screen is "the current image(boot/recovery) have been destroyed and cannot boot"
This screen repeats and I cn't do anything, not able to find any good tool or something to flash stock rom again...Please help am alrady dead
Dude, you just should flashing original/stock boot.img and recovery.img. And your phone already fixed.
Jus flash vbmeta and than flash twrp again . It will work fine and you won't get erro
Flash vbmeta
where did you got the file?
I have the same problem. Also cant flash vbmeta because the phone cant go into fastboot/recovery mode. It seems the only option is to flash it in edl mode and haven't found a tool that can do that
orl4nd said:
where did you got the file?
Click to expand...
Click to collapse
I found one in the pixel rom thread, it worked fine for me when i had this issue flashing candy rom
Ragzone said:
I have the same problem. Also cant flash vbmeta because the phone cant go into fastboot/recovery mode. It seems the only option is to flash it in edl mode and haven't found a tool that can do that
Click to expand...
Click to collapse
You have to flash the boot.img via adb to boot into Fastboot or Recovery.
Stuck at same problem.
I am also facing same problem. I can't open fastboot and the phone reboots to stock recovery after some time. Please help.
same problem for me
Ragzone said:
I have the same problem. Also cant flash vbmeta because the phone cant go into fastboot/recovery mode. It seems the only option is to flash it in edl mode and haven't found a tool that can do that
Click to expand...
Click to collapse
i have the same problem exactly. no access to adb commands nor recovery. please let me know if you could find a solution.
reza14 said:
i have the same problem exactly. no access to adb commands nor recovery. please let me know if you could find a solution.
Click to expand...
Click to collapse
I will keep trying the different flashing tools. Also let me know if you are succesful.
RMX1901CH unbirick
RMX1901CH
I was in the same state but unbirick.
When the power is off Press the volume minus and the power simultaneously.
If you are in fastboot mode
1.adb flashing command // fastboot flash recovery twrp-3.3.1-24- RMX1901-mauronofrio.img
2. after starting TWRP - connected with otg usb memory (StockROM.ozip)
3. USBOTG to mount
4.wipe dalvik / ARTCache & cache & system & data
* 5. INSTALL StockROM
* RMX1901_11_OTA_0190_all_fSt4F56aQlqf.ozip (China) A19
I haven't tried with older versions
The international version will show an inappropriate error, and it may be possible with the same language model
* 6. reboot
Japanese who cannot speak English
I did this way
Is this problem Solve? i face the same problem. what can i do?
Hatzey said:
I unlocked bootloader of my phone, flashed TWRP then installed new ROM and then tried to boot bt the only thing I get on my screen is "the current image(boot/recovery) have been destroyed and cannot boot"
This screen repeats and I cn't do anything, not able to find any good tool or something to flash stock rom again...Please help am alrady dead
Click to expand...
Click to collapse
Please help me.
same issue , can't do anything
the only way I found is , to know this user and pass in this tool so that I could test the firmware and post this here
Такая же проблема, помогите!!!
Long press volume down and power button , the phone will boot into fastboot mode. Flash vbmeta with disable verity command . It worked for me. No need do anything else.
volume down and power button for 10 sec
then flash stock recovery
then wipe data from stock rocovery
then back to bootloader and flash twrp recovery
then transfer stock rom zip on device
install it
done
Man i have the same problem, did you find any solution?
I already downloaded the qualcomm flash image loader, the pc detects the phone only when i press volume + and volume - and connect it, so i know i can do something, im gonna try with the EDL mode, any advance i'll let you know
how to do Flash vbmeta with disable verity command ???
I have trying to flash my a2 lite and its showing an error how to solve this problem
error:Writing 'sec'
FAILED (remote: 'flash write failure')
Click to expand...
Click to collapse
https://drive.google.com/file/d/1mQNqBXRBm-NkZJDHJHTJwT2w6XVCh-hO/view?usp=sharing
Try to flash it from fastboot
Jemon Temon said:
I have trying to flash my a2 lite and its showing an error how to solve this problem
https://drive.google.com/file/d/1mQNqBXRBm-NkZJDHJHTJwT2w6XVCh-hO/view?usp=sharing
Click to expand...
Click to collapse
In my own case, i have neva been able to flash my A2Lite in fastboot mode. I usually have to go into "EDL mode* first, den its a breeze.
While in fastboot mode, connect to d computer & in cmd window type in: fastboot oem edl
Go back to miflash, refresh & start d flash
Divolka said:
Try to flash it from fastboot
Click to expand...
Click to collapse
i tried fastboot and edl both but not worked for me.
agbadino said:
In my own case, i have neva been able to flash my A2Lite in fastboot mode. I usually have to go into "EDL mode* first, den its a breeze.
While in fastboot mode, connect to d computer & in cmd window type in: fastboot oem edl
Go back to miflash, refresh & start d flash
Click to expand...
Click to collapse
I tried fastboot and edl both but not worked for me
I thing its a critical problem.
Any other idea ?
If you can't flash the partition, there may be some kind of low-level damage...
Can you try erasing the partition before flashing it?
Eg. Something like this
fastboot erase sec
fastboot flash sec sec.img
I recall this helping people with another partition...
Jemon Temon said:
I tried fastboot and edl both but not worked for me
I thing its a critical problem.
Any other idea ?
Click to expand...
Click to collapse
An idea dat comes to mind.
1. Try downloading the latest twrp boot.img, offain or deestroy. (Personally i use "deestroy version")
2. Den in fastboot mode, boot into that trwp. Using:
fastboot boot twrp-file.img here u use d name of d twrp file as u have it, not as i put it.
3. While in twrp, go thru Wipe option. Now instead of just using "Factory Reset Swipe" read down...
4. Use the Advanced Wipe option.
5. Select d individual options & use d *Repair/Change File System (do each one individually, from top to bottom)
6. Using the *Repair File System option invariably restores each individual partition to its "default state".
I hav used dis steps b4, altho not with d problem u hav. If all goes well as i hope it shd, u shd be able to go back to fastboot, den use Edl mode & reinstall ur chosen rom via miflash.
Note: if u still have twrp as ur recovery, skip steps 1 & 2. Goodluck
Hello,
I am sorry to bother you with this stupidity but i soft bricked (stuck in fastboot) my Realme GT Master Edition (RMX3363GDPR).
The phone is unlocked but i am unfamilear with flashing this phone and it's partition system.
Anyone can help me? I tried flashing with RealmeOppo flash tool but it or hangs or tells me it's succeeded but it's clearly not. It stays on fastboot mode.
Thanks in advance
pieterrees said:
Hello,
I am sorry to bother you with this stupidity but i soft bricked (stuck in fastboot) my Realme GT Master Edition (RMX3363GDPR).
The phone is unlocked but i am unfamilear with flashing this phone and it's partition system.
Anyone can help me? I tried flashing with RealmeOppo flash tool but it or hangs or tells me it's succeeded but it's clearly not. It stays on fastboot mode.
Thanks in advance
Click to expand...
Click to collapse
https://sourceforge.net/projects/nippongsi/files/Pixel%20-%20Pixel5-Tiramisu-Beta2.1%20-%20KAVHT4FFWN/Pixel5-Tiramisu-Beta2.1-AB-Tiramisu-20220527-NipponGSI.img.gz/download
extract the .gz to become a .img, with 7zip or whatever,then rename it to system.img, put to c drive not under any folder, then execute fastboot command:
fastboot flash system C:\system.img
if fail then replace with
fastboot flash system_a C:\system.img
and
fastboot flash system_b C:\system.img
then
fastboot -w
fastboot reboot
if you are really lucky it will boot up into system
do at your own risk
Thank for your reply. How is Pixel5 firmware compatible with Realme GT Master Edition?
NVM, fixed it already.
pieterrees said:
Thank for your reply. How is Pixel5 firmware compatible with Realme GT Master Edition?
Click to expand...
Click to collapse
ported (added compatibility) for generic android 9 or higher devices
pieterrees said:
NVM, fixed it already.
Click to expand...
Click to collapse
glad you fixed it
LR7875 said:
https://sourceforge.net/projects/nippongsi/files/Pixel%20-%20Pixel5-Tiramisu-Beta2.1%20-%20KAVHT4FFWN/Pixel5-Tiramisu-Beta2.1-AB-Tiramisu-20220527-NipponGSI.img.gz/download
extract the .gz to become a .img, with 7zip or whatever,then rename it to system.img, put to c drive not under any folder, then execute fastboot command:
fastboot flash system C:\system.img
if fail then replace with
fastboot flash system_a C:\system.img
and
fastboot flash system_b C:\system.img
then
fastboot -w
fastboot reboot
if you are really lucky it will boot up into system
do at your own risk
Click to expand...
Click to collapse
I did all that on the phone but the phone is on fastboot ????????? What is the solution please?
nighetspy said:
I did all that on the phone but the phone is on fastboot ????????? What is the solution please?
Click to expand...
Click to collapse
Fastboot does not properly recognize your device?
Try fastboot reboot fastboot before executing the commands
LR7875 said:
Fastboot does not properly recognize your device?
Try fastboot reboot fastboot before executing the commands
Click to expand...
Click to collapse
(remote: 'Partition not found') fastboot error please help me
nighetspy said:
(remote: 'Partition not found') fastboot error please help me
Click to expand...
Click to collapse
Tried system, system_a and system_b?
LR7875 said:
Tried system, system_a and system_b?
Click to expand...
Click to collapse
yes The problem is still there
nighetspy said:
yes The problem is still there
Click to expand...
Click to collapse
GSI on Super Partitions
I want so much to install GSI, but when I was going to flash I saw that my device "doesn't have System" Partition. It's called Super Partition there. Does anyone knows how can I install it? I tried some video tutorials, but it always get an Error...
forum.xda-developers.com
LR7875 said:
GSI on Super Partitions
I want so much to install GSI, but when I was going to flash I saw that my device "doesn't have System" Partition. It's called Super Partition there. Does anyone knows how can I install it? I tried some video tutorials, but it always get an Error...
forum.xda-developers.com
Click to expand...
Click to collapse
fastboot flash <PARTITION> <FILENAME>. ......... Nothing new
pieterrees said:
NVM, fixed it already.
Click to expand...
Click to collapse
Could you please tell me how you fixed it, dealing with the same issue
battus said:
Could you please tell me how you fixed it, dealing with the same issue
Click to expand...
Click to collapse
I also want to know how this problem was solved
Allright,
I had a GDPR version of the firmware. I soft bricked my phone by accident. Then I flashed
Code:
RMX3363export_11_A.04_2021080317040000.ofp
and then it was an export version.
I found other ofp's but they didn't work (alltough for me..)
After i successfully flashed my phone i had update issues so i flashed
Code:
RMX3363export_11_A.09_2021122118530211.ofp
This works and a couple of hours later i even get the Realme UI 3.0 update. (this was my goal before i bricked my phone )
I used this tool:
Code:
OppoRealme-OFP-Flash
Beware, if you flashed your phone and it does not work, try changing your Slot in Fastboot.
If you don't have the correct slot (or the new software is flashed onanother slot, it will keep rebooting to fastboot)
I hope my explanation helps. I was desperate and spent three days fixing my phone. When i succeeded i tried to flash the same file from my laptop. This didn't work.I don't know why.
Good luck
pieterrees said:
Allright,
I had a GDPR version of the firmware. I soft bricked my phone by accident. Then I flashed
Code:
RMX3363export_11_A.04_2021080317040000.ofp
and then it was an export version.
I found other ofp's but they didn't work (alltough for me..)
After i successfully flashed my phone i had update issues so i flashed
Code:
RMX3363export_11_A.09_2021122118530211.ofp
This works and a couple of hours later i even get the Realme UI 3.0 update. (this was my goal before i bricked my phone )
I used this tool:
Code:
OppoRealme-OFP-Flash
Beware, if you flashed your phone and it does not work, try changing your Slot in Fastboot.
If you don't have the correct slot (or the new software is flashed onanother slot, it will keep rebooting to fastboot)
I hope my explanation helps. I was desperate and spent three days fixing my phone. When i succeeded i tried to flash the same file from my laptop. This didn't work.I don't know why.
Good luck
Click to expand...
Click to collapse
How long does it take to flash after this? fastboot --set-active=a ؟؟؟؟؟؟؟؟؟؟؟
I just flashed the ofp, after that i tried to reboot.
Then it didn't work and the device booted back into fastboot. After that I did
Code:
fastboot --set-active=other
and after that
Code:
fastboot reboot
and then it worked.
Maybe a vague tip: when you flashed it correctly and you are on the wrong slot it takes longer to boot into fastboot then when your device is bricked. Then you can change slots and (for me) that did the trick.
Good luck
How long does it take for this to end?
fastboot --set-active=other ؟؟
؟؟
a couple of seconds. When it takes forever try rebooting fastboot and try changing slots again or flash again (on another computer).
pieterrees said:
a couple of seconds. When it takes forever try rebooting fastboot and try changing slots again or flash again (on another computer).
Click to expand...
Click to collapse
What region is your phone used ؟
It works fine with you? RMX3363_11_A.09_2021122118530211.ofp ؟؟