[Request] Orange Great Britain RAZR i - RAZR i Q&A, Help & Troubleshooting

Looking for an Orange branded RAZR i to get the firmware off of. Will require root and having some time to team viewer session.
How to tell if you are Orange branded:
In Settings > About Phone the System Version will look something like this, but the numbers may be off.
81.4.38001.XT890.Orange.en.GB
The important part is the XT890.Orange.en.GB.
Give me a ring at my gtalk ([email protected]) or PM me if you got one and willing to help get the firmware off of it.
Cheers

Dear sir,
Thk for your great work & ask ;
1) After unlock bootloader & flash root kernel & flash back official kernel,will it still root ?
2) Will root allow to update ?
3)Will subsequent update to Jelly Bean have to re-unlock & re root again ?
4)How to replace whole rom with this big size 81.5.38002.Retail.en.GB,fastboot command ?
5) Any place can i get CWM with update kernel or new rom,backup?
Have a good day.Bye.Daniel
mattlgroff said:
Looking for an Orange branded RAZR i to get the firmware off of. Will require root and having some time to team viewer session.
How to tell if you are Orange branded:
In Settings > About Phone the System Version will look something like this, but the numbers may be off.
81.4.38001.XT890.Orange.en.GB
The important part is the XT890.Orange.en.GB.
Give me a ring at my gtalk ([email protected]) or PM me if you got one and willing to help get the firmware off of it.
Cheers
Click to expand...
Click to collapse

I got mine on Orange/EE but from Phones4U.
So its actually XT890.Retail.en.GB
But if theres any other ways I can help in development please say

Daniel 9999 said:
Dear sir,
Thk for your great work & ask ;
1) After unlock bootloader & flash root kernel & flash back official kernel,will it still root ? The root tool I does flashes the insecure, which allows remounting /system/. When this is done the root files are pushed to the phone and set for permissions. Then, not needing the insecured kernel anymore and keeping OTA updates intact, we flash back the secured kernel. So yes, you will still be rooted.
2) Will root allow to update ? Since you flash back the stock kernel, it won't affect root.
3)Will subsequent update to Jelly Bean have to re-unlock & re root again ? Unlock a permanent. We will have to re-root since it seems we cannot use OTA Rootkeeper and similar apps. Not a big deal though.
4)How to replace whole rom with this big size 81.5.38002.Retail.en.GB,fastboot command ? My firmware changer already includes and uses the newer fastboot that does 100MB parts required. (Thanks to P3Droid and aosp.us for that).
5) Any place can i get CWM with update kernel or new rom,backup? No CWM yet.
Have a good day.Bye.Daniel
Click to expand...
Click to collapse
Kind of off topic, but ok....

Related

[Q] does rooting modify the original firmware?

