Ive managed to htc-dev bootloader unlock and root but when it comes to install roms I have question
Do have to have a certain firmware to install some roms?
Am on kernel 3.4 and Hboot 2.15 tmob 3.1453117710rd
I flashed viper rom with no hitch but when i tried any other rom I end up freezing at the logo screen for the rom,ie freezes at carbon loading screen for carbon, even after I re flash both the rom and the boot,img for it
I am currently s-on
My second question is there any way to trouble shoot adb? I keep trying to push files via adb and keep getting adb cannot find such file or directory, I installed ADB according to this http://forum.xda-developers.com/showthread.php?t=879701
I run the cmd prompt from desktop and commands like adb-reboot work fine
But when i attempt to push i get the cant find file error
what recovery are you using? what version of twrp?
twrp 2.3.3
http://techerrata.com/file/twrp2/ville/openrecovery-twrp-2.3.3.0-ville.img
recovery is twrp 2.1.6
Should I update to the new recovery?
foodiegamer said:
recovery is twrp 2.1.6
Should I update to the new recovery?
Click to expand...
Click to collapse
yes, people have a lot of luck with this version of TWRP
Yea flashing to newest trwp did it for me
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 want to root the phone but keep the stock CM 11s and the stock recovery so OTAs continue to work. fastboot boot recovery.img doesn't seem to work any more and the towel root vulnerability is fixed in CM. Suggestions?
thats not the right fastboot command to flash a new recovery, but you dont need a different recovery to root.
The Jack of Clubs said:
thats not the right fastboot command to flash a new recovery, but you dont need a different recovery to root.
Click to expand...
Click to collapse
Can the OPO be rooted from stock recovery?
I've not seen the stock recovery yet, but does it have CWM functions in it?
donalgodon said:
Can the OPO be rooted from stock recovery?
I've not seen the stock recovery yet, but does it have CWM functions in it?
Click to expand...
Click to collapse
no. but thats if you choose the recovery root method. root consists of two parts, a su binary that gives normal users full device write control, and a superuser app that allows android apps to use the su binary. when you use recovery to root, it just flashes these two files to the system partition and you have root. its a failsafe method, but requires you to use a custom recovery that lets you flash whatever you want to the phone. since ota updates use the stock recovery to update, if you replace the stock recovery you cant install ota updates. there are other methods that use fastboot and adb usb debugging exploits to copy the root binary to system, but i havent looked into what works. i planned to do that after i get my oneplus.
i used cf-auto-root on my brothers nexus 5. it keeps stock recovery in place, and uses fastboot to root. ota updates still work after that. however you loose root everytime you update because it wipes and flashes a new system partition. not that big a deal, you just reroot after updates. it would do that whether or not you were to replace recovery. the only way around that is to use a prerooted rom that would include root in the system image. cyanogenmod has their own superuser app thats just not included in this rom so they can get google certification. i imagine they have some way to get it installed easily.
I just did the fastboot boot recovery.img and flashed SuperSU fine...
Chinese 64GB..
Sent from my One using XDA Free mobile app
Hi guys,
I'd like to flash the latest ota on my shield.
having a rooted device with custom recovery i can't so it normally.
Is there another method to flash this OTA without unrooting?
Thanks
gerazzo said:
Hi guys,
I'd like to flash the latest ota on my shield.
having a rooted device with custom recovery i can't so it normally.
Is there another method to flash this OTA without unrooting?
Thanks
Click to expand...
Click to collapse
Just flash the newest OTA in your custom recovery.
It will overwrite your recovery with stock recovery however.
FoxyDrew said:
Just flash the newest OTA in your custom recovery.
It will overwrite your recovery with stock recovery however.
Click to expand...
Click to collapse
already tried.
It asks me if i wanna install an untrusted zip file.
I say yes
and it says unable to verify.
aborted
If you're on a custom recovery + root, then I'm assuming you're no stranger to adb and fastboot commands. You can download the full update (not incremental) from here , unzip, and use the flash-all.sh (or .bat if you're in windows) to flash the full update. You can then flash your custom recovery and superSU after it. You'll probably want to backup your stuff before you do this!
If you're on custom recovery + root because your friend did it for you, go ask your friend! =P
gerazzo said:
already tried.
It asks me if i wanna install an untrusted zip file.
I say yes
and it says unable to verify.
aborted
Click to expand...
Click to collapse
In CWM or TWRP?
Hi and a happy new year,
I have an old HTC ONE S which was running with cm10.1 until they shutdown their servers and the OS starts to missbehave.
After this I tried to switch to LieageOS 13.0 but this will need HBOOT 2.16 and as I read the upgrade of HBOOT requieres S-OFF. I tried to get the S-OFF and SID, I was able to change the SID but without a working android it seems to be impossible to get S-OFF. So I tried to reinstall the old CM 10.1 which was not working, now I installed the actual VENOM rom but all I got is a bootloop the bootloader splashscreen shows up, the phone turns black after some seconds and after this it boots into recovery (TWRP 3.1.0-0).
So I hope you will be able to help me booting an android rom and possibly upgrade HBOOT.
Thanks,
Power
With S-ON you need to manually flash the boot.img of the rom via fastboot. Unzip the rom, copy the boot.img into your fastboot directory and flash it with
Code:
fastboot flash boot boot.img
while the phone is booted to fasboot USB mode.
In addition, you might want to revert to TWRP 2.3.3.0. It's the recommended version for flashing ViperOneS 2.x*.
* I'm not sure whether facepalm can actually be used with ViperOneS 3.x since it's based on the unofficial firmware 4.05.401.1. The exploit might be fixed in that rom. However, I can tell you from personal experiences that it is working with ViperOneS 2.x. Alternatively, you could try rumrunner in combination with CM10 or CM11 (both combinations are known to work, as well).
Hi Flippy498,
thanks for your help.
It's a long time ago that I flashed this device so I didn't remember to flash the boot.img manually.
Now I have the S-OFF and was able to update HBOOT. Later on I will continue with the steps to install LineageOS.
As I can see from your footer you are using LineageOS 14.1 on this device. Are there any bugs or does this rom work without errors?
Best regards,
Alex
The proximity sensor misbehaves a bit if the lock screen is visible. Aside from that I haven't noticed any bugs/issues.
Sent from my HTC One M9 using XDA Labs
ROM cm13 or lineage
It would be interesting that someone can provide a thread where to make the steps to install a ROM cm13 or lineage from the beginning, with everything and recommendations of programs, radio, hboot and everything that is necessary...
Hi,
My phone is rooted and with twrp. After attempting to perform OTA update, it now boots straight to the fastboot screen. I still can get TWRP to work but there is no prompt to decrypt my phone after twrp starts so I basically can't read the phone contents. Much appreciated if anybody here can guide me to fix my phone. Does it mean I will lose all my data?
Thank you!
spicediablo said:
Hi,
My phone is rooted and with twrp. After attempting to perform OTA update, it now boots straight to the fastboot screen. I still can get TWRP to work but there is no prompt to decrypt my phone after twrp starts so I basically can't read the phone contents. Much appreciated if anybody here can guide me to fix my phone. Does it mean I will lose all my data?
Thank you!
Click to expand...
Click to collapse
you can install magisk using adb sideload with the old like Chinese twrp not the latest one anws if u have twrp and root the phone will only boot in fastboot you have to flash the 12.0.4 or older update (android 10) then update to 11 :/ mine have this problem two u cant install having the twrp u can install it later
BassilZ said:
you can install magisk using adb sideload with the old like Chinese twrp not the latest one anws if u have twrp and root the phone will only boot in fastboot you have to flash the 12.0.4 or older update (android 10) then update to 11 :/ mine have this problem two u cant install having the twrp u can install it later
Click to expand...
Click to collapse
u can also install the rom using this recovery https://drive.google.com/file/d/1NBVNr6hJbAI0mOEcRPY9JZ3E7Hqc01Qx/view
Does this PBR work for MIUI 12 Android 11 OTA updates for Xiaomi.eu weeklies?