Database Info

CF-Auto Root for MH8 firmware

Chainfire has updated his CF auto root for the annoying new MH8 firmware with new bootloader!
Yay we can now root our new firmware.
Here's his Google plus page for CF Auto Root download
https://plus.google.com/+Chainfire/posts/5ggu7naWtaW
Thanks Chainfire, you're the man!!!

Obagleyfreer said:
Chainfire has updated his CF auto root for the annoying new MH8 firmware with new bootloader!
Yay we can now root our new firmware.
Here's his Google plus page for CF Auto Root download
https://plus.google.com/+Chainfire/posts/5ggu7naWtaW
Thanks Chainfire, you're the man!!!
Click to expand...
Click to collapse
Pointless thread. Everyone knows to find chainfires thread.

boterkaaseneieren said:
Pointless thread. Everyone knows to find chainfires thread.
Click to expand...
Click to collapse
Well yes, but still good to know and please don't be offended by his comment. That kind of comment is indeed pointless! We're all here to learn and have fun, keep this kind of comment to yourself please...

Basically, looks like Samsung is pulling the same sort of crap they pulled with the S3 bootloader to prevent status resets under the false pretense of security improvements.

can we downgrade with this

pnr2020 said:
can we downgrade with this
Click to expand...
Click to collapse
No you can't
Once you flash it you're stuck on this firmware.
I found that out the hard way

donalgodon said:
Basically, looks like Samsung is pulling the same sort of crap they pulled with the S3 bootloader to prevent status resets under the false pretense of security improvements.
Click to expand...
Click to collapse
Yeah that's what I thought too.
Hopefully we can fix it in time

Obagleyfreer said:
No you can't
Once you flash it you're stuck on this firmware.
I found that out the hard way
Click to expand...
Click to collapse
oh no my battery drained 30% over night phone laggy so i will not be able to put custom rom on phone anymore will we ever be able to downgrade or are we stuck

pnr2020 said:
oh no my battery drained 30% over night phone laggy so i will not be able to put custom rom on phone anymore will we ever be able to downgrade or are we stuck
Click to expand...
Click to collapse
I'm really not sure.
Hopefully there will be a fix I don't know what I would do with a phone I cant run CM on, I'm so p**ssed off right now at this.
Does anyone know if we flash an older firmware in Odin with a .pit file would that fix things?

give me instructions on how to flash firmware with pit file and i will try i got insurance on my phone so dont care if it goes wrong i just need to downgrade

pnr2020 said:
give me instructions on how to flash firmware with pit file and i will try i got insurance on my phone so dont care if it goes wrong i just need to downgrade
Click to expand...
Click to collapse
Try here and let us know please
http://forum.xda-developers.com/showthread.php?t=2401685 or http://forum.xda-developers.com/showthread.php?t=2354122

DjeMBeY said:
Try here and let us know please
http://forum.xda-developers.com/showthread.php?t=2401685 or http://forum.xda-developers.com/showthread.php?t=2354122
Click to expand...
Click to collapse
will try it now and let you know asap oh my god 2hrs to download files i hate hotfile

I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Im sooooo happy!
Sent from my GT-I9505 whilst taking a s**t

