LAF NUKER flashable zip - G2 General

LAF NUKER wipes your Download mode and let you use Fastboot instead.:
Do this on your own responsibility, if you bricked your phone in some weird way then don't look at me.
But with this simple thing you can't brick your phone only if you flashed the wrong zip which wasn't from me.
This is more meant for developers/testers.
Click to expand...
Click to collapse
I was getting irritated that my Fastboot mode dissapeared everytime when I flashed some lollipop stock based rom as those all included bootloader files, so I had to first attempt to get into the rom itself or recovery to wipe it again over and over. So I thought by myself why won't I make something easy and flashable?
This lightweight flashable zip from 2-4KB is tested by me multiple times so after you flashed it I HIGHLYsuggest that you need to test or you can enter download mode and see if it shows now fastboot. If so then everything succeeded like it should, it has an succes rate of 100% as nothing could actually go wrong with this.
This script/method should also work for the G3 and some other LG devices which have this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/laf
For the one's who care the shell script is located in the update-binary, updater-script is just dummy.
If you want to revert back, just flash the jb/kk/lp bootloader files.
Download:
https://docs.google.com/uc?authuser=0&id=0B1u3mnq0nstfZVN1eVQ3bEw5ODQ&export=download
Mirror:
https://www.androidfilehost.com/?fid=23991606952610950
Credits:
Jackpotclavin for the method to get into fastboot mode
Chainfire for the shell updater-script method
osm0sis for the guide about the shell updater-script

Be careful maybe we can't use fastboot to flash it stuck.

somboons said:
Be careful maybe we can't use fastboot to flash it stuck.
Click to expand...
Click to collapse
I experienced once already when it was stuck, recovery kinda screwed up and modified stock rom didn't wanted to boot anymore and I just flashed a new recovery through fastboot mode and it worked properly. I am also still flashing test kernels through fastboot as I am used to that coming from the Nexus family.
This is also more meant for the real flashaholics and or developers as I experienced many times already on my G2 that download mode didn't worked after flashing several stock roms. So this is especially for the people who also face the same issue as me with download mode and who wants to have an backup if something would go wrong. Maybe I could also make later something like savoca made with autoboot but then on the download mode partition with option to boot into download mode or fastboot. But that would probably take some time to make it and I am not sure whats the size of the other available partitions.

Fastboot supports kdz files? As I use Google Nexus, Fastboot supports img files. So how are we gonna flash kdz files when we use Fastboot?

But you can extract files from kdz. And flash them on fastboot.

yes @ceza1380 just like kimitza said you have to extract the images but I am not sure or you are able to flash all the images through fastboot. What you could do is flash with fastboot recovery and download a flashable stock rom or just the bootloader files and flash it through the recovery.

Related

[Q] Stuck On Sony Screen