Hi,
I plan to root a HTC Desire C only for sim unlocking it. So far I am pleased with the original firmware (ICS 4.0) - after disabling some apps the phone runs fast and smooth.
The question is: does rooting modify the original OS in such a way that instabilities may occur?
Thanks.
dr.pythagora said:
Hi,
I plan to root a HTC Desire C only for sim unlocking it. So far I am pleased with the original firmware (ICS 4.0) - after disabling some apps the phone runs fast and smooth.
The question is: does rooting modify the original OS in such a way that instabilities may occur?
Thanks.
Click to expand...
Click to collapse
Rooting itself doesn't modify anything besides installing an app called Superuser.
You deleting/disabling apps that were not meant to be disabled does.
dr.pythagora said:
Hi,
I plan to root a HTC Desire C only for sim unlocking it. So far I am pleased with the original firmware (ICS 4.0) - after disabling some apps the phone runs fast and smooth.
The question is: does rooting modify the original OS in such a way that instabilities may occur?
Thanks.
Click to expand...
Click to collapse
Please, read this for first before doing anything: http://forum.xda-developers.com/showthread.php?t=2323518
(Thanks to @aashay960 )
smoza said:
Please, read this for first before doing anything: http://forum.xda-developers.com/showthread.php?t=2323518
(Thanks to @aashay960 )
Click to expand...
Click to collapse
Thank you for the related link. Helpful.
As I like, for the moment, to stick to the original firmware (to me, it is the most stable among all avalable roms for HTC Desire C), I still have two more questions:
- will the rooting stop the handset from receiving official updates?
- assume I root the handset and install cwm recovery and backup the current rom.
if ever I like to restore this backup, I will need to flash a kernel boot.img.
can I extract the kernel related to my current firmware so I can flash it after I restore?
Thanks.
dr.pythagora said:
Thank you for the related link. Helpful.
As I like, for the moment, to stick to the original firmware (to me, it is the most stable among all avalable roms for HTC Desire C), I still have two more questions:
- will the rooting stop the handset from receiving official updates?
- assume I root the handset and install cwm recovery and backup the current rom.
if ever I like to restore this backup, I will need to flash a kernel boot.img.
can I extract the kernel related to my current firmware so I can flash it after I restore?
Thanks.
Click to expand...
Click to collapse
- As far as I know, you can receive updates but you cannot apply them. It will show in the notifications "Software Update, Click to download" when you download it, it will reboot to recovery and stop there. Again, I'm not 100% sure about this but this happened to me once.
- If you flash a custom kernel like Prometheus Kernel, then you will have to flash the stock boot.img if you wanna go back to stock completely. But if you never changed your kernel from stock, then you don't need to do anything. I have provided the link to stock kernel and stock recovery as well, in the Index thread. (Link in my signature)
PS - As far as Custom ROMs go, you should try the Sense Roms. All of them are based on the stock ROM so all of them are completely stable. You can always put the 'Stock theme' on these roms to make them look like the Stock ROM and you will end up with a ROM that looks exactly like Stock but performs much better and has increased functionality
Hope this was helpful. I'll be glad to answer any further questions.
It will not definitely modify your system it will add a folder to your system to access the system... and also it adds app called Superuser or SuperSU ....
Features of Rooting:
Android rooting is the process of allowing users of smartphones, tablets, and other devices running the Android mobile operating system to attain privileged control (known as "root access") within Android's subsystem.
Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices, resulting in the ability to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. On Android, rooting can also facilitate the complete removal and replacement of the device's operating system, usually with a more recent release of its current operating system. Most of the time,[citation needed] rooting a device voids its warranty.
From Wikipedia ...

[Q&A] [STOCK][D58XX][5.0.2] Firmware 23.1.A.0.690 Generic [ROOT/XZDR/SuperSU]

