Database Develop

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.

Update Available 2.19.401.2

Here you can download OTA, fresh firmware or system image to update your device.
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
firmware.zip only [19.6 MB]
2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip [TWRP] [1.15 GB]
Downloads: mega
​Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer. Don't know, what's that. Looks like a hash or a signature.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed). If you want just firmware, take it. Should be fastboot flashable.
*Additional notes*
Next lines describe my experience before I returned the device state to nearly stock.
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.

city2026 said:
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
Download: mega
Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed).
*Additional notes*
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.
Click to expand...
Click to collapse
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know

TWRP system backup added
csoulr666 said:
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know
Click to expand...
Click to collapse
I tried to update from recent backup (the one before I changed kernel and deleted system apps), but facebook.odex didn't let me.
Finally, the very first backup did it. I took only system and boot, switched twrp recovery to htc, skipped all setup and installed OTA over fresh system.
Here you go. Now you have TWRP image of this update.
BTW, kernel version is different. CL build number is the same.

Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks

ash0r said:
Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks
Click to expand...
Click to collapse
Unfortunately you cannot flash this with TWRP.

Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks

ash0r said:
Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks
Click to expand...
Click to collapse
You can try to restore the TWRP backup in the post. And yes, you will lose every mod since it is a backup of the stock, unrooted firmware.
The main problem of flashing the OTA zip would be that you will have to relock the bootloader before installing . So if you unlock it again, the internal storage will be wiped. The best way is to backup everything(Including the internal storage) and then proceed.

Actually, you can save your data while upgrading from non-worthy stock.
So, you may do this
Full backup, you never know what can go wrong.
Save or make a note of what you changed by yourself in system (from busybox to xposed & various modes.). You may use TB for sys-apps and simple file copying for modes. *
Restore updated system image from 1st post, so you have updated system.
See if it worked out and restore/reinstall your other system stuff.
* Remember, you still may access files of your twrp backup images through some archiver. Like I do using 7-Zip.
It's very important to save backup somewhere, cause it might be that my image can be not absolutely clean or can be not absolute right for your phone (like sell location difference). So it'll be easy to return back to working machine.
For this purposes I also setted up my TB for daily auto-backup of texts and settings and weekly backup of apps.
---
Don't sure about relock for upgrading. It seems to be launching, but it needs pure system and original boot & recovery. Some fastboot-magic helps here. That's how I did it after restoring to the very first backup.

So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful

The Watergod said:
So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful
Click to expand...
Click to collapse
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.

My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.

keninzeg said:
My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.
Click to expand...
Click to collapse
Did you buy your phone from a carrier? Carrier phones get different software updates

csoulr666 said:
Did you buy your phone from a carrier? Carrier phones get different software updates
Click to expand...
Click to collapse
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.

keninzeg said:
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.
Click to expand...
Click to collapse
If it has EE applications then it is an EE branded phone. Your updates will arrive differently and will have a different software number. So using the Europe zip will not help.

city2026 said:
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.
Click to expand...
Click to collapse
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance

The Watergod said:
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance
Click to expand...
Click to collapse
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.

city2026 said:
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.
Click to expand...
Click to collapse
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved

The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Simply flash custom kernel: like liberty sense or stock sense w/ dt2w.
It will unlock the opportunity to write on every partition. I mean system, cache, etc.

The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Hi
I will assume you have the virus I have been seeing lately that wouldn't allow you to reset the phone, where in reset option the automatic restore option remains checked and you can't uncheck it.
The only solution is through TWRP, you need to enter TWRP, erase Cache, Data, System then flash the Lollipop ROM again or stock from here: http://forum.xda-developers.com/one...one-mini-2-t3250020/post63859743#post63859743

So there is no Rom available that's pretty much stock without bloatware that I can install with twrp? If not is there some idiots guide to putting my stock recovery back on thank you all again

[ROOT] Huawei P8 Lite ALE-L21, Android 6.0 Marshmallow

