Related
Hey guys,
I spent all day to find a solution but I failed.
To start off, I've got a Sony Xperia L (taoshan), which I flashed with CyanogenMod using Clockworkmod.
Lately I updatet it to CyanogenMod 12 and slowly but steadily I got pissed because the CyanogenMod Recovery which was automatically installed with CM12 couldn't update to the next version, so I always had to manually flash the "old" boot.img of the cm11 in order to get a working recovery and then flash the new Version of CM12 which again blew out Clockworkmod.
Because I was annoyed of this I tried to install TWRP hoping it would solve that. Of course it didn't went as smooth as in any tutorial which would have been installing the app from the Playstore running it and done, but I had to flash it in the end.
So now TWRP "works". But it couldn't install the latest CM (a couple of hours have already passed, so I don't remember what the error message said or wheter there was a message at all)
Somewhen I did a full wipe to solve something but obviously it didn't work.
At some point I gave up trying to install the latest version and I started trying the Version I had running before. Luckily I still got the .zip of that very Version I flashed a couple of days ago using CWM, which means this .zip does definitly work!
But the sideload of TWRP does not work. The command promt says:"device not found" , while my Xperia L says waiting for input.
So I extracted my Micro Sd, plugged it into my PC copied the "Old" boot.img, that had CWM PLUS the .zip I intend to install and a .zip file with gapps I knew I had to install after the CM12.
After the transfer I repluged the micro sd back into my device and tried to install the CM12 ... .zip directly from the sdCard.
Well for a few seconds it looked like an installation process but then my phone directly rebootet TWRP without installing anything.
Then I tried moving the .zip onto the internal storage and install it from there.
There it says: "Error executing updater binary in zip..."
At that point I had enough of TWRP and tried to go back to my old method... Means
- turning the phone off
- extracting the boot.img from cm-11-20140827-NIGHTLY-taoshan
- setting my phone into fastboot by pressing volume up and connecting it
- open a commandprompt at the folder where fastboot.exe lies
- use fastboot flash boot "path to boot.img" to flash CWM onto my device
- use fastboot reboot and then volume up at the purple light to go to recovery, which should be by then CWM
And I saw a nice blue logo of Team Win Recovery Project and I wanted to cry...
So in Summary I searched a lot of Sites for a solution but didn't find a single one to solve one of my Problems...
For the lazy ones:
- I cannot use Sideload because the commandpromt doesn't recognize my phone... however it did when using CWM
- I cannot install it from my SDCard, because it reboots without doing anything
- I cannot install it from the internal storage because "Error executing updater binary in zip
- I cannot use CWM because if I flash the boot.img that brings about CWM nothing happens and I still have TWRP
Well I am at the end of my knowledge and I truly hope one the answers I get here work out.
Hi
Thanks for writing to us at XDA Assist. For future reference you can find your specific device forum here (bookmark/subscribe this):
Sony Xperia L
Within that section you will find a dedicated q&a sub-forum:
Xperia L Q&A, Help & Troubleshooting
Please go ahead and ask your question in that q&a section.
Good luck!
Thread closed, thanks.
I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files
cgrimm9 said:
I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files
Click to expand...
Click to collapse
Did you fastboot boot into TWRP, then flash twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip? Were you stock prior?
Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal
cgrimm9 said:
Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal
Click to expand...
Click to collapse
Yes, you are not supposed to install twrp, just boot into it. If you install it by mistake, you go back, flash stock boot.img, and do it again.
This is from Dees_Troy's post located here
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314
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.
@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Tulsadiver said:
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.
Click to expand...
Click to collapse
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...
alienjon said:
@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...
Click to expand...
Click to collapse
Things have changed with 8.1. you have to root with magisk. From slot b you cannot fastboot flash boot_a boot.img?
I believe the instructions now are to boot to TWRP, install TWRP pixel installer zip, then flash Magisk zip
Here is where TWRP files are here
https://dl.twrp.me/sailfish/
Tulsadiver said:
From slot b you cannot fastboot flash boot_a boot.img?
Click to expand...
Click to collapse
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)
alienjon said:
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)
Click to expand...
Click to collapse
Yes, the zip file that is located where the flash-all.bat is. Unzip it and flash the boot.img.
I bought a Pixel 2 on swappa. It had different bootloader's on slot a and slot b. I couldn't flash updates when on slot a. I thought I was hosed but from slot b I could flash to slot a so now I'm fine. Slot a had a preview bootloader.
Hello, I would like some help since I got this device just yesterday.
I got it with the EMUI 4 Android 6.0 stock installed on it. Since there was no update for it I unlocked the bootloader installed twrp rooted and manually flashed EMUI 5 7.0. Everything worked fine.
I created a backup through TWRP and restored it succefully multiple times.
Then I installed the Meticulus TWRP (since I was told it is a prerequisite for the AOSP). I Flashed the AOSP but it stuck during the boot animation (30 minutes afterwards I powered it off).
I reflashed my old TWRP and tried restoring my backup. IT fails with the explanation "Cannot wipe /vendor" while at the top it says "Cannot mount /vendor (invalid argument)" "Cannot mount /product (invalud argument)".
Anyone has a clue how to fix this? Fastboot adb all works so there should be a way to boot into an OS properly?
Since AOSP was not booting i guess you forgot formatting /data partition to ext4... And did u Used Stock vendor and not openkirin ones ?
Gesendet von meinem Honor 6X mit Tapatalk
As said I have replaced the custom TWRP with the default one so I think this should not apply anymore?
The "cannot mount vendor/product" messages came from the default TWRP after I reflashed it again.
At the top it says "cannot mount /vendor" either so I guess that is the actual problem?
It would be nice to get teh AOSP up but I really want to be able to boot into something first honestly.
And did u Used Stock vendor and not openkirin ones
Click to expand...
Click to collapse
Can you please explain? When I flashed your ROM i was on your TWRP. Does this even matter anymore?
At best I would be able to restore my backup.
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
algg said:
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
Click to expand...
Click to collapse
Yes you can but not creating it through twrp, but flashing it by fastboot mode: this is because
image (.img) files needs to be flashed by fastboot mode to avoid any kind of problem.
So, you should look for the last version of stock firmware on which you was before going custom, like BLN-L21CXXXB368 for example; tell me your build number and I'll find the package for you. Then, extract from the UPDATE.APP (a very big file that contains every partition in your phone like recovery, vendor, data, ecc. - you'll find this file inside the zip archive that contains the downloaded update) the vendor.img using Huawei Update Extractor, and then flash it through fastboot mode using the command "fastboot flash vendor vendor.img".
Otherwise, you could rely on dload method to reflash a full update package, and this should really fix everything since that it'll be like a new and clean installation of the OS. Then, unlocking the bootloader again and reflash TWRP to finally restore your previous backup made when it was working would be the final step.
Feel free to ask for further help
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
algg said:
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
Click to expand...
Click to collapse
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload because package verification always failed at 5%, i tried every combination but without success.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
RedSkull23 said:
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload, i never be able to using it successfully because package verification always failed at 5%.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
Click to expand...
Click to collapse
For fastboot yes flashing recovery or boot do work but vendor does not. Maybe the ISO is corrupted somehow I will try it again on a different machine now with the tool.
The link you posted the dload method from is the one where I initially found it as well so yea.
Also it shouldn't matter what I install since the only thing I need is the actual vendor (and product?) partition to work. I have a functional backup just TWRP cannot create/mount the partitions. So even a way to just create them without any data would actually fix my problem (at least I hope so?)
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
algg said:
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
Click to expand...
Click to collapse
@RedSkull23, thanks for the tag mate.
@algg, No need to flash the vendor image as you already had the stock vendor img.
Now what else you can try is to flash the stock recovery, boot to stock recovery, select factory reset and reboot. It should most probably fix the issue.
If not, reflash the TWRP, a regular TWRO available and not specific to elite or meticulous, but generic one given by OldDroid.
I hope you have downloaded the content for dload, if not, download these for B140.
Flash this via TWRP- http://update.hicloud.com:8180/TDS/...afnaf/update_data_full_BLN-L21_hw_meafnaf.zip
no further changes and Then use dload method for this file- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v105054/f1/full/update.zip
Try above and provide feedback. This is what I could think of best possible way to have everything with all system app working.
If not, let me know and I will try to help further.
Hi, I thought I need the vendor image since TWRP (all versions) tell me "Could not mount/wipe vendor" and "Could not mount/wipe product" "invalid argument" for both.
I tried the factory reset before but it does not work. It stops at 23% then shows a red exclamation mark and just goes to the original screen with the 3 buttons (restart, shutdown and wipe).
I am currently trying to get it to recognize my sd card. But somehow it does not work through TWRP it just does not recognize the 8GB SD Card. Also I am currently on the TWRP I was before all of this happened (3.1 openkirin). Without the SD Card recognized I can't put the dload files for it on it and in turn I can't use the dload.
I mean technically it should very well be possible to fix the device since it isn't a real brick and even TWRP and Fastboot load. It's just that all those little things are somehow ruining it.
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
algg said:
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
Click to expand...
Click to collapse
Sure, let me explain.
The first file is the data file which will install few systems apps like file manager, updater, themes, clock, fm radio etc. This will work via dload as well but the installation time is around 3-7 seconds so, over the course of time and flashing few times, i realised that these PV files cannbe flashed via TWRP and it works perfectly fine specific to PV files( twrp won't supoort other stock zips). We foash this first so that it updates your buld number and also does not replace the recovery with stock (as if you flash the main update zip first, it will replace with stock recovery so flashing the 2nd file will be quick but with unstable system apps, sometime).
Now we flash the main zip file with update.app via dload and it Install the main firmware for boot, vendor, recovery, system, usrdata etc.
Hope this explanation helps, if not let me know and I will rephrase myself.
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Is there any way I can "debug" what is going on while the boot animation is playing?
What is confusing me is that the boot animation plays just normal but it simply does not continue to the actual OS.
algg said:
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Click to expand...
Click to collapse
Not bricked..its just Data is not mounted or encryption. Should never encrypted it. NVM.
Do one thing, boot to twrp recovery. Try flashing and get error, then go to main TWRP page and click on reboot, select recovery out of 4 options( power off, system, bootloader and recovery). It will boot to recovery, now try flashing it again and see. Most if the time it helps.
Else, go to main page, select wipe, click on format rather than wipe here, it will prompt for typing Yes to confirm. Biit to recovery from main twrp page ( as mentioned above). And try this same thing of formatting data couple of times and then flash the zip and then dload.
I know these are tedious steps but inhave revived my device many a times with all these tricks after some efforts.
Good luck
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
algg said:
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
algg said:
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
I'm happy for you man, indeed it would be so bad, especially because you got this device 3 or 4 days ago if i didn't read bad, anyway what matters is that now it works. Are you able to restore the previous backup through TWRP now? (But before trying... Make a backup of your actual OS )
shashank1320 said:
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
Click to expand...
Click to collapse
Are you joking man? I just tagged you for more help, but practically you helped him in everything, not me; I'm sure that you would noticed the thread and helped as always even without my tag, i just speeded up things for being helpful to algg.
algg, I'd like to apologize myself; i didn't vanished after tagging shashank, today i just was at work and obviously i was busy for help, but as i saw with pleasure he already helped you to restore your OS and that was the objective. Nice one, guys!
Hello, I was searching for a root for my "new" Samsung J3 Prime (SM-J327W) that I got from my sister. I did the OEM Unlock and in ODIN Mode, it says that it's also "FRP LOCK : OFF". So far, CF-Auto-Root didn't work and all TWRP images, that I found, wouldn't even download on the device . I tried images for the "T", "P" and "U" variants also. The "P" one, lead to bootloop (I recovered stock rom since I got it). So is there any root for this device? It's on the latest versions of firmware and Android available for it.
Did you find anything for the J327W yet? I can only find ROMs for the 320, 327P and 330. I've been having very erratic battery life for over a year. It started after a factory android update. Sometimes my battery life will drop from 70% down to less than 5% in a minute. I've done a factory reset, cleared the cache and replaced the battery but nothing has helped. Trying to put a new ROM OS on this POS is my last hope.
shane_c said:
Did you find anything for the J327W yet? I can only find ROMs for the 320, 327P and 330. I've been having very erratic battery life for over a year. It started after a factory android update. Sometimes my battery life will drop from 70% down to less than 5% in a minute. I've done a factory reset, cleared the cache and replaced the battery but nothing has helped. Trying to put a new ROM OS on this POS is my last hope.
Click to expand...
Click to collapse
I think you'll need a battery replacement at this point... I did build a TWRP ROM myself for my popeltecan (code name of J327W in Canada apparently) but, according to a TWRP Builder Developer, my device might have some kernel issues with TWRP so I can share my ROM but I am not sure it will work on your device. Do you have your stock ROM in case?
Here is a GDrive link to my recoveries, there's the stock and the twrp one but be aware that you need all the ROM if there is a problem with the twrp (that means stock : BL, AP, CP and CSC). But you can use the stock recovery to build a device tree.
https://drive.google.com/open?id=1dNZGaNvCtd5kinHNfnr8MV5Z6o2_GOj4
MikasuX14 said:
I think you'll need a battery replacement at this point... I did build a TWRP ROM myself for my popeltecan (code name of J327W in Canada apparently) but, according to a TWRP Builder Developer, my device might have some kernel issues with TWRP so I can share my ROM but I am not sure it will work on your device. Do you have your stock ROM in case?
Click to expand...
Click to collapse
Replaced the battery about 3 months ago but it made no difference. I have some vacation time coming up so will have a little more free time to look into things.
shane_c said:
Replaced the battery about 3 months ago but it made no difference. I have some vacation time coming up so will have a little more free time to look into things.
Click to expand...
Click to collapse
Maybe a factory reset would be a good idea to try. If you want to try my twrp recovery build, you'll be wiping your data anyway. I highly suggest you to get the full stock rom since even just getting back the stock recovery could end up with a weird sort of corruption (like duplicated or unknown options inside the Settings app, or at least I experienced that). I am not responsible if it breaks anything, you were warned to get your precautions such as getting the stock rom.
MikasuX14 said:
Hello, I was searching for a root for my "new" Samsung J3 Prime (SM-J327W) that I got from my sister. I did the OEM Unlock and in ODIN Mode, it says that it's also "FRP LOCK : OFF". So far, CF-Auto-Root didn't work and all TWRP images, that I found, wouldn't even download on the device . I tried images for the "T", "P" and "U" variants also. The "P" one, lead to bootloop (I recovered stock rom since I got it). So is there any root for this device? It's on the latest versions of firmware and Android available for it.
Click to expand...
Click to collapse
hi if your still looking. i looked into it and the j327u twrp does work on j327w. i had the same problem trying to gain SU access with the other image files for j327w i had to use magisk zip and install it from twrp menu. had to format data and mount system in twrp.
twrp j327u does work but i could not get supersu or magisk to work, my build is J327WVLS4BSK1 with 8.1.0 oreo. i'm not sure there's a way to get past dm-verity using the boot patch by asphyx in the TWRP threads or the universal dm-verity workaround by zackptg5.
i first flashed twrp j327u using odin, ran up against dm-verity when running supersu. both MikasuX14 and another twrp j327w version i found would also flash and load, but the touchscreen wouldn't register my input. cfar didn't work either
sfirmware (website) has workable firmware for rev 4 j327w builds in case you need to recover your phone from soft brick - i could get my build's firmware to flash using the patched odin 13.3.3 version found on this site
bytwigorlimerick said:
twrp j327u does work but i could not get supersu or magisk to work, my build is J327WVLS4BSK1 with 8.1.0 oreo. i'm not sure there's a way to get past dm-verity using the boot patch by asphyx in the TWRP threads or the universal dm-verity workaround by zackptg5.
i first flashed twrp j327u using odin, ran up against dm-verity when running supersu. both MikasuX14 and another twrp j327w version i found would also flash and load, but the touchscreen wouldn't register my input. cfar didn't work either
sfirmware (website) has workable firmware for rev 4 j327w builds in case you need to recover your phone from soft brick - i could get my build's firmware to flash using the patched odin 13.3.3 version found on this site
Click to expand...
Click to collapse
heres what i did. i soft bricked, bootlooped and had to flash firmware from sfirmware a few times to get it to work
i used a twrp for j327u i found on a another similar thread on this topic. i flashed it with odin.
once inside twrp menu i went to wipe menu, i hit format, then back to mount menu, checked boxes data/system (previously data or system wouldnt check off before formatting data).once data and system were mounted i then
plugged phone back into computer while in twrp menu. the phone showed up as J327u cut/paste the latest magisk .exe into the internal storage of j327u (on computer) . i then on twrp menu found and installed magisk exe finally got it to properly install magisk i then in reboot menu hit system and reboot.
the phone restarted after awhile like it was factory reset but once i set up the phone magisk apk was already installed and root access was available. hope this helps.
so i've been busy for a long while before looking back into this. I will try again with the J327U rom. Right now, i struggle to find stock roms of the J327W because i flashed a not working twrp apparently and it locks my boot.
The J327U TWRP didn't work for me. Though, twrp itself works but i cannot get the system to boot and i cannot get to root it, no matter what i tried, i ended up in boot loop.
I managed to root this phone without TWRP. I used Linux tools to do this so I'm not sure if it could work on Windows.
Requirements:
Stock ROM for your phone (I used samfirm.js to pull it from the Samsung servers but downloading from sammobile.com works too)
A way to extract zip files
A way to extract tar files
Heimdall flasher (https://www.glassechidna.com.au/heimdall/)
Magisk Manager APK
An Internet connection on your phone
A compatible USB connector for your phone
Of course, a SM-J327W running the stock Android firmware
Obligatory warning: This WILL void the warranty of your phone and permanently trigger the warranty void flag. It also WILL cause a factory reset, so back up all your data first.
Bear with me, because there are a lot of steps. This will take around 15 to 30 minutes.
You will need to download and extract a stock ROM for your phone. Make sure that you download a ROM for the SM-J327W and not another model. Also make sure to download the latest version available.
Stock ROMs usually come in a zip file containing a few tar.md5 files. You will only need to extract the one that starts with "AP" for this procedure.
Step 1: Extract the tar.md5 file that starts with "AP" from your stock rom.
Step 2: Open the tar.md5 file in an archive manager. You may need to remove ".md5" from the end of the file.
Step 3: Extract the boot image (boot.img) from the AP file.
Step 4: Upload the boot image and the Magisk Manager APK to your phone. You can use ADB to transfer the files. For example:
adb push boot.img /storage/emulated/0
adb push Magisk-v22.0.apk /storage/emulated/0
Step 5: Open the files app on your phone. Navigate to the internal storage and tap on the Magisk APK file to install it. You may be prompted to allow installation from unknown sources.
Step 6: Open the Magisk app. It should say that Magisk isn't installed and it shoulld say "Yes" beside "Ramdisk". Tap the cogwheel icon in the top-right corner.
Step 7: Due to a bug in Magisk, you need to install version 21 instead of the latest version (v22). Set the update channel to "Custom Channel".
Step 8: When prompted, enter the following URL: "https://raw.githubusercontent.com/t...d863d3a15c6a2276b1061a280ece80ed7/stable.json" (Without the quotes.)
Step 9: Now it's time to patch the boot.img file. Tap the button to install Magisk and select the option to patch a file. When prompted, navigate to the internal storage and select the boot.img file that you transferred previously.
Step 10: Magisk will patch the file and tell you where it saved the patched file. Transfer the patched file to your computer. You can use ADB for this, for example:
adb pull /storage/emulated/0/Download/magisk_patched_XXXXX.img
Remember to replace the Xs with the the random characters that Magisk added to the file name.
Step 11: Reboot your phone into Download mode. You can shut it down and then hold the power, home, and volume down buttons at the same time to enter Download mode or use ADB: "adb reboot bootloader"
Step 12: A warning may show about the dangers of installing a custom OS. Press the volume up key to continue.
Step 13: The screen should now show "Downloading... Do not turn off target." If your phone isn't already plugged into your computer, plug it in now.
Step 14: Use Heimdall flasher to flash the patched boot image. For example:
heimdall flash --BOOT magisk_patched_XXXXX.img
Again, replace the Xs with the random characters that Magisk added to the file name.
Step 15: After a few seconds, Heimdall should report that the flash succeeded and your phone will reboot. It may take longer than usual. Leave it to do its thing and DO NOT pull out the battery.
Step 16: Your phone will show a notice that unauthorized changes have been detected and will prompt you to factory reset it. Press the button to perform the factory reset.
Step 17: Set up your phone as if it was new. It's not rooted yet, but you're really close if you got so far.
Step 18: Once you reach the home screen, upload the Magisk Manager APK to your phone again and install it like before.
Step 19: Open Magisk Manager. It will show that Magisk is installed and may prompt you to reboot to complete installation. Do not update Magisk to v22 or you will lose root access and you will have to flash the patched image again.
In the (very unlikely) case that your phone doesn't boot after flashing the patched boot.img, you can simply flash the original boot image and it should be fixed.
CONGRATULATIONS! You just rooted your SM-J327W successfully.
I also managed to port TWRP to this phone with the touchscreen working using the kernel from a recovery image for the SM-J327P found here: https://forum.xda-developers.com/t/...-1-samsung-galaxy-j3-emerge-sm-j327p.3573607/. All the partitions are mapped correctly. Due to a bug (presumably with the kernel), the data partition can unfortunately only be mounted read-only. However, this shouldn't affect being able to flash zips on your phone and you can insert an SD card to write backups onto. In the future, I may port CWM recovery to this phone using the stock kernel to be able to mount the data partition read-write.
You can find my custom recovery attached to this reply.
Follow up: It seems that the bug that causes Magisk to fail is fixed in the latest version (v22.1.) As a result, steps 6-8 in my previous post are unnecessary.
MikasuX14 said:
Here is a GDrive link to my recoveries, there's the stock and the twrp one but be aware that you need all the ROM if there is a problem with the twrp (that means stock : BL, AP, CP and CSC). But you can use the stock recovery to build a device tree.
https://drive.google.com/open?id=1dNZGaNvCtd5kinHNfnr8MV5Z6o2_GOj4
Click to expand...
Click to collapse
link is dead do you have twrp for j327w?
First version shared was twrp 3.2
New version is 3.3.0
***ORIGINAL TWRP is not my work. Only the porting of it to this device. I take no credit for the source.
*** DISSCLAIMER ALLERT***
I started having issues with encryption coming back to enforcing when using the Ported Team LR TWRP 3.3
Did not have trouble yet with OMFG-Mod version.
Also @ghost45 has made a build of twrp 3.3.1 for F1. It works good as well
https://forum.xda-developers.com/showpost.php?p=79651368&postcount=49
--- all versions give trouble of loosing IMEI when using the remove force encryption patch I suggest below. Left logs with @Zackptg5 .
**May need more testing**
-decryption is broken
-MTP is working
-ADB is working
****--Advanced menu items are not correctly on 3.2 version.
-- Some of the advanced menu was fixed in 3.3.(install root is working)
- Advanced menu has extra features.(all from source twrp)
-- install magisk (currently has V17 on OMFG V19 on LR TEAM)
-- patch dm-verity and force encrypt remove.zip. ( personally I prefer the universal dm-removal patch from xda)
-- Remove system password, (from original dev, I have not tested)
--
--Install (basic directions only)--details may be added later if needed
Open zip and fastboot flash the recovery image if bootloader is unlocked.
or
Open zip , then open scatterfile (scatter file in test 1 has issue, updating it in next test )with sp-flashtool , select download
--First boot into TWRP will give errors for unable to mount /data. This is from the force-encryption.
- When boot into TWRP, select wipe -> format type 'yes' to format data
- When format is done, return to TWRP home page, select reboot -. recovery
--Now Patch device so no longer forces encryption
-- Use built in feature from 'Advanced Menu' or use the following directions--Fails to unpack boot. (current zip used is not compatible with system-as-root boot.img)
-To remove this I use 'Disable_Dm-Verity_ForceEncrypt' from
-- https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt -- currently based on magisk V19.2
-Download from the "Clone or Download" button on the above linked Github Page.
-Unzip the downloaded file. You will have a folder with same name as the zip package. Browse inside this folder, select all files and zip them.
-Put this new zip file onto your phone. ( Hay notice the MTP function on this TWRP works)
- in stall the zip like any normal twrp package.
--Next Install Magisk
--Use Built in Root Option from 'Advanced Menu' to use Magisk V19 or the following direction
- Goto the releases page of magisk github page. ==>LINK
- Download latest Magisk zip , Put file to phone, Install.
-- Download Folder For TWRP Ported from OMFG-Mod
https://www.androidfilehost.com/?w=files&flid=294886
-Screenshots.
- Ported OMFG-MOD gold Button TWRP V3.2
- Ported Team LR TWRP 3.3 standard Button
Attached Below
--Thanks --Mentions
recovery source from [LR TEAM] MIUI
http: //www.miui.com/forum.php?mod=viewthread&tid=19006123&page=1&mobile=2#pid257831639
link is newer version from ported recovery. They updated recently. Next port may use newer base as well.
hello @ColtonDRG. Long time.
I see you posted in umidigi forum that bootloader is not checking signature. So you CAN flash images with flashtool without unlocking. Is that correct.?
I have based the above install guide on that fact that you CAN.
But the first twrp posted by "ghost45" says no it must be unlocked.
edit:
I should be able to verify later today or this weekend, when my order arrives.
OK, verified, when i used flash tool and put twrp on phone before unlocking bootloader, on reboot I was stuck in "RED" status for boot loader. So must unlock
Flash this zip to remove the AdupsFota app
this is the update app. You will not be able to install OTA when rooted and twrp anyway, And if an OTA comes you will get stuck in recovery bootloop. So this flash file will rename the 2 apk related to OTA download and Force reboot that supposed to install that update.
Reserved
Will keep this post for working on issues .
Right now , I discovered after playing with the built in dm verity patch and root install lead imei's getting erased.
Restored the full rom with flash tool fixed, will update process as necessary
Restarted from the top again.
--1 Full stock rom flashed with sp flash tool.
--2 Twrp flashed in flash tool
--3 format /data, reboot recovery
--4 use mtp to copy Disable_Dm-Verity_Forceencrypt to phone
--5 flash the decrypt zip. And at the end of flash the output log showed 'failed to mount /nvdata file not exist'
*** Waiting for input from the Patch dev. Others on his xda thread with MTK have had similar trouble***
--6 use mtp , put stock recovery file on phone. Image flash stock recovery, reboot recovery, do factory reset in stock recovery. This fixed the /nvdata error.
--7 sp flash twrp again, use built in 'install root' option from advanced menu.
Bam all done
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
ghost45 said:
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
Click to expand...
Click to collapse
Thank you, this one has no displayed errors.
I have question though.
Do you know how to make system be mounted as /system instead of /system/system ?
Hey, buddy. Good to see you on the forums again. When I picked up this device I wondered if anyone from the R1 HD days would also be on it. I seem to have misplaced mine but I'll find it eventually, send me a DM if you wanna talk about it. I'm not 100% sure about this, but the bootloader verifying signatures might have been patched in because I don't remember mine doing that when they first came out. Of course even if it does, SPFT is still useful for unbricking and downgrading, but I really doubt UMIDIGI will patch out the unlock option like BLU did.
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
ColtonDRG said:
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
Click to expand...
Click to collapse
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
mrmazak said:
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
Click to expand...
Click to collapse
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
ColtonDRG said:
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
Click to expand...
Click to collapse
We have the twrp file copied to telegram group also. I'm stuck on mobile, or I would just copy the twrp here.
UMIDIGI
UMIDIGI unofficial TG group
https://t.me/UMIDIGI
Disable_Dm-Verity_ForceEncrypt failed
Hello, I'm trying to patch my F1 using the Disable_Dm-Verity_ForceEncrypt, but am stuck with an error "Dumping/splitting image failed. Aborting..." This occurs when I try using the Install from twrp. Has anyone encountered this issue before? I have done a wipe, and also tried installing Magisk (which installs fine).