Related
Hi y'all!
I'm really having trouble flashing an official stable rom on my device. The rom archive is miui_HM3_V7.3.2.0.LHPCNDD_6a5e1bc33c_5.1.zip.
I downloaded it and copied it to a folder (downloaded_rom) on the internal storage of my redmi 3. After selecting it in the updater app I get asked whether it's OK to delete all data, because the rom I'm updating to is older than the one installed. My phone's miui version is MIUI 77. Stable 77.1.1.0 (LHPCNCK). The doble 7s seem odd to me and may be part of my problem (I bought the phone like that). Then, the device is rebooting and I can see some kind of progression bar for a couple of seconds on the botton of the screen but then it just reboots into android and nothing changed
I also tried to flish it via Mi PC suite. Here, after connecting the device in fastboot mode, I got the message that my device isn't supported.
I also believe that the bootloader is locked and I already got the "permission" from xiaomi to unlock it but I had no luck with this either. The Mi unlock tool is telling me, that the "current account is different from the account info on the device" which wasn't the case after I double checked.
Am I missing something here?
kind regards
lunatikk
yes.
because you are currently in modified rom (rom supplier or seller, etc, etc) you cannot update or do anything about it
flash the official rom using miflash method
after that you can update using updater program
Ice Zodiac said:
yes.
because you are currently in modified rom (rom supplier or seller, etc, etc) you cannot update or do anything about it
flash the official rom using miflash method
after that you can update using updater program
Click to expand...
Click to collapse
I'll try that and report back. Thanks!
Okay, finally I managed to flash my phone with the newest miui.eu rom. What I did was:
- Flashing the official Xiaomi Rom (MiFlash package) via MiFlash (1st try in Win32 wasn't working. 2nd try on Win64 did the job)
- I had to update to the newest official stable OTA, because somehow, I wasn't able to unlock my bootloader with the older version.
- I unlocked the bootloader using the MiFlashUnlocker.
- Updated to the official MIUI 8 dev rom using updater app on my phone
- On dev rom I granted root acces to flashify and flashed the twrp recovery image on my device (which gets wiped from my device every time I reboot - anyone knows why??)
- Reboot into recovery and flash the MIUI.eu zip which is now running on my device.
Thanks for the help guys!
Hi.
I am having the same problem, with pre-installed rom: MIUI 77.1.1.0 Stable. The updater app obviously doesn't work (now i know why) and the MiFlash software doesn't seem to work either. It doesn't recognise the phone, browsing to the downloaded rom does nothing. Am i missing something?
Update, it now recognises the phone, but miflash is saying it can't find the file specified (0x80070002: Execute flash_all.bat)
Thanks for any assistance you can give.
Update 2. Just found out you need a different version of the Rom for fastboot. available from http://en.miui.com/a-234.html for anyone searching.
Okay so Miflash began the process when i had the Fastboot rom, but failed at about 2 percent as the device is locked.
Although i have permission the Mi unlock tool won't unlock my phone as it says the accounts don't match that on the phone, although i have quadruple checked them.
Research suggests it might be a problem with the custom rom on my phone, or that i need to be on the China Dev rom to unlock?
But i can't flash the China Dev Rom!!!
Is there any way to get my device to stock rom?
Sorted.
For the benefit of anyone searching, i followed the instructions here: http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=242867&pid=4510751
I've been messing with root on my G965F and, after a few ROM changes a decided to return to One UI, but my camera simply doesn't work. I'de flashed the CSB3 vendor image in order to install pixel experience ROM.
At the time I did my One UI backup, but I didn't save the original vendor Image, and now I can't completely restore it. Therfor my camera refuses to function.
I've tried restoring my device using odin, but becouse I've TWRP installed it gave me an error (a very scary one), "an error has occurred while updating the device software s9+...". It prompet me to use Smart switch emergency recovery which failed to recognise my device. My solution was to flash TWRP again (Fortunately it worked, and I was back to TWRP).
I restored my one UI backup without the vendor image, and the camera still doesn't work.
If I understood this corectly, if I restore my vendor image the camera will fuction back again. But I'am open to sugestions.
Thanks
RichNoob said:
I've been messing with root on my G965F and, after a few ROM changes a decided to return to One UI, but my camera simply doesn't work. I'de flashed the CSB3 vendor image in order to install pixel experience ROM.
At the time I did my One UI backup, but I didn't save the original vendor Image, and now I can't completely restore it. Therfor my camera refuses to function.
I've tried restoring my device using odin, but becouse I've TWRP installed it gave me an error (a very scary one), "an error has occurred while updating the device software s9+...". It prompet me to use Smart switch emergency recovery which failed to recognise my device. My solution was to flash TWRP again (Fortunately it worked, and I was back to TWRP).
I restored my one UI backup without the vendor image, and the camera still doesn't work.
If I understood this corectly, if I restore my vendor image the camera will fuction back again. But I'am open to sugestions.
Thanks
Click to expand...
Click to collapse
Simply, copy your data and download the official pie from samfirm or where you want and flash it with the latest odin.. have a thread about latest pie for s9 plus you can chek it..
forkatar12 said:
Simply, copy your data and download the official pie from samfirm or where you want and flash it with the latest odin.. have a thread about latest pie for s9 plus you can chek it..
Click to expand...
Click to collapse
I already tried that. But when I attempt to flash it using odin it gives me an error on my phone "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 4 BINARY: 3".
I might be wrong, but to my understanding from your last post you tried to install an original firmware image with bootloader v3 while your phone already has a bootloader v4. If I understand everything correctly you need to use a firmware version (for your region) containing a bootloader v4 for it to install correctly - otherwise it won't install since bootloaders aren't backwards compatible.
About
**********
I've created a flashable ROM zip of the latest H990DS KDZ SEA Region. Everything is working correctly on my H990 Single SIM.
ARB
**********
0
Security Patch
**********
1 April 2019
Download
**********
1. With modem & cust partitions (only if you know what you are doing):
https://drive.google.com/open?id=1YARnnE4-V1y9Jd1EhTzdizdkd6DaAYz_
2. Without modem & cust partitions (keeps your existing modem, recommended):
https://drive.google.com/open?id=1gCHxAk3hXjCsA4Qm3djgSmJEb3rSL5WA
Installation process:
**********
1. Upgrading / flashing over another stock Oreo ROM:
• Flash latest TWRP
• BACKUP everything
• Wipe (caches)
• Flash ROM
• Flash Magisk
• Flash MK2000 Oreo kernel (Important!)
• Reboot
• Enjoy
2. Clean from scratch install:
• Flash latest TWRP
• BACKUP everything
• Backup everything you want to put back, it will be wiped
• Clean wipe (data, system, caches)
• Flash ROM
• Flash Magisk
• Flash MK2000 Oreo kernel (Important!)
• Reboot
• Enjoy
flashing the second rom without modem or cust now on my h990ds , i hope everything goes well
sniper9911 said:
flashing the second rom without modem or cust now on my h990ds , i hope everything goes well
Click to expand...
Click to collapse
Just please remember to flash MK2000 kernel after you flash the ROM without rebooting in-between.
I made the mistake of rebooting afterwards and the stock kernel restored the stock recovery and wiped my device.
(This wasn't an issue because I made a full backup of all of my data though)
updated successfully
Updated the dirty way flashed over my current ROM ... I wiped cache and art cache just in case
Seems legit and so far my device is finishing the data setting , i did make a backup of my firmware files just in case and so far it went smoothly
All i did was downloading the ROM , Twrp , mk2000 h990ds v2.1 And Magisk latest
Flashed Twrp first then recovery rebooted , wiped Dalvick and cache then flashed ROM then flashed mk2000 then magisk and phone booted
Thanks for the update
I have also updated my H990DS successfully by "dirty" upgrade keeping all apps.
I just added H990DS_Hide_Boot_Warning.zip to remove the error message at boot start.
sniper9911 said:
Thanks for the update
Click to expand...
Click to collapse
tapir1505 said:
I have also updated my H990DS successfully by "dirty" upgrade keeping all apps.
Click to expand...
Click to collapse
Thanks for your feedback!
Glad to know it is working correctly
Against 20a the only difference is s3curity patch?
faeterov said:
Against 20a the only difference is s3curity patch?
Click to expand...
Click to collapse
I'm not sure of any other difference except the security patch.
I assume there are some minor tweaks as the update notification
generally mentions "usability improvements", but LG being LG don't
release a change-log so who knows unfortunately...
I have installed v20b (stock room and rooted room), but this version do not support fingerprint sensor, terrible, it took me more than 2 days for this :crying::crying:
luuhungit said:
I have installed v20b (stock room and rooted room), but this version do not support fingerprint sensor, terrible, it took me more than 2 days for this :crying::crying:
Click to expand...
Click to collapse
You'll need to provide more details than this.
Which variant V20? What ROM did you come from? Did you backup partitions? etc.
Also: to add, this is normally a modem issue and is resolved by restoring / flashing the correct modem
jl10101 said:
You'll need to provide more details than this.
Which variant V20? What ROM did you come from? Did you backup partitions? etc.
Also: to add, this is normally a modem issue and is resolved by restoring / flashing the correct modem
Click to expand...
Click to collapse
maybe, thank for idea
i is using h900ds, taiwan version
yesterday, i used LGUP to flash v20b version with refusbish function, but second sim and fingerprint inactive.
maybe refusbish function did not flashed all partition on device
today, i have to flash v10c to use dirtysanta root, then flash all partition of v20b version, but ignore aboot to keep bootloader unlocked, it is using with old data partition very well.
luuhungit said:
maybe, thank for idea
i is using h900ds, taiwan version
yesterday, i used LGUP to flash v20b version with refusbish function, but second sim and fingerprint inactive.
maybe refusbish function did not flashed all partition on device
today, i have to flash v10c to use dirtysanta root, then flash all partition of v20b version, but ignore aboot to keep bootloader unlocked, it is using with old data partition very well.
Click to expand...
Click to collapse
Go to 10c root flash 20a partitions through Patched LGUP ignoring aboot aboot.bak and recovery recovery.bak (tarp may be gone but as long as you'll have boatloads unlocked you can flash twrp back)after that just flash only 20b system via LGUP Partitions DL I dunno whats going on with LG KDZs from now on all you should keep the old partitions from 20A and just flash system
jl10101 said:
Just please remember to flash MK2000 kernel after you flash the ROM without rebooting in-between.
I made the mistake of rebooting afterwards and the stock kernel restored the stock recovery and wiped my device.
(This wasn't an issue because I made a full backup of all of my data though)
Click to expand...
Click to collapse
unfortunately im using F800L, so it will not work if i flash this rom into my device.
is there any change to tell me how to update the security patch for my device?
thx b4 m8
can I use this patch for H990DS IDN (Indonesia version) that is still 2.0? It's dual sim version...
thanks
stingbandel said:
can I use this patch for H990DS IDN (Indonesia version) that is still 2.0? It's dual sim version...
thanks
Click to expand...
Click to collapse
Yes. Use mk200 beta38
Update to 20B and Just remember to back up firmware and efs folders from Oreo 20A and restore after flashing 20B otherwise you will lose the second sim
sniper9911 said:
Updated the dirty way flashed over my current ROM ... I wiped cache and art cache just in case
Seems legit and so far my device is finishing the data setting , i did make a backup of my firmware files just in case and so far it went smoothly
All i did was downloading the ROM , Twrp , mk2000 h990ds v2.1 And Magisk latest
Flashed Twrp first then recovery rebooted , wiped Dalvick and cache then flashed ROM then flashed mk2000 then magisk and phone booted
Thanks for the update
Click to expand...
Click to collapse
I followed exact steps in OP (wiped caches, flashed 20b ROM, Magisk 19.3, MK2000 v2.2b38 H990DS, rebooted) and thought it worked for me as well until I noticed some built-in system apps were not working. Calendar, Chrome and others had strange names in Apps list (Chrome was called "add to dictionary" and Calendar was something like "on time (%s,..."). I managed to get them working again by stopping them and reinstalling from the apk files in system but wasn't sure I woudn't have other issues, so I wiped system partition and reflashed it although it didn't seem to change anything. When I noticed Bluetooth wouldn't enable I decided to go back to 20a by flashing full ROM (all done through TWRP) but that didn't fix the issue. I had even tried going back to MK2000 2.1 but no change. Finally had to do full restore from TWRP backup to get BT working again. Would like to have latest security patch.
Does anyone have any ideas what went wrong? Could any Magisk modules cause issues? Any help is appreciated.
Works perfect.
I flashed it straight from Lineague 16.1 after wipe, no problems.
(LG H990DS)
albaniax said:
Works perfect.
I flashed it straight from Lineague 16.1 after wipe, no problems.
Click to expand...
Click to collapse
Good to hear! Thanks for the feedback!
Hi. H990DS Twn variant. Currently running stock rom 20a (first oreo rom released for 990DS).
I see that you've uploaded another stock rom for 990DS that is 20H. But security patch is from FEB.
But this is a newer thread, so I assume this is the newest release. Could you please just confirm if this is the rom I should flash.
Thanks in advance
Salvaparalyzer said:
Hi. H990DS Twn variant. Currently running stock rom 20a (first oreo rom released for 990DS).
I see that you've uploaded another stock rom for 990DS that is 20H. But security patch is from FEB.
But this is a newer thread, so I assume this is the newest release. Could you please just confirm if this is the rom I should flash.
Thanks in advance
Click to expand...
Click to collapse
I'm not sure why 20H is effectively a "newer" ROM going by LG's naming convention.
They used 20B (this ROM) with a newer security patch, and the actual file is newer than 20H.
I would normally assume that 20H should have a newer security patch and be a newer build of Oreo, but it seems not.
This ROM essentially is the latest available. I cannot find any changelogs to verify that 20H has a newer system / android build though. Sorry!
Hello,
first of all i want to mention that i have a special skill when it comes to choosing smartphones to buy. I like em small and cheap so i always had trouble installing custom roms when buying new phones. Just like this time, when i decidied that replacing my Galaxy S5 Mini screen for the fourth time is just not worth it anymore. I ran to the next store, checked the offers, found the Galaxy A20e, did a quick google "A20e lineage" saw there were a few install threads and decided to buy the phone.
That was on Thursday i have since then continuously tried to either root the stock firmware or flash TWRP to install Lineage GSI.
Whatever i try, when rooting with Magisk and afterwards booting the rooted OS using the recovery key combo, the touchscreen won´t work.
I can boot to the unrooted OS and use the touchscreen.
When installing TWRP using XDADEV guide, i can boot to TWRP right after install, wipe and flash required zip file but after the next reboot i can only boot into stock recovery.
Here´s what i did so far:
Software Used:
- Odin 3.14
- Magisk Manager App 7.5.1
- SamFirm 0.3.6
- downloaded the newest Stock firmware "A202FXXU3BTD1"
- unlocked bootloader / SamsungVault
- Flashed newest Firmware "A202FXXU3BTD1" using Odin.
- Installed Magisk Manager
- Patched extracted file "AP_A202....tar" from "A202FXXU3BTD1"
- Moved the patched AP file back to computer
- Flashed modified AP + stock BL, CP and Home_CSC again
- Wipe/Factory reset
- Start Phone with Power+Volume Up until Logo flashes, then release for rooted OS
- Touchscreen not working
- Boot Phone without root (just press Power Button)
- Touchscreen works fine
II then repeated the complete procedure with an Andoid 9 based FW "A202FXXU3ASL4" which ended with the same result.
Then i wanted to move on, since i always thought that Installing TWRP normally does not require root permissions.
I found several guides, some required root, some not. So i decided to try that. I Found two different testing versions, one from xda and flashed them regarding to the HowTo.
With the Android 10 stock firmware, odin was not able to install them at all.
The Android 9 Stock firmware was able to install TWRP and i was able to wipe and flash additional required zip file but after the next boot, i was only able to boot to stock recovery.
I will continue trying different Firmware versions, for now i want to go back to the newest stock FW since i have tried this one in the beginning of my research, maybe now, 15 hours of work later, i will manage to get it running =D
I am willing to provide further details, just let me know. Hope someone has an idea.
best regards,
Hannes
correcting
after frther testing, there is no way to boot into unrooted OS with working touch once magisk patched firmware is installed
GG
looks like reading and testing for 2 days built the right knowledge so after flashing the most recent firmware and only flashing the modified boot.img again (this was one of my first steps ever) this time it seemed to work.
Magisk is officially installed and the system is rooted. on to the next step, i´ll keep reporting.
on to the next one
I was finally able to get TWRP running after flashing Pie based Stock FW.
Now i am stuck installing Q based GSI, they just wont boot.
Pie based GSI work fine, is flashing Q based Stock FW required to install Q based GSI using TWRP?
SOLVED
hannes22 said:
looks like reading and testing for 2 days built the right knowledge so after flashing the most recent firmware and only flashing the modified boot.img again (this was one of my first steps ever) this time it seemed to work.
Magisk is officially installed and the system is rooted. on to the next step, i´ll keep reporting.
Click to expand...
Click to collapse
Could you be more specific on how you managed to root your A20e SM-202F? I've got the exact same issue with an unresponsive touch screen. My bootloader is unlocked, no problem there. I've tried three different firmwares (one of them being the exact same as stock, and the others are newer versions), and several different (but similar) methods. I've tried patching the firmware with both latest Magisk Manager and the canary version. I use latest Odin. I've also tried to patch both the full AP-file and the only the boot.img (boot.tar). But every time that I reboot into android after I've done the rooting I get a touch screen that's not working. I just can't get past that point...
The phone I'm trying to root has Android 10 and U3 bootloader, NEE version.
EDIT - The solution was to first download and flash the newest firmware _without_ using a patched Boot.img or AP.tar-file. I.e, patching the same firmware the phone had out of the box did NOT work. After the firmware update I could successfully flash the patched Boot.img file and root the phone.
Today my phone just boot looped. Can get to TWRP. But, I want to update A14 to 15, since it might allow the phone to start again. I flash stock Boot A14, that seem to work. Then, I try to flash the update to A15. TWRP gives me this error: fec_open "/dev/block/dm-10" failed bad address.
E2004: my_region.01000100 partition fails to recover.
What does this error mean? and, is there anything else I can do or try?
turns out i have an EU phone, with indian sowftware on it? Is it possible to flash it back to EU? And, how can i check the current version of the firmware in terminal ?
update: ok, it looks I am on version 11. Is there any link available to the boot.img from A10 and the incremental update to A11 (not the telegram link, does not work with a broken phone)? Both Indian and EU? Hope that redoing the update fixed the bootloop