Filed downgrade LeEco Le Max 2 x820 - Upgrading, Modifying and Unlocking

Please help me. I downgrade my x820 becouse in newest firmware can't instal TWRP. Upgrade to 14s complete but stack on boot screen and reset. How can I recovery software? I use data reset but still loop. (Sory for my english)
EDIT
I use fastboot tool to erase data and now working fine. Can delete this post.

rzapsko said:
Please help me. I downgrade my x820 becouse in newest firmware can't instal TWRP. Upgrade to 14s complete but stack on boot screen and reset. How can I recovery software? I use data reset but still loop. (Sory for my english)
EDIT
I use fastboot tool to erase data and now working fine. Can delete this post.
Click to expand...
Click to collapse
Hi- it happened to me too...do you mind posting how did you use the "fastboot tool" to erase data? also any download sites fo the fastboot tool? thanks alot!

http://revolutionlemax2.blogspot.com/2016/07/twrp-302-para-nueva-stock-rom-eui-5815s.html
Just connect phone in fastboot mode (power and vol-) to pc and type in cmd (command line must be in correct directory) fastboot -w

Elkgrove9449 said:
Hi- it happened to me too...do you mind posting how did you use the "fastboot tool" to erase data? also any download sites fo the fastboot tool? thanks alot!
Click to expand...
Click to collapse
Thanks I'll try it next time... I fixed mine after days of googling fastboot command... The trick with the Indian 5.8 ROM is to erase recovery first using "fastboot erase recovery".. Then install twrp using "fastboot flash recovery twrpxxxxx.IMG".... But thanks anyways... Best regards

Related

Twrp problem

Hello everyone here I have an error has 7 install any custom rom and I'm stuck on the logo 1+ it does not restart even with backup thank you for your help
can you boot into fastboot?
if yes, restore backup and erase userdata.
and try to flash twrp again (or another version)
washichi said:
can you boot into fastboot?
if yes, restore backup and erase userdata.
and try to flash twrp again (or another version)
Click to expand...
Click to collapse
Hello yes I have access to fastboot command but what type?
I have more backup my phone on my pc but yes
So how?
jejemc said:
Hello yes I have access to fastboot command but what type?
I have more backup my phone on my pc but yes
So how?
Click to expand...
Click to collapse
just use google "fastboot how to erase userdata"
make sure you are booted into fastboot and connected to pc, type in adb:
"fastboot erase userdata"
then reboot ("fastboot reboot")
washichi said:
just use google "fastboot how to erase userdata"
Click to expand...
Click to collapse
resolved
jejemc said:
resolved
Click to expand...
Click to collapse
did you erase userdata or what?
please post the solution for other people with the same problem...
washichi said:
did you erase userdata or what?
please post the solution for other people with the same problem...
Click to expand...
Click to collapse
Hello user data while not reflash rom stock, today and always error 7 or a custom rom to flash

my zen faild google verification to boot up

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

Help needed to Unbrick