Hello there!
Following these steps, you'll be able to root your freshly marshmallowed P8 Lite.
The method was tested by several other users, with not just this model.
Requirements:
Huawei P8 Lite with the Chinese 6.0 Firmware
Unlocked bootloader
TWRP Recovery (Kirin Chipset)
Do you have everything above?
Good, here are the steps:
Go to THIS post, and download the attachment of it. (BETA-SuperSU-v2.67-SYSTEMMODE.zip)
Put this zip on your SD Card.
Boot into recovery and flash it.
That is all what you need to do.
Credits goes to: aufarxda for making the working zip, zirangua for trying and successfully rooting our device with this, and of course Chainfire for making rooting phones possible and easy.
Note:
If you tried with the official zips from Chainfire's thread, you should rooted your phone as well, but the root was lost after a few reboots.
At least it was like that for me.
The reason for this, Chainfire introduced a new way of rooting the phone, which called "systemless" root. It means, no modification is made to your /system partition, only to your boot image.
The install script of this zip checks for compatibility to do "systemless" root, and if it can do that, it'll do that.
However, with our device, something must be messed up with the boot image, because it seems to be resetting after few (or the first) reboots.
The downloaded zip was modified in a way, that the script only root your phone via the old method, modifying your /system partition.
The whole point to have a "systemless" root is not rerooting after every update, or system reset, however, it seems like it's not working well with our phone, so only the old method remains.

Twrp needed?

slimbullet said:
Twrp needed?
Click to expand...
Click to collapse
Yes, it's needed, and thanks for pointing this out.

How are flash in Recovery Mode? He gives 3 options: Reboot - Download new Version and Recovery - Shutdown!?

You have to flash TWRP by fastboot adb before.
TWRP is needed for flashing the zip files

daviddosa said:
Yes, it's needed, and thanks for pointing this out.
Click to expand...
Click to collapse
I did all of those steps and now i have blackscreen and my phone wont turn on....
I have twrt,unlockedbloader,beta 6.0,debugging etc and it dont work...
and the second boot animation missing

Surdyn said:
I did all of those steps and now i have blackscreen and my phone wont turn on....
I have twrt,unlockedbloader,beta 6.0,debugging etc and it dont work...
and the second boot animation missing
Click to expand...
Click to collapse
the same problem here

daviddosa said:
Hello there!
Following these steps, you'll be able to root your freshly marshmallowed P8 Lite.
The method was tested by several other users, with not just this model.
Requirements:
Huawei P8 Lite
Unlocked bootloader
TWRP Recovery (Kirin Chipset)
Do you have everything above?
Good, here are the steps:
Go to THIS post, and download the attachment of it. (BETA-SuperSU-v2.67-SYSTEMMODE.zip)
Put this zip on your SD Card.
Boot into recovery and flash it.
That is all what you need to do.
Credits goes to: aufarxda for making the working zip, zirangua for trying and successfully rooting our device with this, and of course Chainfire for making rooting phones possible and easy.
Note:
If you tried with the official zips from Chainfire's thread, you should rooted your phone as well, but the root was lost after a few reboots.
At least it was like that for me.
The reason for this, Chainfire introduced a new way of rooting the phone, which called "systemless" root. It means, no modification is made to your /system partition, only to your boot image.
The install script of this zip checks for compatibility to do "systemless" root, and if it can do that, it'll do that.
However, with our device, something must be messed up with the boot image, because it seems to be resetting after few (or the first) reboots.
The downloaded zip was modified in a way, that the script only root your phone via the old method, modifying your /system partition.
The whole point to have a "systemless" root is not rerooting after every update, or system reset, however, it seems like it's not working well with our phone, so only the old method remains.[/QUDo wee
Do wee need an sd card or it can be done witch the main storage?
Click to expand...
Click to collapse

not work stop Screen Takeoff and not star and restart
---------- Post added at 03:05 AM ---------- Previous post was at 02:52 AM ----------
blackscreen and my phone restart how fixed

