Preamble
This is the S-OFF upgrade from GingerBread to HoneyComb
Do not perform this procedure if you have the official HTC hboot, it will not work. You must have a revolutionary hboot (see prerequisites).
***If you performed this procedure with previously and have hboot version 6.14.5555 please update to the new hboot, 6.14.5555 is no longer supported***
Upgrade instructions at the bottom of the procedures.
Prerequisites
You must have performed Revolutionary S-OFF
If running on windows you will need these fastboot drivers
If running the procedure on Linux or MacOS you must have fastboot working.
There are no other software prerequisites for this procedure, it does not matter what ROM/Kernel or recovery you are using.
Don't bother asking for help if you try to do this on a virtual machine, you won't get any.
Run on a real machine.
Windows Instructions
Download this file MD5=c62cc1d0453799a7277abfea444d20e4
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the RUU_Express_B02 directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Alternative Installation Instruction (Any OS)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the RUU_Express_B02_RAW.zip file PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Do not mirror files from this post.
No discussion of Honeycomb content or changes or the relative merits of Gingerbread and Honeycomb. This thread is for the procedure and support thereof only! Also please don't quote the first post because your post becomes an automatic TLDR.
Update Instructions
Use these instructions if you currently have hboot 6.14.5555 - Your data should be preserved but take a backup first just in case.
Method 1
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Copy the file to the root of your external SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
Method 2
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip PG41IMG.zip
[I][COLOR="Red"]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/COLOR][/I]
fastboot reboot
[Revision History]
B02 - updated full version: hboot 6.14.5556
New bootloader to patch bugs with fastboot flashing
- Fastboot flashing splash1 fixed
- Fastboot flashing hboot fixed
Patch for upgrading from a previous version added.
B01 - Initial full version: hboot 6.14.5555
BETA- Developer preview
Special thanks: contradude for the early and riskiest testing, and Maine_Coon for all the ongoing testing
Downgrade to Gingerbread
Preamble
This is the S-OFF downgrade from HoneyComb to S-OFF GingerBread if you are not S-OFF and have a HTC (not revolutionary) hboot then do not do this it will not work.
The full versions of these files will give you a fully functional Gingerbread installation with S-OFF, CWM recovery and boot image with the secure flag turned off.
Windows Instructions
Download this file MD5=f5afc4b457a17f88cc611b40e6c7cdc8
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the Express_Downgrade directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Alternative Installation Instruction (Any OS)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the file downloaded in step1 to PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Do not mirror files from this post.
wow you are really fast, excellent men.
One for me please
reserved 2
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
vancraft said:
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
Click to expand...
Click to collapse
This is an attempt to make downgrading easier for us.
spartan1987 said:
This is an attempt to make downgrading easier for us.
Click to expand...
Click to collapse
Right. That's the "recovery" part.
But its also described as "root, and all". I'm wondering if this allows the installer to root the OTA Honeycomb? Or will more work be required before the install can be further changed (i.e. s-off, eventually upgraded to ICS, etc.)?
It works
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
risb577 said:
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
Click to expand...
Click to collapse
so, does that mean you could, in theory, flash a custom HC rom once we get one?
Throw up some screenshots or a video would you?
edit: oh and test rom manager and titanium backup if you don't mind.
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
stuck on soft brick..
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Maine_Coon said:
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
Click to expand...
Click to collapse
No, as it says in the OP, You MUST be s-off and THEN run an RUU. Accept all updates to include the HC update and the view will be soft bricked. THEN use fastboot to push the mini ruu.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
myowin said:
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Click to expand...
Click to collapse
If it says it's an unrecognized command, then either you do not have fastboot installed, or you haven't gone into environment variables (assuming it's a windows box) and added those commands to the path. try that first (google is your friend and you can google in XDA). Good luck.
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
thank you so much for quick respond..
I think I found it here how to do that.. (for someone like me... )
http://forum.xda-developers.com/showthread.php?t=532719
root
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
I haven't done this yet, but I'm dling the RUU right now to do it and help people troubleshoot.
To answer your question, if you hold down the power button long enough, the view will power off, then you can hold power + vol down to get back into the bootloader and select fastboot mode, then open cmd, type fastboot devices and check to make sure yours shows up, then proceed with pushing the mini-ruu. If I'm wrong guys, correct me. Hope it works out for you.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
Im not sure if this matters, but when I was in soft brick, I rebooted a few times and could not get into the bootloader. It just seemed to ignore the vol down keypress. I then unplugged the usb, powered off from soft brick, and held the vol. down button down even before I hit the power button as I was turning it on. Once I was in bootloader, I just plugged the usb back in.
EDIT: More tips:
1.After I flashed the initial stock ruu, and before I accepted any updates, I turned off fastboot in the power options and enabled usb debugging.
2. I did this from a Windows 7 laptop. When I initially tried to perform the softbrick steps, I got an access denied error message. The files were sent ok, but errored on saving. I closed the command prompt, and re-lauched the command prompt as administrator. The commands sent successfully.
3. Also, once you send the mini ruu over, the Tablet sat in the the oem loader with a 70% full progress bar after I successfully sent the mini ruu. I waited about 10 minutes because I was unsure how to proceed. I finally issued:
fastboot reboot-bootloader
Once back into bootloader, I mounted usb storage, copied SU to the card, and flashed from zip
risb577 said:
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
Click to expand...
Click to collapse
Yeah, rom manager won't work bc we don't have official support from Koush for CWM recovery so that's no issue, I was just curious is all lol. I'm glad to hear titanium detects root, as that was an issue initially for the view. Try to backup your apps, test radios (3g, 4g, wifi, bluetooth, GPS, ETC), run quadrant. I don't know how familiar you are with honeycomb to test out all of it's functions, but we are going to need a few people to test this out for globatron so he can make fixes and/or adjustments as necessary, which is why he specifically asked for devs and people familiar with troubleshooting to do this first. That's the beauty of open source, we're all guinea pigs.
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
soft brick screen
ElAguila said:
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
Click to expand...
Click to collapse
It looks like this pic. Plus another clue you are soft bricked is it stays here longer than 10 minutes if you care to wait lol
OK so I have the Sprint EVO 4G LTE with 1.22.651.3 on it, rooted, S-ON. I have the Team Win Recovery Project v.2.1.8 on it as well with hboot 1.15. I tried loading the newest rooted software 2.13.651.1 710RD and voila.... paperweight. I tried reloading 1.22.651.3 and nothing. I can still boot to the bootloader and TWRP recovery, but nothing seems to work and now because sprint screwed up and removed my total equipment protection service from my plan, I don't have insurance on the phone. PLEASE HELP!!!
You just need to flash the kernel, extract it from the Rom (boot.img) and place it in adb folder, connect phone I'm bootloader and type fastboot flash boot boot.img
You can also flash meanrom, it has a working kernel installer, just let it sit because the kernel installer does take awhile 5-10 minutes
om4 said:
You just need to flash the kernel, extract it from the Rom (boot.img) and place it in adb folder, connect phone I'm bootloader and type fastboot flash boot boot.img
You can also flash meanrom, it has a working kernel installer, just let it sit because the kernel installer does take awhile 5-10 minutes
Click to expand...
Click to collapse
Can you explain how to do this in greater detail? I'm experienced only enough to be dangerous to myself lol
This program should install the kernel that you need. If not you are supposed to be able to swap boot.img files that it will install.
http://forum.xda-developers.com/showthread.php?t=1917106
http://forum.xda-developers.com/showthread.php?t=1752270
This is for the One S but it's the same process for our phones also.
Sorry I've been in a low coverage area and just got home. Open the Rom, extract the boot.img, open adb folder or SDK, hold shift and right click, select open command window here, connect phone in fastboot and type fastboot flash boot boot.img
So I tried to use that program to flash the boot.img from the fastboot screen but the computer wouldnt connect to the phone... now what?
Boot from system into hboot and fast boot while plugged in via USB. Helps your PC determine drivers.
Also, if you need a guide for setting up adb/fastboot, Google a YouTube vid by qbking77 on how to unlock galaxy nexus bootloader, it links to a great tutorial.
from my flying AOKP'd Evo LTE and xda premium
do you have SDK installed on your computer? If not install it. Go through the setup (set up your your environment variables) for fastboot.
Make a copy of the boot.img from a ROM of your choice. Place it in a folder on your desktop name the folder (android) leave the folder open.
Open cmd
Type cd Desktop press enter
Type cd android press enter
Type fastboot flash boot boot.img
After that it should say sending then OK
After that go into recovery then flash the ROM
you should be good to go then...
Sent from my EVO using xda app-developers app
The full SDK is not necessary, just the debug tools
ADB Tools
Also you can directly open the command prompt from within the folder by holding shift and opening the context menu (shift+right click) then select open command window here
i keep getting a message in windows "usb device not recognized" so i switched usb cables and finally got that program to load the boot.img file, then flashed a rom in bootloader but its still not booting... any ideas?
Did you make sure to wipe the phone first? What rom are you trying to flash?
wiped phone first and now trying to flash 2.13.651.1 after loading boot.img thru that program
you have to find a way to update your twrp to version 2.2.0 cause this is the culprit that gave you the issues. did you make a backup try doing a restore to get back up and running then download goomanager from the google play store and install the latest twrp here is a video to update to the latest twrp through goomanager.
twrp downloads I dont know if you have to be s-off to install in bootloader or not. maybe someone could clarify that
ok so i tried flashing twrp 2.2.2.0 and got a message saying "main verison is older" then it said "update failed!" which is weird since i had version 2.1.8.0 to begin with i think.
anyone? any ideas? I feel like my only resort is to have it replaced
You could fastboot flash the recovery image. Thats how I usually do it
So download the recovery image from twrp website and place it in your a dB folder. I don't have my PC but I think the command is fastboot flash recovery "recovery image"
Sent from my EVO using xda premium
corcgaigh said:
You could fastboot flash the recovery image. Thats how I usually do it
So download the recovery image from twrp website and place it in your a dB folder. I don't have my PC but I think the command is fastboot flash recovery "recovery image"
Sent from my EVO using xda premium
Click to expand...
Click to collapse
this should be the correct code to type
fastboot flash recovery openrecovery-twrp-2.1.8-jewel.img
Or
fastboot flash recovery openrecovery-twrp-2.2.2-jewel.img
Depending on how twrp names their recovery image
Sent from my EVO using xda app-developers app
Ok so i updated the twrp by changing the txt file to the proper software number.... then i flashed the lastest software version and NOW IT STARTS!!! WOOOHOOO!!!! Thanks everyone!!
Hi, my friend has an htc evo 4g lte that he wanted to update. He uses this phone just for tethering. He intalled the last ruu that was released. After installing he was able to root and install custom recovery. The problem is when I install superuser it gives an error that reads "there is no SU binary installed". And when I run root checker it says that the device does not have proper root access. He gave me the task to fix it for him but I am stomped. I thought that it was gonna be easy like my samsung but this is so different. If anyone can figure out what I need to doo, pls point me in the right direction. All I need is to get supeuser to work so I can run the tether app.
javi_emma said:
Hi, my friend has an htc evo 4g lte that he wanted to update. He uses this phone just for tethering. He intalled the last ruu that was released. After installing he was able to root and install custom recovery. The problem is when I install superuser it gives an error that reads "there is no SU binary installed". And when I run root checker it says that the device does not have proper root access. He gave me the task to fix it for him but I am stomped. I thought that it was gonna be easy like my samsung but this is so different. If anyone can figure out what I need to doo, pls point me in the right direction. All I need is to get supeuser to work so I can run the tether app.
Click to expand...
Click to collapse
It looks like he's on the updated partitions.
Post 3 in the following thread:
http://forum.xda-developers.com/showthread.php?t=2639180
will give you the link for the recovery you'l need to flash (2.7.1.0b) using fastboot or via PJIMG75.zip
Then you just need to boot into recovery and install SuperSU_1.94.zip, reboot and enjoy.
You can't just install superuser or SuperSU from the play store and have it root itself.
Thanks for pointing me in the right direction. I will try this and post back with an update. Apreciate your help!
I decided to flash the recovery using fastboot but ran in to a problem. I installed the android sdk to my pc and the htc drivers using htc sync. I ran cmd and it detected my device. I downloaded the recovery that was recomended above and placed it in the platform-tools file. When I go to flash the file using fastboot I type: fastboot flash recovery and the name of the file that I downloaded. When I click enter it says error: cannot determine image file name for<name of file that I downloaded>.
So I am stuck here atm. Gonna quit for today and retry tomorrow. If anyone notices what I am doing wrong please post.
UPDATE: finally got it to work. All I had to do was to edit the name of the downloaded recovery to end with .img and it flashed succesfully.
javi_emma said:
I decided to flash the recovery using fastboot but ran in to a problem. I installed the android sdk to my pc and the htc drivers using htc sync. I ran cmd and it detected my device. I downloaded the recovery that was recomended above and placed it in the platform-tools file. When I go to flash the file using fastboot I type: fastboot flash recovery and the name of the file that I downloaded. When I click enter it says error: cannot determine image file name for<name of file that I downloaded>.
So I am stuck here atm. Gonna quit for today and retry tomorrow. If anyone notices what I am doing wrong please post.
Click to expand...
Click to collapse
Try this
Type fastboot flash recovery
Then drag and drop the twrp.img into the cmd window
I am trying to install any ROM, recovery but no luck for 2 weeks!!!
It was unlocked via HTC unlock_code.bin. Now I can relock or unlock again with no issue.
However I could not install any CRW . So I have to install stock RUU, CID is VODAP102 German Vodaphone. main versiyon: 2.17.161.3 , hboot: 1.72.0000
I relocked via fastboot and tried to install stock RUU however it was lower than 2.17.161.3 and gave signature error. I could not find higher RUU.
Is this a garbage now ?
-----
SOLVED: I pressed the left top part while recovering and it booted up recovery. Very interesting
alan02 said:
I am trying to install any ROM, recovery but no luck for 2 weeks!!!
It was unlocked via HTC unlock_code.bin. Now I can relock or unlock again with no issue.
However I could not install any CRW . So I have to install stock RUU, CID is VODAP102 German Vodaphone. main versiyon: 2.17.161.3 , hboot: 1.72.0000
I relocked via fastboot and tried to install stock RUU however it was lower than 2.17.161.3 and gave signature error. I could not find higher RUU.
Is this a garbage now ?
-----
SOLVED: I pressed the left top part while recovering and it booted up recovery. Very interesting
Click to expand...
Click to collapse
If you already successfully unlocked the phone thats a good news. and please keep your unlock_code.bin for future use. Anyways if u can follow all the instruction given in this forum it's not that hard to solve your problem. there are multiple solution for the problem you are facing.
So, well i hope u can still go to the fastboot mode right? if u can then u can use the adb push functions to install a recovery in your HOX+. follow the procedure below to install a recovery:
Unlock the phone again like you did before.
install a recovery:
please download the files u going to need to install the recovery:
a) https://goo.im/devs/philz_touch/CWM_Advanced_Edition/enrc2b/philz_touch_6.19.3-enrc2b.zip/
b)http://d-h.st/rNC all credit goes to m0narx (team venom).
c)before you can do anything u must need to have adb drivers installed on your pc and HTC usb driver to get your phone when you are in fastboot mode. since u already unlock the phone i hope you have those.
i hope you downloaded the abode files needed
1. You need adb drivers installed on your pc and HTC drivers. once this process is done go to fastboot and connect your usb to the phone. your phone will show fastboot USB.
2. In the kernel flasher you will see a rar file containing many files. just unrar the file and go to the folder, you will see a file called VenomKernelFlasher.exe. open it as administrator . then go to manual tab...then only click on flash recovery image and uncheck other options... then click browse and find your philz recovery that you downloaded early(you have to unzip if its a rar/zip). then you just have to press start flash. keep in mind your phone must be connected in fastboot mode and showing fastboot USB before you press start flash or it will do nothing. there are sometimes the first try wont work. venom flasher may show you an error. but don't worry. press start fash again and you might see successful and you have a recovery in your phone.
now you can go to the recovery mode by pressing power+volume down key and then recovery.
If you successfully done the above process now you just need to install a custom rom in your device from philz recovery and have fun with your phone
I think your phone completely blank and you dont have any rom copied in your phone's memory. now only way to install a rom is go to philz recovery.
I am giving you all the easy proess so that u dont need to know any adb command.
DOWNLOAD this another useful software, WinDroid Universal Android Toolkit: http://forum.xda-developers.com/showthread.php?t=2727916
a)go to philz recovery...then go to install zip....then go to install zip from sideload.
b)on the pc now you go to the toolkit then go to adb commands then press sideload ROM and a box will appear. then you just have to browse your custom rom of your own choice. and wait till it finished. there will be no progress bar. but in the toolkit when the process is done it will show you a message. also in the phone. wait for it to complete.
suggested rom:
Download Android Revolution HD 8.0 from here: http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
go to htc one x+ section adn download both rom and boot.img.
AFTER YOU COMPLETED THE ABOVE PROCESS YOUR PHONE HAVE A CUSTOM ROM INSTALLED IN YOUR DEVICE. IF YOUR PHONE IS S-ON THEN FOLLOW THE LAST STEP TO SUCCESSFULLY BOOT YOUR PHONE:
now you going to need the boot.img that you downloaded....you have to push the boot.img with adb shell to boot your android phone.
if you know how to do it then fine. if not pm me i will help you out with this also.
I installed SultanXDA's CM13 ROM and I am using TWRP (not the 3 version). I haven't installed SuperSU, so it means that I am not rooted, too... But...
I wanted to flash this camera: http://forum.xda-developers.com/one...t-oxygenos-3-0-1-beta-camera-cm-aosp-t3386799
The problem is that when I get to recovery mode in order to install the zip file, I see all kinds of folders, but not my "normal" ones... I am using my SD card as internal space...
I read somewhere that I have to update to new TWRP 3 in order to overcome this...
So, does it have to do with the version of twrp and if so, how can I update it without being root and without being able for the current TWRP to read the zip files that I will "feed" it?
Maybe my only method is through adb?
Flashing through adb will erase anything else other than changing the TWRP version?
Thanks in advance guys!
dimxr said:
Maybe my only method is through adb?
Flashing through adb will erase anything else other than changing the TWRP version?
Thanks in advance guys!
Click to expand...
Click to collapse
If your Bootloader is unlocked try Fastboot.
Reboot OPX into Fastboot Mode. (Power + Volume Up i think or trough TWRP or CM)
Connect it to your PC
On PC: Download the latest TWRP img File
Start CMD in same Folder as the downloaded File is.
Type: 'Fastboot devices' to make sure your OPX connected properly
Typ: 'Fastboot Flash Recovery *DownloadedTWRP*.img'
Flashing new TWRP only overwrites current TWRP and doesn't erease anything else
OverBit said:
On PC: Download the latest TWRP img File
Click to expand...
Click to collapse
Can you download it?
I can't seem to be able to start a download no matter which browser I use...
dimxr said:
Can you download it?
I can't seem to be able to start a download no matter which browser I use...
Click to expand...
Click to collapse
Without any problem.
Maybe you be able to download it when i attach it.
Was to big to upload it as img, so I renamed it to .apk,
So don't forget to rename it to .img
Great! So, the procedure begins!