Related
New to me tablet and I'm new to rooting/etc.
Factory tablet on 4.1.1, build 10.4.2.20-20121228
I downloaded and ran the Asus unlock utility, then ran motochopper to root. I then loaded TWRP 2.2.2.0 (I realized the mistake later). Made stock backup using twrp ok. Wiped cache/dalvik/etc and tried to recover to CM.10.0.0. Boots to cyanogenmod logo and just sits and spins. I can reboot back into recovery and restore from backup ok.
I realize now that I've loaded an early version of twrp, would that affect the cm bootup? If so, how do I upgrade twrp? Or should I try CM10.1 exp using twrp 2.2.2.0?
kbud123 said:
New to me tablet and I'm new to rooting/etc.
Factory tablet on 4.1.1, build 10.4.2.20-20121228
I downloaded and ran the Asus unlock utility, then ran motochopper to root. I then loaded TWRP 2.2.2.0 (I realized the mistake later). Made stock backup using twrp ok. Wiped cache/dalvik/etc and tried to recover to CM.10.0.0. Boots to cyanogenmod logo and just sits and spins. I can reboot back into recovery and restore from backup ok.
I realize now that I've loaded an early version of twrp, would that affect the cm bootup? If so, how do I upgrade twrp? Or should I try CM10.1 exp using twrp 2.2.2.0?
Click to expand...
Click to collapse
I can see you are on the 4.1 BL. I would suggest upgrading to the 4.2 bootloader and the using the most recent versions of TWRP and CM. You would do that by flashing the stock 4.2 Asus firmware, then the latest TWRP from their website with -42 and then the latest cyanogen mod ROM which is compatible with that bootloader.
cmendonc2 said:
I can see you are on the 4.1 BL. I would suggest upgrading to the 4.2 bootloader and the using the most recent versions of TWRP and CM. You would do that by flashing the stock 4.2 Asus firmware, then the latest TWRP from their website with -42 and then the latest cyanogen mod ROM which is compatible with that bootloader.
Click to expand...
Click to collapse
First off, thank you for the assistance. Here are the steps I believe I should take. Please correct me if I'm wrong.
1. Download and install latest 4.2 bootloader from Asus= US_epad-10.6.1.27.5
2. Would I need to download and install the unlocker from Asus? = Unlock_v8 for 4.2JB
3. Download and install TWRP for 4.2= TWRP 2.6.3.0-tf300t-4.2 blob
4. Then I should be able to run any of the CM 10.0.0 and up on the 4.2 bootloader, right?
kbud123 said:
First off, thank you for the assistance. Here are the steps I believe I should take. Please correct me if I'm wrong.
1. Download and install latest 4.2 bootloader from Asus= US_epad-10.6.1.27.5
2. Would I need to download and install the unlocker from Asus? = Unlock_v8 for 4.2JB
3. Download and install TWRP for 4.2= TWRP 2.6.3.0-tf300t-4.2 blob
4. Then I should be able to run any of the CM 10.0.0 and up on the 4.2 bootloader, right?
Click to expand...
Click to collapse
Lots of ppl are having problems with the V8 unlocker. Since you are already on 4.1, you could just unlock now with the V7 tool.
1. Unlock with V7 tool (http://forum.xda-developers.com/showthread.php?t=1949758)
2. Flash Latest Asus Stock (http://forum.xda-developers.com/showthread.php?t=1949758)
3. Download and install TWRP for 4.2= TWRP 2.6.3.0-tf300t-4.2 blob (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.6.3.0-tf300t-4.2.blob)
4. Flash Latest CM (http://forum.xda-developers.com/showthread.php?t=2413878)
Personally, I would also make NvFlash Backups so you can restore your tablet just in case anything bad happens. Link is in my sig
cmendonc2 said:
Lots of ppl are having problems with the V8 unlocker. Since you are already on 4.1, you could just unlock now with the V7 tool.
1. Unlock with V7 tool (http://forum.xda-developers.com/showthread.php?t=1949758) Why would I use this now? Shouldn't I already be unlocked?
2. Flash Latest Asus Stock (http://forum.xda-developers.com/showthread.php?t=1949758)Will this put a locked or unlocked version on the tablet?
3. Download and install TWRP for 4.2= TWRP 2.6.3.0-tf300t-4.2 blob (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.6.3.0-tf300t-4.2.blob)
4. Flash Latest CM (http://forum.xda-developers.com/showthread.php?t=2413878)
Personally, I would also make NvFlash Backups so you can restore your tablet just in case anything bad happens. Link is in my sig From what I'm reading, I can only do this after updating to 10.6.?.? So I would have to update to the latest Asus stock, then run this procedure.
Thanks again, and I appreciate your patience.
Click to expand...
Click to collapse
Ok, been reading until my eyes are bleeding.
From what I've read, Motochopper doesn't work for 10.6.1.27.x versions, so I would have to load 10.6.1.15.3. I should be able to download it and unzip it the first time on my pc. Then transfer it to the root directory of the tablet and run TWRP to install the .zip file. This would overwrite everything and bring it up to 4.2. I would then run the unlocker_v8 and install twrp for 4.2 using adb. If all that works, I should be rooted and unlocked and allowed to install CM 10 and above.
Please, anyone, check me on this. And thanks for the help.
kbud123 said:
Ok, been reading until my eyes are bleeding.
From what I've read, Motochopper doesn't work for 10.6.1.27.x versions, so I would have to load 10.6.1.15.3. I should be able to download it and unzip it the first time on my pc. Then transfer it to the root directory of the tablet and run TWRP to install the .zip file. This would overwrite everything and bring it up to 4.2. I would then run the unlocker_v8 and install twrp for 4.2 using adb. If all that works, I should be rooted and unlocked and allowed to install CM 10 and above.
Please, anyone, check me on this. And thanks for the help.
Click to expand...
Click to collapse
Oh sorry, I thought you meant that it had failed to unlock and flash.
Flashing a stock ROM will not relock your bootloader. Asus doesn't want people relocking their bootloader .
I'm not sure why you are using motochopper if you are going to install a custom ROM anyways. Almost all custom ROMs have the SU binaries in them.
Once you have unlocked your tablet, you will never need to run another unlocker, so dont worry about v8. The NvFlash backups need you to be on the 10.6.x.x bootloader, so you would flash the stock ROM then do the nvflash procedure.
cmendonc2 said:
Oh sorry, I thought you meant that it had failed to unlock and flash.
Flashing a stock ROM will not relock your bootloader. Asus doesn't want people relocking their bootloader .
I'm not sure why you are using motochopper if you are going to install a custom ROM anyways. Almost all custom ROMs have the SU binaries in them.
Once you have unlocked your tablet, you will never need to run another unlocker, so dont worry about v8. The NvFlash backups need you to be on the 10.6.x.x bootloader, so you would flash the stock ROM then do the nvflash procedure.
Click to expand...
Click to collapse
Just so I'm clear, I should be able to flash the stock rom w/ the TWRP I have now, using the install command for the zip file, right?
kbud123 said:
Just so I'm clear, I should be able to flash the stock rom w/ the TWRP I have now, using the install command for the zip file, right?
Click to expand...
Click to collapse
I'm not sure if you can flash the stock from the TWRP, to be safe I'd fastboot it from a computer. Once you flash the stock, it will upgrade the bootloader and erase TWRP. You would use the install command.
Success so far! I got it updated to 4.2.1 /10.6.1.27.5 using http://forum.xda-developers.com/showpost.php?p=35294881&postcount=1.
I have version 4.1.1.... I unlocked the bootloader without updating through the Ota. . I rooted and installed twrp.
I want to run lollipop but it says I need 4.2.1 bootloader
How do I upgrade it? Maybe without a pc?
Thank you
Cerv3r said:
I have version 4.1.1.... I unlocked the bootloader without updating through the Ota. . I rooted and installed twrp.
I want to run lollipop but it says I need 4.2.1 bootloader
How do I upgrade it? Maybe without a pc?
Thank you
Click to expand...
Click to collapse
If you have custom recovery on your tablet (which you say you do) download the official asus 4.2.1 update firmware. It is in the form of a zip. Inside that zip is another zip, put the latter one mentioned on your sd card and flash it in recovery. Let it boot up. Done. You now have latest bootloader.
I'm going to threadjack here as I have a similar question: How can I confirm the current bootloader version?
When I boot holding pwr+voldwn, in the top left it says:
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.6.1.27.5-20130902" A03I realize this is the most recent firmware available via the Asus site.
For what its worth:
TWRP v2.6.3.2 is installed
I just flashed the most recently nightly (as of this writing) of CM-12; I must be on 4.2.
I vaguely remember going through a 'zip within a zip' flashing process some time ago. Still, knowing where to look to confirm version info is helpful.
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?
Hello everybody, I hope to find help here.
My phone is the HTC One A9, Europe Version ("hiaeuhl"). Recovery is TWRP 3.0.2-0.
The background story is that I already managed to install Cyanogenmod after downgrading the original ROM to Version 1.10 and unlocked the bootloader with the HTC Unlock tool. I also managed to decrypt the device.
I'd like to update my system regularly, but unfortunately the last running version is the cm-13.0-20160904-NIGHTLY-hiaeuhl.zip from September 4th.
If I try to install the latest versions of Cyanogenmod (for example from September 9th) I always get the error
hiae.veryfy.trustzone() failed to read current TZ version: -2
Updater process ended with ERROR 7
I already tried to remove the lines that check this in the file updater_script inside the ROM's zip, then I could install the update, but afterwards I was stuck in a boot loop.
The error has nothing to do with the encryption, it apears with and without device encryption, and it has nothing to do which system (original or custom) is installed before flashing. It is also indifferent if I try the update via the system's update function or directly in TWRP. It's the fact that the Cyanogenmod version from September 4th is the last working for me. I definetly chose the right one for hiaeuhl, but it seems the developers have added a feature that makey my device incompatible to this ROM.
If there is anything I can do to update my system again, please let me know.
Have the same issue.
We need to update it, but I don't know how
jira.cyanogenmod.org/browse/NIGHTLIES-3351
Here is how I could solve the issue:
- flashing the latest stock firmware (and let it possibly completely update)
- install TWRP via fastboot
- from TWRP a factory reset
- install new version of the Cyanogenmod from TWRP
It worked for me, now I can use my beloved custom Rom
The Same Problem
I have exactly the same Problem, last working CM-Update was the 3rd September
Did you try my solution? With the older CM Rom versions for the HTC A9 you had to downgrade the stock rom, otherwise the CM wouldn't have started after the installation. Now it seems that the stock rom has to be the latest one (for me the 1.56) that you are able to flash the latest CM versions.
I do not have the latest stock Rom, my os is 1.27.161.6, seems actually cm needs 1.57, i am unlocked and s-off
You should probably find the right version for your phone here:
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
You should take the one with the right cid for your phone (which you can find with "fastboot getvar all" in the fastboot mode)
Thanks, i will try it and report
The last build i found for my version is 1.27. this is what i have
Hmmm... then I guess you have to wait until the new version appears in the forum. Seems that you have a device with vodafone branding. Since you already set S-off you also have the possibility to change your cid to one of the existing newer firmwares.
Is there a solution without going back to stock?
I'm not an expert, but I don't think so. It seems that the version number of the stock rom is stored somewhere even after changing the system to Cyanogenmod, and this version has to be the latest one. So unfortunately, as far as I know, you'll have to do the flashing procedure again...
thanks Silberhase, now i am on CM 13 again. Thats what i did: wrote Supdercid, searched a ruu-version for my build, found a 1.56.401.70 version, flashed this, then flashed twrp 3.0.2.0 again, factory reset - without factory reset i was not able to install cm, format data, recovery, latest cm update, flash gapps, restore my other data with titanium, done....
I'm glad to hear it worked for you!
Yes, but next Problem or better i actually do not know what problems will raise. After updating today successfully to last cm build phone is encrypted... TWRP requires password for decryption. Problem all over forums. Today i habe no fun to Format data again and restore all.
That's also what I experienced. Other users reported that the current TWRP version 3.0.2.0 can't handle the encryption of the HTC One A9. And every update will encrypt the device again. As a workaround you can do this:
- copy the downloaded update from /sdcard/cmupdater to the external memory card
- boot to the recovery (when asked for password push the cancel button) and install both the update and the gapps again (without wiping anything) from the memory card.
Its a pity, all worked perfectly. Installed last cm.. Which encrypted phone. Restored my backup. All Working. Updated apps, want backup again.... .... Error opening /system/addon.d (not a directory)..error in generating tarlist......Create tarfork()
Process Ended with error 255
I'm trying to help as much as I can even though I have no experience with all this. I never did a backup
Maybe you find the answer here:
http://forum.xda-developers.com/nexus-6/help/e-createtarfork-process-error255-t3302462
Maybe it helps to mount "system" in TWRP and then delete /system/addon.d. But it seems that this step has to be repeated before every backup.
Any news to this theme? Is Twrp able to handle A9 again in new Version?
The recent version 3.0.2.0 of TWRP is available for the A9 but can't handle it's encryption. It works anyway if you are willing to use some workarounds.
I will try to keep it short and concise;
Had android 5.0.1 (if I recall correctly), unlocked it, installed twrp and rooted it.
Then used the local update option to get to marshmallo. Then tried to root again using supersu and it wouldn't boot. Tried restoring nandroid backup of 5.0.1 backup but it wont boot either.
I have searched for many hours and tried many different roms etc. I can only get to the boot animation and it just stays there.
I can get into TWRP and bootloader with no issue but have no idea if I can use the dload option if I can not boot into the OS.
Can someone please help me get this back either to the stock rom or a custom marshmallo rom installed?
I will be honest that I don't fully understand what it means when there is a prerequisite of "You must already be on B201 or higher to flash this" such as with the Simply International I have tried to flash. And am not sure what the EMUI version is or how it affects what can be installed.
Thanks for any info.
Hello
1) First of all, go into TWRP recovery, and do a full wipe. Then reboot and wait.
2) If unsucessfull, try out the downgrade file for 702L : http://download-c.huawei.com/download/downloadCenter?downloadId=81363&version=323452&siteCode=tw . It does install with official dload method
3) If it's not enough, you'll have to use ADB to fix your device I guess:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378?
its use on X2:
http://forum.xda-developers.com/showthread.php?p=62829551#post62829551
(and following post)
pick up the file from your last installed (or nandroid restored) ROM to use with huawei update extractor.
==
but try out 1 &2, and come back here before using ADB, to have more precise instructions