daviddosa said:
Hello there!
Following these steps, you'll be able to root your freshly marshmallowed P8 Lite.
The method was tested by several other users, with not just this model.
Requirements:
Huawei P8 Lite
Unlocked bootloader
TWRP Recovery (Kirin Chipset)
Do you have everything above?
Good, here are the steps:
Go to THIS post, and download the attachment of it. (BETA-SuperSU-v2.67-SYSTEMMODE.zip)
Put this zip on your SD Card.
Boot into recovery and flash it.
That is all what you need to do.
Credits goes to: aufarxda for making the working zip, zirangua for trying and successfully rooting our device with this, and of course Chainfire for making rooting phones possible and easy.
Note:
If you tried with the official zips from Chainfire's thread, you should rooted your phone as well, but the root was lost after a few reboots.
At least it was like that for me.
The reason for this, Chainfire introduced a new way of rooting the phone, which called "systemless" root. It means, no modification is made to your /system partition, only to your boot image.
The install script of this zip checks for compatibility to do "systemless" root, and if it can do that, it'll do that.
However, with our device, something must be messed up with the boot image, because it seems to be resetting after few (or the first) reboots.
The downloaded zip was modified in a way, that the script only root your phone via the old method, modifying your /system partition.
The whole point to have a "systemless" root is not rerooting after every update, or system reset, however, it seems like it's not working well with our phone, so only the old method remains.
Click to expand...
Click to collapse
Hi this method work only with the chinese version (B535) on european version (B524) i got a bootloop ...
This happen to me

xander33 said:
Hi this method work only with the chinese version (B535) on european version (B524) i got a bootloop ...
This happen to me
Click to expand...
Click to collapse
so how do we root B524 now?

omid.quist said:
so how do we root B524 now?
Click to expand...
Click to collapse
Follow the tutorial on generale section provided by sokkoban the thead it s called [TUTORIAL] ...

how to recover after the boot loop ?? i tried this on the EU marshmallow and now im stuck !!

daviddosa said:
Hello there!
Following these steps, you'll be able to root your freshly marshmallowed P8 Lite.
The method was tested by several other users, with not just this model.
Requirements:
Huawei P8 Lite with the Chinese 6.0 Firmware
Unlocked bootloader
TWRP Recovery (Kirin Chipset)
Do you have everything above?
Good, here are the steps:
Go to THIS post, and download the attachment of it. (BETA-SuperSU-v2.67-SYSTEMMODE.zip)
Put this zip on your SD Card.
Boot into recovery and flash it.
That is all what you need to do.
Credits goes to: aufarxda for making the working zip, zirangua for trying and successfully rooting our device with this, and of course Chainfire for making rooting phones possible and easy.
Note:
If you tried with the official zips from Chainfire's thread, you should rooted your phone as well, but the root was lost after a few reboots.
At least it was like that for me.
The reason for this, Chainfire introduced a new way of rooting the phone, which called "systemless" root. It means, no modification is made to your /system partition, only to your boot image.
The install script of this zip checks for compatibility to do "systemless" root, and if it can do that, it'll do that.
However, with our device, something must be messed up with the boot image, because it seems to be resetting after few (or the first) reboots.
The downloaded zip was modified in a way, that the script only root your phone via the old method, modifying your /system partition.
The whole point to have a "systemless" root is not rerooting after every update, or system reset, however, it seems like it's not working well with our phone, so only the old method remains.
Click to expand...
Click to collapse
Hi Daviddosa you have installed chinese beta android 6 fw? On that firmware is camera with special light effects.. Can you make backup of that camera, and get it here, or copy complete camera sw? Thanks a lot!

Here is HwCamera.apk on Chinese version of MM 6.0

sokkoban said:
Here is HwCamera.apk on Chinese version of MM 6.0
Click to expand...
Click to collapse
thx. just put it in system apps? and replace the old one? because update wont work

sokkoban said:
Here is HwCamera.apk on Chinese version of MM 6.0
Click to expand...
Click to collapse
Thanks.. sadly it is not working. Just wondering why on chinese ROMs there is working light painting, but on EU ROMS no.

danvo01 said:
Thanks.. sadly it is not working. Just wondering why on chinese ROMs there is working light painting, but on EU ROMS no.
Click to expand...
Click to collapse
I'm wonderin too. But this is not only difference in Chinese ROM. On B524 not feature like Touch Plus, Smart Care, Mobile data traffic counter, HiCloud and many others
So my opinion is Chinese firmware is much better that European. For that I change my ALE-L21 to ALE-UL00

