I spent days and nights but I got it
1. download rar file from MOD EDIT: Links removed. Please do not use pay per click links, or links that require registration before downloading...also make sure that your files are not full of malware and that your file hosting service is it loading themselves.
2. put your tablet in debug mode (go to setting >about tablet >click on build number 3times till you unlock developer options)
3. in developer options check USB debugging
4. on your pc unpack the rar file
5. double click on run me
6. write ACCEPT
7. choose option 1 to install ADB drivers
8. close all open run me and write ACCEPT this time choose option 2
9. then choose option A1
10. then choose option 1
11. then choose option R2
12. then type ACCEPT
when finish your tablet will reboot and enjoy your tablet is rooted!
Got my kids one each for 80, so I figured I would try to root.....this didn't work with 4.2.2....locks up after ACCEPT restarts No Root Permission, reinstall......thanks though
a little help plz
mk i downloaded everything like you posted i have a acer a1-830 with 4.4.2 on it mk now when i get to step 8 close the run me that was open then reopen it? when i do close it then reopen it and complete the rest of the steps after i type accept last time it says could communicate with device i do have the debugg box checked after i turned on the developers options on what am i doing wrong for it not to communicate? i have also installed a driver were you said to close it i hit enter to install a drive on my pc should i have done that or not i am really a noob at this plz help me thanks in advance. also i can get it to the reboot droidboot screen with options,
reboot droidboot
reboot
recovery
power off
but when i hit reboot droidboot it restarts tablet goes back to same screen and doesnt communicate with the batch kit thing it says waiting for device and never does anything so am i suposed to hit reboot also if i do this do i loose all my saved games and info?
how i did it
What I did was like that first I download root genius tried it stock on %75 it didn't work then i tried root genius.apk the app it say %80 was completed connect to your pc superuser was instaled but no root access permission then I tried this method that I posted and it worked don't know how but it did by the way my tablet running android 4.2.2 build number ACER_av052_a1-830_1.011.00_WW_GEN1
Hope that helped good luck
options
zartan823 said:
mk i downloaded everything like you posted i have a acer a1-830 with 4.4.2 on it mk now when i get to step 8 close the run me that was open then reopen it? when i do close it then reopen it and complete the rest of the steps after i type accept last time it says could communicate with device i do have the debugg box checked after i turned on the developers options on what am i doing wrong for it not to communicate? i have also installed a driver were you said to close it i hit enter to install a drive on my pc should i have done that or not i am really a noob at this plz help me thanks in advance. also i can get it to the reboot droidboot screen with options,
reboot droidboot
reboot
recovery
power off
but when i hit reboot droidboot it restarts tablet goes back to same screen and doesnt communicate with the batch kit thing it says waiting for device and never does anything so am i suposed to hit reboot also if i do this do i loose all my saved games and info?
Click to expand...
Click to collapse
After you hit droidboot on your device manager you will see unknown device click on it update driver the device type choose android device then choose driver from the unpacked far folder the choose driver android ADB version 4.000 if didn't work try ADB version 8.000 then just follow steps in description it should be fine
Sorry about that forgot to add this detail
genesis2 said:
After you hit droidboot on your device manager you will see unknown device click on it update driver the device type choose android device then choose driver from the unpacked far folder the choose driver android ADB version 4.000 if didn't work try ADB version 8.000 then just follow steps in description it should be fine
Sorry about that forgot to add this detail
Click to expand...
Click to collapse
well i tried all 3 drivers it showed me in device manager were the yellow triangle was and still nothing it goes threw the whole process and gets to droidboot and freezes so i manually turn it off and back on shows bunch of codes and says complete go to root checker says not rooted also that file is loaded with virus's man after in stalling i had like 33 virus's instant plus some kind of task rockettab in cmd that had to be removed plus all the pop ups it installed in my tab was a joke unless there is a better and safer way to do this with out the virus's like they do on mpgh to be safe i will not be trying this again something in your work is not correct and it is loaded with virus's sorry bro but this thing is dangerous and needs to be removed. i should of known better when i see 5 posts and a release kinda funny if you ask me no rep at all.
If a mod could be so kind as to move this to the correct area if this location is incorrect I appreciate it.
Recently I've been given a pretty crappy tablet, but nevertheless I want to get it in working conditon. I love the challenge and I love the opportunity of being able to learn something new.
The specs of this Tablet device are as follows: http://www.sears.com/ideausa-idea7-7inch-tablet-w-dual-core/p-SPM8151247717
Maker: IDEA USA
Model: CT720
SDK: MID-A20-Android4.2-v2.0
Android system recovery <3e>
The owner of this tablet says they went to turn it on one day and it said no operating system found. other than that I have no information other than what is listed previously.
So when turned on I get the green android logo looking like its an android guy putting his arms up. it stays stuck there. I've never once gotten a screen saying no operating system found.
when I turn it on with power + volume up I get recovery mode
power +volume down as well as power + volume up + volume down do not do anything except boot the green guy back up.
I figure through recovery I can maybe get cyanogen onto this device and figure things out along the way somehow.
I boot into recovery mode and of course the volume buttons do nothing even though the screen states to use the volume buttons to navigate. I use adb to reboot to bootloader, where it goes to the green guy again. I check the device status and it says it's status is device.
I use adb to reboot to recovery and it's back at the same screen where the volume keys do nothing. I find some adb commands to push button presses across, no luck as it says
'/system/bin/sh' failed: No such file or directory (2) -
So far I'm thinking my only chance in hell is gonna be if I can force push a different recovery over this one which I'll actually be able to use, followed by trial and error with different roms.
any recovery images I get are ISO files, and I can only adb push .apk files. I'm definitely missing something here as I don't have too much knowledge at this level of android devices.
any help I can get I greatly appreciate it.
---------------------
edit .
when the green guy comes up, im able to adb shell in. I don't know if this helps any, I'm going to continue researching a bit and see if there's anything I can figure out
now that I'm able to shell in I'm able to tell that there is still an operating system. and all files seem to be fine and intact. not sure what's causing this
So I had figured I would make an attempt at messaging the maker IDEA USA and seeing if they could provide me with with a rom.
luckily I received an email providing me with an official .zip which I have hosted here: https://mega.nz/#!mwcmGaiB
The rest of the email stated as follows;
"The Software needed is called PhoenixSuit V1.10 (i used 1.0.6)
You will need a PC with Windows 7 or above
Micro USB to USB Cable (Supplied with your device)
Open the software
Click on the Anchor with Firmware underneath it (See Photo attached)
Click on the Blue Image button, Navigate to where you have the Firmware Image on your device.
With the tablet off Connect the device to the PC.
Press and hold the Volume up (+) key and hold it
Press the power but approx 6 times quickly and you should see the device start to load the firmware.
It should show device connected in the lower left corner of the software. "
I ended up just having to turn it on normally and it auto detected after following the previous instructions. Flashed the firmware and worked like new. Hope this helps anyone else out there with any troubles!
I still would like to put a recovery on to this device, twrp and cyanogen cannot find a compatible recovery. Any direction on where I could go from here?
Hello,
If your device has no custom recoveries available then you can try getting someone to build one for you or you can go to XDA University and find instructions for porting a recovery from another device or you can find how to build a recovery from source, there are many links and some menus that have other links at XDA University, check them all until you find what you are looking for.
---------- Post added at 07:02 PM ---------- Previous post was at 06:58 PM ----------
Trippinshrumes said:
So I had figured I would make an attempt at messaging the maker IDEA USA and seeing if they could provide me with with a rom.
luckily I received an email providing me with an official .zip which I have hosted here: https://mega.nz/#!mwcmGaiB
The rest of the email stated as follows;
"The Software needed is called PhoenixSuit V1.10 (i used 1.0.6)
You will need a PC with Windows 7 or above
Micro USB to USB Cable (Supplied with your device)
Open the software
Click on the Anchor with Firmware underneath it (See Photo attached)
Click on the Blue Image button, Navigate to where you have the Firmware Image on your device.
With the tablet off Connect the device to the PC.
Press and hold the Volume up (+) key and hold it
Press the power but approx 6 times quickly and you should see the device start to load the firmware.
It should show device connected in the lower left corner of the software. "
I ended up just having to turn it on normally and it auto detected after following the previous instructions. Flashed the firmware and worked like new. Hope this helps anyone else out there with any troubles!
Click to expand...
Click to collapse
Consider creating a thread with detailed instructions for how you corrected your issue, you can put it in the Android Development and Hacking forum. It would help a lot of others with your device if they have the same issue. The thread doesn't have to be fancy, just list the steps and links to the files needed(including firmware link, flash tool link and anything else that is required). It shouldn't take a lot of trouble to put the thread together. The community would appreciate it.
Hi guys,
Sorry to bother you with that but i have an issue with my Nexus 5 and i wanted to have more information about a " solution " i found on the web.
So First, my phone got a problem with the power button (on the motherboard). I managed to find a repair shop doing that kind of repair.
Now's the real problem !
The phone won't go further than the " Google " logo.
I can access Fastboot mode but not recovery mode.
The phone is not root, official stock rom, bootloader locked, usb debugging mode : OFF.
I find something on the web but it seems the guy who write it down skipped some steps. And i'm a total noob at that so i don't understand how he managed to do what he described.
Here's the link :
(Ok so i can't post link since it's my first post.... so i will C/P his method here)
METHOD :
Things you will need
Download the Stock ROM for your device- Just Google it, I am dam sure you can find it.
Download SuperSU from UPDATE-SuperSU-v1.65.zip
UPDATE-SuperSU-V1.65.zip contains :
Superuser boot permission manager.
Update script (important) etc.
Basic Knowledge of C++ or Java
Notepad++
WinRAR
Steps to Enable USB Debugging Using Recovery Mode
Unzip the stock rom.
Within the extracted folder you will find system.img well extract it too using Ext4 Unpacker
Also extract the Update-SuperSU.v1.65.zip file.
Now open the folder where you have extracted the system.img files
Grab any .apk file from this folder and change the extension from .apk to .zip
And Copy the RSA Certificated to the Update-SuperSU.v1.65 folder (delete previous files if exist)
Also copy the build.prop to the system folder located within Update-SuperSU.v1.65 folder
Located the update-script file within this folder and edit it using Notepad++
You need to update the build.prop file after adding the following line at the bottom
persist.service.adb.enable=1
Next step is updating SQLite Database
Which can be done by adding following code to update-script file
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "UPDATE global SET value=1 WHERE name='adb_enabled'"
Cheers! You have Enabled USB Debugging
Now you can install your custom or stock rom using ADB – USB Debugging.
So basically, i wanted to know if the " solution " was possible to achieve or if the guy is plain dope, so i can backup my personal data before doing a factory reset.
Or if there's another way to backup my data.
Ah ! When i plug my phone on my PC, it isn't recognised as a Nexus 5 but as a Android Interface Bootloader (or something like that).
Sorry for the long post !
Hi, I understand what you're trying to do but I think this is not possible. The tutorial you've find on the web seems pointless to me because it just say you to customize some system files of a stock rom downloaded from google repo without saying to flash anything (or maybe this is what I understood).
Anyway I'm sorry but the only solution to this is to unlock the bootloader and flash a new system image, of course if this is a softbrick.
Have you already repair the power button? And how the phone get stucked on the logo image, bootloop or just freezed?
Hi
Thank you for replying !
The power Burton is repaired.
And to answer your question, it just freeze.
The phone turns on, "Google" logo appears and it stays that way, and after waiting a few minutes it automatically reboot and freeze again when "Google" logo shows again
In my opinion this could be a softbrick caused by something, I don't see any way out exept flashing something new. Fastboot doesn't require usb debugging enabled to work properly but unlock the bootloader means wipe all your data.
Probably your recovery has gone o something is corrupted in the system startup sequence.
You could wait for someone that can help you in another way that I don't know I'm sorry.
Well, i think i will wait and continue to search until this weekend.
Anyway ! Thank you for answering me, that was very kind
Was there anything that could have been the cause if the bootloop? Have you tried wiping /cache & /data from the recovery? If not try booting into stock recovery and preforming a factory reset. Google: "how to open nexus 5 stock recovery" android.gs has good instructions on booting into recovery. After following those instructions navigate to factory reset, press the power button, then hold the up volume button. If this doesn't work then you'll have to unlock your bootloader. But I won't get into that now. Good luck.
FYI: Don't bother with the instructions outlined in your post, they don't pertain to your situation.
Also, I can't post links as this was my first time posting here.
Hi SuBAtomicFlux,
Like i said, i can't access stock recovery, when i'm at the step where the Android robot shows a red warning sign, nothing happens when i do the key combo to enter into the Stock Recovery Mode and after a few seconds, the phone reboots by itself.
But thank you for trying to help me !
Everything useful for the Samsung Galaxy J4 Core you find now here.
Infos, Tutorials, Tips, Tricks, Hacks...
Enjoy & Join ?!
In this first post I start off with a STEP BY STEP ROOT GUIDE. It's very detailed & hopefully n00b friendly!
Here it is:
In your phone's about section press build number several times, then developer options are activated,
you can find them in the system section of settings when you exit about section.
enable developer options, it is recommended to disable system auto update there, then enable oem unlocking.
(if you can't find this entry, enter a sim, try again. if you still can't find this entry, set the system date 21-30 days back or forth, then reboot. if the entry is still not there, search here on xda for solutions to this known problem or google it.)
go to your pc, download your exact firmware (the one you have installed on your device- look at build date & region in about section of device).
download 7zip zstandard! -with lz4 extracting support.
extract zip of your firmware. there you have 4 tar files. extract the AP tar file, inside are many files. extract smth like boot.img.lz4 or boot.lz4, then you have boot.img. this is the file you need.
in 7zip mark it & press add to archive, select tar in the screen that pops up. enter the path where you want to create the archive.
now you have a new boot.img.tar or boot.tar file,
that you need for the rooting process.
copy this file to the root of your internal storage of your android phone (/sdcard, /storage/emulated/0, or any folder that suits you best).
download & install latest magisk manager on your android.
open magisk manager, in the start screen you find some options. one of them is: preserve force encryption. uncheck them all.
then choose: install magisk, then: patch file. you will be directed to a file manager, there select your created boot.tar file.
now magisk creates a patched boot.tar file for you & renames it as such.
you will find it in the same directory as your file, or in /sdcard/download.
copy it to your pc. in your pc rename it in boot_.tar!
download odin latest! version.
download latest! samsung usb drivers / latest samsung usb drivers for your specific phone model, install just samsung usb drivers & reboot your pc.
enable usb debugging in developer options of your phone.
turn off your phone.
connect your phone with usb cable to pc.
reboot your phone to download mode: when starting vol up + vol down + power button at the same time.
you come to a light blue warning screen. press power up once again, you entered download mode!
in your pc run odin as administrator.
it should recognize your device. you should see in the window on the left side in odin: added!
on the right side in odin are several buttons. one of them is BL. press that & go to the path of your boot_.tar. select your boot_.tar.
odin checks & in a sec you should see a checkmark next to BL.
now set some options in odin: - check flash reset time! - uncheck auto reboot! let all the other options untouched.
now you will flash your magisk patched boot_.tar to your android device: press start in odin.
you will see the ongoing progress in the upper row & in the log window.
you should see reset in blue color & when you see pass in green color, the flashing process was successful! almost done!
now on your phone: you're still in download mode, see the completed progress bar.
press vol down + power at the same time for 7 sec.
your phone will reboot. on the logo splash screen's upper left corner you will see a yellow entry: set warranty bit: kernel.
now the phone will reboot, reset. now your phone will show you a grey screen with a reset button, if you can't click it, no panic, just turn your screen shortly off & on again & then you can click it. phone will reboot again 2 times. don't panic! let it do its thing.
note that your phone will be reset through this process!
now you boot in your phone & the start menu appears.
you can go through it as usual. you should turn secure boot with lock off, choose just the normal phone lock.
at first turn developer options on & see if oem unlocking is there & enabled. (it usually is.) if not, turn it on again!
if it's not there after root, look here in XDA for solutions or google it. (but this is very rare on this phone, that it's not there after root)
leave oem unlocking & developer options always on! (unless you want to unroot)
turn system auto update off in dev options!
you can reinstall magisk manager & check if magisk is installed.
congrats, you're rooted!
now you can do everything that's neccessary & useful after root!
Guide follows soon!
[important: better safe than sorry: in your phone, right after rooting, enable developer options again & look if oem unlock is ticked on. let it always be ticked on! also leave developer options on! if not so, then do it immediately. otherwise it could be overwritten by security in your phone & you could lose root, your phone could be reset, or in the worst case your phone will be blocked to boot. never turn off oem unlocking!]
I will add some files soon here, to make it easier for you.
but if you follow this guide step by step, you should succeed, normally.
I've tested this procedure several times on my own with this phone, with different firmwares.
I can confirm that this guide is functioning well!
if you need further help just post me!
[please think about the steps you made prior to the rooting process also after root. don't forget your phone has become reset & some settings eg oem unlocking & others need to be re-applied !]
please use your mind! ?
Happy Rooting! ?
credits: to everyone I learned from!
Rooting, Flashing & everything you do on your device, you do on your own risk!
You take responsibility for your own actions!
Please consider before you copy my guides, to give me a thanks & if you wanna use my guides elsewhere, give me credits there, respectively!
This Guide/My Thread will be further improved in form, speech & content.
So much more to come in the future!
Please feel free to post me your thoughts, recommendations & criticism!
You're heartly invited to participate in my thread! ?
I have the root on my j410G following your guide thanks ...:good:
@JhonJC
you're welcome!
fine that you succeeded!
I used this method to root the j7 prime with new binary.
But i flashed boot patched as AP in odin. Works fine.
JohnEdwardMS said:
I used this method to root the j7 prime with new binary.
But i flashed boot patched as AP in odin. Works fine.
Click to expand...
Click to collapse
great to read that! odin normally flashes the whole firmware -including the boot.img- through ap, so pushed your boot.img automatically to the right partition.
but I still recommend flashing through BL. think I've read about it in the magisk documentations, but I will check that again, investigate further. thank you for info.
The method works but if you turn off the phone and turn it on you are greeted by a "this phone has been flashed with unauthorized software & is locked" screen.
zeratos said:
The method works but if you turn off the phone and turn it on you are greeted by a "this phone has been flashed with unauthorized software & is locked" screen.
Click to expand...
Click to collapse
@zeratos I had this too, in the beginning, when I experimented with rooting this phone. have you left developer options + oem unlocking kept on? this is essential for this phone, I've written this before in the above guide. another thing might be, if you boot into the stock recovery, then it detects, that your phone has been modified, refuses to boot + brings you to the screen that you mentioned. don't boot into stock recovery after rooting this phone, don't try to reset your phone through stock recovery or android settings! instead, get twrp or orange fox + flash it through odin. do everything then with your custom recovery, or flash everything through magisk manager!
it is also important to tick off all 3 options in magisk manager start screen and disable all unnecessary security features in your android, such as secure startup.
unfortunately, with the newer (samsung) phones, rooting is not so easy peasy anymore like it was back in the days. they gave us some really annoying hurdles.
I hope I could help.
so thanks for mentioning this, so others with the same problem can find it!
...................................... ~............................................
*can you please speak in your own person? 'you' suggests, that everyone, following my root guide will experience the same as you did. that's not true + I'm bit sensitive about truth + facts being falsified. no offence, thank you.*
the links to the great + genius orange fox + twrp recoveries for samsung galaxy j4 core:
1.) https://forum.xda-developers.com/ga...recovery-orangefox-samsung-galaxy-j4-t4059533
2.) https://forum.xda-developers.com/ga...ecovery-unofficial-twrp-3-1-1-galaxy-t4046189
@zeratos, could you get around your problem?
as I don't know what exactly went on on your phone,
I don't know if I could help you.
I just can try to tell you what can help you.
it's always good to go to magisk settings, magisk section + enable: hide magisk from various forms of detection.
next: it doesn't hurt to disable google services + other google apps until your root is stable.
the same for builtin samsung apps.
that helps preventing to trigger knox.
best is to say bye to google services/google apps at all + go with microg. then you can install custom playstore for microg + make purchases + all. not so easy btw. but if you figured it out, everything works very well.
if you already solved your problem, please tell us how you did it, could help others.
I just can tell, if you don't mind to say bye bye to all that proprietary stuff on your phone, root + everything else works almost perfect on that phone.
plus you have the free memory for all the good tools!
if you want to leave google services & co installed after root, at least flash the magisk module 'universal gms doze' , disable some permissions, run greenify + hibernate some apps strictly.
you get a much better effect with also xposed, (the original magisk xposed). but that's again not so easy at first. but you would already need it for microg, for the licence patch, (assuming you don't do the licence patch from the command line or use smali patcher).
Meu j4 core não aparece a opção do oem o que fazer pfv me ajuda
K.Vitorioso said:
Meu j4 core não aparece a opção do oem o que fazer pfv me ajuda
Click to expand...
Click to collapse
you find it above in my guide, otherwise there are many xda threads/posts to this topic, or google a bit around. good luck!
vous le trouverez ci-dessus dans mon guide, sinon il y a beaucoup de fils xda/posts sur ce sujet, ou bien cherchez un peu sur google. bonne chance !
working great guide!!!!!! thank you
Hello,
Can anyone help me ? I always get error "E1001: failed to update system image" and "updater process ended with error 7" every time I try to flash a custom ROM. Removed assert values fixed error 7 but the first one still exists.
If anyone have working custom ROM for j4 core please give me a link.
Photo of the error
thimprfct said:
In this first post I start off with a STEP BY STEP ROOT GUIDE. It's very detailed & hopefully n00b friendly!
Here it is:
In your phone's about section press build number several times, then developer options are activated,
you can find them in the system section of settings when you exit about section.
enable developer options, it is recommended to disable system auto update there, then enable oem unlocking.
(if you can't find this entry, enter a sim, try again. if you still can't find this entry, set the system date 21-30 days back or forth, then reboot. if the entry is still not there, search here on xda for solutions to this known problem or google it.)
go to your pc, download your exact firmware (the one you have installed on your device- look at build date & region in about section of device).
download 7zip zstandard! -with lz4 extracting support.
extract zip of your firmware. there you have 4 tar files. extract the AP tar file, inside are many files. extract smth like boot.img.lz4 or boot.lz4, then you have boot.img. this is the file you need.
in 7zip mark it & press add to archive, select tar in the screen that pops up. enter the path where you want to create the archive.
now you have a new boot.img.tar or boot.tar file,
that you need for the rooting process.
copy this file to the root of your internal storage of your android phone (/sdcard, /storage/emulated/0, or any folder that suits you best).
download & install latest magisk manager on your android.
open magisk manager, in the start screen you find some options. one of them is: preserve force encryption. uncheck them all.
then choose: install magisk, then: patch file. you will be directed to a file manager, there select your created boot.tar file.
now magisk creates a patched boot.tar file for you & renames it as such.
you will find it in the same directory as your file, or in /sdcard/download.
copy it to your pc. in your pc rename it in boot_.tar!
download odin latest! version.
download latest! samsung usb drivers / latest samsung usb drivers for your specific phone model, install just samsung usb drivers & reboot your pc.
enable usb debugging in developer options of your phone.
turn off your phone.
connect your phone with usb cable to pc.
reboot your phone to download mode: when starting vol up + vol down + power button at the same time.
you come to a light blue warning screen. press power up once again, you entered download mode!
in your pc run odin as administrator.
it should recognize your device. you should see in the window on the left side in odin: added!
on the right side in odin are several buttons. one of them is BL. press that & go to the path of your boot_.tar. select your boot_.tar.
odin checks & in a sec you should see a checkmark next to BL.
now set some options in odin: - check flash reset time! - uncheck auto reboot! let all the other options untouched.
now you will flash your magisk patched boot_.tar to your android device: press start in odin.
you will see the ongoing progress in the upper row & in the log window.
you should see reset in blue color & when you see pass in green color, the flashing process was successful! almost done!
now on your phone: you're still in download mode, see the completed progress bar.
press vol down + power at the same time for 7 sec.
your phone will reboot. on the logo splash screen's upper left corner you will see a yellow entry: set warranty bit: kernel.
now the phone will reboot, reset. now your phone will show you a grey screen with a reset button, if you can't click it, no panic, just turn your screen shortly off & on again & then you can click it. phone will reboot again 2 times. don't panic! let it do its thing.
note that your phone will be reset through this process!
now you boot in your phone & the start menu appears.
you can go through it as usual. you should turn secure boot with lock off, choose just the normal phone lock.
at first turn developer options on & see if oem unlocking is there & enabled. (it usually is.) if not, turn it on again!
if it's not there after root, look here in XDA for solutions or google it. (but this is very rare on this phone, that it's not there after root)
leave oem unlocking & developer options always on! (unless you want to unroot)
turn system auto update off in dev options!
you can reinstall magisk manager & check if magisk is installed.
congrats, you're rooted!
now you can do everything that's neccessary & useful after root!
Guide follows soon!
[important: better safe than sorry: in your phone, right after rooting, enable developer options again & look if oem unlock is ticked on. let it always be ticked on! also leave developer options on! if not so, then do it immediately. otherwise it could be overwritten by security in your phone & you could lose root, your phone could be reset, or in the worst case your phone will be blocked to boot. never turn off oem unlocking!]
I will add some files soon here, to make it easier for you.
but if you follow this guide step by step, you should succeed, normally.
I've tested this procedure several times on my own with this phone, with different firmwares.
I can confirm that this guide is functioning well!
if you need further help just post me!
[please think about the steps you made prior to the rooting process also after root. don't forget your phone has become reset & some settings eg oem unlocking & others need to be re-applied !]
please use your mind! ?
Happy Rooting! ?
credits: to everyone I learned from!
Rooting, Flashing & everything you do on your device, you do on your own risk!
You take responsibility for your own actions!
Please consider before you copy my guides, to give me a thanks & if you wanna use my guides elsewhere, give me credits there, respectively!
This Guide/My Thread will be further improved in form, speech & content.
So much more to come in the future!
Please feel free to post me your thoughts, recommendations & criticism!
You're heartly invited to participate in my thread! ?
Click to expand...
Click to collapse
bro did you know how to enable volte calls ?
i am from india
ZorEl212 said:
Hello,
Can anyone help me ? I always get error "E1001: failed to update system image" and "updater process ended with error 7" every time I try to flash a custom ROM. Removed assert values fixed error 7 but the first one still exists.
If anyone have working custom ROM for j4 core please give me a link.
Photo of the error
Click to expand...
Click to collapse
this should be one that works: https://forum.xda-developers.com/t/rom-oneui-j4-core-litee-j4-port-1-0.4116115/#post-83005025
Hello world!
Last year, I attempted to install a custom ROM into my device (J410F). I have no idea what is the name of the ROM but I know is compatible (from the updater script). But, anytime I tried to install it, Error 1 always appear. What do I have to do? Install Orangefox, chmod it, or just give up?
Edit 1: It's HavocOS. Some of my LineageOS in my SD Card output Error 7, and some output Error 1.
thank you---- thank you----- thank you ------ i could give you a big kissss.. lol.
ive been wanting to root my fone for years now with this guide ive done it 1st time without any problems, now i know what its like to be in controll. your a genius and i wish there were more like you in the world.
thimprfct said:
this should be one that works: https://forum.xda-developers.com/t/rom-oneui-j4-core-litee-j4-port-1-0.4116115/#post-83005025
Click to expand...
Click to collapse
This works. But if you don't care about the laggy experience that it provides (OneUI on 1GB RAM heh) and the broken camera app, then it's good for you.