Hi,
I own an Honor 7X (BND-L21) European variant. I was on Oreo Beta firmware BND-L21C432B302(432log) version.
I wanted to update to stable oreo firmware following this guide by @mrmazak
But unfortunately while in twrp, it wasn't responding to my volume down button click & auto aborted (as stated in the linked thread)
So I reboot the phone & suddenly it went into stock recovery & started to update. But at 5% it failed & from then, I'm unable to flash anything.
Tried rebooting & booting into TWRP, but TWRP doesn't exist anymore & boots into erecovery or stock recovery.
Phone doesn't goes beyond Huawei logo.
Tried flashing Oreo TWRP but it fails. tried flashing stock OREO recovery from update.zip, fails.
Tried both fastboot flash recovery & fastboot flash recovery-ramdisk command
My device detail is as below
fastboot oem get-product-model : BND-L21
fastboot getvar vendorcountry : hw/eu
fastboot oem get-build-number : BND-L21 8.0.0.302(C432log)
fastboot getvar rescue_enter_recovery : getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION : BND-L21C432B102CUSTC432D001
The firmware I tried was BND-L21C432B330CUSTC432D2
Any kind of help is appreciated.
Cheers.
mumith3 said:
Hi,
I own an Honor 7X (BND-L21) European variant. I was on Oreo Beta firmware BND-L21C432B302(432log) version.
I wanted to update to stable oreo firmware following this guide by @mrmazak
But unfortunately while in twrp, it wasn't responding to my volume down button click & auto aborted (as stated in the linked thread)
So I reboot the phone & suddenly it went into stock recovery & started to update. But at 5% it failed & from then, I'm unable to flash anything.
Tried rebooting & booting into TWRP, but TWRP doesn't exist anymore & boots into erecovery or stock recovery.
Phone doesn't goes beyond Huawei logo.
Tried flashing Oreo TWRP but it fails. tried flashing stock OREO recovery from update.zip, fails.
Tried both fastboot flash recovery & fastboot flash recovery-ramdisk command
My device detail is as below
fastboot oem get-product-model : BND-L21
fastboot getvar vendorcountry : hw/eu
fastboot oem get-build-number : BND-L21 8.0.0.302(C432log)
fastboot getvar rescue_enter_recovery : getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION : BND-L21C432B102CUSTC432D001
The firmware I tried was BND-L21C432B330CUSTC432D2
Any kind of help is appreciated.
Cheers.
Click to expand...
Click to collapse
Re failing at 5% suggests to me that one of the three file was not found.
Not able to fastboot flash never happened to me.
The not booting happened to me after flashing different region firmware. And factory resetting with recovery including format cache got it to boot.
Is you bootloader unlocked. Still?
mrmazak said:
Re failing at 5% suggests to me that one of the three files was not found.
Not able to fastboot flash never happened to me.
The not booting happened to me after flashing different region firmware. And factory resetting with recovery including format cache got it to boot.
Is your bootloader unlocked? Still?
Click to expand...
Click to collapse
all 3 files were perfectly there in "HWOTA8" folder in external SD
Bootloader & FRP both unlocked still.
Firmware region is same. I matched it thoroughly.
I don't know why fastboot can't flash recovery anymore
right now, I tried to fastboot flash system with aosp GSI img. it worked... then again extracted system.img from update.app .... again bootloop.
but still the same problem with fastboot flash recovery.... can't flash recovery.
Any advice?
mumith3 said:
all 3 files were perfectly there in "HWOTA8" folder in external SD
Bootloader & FRP both unlocked still.
Firmware region is same. I matched it thoroughly.
I don't know why fastboot can't flash recovery anymore
right now, I tried to fastboot flash system with aosp GSI img. it worked... then again extracted system.img from update.app .... again bootloop.
but still the same problem with fastboot flash recovery.... can't flash recovery.
Any advice?
Click to expand...
Click to collapse
What command Are you using to flash recovery?
Code:
fastboot flash recovery_ramdisk twrp-filename.img
mrmazak said:
What command Are you using to flash recovery?
Code:
fastboot flash recovery_ramdisk twrp-filename.img
Click to expand...
Click to collapse
Sir, I tried with the RECOVERY_RAMDIS.img in your AFH .... It worked !!!! how???
Edit
Funnily, fastboot flash recovery-ramdisk works in powershell.... doesn't work with CMD..... !!!! What in the world is happening?
edit
Sir @mrmazak can not boot into fastboot anymore.... doesn't get past after stock recovery !!! any advices?
mumith3 said:
Sir, I tried with the RECOVERY_RAMDIS.img in your AFH .... It worked !!!! how???
Edit
Funnily, fastboot flash recovery-ramdisk works in powershell.... doesn't work with CMD..... !!!! What in the world is happening?
edit
Sir @mrmazak can not boot into fastboot anymore.... doesn't get past after stock recovery !!! any advices?
Click to expand...
Click to collapse
Really don't know what you are doing, it is not recovery-ramdisk It is recovery_ramdisk
Under score not dash
mrmazak said:
Really don't know what you are doing, it is not recovery-ramdisk It is recovery_ramdisk
Under score not dash
Click to expand...
Click to collapse
it was a typo in forum.... !!! :cyclops: got into fastboot.
Sir, when I install hwota8_update-auto-rename, I need to press volume down at the end of the script, roght? but my volume down button press is not being detected.... should I try the commands from directly inside TWRP terminal?
& if you don't mind, can I have your whatsapp/telegram nmbr in PM? I'm really trying to fix my phone :crying:
Current situation,
TWRP installed,
Fastboot accessible
doesn't go past huawei splash logo/twrp
Edit
Manual Flashing through TWRP terminal worked.... currently on OREO Stable
mumith3 said:
it was a typo in forum.... !!! :cyclops: got into fastboot.
Sir, when I install hwota8_update-auto-rename, I need to press volume down at the end of the script, roght? but my volume down button press is not being detected.... should I try the commands from directly inside TWRP terminal?
& if you don't mind, can I have your whatsapp/telegram nmbr in PM? I'm really trying to fix my phone :crying:
Current situation,
TWRP installed,
Fastboot accessible
doesn't go past huawei splash logo/twrp
Edit
Manual Flashing through TWRP terminal worked.... currently on OREO Stable
Click to expand...
Click to collapse
I need to look at that code I'm using, that looks for the buttons. It works sometimes and not others.
Manual reboot to recovery should have worked also. Bit good that you are back going again
edit:
updated the hwota8_update-auto-rename.zip , removed the volume button check and leave it for the user to do a reboot recovery from menu. (made this way , to be able to cancel the update for whatever reason , might arise.)
mrmazak said:
I need to look at that code I'm using, that looks for the buttons. It works sometimes and not others.
Manual reboot to recovery should have worked also. Bit good that you are back going again
edit:
updated the hwota8_update-auto-rename.zip , removed the volume button check and leave it for the user to do a reboot recovery from menu. (made this way , to be able to cancel the update for whatever reason , might arise.)
Click to expand...
Click to collapse
Thanks for all the help Sir ?
P.S. Oreo stable is pretty damn good so far.

