Related
Hello everyone, I'm new here so sorry if I'm doing something wrong, I tried to search but couldn't find anything related to my problem!
I'm running in a little trouble trying to recover to my local factory firmware with SEUS since last friday, reading a lot of threads here and at other forums with no luck.
Hope someone could enlight me.
[EDIT to what is happening right know]
The history log:
- I update my U20a (1239-7686) mini pro with PC Companion as soon as I bought it to 2.1.1.A.0.6.
- Then I rooted, tried hundreds apps, removed other dozen with Titanium Backup installed JIT and then I had the "brilliant" to reset from the inside android menu wondering that my firmware will return fresh and clean, big mistake.
- After trying three different firmwares and versions (including downgrading to 1.6) with FlashTool 0.2.9.1 I finally found that with this one SEUS recognize my phone and repair it.
The problem is that when I edit build.prop to my factory CDF number, SEUS do not recognize it anymore. What am I doing wrong? Any clue??
just a thought...
Did you try force method?
Use seperated SE Update software not update from pccampanion.
Then when you have selected model etc etc enter in flash mode and let it finish with flashing ... works in 99% time..
what worked for me
I had about the same problem, but managed to sort it out with the Flash Tool.
Check if the latest firmware has been downloaded by the SE Updater Service to /Program Files/Sony Ericsson/Updater Service/db/. (check the size, there should be about 100+ MB in there).
If so, you can use the Flash Tool to :
1) decrypt the files in the .../db/12345678/ folder
2) build a package from the newly decrypted .sin files (the build package window will open right after the decryption), select all the .sin files, name the package and go
3) flash that package to your phone.
I hope this will work for you too.
Chumby_666 said:
Did you try force method?
Use seperated SE Update software not update from pccampanion.
Then when you have selected model etc etc enter in flash mode and let it finish with flashing ... works in 99% time..
Click to expand...
Click to collapse
I tried with PC Companion, and SE Update Service, both softwares available from SE website.
If you mean I should use SE Update Service, that's exactly the problem, it doesn't work. Otherwise I don't know what you mean about force method.
mkrzesin said:
I had about the same problem, but managed to sort it out with the Flash Tool.
Check if the latest firmware has been downloaded by the SE Updater Service to /Program Files/Sony Ericsson/Updater Service/db/. (check the size, there should be about 100+ MB in there).
If so, you can use the Flash Tool to :
1) decrypt the files in the .../db/12345678/ folder
2) build a package from the newly decrypted .sin files (the build package window will open right after the decryption), select all the .sin files, name the package and go
3) flash that package to your phone.
I hope this will work for you too.
Click to expand...
Click to collapse
I didn't try this because SE Updater stops right after I choose the Mini Pro, it tells me I have the lastest firmware no matter what firmware I've flashed, even 1.6. Just to be sure I'll check this when I go back home.
Try to change the custom revision number too inside the build.prop, it helped for me before. Eg from R4B to R3B.
Sent from my U20i using XDA Premium App
i got this problem too, now im stuck on the previous kernel and dont know what to do... but the SEUS file decryption sounds nice... ill give it a shot...
datagubben said:
Try to change the custom revision number too inside the build.prop, it helped for me before. Eg from R4B to R3B.
Sent from my U20i using XDA Premium App
Click to expand...
Click to collapse
Good idea, thks! Do you try a random value?
Introduction:
These are stock rom images of the various venue roms. Unlike the streak, the majority of roms on the venue have never been released as update.pkgs. Without update.pkgs it is not possible to fully restore a venue after bricking it.
The only exception is for korean users, so far 319 (which is a korean rom) is the only update available. Update.pkgs update everything: baseband and all the various firmwares.
These zips only contain the /system folder, the kernel, and the recovery image. It does not update any of the firmwares. If your baseband and your rom version do not match, you will get the 'blinking leds' issue. Which means the soft button leds will blink semi-constantly. The only way to fix this is by using a matching rom.
What this ultimately means is that anyone that updated to 319 cannot migrate away from it until another rom update is released, whenever that is.
These images/zips will allow you to unbrick your device if it was caused by modifying /system. If it was caused by someone not related it will not fix them.
Click to expand...
Click to collapse
WARNING:
Do not use if your device already works
Only install the one matching your baseband:
Look at Dell Venue - XDA wiki to find your matching version
Back up your data before attempting if possible
If you do not know how to use the command line, find a tutorial on google
Click to expand...
Click to collapse
Install Instructions:
(This assumes you already know how to use the command prompt on your PC)
Download Fastboot+ADB.zip and install it
Download the version matching your baseband:
101:
Dump not available
302:
stock-V302.zip [Cleaned dump]
303:
Dump not available
304:
stock-V304.zip [Cleaned dump]
307:
stock-V307.zip [Good dump]
319:
Not required - pkg is available
321:
stock-V321.zip [Good dump]
323:
Not required - pkg is available
324:
Dump not available
325:
Not required - pkg is available
Flash them with fastboot
fastboot flash boot <path to boot.img>
fastboot flash recovery <path to recovery.img>
fastboot flash system <path to system.img>
Factory reset your device
Click to expand...
Click to collapse
IF YOU BRICK AN ALREADY WORKING VENUE BECAUSE YOU WERE CURIOUS, IT IS YOUR OWN FAULT. DO NOT USE ON A WORKING DEVICE UNLESS YOU ALREADY KNOW HOW TO UNBRICK IT
Notes:
I am still missing dumps for:
101
303
324
Verified clean dumps of:
302
304
Do not link to the untested images, they will be repackaged as they are tested and the links will become invalid
stock zips are tested images, they are safe to link to
stock zips are packaged as nandroid updates. They will work fine with fastboot or nandroid (ignoring the fact a custom recovery is not yet available)
Click to expand...
Click to collapse
2char
I volunteered
bump, still looking for more testers
I'll give it a shot.
Would love to help, but I am a newb. And I have no programming type skills. I wish you guys luck. Would love to do some overclocking, and custom roms.... I miss my nexus s.
Just got my venue from Dell service center. I erased my system partition while I was experimenting with it.... and Dell guys fixed it by re-flashing it..... Plz upload your Rom, ill try it if something goes wrong ill go the service center.....
Sent from my Dell Venue using XDA App
This worked for me just now. I had bricked my venue by accidentally factory resetting, with the dell stage apk removed. I spent hours just trying to get the right person @ dell, long story. When it rebooted after a factory reset, I could unlock the phone, but the ui would not load. By trying to fix it throughout the day, I made it worse where it would only loop on the dell logo. I just figured out how to follow the instructions, posted above, and it booted back up with the stage ui MANY THANKS..
What baseband version do you have?
Under Baseband version it states:
GTOUB1A130730-US
Check Development Page, I Have Uploaded The Stock Dell Venue ROM Dumps.
Sent from my Dell Venue using XDA App
Added 304 now,
only missing 101/302/303/325 now
May be a stupid question, but can these stock images not be augmented to create a custom rom?
They can, but the lack of a custom recovery is a major obsticle to making custom roms. Though actually porting a custom recovery seems to be trivial in comparison to kernel mods.
To make a custom rom on the venue you just have to unpack, modify, and repack it. You cant do 'patches' as you need a custom recovery for update zips. Every mod would require downloading the entire rom or manually pushing the pieces with adb
I am guessing that you would need a good understanding of programming to modify these images? What is needed to unpack? Would like to look around and see if its something I can figure out.
If you're on windows just look for unyaffs.exe, I assume there's a similar util for *nix/osx.
To repack them I dont have a pc util to do it. I just flash it on my streak then make a nandroid. As I dont do this that often really I havnt bothered looking up for a tool to do this. I do believe there's a bundled tool to do this in linux (build a filesystem into an image).
Please step by step, how to repair Dell venue stop at Logo
TheManii said:
To make a custom rom on the venue you just have to unpack, modify, and repack it. You cant do 'patches' as you need a custom recovery for update zips. Every mod would require downloading the entire rom or manually pushing the pieces with adb
Click to expand...
Click to collapse
I have a new unlocked build number 13505 device that is defying all my efforts to root it. Can this method be used to force root access?
edit
Actually it finally rooted using SuperOneClickv1.5.4-ShortFuse, 4 hours yesterday and failure, first try today after posting and it worked.
TheManii said:
WARNING:
Do not use this if your venue already works. The images will overwrite what's already installed. As these are untested (but work on my streak) I have absolutely no idea if they work.
Even if they do work, they will ONLY work on devices that would boot otherwise because of /system being damaged.
If you broke it somewhere unrelated to /system this wont fix it.
Install Instructions:
(This assumes you already know how to use the command prompt on your PC)
Download Fastboot+ADB.zip and install it
Download the version matching your baseband:
304:
boot.img
recovery.img
system.img
307:
boot.img
recovery.img
system.img
321:
boot.img
recovery.img
system.img
flash them with fastboot
fastboot flash boot <path to boot.img>
fastboot flash recovery <path to recovery.img>
fastboot flash system <path to system.img>
factory reset your device
Please look at Dell Venue - XDA wiki to see what rom you have/should have
IF YOU BRICK AN ALREADY WORKING VENUE BECAUSE YOU WERE CURIOUS, IT IS YOUR OWN FAULT. DO NOT USE ON A WORKING DEVICE UNLESS YOU ALREADY KNOW HOW TO UNBRICK IT
Notes: I do not have images for 101/302/303/325. If you have any of these builds and are willing to help attempt to dump them please contact me on #dellstreak on freenode. 307 and 321 have been safely dumped from venues without harming them in any way.
Note2: The download links will change if these are confirmed to work, please do not link to them directly for the time being, please link to this thread/OP
Click to expand...
Click to collapse
Dell Venue Hongkong
Basebannd vesion: GTOUB1A130211-AWS
Kernel vesion: 2.6.32.9-pert
OEM Version: GTOUB1A130211
Build number: 12837
boot.img + recovery.img + recovery_bak.img
system.img
Thanks!
Do you recall if you've modified the rom before uploading it? I'm assuming there was a large streach of time from when you got it to when you made a dump
Edit: after going though it, there are a couple of changes, but I believe i was able to revert it to near original
Cleaned and repacked 302 now. As 307 was reported to be working, I packaged it up as a nandroid zip and moved to it's normal location on the server.
Solved
Nikolay82 said:
Hello. I am fairly new to the XDA forums and I would like to say hello to everyone.
I am looking for someone to help me with the following problem.
I flashed CID to take in any RUU. I've tried many even the USA T-mobile. It worked but had problems using mobile data. Now I use stock european one where version is:1.32.401.17
RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_.exe
. I got this version through official RUU. Device is currently S-OFF rooted and has twrp on it.
But now problems are here. I am aware european models got the 5.1 OTA update and I do have it downloaded.
File Says:
OTA_HIMA_UHL_L51_SENSE70_MR_HTC_Europe_2.10.401.1-1.40.401.8_release_444119.zip
Now when I try to update OTA through twrp it doesnt let me. Says something about Err_message. That being said, sideload wont work either. Now my question is, how do I get the OTA to my device? Note; when checking for updates via settings in the phone it says no updates available, regardless of updated airing for a while now. Now i wonder if can update from :1.32.401.17 to 2.10.401.1 with OTA or do I need to update first to 1.40.401.8 (I have 1.40.401.8 flash file).
Please if someone can help me I would thankful. Thanks.
Click to expand...
Click to collapse
OTAs can only be used with the stock recovery. I don't recommend doing a stock OTA if you have modded parts of the system. Better to flash a rom through TWRP. You might need to update the firmware as well.
Are you referring to 0PJAMIG*.zip file? in that case i have them plenty and one I need that matches my phone is like missing some files in the zip. Sadly, I can't post the link yet.
Let me explain this better please:
1. I do have RUUs,; RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_2_4
2. I do have 0PJAIMG Files as well: 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.8_Radio_01.01_U11440261_56.02.50306G_2_F_release_425571_signed_Hboot.zip
3. And I believe I have proper firmware and recoveries for said 0PJAIMG. I have every one of them downloaded for gradual update.
Problem is; I don't have the automatic RUU for version 1.32.401.8, the exe stuff. And I am having hard time installing the 0PJAIMG file on the phone because it gives errors and missing files inside from the looks.
File size of 0PJAIMG is 2gb but content withing the zip is barely 40mb but it says 2gb...
If I am able to get everything related with 1.32.401.8 I could most likely do the all process till latest update.
I am aware I can't post links but for this sake I would like to post it like this: tinyurl[dot]com/m9roms
Just replace "[dot]" with "."
moderator can remove the link however but I need urgent help. If someone can guide me what to I would appreciate it.
It looks like T-Mobile has updated the rom again. Does anyone have an extract which they can upload?
https://support.t-mobile.com/docs/DOC-28482
It appears as if sammobile already has it???
http://www.sammobile.com/firmwares/confirm/99757/G900TUVS1GPI1_G900TTMB1GPI1_TMB/
SurfinMobile77 said:
It looks like T-Mobile has updated the rom again. Does anyone have an extract which they can upload?
https://support.t-mobile.com/docs/DOC-28482
Click to expand...
Click to collapse
Here is an unmodified reupload of the new update straight from sammobile
https://mega.nz/#!5tNjRITJ!tjVgleABN53tmqFwmT9T9mSE_qZ8exIwxpoBVAFNvcw
In the process of updating my encrypted G900T, will post the necessary Odin flashable Protected Partitions once I have extracted them and hopefully not bricked my phone in the update process.
SimLynks said:
Here is an unmodified reupload of the new update straight from sammobile
https://mega.nz/#!5tNjRITJ!tjVgleABN53tmqFwmT9T9mSE_qZ8exIwxpoBVAFNvcw
In the process of updating my encrypted G900T, will post the necessary Odin flashable Protected Partitions once I have extracted them and hopefully not bricked my phone in the update process.
Click to expand...
Click to collapse
Thanks SimLynks, were you able to extract the constituent files and post them (bootloader and modem)?
SurfinMobile77 said:
Thanks SimLynks, were you able to extract the constituent files and post them (bootloader and modem)?
Click to expand...
Click to collapse
Got the files, finally posting them here now. Please go to my AndroidFileHost SM-G900T folder to grab the flashable files. https://www.androidfilehost.com/?w=files&flid=121594
Contains the OTA Update ZIP, and the two Odin Flashable TAR files.
To update your rooted/encrypted G900T to the latest OTA without needing to flash the full ROM update file, download the three files from the link posted above, and follow these steps:
1) Install Chainfire's FlashFire if you dont have it already and grant it root permissions.
Download the OTA Update to YOUR DEVICE ITSELF, Run FlashFire, and Hit the Red "Plus" -> Use either "Flash Firmware package" OR "Flash ZIP or OTA" options, find the OTA ZIP downloaded to your device and let FlashFire do it's thing.
NOTE: DO NOT LET FLASHFIRE UPDATE YOUR BOOTLOADER/MODEM these are the "Protected Partitions" and are Locked while booted into your "Custom" ROM by Samsung after it detects you've been rooted. FlashFire documentation explains this in a bit more detail.
2) Download the TAR files to the computer you will be running Odin from, and Restart your Galaxy S5 in Download Mode (Turn device off -> Hold Power Down + Home + Power)
3) Flash the TAR archives in Odin, standard way is Open Odin, connect phone in download mode (should be detected by Odin) hit the "AP" button and UNCHECK "Auto Reboot" if you want to be able to flash both the Bootloader and the Modem without the Device rebooting automatically after the first flash.
Once you have flashed BOTH the Bootloader and the Modem, go ahead and restart your device, you should now have an updated Kernel (OTA Package in FlashFire, Updated Bootloader/Modem from Odin) and be good to go even with Root/Xposed/Encrypted enabled and TWRP that cannot decrypt the Data partition with Samsung Encryption.
SimLynks said:
Got the files, finally posting them here now. Please go to my AndroidFileHost SM-G900T folder to grab the flashable files. https://www.androidfilehost.com/?w=files&flid=121594
Contains the OTA Update ZIP, and the two Odin Flashable TAR files.
To update your rooted/encrypted G900T to the latest OTA without needing to flash the full ROM update file, download the three files from the link posted above, and follow these steps:
1) Install Chainfire's FlashFire if you dont have it already and grant it root permissions.
.
Click to expand...
Click to collapse
I tried your steps, now have Baseband at TUVS1GPL1 but Build is still TUV1GPE1 and the stagefright scans still show the vulns. Also show "Android security patch level: May 1,2016" Here's what I tried:
1. did flashfire using the OTA method, rebooted. Did not update bootloader. Didn't seem like anything happened.
2. Used Odin to flash modem and bootloader. Rebooted.
3. Tried FlashFire again using the "Flash Firmware" method. Booloader items were greyed out, but left the boot.img item checked. This went through an update process.
Rebooted and checked stagefright, still fails the vulns. Just got a notifications pop-up saying "Device Seurity, threat found. Unauthorized actions have been detected, restart to undo changes." I'm assuming this is knox kicking in somehow. Now just get "Recovery is not SEANDROID enforcing" and boots straight into TWRP ... hmm.
tsh said:
I tried your steps, now have Baseband at TUVS1GPL1 but Build is still TUV1GPE1 and the stagefright scans still show the vulns. Also show "Android security patch level: May 1,2016" Here's what I tried:
1. did flashfire using the OTA method, rebooted. Did not update bootloader. Didn't seem like anything happened.
2. Used Odin to flash modem and bootloader. Rebooted.
3. Tried FlashFire again using the "Flash Firmware" method. Booloader items were greyed out, but left the boot.img item checked. This went through an update process.
Rebooted and checked stagefright, still fails the vulns. Just got a notifications pop-up saying "Device Seurity, threat found. Unauthorized actions have been detected, restart to undo changes." I'm assuming this is knox kicking in somehow. Now just get "Recovery is not SEANDROID enforcing" and boots straight into TWRP ... hmm.
Click to expand...
Click to collapse
TSH, seems like you did this correctly (or at least you have the same build info I have on my own device) only thing that appears different is my TWRP does not throw the SEANDROID Not Enforcing message, BUT thats somewhat irrelevant anyway as from what i've read from the TWRP Devs, that message is just "hidden" with the newest release of TWRP, so the Recovery is not SEANDROID Enforcing, but they remove the error message on the newest builds.
Also can you confirm what version of TWRP your running? Latest build is 3.0.2-2 (and is what im running without the SEANDROID message you have). At one point I had a "custom" build of TWRP with version I think 3.0.2-3 but the dev of that custom build eventually pulled the files as the official 3.0.2-2 had been updated past the custom build notwithstanding the conflicting build numbers.
Anyway as to your Build Number still at GPG2 but Baseband at GPI1 that is EXACTLY the same as my device and from what I can tell the correct build numbers you should be seeing. This OTA did not update the "build" it just updated the Kernel/Modem/Bootloader to GPI1. The important thing to check for the the Kernel build DATE, which should now be "Mon Sep 12". My Security Patch Level is "July 1, 2016" not May 1 so im not sure how that mismatch has happened. Please try to run the OTA from TWRP and let me know what happens. This is the first time i've ever tried to update using the OTA file directly so might have missed a step or forgotten I flashed with FlashFire then to double ensure I updated correctly updated in TWRP also before using Odin to flash the rest.
Additionally, when I first updated to this OTA a few days ago, ran the Zimperium Stagefright testing and passed 100%, However when I reran the test after reading your post, as has become my expectation with Stagefright and Samsung "patches" it now fails again, because Zimperium is constantly updating the test to include the newest found bugs with Stagefright...so the GPI1 Kernel is patched for any Stagefright bugs as-of Sep 12, but the Zimperium people seem to constantly find new bugs with this damn library...So we need to wait for the next OTA patch to only have the Stagefright testing fail again a week later once Zimperium has updated the tests to include the neverending Stagefright bugs.
I really need to run the Stagefright testing on my friend's Nexus which is running Nougat and was the first device in a while i've seen pass 100%, might have same issues there but I have not checked yet.
Yep, latest TWRP 3.0.2.2... I was able to get the security notification to stop by uninstalling the Samsung security log system app. Still can't pass the stagefright test... I get 12 critical and 45 high vulns testing with Zimperium v5.3
Something definitely not right... Afraid I may just bite the bullet and do a complete wipe and install fresh.
Sent from my SM-G900T using XDA Free mobile app
tsh said:
Yep, latest TWRP 3.0.2.2... I was able to get the security notification to stop by uninstalling the Samsung security log system app. Still can't pass the stagefright test... I get 12 critical and 45 high vulns testing with Zimperium v5.3
Something definitely not right... Afraid I may just bite the bullet and do a complete wipe and install fresh.
Click to expand...
Click to collapse
Right, I mean a full wipe / restore will definitely fix the issue no doubt, but before you try that you can always do the "full" ROM update using the same method as I previously posted, just replace flashing the OTA from FlashFire, with flashing the full ROM Update and follow all the other steps. Also make sure FlashFire has "Everroot" Checked and I entirely disable flashing "Protected Partiions" in settings, so there is no "unchecking" anything, FlashFire does that automatically.
OTA or Full ROM release, FlashFire still cant safely deal with the "protected partitions", but this is how prior to attempting to use the smaller OTA file, I have been updating my rooted/xposed/encrypted G900T from release to release, the downside to the full update is that after flashing everything you get to wait for the ROM to rebuild the cache, reboot to TWRP and reflash SuperSU and if using Xposed reflash that as well and then again wait for the system to rebuild as Xposed does it's thing on the first boot after install.
I also did not think to consider that my heavily "trimmed" System Apps might have an effect on this, I use Titanium Backup & Greenify immediately after install to outright freeze all the bloatware or Greenify things the system needs to function properly, but I don't want running all the time. When I get a chance Im going to update my friend's G900T using my method and try to figure out this discrepancy between what worked for me, and what is clearly giving you some issues. Until then i'd appreciate any further feedback you can give me so I can revise the process to eliminate any potential trouble spots. Sorry to keep spamming you with all this unnecessary info, but until I can post my own thread on this stuff im just kinda throwing everything I've got here so the info is somewhere.
As for the Stagefright issue, I just reran the Zimperium Stagefright testing again on my up-to-date G900T as well as a Galaxy S3 I'm running the latest nightly Exodus ROM release on (Google Release r68, Android Security Patch Date September 6, 2016, Kernel Build Date Oct 6, 2016) and BOTH devices now fail the Stagefright testing again, after previously passing for about a week or so...This is just how it works with Stagefright unfortunately, they patch it until more bugs are found, rinse repeat.
So no matter what it seems, your gonna fail Stagefright even if on an incredibly recent Build/Kernel. My last test for this needs to be if Nougat also now fails as well, because if so, then it's just another round of the Stagefright party as standard, since they first announced this back in July 2015.
tsh said:
I tried your steps, now have Baseband at TUVS1GPL1 but Build is still TUV1GPE1 and the stagefright scans still show the vulns. Also show "Android security patch level: May 1,2016" Here's what I tried:
1. did flashfire using the OTA method, rebooted. Did not update bootloader. Didn't seem like anything happened.
2. Used Odin to flash modem and bootloader. Rebooted.
3. Tried FlashFire again using the "Flash Firmware" method. Booloader items were greyed out, but left the boot.img item checked. This went through an update process.
Rebooted and checked stagefright, still fails the vulns. Just got a notifications pop-up saying "Device Seurity, threat found. Unauthorized actions have been detected, restart to undo changes." I'm assuming this is knox kicking in somehow. Now just get "Recovery is not SEANDROID enforcing" and boots straight into TWRP ... hmm.
Click to expand...
Click to collapse
You need to flash a firmware package containing a system/system.img. stagefright are system libs. If you want that fix you need to just go ahead and flash the entire firmware. Only thing is tho, stagefright has never been 100% fixed
SimLynks said:
Anyway as to your Build Number still at GPG2 but Baseband at GPI1 that is EXACTLY the same as my device and from what I can tell the correct build numbers you should be seeing. This OTA did not update the "build" it just updated the Kernel/Modem/Bootloader to GPI1.
Click to expand...
Click to collapse
I don't believe that is correct, after flashing the complete OTA (without wiping) both my baseband and build are showing GPI1. Baseband is G900T3UVS3GPI1, build is MMB29M.GT900T3UVS3GPI1. Kernel is 3.4.0-7500527. There's no longer any GPG2 reference on my phone.
Flashed the firmware from scratch. I ran a debloater and openvpn don't work. Running Windows and I can't seem to open system.img.ext4. Can someone check this firmware to see if there is a vpndialogs.apk inside? Need this to get vpn working again.
djy said:
Flashed the firmware from scratch. I ran a debloater and openvpn don't work. Running Windows and I can't seem to open system.img.ext4. Can someone check this firmware to see if there is a vpndialogs.apk inside? Need this to get vpn working again.
Click to expand...
Click to collapse
yes, I can find vpndialogs.apk under priv-app
Could you please post it for me, along with the target path? I can't get ext2explore.exe to open the image.
djy said:
Could you please post it for me, along with the target path? I can't get ext2explore.exe to open the image.
Click to expand...
Click to collapse
Please follow the instructions in this thread
http://forum.xda-developers.com/android/help/android-dat-img-file-unpack-repack-2-0-t3309285
SimLynks said:
TSH, seems like you did this correctly (or at least you have the same build info I have on my own device) only thing that appears different is my TWRP does not throw the SEANDROID Not Enforcing message, BUT thats somewhat irrelevant anyway as from what i've read from the TWRP Devs, that message is just "hidden" with the newest release of TWRP, so the Recovery is not SEANDROID Enforcing, but they remove the error message on the newest builds.
Also can you confirm what version of TWRP your running? Latest build is 3.0.2-2 (and is what im running without the SEANDROID message you have). At one point I had a "custom" build of TWRP with version I think 3.0.2-3 but the dev of that custom build eventually pulled the files as the official 3.0.2-2 had been updated past the custom build notwithstanding the conflicting build numbers.
Anyway as to your Build Number still at GPG2 but Baseband at GPI1 that is EXACTLY the same as my device and from what I can tell the correct build numbers you should be seeing. This OTA did not update the "build" it just updated the Kernel/Modem/Bootloader to GPI1. The important thing to check for the the Kernel build DATE, which should now be "Mon Sep 12". My Security Patch Level is "July 1, 2016" not May 1 so im not sure how that mismatch has happened. Please try to run the OTA from TWRP and let me know what happens. This is the first time i've ever tried to update using the OTA file directly so might have missed a step or forgotten I flashed with FlashFire then to double ensure I updated correctly updated in TWRP also before using Odin to flash the rest.
Additionally, when I first updated to this OTA a few days ago, ran the Zimperium Stagefright testing and passed 100%, However when I reran the test after reading your post, as has become my expectation with Stagefright and Samsung "patches" it now fails again, because Zimperium is constantly updating the test to include the newest found bugs with Stagefright...so the GPI1 Kernel is patched for any Stagefright bugs as-of Sep 12, but the Zimperium people seem to constantly find new bugs with this damn library...So we need to wait for the next OTA patch to only have the Stagefright testing fail again a week later once Zimperium has updated the tests to include the neverending Stagefright bugs.
I really need to run the Stagefright testing on my friend's Nexus which is running Nougat and was the first device in a while i've seen pass 100%, might have same issues there but I have not checked yet.
Click to expand...
Click to collapse
Hi!
I think your method fails to update the build. FlashFire doesn't patch anything, (build number still show GPG2)
This is what I do:
Restore original boot from my GPG2 clean install (boot is unpatched)
Restore stock recovery (through ODIN)
(2 previous steps avoid status 7 error while applying OTA updates)
Flash OTA update .zip through stock recovery
Reinstall TWRP custom recovery
Reroot Applying superSU.zip method
Wipe Dalvik / cache
Reboot
After 10 minutes everytihng working!
I'm uploaded a screenshot with the results
I think triyng to apply OTA updates with any workaround is possible whenever system partition is reasonably stock, because OTA updates patch files, not replace files
My system was just rooted and 2 battery stats helpers installed. I think with xposed installed the above steps must work. But with other tweaks more complex OTA updates with no stock system will fail
That's similar to what I did, but without the need to restore data since you flashed the stock recovery without flashing the system by the sound of it. Can you explain exactly which images you flashed for boot & stock recovery? I'm thoroughly confused over what's what, since everybody seems to use different jargon to mean the same thing.
invisiblewave said:
I don't believe that is correct, after flashing the complete OTA (without wiping) both my baseband and build are showing GPI1. Baseband is G900T3UVS3GPI1, build is MMB29M.GT900T3UVS3GPI1. Kernel is 3.4.0-7500527. There's no longer any GPG2 reference on my phone.
Click to expand...
Click to collapse
Was your phone rooted? AFAIK, We cannot apply OTA update with boot or recovery modified
My phone was rooted I restore stock recovery and boot and apply OTA, And I didn't lose my data or installed apps
Reyse said:
Was your phone rooted? AFAIK, We cannot apply OTA update with boot or recovery modified
My phone was rooted I restore stock recovery and boot and apply OTA, And I didn't lose my data or installed apps
Click to expand...
Click to collapse
yes, it was rooted, I restored the entire image, ran the update, then re-rooted & restored /data. Do you have a link to the stock recovery/boot image? I'd like to do it the same way as you next time.
invisiblewave said:
yes, it was rooted, I restored the entire image, ran the update, then re-rooted & restored /data. Do you have a link to the stock recovery/boot image? I'd like to do it the same way as you next time.
Click to expand...
Click to collapse
I extracted both image from the full update from Sammobile
Follow these instructions
Download 7Zip archive manager http://www.7-zip.org/download.html
Download the full image of your phone from SAMMOBILE
For example my previous phone version was G900TUVS1GPG2_G900TTMB1GPG2_TMB.zip
Open that file with 7zip
it contains G900TUVS1GPG2_G900TTMB1GPG2_G900TUVS1GPG2_HOME.tar.md5
double click to extract
these are the files in the archive
Code:
aboot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
cache.img.ext4
modem.bin
boot.img => stock boot
recovery.img => stock recovery
extract both files
Now for each of them:
- right click => 7ZIP => Add to archive...
- it suggest the same name (irrelevant)
- Choose archive format => tar (very important)
- Press Ok
- Flash with ODIN
(don't reboot, turn off and turn on for each flash to avoid boot phone and mess versions)
Source of this instructions: http://howto.highonandroid.com/samsung-tutorials/how-to-extract-stock-recovery-from-samsung-firmware/
Since a lot of people is asking for firmware files, OTAs, boot.img, I decided to collect all the resources here, so that it would be easier to get what you need.
First of all, you have to identify your ROM version. It is not the scope of this post to teach you how to use adb, so I suppose you already know.
Run adb shell getprop ro.build.oplus_nv_id and check the result with the table at the end of the post to know if you have the export or GDPR ROM.
Full (EDL mode) firmware downloads:This is the firmware you can also find on realmefirmware.com, but the website doesn't have all the versions.
Unfortunately, not all versions are available on the Realme servers, so if a firmware is not listed here, it's not available.
export firmware downloads:Android 12:RMX3301export_11_A.06_2022020500280000.zip
RMX3301export_11_A.08_2022022300070395.zip
RMX3301export_11_A.10_2022031419130229.zip
RMX3301export_11_A.11_2022031821250000.zip
RMX3301export_11_A.13_2022040705040000.zip
RMX3301export_11_A.14_2022041311050164.zip
RMX3301export_11_A.15_2022042701280000.7z
RMX3301export_11_A.16_2022052418230167.7z
RMX3301export_11_A.17_2022062222270183.7z
RMX3301export_11_A.18_2022072511110152.zip
RMX3301export_11_A.19_2022082205500000.zip
RMX3301export_11_A.21_2022092223350165.zip
Android 13:RMX3301export_11_C.08_2022102215440135.zip
RMX3301export_11_C.12_2022121600040215.zip
RMX3301export_11_C.13_2023010918370148.zip
RMX3301export_11_C.16_2023031621430000.zip
Android 13 (ColorOS 13.1):RMX3301export_11_C.18_2023050511080109.zip
RMX3301export_11_C.19_2023052220180130.zip
GDPR firmware downloads:Android 12:RMX3301GDPR_11_A.06_2022021320090088.zip
RMX3301GDPR_11_A.07_2022021800320350.zip
RMX3301GDPR_11_A.09_2022030402540000.zip
RMX3301GDPR_11_A.10_2022031818500135.zip
RMX3301GDPR_11_A.14_2022041414290143.zip
RMX3301GDPR_11_A.17_2022062222280000.7z
RMX3301GDPR_11_A.18_2022072511120000.zip
RMX3301GDPR_11_A.19_2022082205510000.zip
RMX3301GDPR_11_A.21_2022092223360000.zip
Android 13:RMX3301GDPR_11_C.08_2022102215410137.zip
RMX3301GDPR_11_C.12_2022121600050000.zip
RMX3301GDPR_11_C.13_2023010918380000.zip
RMX3301GDPR_11_C.16_2023031621420140.zip
Android 13 (ColorOS 13.1):RMX3301GDPR_11_C.18_2023050510510127.zip
RMX3301GDPR_11_C.19_2023052220190000.zip
Full OTA firmware downloads:You can install this directly from your phone, but it is specific for your nv_id, so if you can't find your ID here, use the full firmware if available or read below to get the URL by yourself.
India (IN) firmware downloads (nv_id = 00011011):Android 12:RMX3301_11.A.14_0140_202204131105: RMX3301_ROLL_BACK_Android12_IN.zip (Can be used to roll back from any future version)
RMX3301_11.A.15_0150_202204270128: 2620c0ef8b8d4057a77b7f114f18f1b9.zip
RMX3301_11.A.16_0160_202205241823: 9d61d0852808452091f4a552997a63ed.zip
RMX3301_11.A.17_0170_202206222227: a4b475a3f4b54619adfbcd36ca4282cd.zip
RMX3301_11.A.18_0180_202207251111: 24968044538344fbb0d34fbd21858e09.zip
RMX3301_11.A.19_0190_202208220550: 57fea9b57d4e4880b7ffb336bcd0d3ed.zip
RMX3301_11.A.21_0210_202209222335: 8b0fb5198b894a218d55d423355bd13e.zip
Android 13 Beta:RMX3301_11.C.01_1010_202205071838: RMX3301_11_C.01_Update_Android13_IN.zip (Android 13 DP1)
RMX3301_11.C.02_1020_202208152015: 3b232a024abc4168a24a0a7e4e24c879.zip (Official Trial Program)
RMX3301_11.C.05_1050_202209011105: 94662e8d4288490394eb240dd040f434.zip (Official Trial Program)
RMX3301_11.C.06_1060_202209192326: 0836f0a8968f4e10bc2dd123615a78b7.zip (Open Beta Program)
Android 13:RMX3301_11.C.08_1080_202210221544: 4ccc3d3cb837437ea787baaac853fc4d.zip
RMX3301_11.C.11_1110_202212121458: cdddcd5ba2c24a88bf8bf12ecb1b848c.zip
RMX3301_11.C.12_1120_202212160004: 2d60293ecc02486db514639c4493e73d.zip
RMX3301_11.C.13_1130_202301091837: bb2e8a1445c742e582a528399eb6d4e3.zip
RMX3301_11.C.16_1160_202303162143: 0389f0251b6243d99a8a23774df59022.zip
RMX3301_11.C.16_1160_202303162143: RMX3301_ROLL_BACK_Android13_IN.zip (Can be used to roll back from any future version)
Android 13 (ColorOS 13.1):RMX3301_11.C.18_1180_202305051108: b741fb43f5a94ffa981f440453ce5e8e.zip
RMX3301_11.C.19_1190_202305222018: 0d8de9b09a2e457a92726bdbcb8390ed.zip
RMX3301_11.C.20_1200_202306191319: 3fd59892f871401f9a4395994ebf6d47.zip
Android 14:RMX3301_11.F.01_3010_202304262041: RMX3301_11_F_OTA_3010_all_M5Kvg6_00011011.zip (Android 14 DP1)
Europe (EUEX) firmware downloads (nv_id = 01000100):Android 12:RMX3301_11.A.14_0140_202204141429: RMX3301_ROLL_BACK_Android12_EU.zip (Can be used to roll back from any future version)
RMX3301_11.A.15_0150_202204270129: 72db4088a1f34478bdc177d850ce3144.zip
RMX3301_11.A.16_0160_202205241824: 2f2b32b599734ca1975f8b95deb3dd0a.zip
RMX3301_11.A.17_0170_202206222228: c1db6ff9301c4de09773f1e1add9bd9d.zip
RMX3301_11.A.18_0180_202207251112: c97759dd1029491cae944ff1fadf8853.zip
RMX3301_11.A.19_0190_202208220551: beac418fbda441a786e58892b10f9538.zip
RMX3301_11.A.21_0210_202209222336: 1c78489d1868491c9e4c5d54369c7d8e.zip
Android 13 Beta:RMX3301_11.C.01_1010_202205071837: RMX3301_11_C.01_Update_Android13_EU.zip (Android 13 DP1)
RMX3301_11.C.02_1020_202206061202: RMX3301_11_C.02_Update_Android13_EU.zip (Android 13 DP2)
Android 13:RMX3301_11.C.08_1080_202210221541: 336d3d23e61d4839a2fdd21c8b9d56d7.zip
RMX3301_11.C.11_1110_202212121459: 7449aed556e444d3b369ef3458f95c1c.zip
RMX3301_11.C.12_1120_202212160005: 685a18388d0047a59c5d16fa16aa2ea5.zip
RMX3301_11.C.13_1130_202301091838: f3c7c3df25ce460399c7c47c608bf8c6.zip
RMX3301_11.C.16_1160_202303162142: 4fceb2d35bb9483ebc73043e00f90dad.zip
Android 13 (ColorOS 13.1):RMX3301_11.C.18_1180_202305051051: 5feda6c46e9649acb610be202d7869ab.zip
RMX3301_11.C.19_1190_202305222019: d3e80c6c535f427fa2e74ab2d31893c7.zip
How to get the latest OTA URL by yourself:You can use realme-ota to get the latest OTA for another nv_id or the ones above if I haven't updated this topic yet after a new update is released. Just keep in mind that, if the rollout is still ongoing, you may still get the previous version. Just wait a few days and try again.
For example, to get the latest TW OTA (nv_id = 00011010), run
Code:
realme-ota -r 0 RMX3301 RMX3301_11.A.00_0000_000000000000 3 00011010
You will find the URL near the top of the response.
How to extract images from EDL firmware package:
Extract the zip or 7z file
Use mct_ofp_extractor or oppo_decrypt to extract the OFP file
If you need to get super.img, open super_map.csv and take note of the files you have to merge for your nv_id
Use simg2img to merge your files like this (search online for the simg2img binary if you're on Windows):
Code:
simg2img super.0.xxxxxxxx.img super.1.xxxxxxxx.img super.2.xxxxxxxx.img super.img
If you need to extract super.img too, use lpunpack (please search online for the download and how to use it)
How to extract images from OTA zip files:
Extract the OTA zip file
Download and extract payload-dumper-go
Drag and drop payload.bin on payload-dumper-go executable
NV IDs table (needs confirmation):
RegionRegion abbreviationnv_id (HEX)nv_id (BIN)ROM typeNotesTaiwanTW1A00011010exportIndiaIN1B00011011exportIndonesiaID3300110011exportRussiaRU3700110111exportMalaysiaMY3800111000exportThailandTH3900111001exportPhilippinesPH3E00111110exportSaudi ArabiaSA8310000011exportLatin AmericaLATAM9A10011010exportBrazilBR9E10011110exportMiddle East and AfricaMEAA610100110exportEurope (EU, EEA, UK and Switzerland)EUEX4401000100GDPRUnited KingdomGB8A10001010GDPR1TurkeyTR5101010001GDPRRest of EuropeEU-NONEEA-Double8D10001101GDPRChinaALLNET9710010111domestic
Notes:
Only found in build C.08 through C.16 inclusive; identical to the EUEX one, but with the potential to differentiate some partitions.
very nice, l'm downloading. but...how did you find them? there are some special sites
Rapper_skull said:
Since a lot of people is asking for firmware files, OTAs, boot.img, I decided to collect all the resources here, so that it would be easier to get what you need.
First of all, you have to identify your ROM version. It is not the scope of this post to teach you how to use adb, so I suppose you already know.
Run adb shell getprop ro.build.oplus_nv_id and take note of the result.
If the result is 01000100, 01010001 or 10001101, you have the GDPR ROM installed, otherwise you have the export one.
Full (EDL mode) firmware downloads:This is the firmware you can also find on realmefirmware.com, but the website doesn't have all the versions.
Unfortunately, not all versions are available on the Realme servers, so if a firmware is not listed here, it's not available.
export firmware downloads:RMX3301export_11_A.06_2022020500280000.zip
RMX3301export_11_A.08_2022022300070395.zip
RMX3301export_11_A.10_2022031419130229.zip
RMX3301export_11_A.11_2022031821250000.zip
RMX3301export_11_A.13_2022040705040000.zip
RMX3301export_11_A.14_2022041311050164.zip
RMX3301export_11_A.15_2022042701280000.7z
RMX3301export_11_A.16_2022052418230167.7z
RMX3301export_11_A.17_2022062222270183.7z
GDPR firmware downloads:
RMX3301GDPR_11_A.06_2022021320090088.zip
RMX3301GDPR_11_A.07_2022021800320350.zip
RMX3301GDPR_11_A.09_2022030402540000.zip
RMX3301GDPR_11_A.10_2022031818500135.zip
RMX3301GDPR_11_A.14_2022041414290143.zip
RMX3301GDPR_11_A.17_2022062222280000.7z
Full OTA firmware downloads:You can install this directly from your phone, but it is specific for your nv_id, so if you can't find your ID here, use the full firmware if available.
India (IN) firmware downloads (nv_id = 00011011):RMX3301_11.A.14_0140_202204131105: RMX3301_ROLL_BACK_Android12_IN.zip (You can use this package to roll back from any future version)
RMX3301_11.A.15_0150_202204270128: 2620c0ef8b8d4057a77b7f114f18f1b9.zip
RMX3301_11.A.17_0170_202206222227: a4b475a3f4b54619adfbcd36ca4282cd.zip
RMX3301_11.A.18_0180_202207251111: 24968044538344fbb0d34fbd21858e09.zip
RMX3301_11.C.01_1010_202205071838: RMX3301_11_C.01_Update_Android13_IN.zip (Android 13 DP1)
Europe (EUEX) firmware downloads (nv_id = 01000100):RMX3301_11.A.14_0140_202204141429: RMX3301_ROLL_BACK_Android12_EU.zip (You can use this package to roll back from any future version)
RMX3301_11.A.15_0150_202204270129: 72db4088a1f34478bdc177d850ce3144.zip
RMX3301_11.A.16_0160_202205241824: 2f2b32b599734ca1975f8b95deb3dd0a.zip
RMX3301_11.A.17_0170_202206222228: c1db6ff9301c4de09773f1e1add9bd9d.zip
RMX3301_11_A.18_0180_202207251112: c97759dd1029491cae944ff1fadf8853.zip
RMX3301_11.C.01_1010_202205071837: RMX3301_11_C.01_Update_Android13_EU.zip (Android 13 DP1)
RMX3301_11.C.02_1020_202206061202: RMX3301_11_C.02_Update_Android13_EU.zip (Android 13 DP2)
Click to expand...
Click to collapse
i finished downloading the complete rom.
I put payload.bin in input in payload_dumper, but in output it only picks me up:
hyp.img
my_manifest.img
xbl_ramdump.img
to fetch the boot?
sorry i'm bothering you so much, but i'm stuck here
marco.chinagliaxx91 said:
i finished downloading the complete rom.
I put payload.bin in input in payload_dumper, but in output it only picks me up:
hyp.img
my_manifest.img
xbl_ramdump.img
to fetch the boot?
sorry i'm bothering you so much, but i'm stuck here
Click to expand...
Click to collapse
I updated the post with the payload dumper I use. Please try it.
Rapper_skull said:
I updated the post with the payload dumper I use. Please try it.
Click to expand...
Click to collapse
when i downloaded the rom, a18 in the phone settings with a file manager i was able to download ota, but i had the same problem that i described above. I didn't know you had to use payload - go. You saved my life man. Now I know how. I promise that with each update I will post the updated files.
Excellent thread. Include Export firmware OTA also if possible
shivrajsingh said:
Excellent thread. Include Export firmware OTA also if possible
Click to expand...
Click to collapse
OTAs are not divided in export and GDPR, but by nv_id. There are OTA links for India in the post, and that's one of the many export nv_ids. Unfortunately, I can not keep track of every nv_id, because there are too many.
Rapper_skull said:
OTAs are not divided in export and GDPR, but by nv_id. There are OTA links for India in the post, and that's one of the many export nv_ids. Unfortunately, I can not keep track of every nv_id, because there are too many.
Click to expand...
Click to collapse
if you want we can do that at each update I take care of the EU.
I create a folder on mega sorted.
Each folder will have the name of the firmware, in it I will put that firmware
boot_stock.img
vbmeta.img
magisk.img
and two bat files
stock_boot.bat
magisk_boot.bat
that I created, just run it to give root permissions or restore the original boot. Whether the phone is on or in fastboot it will be the same. In the bat I have thought of everything. A little thank you here
marco.chinagliaxx91 said:
if you want we can do that at each update I take care of the EU.
I create a folder on mega sorted.
Each folder will have the name of the firmware, in it I will put that firmware
boot_stock.img
vbmeta.img
magisk.img
and two bat files
stock_boot.bat
magisk_boot.bat
that I created, just run it to give root permissions or restore the original boot. Whether the phone is on or in fastboot it will be the same. In the bat I have thought of everything. A little thank you here
Click to expand...
Click to collapse
All users who flashed from China Rom to Global Rom have that particular Export version. They are mostly rooted and get OTA late. So ota link may be beneficial for them.
How to check NV ID?
shivrajsingh said:
All users who flashed from China Rom to Global Rom have that particular Export version. They are mostly rooted and get OTA late. So ota link may be beneficial for them.
How to check NV ID?
Click to expand...
Click to collapse
not so answer you. I have eu firmware
I'm marco.chinagliaxx91. This Is my real account. Now i can use a gt2pro
shivrajsingh said:
All users who flashed from China Rom to Global Rom have that particular Export version. They are mostly rooted and get OTA late. So ota link may be beneficial for them.
How to check NV ID?
Click to expand...
Click to collapse
getprop ro.build.oplus_nv_id
Rapper_skull said:
getprop ro.build.oplus_nv_id
Click to expand...
Click to collapse
Its 00011010
shivrajsingh said:
Its 00011010
Click to expand...
Click to collapse
That is the TW (Taiwan) ROM. I suggest migrating to the IN ROM, since it is also the default region. In any case, I updated the first post with instructions on how to get the latest OTA URL by yourself.
Maybe in the future I will write a script to get all the URLs automatically.
I get 10100110. Does this mean I have the IN version?
when I try realme-ota -r 0 RMX3301 RMX3301_11.A.00_0000_000000000000 3 10100110 it gives me a few lines:
Load payload for RMX3301 (RealmeUI V3)
Wait for the endpoint to reply
Response status mismatch, expected '200' got '500'!
I am trying to get the firmware for my phone because ever since I took the A.18 update my phones Widevine was downgraded to L3. I am hoping A18 just messed something up in update process and flashing the A17 stock rom then rerooting will fix it.
GIutton said:
I am trying to get the firmware for my phone because ever since I took the A.18 update my phones Widevine was downgraded to L3. I am hoping I just messed something up in update process and flashing the stock rom then rerooting will fix it.
Click to expand...
Click to collapse
Widewine degrades to L3 by flashing Global and there is no official fix.
EDIT: Typo, degrades to L3, not L1
Quake94 said:
Widewine degrades to L1 by flashing Global and there is no official fix.
Click to expand...
Click to collapse
But I have never flashed any roms to the phone. Have rooted with magisk and only ever used the stock OTA updates from "about phone"
GIutton said:
But I have never flashed any roms to the phone. Have rooted with magisk and only ever used the stock OTA updates from "about phone"
Click to expand...
Click to collapse
After unlocking bootloader, how did you root your phone? Did you flash a patched boot.img over the stock ROM?
No I booted the phone with a magisk patched boot.img then did a direct install using the magisk app on stock A.17. I had wideine L1 until I took the A.18 official OTA for my phone then it went to L3. It was an incremental update. To go from A.17 to A.18 I used magisk > uninstall magisk > restore images. Then downloaded and installed the OTA, took a copy of the boot.img from the inactive slot and patched it with magisk and copied to PC. Then I restored root with magisk direct install, turned on airplane mode, rebooted the phone from the System Update Dialog "install" then rebooted to bootloader and used fastboot boot magisk-patched-boot.img and then used magisk to do a direct install to make root permanent.
I had to unroot the phone and relock the bootloader in order to get back to Widevine L1. Maybe I am just wrong and it went to L3 right after I unlocked the bootloader. Has anyone been able to keep Widevine L1 with an unlocked bootloader and Magisk rooted?