Related
Hi,
I've just upgraded the OS of my HTC One to 4.4 with Sense 5.5 and rooted the handset.
I took the majority of information and downloads from here:
http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/
while the rooting stuff I grabbed from here:
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
So ok this is my 3rd OS upgrade with root so in a basic sense I did this:
- Updated TWRP to version 2.7.x
- Used TWRP recovery WIPE option to format / (root)
- Installed the 4.4 stock ROM from above link
- TWRP then asked me if I would like to root the device and so I said ok to that
- Booting into the OS everything was fine and I had the SU-Root icon in the Apps menu
I'm not sure what happened if the battery got drained or so but in anycase after a restart the handset was no longer rooted??
As I have the 2.65 SU-ROOT Zip file on my storage partition I went back to TWRP and Install then clicked on the Zip file and re-rooted the device; then wiped the cache and booted back into the OS.
For some reason now the phone isn't able to be rooted at all? I am pretty sure I had similar behavior with Android 4.3, though the initial stock build was absolutely fine.... I think I managed to get from 4.1 to 4.2 successfully.
Will I need to format the handset again then re-install the ROM and re-root or is something else going on which I'm unaware of??
I've also noticed that the device becomes un-rooted each time the battery goes low or dies for some reason... a persistent root would be nice as I have many apps needing full root access; not to mention being able to work with the full Android system too.
Would anyone be able to suggest anything? Thanks!
JohnnySSH said:
Hi,
I've just upgraded the OS of my HTC One to 4.4 with Sense 5.5 and rooted the handset.
I took the majority of information and downloads from here:
http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/
while the rooting stuff I grabbed from here:
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
So ok this is my 3rd OS upgrade with root so in a basic sense I did this:
- Updated TWRP to version 2.7.x
- Used TWRP recovery WIPE option to format / (root)
- Installed the 4.4 stock ROM from above link
- TWRP then asked me if I would like to root the device and so I said ok to that
- Booting into the OS everything was fine and I had the SU-Root icon in the Apps menu
I'm not sure what happened if the battery got drained or so but in anycase after a restart the handset was no longer rooted??
As I have the 2.65 SU-ROOT Zip file on my storage partition I went back to TWRP and Install then clicked on the Zip file and re-rooted the device; then wiped the cache and booted back into the OS.
For some reason now the phone isn't able to be rooted at all? I am pretty sure I had similar behavior with Android 4.3, though the initial stock build was absolutely fine.... I think I managed to get from 4.1 to 4.2 successfully.
Will I need to format the handset again then re-install the ROM and re-root or is something else going on which I'm unaware of??
I've also noticed that the device becomes un-rooted each time the battery goes low or dies for some reason... a persistent root would be nice as I have many apps needing full root access; not to mention being able to work with the full Android system too.
Would anyone be able to suggest anything? Thanks!
Click to expand...
Click to collapse
I think there is an update for supersu
please google it
if yes than move it to your phone and flash it in the recovery
Thanks I managed to find version 1.94 which worked fine:
http://download.chainfire.eu/396/
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
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
So the android 6.0 OTA update just got available for me.
I tried to install it but the update failed. I have a rooted xperia z3 c (D5803) running android 5.1.1 with locked bootloader and custom recovery installed.
So my question is, how do i install the update? i dont mind if i lose root and custom recovery, i just want to keep my apps and settings.
-Victor- said:
So the android 6.0 OTA update just got available for me.
I tried to install it but the update failed. I have a rooted xperia z3 c (D5803) running android 5.1.1 with locked bootloader and custom recovery installed.
So my question is, how do i install the update? i dont mind if i lose root and custom recovery, i just want to keep my apps and settings.
Click to expand...
Click to collapse
The only way you will get OTA to work via PC Companion is buy putting your phone back to stock (no root, no recovery). It might be possible to use flashtool to restore a stock build without wiping data, but if it goes into a bootloop, then you will have to wipe it to fix it, loosing everything.
You could use Titanium backup to save all your apps/settings onto the SD card, then force PC Companion to 'repair' your phone. But then you'll be stuck with trying to root your MM build so you can restore your TA backup (Don't be tempted by Kingroot).
Have you considered moving to an MM custom rom? Slim works with a locked bootloader and is very popular, or an MM stock prerooted build. Both of these have install instructions that recomend a wipe, but it may not be necessary.
Several users in the Slim thread have said they successfully flashed without wipe.
There are still lots of glitches and problems with the MM build, are you sure you want to go through the pain of being an early adopter? Another month or so and they'll all be fixed.
Make sure you do a TWRP backup before you start, preferably onto the SD card.
Didgesteve said:
The only way you will get OTA to work via PC Companion is buy putting your phone back to stock (no root, no recovery). It might be possible to use flashtool to restore a stock build without wiping data, but if it goes into a bootloop, then you will have to wipe it to fix it, loosing everything.
You could use Titanium backup to save all your apps/settings onto the SD card, then force PC Companion to 'repair' your phone. But then you'll be stuck with trying to root your MM build so you can restore your TA backup (Don't be tempted by Kingroot).
Have you considered moving to an MM custom rom? Slim works with a locked bootloader and is very popular, or an MM stock prerooted build. Both of these have install instructions that recomend a wipe, but it may not be necessary.
Several users in the Slim thread have said they successfully flashed without wipe.
There are still lots of glitches and problems with the MM build, are you sure you want to go through the pain of being an early adopter? Another month or so and they'll all be fixed.
Make sure you do a TWRP backup before you start, preferably onto the SD card.
Click to expand...
Click to collapse
Does the custom roms unlock the bootloader?
-Victor- said:
Does the custom roms unlock the bootloader?
Click to expand...
Click to collapse
No, neither does using a stock prerooted.
Generally, is it says 'stock' or 'LB' in the title of the thread, then you can use it without having to mess with the bootloader.
Hi,
Im kind of late in terms of LG G4. But it it is now my curret phone. Have expierence installing unlock bootloader installing twrp and supersu on motorola phones. Owned a LG G2 and bricked it because of flashing wrong files.
There are alot of variants to LG phones...compared to motorola that create a higher risk.
So im trying to be cautious here.
Ive done my research and found this link.
https://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Can someone confirm that this will work on my LG G4 T mobile 20v with 6.0 marshmellow?
From what i understand i just skip the first step Flashing the imagee (because it is for the 20i) then continue with the normal routine? Is this twrp and supersu compatible?
Is there a way to restore my variant stock rom if i screw up?
Bigd1988 said:
Hi,
Im kind of late in terms of LG G4. But it it is now my curret phone. Have expierence installing unlock bootloader installing twrp and supersu on motorola phones. Owned a LG G2 and bricked it because of flashing wrong files.
There are alot of variants to LG phones...compared to motorola that create a higher risk.
So im trying to be cautious here.
Ive done my research and found this link.
https://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Can someone confirm that this will work on my LG G4 T mobile 20v with 6.0 marshmellow?
From what i understand i just skip the first step Flashing the imagee (because it is for the 20i) then continue with the normal routine? Is this twrp and supersu compatible?
Is there a way to restore my variant stock rom if i screw up?
Click to expand...
Click to collapse
These instructions are more up to date and accurate! - https://forum.xda-developers.com/tmobile-g4/general/how-to-unlock-bootloader-flash-twrp-t3344421
on line 10 change the command to 'fastboot boot recovery "NAME OF TWRP FILE" - this will boot twrp on the phone itself, then from phone install twrp and supersu from your microsd card
you need to put a copy of twrp in the adb/fastboot folder on your pc and twrp and supersu on your microsd card before starting, to avoid mistakes name them recovery.img and supersu.zip
latest twrp: https://dl.twrp.me/g4/twrp-3.1.1-1-g4.img.html
latest supersu: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
rooted with recovery installed, thank you
can I flash any tmobile custom rom for the lg g4? or will it cause brick too?
phone is marshmallow
Seems to be something wrong with this TWRP....cant make a backup.....screen goes black...think phone is still on? have to take battery out....tried several times.
not flashing a custom rom till I can make a backup
deltadiesel said:
Seems to be something wrong with this TWRP....cant make a backup.....screen goes black...think phone is still on? have to take battery out....tried several times.
not flashing a custom rom till I can make a backup
Click to expand...
Click to collapse
Start the backup and wait at least 10 min. The screen should become responsive after the backup has finished - normally sooner but it is not crashing just using all power available.
.
Sent from my LG-H815 using XDA Labs
Did exactly that...was response after backup
Thank you