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.
Related
TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
You're the man! Props for all the hard work you've put into this.
TY!!!!
Awesome. I might have to wait a bit to install but glad to see the Pixel getting twrp.
Sent from my Pixel XL using Tapatalk
Wow, and so it begins. Thanks!
Thank you!!
Nice!!! Awesome job @Dees_Troy
Sent from my Pixel XL using Tapatalk
I just installed the IMG w/out issue.
I can't find the zip in TWRP file manager to flash though.
Everything looks encrypted.
EDIT: It went through on the 4th try of flashing the IMG, now I can see my /sdcard and install the zip.
But somehow this killed my OS.
Just flashed the flash-all.bat after removing -w so it doesn't wipe.
Now I'll try TWRP install again.
EDIT 2: Okay, after restoring to stock, the TWRP install went fine.
Maybe it didn't like my elementalx kernel or the existing root. The OP did mention something about root conflicts, I guess it may prevent TWRP installs too? But now I have OS *and* TWRP.
And I'm getting "Unspecified Error" when trying to copy my EFS backup from /sdcard/twrp/backup to my local computer. I am able to copy other non-TWRP files though.
.
.
.
Does a full backup on Pixel include System Image and Vendor Image? I don't recall seeing these on other devices.
Or do I just back up boot, system and data like usual?
***Hey ya'll, don't forget to back up EFS at least once and copy it to your computers!
Yea! Worked perfect!!!
Would the flashable SuperSU v2.78 SR3 zip work?
Looked it up and because of conflicting init binaries between TWRP and the current root method, it just wouldn't work.
While we're still on or near the first page of the thread, I'd like to clarify the whole EFS backup thing.
It's completely unnecessary. You don't need to do it. But the option is there (so no one asks where it went!)
Both the modemst1 and modemst2 partitions are merely a caching area for your modem firmware. They do not contain sensitive data like IMEI, or anything important. You can wipe them and they will be regenerated from scratch! Have no fear, your IMEI cannot be destroyed through means of bad flashes!
The issue with these partitions however is that should they ever become corrupt, the modem firmware will panic and fail to load - this is why you see your IMEI missing in such a case. The modem firmware simply refused to load due to encountering corrupt data. By clearing your modemst partitions (writing zeros to them), your modem firmware would happily load and regenerate the partitions, bringing back full call support & a visible IMEI.
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Yep just want to let ya guys know might want return to stock before doing this. Besides that all good. Good job TWRP team! :good:
CZ Eddie said:
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Click to expand...
Click to collapse
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
FYI on OP - A SuperSU update will be required to allow TWRP and SuperSU to co-exist.
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
delete
CZ Eddie said:
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
Click to expand...
Click to collapse
Do we still flash root the same way after we install TWRP? Or is there an su zip to flash?
Hooray! Cheers!
Hello,
I write to tell you about my problem with a rear camera of my Huawei Y6 [SCL-l01][C432B140] and ask for any possible help. I really like to use it and i tried to get it back, but even after back to my firmware and stock recovery my camera doesn't work anymore[You cannot connect to the camera] after first rom flash.
Let's start from begining:
Once i decided to install custom rom on my phone, i done everything like it was on tutorials. I unlocked bootloader, i backup my data and i flash TWRP 3.1.2. Of course, TWRP didn't shown any error or issues, but my backup after restore, cause bootloop of my device and after second reboot startin recovery[not even bootloader of OS].
I tried many fixes to get my camera working on Custom Roms like AOSP, DARKNESS, CM,[ and few from HUAWEI Y6 thread] and I always fails. After few tries i gave up. My problem was that my backup was broken and my recovery was flashed by TWRP. Lucly i found stock recovery for my phone and flashed it.
Stock recovery gave my chance to install my stock rom from UPDATE.app, but after i install my stock lolipop 5.1 - my camera won't work anymore.[Can't connect to the camera, flashlight doesn't work too].
I tought to myself "hell, it could be problem that my original soft is modificated", but luckly i had two smartphnoes of my type SCL-l01[not mine ]. I took copy of working one by TWRP and flash it to my doesn't working... It gave the same result [I used TWRP by fastboot boot twrp.img for survive of my stock recovery] - camera simply wasn't work anymore even after flash the same firmware [once from update.app and second from another scl-l01]
And there is my question - Is it possible to get this camera working again?
Just pls - don't write to my about basics like clear cache or force stop etc , becouse i tried it all.
Thanks for every answer - and sry for my mistakes in my statement.
have the same problem for quite some time, I tried to return to stock with the update.app and the camera no longer worked, and I did not find a way to make the camera work. In stock it does not work, and in ROMS as LineageOS either, eh done the same thing to reinstall the update.app and neither, I think it could be a hardware problem
I clarify, I have a SCL-L03
link plzz
i ccant find the oficial room for scl-l01 cen you guys give me the link:cyclops::crying::crying::crying::crying::crying:
WantedG said:
i ccant find the oficial room for scl-l01 cen you guys give me the link:cyclops::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
http://huawei-firmware.com/rom/huawei-y6/scll01/1194
If you want to flash it, use huawei updater extractor and extract the system.img and boot.img from the update.app and flash it from fastboot.
Or if you have stock recovery make an folder Dload in sdcard and put the update.app here. After that, press power button and volume up and down (your phone needs to be shutdowned)
That's it.
Thanks button works well if I helped
My xperia X is my secondary phone that I use to experiment with ROM & Foss. It has unlocked bootloader, root & TWRP recovery installed. I was trying to upgrade from unofficial LOS 15 to unofficial LOS 16. It failed during flashing vendor image. While trying to troubleshoot this, I wiped & formatted data & repaired & mounted partitions & flashed some other images. NOw in the end, the phone has lost whatever files that help phone identify as Xperia X. As a result, no ROM is getting installed on the phone. Even when I tried to flash Sony's own firmware using Flashtool, it refused saying incompatible device. Xperia companion also does not recognize the phone.
Another problem is no matter what I do /vendor partition remains missing. I flashed sony binaries, TS partition backup, vendor.img file I found in another ROM but vendor partitions remains missing. I managed to flash LOS 15 again by modifying its script but it is not stable at all. The UI crashes, Apps crash, Phone restarts randomly. Can anyone tell me How can I repair my phone? Which files are needed to identify my phone as Xperia X & where can I find them ?
I think you just found a New way to hard brick
Flash an ODM.img on TWRP, I suggest you AOSP Nougat 7.1.1, then proceed to install a ROM or if you made a previous backup restore it
Your best bet should be Emma. Back when I was messing around with OmniRom, it managed to recognize my phone and flash stock fw back on it while Flashtool or Xperia Companion failed.
https://developer.sony.com/develop/open-devices/get-started/flash-tool
Remember, it's not a hard brick unless your hardware or the bootloader fails.
Some random said:
I think you just found a New way to hard brick
Click to expand...
Click to collapse
Well, its not hard-bricked since I can flash LOS 15.1 by editing a script in it. But like I said it becomes unstable.
GOrMHATRe said:
Well, its not hard-bricked since I can flash LOS 15.1 by editing a script in it. But like I said it becomes unstable.
Click to expand...
Click to collapse
Which Script???
Update: My phone has been repaired now. I guess repairing cache, system, data with twrp recovery & installing OEM image worked.
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.
Sorry if this is posted in the wrong place but I could not find anywhere to post it by following Help threads I just went round and round in circles. Hi I am fairly new to phone modding. I updated my moto e XT1524 to LineageOS 16.1 some months ago. Yesterday I decided to update to 17.1. I followed the instruction to install. I have wiped phone and ran fastboot adb as instructed. I keep gettting -This packeage is for XT1514,XT1524,XT1526......... ect and error7. I have ammended the updater-script as detailed in the "How to fix error 7 " document but the rom will still not load. same error message. I have now noticed that * Required * firmware version must be based on Marshmallow on the Installation section on the main forum page. Can someone help me get the phone back to stock rom or any other rom for that matter. I can get the phone into recovery mode and I have TWRP installed i aslo have SDK tools installed on PC.
@rddxda
TWRP can't be used to flash Stock ROMs. In your case you need QFIL ( read: Qualcomm Flash Image Loader ) to flash a Stock ROM, and also the Motorola USB driver installed on PC.
jwoegerbauer said:
@rddxda
TWRP can't be used to flash Stock ROMs. In your case you need QFIL ( read: Qualcomm Flash Image Loader ) to flash a Stock ROM, and also the Motorola USB driver installed on PC.
Click to expand...
Click to collapse
Thanks for your help, could you please help a little further as I cannot find a stock rom. I have been on the motorola site and followed a few links on the internet but only to find the file is no longer available. Any idea where I can get a stock rom from or can I use QFIL to load a non stock rom?
I have found a stock rom XT1524_SURNIA_RETEUALL_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml.zip this is not an mbn file, however if I open the zip folder there is a fsg.mbn file in there along with boot, bootloader gpt.bin etc. Is this the file to use with QFIL. Sorry to be a pain but I don't want to make the situation worse.
Also can you tell me if restoring to stock rom will this re-lock the bootloader?
UPDATE: First of all thank-you for all your help - I have learned a lot over the past 6 days (that's how long I have been trying to fix it). I flashed lineage-17.1-20200814-recovery-surnia and then sideloaded adb sideload lineage-17.1surnia.zip. Phone now rebooted in normal mode and showing on PC now OK. So old Moto E XT1524 on Lineage OS 17.1.