I have the castor windy version 16gb SGP511. I was previously rooted but not unlocked. I unlocked the boot loader. Installed the twrp image on the pac man thread which i think was dual recovery cause Philz,Cwm came out, so I can install lollipop version of the rom. Made a backup of the stock rom. Followed this instructions - Install the Lollipop ROM + GApps+SuperSU using whatever Recovery you have.
- Turn off device completely.
- Press <Volume Up> and plug USB cable.
- LED should turn blue.
- Send command: "fastboot erase recovery"
- Send command for Castor_Windy: "fastboot flash recovery TWRP_Castor_Windy.img"
- Send command for Castor: "fastboot flash recovery TWRP_Castor.img"
- Unplug USB cable.
- Device will reboot.
- When LED turns pink press <Volume Up> and <Volume Down> several times.
- You should now see TWRP
I wasnt fast enough so stock rom booted. I used Adb reboot recovery to access recovery and did as the above mentioned. Wiped i tried to install the rom which failed. Rebooted back to system and got stuck in Sony boot up screen. I can access fastboot. Read though the forums I have to find a ftf or a system image file and use a flash tool. What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Kamaleon said:
What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Click to expand...
Click to collapse
Try this Xperia downloader tool. Should let you see which versions are which. If you want an easy root, then stay away from the KitKat builds, unless you want to unlock bootloader.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Use Flashtool to flash your downloaded ftf file. Just make sure your device is charged.
http://forum.xda-developers.com/showthread.php?t=2335555
I believe flashtool will even install the drivers for your 511
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Kamaleon said:
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Click to expand...
Click to collapse
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Moscow Desire said:
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Click to expand...
Click to collapse
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Kamaleon said:
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Click to expand...
Click to collapse
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Moscow Desire said:
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Click to expand...
Click to collapse
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Kamaleon said:
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Click to expand...
Click to collapse
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Moscow Desire said:
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Click to expand...
Click to collapse
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Kamaleon said:
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Click to expand...
Click to collapse
Well, I'm not sure which route to take.
However, I will tell you what I have learned the other day.
I have the 521 with unlocked bootloader. Rooted with my own boot.img, flashed SuperSU using "flashboot boot recovery.img" (yeah, sometimes it doesn't show on the display, so it takes a few times).
Now, other day I was going to check out the new LyPop pre-rooted. Fastboot flash recovery recovery,img, and it won't boot it to recovery like it should. Like it's not flashed. Tried it a couple times. Now, I didn't install the dual recovery as I'm not sure how that kernel (boot.img) will interact with my current tabs OS. Not to mention I need it for my work until tomorrow. But strangely it sounds like the same issue you have.
This weekend I will investigate it. As for me, I will probably flash the Stock ftf lyPop build, and just root it using a modified boot.img.
One thing I do know, is flashing a custom recovery to the "recovery" partition, doesn't seem to work like it used to work on other devices. It seems the flashing to the "Fota kernel" partition seems to be the only method that works. This is what happens when you flash that dual recovery, or any recovery that has a boot image using "Fota". Probably explains why you can't get rid of it using "fastboot erase recovery". because it's erasing the wrong partition. Only flashing a full ftf gets rid of it, because the ftf has a new FotaKernel it flashes.
Eh, something like that. Will look at it this weekend.

Can't get onto latest TWRP

So I am stuck on TWRP 2.7.1.0 and i am running slimrom 4.4.4 on a c6833 and the reason for this is because it's the only thing that will boot on my phone. There was some intense trial and error a few months ago and a few days with a bricked phone but I finally got it running again, and I am nervous about messing things up again.
I am wanting to move to a more up to date ROM either scrubber port 5.1 or remix 5.1.1, but they both ask for updated TWRP to install. And I can't update TWRP using the TWRP tool from the store. It downloads but when it tries to install it says there is a problem. Previously, trying to update TWRP would result in SONY bootloops. I was about to try the dd method but just wanted to make sure it was safe.
I am a bit of an idiot (I got rid of my encrypted keys on day 2 of owning the phone) so any help would be appreciated.
Thanks!
walkingagh said:
...
Click to expand...
Click to collapse
The easiest way is to use Rashr. It should set everything up automatically. You may then reboot to recovery from the ROM, or by holding Vol- when the LED turns purple on boot-up.
If that doesn't work, for whatever reason, try dd or Flashtool. Using Flashtool, you can flash openrecovery-twrp-2.8.5.0-togari.img with the phone in Fastboot mode.
Let me know if you have any further questions!
Used Rashr...and now I can't get into recovery. I can still boot into my phone, but booting into recovery just fails with a yellow LED?
So Rashr still says I have 2.7.1.0 installed. :/
walkingagh said:
Used Rashr...and now I can't get into recovery. I can still boot into my phone, but booting into recovery just fails with a yellow LED?
Click to expand...
Click to collapse
Alright, you likely need a newer kernel first. Using Flashtool, you can flash this boot.img (newest AICP kernel) to the boot partition using the Fastboot mode (or use fastboot manually from the Flashtool/x10flasher_lib folder with "fastboot flash boot boot.img"). At this moment, you'll no longer be able to boot into the ROM, so make sure you've done all necessary backups and are ready to install a newer ROM. Then use Flashtool/Fastboot to flash the openrecovery-twrp-2.8.5.0-togari.img file to your recovery/FOTAKernel partition ("fastboot flash recovery openrecovery-twrp-2.8.5.0-togari.img"). You should be able to enter recovery now.
Awesome thanks! Will I need to do this each time I flash a ROM? Or can I just jump from something like scrubber to something else?
I know this is an old thread but is that the boot image I need to run TWRP 3? If so, can I do this via dd?
Triflot said:
Alright, you likely need a newer kernel first. Using Flashtool, you can flash this boot.img (newest AICP kernel) to the boot partition using the Fastboot mode (or use fastboot manually from the Flashtool/x10flasher_lib folder with "fastboot flash boot boot.img"). At this moment, you'll no longer be able to boot into the ROM, so make sure you've done all necessary backups and are ready to install a newer ROM. Then use Flashtool/Fastboot to flash the openrecovery-twrp-2.8.5.0-togari.img file to your recovery/FOTAKernel partition ("fastboot flash recovery openrecovery-twrp-2.8.5.0-togari.img"). You should be able to enter recovery now.
Click to expand...
Click to collapse
That file has expired, any chance you can re-post it?

Softbrick after twrp flash

Hi everyone,
I tried to install Lineage OS on my Xperia Tablet Z Wifi and followed the instructions here: https://wiki.lineageos.org/devices/pollux_windy/install
I am on Ubuntu and I did unlock the bootloader successfully. Then I tried to flash twrp but this is where things went wrong.
After entering
Code:
fastboot flash boot ./twrp-3.5.2_9-0-pollux_windy.img
the device did not start anymore. I can still enter fastboot mode and the device is recognized on the PC but else the only thing that happens is the LED blinking red.
Any ideas where to go from here are appreciated.
Rootk1t said:
you flashed recovery to boot. So only recovery exists in boot section.
Of course tablet won't boot afterwards, as there is not kernel.
Download custom rom you want to install, unpack boot.img from roms zip files and flash via "fastboot flash boot boot.img"
Afterwards enter recovery and flash custom rom zip, gapps or whatever you need.
Click to expand...
Click to collapse
I tried this but flashing the boot.img does not change anything unfortunately.
brickedmytablet said:
I tried this but flashing the boot.img does not change anything unfortunately.
Click to expand...
Click to collapse
You can reflash stock ROM via Flashtool v.0.9.18.6. or flash another boot.img to check if it boots or not.
Thank you, this worked for me.
Should have used the right twrp form the beginning. flash to boot works if it is the right version in my case scorpion_windy

Question I'm At A Loss, Please Help

I recently bought an unlocked Moto G Play 2021 with the intent of learning how to flash custom rom's etc. The steps I've done so far are below.
Went to Motorola's site and got the code to unlock the bootloader
Waited for the "OEM Unlock" button to be available in the Developer Options menu.
Followed the directions Here to try to get an unofficial version of TWRP installed.
when I type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img Using the vbmeta.img from the link above, I get some kind of anti-rollback error and can't boot to recovery.img
So far, what I've found says I need to be on Android 10 for this to work but I can't find a stock rom of Android 10 for this device. Electimon posts AOSP builds for this phone Here so I assume there's a way to get this to work, I just don't know what it is and I've gone through these threads a few times now and can't piece it together. Any assistance would be greatly appreciated.
Additionally, thanks Electimon for doing those AOSP builds.
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Luiz Vinicius said:
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Click to expand...
Click to collapse
I'm not sure entirely what happened, but after I used the TWRP app my phone bricked and I had to use the Lenovo rescue app on my pc to factory reset it.
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
svoc said:
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
Click to expand...
Click to collapse
Thank you for the response!
I made sure my phone was on wi-fi and checked for updates. I then rebooted to fastboot and flashed recovery to the MotoGuamnaFixed2.img. I still got a blank screen when I tried to reboot to recovery. I then rebooted to fastboot manually and did
fastboot flash recovery_a MotoGuamnaFixed2.img
fastboot flash recovery_b MotoGuamnaFixed2.img
It said ok both times, and when I try to reboot to recovery, I get a blank screen that I can't interact with. Pressing the power and volume buttons does nothing. Rebooting and letting the phone go through the boot process, to include waiting for the warning about the unlocked bootloader to go away results in a blank screen.
I also tried booting to fastboot and selecting "Recovery Mode" from the fastboot menu. Same result. That being said, I followed the instructions in the second link anyway, which are
fastboot -w
fastboot update (filename).zip
Now my phone has a blank screen I cannot interact with, but when I type "adb devices" I see the phone. Typing "adb shell ls -l" shows there is definitely a file structure there.
Just download the rom for the version that your device is unzip it and manual flash each one to the correct spot except recovery flash the twrp and then reboot and let me know look at flash file.xml to see where to flash each IMG and bin to make shur you download your rom and not another one for the same device but different carrier what it sounds like to me is happening is you downloaded the wrong ROM when you tried to do a force update
Send me a screenshot of your about device screen please I might need to make a change to a few things to get it working
I'm stuck in a boot loop right now. WIll the output from fastboot getvar work?
What carrier do you have
Download your rom first then follow my last post to get it back out of a bootloop
svoc said:
What carrier do you have
Click to expand...
Click to collapse
It's an unlocked phone, no carrier, no SIM. I did the factory reset with the Lenovo rescue tool and sent you the screen shot of the device info page.
Update - svoc has spent a crap ton of his personal time trying to help me with this. I've learned a bunch and wanted to publicly acknowledge his willingness to go way above and beyond trying to get this working.
I don't understand why I can't get twrp to boot I'm not for shut what the problem is if any one has any idea please let me and I will try
Big thanks to svoc for all the phone calls and troubleshooting my device, that is apparently possessed by at least 3 demons and a donkey. There are two links below. The first is the link to the intstructions that worked.
The second is to the compressed file that gave me a degoogled android. It's really, really basic and you'll have to side load the app store of your choice onto the device but it works.
*NOTE* I have not used a sim card or tested the cellular capability. If you do the things below and it doesn't work, reboot to bootloader and flash the radio.img with the one from your stock rom, which can be obtained from lolinet.
Any custom ROMs out there for Moto g play 2021 (guamna)?
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
forum.xda-developers.com
https://github.com/phhusson/treble_experimentations/releases/download/v412/system-squeak-arm64-ab-vanilla.img.xz

[SOLVED] Realme 5i stuck on fastboot after flashing custom ROM no recovery or OS

Yes, Im stuck. Im on realme 5i and I flashed PixelExperience+ with TWRP, clean flash, made sure to wipe data and clear cache before and after flashing. I rebooted and boom, stuck on fastboot/bootloader. I can't go back to recovery mode or to system, it just takes me back to fastboot/bootloader. I backed up my files btw.
Supposed fixes that did not work:
1: Fastboot erase boot && fastboot erase dtbo && fastboot erase recovery && fastboot erase vbmeta && fastboot erase system && fastboot erase userdata and fastboot flash recovery TWRP.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot reboot-bootloader.
- it brings me back to fastboot when I try to go to recovery mode.
2: Push volume down/up and power button.
- it brings me back to fastboot when I try to go to recovery mode. (2)
3: flash stock recovery (I can't go to recovery so I cant flash stock ROM too)
- it brings me back to fastboot when I try to go to recovery mode. (3)
What else do I do? Am I missing something from the fixes I've tried above?? I am in need of urgent help.
Update: I've tried realme flash tool, for stock ROM and it says cannot find central directory.
I've tried putting the ofp to AppData/Roaming/flashtool/temp as said from another thread. I've also tried running in administrator but none work. I've ran out of luck today, please help.
Phone: Realme 5i
Story: I had my phone get a custom recovery, TWRP. Got it rooted. Before I rooted it I rolledback to android 9, ColorOS, bw. Then decided why not use a custom ROM? So I did. PixelExperiencePlusEdition ANDROID 12. I flashed it with TWRP, factory reset and cleared cache, in other words, clean flash. I'm hopeless cause once I rebooted, I got sent to fastboot then when I tried to go to recovery mode, it sends me back to fastboot! What do I do? I need help. please.
Update: So maybe I am doing the 1st method wrong. I got all the img files wrong, cause I need them from my stock firmware right? So I tried programs to extract those img from their new.dat.br files right? I did and the extractors keep giving me something is missing, line this and that is incorrect or something like that. I'm really hopeless. Can someone give me the img files of RMX2030EX_11_OTA_0210_all_1hZhuZlgVC1t? system.img, boot.img, vendor.img, vbmeta.img, dtbo.img? What else am I missing to manually flash it?
I am facing the same issue as well, I had downloaded the RMX2030EX_11_C.75_210917_1b9832bb file and extracted using https://github.com/bkerler/oppo_decrypt but the first method still didn't work. was is the wrong file? or did the decryptor didn't work properly idk.
koarc lkas said:
Update: So maybe I am doing the 1st method wrong. I got all the img files wrong, cause I need them from my stock firmware right? So I tried programs to extract those img from their new.dat.br files right? I did and the extractors keep giving me something is missing, line this and that is incorrect or something like that. I'm really hopeless. Can someone give me the img files of RMX2030EX_11_OTA_0210_all_1hZhuZlgVC1t? system.img, boot.img, vendor.img, vbmeta.img, dtbo.img? What else am I missing to manually flash it?
Click to expand...
Click to collapse
I can't find a file on realme software page with this name where did you get the file? plus does your variant has Qualcomm or Mediatek CPU? I saw a video where it stated that this phone has two variants one with Qualcomm and other with Mediatek(Helio) CPU.
Edit: Do an MD5 check maybe your file got corrupt..
I managed to fix, you will need download these files from telegram. one of them should work for me the ColorOS file worked. Follow the instruction given in the readme file and that should do. I am installing DotOS now it showing the splash animation from last 5 minutes, if it works i'll update the comment or will provide further instructions to fix.
FastbootFix-Realme-5-5i-5s~RUI.zip
FastbootFix-Realme-5i~Color OS.zip
Edit: the reason it was taking so long to bootup and was stuck on splash animation is that I forgot to format (type yes).
yasir.r said:
I can't find a file on realme software page with this name where did you get the file? plus does your variant has Qualcomm or Mediatek CPU? I saw a video where it stated that this phone has two variants one with Qualcomm and other with Mediatek(Helio) CPU.
Edit: Do an MD5 check maybe your file got corrupt..
Click to expand...
Click to collapse
I got it from this:
This is what I used to rollback to android 9 cause another video said I had to do this first before rooting. It worked though then custom ROM happened and now phone's bricked. Hasn't been used ever since.
I'll do MD5 if your fix didn't work.
Hey um, Im a turtle and Im reading the .txt from the link you gave the color os one specifically. So Im at the step where I have to Double Click "Open This to Proceed" file to start the process. What is this "Open This to Proceed" exactly?
Edit: Never mind. I should've looked more before asking..
IT WORKED!!!!!!! THANK YOU SO MUCH! YOU'RE A LIFESAVER!
koarc lkas said:
IT WORKED!!!!!!! THANK YOU SO MUCH! YOU'RE A LIFESAVER!
Click to expand...
Click to collapse
Now if you want to flash the stock rom you will have to flash firmware first.
flash fw c.xx
wipe 5
flash rom
flash vbmeta disabler
format (type yes)
reboot
You can download the firmware file form here. https://github.com/realme-trinket-organization/firmware_files_RMX1911/releases and the vbmeta disabler from here. https://t.me/r5notes/52
yasir.r said:
Now if you want to flash the stock rom you will have to flash firmware first.
flash fw c.xx
wipe 5
flash rom
flash vbmeta disabler
format (type yes)
reboot
You can download the firmware file form here. https://github.com/realme-trinket-organization/firmware_files_RMX1911/releases and the vbmeta disabler from here. https://t.me/r5notes/52
Click to expand...
Click to collapse
!!! Im having a problem with flashing my stock rom cause it keeps getting bricked. Thank you so much for giving me this!
yasir.r said:
Now if you want to flash the stock rom you will have to flash firmware first.
flash fw c.xx
wipe 5
flash rom
flash vbmeta disabler
format (type yes)
reboot
You can download the firmware file form here. https://github.com/realme-trinket-organization/firmware_files_RMX1911/releases and the vbmeta disabler from here. https://t.me/r5notes/52
Click to expand...
Click to collapse
How do I know my exact build number? I just know that it's realme 5i and it is RMX2030, not those C69 thingies.
koarc lkas said:
How do I know my exact build number? I just know that it's realme 5i and it is RMX2030, not those C69 thingies.
Click to expand...
Click to collapse
I just used the latest version c.73 it worked. I do have to same phone. R5i, RMX2030 with SD665 CPU.
How do I flash the firmware I downloaded from your link? and the vbmeta disabler img is in the firmware-update file, correct?
koarc lkas said:
How do I flash the firmware I downloaded from your link? and the vbmeta disabler img is in the firmware-update file, correct?
Click to expand...
Click to collapse
no no not the image, vbmeta-disabler.zip from here https://t.me/r5notes/52 and flash them in pbrp like you flash the rom.
ohh both zip files, okay
yasir.r said:
no no not the image, vbmeta-disabler.zip from here https://t.me/r5notes/52 and flash them in pbrp like you flash the rom.
Click to expand...
Click to collapse
Upon flashing the firmware zip, my phone keeps getting stuck on bootloop, it doesnt even let me go to recovery mode. It keeps restarting too?
Edit: is this normal??
The tool you gave me to fix fastboot doesnt work anymore :<
koarc lkas said:
Upon flashing the firmware zip, my phone keeps getting stuck on bootloop, it doesnt even let me go to recovery mode. It keeps restarting too?
Edit: is this normal??
Click to expand...
Click to collapse
did you follow the process, properly?? don't tell you flashed just the firmware and nothing else..
yasir.r said:
did you follow the process, properly?? don't tell you flashed just the firmware and nothing else..
Click to expand...
Click to collapse
I only got to step one which you said to get firmware and flash it. I flashed it and my phone rebooted but it keeps restarting. I can still flash images but I cant seem to fix this "reboot loop" and the tool you gave doesnt fix it either. What Im guessing is C73 isnt my firmware version since this phone is years old? Do you know how to delete the firmware so maybe the tool you gave me would work again and I can start over once more?
Edit: Im once again stuck in fastboot btw.
Edit: I fixed the rebooting loop with the stock recovery.bat from the file you gave me but when I do the "open this to proceed" it goes back to rebooting automatically. I still want to remove the C73 firmware though.

Categories

Resources