Related
Even being a Linux user for 3 years I had difficulties flashing (herer the Cyanogen) Image. I didn't find all of the steps into one post, so I aggregate them for the completely "idiot" here:
1) Have an SD-card (FAT32 or ext3) inside the phone. .ZIP or .IMG files will be put there to be installed on the phone.
On the phone TURN ON: Settings>Applications>Development>USB Debugging
2) Find your Magic Version (32A or 32B, most probably 32A). Answer Number 1.1 at wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking
3) DOWNLOAD ANDROID Programs:
a) Android-SDK from developer.android.com/sdk/index.html and unzip. Later you will work inside the folder tools or put the app. adb into the PATH
b) Fastboot from android-dls.com/wiki/index.php?title=Fastboot, unzip and move the program into the folder tools or put it into the PATH
4) Gain ROOT access to your Phone's OS from android-dls.com/wiki/index.php?title=Magic_Rooting
NOTE: Follow Method 2.
5) INSTALL Amon_RA's Recovery Image (its the Best) from forum.xda-developers.com/showthread.php?t=530492
SUGGESTION: Use 'via adb' method, that is:
Having the the phone normally started, plugin the USB.
From the turn on USB and copy the recovery_XXX.img file to the SdCard.
On a PC-shell give:
sudo adb shell
#flash_image recovery /sdcard/recovery_XXX.img
#exit
6) Reboot into that recovery image and keep a NANDROID backup.
a) Close the phone.
b) Hold HOME+POWER-ON buttons together for a few seconds. Wait until the menu shows up.
c) Go to backup option and make it. The backup will be automatically saved on the SD card.
d) Reboot normally and save the nandroid Backup folder from Sdcard to your PC.
7) INSTALL (aka Flash) the ROM.
For the Cyanogen MOD download the LATEST version of 3 .ZIP files from forum.xda-developers.com/showthread.php?t=592377
a) HTC Android 1.6 base image (named DRC83_base_defanged or the like)
b) an update _XXX.ZIP file
c) a "kernel port" (name something like bc-XXX_signed.zip)
Beware all the files have the same version!
Then follow the easy and simple steps noted in forum.xda-developers.com/showthread.php?t=568032
It took me an afternoon to collect all this info that is scattered here in there in the forum.
Thank you all!
Except that you cannot flash the recovery via that method if your current rom is stock (no root).
eyegor said:
Except that you cannot flash the recovery via that method if your current rom is stock (no root).
Click to expand...
Click to collapse
You are correct! I edited my post. I had made myself this step but I thought root access would be covered using RA's Recovery. There are so many little steps and nowhere are explained all in one place. Thanx...
I see no reason to call these people IDIOTS. That's such a shame.
If you're going to make this guide for idiots, why don't you make it say what the guide is actually for?
C0dy said:
If you're going to make this guide for idiots, why don't you make it say what the guide is actually for?
Click to expand...
Click to collapse
hey can you please show me how you got your mytouch running on 2.1 pleasee
t3hflame said:
I see no reason to call these people IDIOTS. That's such a shame.
Click to expand...
Click to collapse
The expression was not meant like that. It included me and intended to separate the newbies that can easily browse to the forum and gather this scattered info from those that cannot have such ability and wished all these steps are logged into ONE post. Again, never meant in "that" way.
Why dont you just suggest applying the recovery through flashrec instead of complicating it by separating it into 2 steps.
EDIT: Plus, the rooting method is NOT the same for all phones...
I think this is a good idea, but everyone should chime in so that we can have a method for every Magic
someone has just finished the psfreedom port to aria
Prerequisites
Rooted Phone
ROM using 2.6.29
Aria_Freedom.zip
Terminal Emulator
Recommendations
ClockworkMod Recovery
Installation
1. Grab the below ZIP File (Aria_Freedom)
2. Place ZIP file on /sdcard/
3. Reboot to Recovery
4. Make a Nandroid (this is for restoring your BOOT partition)
6. Flash Aria_Freedom.zip
7. Restart Phone
8. Make sure your touch screen is working (should be)
9. In a Terminal Emulator, and enter: insmod /system/lib/modules/psfreedom.ko
10. Jailbreak PS3 as per instructions here:
Restoring
1. Reboot into Recovery (remember USB doesn't work, so you'll have to use HOME+POWER or VOLDOWN+POWER depending on Recovery Image)
2. If using ClockworkMod Recovery (recommended)
2A. Select Nandroid
2B. Select Advanced Restore
2C. Select the backup to use
2D. Select Restore Boot
2E. Goto step 4
3. If using Amon_RA you will need to do a full nandroid restore
4. Reboot the phone!
Credits:
KaKaRoTo -> PSFreedom
alephzain -> HTC Hero (cdma) Diff File
magicbyrdman_ -> testing / confirming
Klutsh/Decad3nce -> Troubleshooting
Koush -> AnyKernel Updater
Anyone else I missed.
Download (mirrors):
http://www.mediafire.com/?c52xc25it9eo9g5
updated this pages prereq's
im having problems sorry new to this but whenever i try to insert psfreedom.ko i get operation not permitted can anyone explain why that is? please and thank you
try typing su then hit enter key then try it
thanks it worked
I'm dumb what is this?
Sent from my Liberty using XDA App
ycode90 said:
I'm dumb what is this?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
It enables homebrew apps on the PS3, as long as your firmware is 3.41.
Work great thanks for all
for those who are having problems the link to the software is great
1. make sure you have a terminal program installed
2. make a nandroid back up
3.boot into recovery clockwork etc
4. flash the aria freedom zip which you get from the link in the first post
5.reboot
6.go into the terminal and type in: su(required if not you will get an error): insmod /system/lib/modules/psfreedom.ko
7.if it looks like an error its not just proceed with the jailbreak
worked for me
does anybody know how to port the payloads over?
AsbestOS loader needs a newer payload
A PSF recovery image for ARIA
FFXTDS said:
does anybody know how to port the payloads over?
AsbestOS loader needs a newer payload
Click to expand...
Click to collapse
If the test recovery image I made is functionnal, you shouldn't worry about that.
I put online a test recovery image for ARIA here.
Report me error or success (obviously).
alephzain said:
If the test recovery image I made is functionnal, you shouldn't worry about that.
I put online a test recovery image for ARIA here.
Report me error or success (obviously).
Click to expand...
Click to collapse
How do I flash this?
i figured out how to flash it
when i pick load asbestos it say sucessfully loaded and psfreedom enable but the ps3 don't recognize it it boot as normal
Sent from my HTC Liberty using XDA App
FFXTDS said:
How do I flash this?
i figured out how to flash it
when i pick load asbestos it say sucessfully loaded and psfreedom enable but the ps3 don't recognize it it boot as normal
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Which is your PS3 firmware version ? Because asbestos provided in psf-aria zip file only support 3.41 firmware.
But before, important question, does the jailbreak work ?
Can you test if ADB and Mass storage work in recovery ?
I can help you but you have to send me more information rather than : it boot as normal .
Enable kernel log before loading asbestos or plug the phone on your ps3, once enable plug your phone on ps3 and launch it with power + eject. Wait the ps3 load in xmb and reboot your phone in recovery if adb work or android if not the case and pastebin the file content in /sdcard/psf-kernel.log and send me the link on irc.
But before doing that, I invite you to download this psfreedom module and copy it in /sdcard/psfreedom/modules/.
It enable verbose debug log kernel message and will help me to find the problem.
i have a 120GB slim v3.41. it does jailbreak. Mass storage does work i don't know how to do adb.
did you get my link on irc?
how do i setup wifi for updating PSF through net?
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT06NR003843 recovery
FFXTDS said:
i have a 120GB slim v3.41. it does jailbreak. Mass storage does work i don't know how to do adb.
did you get my link on irc?
how do i setup wifi for updating PSF through net?
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT06NR003843 recovery
Click to expand...
Click to collapse
I saw your link, thanks. Asbestos don't work anymore with last version of psfreedom, there is a minor bug who will be corrected soon. I put the fix to KaKaRoTo branch. And release the final image with update in same time.
For wifi connection you have to go in "Update (net)" menu, first time it will copy you configuration file from android in /sdcard/psfreedom/wifi/wpa_supplicant.conf.
Edit wpa_supplicant.conf to let only your home network. That's all.
Ill put a readme in the final recovery image archive to explain how to setup wifi.
OK
Sent from my HTC Liberty using XDA App
Final recovery image available here.
Fix Asbestos loading.
Include last PSFreedom and PL3 version
Content :
- recovery.img
- psf-aria-110110_153912.zip
- README.txt
For future updates go on psfreedom wiki.
it don't seam to be working right usb mass ant working and asbestos ant working right the phone reboots to recovery when ps3 boots and the ps3 show a black screen. maybe i did something wrong. it jailbreaks though if i don't pick asbestos
FFXTDS said:
it don't seam to be working right usb mass ant working and asbestos ant working right the phone reboots to recovery when ps3 boots and the ps3 show a black screen. maybe i did something wrong. it jailbreaks though if i don't pick asbestos
Click to expand...
Click to collapse
Its normal, the phone reboot once jailbreak is done or asbestos stage2 loaded. You have a black screen because you have to setup a tftp server and configure dhcp server, so you have to connect your ps3 to your network, the asbestos stage2 try to get dhcp lease with the boot filename to download, if not found the ps3 stop and the red led blink. Follow instruction here
Oh made a mistake with mass storage, so re-download the final recovery image and reflash recovery.img. It should be ok.
Ok
Sent from my HTC Liberty using XDA App
I have seen so many thread with same questions all over in One X Q&A, so I have tried to pool all questions in one place and provide the answers.
Mod*- This should be in Q&A because i think people who do not read posts in General and come back and post questions in Q&A
First and Foremost
........................................Please please Read Read Read Read Read Read before you post or flash anything...................................................
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question 1 - How to root 2.20 firmware
Answer
If you want to do all this in more easy way (i.e using GUI) then i would recommend you to follow - [TOOL] HTC One X (Evita) All-In-One Toolkit V1.1 [10-28-12] [PERM ROOT][Noob-Proof]
Step 1 - Setup the environment which will help you in rooting your device
1) Download Android SDK from here {For Windows}
2) Download java if you need it - here
3) Only for windows - Download htc sync ( It will install necessary htc drivers) - Link
4) Just to check if htc drivers installed properly , open "C:\android-sdk\platform-tools" ( Or folder where adb and fastboot exists) then "Press shift + right click and select "Open command window here" ( open command prompt and cd "folder where adb and fastboot exists).
5) In command window type " adb devices" and see output - If you get output then htc drivers installed properly.
"Info - What to learn about more about adb then goto - [HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - Tutorial
Fastboot - Link"
You can skip step 4 & step 5 - These steps are only for verification .
6) Goto [ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit and follow the instructions there.
7) I hope you successfully rooted your device (If not look at the FAQ)
If you think above instructions are difficult to follow then - There is awesome guide by XsMagical [ROOT][2.20][hboot 1.14] One XL Bootloader unlock & Root guide
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question 2 - How to Installing custom recovery
1) You need follow the instructions listed here - Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=33179690 ( Thanks to GuyIncognito721)
I have further simplified the instructions which are listed in above link , so that they are more noobbbbb friendly (noobbbb - people who cannot read and follow instructions )
1) Download custom recovery, TWRP is preferred: http://teamw.in/project/twrp2/99
Info"""" Reason to use TWRP -
CWM does not officially support our device, and its just a port. Due to this, CWM has some serious and known problems. As already mentioned, USB mount doesn't work. Also, it has been known in some cases to cause some major issues with dialer and other phone functionality after flashing a ROM. Problems that persist even if you try flashing another ROM or restoring a backup. These problems are difficult (although not impossible) to fix, and a big headache.
TWRP officially supports our device, gets regular updates. Its fully working, and its recommended by almost all (if not all) our developers." (Thanks to redpoint73) """""
2) Make sure the file you downloaded "openrecovery-twrp-2.2.1.0-evita.img (for example) should be in same folder where adb and fasboot present ( How to make sure = You need to copy the file in the folder where adb and fasboot present)
Example - If you downloaded android sdk then the downloaded file should be in "C:\android-sdk\platform-tools" folder.
Look at twrprecovery1 - image in the attachment
3) Then open command prompt in the same folder ( by pressing shift+right click and select "open command window" here) or open command window and type cd C:\android-sdk\platform-tools (or change to directory where adb and fastboot exists)
4) Then Run the following command fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img (openrecovery-twrp-2.3.1.0-evita.img is the file name which you downloaded) in command prompt
5) Then run the command fastboot reboot in the command prompt (phone will reboot, so do not panic)
6) Run the following command after the phone is rebooted adb reboot recovery
7)You should be in the new TWRP recovery.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
From here follow the instructions below to flash custom roms
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question 4 - How to flash Custom ROMS
Info - We have two development forums
One X Android Development - For custom roms based on sense
One X Android Orgnial Development - For ASOP, CM10 roms
1) Download the ROM of your choice on to your pc from above links
2) Once you downloaded the ROM of your choice, then extract the ROM.zip ( that mean you need to unzip it )
For example you downloaded CM10 -cm-10-20121012-NIGHTLY-evita and extracted it . Now you can see the boot.img in the folder you extracted. (( See the extract image in below ))
For example you downloaded Nocturnal Megre X rom and extracted it. Now you can see the boot.img in the folder you extracted. (( See the extract1 image in below ))
3) Now copy the boot.img from the extracted folder and paste in folder where fastboot and adb are present ( if you downloaded Android then paste it in C:\android-sdk\platform-tools )
Your folder where adb and fastboot present should now have boot.img of the ROM you extracted
4) Put phone into bootloader mode,
Either by opening command prompt in the same window where you placed boot.img (i.e where adb, fastboot is present) and running the command adb reboot bootloader in command prompt ( do not close the command prompt)
Or, since your phone is in recovery , select "Reboot" then Bootloader .
Note*- You always can get into bootloader by pressing power button + volume down for 10-15 sec. Also from there you can get into recovery by using volume keys to select recovery and pressing power button to enter into recovery
5) Once your phone is in bootloader mode, type the following command fastboot flash boot boot.img ( If command prompt is closed then open command prompt in the folder where boot.img, adb, fastboot are present . For example: C:\android-sdk\platform-tools - Same folder used in step 3)
5) Then run the following command adb reboot recovery
6) Your phone is in TWRP recovery
7) Select mount from recovery ( See mount - image in the attachments for example)
8) Copy the ROM.zip which you downloaded earlier to the SD card ( For example cm-10-20121012-NIGHTLY-evita.zip) ( Not the extracted folder but the actual zip file which you downloaded)
4) Copy the gapps into sd card ( you need to download gapps if you using CM10 or ASOP roms )
5) Unmount, then select Wipe and select Factory reset ( it is recommended to do a factory reset before flashing the new ROM. ) (See wipe, wipe1 images below )
6) Select Install in recovery and flash the ROM.zip
7) You need flash gapps if you flashing CM10 or ASOP ROMS
8) Enjoy
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1) If you keep getting htc red screen ( saying " This Build is for development only") then it does not mean you bricked your device. It means you forgot to flash boot.img or missed some step
2) if you are flashing similar ROMs ( having same kernel ).. there is no need to flash boot.img separately. But say if you wanna switch from sense to aosp you must do that as they have different kernels.
Again if you are just upgrading from older version to newer version of same ROM and if there are no kernel changes no need to flash it" (thanks kancherlapraneeth)
3) Another scenario, if you struck in boot for every long and you panicked and you did factory reset. After you can access only twrp recovery then do not worry, do the following
"plug in phone to your computer and enter twrp, choose "mount". Get on your computer and download Rom of choice. Once downloaded, extract Rom and seperate the boot.img. rezip Rom. Transfer Rom onto phone.
fastboot boot.img, then flash the Rom through twrp. Then your golden" (Thanks to InflatedTitan) ( Do not understand fastboot , boot.img then read above)
4) If you flashed an internation rom or rom which is not for our device and bricked your device then follow this link , the OP has similar problem and people helped him
5)Which version of super user do I need to flash [/B
In above instructions, after you installed Custom recovery you flashed custom ROM then you already have it ( since you rooted) , so check the root with app called root checker.
"If your on stock with twrp installed then it was a temp root, so root is gone after you reboot, but it allowed for a permanent boot loader unlock. So you will need to flash an su binary package and then download a superuser app from the play store." (thanks to absolutelygrim) (Case where you did not unlock the bootloader but just rooted and rebooted. ) then download http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip (Superuser zip ) and flash in recovery ( same way we flash custom ROM or gapps.) then download supersu from the market and update the binaries
Anyone correct if I wrote something wrong or need to be changed.
Mods - Delete if you find it unnecessary
I find this a good idea.... I feel we should sticky things like this in the q/a and not have one hundred threads of the same problem...like this stickied... We could have different popular subjects stickied and so not so many threads would arise
---------- Post added at 05:14 PM ---------- Previous post was at 05:13 PM ----------
This is like a all in one thread good job!
Bro you did a damn good job on this. If a noob can't follow this, he doesn't need to be hacking anything. I mean for god sakes you've included pictures lol. Even though you've included steps and the fastboot commands, What about adding a link to gunnyman's quick anb dirty adb and fastboot tutorial? Rich in knowledge
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
I hope I don't sound stupid, but can we flash kernels after using the 2.20 Root method? Or should I not risk flashing a kernel?
InflatedTitan said:
Bro you did a damn good job on this. If a noob can't follow this, he doesn't need to be hacking anything. I mean for god sakes you've included pictures lol. Even though you've included steps and the fastboot commands, What about adding a link to gunnyman's quick anb dirty adb and fastboot tutorial? Rich in knowledge
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Click to expand...
Click to collapse
Thanks bro, I forgot about that tutorial . I will add it now
I gotta say, I'm proud of our little community. I really haven't seen any harsh words or flaming of the recent wave of noobs, even though a lot of problems could have been easily avoidable on their part. Great job for those who have helped someone recently. I'm sure those in need appreciated it, even if they haven't hit the thanks button. They'll soon see how great the HOXLers are!
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
InflatedTitan said:
I gotta say, I'm proud of our little community. I really haven't seen any harsh words or flaming of the recent wave of noobs, even though a lot of problems could have been easily avoidable on their part. Great job for those who have helped someone recently. I'm sure those in need appreciated it, even if they haven't hit the thanks button. They'll soon see how great the HOXLers are!
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Click to expand...
Click to collapse
+1 bro really we are awesome community who keep helping without ranting or flaming
Sent from my HTC One XL using xda premium
InflatedTitan said:
I gotta say, I'm proud of our little community. I really haven't seen any harsh words or flaming of the recent wave of noobs, even though a lot of problems could have been easily avoidable on their part. Great job for those who have helped someone recently. I'm sure those in need appreciated it, even if they haven't hit the thanks button. They'll soon see how great the HOXLers are!
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Click to expand...
Click to collapse
This probably is the most friendly community I've seen on xda..flaming only appears here when obviously deserved ...but holy critters I don't know how many bricked threads j saw when I woke up yesterday
Well done this should be put in the recourse, compilation roll-up.
Sent from my One X using xda premium
Amazing write up. This would have helped me tremendously but I managed to figure it out late last night.
Definitely appreciate people like you, and developers, that take time out of their "real" lives to do things like this for the benefit of others. Thanks!
Sent from my One X
bumpy bump
Crappyvate said:
bumpy bump
Click to expand...
Click to collapse
@crappyvate I learned that no use of writing all this, no one reads them
Sent from my HTC One XL using xda premium
abhipati said:
@crappyvate I learned that no use of writing all this, no one reads them
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
i forgot which dev said that but to paraphrase : "if you want to make sure something is not read, put it in the OP"
funny (sad really) but truw
Crappyvate said:
i forgot which dev said that but to paraphrase : "if you want to make sure something is not read, put it in the OP"
funny (sad really) but truw
Click to expand...
Click to collapse
If you want to make sure no one sees that than make it a sticky
Sent from my HTC One XL using xda premium
abhipati said:
If you want to make sure no one sees that than make it a sticky
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Sadly ...very true and its unfortunate because this is actually.very clear and helpful and.if they took five minutes to read and analyze they'd never have a problem
Hey, I'm a newbie but loving it. If I root my One X will I still be able to get the HTC jellybean update?
Thanks!
Green1534 said:
Hey, I'm a newbie but loving it. If I root my One X will I still be able to get the HTC jellybean update?
Thanks!
Click to expand...
Click to collapse
This should have the answer your looking for:
http://forum.xda-developers.com/showthread.php?p=27195248
Sent from my One X using xda premium
Trying to install ROM (CM10) and Gapps through TWRP and it fails to install. Says E: Unable to mount '/sdcard' and E:Unable to mount storage.
ul49 said:
Trying to install ROM (CM10) and Gapps through TWRP and it fails to install. Says E: Unable to mount '/sdcard' and E:Unable to mount storage.
Click to expand...
Click to collapse
which version of TWRP you are using.. use latest version if you are using older one
WARNING: Performing the actions decribed here will void your warranty and possibly brick your device. This was not written for complete noobs and assumes some prior experience. I will not be held responsible if you ruin your device.
NOTE: This was all tested on a stock iWork 10 Flagship dual boot (aka iWork 10 Ultimate) purchased from the manufacturers website. Device model is "i15 T", Device serial number starts with "i15TD": if you have another variant such as i15TL i can not vouch for any of this working the same way.is tablet
UPDATE: @popcorn2404 modified the boot.img on his USB Type-C variant if this tablet (i15-TCL), confirmed everything working well and was nice enough to provide the modified boot image. See downloads at end of post.
OTA: Most likely this will break OTA. Dont know yet...
Prerequisites:
PC with working ADB/Fastboot
Device properly recognized.
I'm using ubuntu 15.10 so I just added an entry to /etc/udev/rules.d/51-android.rules to get things going properly
(EDIT: Windows 64 bit usb drivers attached to post -thanks @Jade.J.Munkey)
TIP: I would highly recommend extracting your stock recovery, boot and system images for safekeeping. These can easily be flashed back in fastboot if something goes wrong. Some may say this is overkill as you will be able to backup and recover with TWRP, but one never knows...
Unlocking bootloader
WARNING: this will erase all data, settings, etc... AND system default language will be chinese when you reboot
Go to settings, about tablet and tap 5 times on the Build number to activate developer options
Go to Developer options and enable OEM unlocking & USB debugging
Plug in your device while booted into android, then open a terminal
just to make sure adb is good type
Code:
adb devices
my output looks like this
Code:
List of devices attached
0123456789ABCDEF device
reboot tablet into fastboot mode
Code:
adb reboot fastboot
The device will now reboot to the OS selection screen. Select android and then it will boot into fastboot mode
once again just to be sure all is good type
Code:
fastboot devices
once again, my output
Code:
0123456789ABCDEF fastboot
then to unlock the bootloader
Code:
fastboot oem unlock
you then should see something like:
Code:
...
(bootloader) Unlock protection is set
(bootloader) Unlocking anyway since this is not a User build
OKAY [ 15.330s]
finished. total time: 15.330s
This is what you should see now in the bootloader if all went well:
SECURE BOOT - DISABLED
LOCK STATE - unlocked
Your bootloader in now unlocked. When you reboot it will take some time for the first boot and the system language will have defaulted back to chinese. Not too difficult to sort if you're familar with Android settings. Otherwise just google "android change system language from chinese to english".
Tip: At this point you may want to already download/copy the supersu zip to internal storage of the tablet so you're all set up for flashing it later...
Modified boot.img
Because of built in security, if you make any changes to system the device will not boot, so you need a modified boot image.
If you have the exact same kernel version as I do you can download the provided modified boot image here. Otherwise you can look HERE for instructions on how to make your own modified boot image. Personally I used SuperR's Kitchen to unpack & repack the image and did the modifications manually with gedit.
Kernel version 3.14.37-x86_64-L1-R429 made on Wed Mar 2 18:22:46 CST 2016
-if you have that one you are good to go ahead and use the image provided here.
Boot device into fastboot connected to PC. From the directory where you have the modified boot image type:
Code:
fastboot flash boot i15TDboot.img
Obviously if you made your own boot image you'll need to replace "i15TDboot.img" with the name of yours...
That's it, now on to recovery and rooting...
Flashing custom TWRP (compiled by @vampirefo)
Assuming you are still connected to the device in fastboot and the custom recovery is in the same directory:
Code:
fastboot flash recovery i15t_recovery.img
Now use volume buttons to select recovery mode and tap power button.
You should now be in TWRP. First, please be smart and make a backup!
Because this device has an unusual mount point, the supersu script will fail to properly mount system (thus failing to flash) so:
From TWRP main screen select "mount" then select system, then return to main screen
Select "install" and then the supersu zip you should already have on the tablet.
Boot system. Now there is one thing left to do:
To prevent the system from overwriting TWRP with the stock recovery on the next reboot:
With a root enabled file manager mount system r/w and navigate to /system/etc
Rename install-recovery.sh to install-recovery.sh.bak
That's it. Enjoy!
If you're looking for more info on this device, check out Laura's great thread
Thanks
@vampirefo - for taking the time to compile TWRP for this device, you rule man!
Laura - for all the info she's made available for this device
@SuperR. - for his kitchen
@Chainfire
@popcorn2404
Downloads
TWRP recovery
Modified boot image (i15-TD)
Modified boot image (i15-TCL)
SuperSU
There will be additional resources for this device here
Delete
Windows 10 64bit fastboot driver for Cube iwork10 Ultimate
When the device is at fastboot, Windows Device Manager says "Cherry Trail CR" with a yellow exlamation point. abd works fine when it is booted in to normal android. Anyone have this driver or could tell me where to aquire it ?
Cube iwork10 Ultimate Fastboot driver for Windows 10 64bit
Jade.J.Munkey said:
When the device is at fastboot, Windows Device Manager says "Cherry Trail CR" with a yellow exlamation point. abd works fine when it is booted in to normal android. Anyone have this driver or could tell me where to aquire it ?
Click to expand...
Click to collapse
Thanks very much for the good work, I am successfully rooted. The only deviation from the instructions that occurred for me was that /system/etc did not appear in the TWRP file manager, fortunately the .sh did not run upon rebooting after installing the SU zip. So I just I just renamed the .sh in NextApp File Explorer with Root Add-On installed once booted in to android; I have since tested booting in to recovery and then back to android and it is working fine.
Here is the driver I found to enable the Cube iwork10 Ultimate to be seen by Windows 10 64bit whilst in fastboot:
onedrive.live.com/redir?resid=96BA73741E4680ED!5237&authkey=!ALGigNIfrlvxfvI&ithint=file%2czip
if anyone needs it. (remove space from url before pasting in to browser)
Jade.J.Munkey said:
Thanks very much for the good work, I am successfully rooted. The only deviation from the instructions that occurred for me was that /system/etc did not appear in the TWRP file manager, fortunately the .sh did not run upon rebooting after installing the SU zip. So I just I just renamed the .sh in NextApp File Explorer with Root Add-On installed once booted in to android; I have since tested booting in to recovery and then back to android and it is working fine.
Here is the driver I found to enable the Cube iwork10 Ultimate to be seen by Windows 10 64bit whilst in fastboot:
onedrive.live.com/redir?resid=96BA73741E4680ED!5237&authkey=!ALGigNIfrlvxfvI&ithint=file%2czip
if anyone needs it. (remove space from url before pasting in to browser)
Click to expand...
Click to collapse
Glad it worked out for you. Based on your experience I changed the instructions in the OP. Actually that's the exact same I did after doing this the first time but I thought it would be easier to do before first boot in TWRP. Anyhow thanks for pointing this out.
Attached windows usb driver to OP. Thanks!
Stock based, recovery flashable ROMs now available:
http://forum.xda-developers.com/android/development/rom-stock-cube-iwork-10-flagship-i15-t-t3372281
Can someone please make like a video for this or something more lames terms (user friendly). Cause i have a cube iwork 10 Ultimate Dual Boot (i15-TL) and am having issues on Android side where i do not have an option to move apps to sd card in apps settings. Also in storage there is no tab showing all apps on sd card. Im guessing i would need to root my device right? Can someone please help me i just want to get this working properly... i would show screenshots but i don't know how to attach them.
Will the recovery work with i15-TL?
Thank you in advance
flubber1911 said:
Will the recovery work with i15-TL?
Thank you in advance
Click to expand...
Click to collapse
From what I understand from reading at http://techtablets.com/forum/forums/cube/iwork-10-ultimate/
-it *should* work as my understanding is that the TD and TL are virtually identical other than different flavors of windows installed. But I can NOT personally confirm this as I have not tested on the TL variant.
What I can say with a higher level of certainty is that the procedure for unlocking the bootloader should be exactly the same. Once the bootloader is unlocked it is easy to reflash the stock recovery via fastboot should the custom recovery not work properly. (Assuming one has previously extracted an image of the original recovery to begin with. Same for boot and system images.)
So if the custom recovery does not work, it is pretty easy to reflash the original, as well as the original boot or system images should something else get messed up.
Hope this helps. Feel free to ask anything else if anything is unclear...
Sent from my OnePlus2 using XDA Labs
Thank you for your precise answer. I already successfully rooted my Cube. I need the recovery to flash the latest xposed sdk. I' ll have a look if someone extracted the original recovery.
geryalvi said:
Can someone please make like a video for this or something more lames terms (user friendly). Cause i have a cube iwork 10 Ultimate Dual Boot (i15-TL) and am having issues on Android side where i do not have an option to move apps to sd card in apps settings. Also in storage there is no tab showing all apps on sd card. Im guessing i would need to root my device right? Can someone please help me i just want to get this working properly... i would show screenshots but i don't know how to attach them.
Click to expand...
Click to collapse
The stock android on this device does not offer the option to move apps to sdcard.
Tools such as link2sd require a rooted device.
Sent from my OnePlus2 using XDA Labs
flubber1911 said:
Thank you for your precise answer. I already successfully rooted my Cube. I need the recovery to flash the latest xposed sdk. I' ll have a look if someone extracted the original recovery.
Click to expand...
Click to collapse
Yeah, no problem man. I'm curious to see how xposed works out, I've not got around to trying to install yet. Let us know here how that goes.
A copy of the original recovery from my i15-T(D) can be downloaded here: https://www.androidfilehost.com/?fid=24499762636003042
Sent from my OnePlus2 using XDA Labs
I installed an app called Rashr - Flash Tool on my phone. It says it can backup the recovery.
So I did; lets see then if your custom recovery works out
jetfin said:
The stock android on this device does not offer the option to move apps to sdcard.
Tools such as link2sd require a rooted device.
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Ok so i have i15-TL, with the instructions provided will i be able to root my Android? Also if i Root Android does anything happen with the Winows side? (I still would like a Dual Boot) So im looking to be able to move apps to my sd card, can someone please help me understand how to Root my device and be able to move apps to sd card? Any help would be greatly appreciated, and also thanks to Jetfin for replying my last post. Plz hlp...
geryalvi said:
Ok so i have i15-TL, with the instructions provided will i be able to root my Android?.
Click to expand...
Click to collapse
As clearly stated in the OP, I do not know for sure because I have not tried on that variant, but it *should* work. If you read a few posts back, you can see that another TL owner seems to have successfully rooted his device. Hot tip: *reading* is very important here before asking questions.
geryalvi said:
Also if i Root Android does anything happen with the Winows side? (I still would like a Dual Boot)
Click to expand...
Click to collapse
No, this will not affect the windows side of things. Dual boot is unaffected.
geryalvi said:
So im looking to be able to move apps to my sd card, can someone please help me understand how to Root my device and be able to move apps to sd card?
Click to expand...
Click to collapse
The instructions for unlocking and rooting in the OP are very simple and straightforward. If you are inexperienced in general with rooting android or with adb/fastboot, those answers can easily be found on XDA and elsewhere by searching.
As far as moving apps to SD, since nobody seems to have done it yet (or posted that they have) the only way right now would be to root your device and try out one of the specific apps for that like link2sd. I will try to check this out ASAP but can not promise how soon because I'm focusing my efforts right now on porting another ROM to this device...
Sent from my OnePlus2 using XDA Labs
I could cry right now ... At first I have to say that flashing the TWRP recovery worked flawlessly But always when I tried to flash the Xposed SDK I got an error saying: Updater process ended with error: 255 ( I have no idea how to fix that yet
flubber1911 said:
I could cry right now ... At first I have to say that flashing the TWRP recovery worked flawlessly But always when I tried to flash the Xposed SDK I got an error saying: Updater process ended with error: 255 ( I have no idea how to fix that yet
Click to expand...
Click to collapse
Did you manually Mount system in TWRP before flashing xposed?
Sent from my OnePlus2 using XDA Labs
jetfin said:
Did you manually Mount system in TWRP before flashing xposed?
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
No, do I have to do that? D
---------- Post added at 10:55 PM ---------- Previous post was at 10:51 PM ----------
Ok I manually mounted System, but it still doesn´t work ...
jetfin said:
As clearly stated in the OP, I do not know for sure because I have not tried on that variant, but it *should* work. If you read a few posts back, you can see that another TL owner seems to have successfully rooted his device. Hot tip: *reading* is very important here before asking questions.
No, this will not affect the windows side of things. Dual boot is unaffected.
The instructions for unlocking and rooting in the OP are very simple and straightforward. If you are inexperienced in general with rooting android or with adb/fastboot, those answers can easily be found on XDA and elsewhere by searching.
As far as moving apps to SD, since nobody seems to have done it yet (or posted that they have) the only way right now would be to root your device and try out one of the specific apps for that like link2sd. I will try to check this out ASAP but can not promise how soon because I'm focusing my efforts right now on porting another ROM to this device...
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply, so my question before i attempt to root my device is: if i follow the steps provided on OP will i loose any of my current information on my Android side? If so would i need to backup my android (How so). Sorry for all of hte questions but i am a noob on how to do this..
Thanks again
As the title states this guide will walk you through restoring your laf partition/download mode after root via the lafsploit method.
This guide is for the H918/T-Mobile variant ONLY!
Attempting to use the files provided in this thread on any other variant may result in a brick! You have been warned.
YOU MUST HAVE SOME FORM OF ROOT ACCESS FOR THIS PROCESS TO WORK!
Before we begin this guide will be relatively straight forward, and much easier than rooting the phone itself (IMO). That said when making any modifications to your device, and by following this guide you assume any & all responsibility for any damage physical or otherwise to your device(s).
Prerequisites/Downloads:
1. ADB & Fastboot drivers Download & install (If you don't already have them of course) from here: https://forum.xda-developers.com/showthread.php?t=2588979
(There are other ways to obtain them, but this is the simplest and most straight forward.)
2. I'm not entirely sure they are needed for this, but it wouldn't hurt to install the LG Mobile Drivers either found here: http://www.lg.com/us/support/software-firmware-drivers
3.I have extracted (from 10P KDZ) and tested this image myself before uploading, and now have download mode back on my v20. You can find it here: https://www.androidfilehost.com/?fid=818222786056038567 (Save to a location you can remember. If you're unsure go ahead and save it to your desktop.)
These remaining downloads are entirely optional, but I figured I would include them. Only download these if you intend to extract the laf.img yourself. (More details on that later.) (Not recommended for the average user.)
1. You'll need the kdz to extract the images from. Found here: https://lg-firmwares.com/lg-h918tn-firmwares/#more-3864 (You're looking for the H91810p kdz).
2.You'll also need to download the WindowsLGFirmwareExtractor found here: https://forum.xda-developers.com/showthread.php?t=2600575 (Be sure to leave a thanks for this awesome tool.)
Flashing the image
1. Begin by verifying USB debugging is enabled on your device. (If it is not go to Settings/About/Software Info. Click build number until you get the toast notification that you are a developer. Back out to Settings Click Developer Options, and turn on USB debugging.)
2. Plug in your device (Make sure it is in File transfer mode.)
3. Open up a command prompt (May require running as admin. I always do so I have no clue.)
Type:
Code:
adb devices
Your device should be listed if you have accepted the prompt on your device. (If you are not quick enough and accept the prompt, but it still shows nothing run adb devices again.)
4. If your device is listed navigate to where you saved the laf.img (again for the purposes of this guide I will be using the Desktop.)
Type:
Code:
cd c:/users/Type your windows username here/Desktop
You should now be in your desktop.
Type:
Code:
adb push -p laf.img /sdcard/laf.img
wait for it to complete.
Type:
Code:
adb shell
then
Code:
su
You will need to grant adb Superuser permissions on your device to continue. If you are successful you should see this "elsa:/ #"
Finally type:
Code:
dd if=/sdcard/laf.img of=/dev/block/bootdevice/by-name/laf
Wait for it to complete.
Type exit twice.
5. You can now unplug your device, power off, and plug in the usb while holding vol up to enter dl mode to verify it worked.
6. Success Congrats. You have download mode back on your device!
Extracting the laf image yourself(For the extremely paranoid)
1. Download the required files from above.
2. Extract WindowsLGFirmwareExtract v1.2.5.0 to your desktop, and open it up (preferably in it's own folder).
3.Select Open across from KDZ/TOT file, and browse to your KDZ you download previously and double click.
4.After it loads the kdz check H91810p00.dz, and click Extract KDZ.
5.Close and re open the program this time Click open across from DZ File in the folder where you placed WindowsLGFirmwareExtract you should see a file called H91810p00.dz Double click to open it.
6.Check laf_6.bin then click Extract DZ.
7.Rename the laf_6.bin to laf.img.
8.Follow the steps above to flash the newly extracted image to your device.
Credits:
@bullghost for the Extraction tool (And those in his credits as well.)
@runningnak3d (For lafsploit and the countless amount of hours he has put in to getting it working for us.)
reserved
Thanks man u r too good to us.
Sent from my [device_name] using XDA-Developers Legacy app
gavilan2010 said:
Thanks man u r too good to us.
Click to expand...
Click to collapse
Just trying to help give something back to the community. That said this my first guide. I tried to make it as simple as possible, and laid out in a way that's easy to understand and follow. So if anyone has any suggestions please don't hesitate to let me know.
Sent from my LG-D851 using XDA Labs
Or you could just flash the zip in TWRP to get laf back
xXCoolGuYXx said:
Or you could just flash the zip in TWRP to get laf back
Click to expand...
Click to collapse
What zip are you referring too?
Sent from my LG-D851 using XDA Labs
For insure purpose to return the phone how bout making a zip file flash it in twrp then reboot then everything is stock again. But i cant find any zip file to do that please point me to the right link if anybody know
Sent from my [device_name] using XDA-Developers Legacy app
gavilan2010 said:
For insure purpose to return the phone how bout making a zip file flash it in twrp then reboot then everything is stock again. But i cant find any zip file to do that please point me to the right link if anybody know
Click to expand...
Click to collapse
That's because one doesn't exist, but if you follow the OP instructions which are pretty simple then you should be golden
Sent from my LG-H910 using XDA Labs
I've had my h918 arb1 10u rooted for a month now, never noticed in twrp till now of an all in red "The partition cannot be located by the name "LAF".
Do I really need it?. I was coming from RR rom 8.0 back to Super rom 7.0 in twrp. While installing Super rom thats where I noticed the red worded statement in the list of rom install load. I was kinda startle cuz it's laf... I was like ahhh fkkk I'm gonna get bricked but then phone boots like normal, everything is normal, I even install other roms back n fourth just to test for anything else wrong but nope everything is good. I can still enter download mode with USB cord.. it acts normal, I can boot to twrp recovery normally from trwp app in stock super rom and advance menu on aosp roms too. So.... Is laf any important anymore?? Should I go ahead and and follow this guide for laf repair?....
(Edit)
Nevermind, Sorry.
I found that laf after rooting is not needed anymore cuz twrp occupies that spot. I did find a flashable laf restore zip in the thread by "[ROOT] - lafsploit - H918 (any version up to 10u) - now n00b friendly by runningnak3d".
Problem solved.
download link broken
Wanted to thank you this worked perfectly! I was in quite the predicament where I ran the LAF exploit in FWUL but I didn't downgrade before rooting. That made it so I couldn't flash TWRP to recovery and for whatever reason I couldn't boot into TWRP from download mode again (only worked once or twice) I couldn't flash in fastboot and I was sure I was screwed. THANK YOU!!!
dl link is broken, pls reup !
thx