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
Related
I used to flash recovery via terminal app on Nexus One, using command "flash_image". But it seems this command doesn't exist on Atrix 4G. Is it able to do this on Atrix 4G & how?
I think you have to use fastboot via USB from pc... Google it
However once you have CWM you can update via zip files within CWM
Sent from my Sony Tablet S using Tapatalk
wintermute000 said:
I think you have to use fastboot via USB from pc... Google it
However once you have CWM you can update via zip files within CWM
Sent from my Sony Tablet S using Tapatalk
Click to expand...
Click to collapse
Thanks any way.
There is an app called MOTOA4 Bootstrap that can install a CWM Recovery shipped with the app. Maybe ROM Manager would also do (not tested yet). So it's possible to change recovery within Android system (rooted). What I'm looking for is just an command line utility to flash any recovery I want.
amraamz said:
I used to flash recovery via terminal app on Nexus One, using command "flash_image". But it seems this command doesn't exist on Atrix 4G. Is it able to do this on Atrix 4G & how?
Click to expand...
Click to collapse
i think that is possible only with a recovery yet installed, to upgrade or something else
amraamz said:
Thanks any way.
There is an app called MOTOA4 Bootstrap that can install a CWM Recovery shipped with the app. Maybe ROM Manager would also do (not tested yet). So it's possible to change recovery within Android system (rooted). What I'm looking for is just an command line utility to flash any recovery I want.
Click to expand...
Click to collapse
you can flash latest cwm recovery with rom manager
Has Anyone Got it yet? some nexus 4 and nexus 7 users are getting it right now in the usa it seems
http://www.androidpolice.com/2013/02/11/breaking-android-4-2-2-update-rolling-out-to-gsm-galaxy-nexus-nexus-7-nexus-10/
come on developers drop it to ROMs !!
anyone receive it
please help to find the ota link
step
http://forum.xda-developers.com/showpost.php?p=21025378&postcount=27
Popped up on my daughter's stock, unrooted N7 about 5 minutes ago. I assume because I'm running a custom ROM with a custom recovery OTAs will be blocked on my N10 (that's how it was on my OG Droid and LTE GNexus).
I might have been excited about this a few months ago but now it's just meh.. I'll just wait for Rascarlo to update RasBean... My tablet is rock solid stable right now.. I'm in no rush to beta test another one of Googles messes.
Nexus 10 4.2.2 OTA URL
Hi all,
You can download 4.2.2 OTA from below link. Have a fun!! :fingers-crossed:
MD5:ed637878ccba20ba9d44e62685ac67e9
http://android.clients.google.com/p...igned-mantaray-JDQ39-from-JOP40D.eaef1443.zip
saltxyz said:
Hi all,
You can download 4.2.2 OTA from below link. Have a fun!! :fingers-crossed:
MD5:ed637878ccba20ba9d44e62685ac67e9
http://android.clients.google.com/p...igned-mantaray-JDQ39-from-JOP40D.eaef1443.zip
Click to expand...
Click to collapse
awesome thanks ! now how to update ?
nightfox11 said:
awesome thanks ! now how to update ?
Click to expand...
Click to collapse
adb sideload UPDATE-NAME.zip from Recovery with Android SDK
Not showing up for me in Canada yet.
Sent from my GT-I9300 using xda premium
espionage724 said:
adb sideload UPDATE-NAME.zip from Recovery with Android SDK
Click to expand...
Click to collapse
And with stock rom and stock recovery? Update from zip?
lKBZl said:
And with stock rom and stock recovery? Update from zip?
Click to expand...
Click to collapse
you should have adb in stock recovery aswell. just boot to stock recovery, make sure that you've configured the drivers and use the above command to install the update via adb
I've never tried that procedure though, but I guess it should work
I'm rooted but with stock recovery. Can I just use OTA root-keeper to temp-unroot, install update and then re-root?
antonusklesk said:
I'm rooted but with stock recovery. Can I just use OTA root-keeper to temp-unroot, install update and then re-root?
Click to expand...
Click to collapse
Yes, but don't temp unroot, backup the root and then use backup to root again.
Cheers, looking forward to getting home and having a play.....even if it is only minor fixes.
And thus starts a barrage of soft brick help threads because toolkits make simple tasks stupidly more complicated then they need to be.
onemandivision said:
you should have adb in stock recovery aswell. just boot to stock recovery, make sure that you've configured the drivers and use the above command to install the update via adb
I've never tried that procedure though, but I guess it should work
Click to expand...
Click to collapse
Can this get me into a soft brick and the comment over this one says?
lKBZl said:
Can this get me into a soft brick and the comment over this one says?
Click to expand...
Click to collapse
Yup.
So, is there a changelog?
lKBZl said:
Can this get me into a soft brick and the comment over this one says?
Click to expand...
Click to collapse
heres what i did:
1) download the latest stock factory image from google: https://developers.google.com/android/nexus/images#mantaray (JOP40C)
2) download the ota update JP40C->JOP40D http://android.clients.google.com/p...gned-mantaray-JOP40D-from-JOP40C.07ac4f5d.zip
3) download the ota update JOP40D->JDQ39 http://android.clients.google.com/p...igned-mantaray-JDQ39-from-JOP40D.eaef1443.zip
4) download the latest team win recovery .img file: http://techerrata.com/browse/twrp2/manta
5) reboot into bootloader mode
6) unzip the stock firmware from step 1)
7) open command line window, cd to folder where image-mantaray-jop40c.zip is, type fastboot update image-mantaray-jop40c.zip (add option -w if you want to clear userdata aswell, this will wipe your sdcard)
8) wait for reboot and get back into bootloader
9) open command line window, cd to folder where the team win recovery image file is, type fastboot flash recovery openrecovery-twrp-2.4.1.0-manta.img (filename can be different depending on the version you downloaded)
10) reboot into bootloader, select reboot recovery, open command line window, cd to where ota updates are, type adb push *filename* /sdcard for each ota update (replace *filename* by actual filename)
11) select install in team win recovery, install update from step 2) first, then update from step 3)
reboot.
you might lose all your data including your files stored on your tablet. this is probably the must reliable way to update because everything is set back to stock and then updated. so no customization whatsoever should interfere
heres the result:
Ignore the post by onemandivision previous steps are easier
Custom boot image for 6.2.A.0.400 + CWM Touch v5.5.0.4 stable
DISCLAIMER:
I am not responsible for anything! If you using this boot you need to agre that you using this thread on your own risk, I am not responsible for anything! You doing this on your own risk! If you no want to play with this than simple skip this thread!
All tweaks and features is the same like in my ICS custom rom, so contain OC, init.d, tweaks, governors, schedulers ...etc!!! Bluetooth is fixed and everything working now! CPU clock is by default disabled so if you need owerclock simple install an apk for CPU control and setup whatewer you want. Defauld scheduler is SIO.
Download:
custom_boot_for_stock_XPERIA_Go_JB.zip
Tutorial:
1. reboot to fastboot (shutdown device, pres and hold volumeup+connect usb to your computer, you will see blue led which mean you entered phone into fastboot mode)
2. unlock boot loader if you have bootloader not unlocked (go to Sony site for tutorial)
3. in the same window where you unlocked boot loader flash boot.img (extract them from zip archive and put into the same folder with fastboot.exe) by command:
fastboot.exe flash boot boot.img
4. next command:
fastboot reboot
5. wait 4 diferent led colors and press volume up or down button after vibration to enter into recovery mode
6. go to mounts and storage and open mount external storage sub menu, mount internal sdcard and put our zip archive into sdcard, remount sdcard, back into main menu
7. install zip trought menu "install zip from sdcard"
8. busybox is included in zip and will be automatically installed
9. su binary is included but is compatible only with Superuser.apk!!! If you want to install SuperSu.apk you need to change su binary because curent su binary is compatible only with Superuser.apk !!!
10. install Superuser.apk from Playstore
11. you are done, reboot again your phone
Do not use flashtool for rooting! Do not use bin4ry for rooting! Do not install another busybox. I tested everything only by using methods from this OP, all other untested methods will be ignored and I will ignore you (and maybe stop all developments related to Xperia Go if you iratate me by your negative comments) if you not folowing current OP and if you report here bad things about boot image after not folowing me here! Our boot image is tested only on STOCK ROM AND NOT ON TWEAKED ROMS!!! DO NOT REPORT HERE ANYTHING IF YOU USE MODIFIED STOCK ROM!!!
My kernel source code:
https://github.com/munjeni/android_kernel_xperiago
Credits:
- Sony for kernel source code
munjeni said:
Hi, here is boot image and CWM only for Stock JB rom, enjoy!
http://d-h.st/pWj
Click to expand...
Click to collapse
wow 10x ! ! !
Dude you rock!!!
As it Install?
Thanks Munjeni!
Flashed boot.img over official stock in fastboot mode
No more internal neither external memory recognized for me (CE firmware)
Any fix?
EDIT: just a problem with my SD card. Now works! thank you again Munjeni!
It work for me, I changed the si_numbers in buildprop, update from Ics to Jb. Then unlocked the bootloader and flashed the boot.img. Then from recovery i installed su for to have root....... Perfect many thanks.
Sent from my ST27i using xda premium
JB resources released by Sony
http://developer.sonymobile.com/dow...uild-6-2-a-0-400-6-2-a-0-402-and-6-2-a-0-404/
Sent from my Xperia Sola using xda premium
Edit: Im a bit confuse... can you make a tutual?
Sent from my ST27i using xda premium
konchkae said:
Hi, i'm new i just install CWM
how to root? xperia go JB unlock BL
Sent from my ST27i using xda premium
Click to expand...
Click to collapse
I'm attempt a guide for flash boot.img
Amazing, as always..
Thanks..
needs bl unlocked?
androidmeda said:
needs bl unlocked?
Click to expand...
Click to collapse
Hi.
Yes you need
Wow will try this later
Sent from my ST27i using xda premium
munjeni, can you help us to use sd card as internal on JB like nosmaster help with changing "vold.fstab" on ICS? I don't think it works here.
xperia_88 said:
munjeni, can you help us to use sd card as internal on JB like nosmaster help with changing "vold.fstab" on ICS? I don't think it works here.
Click to expand...
Click to collapse
Try directory bind
CiscoX said:
Hi.
Yes you need
Click to expand...
Click to collapse
I'll probably wait for the locked bl root. How's the performance with stock?
Very good beter then Ics.
Sent from my ST27i using xda premium
CiscoX said:
Hi.
Yes you need
Click to expand...
Click to collapse
Hi can to tell me step by step?
I want too root
i flash via flashtools but.it said fail
Sent from my ST27i using xda premium
konchkae said:
Hi can to tell me step by step?
I want too root
i flash via flashtools but.it said fail
Sent from my ST27i using xda premium
Click to expand...
Click to collapse
Hi.
You need to unlock the bootloader before you use flashtool.
http://unlockbootloader.sonymobile.com/
Read it carefully and follow the instructions. This will help you to unlock the bootloader.
After that you can use the flashtool, use fastboot mode then.
i just flashed boot.img but when i downloaded superuser and supersu it said that su binary is not found...so how is this boot.img prerooted?
I have seen that since the update notification for Jelly Bean has arrived, Many people (Including me) have been asking for a Tutorial to root the Jelly Bean updated HTC Desire X (HTC DX for short). In this tutorial I would like to mention the steps to root Android Jelly Bean (JB) on HTC DX.
UPDATE: Tutorial with Screenshots here : HTC Desire X Root
This was what had worked for me when I recently rooted by HTC Desire X with Jelly Bean Update, So I hope it works for you too. I am assuming you have just installed the OTA Update and are now sitting with a Stock Jelly Bean on your device.
Summary:
1. Unlock Bootloader (if not already unlocked).
2. Install Jelly Bean compatible Custom Recovery.
3. Flash Super User and Install Busy Box.
4. Enjoy.
Steps.
1. Unlocking Bootloader.
There is a fully explained thread on unlocking bootloader and rooting android ICS put up by user nlooooo, Follow that thread and unlock your bootloader.
http://forum.xda-developers.com/showthread.php?t=2076675
2. Install Jelly Bean compatible Custom Recovery.
Once you update via OTA for the JB Update, Your HBoot becomes JB Hboot instead of the old ICS Hboot so you need a JB Hboot compatible Custom Recovery to flash the Super User and Root.
Our fellow user atis112 fixed the recovery by neXus PRIME to make it work with JB. So you need to download the JB Custom Recovery from the attachment and put it in your C Drive, So the file location would be C:\recovery.img
2.1] Download JB Recovery.img from here : http://forum.xda-developers.com/showpost.php?p=39662992&postcount=66 OR You can use the TWRP Recovery Image made by Yasir. Download from here : http://d-h.st/tSc
2.2] Once you put it in C Drive you need to connect your HTC Mobile to PC and Install HTC JB Drivers, You can install the drivers from here : http://forum.xda-developers.com/showthread.php?t=2222501. Make sure you have installed the Drivers correctly.
2.3] Open your Android SDK (Download it from here if not already) and Go to the \sdk\platform-tools folder. If on Windows 7, Keep the Shift Key pressed + Right click on an empty place in the platform-tools folder > Open Command Window here.
2.4] Type in the following command and see if your device is detected.
adb devices
Click to expand...
Click to collapse
After it is detected, Type the following command.
adb reboot bootloader
Click to expand...
Click to collapse
Once you are in the bootloader, Type the following command.
fastboot flash recovery c:\recovery.img
Click to expand...
Click to collapse
followed by
fastboot reboot-bootloader
Click to expand...
Click to collapse
and
fastboot erase cache
Click to expand...
Click to collapse
2.5] Now you have installed your custom recovery. Now Reboot your Phone.
3. Install SuperUser and Busybox.
3.1] Once again connect your HTC to PC, Download the attached SuperUser.zip and copy it to your SD Card.
3.2] Open the command prompt again as said earlier by going to platform-tools folder and using the adb devices command to check if the phone is detected.
3.3] Once it is connected, Type the following command.
adb reboot recovery
Click to expand...
Click to collapse
3.4] Now you are in the recovery, Use the Volume Up and Down keys to navigate it (Use the power button to select an option).
Navigate to Install Flashable Zip. (This should be the first option and already selected.)
Press Power Button once.
Select "Choose Zip from internal SD-Card" or "external SD-Card" accordingly as to where you put the Superuser.zip.
Press Power Button once.
Scroll and select the Superuser.zip using the Volume Keys.
Press Power Button once.
Then you have flashed your Zip successfully and you are rooted.
Go back to the Main screen using the "Go back" option. Select the "Reboot System Now".
Once you are in the HTC Main screen > Go to App Drawer > Google Play Store > Search for Busy Box and Install it.
That is it, You are now on Jelly Bean and Successfully Rooted.
To Check If You Are Rooted.
1. Open Playstore and search for an app named "Terminal Emulator".
2. Install it.
3. Open it and type in su and execute it.
4. You will get a prompt from Superuser to allow or deny > Allow it.
If you get that prompt, You are successfully rooted.
I hope I have provided credits to all the users whose threads I have mentioned. If not please let me know.
Thanks for reading this.
Or you can refer to my TWRP for JB. Its much better than the fixed neXusRecovery.
Hey, I didn't check that.. Can you give a link to the recovery?
Droid.Anoop said:
Hey, I didn't check that.. Can you give a link to the recovery?
Click to expand...
Click to collapse
Here: http://d-h.st/tSc
xpirt
xpirt said:
Here: http://d-h.st/tSc
xpirt
Click to expand...
Click to collapse
Done. Added it to the post. Thanks Yasir and Xpirt
Droid.Anoop said:
Done. Added it to the post. Thanks Yasir and Xpirt
Click to expand...
Click to collapse
1 more little thing.
I think the instructions in recovery are using vol up down and power buttons. But if im not mistaken,, both my recoveries you mentioned are Touch enabled. So actually no need to bash the crappy volume buttons (i really hate these volume buttons due to bad tactile feedback)
neXus PRIME said:
1 more little thing.
I think the instructions in recovery are using vol up down and power buttons. But if im not mistaken,, both my recoveries you mentioned are Touch enabled. So actually no need to bash the crappy volume buttons (i really hate these volume buttons due to bad tactile feedback)
Click to expand...
Click to collapse
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Droid.Anoop said:
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Click to expand...
Click to collapse
Both my recoveries are touch enabled.
1. TWRP (JB)
2. neXusRecovery. (discontinued for updates)
I'm not really a fan of buttons.
Droid.Anoop said:
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Click to expand...
Click to collapse
Yes, also fixed recovery is touch enabled: you mean the nexus Recovery, right?
xpirt
xpirt said:
Yes, also fixed recovery is touch enabled: you mean the nexus Recovery, right?
xpirt
Click to expand...
Click to collapse
Yes, Thanks for letting me know. Also is there any method to unlock the write protection in JB? I think the JB Sources are not released yet but any workaround?
Droid.Anoop said:
Yes, Thanks for letting me know. Also is there any method to unlock the write protection in JB? I think the JB Sources are not released yet but any workaround?
Click to expand...
Click to collapse
I think ckpv5 found a way. Just think.
xpirt
xpirt said:
I think ckpv5 found a way. Just think.
xpirt
Click to expand...
Click to collapse
Wow that is cool! Wonder if he will share it soon. Or has he already shared it somewhere?
Droid.Anoop said:
Wow that is cool! Wonder if he will share it soon. Or has he already shared it somewhere?
Click to expand...
Click to collapse
Look at his ROMs: deodexed one and myOneDx+ have both hTC write permissions defeated.
xpirt
xpirt said:
Look at his ROMs: deodexed one and myOneDx+ have both hTC write permissions defeated.
xpirt
Click to expand...
Click to collapse
There is a wp_mod which has a Module file "wp_mod2.ko" and an init.d script, (credits to flar2) using which ckpv5 has made his roms.
neXus PRIME said:
There is a wp_mod which has a Module file "wp_mod2.ko" and an init.d script, (credits to flar2) using which ckpv5 has made his roms.
Click to expand...
Click to collapse
Can you explain how to implement it in stock ROM? Then we can integrate it in the tutorial with proper credits.
Droid.Anoop said:
Can you explain how to implement it in stock ROM? Then we can integrate it in the tutorial with proper credits.
Click to expand...
Click to collapse
Look at flar2's thread but use the files from ckpv5's ROM, but first ask him for permission.
xpirt
root JB without flashing custom recovery?
Hi!
I haven't flashed TWRP v2.5.0.0 but only boot the phone into this custom recovery, which is working perfectly. (I want to keep the stock recovery.)
I can install and use the Aroma File Manager (TWRP with Aroma File Manager did not work.)
I can mount the system partition and change / delete files.
However, with a reboot, all my changes will be undone.
Before installing Aroma File Manager for the first time, I installed SuperSu1.34.zip. No error. I installed Aroma File Manager right after it, and I think it said "rooted".
Using TWRP's SuperSu does not work (no error message, but system reboots, and it says it's not rooted.)
My question: can I root my phone while only booting into a non-stock recovery or do I have to flash TWRP and then root the phone?
Would I see the system apps e.g., after mounting /system, even if the phone was not rooted?
I am new to JB, I had 2.3.7 before, which I could root without flashing a custom recovery.
I am not sure if I have to flash the custom recovery because of the s-off problem with HTC devices?
If I flash a custom recovery and root the device, can I flash the stock recovery afterwards without loosing root again?
Would you recommend using SuperSu or Superuser? Which version?
I don't think I need busybox.
I only want to delete bloatware and change the battery symbol.
Thanks for your help!
I didn't try rooting using the stock recovery, but I think it won't be possible as it won't let us change system partition due to S-On. But after you rooted using a custom recovery you can flash the stock recovery again without loosing root. But keep in mind that you won't be able to change system partition. Also, you can't flash zips which aren't signed by HTC.
Sent from my HTC Desire X using xda premium
dansou901 said:
I didn't try rooting using the stock recovery, but I think it won't be possible as it won't let us change system partition due to S-On.
Click to expand...
Click to collapse
The question is if there is a difference if I just boot into the custom recovery vs. if it is flashed and I boot into it. Does ist need to be properly flashed to allow writing in /system?
mary-lou said:
The question is if there is a difference if I just boot into the custom recovery vs. if it is flashed and I boot into it. Does ist need to be properly flashed to allow writing in /system?
Click to expand...
Click to collapse
How do you boot into a custom recovery without flashing it first? It has to be on recovery partition to work correctly.
Hello
After searching the internet for good 30-40 minutes I found the Stock OnePlus 2 recovery image. I am returning my unit so needed it to be fully stock.
Download: https://www.dropbox.com/s/8np35kw71i222as/OPT Stock Recovery.7z?dl=0
Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Been searching for this for past hour!!!!!!
Hi,
Thank you very much.
I'm also returning my phone to oneplus and i had unlocked and rooted the phone like you.
May i know how you restore the stock ROM and recovery?
thank you
Why do you need stock recovery for that? I just wiped everything on mine and when I rebooted from twrp I chose not to protect twrp. Rma was approved so I guess they were satisfied with that.
Sent from my A0001 using Tapatalk
granfot said:
Why do you need stock recovery for that? I just wiped everything on mine and when I rebooted from twrp I chose not to protect twrp. Rma was approved so I guess they were satisfied with that.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
What do you means by "wipe everything"? include internal storage?
And i heard that official twrp dont have the option of "not to protect twrp".
werthechamp said:
What do you means by "wipe everything"? include internal storage?
And i heard that official twrp dont have the option of "not to protect twrp".
Click to expand...
Click to collapse
Yes, including internal storage.
That I didn't know, but you don't void warranty by installing custom recovery or rooting so it shouldn't be an issue either way.
Sent from my A0001 using Tapatalk
granfot said:
Yes, including internal storage.
That I didn't know, but you don't void warranty by installing custom recovery or rooting so it shouldn't be an issue either way.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Is this the recovery of the international version or chinese?
thx
This is not the international version but chinese . Im looking for the english version, searched everywhere but unable to find it. wtf
1. Download the latest signed flashable zip from here.
2. Press thanks for Spannaa.
3. Extract recovery.img from the zip file with 7zip.
4. Flash it from fastboot using the "flash recovery recovery.img" command.
CafeKampuchia said:
1. Download the latest signed flashable zip from here.
2. Press thanks for Spannaa.
3. Extract recovery.img from the zip file with 7zip.
4. Flash it from fastboot using the "flash recovery recovery.img" command.
Click to expand...
Click to collapse
Problem: The signed flashable zips don't contain recovery.img
Spannaa said:
Problem: The signed flashable zips don't contain recovery.img
Click to expand...
Click to collapse
Hmmmm... that would be a problem. :/ Thanks for pointing that out.
CafeKampuchia said:
Hmmmm... that would be a problem. :/ Thanks for pointing that out.
Click to expand...
Click to collapse
I Installed the 2.0 manually...then update ota...now I have stock recovery.
zat0x said:
This is not the international version but chinese . Im looking for the english version, searched everywhere but unable to find it. wtf
Click to expand...
Click to collapse
Hey, I don't know if you ever found the stock recovery but another member had posted fastboot images in the OnePlus2 Android Development section.
I haven't tested out the recovery myself, but you can check to see if it's the English one.
All Fastboot images: https://www.androidfilehost.com/?w=files&flid=40701
Stock Recovery Image: https://www.androidfilehost.com/?fid=24052804347834210
Hope this helps.
Using these, how would I return my OP2 to completely stock recovery and kernel?
Thanks
keshavmot2 said:
Using these, how would I return my OP2 to completely stock recovery and kernel?
Thanks
Click to expand...
Click to collapse
Good question! Want to know that too...
keshavmot2 said:
Using these, how would I return my OP2 to completely stock recovery and kernel?
Thanks
Click to expand...
Click to collapse
1:
Flash the full stock rom from OxygenOS 2.1.1: http://forum.xda-developers.com/showthread.php?t=3209863
2: Flash the OxygenOS 2.1.2 zip from the same post
3: flash the stock recovery from tgis thread
Hope I helped you
Download OP2 Stock Recovery from Official Site: https://s3.amazonaws.com/oxygenos.oneplus.net/OP2_recovery.img
It seems OnePlus uses AWS to host all of their OTA's.
E.G. https://s3.amazonaws.com/oxygenos.oneplus.net/OnePlus2Oxygen_14_OTA_012_all_1602261837.zip ( This is for OxygenOS 2.2.1 releases in 2012 26th Feb - 970MB )
Recent ROM Downloads of OP2: http://downloads.oneplus.net/devices/oneplus-2/ ( Includes Marshmallow Beta OxygenOS 3.0 , however, seems the ROM has Battery issue, major )
matrixdefalco said:
I Installed the 2.0 manually...then update ota...now I have stock recovery.
Click to expand...
Click to collapse
I did the same thing and it worked for me If somebody is still facing this issue
anyone knows how the flash the stock recovery from mac???
krishp said:
anyone knows how the flash the stock recovery from mac???
Click to expand...
Click to collapse
One "?" is enough dude..
You have to install adb for Mac (http://stackoverflow.com/questions/31374085/installing-adb-on-mac-os-x), enable USB Debugging on your phone, reboot into bootloader mode :
Code:
adb reboot-bootloader
then go into:
Code:
su
and then
Code:
fastboot devices
fastboot flash <recovery_name>.img