Hi, I've posted here before but now I made sure I did my research
I recently flashed Resurrection Remix from OpenKirin's website. Link: https://forum.xda-developers.com/ma...pment/roms-openkirin-aosp-collection-t3828794
After this my FRP is locked, my Bootloader is unlocked.
- I can't flash anything through Fastboot (system/recovery/kernel). And I also cannot install a custom recovery to flash other files.
- In Developer Options the OEM Unlocking is greyed out. So I can't change anything
- If I try to Factory Reset in the options of the Settings menu, nothing happens.
- Trying to unlock the FRP through fastboot: fastboot oem frp-unlock doesn't work because I don't know the password it's asking.
I'm considering to get DC-Unlocker but I'm not sure if that's gonna help me any further.
Thank you for reading.
Did you delete the Google account manually?
FRP Locked for Mate 10 Lite Solved
dabateau said:
Hi, I've posted here before but now I made sure I did my research
I recently flashed Resurrection Remix from OpenKirin's website. Link: https://forum.xda-developers.com/ma...pment/roms-openkirin-aosp-collection-t3828794
After this my FRP is locked, my Bootloader is unlocked.
- I can't flash anything through Fastboot (system/recovery/kernel). And I also cannot install a custom recovery to flash other files.
- In Developer Options the OEM Unlocking is greyed out. So I can't change anything
- If I try to Factory Reset in the options of the Settings menu, nothing happens.
- Trying to unlock the FRP through fastboot: fastboot oem frp-unlock doesn't work because I don't know the password it's asking.
I'm considering to get DC-Unlocker but I'm not sure if that's gonna help me any further.
Thank you for reading.
Click to expand...
Click to collapse
This happened to me and I was saved by a Dev on Mate 10 Lite thread named @KingOfMezi. This happens when you enable Developer Options and then select restore defaults.
Download zip file from link below and flash it in TWRP but remember I was on custom emui 8.0 oreo rom not on resurrection rom. Still chances are heavy that it will work
https://mega.nz/#!nw0wAYoA!hYtf78s0AjwRCpPo_NQ2F4LYclngNBNurJNETypSNKQ
connnor kenway said:
Did you delete the Google account manually?
Click to expand...
Click to collapse
Yes, multiple times. To the point where there were no accounts left
maniwaraich said:
This happened to me and I was saved by a Dev on Mate 10 Lite thread named @KingOfMezi. This happens when you enable Developer Options and then select restore defaults.
Download zip file from link below and flash it in TWRP but remember I was on custom emui 8.0 oreo rom not on resurrection rom. Still chances are heavy that it will work
https://mega.nz/#!nw0wAYoA!hYtf78s0AjwRCpPo_NQ2F4LYclngNBNurJNETypSNKQ
Click to expand...
Click to collapse
Yeah I would've tried this already if I were actually able to flash anything. I only have the stock recovery and no TWRP available.
I also can't flash a new recovery so it's a dead for me in both ways.
Small update - I have tried unlocking it with DC Unlocker but even though I paid for it, the program couldn't get rid of the FRP lock on the phone.
I'm considering to just call it a dead device at this point.
Edit - 8 April 2019
I've managed to relock the bootloader after some more fiddling around.
However I'm now stuck; the phone only boots into eRecovery.
I can do two things now, aside from (re)booting, clearing cache and wiping data:
* Try to download firmware through WiFi, which fails after a short time with the message "Getting package info failed"
* Try to use the 'dload' method. At 5% it stops and says "Software install failed!". I already formatted the SD card to NTFS and the only file that's on the card is the UPDATE.APP that I got through FirmwareFinder. That file is inside the 'dload' folder, yes.
Any ideas?
Bump.
dabateau said:
Small update - I have tried unlocking it with DC Unlocker but even though I paid for it, the program couldn't get rid of the FRP lock on the phone.
I'm considering to just call it a dead device at this point.
Edit - 8 April 2019
I've managed to relock the bootloader after some more fiddling around.
However I'm now stuck; the phone only boots into eRecovery.
I can do two things now, aside from (re)booting, clearing cache and wiping data:
* Try to download firmware through WiFi, which fails after a short time with the message "Getting package info failed"
* Try to use the 'dload' method. At 5% it stops and says "Software install failed!". I already formatted the SD card to NTFS and the only file that's on the card is the UPDATE.APP that I got through FirmwareFinder. That file is inside the 'dload' folder, yes.
Any ideas?
Click to expand...
Click to collapse
You need actual dload firmware for dload, from androidhost.ru.
Regular firmware from FF is online only, hence it needs to auth to install. Offline firmware, which is used for dload, does not need to auth to install.
You could also try eRecovery install method using FF, you would need to set up a dns in your router though.
But dload should work fine.
Also, I too had OEM Unlock greyed out before. For me it was enough to connect to wifi and then Restore Default in developer options, this made it available again.
ante0 said:
You need actual dload firmware for dload, from androidhost.ru.
Regular firmware from FF is online only, hence it needs to auth to install. Offline firmware, which is used for dload, does not need to auth to install.
You could also try eRecovery install method using FF, you would need to set up a dns in your router though.
But dload should work fine.
Also, I too had OEM Unlock greyed out before. For me it was enough to connect to wifi and then Restore Default in developer options, this made it available again.
Click to expand...
Click to collapse
Oh well, I relocked my bootloader and sent the phone to the retailer.
They replaced the motherboard (I think?) as it said "defective components replaced".
All good now, but my inner flashoholic can't just sit still
Related
So i got my Honor 5x yesterday and thought i would install a custom rom on it since people are recommending it.
Its my first time so i followed guids. I installed adb and fastboot and managed to get TWRP 3.1.1-0- on it.
Btw, i have a Honor 5x
Model KIW-L21
I am able to get into the recovery TWRP. I made a backup and saved the folder "BACKUPS" on my PC.
I then downloaded LineageOS from their Homepage: download (DOT) lineageos (DOT) org/kiwi
I downloaded the latest version. I also downloaded Gapps from Opengapps.org. I downloaded ARM64 version 7.1
I wiped my phone completely and copied the two zip files on the phone. I went to "install", selected LineageOS zip and added Gapps. i swiped right to install and the installation stopped with ERROR 7
I tried to download older versions of LineageOS but the same thing happens. ERROR 7
I then downloaded an olderversion of CM13 with GAPPS 6.0. Again, Error 7
I downloaded XENON HD ZIP from here: mirrors (DOT) c0urier (DOT) net/android/teamhorizon/N/Official/kiwi/
Error 7
I downloaded ASOP from here: downloads (DOT) aospextended (DOT) com/kiwi/
Error 7
I looked up Error 7 and its says it is a security check that figures out, that the ROM is not compatible with the Phone. Some guy told me that this happens a lot and that i should use another rom.
I looked for a solution on youtube and found a guy who said that i can do the following:
Unzip the ROM on your pc, go into \META-INF\com\google\android and open the updater script with Notepad++. Delete the first two lines that says asserts, save, close it again and zip the whole package again.
I copied the new, modifiled rom on the phone with the GAPPS and installed it. This time ERROR 7 didnt appear. GAPPS were also installed. When i boot my device i get in the loading screen from Lineage for about 5-10 minutes. After that, it just restarts and restarts and restarts. I can't get out of the boot loop since I can't remove my battery. when I press VOL UP I come back the TWRP and can wipe the phone again.
I tried that with 3 different LineageOS ROMS and one XENON HD ROM.
I also get into a boot loop where my phone just restarts and restarts and restarts.
I tried to get my backup working so I copied the folder "BACKUPS" on my phone and went to restore in TWRP. but... i found nothing there?
I am super frustrated since my phone is basically dead and I have no idea what I can do.
BTW, every site calls my phone "KIWI" but my model number is "KIW-L21"
As mentioned in Los 14.1 thread (& should be mentioned in all threads), "ROM Firmware Required: No VoLTE firmware! (B360, B370, ...)". You must downgrade your stock rom to B350 at least, before try playing with custom roms (only for kiwi, of course).
Non VoLTE Marshmallow firmware is required. As said by @mauam get in there and have the same process repeated
Thank you for your replies.
The only thing i could find was this thread: https://forum.xda-developers.com/ho...-lineageos-14-1-pre-official-kiw-l24-t3528488
It said there:
Important note:
Stock Firmware B360 and B370 are known to cause bootloops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
It doesnt mentioned what that mean and even said "dont ask in here how to downgrade"
I have no idea what all that means. I dont know what stock firmware is, what version i have or how i could downgrade it. I can access TWRP, but still have no OS on it.
edit: this is the full log:
Updateing partition details...
... done
Full SElinux support is present.
MTP Enabled
Installing zip file '/sdcard/lineage-14.1-20170816-nightly-kiwi-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Comparing TZ version TZ.BF.3.0.C3-00025 to TZ.BF.3.0.C3-00022") =="1"
assert failed: kiwi.verify_trustzone("TZ.BF.3.0.C3-00025") == "1"
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-14.1-20170816-nightly-kiwi-signed.zip'
Updating parition details...
...done
Click to expand...
Click to collapse
When i edit the zip file and delete the first two line of the updater scripter with notepad++ as i mentioned above, i can install these ROMS, but they wont boot / are in an infinite Bootloop
So on which firmware you were before flashing Los
PalakMi said:
So on which firmware you were before flashing Los
Click to expand...
Click to collapse
how do i check that?
I was able to get the backup running. So I am back to EMUI 3.1 / Android 5.1.1. Here is a screenshot from my phones status: i.imgur (DOT) com/rCnuOpX.png
Activehannes said:
how do i check that?
I was able to get the backup running. So I am back to EMUI 3.1 / Android 5.1.1. Here is a screenshot from my phones status: i.imgur (DOT) com/rCnuOpX.png
Click to expand...
Click to collapse
Just go to about phone
PalakMi said:
Just go to about phone
Click to expand...
Click to collapse
I did and posted a screenshot above
is it Build number "KIW-L21C432B160"
so... B160?
update:
I just downloaded this:
NEW KIW-L21 C432B350 - D003
from this thread: https://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
I was going to unzip it, copy the "dload" folder on my device, go the the updater and run the "local update package".
And then my phone will be on android 6.0 with b350, right?
The next step would be to start the phone in the recovery TWRP, go to wipe --> advance wipe and select everything (system, data, cache etc). after that i copy the latest Kiwi lineage OS zip rom on my device with the GAPPS 7.1 and try to install them again via TWRP 3.1.1?
Is this right?
I just wanna ask because my phone doesnt work for 2 days now and i dont want to brick it completely. cant afford a new one
Update to marshmallow first (any update before b360, like b320)
Update to marshmallow first (any update before b360, like b320)
Click to expand...
Click to collapse
when i go to the "updater" and and search for a new update it says that there is none. My phone is still on EMUI 3.1/android 5.1.1/b160. Do i need to manually download another firmware? so a B320 patch first (with the dload folder and local upgrade package) and after that the B350 upgrade?
Try manual ota here or search here. If no luck use XDA search bar &/or Google. Good luck.
Activehannes said:
when i go to the "updater" and and search for a new update it says that there is none. My phone is still on EMUI 3.1/android 5.1.1/b160. Do i need to manually download another firmware? so a B320 patch first (with the dload folder and local upgrade package) and after that the B350 upgrade?
Click to expand...
Click to collapse
Try any marshmallow update before b360.
If it didn't work, try the above post.
so i followed this guide: https://forum.xda-developers.com/honor-5x/how-to/manual-ota-update-guide-update-app-t3445976
he describes 2 methods.
I wasnt able to find a B320 update for KIW L21, only for KIW L22 which is the Indian device I think. so I downloaded KIW L21 B330 Denmark. I unzipped the file and copied the dload folder on my device,
i went to update --> menu --> local update --> UPDATE.APP
my phone restarts into TWRP and does nothing. I know that I need the EMUI stock recovery, not TWRP, but no matter how many times I do this, it always restarts into TWRP.
i also tried the other method.
I shut down my phone, press VOLUP and VOLDOWN and Power. The phone goes into the the "honor" loading screen and restats after a few seconds. and restart again and again. If i release the power button before it restarts, it just boots into the system. If I shut it down and hold VOLUP and Power it boots into TWRP. I tried so many different compinations, but i cant get my phone into the EMUI Stock recovery. I read in the other XDA thread, that i need to unlock my phone. So i tried that. i went adb reboot bootloader --> fastboot oem relock CODE. the console did its magic but my phone is still unlocked. And now i cant repeat that command. when i go again into the bootloader and type fastboot oem relock it says:
PS C:\adb> adb devices
List of devices attached
W6HDU17610003396 device
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot oem relock 1524319619165116
...
FAILED (remote: Image verify failed,relock fail)
finished. total time: 1.810s
PS C:\adb> adb devices
List of devices attached
PS C:\adb>
Click to expand...
Click to collapse
So, i still have b160 / android 5.1 on my phone :/ can anyone figure out what went wrong?
Activehannes said:
so i followed this guide: https://forum.xda-developers.com/honor-5x/how-to/manual-ota-update-guide-update-app-t3445976
he describes 2 methods.
I wasnt able to find a B320 update for KIW L21, only for KIW L22 which is the Indian device I think. so I downloaded KIW L21 B330 Denmark. I unzipped the file and copied the dload folder on my device,
i went to update --> menu --> local update --> UPDATE.APP
my phone restarts into TWRP and does nothing. I know that I need the EMUI stock recovery, not TWRP, but no matter how many times I do this, it always restarts into TWRP.
i also tried the other method.
I shut down my phone, press VOLUP and VOLDOWN and Power. The phone goes into the the "honor" loading screen and restats after a few seconds. and restart again and again. If i release the power button before it restarts, it just boots into the system. If I shut it down and hold VOLUP and Power it boots into TWRP. I tried so many different compinations, but i cant get my phone into the EMUI Stock recovery. I read in the other XDA thread, that i need to unlock my phone. So i tried that. i went adb reboot bootloader --> fastboot oem relock CODE. the console did its magic but my phone is still unlocked. And now i cant repeat that command. when i go again into the bootloader and type fastboot oem relock it says:
So, i still have b160 / android 5.1 on my phone :/ can anyone figure out what went wrong?
Click to expand...
Click to collapse
May be i can help u with this .
Hey Guys,
i spent the last 8 hours to get my z back to life but without luck.
i was on aokp (official) as i decided to go back to stock rom, after i have seen that my device wouldnt boot a normally after the first flash, i flashed lineage os and from there it always tells me that it needs a password to start android. but i never had a passwort so i tried the one from my google account but it doesnt worked.
and now im stuck on the warning screen from the unlocked bootloader i can still go in recovery / bootloader mode but it doesnt matter what i flash it wont work.
SO PLEEASE HELP ME... i can give a small donate via paypal if you can help me the right way!
Hi.
You still have access to TWRP? if yes go to Advanced > File Manager then navigate to this path: /data/system
Look for this files:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
Delete them all. if one or two of them is not exist that's Ok, skip them.
Now reboot the phone and see the password request form appears or not.
P.S. Don't panic you not bricked your phone.
Hello and thank you for your answer. But i do not have this files.
in data/system/ i have 3 ordners "dropbox-add" "heapdump" and "perfd".
nexxer92 said:
Hello and thank you for your answer. But i do not have this files.
in data/system/ i have 3 ordners "dropbox-add" "heapdump" and "perfd".
Click to expand...
Click to collapse
Then i suggest try a full wipe.
Dalvik
Catch
Data
System (By wiping this partition hole android OS will remove)
after that try to flash an custom ROM (Lingoes, RR, orginal images)
I hope this will solve the problem.
Soo, after a full night of flashing ( im seriously feeling like a pro hacker with all those command windows open ) i have managed to get back to stock reteu wit november security patch and relocked bootloader.
The only thing which bothers me at the moment is when i start the phone normally it takes me directly in the fastboot menu, but the screen for bootloader unlock is gone and it still says status: modified.
How is it possible that the phone boots normally? And can i do OTA Updates now with relocked Bootloader?
Thanks in advance!
nexxer92 said:
Soo, after a full night of flashing ( im seriously feeling like a pro hacker with all those command windows open ) i have managed to get back to stock reteu wit november security patch and relocked bootloader.
The only thing which bothers me at the moment is when i start the phone normally it takes me directly in the fastboot menu, but the screen for bootloader unlock is gone and it still says status: modified.
How is it possible that the phone boots normally? And can i do OTA Updates now with relocked Bootloader?
Thanks in advance!
Click to expand...
Click to collapse
How did you do that. I'm trying and trying to get back to stock EU firmware. No chance, I always get verification problem, need signed boot bla bla.
Btw. For normal boot try this
fastboot oem fb_mode_clear
knjigo said:
How did you do that. I'm trying and trying to get back to stock EU firmware. No chance, I always get verification problem, need signed boot bla bla.
Btw. For normal boot try this
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
hi
i flashed an RETBR Firmware.. bootet it, installed update.zip to 7.1.1 with adb sideload and then flashed again with fastboot oem lock begin.
nexxer92 said:
hi
i flashed an RETBR Firmware.. bootet it, installed update.zip to 7.1.1 with adb sideload and then flashed again with fastboot oem lock begin.
Click to expand...
Click to collapse
Great for you. Where did you get update to 7.1.1?
I get always error not signed boot.
If you could provide some step by step manual how to flash stock rom and relock bootloader it would be great.
I was also on reteu german firmware.
BACKUP YOUR DATA FIRST
Only for zs570kl 2.15ghz CPU; NO zs570klPRO 2.4ghz device.
Hi all,
official image to flash Android 8 Oreo.
HOW TO:
Method fast 1
1.Extract ZIP
2.Go into the fastboot (key vol + and power on)
3. On the folder extract open update_image.bat
Wait to done 2/3 minut and ENJOY android Oreo
Method 2
Flash using Asus Flash Tool
to download and info
https://www.asus-zenfone.com/2017/03/download-asus-flashtool-10045-for-zenfone-3.html?m=1
Update file Android 8 Oreo 15.0210.1804.47:
https://drive.google.com/open?id=1U5SBXDpezUIIxisDPY8qm85LoGNfS5i6
I take no responsibility for brick device.
Have testeted the rom and work fine.
That's official from Asus?
If I flash it from TWRP Will replace stock recovery?
tecnicopascoal said:
That's official from Asus?
If I flash it from TWRP Will replace stock recovery?
Click to expand...
Click to collapse
official Asus, no only in fastboot mode
Has anyone suffering battery drain? I've updated my ZS570KL to 8.0 with Asus official but phone became hot and battery drain is dramatical…. obvious reset many time to factory default and wipe all…. The problem appears from the beginning…. starting the initial setup. Thanks.
grean said:
official Asus, no only in fastboot mode
Click to expand...
Click to collapse
So is this rootable or is it pre-rooted? I also am wondering if this Oreo update fixed the Quickcharge limit (where QC is disabled)?
It is the only way to update?? Except ota
EDIT. Guys, the other way you can update to oreo is flashing oreo stock recovery and then install the firmware
Wheres the MAGIC
have oreo up and running no problem, lost root/magisk and cant seem to get it back. trying to flash magisk installer failed even up to 16.4 just goes into bootloop, flashing stock boot back and it boots up ok to oreo.
If any one on ZS570KL 2.1ghz has oreo running with MAGISK please post a copy of your boot.img.
the only other thing I can think off is that the bootloader is relocked. Anybody with any experience of this?
Aussiewaterdragon said:
have oreo up and running no problem, lost root/magisk and cant seem to get it back. trying to flash magisk installer failed even up to 16.4 just goes into bootloop, flashing stock boot back and it boots up ok to oreo.
If any one on ZS570KL 2.1ghz has oreo running with MAGISK please post a copy of your boot.img.
the only other thing I can think off is that the bootloader is relocked. Anybody with any experience of this?
Click to expand...
Click to collapse
I'm having the same issue, also I can't seem to unlock my bootloader using the unlock tool on asus website it always says "Failed to unlock this device, please try again later"
also what's up with this automatic device encryption ? I flashed twrp recovery and it can't decrypt the device using the password or the PIN i've set, I even tried "default_password" still doesn't work
BahaStriker said:
I'm having the same issue, also I can't seem to unlock my bootloader using the unlock tool on asus website it always says "Failed to unlock this device, please try again later"
also what's up with this automatic device encryption ? I flashed twrp recovery and it can't decrypt the device using the password or the PIN i've set, I even tried "default_password" still doesn't work
Click to expand...
Click to collapse
Have you had any luck? I'm having a similar problem to you. When I try to unlock my bootloader using the unlock tool it complains that I don't have a PIN set (even though I do) then fails and says "Failed to unlock this device, please try again later".
karlnorth said:
Have you had any luck? I'm having a similar problem to you. When I try to unlock my bootloader using the unlock tool it complains that I don't have a PIN set (even though I do) then fails and says "Failed to unlock this device, please try again later".
Click to expand...
Click to collapse
Tried all means, I just gave up
I'm happy to say that I got it working. It appears the Unlock tool gives the "Can't unlock your phone right now" error if your phone is already unlocked.
Previously, I was running the Turbo ROM 6.01 found in the ZF3 Deluxe thread. My phone was BootLoader unlocked and Rooted. I upgraded to 8.0 by running the very straightforward "Update_Image.bat" command found in the 8.0 ROM folder. I figured the update would re-lock my BootLoader, so I ran the 8.0 version of the Unlock tool. Then I ran into the previously mentioned error. In my frustration I just said 'screw it, I have 4 of these phones'. So I booted the phone into fastboot mode and flashed TWRP 3.2.2. I expected it to fail; however, it WORKED! I then booted the TWRP 3.2.2 image and flashed SuperSU v2.82 SR5. That worked! I then flashed the Xposed v90-sdk27-arm64-beta3 zip and THAT worked! I rebooted the phone and it loaded up pretty as you please.
I've followed this procedure with all 4 of my ZF3 Deluxe phones and they are all happily on 8.0.0, Rooted, and have Xposed running
Mate 10. So, I tried to install the latest EMUI version using HuRUpdater - bad idea. Now, my phone will not boot. I can enter EMUI Recovery Mode but when I try to receive download package, it says it can't be retrieved. I can also enter Fastboot Mode but the problem with that is that under Device Manager, it only gets recognized as, "Android Bootloader Interface."
Please, any help would be greatly appreciated.
edit: So, fastboot DOES work. What files from what version do I flash to return to stock recovery? I don't even know if Pie was actually written to the device or not before the device rebooted and wouldn't boot.
edit again: I have just successfully installed TWRP via fastboot but it hangs at startup screen - is this because it's not compatible with Pi?
So I've tried flashing ramdisk_recovery.img, kernel.img and system.img from the Pi version but I still can't factory reset the phone. It boots back to the white screen with the android dude and says, "Please update system again."
Any help would be appreciated...
Using Multi-Tool, it detects my device in Fastboot mode as still 8.0.0.143. So, I'm trying to flash System, Ramdisk, Cust, Recovery_Ramdisk and Userdata......all succeed, except one - Ramdisk.img. When I manually try to flash Ramdisk.img in command prompt, it also fails, "FAILED (remote: partition length get error)". In Multi-tool, the error is, "the size or path does not match the file system markup."
Please, does anyone have any other suggestions? I've been at this for nearly 12 hours straight.
I assume u have unlocked bootloader and frb unlocked too if both yes u can search in xda for zip file beta downy 0.4
It will help you to downgrade emui 9 to. Emui 8
If u have unlocked bootloader only I guess u need funky huawei to restore ur devise
I hope I did helped u
Thanks for the reply.
My bootloader is unlocked but how do I know if I have unlocked FRP?
And downy tool requires ADB but I can only access Fastboot.
edit: I just checked and my FRP is also unlocked. What now?
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
essen212 said:
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
Click to expand...
Click to collapse
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Pretoriano80 said:
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Click to expand...
Click to collapse
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
essen212 said:
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
Click to expand...
Click to collapse
Try with EMUI 9 first, then, if it fails, try Oreo. The most important part is finding a DLOAD firmware for your cust/region.
I've fixed it!
Funky emailed me back and I ended up using a different method on their site which worked like a charm. I couldn't recommend them enough.
Hi, good to hear you got it sorted! Would you mind sharing the details on what you had to do differently with FHC? I'm in the same boat here with a mate 10 pro that died on emui9 and I'm not sure if I should go the FHC way or not...
Thx - David
Is there a system app or security feature on the sm-j737p 9.0 pie U7 that needs to be disabled in order to gain root access? I cant get it to flash any su on the device nor get magisk to work right on it. I cant find a guide that will work for it. Is it unrootable?
Look inside here.
jwoegerbauer said:
Look inside here.
Click to expand...
Click to collapse
Iv seen and followed that guide before, when I flash twrp onto my device it fails. I'm on android 9.0 pie U7.
I cant get two to flash.
dunnothename said:
Iv seen and followed that guide before, when I flash twrp onto my device it fails. I'm on android 9.0 pie U7.
I cant get two to flash.
Click to expand...
Click to collapse
If not already done yet, unlock phone's bootloader and also disable Android's AVB & Android's dm-verity .
jwoegerbauer said:
If not already done yet, unlock phone's bootloader and also disable Android's AVB & Android's dm-verity .
Click to expand...
Click to collapse
I cant get the bootloader unlocked cause the phone doesnt go into fast boot mode
dunnothename said:
I cant get the bootloader unlocked cause the phone doesnt go into fast boot mode
Click to expand...
Click to collapse
Read here
nope, isnt working . cant disable any dm-verity or AVB, theres no fastboot mode on this phone, the usual things that go into rootin a samsung isnt possible with this one for some reason
Success!!
I got it rooted
. Stock firmware AP > Magisk > magisk.tar > Odin > flash > Root.
Hi can you possibly tell me where I'm going wrong, I've been at this for hours and can't seem to get it working. So based on the guide I've been following, I got the correct firmware file for my phone and then flashed it with magisk. I turn off the phone and put it in odin mode where I flash the patched tar file. Then it says to immediately put the phone in recovery mode, which I do, and wipe the data then reboot and it should be root with Magisk installed. However, this does not happen, instead it just runs through the new phone setup where it downloads a system update and there's no way to bypass it. I also tried flashing twrp, and I made sure it was the latest version and for my model yet when I try to flash twrp and boot straight into recovery (or not, it doesn't matter what I do at this point) the phone just bootloops until I put it back in odin and flash the firmware again. I just don't understand, I've rooted many phones and tablets and I've had a lot of trouble but there always seemed to be more resources and people having similar issues that would help.