sokkoban said:
I'm wonderin too. But this is not only difference in Chinese ROM. On B524 not feature like Touch Plus, Smart Care, Mobile data traffic counter, HiCloud and many others
So my opinion is Chinese firmware is much better that European. For that I change my ALE-L21 to ALE-UL00
Click to expand...
Click to collapse
so.. do you think it is better to flash back chinese beta v 311 (?) instead of 524? I looked for more stable bluetooth connection, and now i see differences...

I never use Bluetooth. But Chinese version of 6.0 is B535

[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

Good source for firmwares?

I'm looking for a good source of firmwares, i know the famous sites but some firmwares doesn't seem to be listed. I know in the time os Samsung KIES there were tools which communicated directly with samsung.
For example these firmware builds for the SM-G975Ux aren't listed on most firmware sites but have the December secutiry update with binary/bootloader version 8: G975USQS8IVL1 and G975USQS8IVL2

All the big sites have ROMs for that phone (same one I have). There is no "Ux" model... it's *U or *U1, with the latter being unlocked. IF you search for U1 ROMs you have many selections, but most get the XAA version which will usually change carriers automatically based on the SIM card.
The latest BL=8 version I see there is https://www.sammobile.com/samsung/g...M-G975U1/XAA/download/G975U1UEU8IWB6/1741280/ which is the February 2023 security update. I believe this is the last one we are getting (but I could be mistaken as there may be 1 more security patch, I don't remember).

There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml

I'd recommend around sammobile and samfw. These are the two sources I use the most

hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?

Ben1987 said:
hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?
Click to expand...
Click to collapse
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?

WooBLOATERRRR said:
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?
Click to expand...
Click to collapse
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for

Right now I don't even care if I get the original firmware or a custom rom running... I hope I didn't brick it (((

My old device was a G930F, its unbreakable make sure you flash the right rom and wipe data and dalvik cache after flashing.... THis ons is locked so it doesn't have fastboot. My G-930F came with fastboot enabled so you can always fastboot a recovery.img. like TWRP
Did you try to download TWRP from twrp.me and "fastboot boot twrp-3.7.0_9-0-herolte.img" ? it should boot to twrp in fastboot mode (hold volume down + home + power).

Ben1987 said:
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for
Click to expand...
Click to collapse
1. is your KG status is broken?
2. Is your bootloader unlocked?

You know how to flash lineageos through twrp right? and how to use odin?
Maybe flash lineageos to see if everything works.... and then revert to original software. Be sure to wipe cache/dalvik and userdata

DaanNL said:
There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml
Click to expand...
Click to collapse
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).

WooBLOATERRRR said:
I solved the problem! I had unlocked the bootloader, but I also had to deactivate verity via CMD with twrp+adb "adb disable-verity"
ok i've solved the problem now, but does anyone know why i couldn't even start the original stock roms? Actually, the stock ROM should set everything to factory settings...
Click to expand...
Click to collapse

WooBLOATERRRR said:
1. is your KG status is broken?
2. Is your bootloader unlocked?
Click to expand...
Click to collapse
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday

Ben1987 said:
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday
Click to expand...
Click to collapse
Samsung/apple support in a nutshell

schwinn8 said:
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).
Click to expand...
Click to collapse
I've tried different firmwares, its all about snapdragon. You can also flash SM-G975W parts and other snapdragon variants.... there's a lot of variants out there.
I first upgraded and then downgraded to the parts i wanted and am on a rom now with security patch level December 2022, as long as the binary version is the same there's no problem. I've got the latest modem installed and the oldest firmare and bootloader for the latest binary version, i can upgrade or downgrade my bootloader. I already asked someone before if this was possible and if he could confirm because before i was only able to flash CSC and AP i think.
If there's no updates comming anymore why not downgrade and wait for a new leak
I'm also sure we can unlock the bootloader, i'm trying to make an lposed module. I've installed lspatch and lposed and they work fine for some modules. The bootloader unlock has several prerequisites (properties and such) if i can make it look for other properties or something like that we might get an unlock option. Also it looks for an encrypted file on EFS, if someone with an unlocked samsung phone could copy that file we would be a lot further.
It's called /efs/sec_efs/sktdm_mem/encmembership.txt and should be an encrypted file, also if anyone knows how to set ro properties without root (like a stub before the preference controller starts) this would be very usefull.