Soft bricked, need help.

Hi guys, in short, I wanted to install the latest xiaomi.eu MIUI 12.5 beta on a Mi 10T Pro, european version.
What I did was: unlocked bootloader, flash latest TWRP 3.5 beta version, I think I booted the device normally after this...
Then went back to TWRP and flashed the Zip file right away, don't know what I wiped after the install.
All in all the device won't boot now, I'm stuck to either twrp or fastboot.
Problem is I cant flash a fastboot stock rom, says it's successful but the flashing process is like 2 seconds, i can't copy a recovery rom to the internal storage, i think Data partition got corrupted.
Can't wipe Data partition, there is a FBE decription error, and says unsupporter file system auto.
Does anyone have any idea what can I try.
Already tried to change Data file system to ext2 then back to ext4 but no luck.
PC recognizes the phone as a media device, I can see the Internal storage icon, but can't see any files nor can I copy anything to it.
Tried flashing the stock rom with mi flash tool and with command prompt too.
Any advice is welcome.
WSSRoach said:
Hi guys, in short, I wanted to install the latest xiaomi.eu MIUI 12.5 beta on a Mi 10T Pro, european version.
What I did was: unlocked bootloader, flash latest TWRP 3.5 beta version, I think I booted the device normally after this...
Then went back to TWRP and flashed the Zip file right away, don't know what I wiped after the install.
All in all the device won't boot now, I'm stuck to either twrp or fastboot.
Problem is I cant flash a fastboot stock rom, says it's successful but the flashing process is like 2 seconds, i can't copy a recovery rom to the internal storage, i think Data partition got corrupted.
Can't wipe Data partition, there is a FBE decription error, and says unsupporter file system auto.
Does anyone have any idea what can I try.
Already tried to change Data file system to ext2 then back to ext4 but no luck.
PC recognizes the phone as a media device, I can see the Internal storage icon, but can't see any files nor can I copy anything to it.
Tried flashing the stock rom with mi flash tool and with command prompt too.
Any advice is welcome.
Click to expand...
Click to collapse
LOG IN IN MI FLASH
jjgvv said:
LOG IN IN MI FLASH
Click to expand...
Click to collapse
What do you mean?
how do you flash stock rom 2 secs?
jjgvv said:
how do you flash stock rom 2 secs?
Click to expand...
Click to collapse
I think it doesn't fully flash, says it's successful but nothing really happens.
use what flash tool?
jjgvv said:
use what flash tool?
Click to expand...
Click to collapse
Tried latest from xiaomis website but that gives error, so i tried to download one from another website, says its latest version too
have you log in in that flash tool?
jjgvv said:
have you log in in that flash tool?
Click to expand...
Click to collapse
There is no way to log in, aren't you talking about the mi unlock tool?
mi flash?
jjgvv said:
mi flash?
Click to expand...
Click to collapse
Yes, there is no option to log in to mi flash tool
fastboot erase data then
jjgvv said:
fastboot erase data then
Click to expand...
Click to collapse
How do i do that?
WSSRoach said:
How do i do that?
Click to expand...
Click to collapse
go into fastboot and Type fastboot erase data in the fastboot cmd prompt
jjgvv said:
go into fastboot and Type fastboot erase data in the fastboot cmd prompt
Click to expand...
Click to collapse
Will try as soon as i get near a PC
jjgvv said:
go into fastboot and Type fastboot erase data in the fastboot cmd prompt
Click to expand...
Click to collapse
Sadly it fails
WSSRoach said:
Sadly it fails
Click to expand...
Click to collapse
how does it fail
jjgvv said:
how does it fail
Click to expand...
Click to collapse
I typed fastboot erase data, i get: FAILED (remote: Check device console)
Code:
fastboot -w
or
Code:
fastboot erase userdata
is the correct command. Now, if this fails, find lr-twrp, flash that, reboot, wipe data, and try again... And you have to do fastboot commands from fastboot, not from twrp...
calinorg said:
Code:
fastboot -w
or
Code:
fastboot erase userdata
is the correct command. Now, if this fails, find lr-twrp, flash that, reboot, wipe data, and try again... And you have to do fastboot commands from fastboot, not from twrp...
Click to expand...
Click to collapse
this looks like it worked, still now says unable to mount storage when trying to format data from twrp, but thats a step ahead...now it says in yellow )
I have an idea to flash lineage os recovery with fastboot, might that work?

Question Soft brick RMX3363GDPR

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 ؟؟

Categories

Resources