Database Info

Thoughts on Downgrading 183.46.15 to 183.46.10

So I've tinkered a lot with this device, as well as the RAZR M. You may not recall my username, but I am the one that found out that the LG G3s Clockworkmod Recovery works on our locked devices. That being said, I've made several other side attempts at unlocking the bootloader on these devices, all of course to no avail. There are a few odd things I've found in an attempt to downgrade to 183.46.10. First of all, you CAN downgrade to 183.46.10 easily from 183.46.15 obviously if you are unlocked OR if you replace the gpt.bin, tz.mbn, and boot.img from 183.46.15 and run the flashing script. I've also noticed that devices that are on 182.46.15 also are running with an updated "sbl3.mbn" . So if you have RSD Flashed to 183.46.15 (or are just running that firmware), the only three updated files you're dealing with are the kernel (boot.img), trust zone (tz.mbn), and partition graph (gpt.bin). I've tried to flash a downgraded boot.img (the May 2nd) kernel via this "FlashBackToKK" script from droidrzr.com, and the kernel flashed successfully from the CWM recovery, but of course when I booted the device, I got a fastboot error boot failed: Downgraded security version. So the kernel successfully flashed, but some other part of the boot chain, presumably the trust zone, knows that the kernel image has been downgraded, so WHAT IF all three updated partitions are flashed via that CWM Recovery script? I need everyone who has experience in this kind of thing to please respond..

Honestly however way you try to work around I really don't believe will work. I really think some reverse engineering and code are needed for this to work. There way of bootloader locking on the razrs helped pathed the way of success in them keeping the Galaxy S5 and Other Phones BL Locked! Once one of them are unlocked I believe the s5 phones will be just as easy or similar. Maybe some hex editing and some file checksums need to be patch. Just my thought. I'll leave it to the experts.

Questions from a HTC Newbie regarding Root / Update / Recovery

Hi everyone,
I guess I need a bit help, I switched from Samsung devices to HTC and the rooting / update procedure etc seems a lot different than what i was used to.
So I have tested a bit with ADB and fastboot and managed to unlock the bootloader and root the device and install the TWRP.
But now my problem starts:
How can i update to a new android stock-version without losing my data? OTA is not possible due to TWRP, right?
Flashing Roms with TWRP is not possible with S-On, right?
So what are my next steps?
Buyng sunshine and then flashing via TWRP? Or is there another option?
I dont want the CM13, i just want to be able to update the HTC Stock versions with Root and a custom recovery.
Any help would be greatly appreciated
Thanks
André

How do I safely root and unlock bootloader on Marshmallow?

