Related
I am currently running TWRP 2.3.1.0 and would like to update it to the most current version. Is there a specific process that I have to go through in order to update it correctly, or can I just download if from Goomanager and install it without any additional steps?
Thanks
Goomanager should work fine assuming you're rooted
Sent from my Nexus 10 using xda app-developers app
browning said:
Goomanager should work fine assuming you're rooted
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
This is what I did.
I do mine via fastboot, it's pretty easy just run fastboot flash recovery recovery.img and just make sure the TWRP is in your fastboot folder and you replace recovery.img with the latest file name you downloaded. GooManger should be much easier if you don't wanna use fastboot.
Sim-X said:
I do mine via fastboot, it's pretty easy just run fastboot flash recovery recovery.img and just make sure the TWRP is in your fastboot folder and you replace recovery.img with the latest file name you downloaded. GooManger should be much easier if you don't wanna use fastboot.
Click to expand...
Click to collapse
Thanks to all the replies. I was able to update TWRP via Goo without a problem.
2.4.2
mr0roboto said:
Thanks to all the replies. I was able to update TWRP via Goo without a problem.
Click to expand...
Click to collapse
goo wants to give me 2.4.2 wonder if theres any issues with that version
Nope seems good.
Hello everyone,
recently I bought an HTC One X Plus that was AT&T powered. I wanted to get rid of the restrictions they imposed on the phone, like using the FM Radio, and decided to flash a ROM. In TWRP I did first with success. Then I wanted to flash a custom rom and wiped all data, including the zip file that was pushed to the mobile phone. Consecuence: I was left without an OS on the phone and could not install the custom rom. Now my phone is bricked! Luckily I saved CWM recovery on my PC, and I tried fastboot flash recovery recovery.img. It is being pushed somewhere, but I still don't have access to my mobile phone! Who can help me with this, I am desperate! It seems I made an expensive error!
erkui said:
Hello everyone,
recently I bought an HTC One X Plus that was AT&T powered. I wanted to get rid of the restrictions they imposed on the phone, like using the FM Radio, and decided to flash a ROM. In TWRP I did first with success. Then I wanted to flash a custom rom and wiped all data, including the zip file that was pushed to the mobile phone. Consecuence: I was left without an OS on the phone and could not install the custom rom. Now my phone is bricked! Luckily I saved CWM recovery on my PC, and I tried fastboot flash recovery recovery.img. It is being pushed somewhere, but I still don't have access to my mobile phone! Who can help me with this, I am desperate! It seems I made an expensive error!
Click to expand...
Click to collapse
Lol,
First of all , Why would you flash CWM if you already have TWRP installed ?
If you want to flash a custom ROM just use adb while in recovery to push the rom.zip to your sdcard in order to flash it on your phone.
For example if you want to flash cm11.zip , open a command prompt or a terminal if you're using linux ,then change directory to where the zip file is placed.
for example if your cm11.zip is placed on Desktop , after opening cmd use "cd C:\Users\username\Desktop" then type "adb push cm11.zip /sdcard/" (this will push the ROM zip into your sdcard so you can flash it from recovery.
if you need any more help then feel free to ask ! lol
Please press the thanks button if i helped !
backb0ne5p1d0r said:
Lol,
First of all , Why would you flash CWM if you already have TWRP installed ?
If you want to flash a custom ROM just use adb while in recovery to push the rom.zip to your sdcard in order to flash it on your phone.
For example if you want to flash cm11.zip , open a command prompt or a terminal if you're using linux ,then change directory to where the zip file is placed.
for example if your cm11.zip is placed on Desktop , after opening cmd use "cd C:\Users\username\Desktop" then type "adb push cm11.zip /sdcard/" (this will push the ROM zip into your sdcard so you can flash it from recovery.
if you need any more help then feel free to ask ! lol
Please press the thanks button if i helped !
Click to expand...
Click to collapse
Thanks pal,
problem is only that the ADB gives the message "no device detected", don't forget that the OS on the mobile phone was wiped! But I found the solution, using a tool called WinDroid for HTC One X Plus. With this tool, I flashed CWM to the phone and rebooted in recovery mode. From there, I could mount the SD-card which gave me the option to copy the .zip file to /SDCARD/ using ADB. Also with the tool CWM, I then installed the file, and it worked. I'm on the air now,passed a night without sleep but I learned a lot!! Problem solved!.
Even if you don't have an OS installed ADB should work while in recovery.
Well I'm glad you could solve your problems. I knew about the toolkit but trying the harder way is always better for gaining more knowledge.
Sent from my One X+ using XDA Premium 4 mobile app
Stable ROM for HTC One XL Telus Version
I have HTC One XL / Tellus with 64 GB Internal Storage. I wanted to update it to Jelly Bean through Custom roms like ViperXL + / Elegance.
The phone has HBOOT 1.32.000
Whenever I flash Viper XL+ Tellus on the phone the phone Boots to the Home Screen and then if I unlock then the phone does nothing and just shows the HTC logo on Screen.
I had verified the ROM zip file and had checked its MD5
I got same results with Lower version of Viper XL 1.2.0 / Elegancia 6.2.0 ..
I have flashed ROM 2 to 3 Times with same result.
Is HBOOT1.32.00 not compatible to these ROMs?
What am I doing wrong? Has anyone faced the same problem.
Thanks,
SK
Sujitkundar999 said:
I have HTC One XL / Tellus with 64 GB Internal Storage. I wanted to update it to Jelly Bean through Custom roms like ViperXL + / Elegance.
The phone has HBOOT 1.32.000
Whenever I flash Viper XL+ Tellus on the phone the phone Boots to the Home Screen and then if I unlock then the phone does nothing and just shows the HTC logo on Screen.
I had verified the ROM zip file and had checked its MD5
I got same results with Lower version of Viper XL 1.2.0 / Elegancia 6.2.0 ..
I have flashed ROM 2 to 3 Times with same result.
Is HBOOT1.32.00 not compatible to these ROMs?
What am I doing wrong? Has anyone faced the same problem.
Thanks,
SK
Click to expand...
Click to collapse
you probably forgot to flash the boot.img (the kernel). That's probably why it's not booting
Just reboot into bootloader (fastboot mode) connect it to your computer and use "fastboot flash boot boot.img" then fastboot erase cache then fastboot reboot
This should get it working
Please press the thanks button if I helped
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks for reply.
I have already tried that option.:crying:
erkui said:
Thanks pal,
problem is only that the ADB gives the message "no device detected", don't forget that the OS on the mobile phone was wiped! But I found the solution, using a tool called WinDroid for HTC One X Plus. With this tool, I flashed CWM to the phone and rebooted in recovery mode. From there, I could mount the SD-card which gave me the option to copy the .zip file to /SDCARD/ using ADB. Also with the tool CWM, I then installed the file, and it worked. I'm on the air now,passed a night without sleep but I learned a lot!! Problem solved!.
Click to expand...
Click to collapse
If you're able to mount /sdcard/ in recovery. You don't have a One X+.
Sent from my HTC One X+ using Tapatalk
Sujitkundar999 said:
Thanks for reply.
I have already tried that option.:crying:
Click to expand...
Click to collapse
Then flash another kernel. Other than the one that comes with the ROM. Flash a kernel compatible with viperx and it might work.
Cuz when i installed ViperX+ on my phone the kernel that came with the ROM didn't work so i used elite kernel instead. I honestly don't knkw if there's Elite kernel for your phone.. Just flash any other kernel compatible
Sent from my HTC One X+ using XDA Premium 4 mobile app
AndroHero said:
If you're able to mount /sdcard/ in recovery. You don't have a One X+.
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
if your trying to flash a 4.2.2 X+ sense 5 rom it is recomended that you be at hboot 1.40 im not 100% sure of the compatibility with 1.32 but any of the custom roms should flash fine without regard to the newest hboot
I want to root my device but now I don have my pc here so any process of rooting galaxy s3 without pc (adb/odin)
I want flashable zip file for rooting is there any way....?
I want root access only for some apps like chainfire .firewall.....
If you already have a custom recovery, then yes. You can. Usually, when you get out from the recovery, and you are not rooted, it will ask you to root. You select yes and it will root for you
It you are running custom recovery, I think it will be a bit harder.
Anyway, this thread had to be moved to Q&A.
Sent from my GT-I9300 using XDA Premium 4 mobile app
with custom recovery flash this
https://www.dropbox.com/s/hrnpvcrys3tkpuy/UPDATE-SuperSU-v1.93.zip
Sent from my GT-I9300 using XDA Premium 4 mobile app
_moelle said:
with custom recovery flash this
https://www.dropbox.com/s/hrnpvcrys3tkpuy/UPDATE-SuperSU-v1.93.zip
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashing this file root my device completely. ?
Or I have to do anything else. .?
sam.jaat said:
Flashing this file root my device completely. ?
Or I have to do anything else. .?
Click to expand...
Click to collapse
just flashet
Does this file work if I flash it through stock recovery?
No I tried it on stock recovery nd it doesn't work. ..
I think first we need to install custom recovery on it ......
1 Que:-can ww install a custom recovery without pc..?
i already said CUSTOM recovery. - dunno if you could install custom recovery without pc
Sent from my GT-I9300 using XDA Premium 4 mobile app
_moelle said:
i already said CUSTOM recovery. - dunno if you could install custom recovery without pc
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can find your answer in this link
http://forum.xda-developers.com/showthread.php?t=2364018
The best answer to my questions was provided by BCSC, THANKS! Worked great!
Follow these steps exactly and you will have the latest Recovery running. You do not need a PC for this method.
1) Download correct Clockworkmod ot TWRP (touch or regular as you wish) for your device
2) Rename it to recovery.IMG and place it at the root of your internal sdcard
3) Download and install terminal emulator from the Play Store
4) Run the terminal and
type: su (press enter)
Then type: dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (press enter)
Be sure that you have typed the above code correctly. You will not see a confirmation. It is done almost instantly.
5) Reboot into recovery and enjoy
Click to expand...
Click to collapse
And this OP should be moved to Q&A
This won't work since su command won't run successfully coz there is no supersu app.
_____________
Sent from my GT-I9300 powered by Temasek Rom & Kernel
Fueled by 7000mAh ZeroLemon Battery
Solution already available.
The only working and tested method is:
http://forum.xda-developers.com/showpost.php?p=43305707&postcount=1
All other methods will not work.
RESOLVED !!! (Every solution is available in the forum, just require a query for search).
Is there any way to install customod recovery without pc
Using rooted s3
I tried terminal emulator but some error came up
Custom recovery
sam.jaat said:
Is there any way to install customod recovery without pc
Using rooted s3
I tried terminal emulator but some error came up
Click to expand...
Click to collapse
If it is rooted you can use mobile odin and flash tar recovery file.You can even root it without computer using rooting app.Tested.
vietkao said:
You can find your answer in this link
And this OP should be moved to Q&A
Click to expand...
Click to collapse
sam.jaat said:
Is there any way to install customod recovery without pc
Using rooted s3
I tried terminal emulator but some error came up
Click to expand...
Click to collapse
hi,
in i9300 gs3 -recovery partition is 6 not 18
"/dev/block/mmcblk0p6
So guys thanks to the lovely people here on XDA we have the incremental OTA captured!
its NOT the full ROM but is rather a patch to allow you to update to latest 4.4.3
Since this is incremental patch you will need to be on stock/minimally modified Stock KOT49H 4.4.2 ROM, most importantly you will have to be on original kernel (boot.img)...
best would be to use this procedure:
[IMP][ZU_GPe][How-To] Restore to original Google Play Edition firmware!
to get back to stock 4.4.2 (but you may lose your app data)
If you want an in-place upgrade and if you are using any of my kernel (recovery kernels or DooMKernel) then you will have to revert to pure stock kernel..
unfortunately you wont be able to flash the original KOT49H kernel via fastboot (considering that you might have unlocked bootloader)...
i am attaching below the original KOT49H as a recovery flashable zip:
ZU_GPe-DooMLoRD-Stock_KOT49H_kernel
flash it using CWM recovery and the kernel on your GPE device will be replaced with original kernel
now reboot into bootloader
Code:
adb reboot bootloader
select recovery and enter it...
select ADB method and flash the incremental OTA using the command:
Code:
adb sideload <NAME-OF-OTA-FILE>
it will take a while but once its done reboot device and enjoy latest KitKat 4.4.3
regards,
DooMLoRD
once i enter recovery and use the adb sideload command i get the following error:
device not found
vivalamoza said:
once i enter recovery and use the adb sideload command i get the following error:
device not found
Click to expand...
Click to collapse
you have to enable recovery menu (press POWER + VOLUME DOWN for a second or so when u see the "dead android robot screen")...
then select flash via adb (1st option in the recovery)
Can we follow this procedure if using the ported GPE ROM in a C6833? Is there anything GPE-specific in the update ZIP that could brick a non-GPE device?
Thanks!
dbolivar said:
Can we follow this procedure if using the ported GPE ROM in a C6833? Is there anything GPE-specific in the update ZIP that could brick a non-GPE device?
Thanks!
Click to expand...
Click to collapse
PLEASE DO NOT TOUCH THE INCREMENTAL OTA ZIP ON NON-GPE DEVICE!
bootloader/modem and lots of other things are getting patched!
wait for the fill flash zip and then port that...
What happens if I click restart and install that notification won't go away
Sent from my C6806_GPe using XDA Premium 4 mobile app
Okay restoring from the full 4.4.2 OTA then sideloading of the 4.4.3 OTA worked.
Definitely not as using fastboot....
So... Once I flash the 4.4.3 Update (Thanks btw); do I reflash your Kernel?
If not, how do I re-root?
Thanks,
Flipper
DooMLoRD said:
So guys thanks to the lovely people here on XDA we have the incremental OTA captured!
its NOT the full ROM but is rather a patch to allow you to update to latest 4.4.3
Since this is incremental patch you will need to be on stock/minimally modified Stock KOT49H 4.4.2 ROM, most importantly you will have to be on original kernel (boot.img)...
best would be to use this procedure:
[IMP][ZU_GPe][How-To] Restore to original Google Play Edition firmware!
to get back to stock 4.4.2 (but you may lose your app data)
If you want an in-place upgrade and if you are using any of my kernel (recovery kernels or DooMKernel) then you will have to revert to pure stock kernel..
unfortunately you wont be able to flash the original KOT49H kernel via fastboot (considering that you might have unlocked bootloader)...
i am attaching below the original KOT49H as a recovery flashable zip:
ZU_GPe-DooMLoRD-Stock_KOT49H_kernel
flash it using CWM recovery and the kernel on your GPE device will be replaced with original kernel
now reboot into bootloader
Code:
adb reboot bootloader
select recovery and enter it...
select ADB method and flash the incremental OTA using the command:
Code:
adb sideload <NAME-OF-OTA-FILE>
it will take a while but once its done reboot device and enjoy latest KitKat 4.4.3
regards,
DooMLoRD
Click to expand...
Click to collapse
flipperg said:
So... Once I flash the 4.4.3 Update (Thanks btw); do I reflash your Kernel?
Thanks,
Flipper
Click to expand...
Click to collapse
The kernel provided in the first post is for 4.4.2
If you flashed the 4.4.3 update properly then you you are good to go!
Though if you want custom recoveries just check the advanced stock kernel posted in my other thread...
Sent from my D6503 using XDA Free mobile app
Awesome!
:laugh:
That's what I needed - thank you, I did exactly that and then re-rooted from CWM via your Advanced Stock Kernel. I'm back.
Thank you,
Flipper
DooMLoRD said:
The kernel provided in the first post is for 4.4.2
If you flashed the 4.4.3 update properly then you you are good to go!
Though if you want custom recoveries just check the advanced stock kernel posted in my other thread...
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
---------- Post added at 02:26 AM ---------- Previous post was at 02:18 AM ----------
In case this helps others - I always change my DPI via ROM Toolbox build.prop editor and also install Xposed Framework...
Undo both (400 DPI, and Uninstall Framework) before you run the update or it will fail.
Flipper
flipperg said:
:laugh:
That's what I needed - thank you, I did exactly that and then re-rooted from CWM via your Advanced Stock Kernel. I'm back.
Thank you,
Flipper
Click to expand...
Click to collapse
DooMLoRD said:
you have to enable recovery menu (press POWER + VOLUME DOWN for a second or so when u see the "dead android robot screen")...
then select flash via adb (1st option in the recovery)
Click to expand...
Click to collapse
Thanks
Did that and now I have a message on my phone saying:
Now send the package you want to apply to the device with "adb sideload <filename>...
The thing is when I send the file via adb I get the error: device not found
I check my device manager and I found a yellow exclamation mark next to the phone, does the phone need a different driver to use the sideload command?
vivalamoza said:
Thanks
Did that and now I have a message on my phone saying:
Now send the package you want to apply to the device with "adb sideload <filename>...
The thing is when I send the file via adb I get the error: device not found
I check my device manager and I found a yellow exclamation mark next to the phone, does the phone need a different driver to use the sideload command?
Click to expand...
Click to collapse
A driver is probably not installed correctly. Re-install it and try again. If that doesn't work:
- Boot your phone
- Go to developer settings and enable USB debugging, and authorize ADB (it'll pop up and ask you on your phone)
- Open cmd on your computer and type "adb devices". Your device is a string of characters and numbers, like: "4JKF45234F" etc.
- If your device is found, try sideloading it now, by typing "adb sideload [file path]" and wait for it to flash it.
vivalamoza said:
Thanks
Did that and now I have a message on my phone saying:
Now send the package you want to apply to the device with "adb sideload <filename>...
The thing is when I send the file via adb I get the error: device not found
I check my device manager and I found a yellow exclamation mark next to the phone, does the phone need a different driver to use the sideload command?
Click to expand...
Click to collapse
I had this issue and drivers needed to be installed. Right click on device with exclamation, tab over to drivers, then select update drivers and "choose browse my computer", find the Sony fastboot and adb drivers from flashtool folder and install them. If you are on win8 or 8.1 you will need to disable signature verification. I assume somehow flashtool is able to use the drivers without them actually being installed?
@vivalamoza another option is to copy update to SD card and flash it from there using stock recovery.
Exactly that's a question I had, can't I just choose apply update from SD instead and browse the file location on my phone.
Sent from my C6806_GPe using XDA Premium 4 mobile app
vivalamoza said:
Exactly that's a question I had, can't I just choose apply update from SD instead and browse the file location on my phone.
Sent from my C6806_GPe using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did it that way by copying update to SD , flashing the CWM flashable stock recovery, then following the return to stock guide. Except at the end I chose apply update from SD instead of adb sideload. If you have used xposed to edit framework I would use the uninstall option inside xposed installer app. Also if any system apps have been deleted it will error out and not install.
@DooMLoRD do you have any idea what broke our cameras after update? Is it possible to return to 4.4.2 using your restore method with the full ota?
adfurgerson said:
@DooMLoRD do you have any idea what broke our cameras after update? Is it possible to return to 4.4.2 using your restore method with the full ota?
Click to expand...
Click to collapse
Full OTA of 4.4.2 won't work... Give me a few days I am out of town, will work on a fix soon!
Sent from my D6503 using XDA Free mobile app
DooMLoRD said:
Full OTA of 4.4.2 won't work... Give me a few days I am out of town, will work on a fix soon!
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks!
I flashed 4.4.3 using stock recovery and I'm unrooted. I'm having no camera problems, everything seems to be working fine. I'm using Google camera.
Sent from my C6806_GPe using XDA Premium 4 mobile app
vivalamoza said:
I flashed 4.4.3 using stock recovery and I'm unrooted. I'm having no camera problems, everything seems to be working fine. I'm using Google camera.
Sent from my C6806_GPe using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odd. My camera is completely broken.
Sent from my BN NookHD+ using Tapatalk
So I got the 5.12.10 update for the weekly developer ROM and it installed stock recovery over TWRP and unrooted my phone. The first time I rooted I managed to flash TWRP with stock recovery, but it isn't working this time. I've had a lot of trouble trying to install via ADB drivers. Help please?
PytSkee said:
So I got the 5.12.10 update for the weekly developer ROM and it installed stock recovery over TWRP and unrooted my phone. The first time I rooted I managed to flash TWRP with stock recovery, but it isn't working this time. I've had a lot of trouble trying to install via ADB drivers. Help please?
Click to expand...
Click to collapse
Did you rename TWRP to update.zip and put it on the root of the internal storage before flashing? If yes and it still failed, you'll have to give us a bit more info as to why it failed to flash (any error messages f.e.?). Should be fairly trivial to flash TWRP and SuperSU
elaurens said:
Did you rename TWRP to update.zip and put it on the root of the internal storage before flashing? If yes and it still failed, you'll have to give us a bit more info as to why it failed to flash (any error messages f.e.?). Should be fairly trivial to flash TWRP and SuperSU
Click to expand...
Click to collapse
It wasn't too difficult the first time, but the recovery seems to be using some sort of signature on the ROM's. All it tells me is that "Install update.zip failed! update.zip signature verification failed." It is named update.zip on the root of internal storage.
PytSkee said:
It wasn't too difficult the first time, but the recovery seems to be using some sort of signature on the ROM's. All it tells me is that "Install update.zip failed! update.zip signature verification failed." It is named update.zip on the root of internal storage.
Click to expand...
Click to collapse
Hm, from what I've found on the miui forum, you're not the first one having this issue. These are the "possible" solutions I've gathered from a couple of threads.
1) Flash TWRP using fastboot (rename twrpxxxx.zip to recovery.zip and place it in the same folder as the fastboot executable):
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
2) Update your current ROM (stable/developer) to the latest version if that isn't the case yet and try flashing TWRP again trough the update app
3) Flash TWRP using Flashify
1. download flashify app from playstore and give root acces
2. download img of twrp for redmi 2 note and put in your sd card (I prefer sdext root folder)
3. Open flashify, select "recovery image", find the img file you've downloaded
4. confirm flash, wait until it's done
4) Re-download a copy of TWRP or use a different one (like this one for example)
Let me know how it went..
So I tried Flashify and every time I tried to use it, the app froze right before/after selecting the recovery image. I did, however, manage to make the ADB and fastboot methods work on my desktop PC. I have no idea what I did wrong before, maybe the wrong ADB drivers? Anyway, I did get it working, so thank you
PytSkee said:
So I tried Flashify and every time I tried to use it, the app froze right before/after selecting the recovery image. I did, however, manage to make the ADB and fastboot methods work on my desktop PC. I have no idea what I did wrong before, maybe the wrong ADB drivers? Anyway, I did get it working, so thank you
Click to expand...
Click to collapse
Used windroid to do all these: http://en.miui.com/forum.php?mod=viewthread&tid=167882&extra=pag
Sent from my Redmi Note 2 using Tapatalk
timberwolf60 said:
Used windroid to do all these: http://en.miui.com/forum.php?mod=viewthread&tid=167882&extra=pag
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
I remember seeing this right after I ordered my phone. I had totally forgotten about it by the time I got it though, as it was more than a month later But thanks for reminding me, I already have it installed on my home PC!