Q&A for [STOCK][D58XX][5.0.2] Firmware 23.1.A.0.690 Generic [ROOT/XZDR/SuperSU]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [STOCK][D58XX][5.0.2] Firmware 23.1.A.0.690 Generic [ROOT/XZDR/SuperSU]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can i flash zip or ftf via adb? i'm using cm12 rom.
hi guys,
I bought a Z3C and I just checked the bootloader is not locked .
pen the dialler and enter #*#7378423#*# to access the service menu.
Tap Service info > Configuration > Rooting Status. Bootloader unlock allowed says Yes
I wanted to know if I could flash via Flashtool software directly ?
OK, so I've used the method described in the thread, flashed firmware.zip from recovery on rooted 4.4.4. (.77), after flashing I wiped cache and dalvik, rebooted, android was upgraded, system booted, and all of my apps and settings remained intacted. Is this normal? I expected clean start. I used D5803_23.1.A.0.690_Generic_NCB-Root-XZDR2.8.3-SuperSU.
savudin said:
OK, so I've used the method described in the thread, flashed firmware.zip from recovery on rooted 4.4.4. (.77), after flashing I wiped cache and dalvik, rebooted, android was upgraded, system booted, and all of my apps and settings remained intacted. Is this normal? I expected clean start. I used D5803_23.1.A.0.690_Generic_NCB-Root-XZDR2.8.3-SuperSU.
Click to expand...
Click to collapse
If you didn´t wipe data in recovery, then no data should be wiped. That´s normal.
Yes, that's it. But, did I had to wipe data? I've read that clean install is recommended. I've noticed no problems in the last couple of hours of usage.
Dirty Flash from 23.0.1.A.5.77
I dirty flashed 23.1.A.0.690 from Greatslon MIUI v5 23.0.1.A.5.77 and still have root.
The phone froze and bootlooped a couple of times when i installed and restarted it, but patience was rewarded, as it finally booted.
I can still mount /system as rw both via adb shell, "onboard" terminal and through Root Browser.
Can i be of some help with a logcat, and in case how?
I am a software developer myself, but in a different branch than android. I just can't see through how i should get started with android development.
Great work guys
I guess i should add, that i still have my bootloader locked.
So to summarize:
>Bootloader locked (never unlocked)
>Firmware 23.1.A.0.690 from this thread
>Full root
>System R/W
Hey,
is there a chance to change the carrier name on the lockscreen? In the upper left corner it says "no service" but my carrier is already set up successfully.
Maybe its just because im from germany and its a generic rom or something. so is there a option to set up manually?
greets
Interesting, I did exactly the same but only have partial root, meaning that my system indicates root but I don't have writing permissions. Tried the ADB fix but did not work. Any other suggestions for getting full root again?
FYI: Nut has mentioned that he fixed recovery in his main development thread and will be working on releasing it to everyone soon.
Tnx for ur great work... but i have problem to download from mega site.. and specialy from the folder...
can anyone give me the direct link of [5.0.2] Firmware 23.1.A.0.690 Generic and A.5.77... not the folder link...
and can anyone tell me where exactly save the file we download from mega site ?
i cant find it anywhere...
Tnx alot.. :xX
How to delete recovery when it not working, thanks
Can't try new xposed for lollipop because it require install from recovery. And recovery not working in 5.0.2
air32 said:
Hey,
is there a chance to change the carrier name on the lockscreen? In the upper left corner it says "no service" but my carrier is already set up successfully.
Maybe its just because im from germany and its a generic rom or something. so is there a option to set up manually?
greets
Click to expand...
Click to collapse
edit the build.prop
what if I restore the TA Backup after that?
AndreDNA said:
what if I restore the TA Backup after that?
Click to expand...
Click to collapse
You would only need to restore the TA backup if you've unlocked your bootloader in the past.
I'm locked now, but it seem that I have to be unlocked to manage in upgrading to LP and keep the R/W is that right?
Sent from my D5803 using XDA Free mobile app
AndreDNA said:
I'm locked now, but it seem that I have to be unlocked to manage in upgrading to LP and keep the R/W is that right?
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
No, system rw is working atm with the newest(2.8.3) release from nut with locked bl. At least for Z3C . the system rw not working refers to other devices.
So when he manages to get the new recovery working you should just be able to install it. That is my hope at least. Anyway in case it doesnt you can backup with titanium backup and after flashing everything again just restore.
2mal16 said:
No, system rw is working atm with the newest(2.8.3) release from nut with locked bl. At least for Z3C . the system rw not working refers to other devices.
So when he manages to get the new recovery working you should just be able to install it. That is my hope at least. Anyway in case it doesnt you can backup with titanium backup and after flashing everything again just restore.
Click to expand...
Click to collapse
oh!
Really thanks for the answers, but I'm not sure to have understand (first sony for me).
I have kk, rooted and with locked bootloader. I have no recovery (I can't manage in flashing that without unlock), so how can I flash the preeroted LP?
I understand that if I backup TA, unlock BL, flash a recovery, flash a pre-rooted LP (after a full wipe), flash the last NUT recovery and then relock the BL restoring TA, I should finally have LP with root, R/W, and drm feature right? Am I missing something? Sorry for the High Noob Lvl xD
AndreDNA said:
oh!
Really thanks for the answers, but I'm not sure to have understand (first sony for me).
I have kk, rooted and with locked bootloader. I have no recovery (I can't manage in flashing that without unlock), so how can I flash the preeroted LP?
I understand that if I backup TA, unlock BL, flash a recovery, flash a pre-rooted LP (after a full wipe), flash the last NUT recovery and then relock the BL restoring TA, I should finally have LP with root, R/W, and drm feature right? Am I missing something? Sorry for the High Noob Lvl xD
Click to expand...
Click to collapse
Go to the thread of NUT dual recovery and (assuming your on a windows pc) download the installer for nut dual recovery. it will let you install the recovery on locked bootloader by running the install.bat file. with this recovery you can then flash a prerooted lollipop zip (you can do it yourself with prf creator, include the newest SuperSU zip and the newest dual recovery zip together with stock lollipop rom) after wiping your phone. people also just flashed over KK but i prefer to do it clean and set up my phone newly again. you will then end up with a phone which has system rw and root on lollipop but the recovery will be gone until NUT fixes it. That is what everybody is waiting for.
So unlocking BL wont really gain you anything except sonys DRM keys not working. it will just introduce an additional step to relock them.
Here is the thread: http://forum.xda-developers.com/showthread.php?t=2261606
to get into recovery just spam the volume up button(or down since it has two recoveries ) when your phone boots and lights up the led.

Problem in ota-update after installing kingroot

Hi all ,
This problem is facing very one how install kingroot and made his/her device rooted with kingroot , the root is done will , but after Root we can receive ota updates but when we download and install the ota update a problem found :
Unexpected error : install-recovary.sh status 7
I have trying to make full un-root by kingroot , or superus and nothing fixed until now !!!
Some people told me that you must install stock-rom !?
But why stock-rom if there is better and easy solution ?
I need your help developers I guess this problem not hard one for you ^_^ .
So who is the hero that's will save the day
Thanks.
As I've told you, you need the stock install-recovery.sh for your device (LUZ17x or LUZ59x?)
Everything else it way too complicated! (You will need an unlocked Bootloader, modded stock-recovery or TWRP, patched updater-script, etc...)
But it seems, nobody here is willing to pull the file (or even better a stock system.img) from their device.
I forgot to pull a system.img before rooting, so I can't help.
Seems, that there is unfortunately no real active community in Thailand or Turkey (apart from the language barrier), when it comes to these devices.
At least until now.
update
theeteempire said:
Hi all ,
This problem is facing very one how install kingroot and made his/her device rooted with kingroot , the root is done will , but after Root we can receive ota updates but when we download and install the ota update a problem found :
Unexpected error : install-recovary.sh status 7
I have trying to make full un-root by kingroot , or superus and nothing fixed until now !!!
Some people told me that you must install stock-rom !?
But why stock-rom if there is better and easy solution ?
I need your help developers I guess this problem not hard one for you ^_^ .
So who is the hero that's will save the day
Thanks.
Click to expand...
Click to collapse
if you want update then why u rooted your device? this is the basic thing you have to keep in mind before root you device that you cant install OTA if your device is rooted or any thing is changed into the system(i.e. cant be done without root).
The people telling you about installing stock rom, is the best and last solution according to me... search the net you will surely find the stock rom and its procedure to install as well...
Best of luck with searching and flashing the stock rom:good:
sagar27691 said:
if you want update then why u rooted your device? this is the basic thing you have to keep in mind before root you device that you cant install OTA if your device is rooted or any thing is changed into the system(i.e. cant be done without root).
The people telling you about installing stock rom, is the best and last solution according to me... search the net you will surely find the stock rom and its procedure to install as well...
Best of luck with searching and flashing the stock rom:good:
Click to expand...
Click to collapse
I think that un-root will solve this problem with out need to make stock-rom
vel_tins said:
As I've told you, you need the stock install-recovery.sh for your device (LUZ17x or LUZ59x?)
Everything else it way too complicated! (You will need an unlocked Bootloader, modded stock-recovery or TWRP, patched updater-script, etc...)
But it seems, nobody here is willing to pull the file (or even better a stock system.img) from their device.
I forgot to pull a system.img before rooting, so I can't help.
Seems, that there is unfortunately no real active community in Thailand or Turkey (apart from the language barrier), when it comes to these devices.
At least until now.
Click to expand...
Click to collapse
I need stock " install-recovary.sh for LUZ17E ". But no one help me to do that , I think there is no real developers here in second generation
theeteempire said:
I think that un-root will solve this problem with out need to make stock-rom
Click to expand...
Click to collapse
If you don't have a backup of that file (either made by yourself or the rooting software you have used), then 'unrooting' cannot help. That file is gone.
I went through @Sadronis's LUZ17E rom dump, extracted install-recovery.sh and attached it for you. But next time, please remember to backup the original file before rooting since especially for non-Nexus devices, stock ROMs (and thus files inside them) are not easy to find.
pawitp said:
If you don't have a backup of that file (either made by yourself or the rooting software you have used), then 'unrooting' cannot help. That file is gone.
I went through @Sadronis's LUZ17E rom dump, extracted install-recovery.sh and attached it for you. But next time, please remember to backup the original file before rooting since especially for non-Nexus devices, stock ROMs (and thus files inside them) are not easy to find.
Click to expand...
Click to collapse
Thank you man.
I can't replace the file or. Overwrite it , I have the root for my device but I can do nothing do you know why ?
theeteempire said:
Thank you man.
I can do nothing do you know why ?
Click to expand...
Click to collapse
Yes, you have to mount /system as "rw", for example:
Code:
adb remount
vel_tins said:
Yes, you have to mount /system as "rw", for example:
Code:
adb remount
Click to expand...
Click to collapse
Thank youuuuuuuuuu you help me a lot man
It's all done good .
I wanna ask you the stok rom that shared in this forum , can it be updated normally or not ?
First of all king root did not support on mine tablet but after a week ,i install 4.6 version of kingroot and it work but after a day when i want to update mine tablet galaxy 4 10.1 with ota ,it seem that the operating system of your device has been ........try to connect pc and etc.please help me ,i try lots of things like wipe cage, re factory etc others but now please help me without using pc.

Huawei P9 - Android 6 to 7 Firmware

Hi all,
Ive been a fair while out of flashing ROMs since Note 4 Edge / HTC M7 and have today unlocked bootloader and rooted my P9.
It is currently Australian Vodafone release EVA-L09CC346B160 (Android 6) but I want Nougat.
There is no local carrier updates available but I understand that there is Android 7 available in Australia on 'international' branded handsets.
How can I identify what this firmware is for international Nougat? Can some one assist me. Or can someone advise what would be a suitable equivalent firmware that I can use in place of.
I am unsure how this device goes in flashing ROMs of higher or lower android versions on the current firmware and dont really want to brick it.
Thanks for any tips / suggestions
Umm, just found a thread mentioning L09C636B361 - will check this out, but is there any more recent? And still how does fl;ashing other premade ROMs on 7 go on top of the current Android 6 firmware go?.. Ta
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
using this guide you can update to the latest nougat release
Thank yuo Xtcislove
I have completed the steps suggested and now have Nougat. Though it is a newer version being .383 which was updated via OTA to .378 and then zip to .383.
Thank you for the help
I'm trying to flash firmware on my P9, now I have EVA-L09C40B181, but it stuck on 5% and HiSuite shows Recovery failed! I tried custom firmware, same problem. What can I do ?
Dfani511 - just follow the instructions in the thread provided by Xtcislove, it works but took me a long time.
I found the steps concerning the update to be added in dload was a little not clear, in the update zip that's downloaded, you need to open it until you get the dload folder, extract that and copy to the SD card.
Throughout my updating, o never ended up on the firmware you have
This N seems to be working fine, nicer looking.
I do have 1 issue, no matter what I do I can not get root to work. I'm on .383, can this one be rooted or not currently? If it can, how do I root .383? I have TWRP 3.1.0.3 as current recovery..
Or, is that ok to flash on my current P9 L09C432B383 ? from this thread - https://forum.xda-developers.com/p9/development/root-pre-rooted-boot-img-p9-nougat-b378-t3574548
The stock and pre-rooted boot.img states its form .378 but would it be ok on .383?
I dont know how to get root on it currently...
twerg said:
This N seems to be working fine, nicer looking.
I do have 1 issue, no matter what I do I can not get root to work. I'm on .383, can this one be rooted or not currently? If it can, how do I root .383? I have TWRP 3.1.0.3 as current recovery..
Or, is that ok to flash on my current P9 L09C432B383 ? from this thread - https://forum.xda-developers.com/p9/development/root-pre-rooted-boot-img-p9-nougat-b378-t3574548
The stock and pre-rooted boot.img states its form .378 but would it be ok on .383?
I dont know how to get root on it currently...
Click to expand...
Click to collapse
This is what I did to root my Huawei P9 on Nougat L09C432B383:
Use the SuperSU-v.27.9-201612051815EMUI5.0.zip file flash via custom recovery and it should root your device no problem.
twerg said:
This N seems to be working fine, nicer looking.
I do have 1 issue, no matter what I do I can not get root to work. I'm on .383, can this one be rooted or not currently? If it can, how do I root .383? I have TWRP 3.1.0.3 as current recovery..
Or, is that ok to flash on my current P9 L09C432B383 ? from this thread - https://forum.xda-developers.com/p9/development/root-pre-rooted-boot-img-p9-nougat-b378-t3574548
The stock and pre-rooted boot.img states its form .378 but would it be ok on .383?
I dont know how to get root on it currently...
Click to expand...
Click to collapse
Use this
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
xtcislove said:
Use this
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Click to expand...
Click to collapse
Hey xtcislove - is there a preferred version? 1, 2 or 3 do you recommend? Thanks mate
--------------
EDIT - Nevermind, Xtcislove, your the best man, appreciate your help with your guides etc. I went with option 1 and the handset is now rooted on Nougat. Thanks so much
twerg said:
Hey xtcislove - is there a preferred version? 1, 2 or 3 do you recommend? Thanks mate
--------------
EDIT - Nevermind, Xtcislove, your the best man, appreciate your help with your guides etc. I went with option 1 and the handset is now rooted on Nougat. Thanks so much
Click to expand...
Click to collapse
3 is the version i preffer, you cant freeze apps with v1 but most things should work fine.
btw you can flash v3 over v1.
Ive flashed v3 over 1 and all appears good, root working fine. Thanks again.
Though I have noticed on both v1 and v3 that SuperSU binary needs to be updated, ob both v1 and v3. The phone fails to update both, states unsuccessful and to reboot, which also does not update the binary.
Only other thing I have done is to get BusyBox.
What can be done about the failing binary update? Will it be fine to leave as is, just getting rid of the prompt when it appears, or does it really need to have the update done sometime?

[ROM] [7.1.1] Stock Rom for J320A/J320AZ/J320AG

This is an unrooted 100% Stock J320AUCU3BQI5 firmware.
Working on all exynos j3 models!! (You first need root and to flash with flashfire)
AG models will probably need to enable oem unlock in dev options.
Download
As I said no root, but you can always downgrade back to mm if you need root.
Btw the eng_ root kernel won't boot the system, but it will let you mount as RW and you can edit things thru adb... someone figure out root on this thing!
Thanks to @Iurop for testing AG
@DamienMc thanks for assist me and help me. My J320AG now works with Nougat 7.1.1 without any problem.
Here a couple of screenshots.
galaxy express prime(J320A)
Um I have a question the firmaware above if I want to install it do I need to root? if yes how do I root?
부캐입니다 said:
Um I have a question the firmaware above if I want to install it do I need to root? if yes how do I root?
Click to expand...
Click to collapse
To root just follow this method:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-j320a-j320az-alternate-method-t3627225
Hi lurop thanks for your reply! but i have another question to flash nougat file do i have to root or i dont have to
Hi, yes you have to root the phone following the method posted above. Then install flashfire and use it to flash the rom.
Have you do something similar already?
If you do not wish to root and your device is the A or AZ model you can update with Odin.
I fixed and uploaded the full firmware @Iurop provided. You can find that here
Finally got time to mess around with root...and unfortunately we do need a new eng_boot.
But fortunately, like I mentioned, we can still use our old eng_root boot to acquire a root shell.
Btw noticed this Rom does not update stock recovery. I'll package up a fix for it tomorrow, if anyone actually cares
DamienMc said:
Finally got time to mess around with root...and unfortunately we do need a new eng_boot.
But fortunately, like I mentioned, we can still use our old eng_root boot to acquire a root shell.
Btw noticed this Rom does not update stock recovery. I'll package up a fix for it tomorrow, if anyone actually cares
Click to expand...
Click to collapse
I care. Thanks for your time and effort; I can imagine that it (developing) seems rather thankless at times, but your contributions are definitely appreciated.
DamienMc said:
Finally got time to mess around with root...and unfortunately we do need a new eng_boot.
But fortunately, like I mentioned, we can still use our old eng_root boot to acquire a root shell.
Btw noticed this Rom does not update stock recovery. I'll package up a fix for it tomorrow, if anyone actually cares
Click to expand...
Click to collapse
Until now my J320ag works perfectly, no problem at all, phone, sms, internet, app everything run absoluttely fine.
Thanks @DamienMc
I wonder if I could port this to the J320FN?
stock recovery patch
I'll update the rom one day, but this patch is the easiest way to update things...
To apply you must use your pc, use Odin to flash the included eng_root kernel. When it boots the logo will remain onscreen, after two minutes or so you can click the recovery.bat and let it do its thing.
is this rom have arbic ?
tested and working like charm, is there any tool etc for add arbic etc ?
Cant be ported to J320F because of different Chipset,right?
Mr Hassan said:
tested and working like charm, is there any tool etc for add arbic etc ?
Click to expand...
Click to collapse
I never had time to look into adding extra languages, and afaik more locale doesn't support Arabic (plus it doesn't translate everything)
jnk3344 said:
Cant be ported to J320F because of different Chipset,right?
Click to expand...
Click to collapse
Correct, will not work. Most importantly tho they don't have a nougat kernel. And if they did, they'd have their own stock rom... Sorry @Diamond26
DamienMc said:
I never had time to look into adding extra languages, and afaik more locale doesn't support Arabic (plus it doesn't translate everything)
Correct, will not work. Most importantly tho they don't have a nougat kernel. And if they did, they'd have their own stock rom... Sorry @Diamond26
Click to expand...
Click to collapse
Yeah I know sadly...
will this remove region lock?
will this remove region lock?
DamienMc said:
Finally got time to mess around with root...and unfortunately we do need a new eng_boot.
But fortunately, like I mentioned, we can still use our old eng_root boot to acquire a root shell.
Click to expand...
Click to collapse
Isn't eng_boot.tar just a boot.img? Could we extract build.prop from the Nougat ROM and the boot.img from the firmware to update the Root_J320A.zip in your root thread?
@DJJosephJumper
That method will work, we just can't boot while rooted with the stock boot. We need a permissive boot. if you edit that root like you mentioned, it'll only boot to the logo with a working shell. Su commands work there, so it will with with permissive.
Eng_root will do the same, boot to logo only with a rooted shell

Categories

Resources