My device is European L04, currently running North Africa release (the earliest Marshmallow build uploaded) - L04_2016_0316_0900 (B820)
I'd like to unlock the bootloader and root my Honor 6. I've never done it (on this particular device), because I've read enough here to know it's slightly more risky than on other devices, especially when you plan to update the stock rom soon, so I preferred to wait until I have the last important update the device is likely to receive - Android 6.0.
What I want to know (some of the answers are in the topics which I listed below):
MultiTool - I've seen reports of bricks when using MultiTool with EMUI4/Marshmallow - why does it happen? My understanding is that MultiTool is a bundle of adb/fastboot and some recovery images for older Android versions, so my theory is that instead of using MultiTool, I should simply get the proper recovery for Marshmallow and flash it manually with fastboot, right?
unlocking bootloader, rooting, flashing recovery - I think I understand the process; in a nutshell: 'fastboot oem unlock X', 'fastboot flash recovery imagename.img', then flash the proper SU.zip in recovery. Where do I find the code, the Marshmallow recovery image, the SU.zip file?
will recovery backup in TWRP work without any problems?
what is the procedure to go back to stock completely after rooting? Unroot, (then wipe if it's needed?) so I am able to safely flash stock firmware again (since, from what I know, flashing stock on a rooted phone makes itself brick permanently, right? or is it just a soft-brick and it can be fixed?)
is there anything else I should know before proceeding?
What I found so far:
http://forum.xda-developers.com/showpost.php?p=66615082&postcount=502 - two recovery images, TWRP and another one (stock?) for the Marshmallow release
http://forum.xda-developers.com/honor-6/general/honor6-multi-tool-t2963060/page50 some rooting instructions for the L02 beta, see posts 494 and 498; no idea whether this is applicable to final Marshmallow or L04 at all
http://forum.xda-developers.com/honor-6/general/huawei-honor-6-plus-unlock-bootloader-id-t3357259 an app to get the unlock code, seems a bit shady to me though on the first glance
http://forum.xda-developers.com/honor-6/development/honor-6-rooting-method-t2962795 alternate methods for bootloader (through a website or by email), in case the app won't work; also, detailed instructions on unlocking and rooting
Basically, I need to know whether my procedure is more or less right before I proceed. I think the information is quite hard to find and the risks are quite high, so I'd like to make a promise - when I'm done rooting it and I know the correct process, I'm going to make a "Update to Marshmallow, unlock, root" how-to thread for all the people that will need it in the future.

Another two questions...
1. Where do I get proper SuperSU for Marshmallow? I get a boot loop (yeah, I know I have to wait and I did, but it's a pretty obvious bootloop from watching the logcat content, and nothing new happens...) after flashing http://download.chainfire.eu/supersu-stable (2.65).
2. I have unlocked my bootloader and installed TWRP, so recovery and fastboot are functional. I didn't make a backup before flashing the zip and now I'm in a bootloop. How do I restore working Marshmallow? I assume I can either beg somebody to upload a TWRP backup for my H60-L04, or somehow flash the stock over what I have now. Can I simply use manual update from SD? Can I somehow flash Marshmallow again with fastboot? I'm too scared of bricking my device right now so I guess I'll brace myself for a few days without a phone until somebody helps me :/

I just flashed the Marshmallow release I had before the bootloop (I used Huawei Update Extractor and flashed boot, cust, system and recovery with fastboot; then open up Huawei recovery and factory reset for good measure, I'm not sure it was even needed) and the device is working. I'll restore my stuff, install TWRP, make a backup then try out your ZIP. Thanks
edit: thanks again - your zip works indeed. So after the initial hurdles, now I've got working root and a reasonable way of restoring in case I screw something up along the way.

Before making a new topic with the tutorial I have a few more questions.
First of all, why exactly we weren't supposed to update the rooted devices? I'm not currently interested in OTAs (it's pretty obvious that it needs a functional Huawei recovery, and you need to unroot cause an update can make a mess in a rooted system, making it bootloop for example), but can we flash extracted images with fastboot on rooted devices? Logically, we should be able to... How about sdcard update method?
Can we flash Marshmallow on Kitkat? (fastboot, sdcard, local update methods?) Or do we need to update to Lollipop along the way?
Can I flash stock roms in general (evenbetween different Android versions) by using fastboot with {boot, cust, recovery, system} images only? There's a lot of images that you can extract with Huawei Update Extractor - why there's so many if they're not needed?

VZW Variant - Vendor IMG Error, SIM Card Not Recognized??

What can cause this? My friend got a Pixel with the not-newest firmware and could unlock BL & root, etc, and he is attempting to flash custom ROMs but getting the same result (in the title). Does anyone know why? It is happening reliably on first boot of each ROM flash.

You don't give us much information to troubleshoot with. However, there a good chance you didn't follow the OP of whatever rom you flashed. Go back and follow every step. My guess is you didn't reboot to bootloader AFTER flashing the rom followed by flashing the vendor image in recovery to the newly activated slot.
Could also be any number of other things: outdated fastboot, outdated twrp, wrong flashing order, who knows with this little info.

Can only install official binaries message when flashing TWRP with Odin3 on A750FN U4

Hi, I'm having a lot of trouble trying to install a custom recovery. I had it working a couple months back but wanted to go with official again for dumb reasons and now i want to go back but it won't let me flash TWRP, i can't find a TWRP specifically for this version either. It's Android 10 with March security patch.
I hope someone can help me.
Thanks.

Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.

Didgeridoohan said:
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Click to expand...
Click to collapse
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.

Parthiv Shaji said:
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Click to expand...
Click to collapse
Like I said, I'm not 100% on Samsung shenannigans, but have you checked to verify that you didn't lock the bootloader as a part of flashing the stock firmware?

OEM unlock toggle in Developer's Options

Hi ¡...
1. You have to reinstall via odin the latest version 9 (AP, BL...etc)
2. On reboot do the entire TWPR flashing process for android 9
The current problem is that there is no TWPR for android 10.
Cheers