Obagleyfreer said:
I'm really not sure.
Hopefully there will be a fix I don't know what I would do with a phone I cant run CM on, I'm so p**ssed off right now at this.
Does anyone know if we flash an older firmware in Odin with a .pit file would that fix things?
Click to expand...
Click to collapse
Flashing older firmware with PIT didn't work for me.
pnr2020 said:
will try it now and let you know asap oh my god 2hrs to download files i hate hotfile
Click to expand...
Click to collapse
Let me know if it works for you - unfortunately didn't for me.
Obagleyfreer said:
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Click to expand...
Click to collapse
Any chance of a step-by-step guide on how you did this? Especially what you deleted. Also is there any chance it would work if you wanted to go back to an older stock ROM? Reason I want/need stock is because I use the Bluetooth RSAP profile - unless anyone knows if this is included in the CM ROMS...
If you boot into recovery does it have any of the KNOX lines or is the recovery with CM different to stock? If so perhaps it would be possible to do something like (assuming I've understood correctly) : Root Phone -> Install CM -> Un CM the phone with a stock ROM?

Obagleyfreer said:
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Im sooooo happy!
Sent from my GT-I9505 whilst taking a s**t
Click to expand...
Click to collapse
please put up a step by step guide to what you did

pnr2020 said:
give me instructions on how to flash firmware with pit file and i will try i got insurance on my phone so dont care if it goes wrong i just need to downgrade
Click to expand...
Click to collapse
pnr2020 said:
will try it now and let you know asap oh my god 2hrs to download files i hate hotfile
Click to expand...
Click to collapse
I've prepared special ZIP, it should (in theory) downgrade bootloaders
NOT TESTED YET!!!! IT CAN BRICK YOUR PHONE!!
Instructions:
1. Download and copy ZIP to SD/ExtSD card
2. Check if you have BusyBox in /sbin, if not, copy and paste it from /xbin
3. Reboot into Custom Recovery (CWM/TWRP etc)
4. Install ZIP
5. Reboot
Please report how it goes

@DjeMBeY
thanks for bootloader and i added here that same bootloader but for Odin cread as tar file
Zippyshare ---> http://www28.zippyshare.com/v/62712373/file.html

no work
DjeMBeY said:
I've prepared special ZIP, it should (in theory) downgrade bootloaders
NOT TESTED YET!!!! IT CAN BRICK YOUR PHONE!!
Instructions:
1. Download and copy ZIP to SD/ExtSD card
2. Check if you have BusyBox in /sbin, if not, copy and paste it from /xbin
3. Reboot into Custom Recovery (CWM/TWRP etc)
4. Install ZIP
5. Reboot
Please report how it goes
Click to expand...
Click to collapse
Im tested,and not working for me. Im use kt-sgs4 kernel with mh8 rom, with root, busybox and the system is ok...but the bootloader is nt cool, i cant intall any custom rom. No voice, and cant call. Odin .tar file no working nand flash fail...
I think install with odin mh1 rom, and install philztouch recovery and intall bootloader recovery...its fine?Thanx

Obagleyfreer said:
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Im sooooo happy!
Sent from my GT-I9505 whilst taking a s**t
Click to expand...
Click to collapse
That info is going to come in handy to some users who bounce back and forth from Stock to CM.
Thankfully, I had not been tempted to do so and still have the old bootloader. Never going back to stock myself.

donalgodon said:
That info is going to come in handy to some users who bounce back and forth from Stock to CM.
Thankfully, I had not been tempted to do so and still have the old bootloader. Never going back to stock myself.
Click to expand...
Click to collapse
Hopefully it helps at least a couple of people.
The problem comes when you need to send your phone back to Samsung for warranty purposes.
Even if you have old firmware, reset flash counter etc. I can bet my bottom dollar when it returns from Samsung they would have flashed the new firmware and new bootloader to your device. They are great like that!!

[Q] official KitKat ota error

I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??

kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.

scott_doyland said:
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.
Click to expand...
Click to collapse
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.

kieranc88 said:
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.
Click to expand...
Click to collapse
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').

scott_doyland said:
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').
Click to expand...
Click to collapse
Yeah,send it,I'll try copying it,unrooting and then trying the update

kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
And will it matter what version of the stick recovery I'm using( if there are different versions)

kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx

tee_pot said:
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx
Click to expand...
Click to collapse
OK,well at the moment I'm trying out cm11 unofficial builds,I'll see how they go, I'll try the full unroot option when I restore my cwm backup and reflash stock recovery and see if that works ,as I only tried the temporary unroot option in supersu(which is probably leaving some root files behind so it can reinstall su ) if that don't work I'll flash back to stock and try again.

kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I will send file tomorrow when I'm at my PC.

kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I have attached the file /system/etc/install-recovery.sh file to this post (had to gzip it as couldnt upload when it was just called .sh)
Im not sure what the original persmissions of the file should be on your phone, but if you make it read/write/executable by everyone then should be OK I guess.
As I mentioned it'd be good if you unrooted and did a backup and extracted the file to see the contents (before copying over the file). That would first tell you for sure if the file does revert back to original or if it stays as a 'superSU' file when you unroot.
If its reverted back to original then my theory is wrong anyway so no need to copy over the file.
Re the stock recovery type/version being different from what is expected - I dont know if that makes a difference to the OTA working or not. Its an interesting question though so I may do some googling and find out.

I also have a UK retail stock recovery.img (taken with CWM) (my phone is 16GB from phones4u). So if you want that you can have it. Should rule out the recovery type as a problem.
FYI the install-recovery.sh original file actually flashes a new stock recovery when an OTA is performed. At least if you look in the comments of the file I attached above thats what it says.

Android L OTA update on a rooted device?

Hi, i have a Nexus 5 (as you may have guessed) and was sent the L OTA update last night. After downloadong, i thought I'd check online to see if there was any issues with the update and the L OTA update. I only found one blog/post anywhere that answered my question and it said that it would fail, so I didn't install it.
I have just used the 'full unroot' in SuperSU, and it appears to have worked (root checker says 'Sorry, this device does not have proper root access') but I dont know if this is enough to return my device to stock in a big enough degree to allow the OTA update to work (I have no custom ROM or Recovery, just a stock image which i rooted) So I'd basically like some advice And hopefully solve my problem without much issue...

Should be OK. Root itself doesn't cause the fail. Just modified system files. Root gives new system files, not modified existing ones.

rootSU said:
Should be OK. Root itself doesn't cause the fail. Just modified system files. Root gives new system files, not modified existing ones.
Click to expand...
Click to collapse
So if i had installed a custom ROM/ recovery, would that mess with the OTA update?
If so, then that is a relief, as I thought I would have to flash a stock image and relock the bootloader

SamuelGTeague said:
So if i had installed a custom ROM/ recovery, would that mess with the OTA update?
If so, then that is a relief, as I thought I would have to flash a stock image and relock the bootloader
Click to expand...
Click to collapse
Custom ROM or Recovery cannot accept OTA. if any existing apk or file is missing or different, you also cannot accept an OTA as the OTA checks the "fingerprint" of those files. Adding new files aren't an issue as the OTA doesn't know about them so cannot check the fingerprint.

rootSU said:
Custom ROM or Recovery cannot accept OTA. if any existing apk or file is missing or different, you also cannot accept an OTA as the OTA checks the "fingerprint" of those files. Adding new files aren't an issue as the OTA doesn't know about them so cannot check the fingerprint.
Click to expand...
Click to collapse
So as I understand it, with my current set up, the OTA should run and complete. (Sorry if it sounds stupid and repetative, i just cant afford to brick my phone)

SamuelGTeague said:
So as I understand it, with my current set up, the OTA should run and complete. (Sorry if it sounds stupid and repetative, i just cant afford to brick my phone)
Click to expand...
Click to collapse
It wont brick for modified system files. It will just fail verification. if it's going to brick, it wont be for this reason.

rootSU said:
It wont brick for modified system files. It will just fail verification. if it's going to brick, it wont be for this reason.
Click to expand...
Click to collapse
Thanks for all your help, its all installed and is running perfectly!

Need a TWRP backup from an FRD-L04 or a full, TWRP flashable ROM for the same phone..

Tried everything...ERecovery gives me the "getting package failed" (and that was with the stock recovery installed), trying to install a firmware through the HOLD VOLUME+ AND VOLUME- while booting gives me "Software install failed: The Update package does not exist"...I'm running TWRP currently, and no ROM at all is installed...Ideas?

I have a copy of stock ROM TWRP backup. I'll see if I can upload it when I get off today. I think it is update B131 on Stock EMUI 4.1.

Ascertion said:
I have a copy of stock ROM TWRP backup. I'll see if I can upload it when I get off today. I think it is update B131 on Stock EMUI 4.1.
Click to expand...
Click to collapse
If it gets my phone running, that would be perfect.

VaultBoy! said:
If it gets my phone running, that would be perfect.
Click to expand...
Click to collapse
Try pushing this to your device. Should restore just system. Let me know if it works for you. You'll need to unzip it after you download it.
https://drive.google.com/file/d/0BwK7J4olvUi8bWloU1lKUGtoZW8/view?usp=drivesdk

Ascertion said:
Try pushing this to your device. Should restore just system. Let me know if it works for you. You'll need to unzip it after you download it.
https://drive.google.com/file/d/0BwK7J4olvUi8bWloU1lKUGtoZW8/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry for the noob question, but should I throw this in the TWRP backups folder, push it using ADB or flash it using TWRP?

VaultBoy! said:
Sorry for the noob question, but should I throw this in the TWRP backups folder, push it using ADB or flash it using TWRP?
Click to expand...
Click to collapse
Try to push it to your TWRP file path. It's different for each person, but looks like it's /sdcard/TWRP/Backups/*serial number here*/

Ascertion said:
Try to push it to your TWRP file path. It's different for each person, but looks like it's /sdcard/TWRP/Backups/*serial number here*/
Click to expand...
Click to collapse
Now I'm getting an error telling me no chosen partition to restore, but there are no choices for partitions. I might have an idea, though.

VaultBoy! said:
Now I'm getting an error telling me no chosen partition to restore, but there are no choices for partitions. I might have an idea, though.
Click to expand...
Click to collapse
No luck.
I have a ROM installed (RevolutionRemix), but I want to go back to stock, with no seemingly possible ways to do so. Any ideas?

http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039
Find an older ROM and try this method as your last... This one definitely works, but you need to do OTA from beginning.

jerryhou85 said:
http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039
Find an older ROM and try this method as your last... This one definitely works, but you need to do OTA from beginning.
Click to expand...
Click to collapse
YOU ARE A LIFESAVER.
After messing with this thing all day, trying everything, this worked.

VaultBoy! said:
YOU ARE A LIFESAVER.
After messing with this thing all day, trying everything, this worked.
Click to expand...
Click to collapse
Glad to help. Better keep a lateset ROM zip you can find at hand, you never know what time you will need it.

[H918][STOCK] 10i KDZ + IMGs

10i for T-Mobile V20 H918 is out.
It's still anti-rollback v00. :good:
Android Security Patch: 2016-12-01 (dirtycow/recowvery patched)
Download Link
UPPERCUT should work if using LGUP/KDZ.
If you flash this KDZ there is no current root method for 10i... so no TWRP etc (at this very moment anyway).
Everyone who can only boot to download mode.. this should save you.
those w/TWRP already can use the images (or wait for someone to make a flashable "rom" zip.
H91810-system.img.zip is just the system.img compressed, not a flashable zip.
if flashing the stock system.img/boot.img be careful not to lose TWRP..
delete the "recovery-from-boot.p" in system while still in TWRP if you want to be extra safe.
I don't have a V20 and won't be supporting this thread. Just providing files.

Thanks for this. Wonder what the changes from v10d are (other the exploit patch)

If and when someone creates a flashable zip, can we flash SuperSU after we flash the ROM to still have root?

Great.. My replacement is coming today which means it'll probably self update on first boot before I can do anything about it..

I love you daddi

Is this also OTA? I see nothing

kyledowling said:
If and when someone creates a flashable zip, can we flash SuperSU after we flash the ROM to still have root?
Click to expand...
Click to collapse
yes, that's how it works. tho.. idk if it's user-error or what... sometimes people flash supersu and it doesn't patch the boot.img and when they boot into android they lose twrp. hasn't happened to me but ¯\_(ツ)_/¯ . so that's why I also suggested removing the recovery-from-boot.p as an option.
people could also just dd the images manually if they don't want to wait for a zip... but I guess those comfortable with dd already know that.
Swizzle82 said:
Great.. My replacement is coming today which means it'll probably self update on first boot before I can do anything about it..
Click to expand...
Click to collapse
lol just don't put a sim in or connect it to wifi before you use recowvery.

autoprime said:
yes, that's how it works. tho.. idk if it's user-error or what... sometimes people flash supersu and it doesn't patch the boot.img and when they boot into android they lose twrp. hasn't happened to me but ¯\_(ツ)_/¯ . so that's why I also suggested removing the recovery-from-boot.p as an option.
people could also just dd the images manually if they don't want to wait for a zip... but I guess those comfortable with dd already know that.
lol just don't put a sim in or connect it to wifi before you use recowvery.
Click to expand...
Click to collapse
Great idea.. Sometimes you're smart, lol

Swizzle82 said:
Great idea.. Sometimes you're smart, lol
Click to expand...
Click to collapse
altho now that i think about it.. they may force you on the setup screen. but theres no way it'll download/install in the time it takes to get through setup. so just disable internet as soon as you're setup. :good:

autoprime said:
altho now that i think about it.. they may force you on the setup screen. but theres no way it'll download/install in the time it takes to get through setup. so just disable internet as soon as you're setup. :good:
Click to expand...
Click to collapse
What I usually do is make a twrp back up from my old phone and restore it on the new phone after making a fake backup and moving the old one in the new folder the fake backup created. Theoretically this should restore my google account without ever having to initially setup my account when I turn on the new phone. Right? Or do you think it'll cause authentication issues?

Swizzle82 said:
Great.. My replacement is coming today which means it'll probably self update on first boot before I can do anything about it..
Click to expand...
Click to collapse
As long as it isn't preloaded you should be able to get around it...
Common sense isn't all that common

ZDeuce2 said:
As long as it isn't preloaded you should be able to get around it...
Common sense isn't all that common
Click to expand...
Click to collapse
I'm sure I'll get it figured out.

Hopefully @Eliminater74 will make part 1 & 2 ROM for H918 users.

mingkee said:
Hopefully @Eliminater74 will make part 1 & 2 ROM for H918 users.
Click to expand...
Click to collapse
Is he coming to the v20. Plz say yes.

System.img.zip, do I just rename it to system.img? Cause I extracted from zip file and system.img did not flash. But when I renamed it, it flashed but wouldn't boot.

kcsevo said:
System.img.zip, do I just rename it to system.img? Cause I extracted from zip file and system.img did not flash. But when I renamed it, it flashed but wouldn't boot.
Click to expand...
Click to collapse
If you really want this, just use the LG Bridge and update it through that. It's much easier than flashing manually and accomplishes the same thing.

kibmikey1 said:
If you really want this, just use the LG Bridge and update it through that. It's much easier than flashing manually and accomplishes the same thing.
Click to expand...
Click to collapse
Oh sweet! But for the file itself do I need to extracted or rename the file? I flashed the system.img and boot in twrp but it hung in LG logo. And I'm also trying to retain root.

kcsevo said:
Oh sweet! But for the file itself do I need to extracted or rename the file? I flashed the system.img and boot in twrp but it hung in LG logo
Click to expand...
Click to collapse
You don't need the file at all. Just download the LG Bridge from the LG website, install the LG Universal mobile drivers, plug in your phone and use the software update option. It does it all by itself, and will restart your phone on it's own.

kibmikey1 said:
You don't need the file at all. Just download the LG Bridge from the LG website, install the LG Universal mobile drivers, plug in your phone and use the software update option. It does it all by itself, and will restart your phone on it's own.
Click to expand...
Click to collapse
Do i need to be back factory stock including recovery to use this option? And I'm guessing this way would make me lose root? Thank you for your responses.

kcsevo said:
Do i need to be back factory stock including recovery to use this option? And I'm guessing this way would make me lose root? Thank you for your responses.
Click to expand...
Click to collapse
You only need to plug in your phone and let it work. Since this is a stock image, you will lose root. Also, the as described in the original post on page 1, the December security patch also patches the dirty cow exploit used to achieve root, so once you flash this, you'll be stock unrooted until a new method comes along.